Related
My university has a dedicated 802.1X connection specifically for mobile devices that I've been able to hook my Samsung Intercept (rooted, running 2.2) up to. The directions for connecting any Android platform to the connection is fairly straightforward:
Use these settings:
• EAP Method: TTLS
• Phase 2 authentication: PAP
• CA Certificate: (leave as N/A)
• Client Certificate: (leave as N/A)
• Identity: <GW NetID>
• Anonymous identity: (leave blank)
•Wireless password: <NetID password>
Click to expand...
Click to collapse
The thing is though, the NC's wireless tab doesn't allow for EAP Method input or Phase 2 authentication. Is there any way for me to access those protocols and connect?
MashableMe said:
My university has a dedicated 802.1X connection specifically for mobile devices that I've been able to hook my Samsung Intercept (rooted, running 2.2) up to. The directions for connecting any Android platform to the connection is fairly straightforward:
The thing is though, the NC's wireless tab doesn't allow for EAP Method input or Phase 2 authentication. Is there any way for me to access those protocols and connect?
Click to expand...
Click to collapse
Same as Android always is... Configure it as much as you can, then use this app to configure it all the way: http://www.appbrain.com/app/wifi-advanced-config-editor/org.marcus905.wifi.ace
Downloaded the suggested app, but for some reason whenever i moddify the protocols they snap right back as soon as i navigate away from the page. Any suggestions?
Same happened to me. It's the phase 2 encryption (PAP) that always snaps back. Tried on Nookie without any problem (just stock froyo wifi functionally, not by configuring wifi advanced configuration editor). So the there should be no hardware issue. I bet B&N's crippled OS lacks support for PAP.
MashableMe said:
Downloaded the suggested app, but for some reason whenever i moddify the protocols they snap right back as soon as i navigate away from the page. Any suggestions?
Click to expand...
Click to collapse
Haven't had any issues with my Nook Color and 802.1x/PEAP/TKIP/RADIUS/MS-CHAPv2.
In wifi advanced configuration editor it ways revert phase 2 to MS-CHAPv2, so I guess that's the only one B&N implemented, which also explains why it works in your case.
RasputinAXP said:
Haven't had any issues with my Nook Color and 802.1x/PEAP/TKIP/RADIUS/MS-CHAPv2.
Click to expand...
Click to collapse
Crap, you're right.. But not quite. Phase2 doesn't seem to save right at all.. If you set it to None, you can't set it back to any of them...
Could try editing the wpa_supplicant.conf file
Tried that but instructions on nookdevs are not very clear. Can you point me to a more thorough documentation?
khaytsus said:
Crap, you're right.. But not quite. Phase2 doesn't seem to save right at all.. If you set it to None, you can't set it back to any of them...
Could try editing the wpa_supplicant.conf file
Click to expand...
Click to collapse
jianglai said:
Tried that but instructions on nookdevs are not very clear. Can you point me to a more thorough documentation?
Click to expand...
Click to collapse
Well, probably the easiest way is this, since the tool I mentioned doesn't work.. Sucks, because it does work on my Nexus One. But if the protocols aren't supported this obviously won't magically make it work, but I doubt that's really an issue.
First off, turn off wifi if you can.. If you're using wifi adb, then turn off wifi and back on when you complete this..
Code:
adb pull /data/misc/wifi/wpa_supplicant.conf
(edit wpa_supplicant.conf)
adb push wpa_supplicant.conf /data/misc/wifi/
However... You'll PROBABLY have to fix its permissions, as I suspect they'll be wrong, and if so, wifi won't work at all until you do. So here's how you'd fix that:
Code:
adb shell
su
cd /data/misc/wifi
chown system.wifi wpa_supplicant.conf
chmod 660 wpa_supplicant.conf
I suggest toggling wifi on/off again... If you have any issues, double check your file ownership and permissions.
BTW, if you're really adventurous, you could do it directly in vi Unless you know how to use vi, use the above...
Code:
adb shell
su
cd /data/misc/wifi
vi wpa_supplicant.conf
Great! So what I did is to connect to our network through setting-wireless. After entering username and password it just says remembered but never tried to connect. And in wifi advanced configuration editor even though I could choose TTLS and PAP, the PAP part always snaps back to default when I leave the editor, which makes me think it might be a permission problem. So i pulled the .conf file, edited it and pushed it back then changed ownership and permission as you suggested, everything works perfectly since then!!! Thank you so much!
BTW, in adb shell it seems I do not have vi... All I installed is the basic SDK as suggested in nookdevs, is there anymore packages I should install to have more tools like vi?
khaytsus said:
Well, probably the easiest way is this, since the tool I mentioned doesn't work.. Sucks, because it does work on my Nexus One. But if the protocols aren't supported this obviously won't magically make it work, but I doubt that's really an issue.
First off, turn off wifi if you can.. If you're using wifi adb, then turn off wifi and back on when you complete this..
Code:
adb pull /data/misc/wifi/wpa_supplicant.conf
(edit wpa_supplicant.conf)
adb push wpa_supplicant.conf /data/misc/wifi/
However... You'll PROBABLY have to fix its permissions, as I suspect they'll be wrong, and if so, wifi won't work at all until you do. So here's how you'd fix that:
Code:
adb shell
su
cd /data/misc/wifi
chown system.wifi wpa_supplicant.conf
chmod 660 wpa_supplicant.conf
I suggest toggling wifi on/off again... If you have any issues, double check your file ownership and permissions.
BTW, if you're really adventurous, you could do it directly in vi Unless you know how to use vi, use the above...
Code:
adb shell
su
cd /data/misc/wifi
vi wpa_supplicant.conf
Click to expand...
Click to collapse
jianglai said:
Great! So what I did is to connect to our network through setting-wireless. After entering username and password it just says remembered but never tried to connect. And in wifi advanced configuration editor even though I could choose TTLS and PAP, the PAP part always snaps back to default when I leave the editor, which makes me think it might be a permission problem. So i pulled the .conf file, edited it and pushed it back then changed ownership and permission as you suggested, everything works perfectly since then!!! Thank you so much!
BTW, in adb shell it seems I do not have vi... All I installed is the basic SDK as suggested in nookdevs, is there anymore packages I should install to have more tools like vi?
Click to expand...
Click to collapse
Woot, it worked! I mean.. You're welcome!
Aha, vi must have come from the busybox I installed maybe.... Perhaps the one from Titanium?
Thanks a lot for these directions, as soon as I got adb working it worked perfectly! I first tried to do this using on-device apps since I was having trouble installing ADB, and that didn't work. This just proved that it is absolutely necessary to use adb to do this. Regardless, it works, i'm happy!
Another Workable Idea...
So my work has 802.1x EAP PEAP authentication for the wifi. I tried the advanced wifi editor, but that didn't work. Tried editing the wpa file, that didnt work. When I connected I was always being rerouted to a screen to download a certificate for authentication.
So I used the HC SD bootable rom and was able to manipulate the wifi settings like you can on your android phone, and connect to the wifi. When I pulled out the SD and rebooted into Autonooter 3.0 the authentication stuck and now the 802.1x wifi network is rocking on.
Just thought you all might like an update.
bnole said:
So my work has 802.1x EAP PEAP authentication for the wifi. I tried the advanced wifi editor, but that didn't work. Tried editing the wpa file, that didnt work. When I connected I was always being rerouted to a screen to download a certificate for authentication.
So I used the HC SD bootable rom and was able to manipulate the wifi settings like you can on your android phone, and connect to the wifi. When I pulled out the SD and rebooted into Autonooter 3.0 the authentication stuck and now the 802.1x wifi network is rocking on.
Just thought you all might like an update.
Click to expand...
Click to collapse
Considering you made wifi changes in HC on your SD card then booted your stock, nothing "stuck". Each time you connect your wifi will re-authenticate, in fact it'll re-authenticate on some systems multiple times per hour.
So I have been looking for a way to get on my university's wireless network. I've searched the internet and saw a few people on various forums who were at the same school (University of Illinois at Chicago) looking to do the same thing, but with no luck. There was a lot of information out there but none that really worked, so I spent a few hours today messing with the nook and was able to do it. Here is what I did.
Through Root explorer I accessed... /data/misc/wifi/ wpa_supplicant.conf and holding my finger over the file, I chose "open in text editor"
I added the following information.
network={
ssid="UIC-WiFi"
key_mgmt=WPA-EAP IEEE8021x
eap=TTLS
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
phase2= "auth=PAP"
priority=14
}
I did not need a Thwate certificate or anything like that. Worked like a charm and now I can access the university's wifi from the nook. I know this is kind of a very specific post , my apologies, but I don't know if it might help someone else down the road as a starting point to get onto their network if the general tricks and tips don't work.
What was the isssue first? You couldn't see the login page? I know school and coffee shop allow you to connect to their wifi but you have to go to a login page first and accept the cert before accessing the network. Just curious because my wife today told me that she had issue accessing the school wifi on the unroot nook. The login page didn't come up. I am going to try it out with mine (currently running cm7 nightly build).
Sent from my PC36100 using XDA App
Perhaps you should take up this issue with your school's IT Department. Just mention that you are trying to connect an android device to their secure wireless.
Ah, I just read that you figured out. Well, still pass your method to the IT Department so that they can share it with other students and perhaps create some documentation.
branjosef75 said:
So I have been looking for a way to get on my university's wireless network. I've searched the internet and saw a few people on various forums who were at the same school (University of Illinois at Chicago) looking to do the same thing, but with no luck. There was a lot of information out there but none that really worked, so I spent a few hours today messing with the nook and was able to do it. Here is what I did.
Through Root explorer I accessed... /data/misc/wifi/ wpa_supplicant.conf and holding my finger over the file, I chose "open in text editor"
I added the following information.
network={
ssid="UIC-WiFi"
key_mgmt=WPA-EAP IEEE8021x
eap=TTLS
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
phase2= "auth=PAP"
priority=14
}
I did not need a Thwate certificate or anything like that. Worked like a charm and now I can access the university's wifi from the nook. I know this is kind of a very specific post , my apologies, but I don't know if it might help someone else down the road as a starting point to get onto their network if the general tricks and tips don't work.
Click to expand...
Click to collapse
if your school has a guests network you can connect into that and just login to their webportal using your id login
my school does this but im not sure if all schools do this
branjosef75 said:
So I have been looking for a way to get on my university's wireless network. I've searched the internet and saw a few people on various forums who were at the same school (University of Illinois at Chicago) looking to do the same thing, but with no luck. There was a lot of information out there but none that really worked, so I spent a few hours today messing with the nook and was able to do it. Here is what I did.
Through Root explorer I accessed... /data/misc/wifi/ wpa_supplicant.conf and holding my finger over the file, I chose "open in text editor"
I added the following information.
network={
ssid="UIC-WiFi"
key_mgmt=WPA-EAP IEEE8021x
eap=TTLS
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
phase2= "auth=PAP"
priority=14
}
I did not need a Thwate certificate or anything like that. Worked like a charm and now I can access the university's wifi from the nook. I know this is kind of a very specific post , my apologies, but I don't know if it might help someone else down the road as a starting point to get onto their network if the general tricks and tips don't work.
Click to expand...
Click to collapse
Thanks for your post. I do have a similar problem (i.e., not having the log in screen after connecting to the "open" WiFi on campus) and will try your method later today. Will be back with the results
madtopcoder said:
What was the isssue first? You couldn't see the login page? I know school and coffee shop allow you to connect to their wifi but you have to go to a login page first and accept the cert before accessing the network. Just curious because my wife today told me that she had issue accessing the school wifi on the unroot nook. The login page didn't come up. I am going to try it out with mine (currently running cm7 nightly build).
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My issue was that I couldn't simply log on to the campus wifi network with the nook color (rooted) and the IT department said I needed to wait until Barnes and Noble issued an update to the software so I could change the required settings needed for their network. I tried the guest wi-fi network but that didn't work either, so I thought I would just try to figure it out myself. Which I did and I thought I would pass it along. I'm going to let the IT department know what I did in case anyone else comes to them looking to put their nook on the network. One caveat though is the nook color has to be rooted. I don't think you access the necessary file unless it's rooted. : )
branjosef75 said:
My issue was that I couldn't simply log on to the campus wifi network with the nook color (rooted) and the IT department said I needed to wait until Barnes and Noble issued an update to the software so I could change the required settings needed for their network. I tried the guest wi-fi network but that didn't work either, so I thought I would just try to figure it out myself. Which I did and I thought I would pass it along. I'm going to let the IT department know what I did in case anyone else comes to them looking to put their nook on the network. One caveat though is the nook color has to be rooted. I don't think you access the necessary file unless it's rooted. : )
Click to expand...
Click to collapse
Yeah, I'm at UIC as well and had similar problems connecting to UIC-Wifi on my Nexus One while it was still running 2.1... the ACCC (Campus IT) gave me the run-around on all this stuff for a while... let me tell you...
It has something to do with versions earlier than Android 2.2 only partially supporting 802.1x Authentication or something like that... I ended up doing something similar to what you just described to the wpa_supplicant configuration file in order to get it to work... after I described this to the Campus IT department, they "informed" me that they would be unable to support this method because it required the phone to be "jailbroken" (LOL! ) anyway... long story short... works okay now...
Just ordered myself a nook color yesterday.... good to know this is possible!
I'm excited to get started screwing around with it...
redstar3894 said:
Yeah, I'm at UIC as well and had similar problems connecting to UIC-Wifi on my Nexus One while it was still running 2.1... the ACCC (Campus IT) gave me the run-around on all this stuff for a while... let me tell you...
It has something to do with versions earlier than Android 2.2 only partially supporting 802.1x Authentication or something like that... I ended up doing something similar to what you just described to the wpa_supplicant configuration file in order to get it to work... after I described this to the Campus IT department, they "informed" me that they would be unable to support this method because it required the phone to be "jailbroken" (LOL! ) anyway... long story short... works okay now...
Just ordered myself a nook color yesterday.... good to know this is possible!
I'm excited to get started screwing around with it...
Click to expand...
Click to collapse
i had the same exact situation you did but with my evo.
but you dont need to do this anymore. you can connect just fine thru the wifi settings.
http://www.uic.edu/depts/accc/android/index.html
edit: i take that back. doesnt work in 2.1. works in 2.2 just fine though
Does anyone have any more info on a fix for this? My gf's NC is running CM7 Nightly14, and she can't connect to USC's wireless network- apparently the login screen won't come up, so she can't sign in.
She was able to while she was running the stock software, so i'm wondering what has changed.
xeren said:
Does anyone have any more info on a fix for this? My gf's NC is running CM7 Nightly14, and she can't connect to USC's wireless network- apparently the login screen won't come up, so she can't sign in.
She was able to while she was running the stock software, so i'm wondering what has changed.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=988802
Check out my thread.
I couldn't connect to my school's network (SDSU) so I pushed those files in [Problem 1] and it worked after that!
Try it!
Thanks a lot. It is great. Very easy and helpful. Thanks again. You should post it on ACCC.
This should work with other wireless connections, if you know the SSID.
As for down here in champaign, try this (I'm not getting my nook color until sometime over spring break, so this is a guess):
network={
ssid="IllinoisNet"
key_mgmt=WPA2-EAP IEEE8021x
eap=PEAP
identity= "INSERT YOUR USER NAME (UID)"
password="INSERT YOUR ACTIVE DIRECTORY PASSWORD"
phase2= "auth=WPA2"
priority=14
}
That's the best to my knowledge. CITES doesn't like to disclose much about anything online, so I pulled most of this from the windows xp setup configuration.
Good work!!!
Sent from James' OCed Nook Color
Interesting. My university uses a WPA(2?), PEAP system that requires a THAWTE certificate, but the nook color -- both on stock rooted, and CM7 connected fine with username and password. Your network looks similar to ours, but its a good tip you've posted, adding it manually may help in the case of other similar networks as well.
Quick update: I updated my gf's NC from CM7 Nightly 19 to 31, and now it's connecting to her university's wireless- not sure what the devs changed, but it's working great now!
If you still haven't been able to get it working with the above hacks, try updating to the latest CM7, it may work for your school as well.
Thank you.
I tried this on my rooted nook color (stock 1.2) It didn't work.
branjosef75 said:
So I have been looking for a way to get on my university's wireless network. I've searched the internet and saw a few people on various forums who were at the same school (University of Illinois at Chicago) looking to do the same thing, but with no luck. There was a lot of information out there but none that really worked, so I spent a few hours today messing with the nook and was able to do it. Here is what I did.
Through Root explorer I accessed... /data/misc/wifi/ wpa_supplicant.conf and holding my finger over the file, I chose "open in text editor"
I added the following information.
network={
ssid="UIC-WiFi"
key_mgmt=WPA-EAP IEEE8021x
eap=TTLS
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
phase2= "auth=PAP"
priority=14
}
I did not need a Thwate certificate or anything like that. Worked like a charm and now I can access the university's wifi from the nook. I know this is kind of a very specific post , my apologies, but I don't know if it might help someone else down the road as a starting point to get onto their network if the general tricks and tips don't work.
Click to expand...
Click to collapse
I just tried it on nook color(stock 1.3 rooted). It did work. I first tried to log in our wifi before changing that file. Then I opened the file, and it becomes
network={
ssid="UIC-WiFi"
key_mgmt=WPA-EAP IEEE8021x
eap=PAP
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
}
I changed it like him and also added another line(scan_ssid=1):
network={
ssid="UIC-WiFi"
scan_ssid=1
key_mgmt=WPA-EAP IEEE8021x
eap=TTLS
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
phase2= "auth=PAP"
priority=14
}
I noticed that I was able to connect once (the first time), and then could not reconnect afterwards. My Kubuntu netbook and iPad did not have this problem. After opening /data/misc/wifi/wpa_supplicant.conf as recommended, I immediately saw the problem: the password isn't being saved for my WPA2-Enterprise network. All the other networks had a password field, if applicable. Go figure...
Thanks for the hint! It appears that this may be a more general problem than you thought (I did not test this yet, but will do so tomorrow.)
been searching all over the internet and have tried a few methods but nothing seems to stick on the tab. im doing this because my mac address is something funky, 12:34:56... and i cant connect to my schools wifi. my IT department doesnt service "gadgets" so im on my own. ive tried the instructions here:
http://blog.thecodecracker.com/hacks/spoof-mac-address-in-android/
but they dont seem to stick. when i connect back to my wifi network (at home) it just goes back to the corrupt one. anyone have any experience with this?
i havent been able to connect in about 3 months so as you might imagine, im really getting frustrated with it. any help would be great.
Ayman
been searching all over the internet and have tried a few methods but nothing seems to stick on the tab. im doing this because my mac address is something funky, 12:34:56... and i cant connect to my schools wifi. my IT department doesnt service "gadgets" so im on my own. ive tried the instructions here:
http://blog.thecodecracker.com/hacks/spoof-mac-address-in-android/
but they dont seem to stick. when i connect back to my wifi network (at home) it just goes back to the corrupt one. anyone have any experience with this?
i havent been able to connect in about 3 months so as you might imagine, im really getting frustrated with it. any help would be great.
Ayman
Edit*
Temporary Fix:
1) Go to wireless & network settings
2) Disconnect and forget ALL previous SSID's that you connected to before
3) download a terminal emulator from the market
4) type the following, make sure you hit enter after every line
Code:
su
busybox ip link set eth0 address XX:XX:XX:XX:XX
Where XX:XX:XX:XX:XX is, make you have to put the MAC address you want there.
to confirm if it worked type:
Code:
busybox ip link show
it should show the new MAC address. Go connect to your network as normal.
NOTE:
If you go to the status option in the settings, you will see that the MAC Address DID NOT CHANGE. This is normal. It wont show the new MAC Address; at least it didnt for me.
One thing to keep in mind, sometimes you cant just put in an hexadecimal combination and expect it to work. It didnt work for me. So what I did is I connected to the school's network from my vibrant making sure I could surf the internet. then i disconnected and copied its MAC address to my tab. when i tried putting in my own custom MAC address, it didnt work. I could connect but packets wouldnt be sent.
Unfortunately when I reboot, my settings are not saved and I have to repeat the procedure. Simplest fix is to just download gscript lite from the market and put in the command I wrote above and whenever i restart my tab run the script quickly. If someone knows of a permanent fix, please let me know so I can update this.
feels good to finally be able to connect after 3 months.
I wrote a quick app that will do this - but i hardcoded the script for something else. I will modify it tomorrow so you can customize the script it runs and put it up here tomorrow or sunday if i get the time.
I would sincerely appreciate that!
Sent from my GT-P1000 using Tapatalk
ayman07 said:
One thing to keep in mind, sometimes you cant just put in an alphanumeric combination and expect it to work.
Click to expand...
Click to collapse
"alphanumeric"?
More like "hexadecimal"
Valid charachters are 0123456789abcdef and nothing more, if you used something else that would explain why it didn't work.
Sent from my GT-P1000 using Tapatalk
AlexTheStampede said:
"alphanumeric"?
More like "hexadecimal"
Valid charachters are 0123456789abcdef and nothing more, if you used something else that would explain why it didn't work.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Fixed
Sent from my GT-P1000 using Tapatalk
Ok here is the boot script loader.
I didn't spend any time on the interface or layout for you:
Obviously requires root to run
you don't need to start script with "su"-everything runs as su
enter the script in the edit box, click test to test it, click save to save it. It will run whatever has last been saved every boot.
Do NOT move to SD card or it will not pick up the BOOT_COMPLETED intent
i haven't tested if it runs before the SD card is fully mounted: so don't get carried away with your scripts. I suppose I could add options to run only after SD card is mounted but... i probably don't have time
Since this runs as root, do stupid things in your script things at your own risk. I'm not responsible in anyway.
the output from testing or from the boot log is:
stdOut
..some stdOut text
stdErr
..some stdErr text
where stdOut text is the results of your commands (you can see testing with a simple script containing just "ls" without the quotes)
and stdErr is any errors that occurred while running the script (you can see testing with a simple script containing "aasdf" without the quotes
click the "Thanks" button if you use this and it works
i really appreciate this. unfortunately i wont be able to try it out till monday when im at school. ill update it then.
thanks a lot of the script loader. it seems to do its job. but it seems my situation is a bit more complex than i thought. see i can only change the MAC address if i delete all the previously connected SSID. if i remove the dchp.list will that remove/forget all the previous SSIDs? i would have to run a cmd to forget all the SSIDs prior to running the MAC address change cmd.
I typed busybox ip link set eth0 address XX:XX:XX:XX:XX
i am receiving " bad address"
Pls help me
Ok I'm a moron.
I accidentaly told my nook to forget a wireless network and now I can't get it back. I've looked all through settings and don't see anything that would allow me to reset this. I've tried scanning as well.
I'm running gingerbread the CM7 mod.
Sorry I tried searching but when you look for something like 'resetting' you get a lot of threads about resetting back to stock which is not what I want to do.
Is there a way to I don't know purge the wireless settings so it will search for networks that it has been told to forget?
twopossums said:
Ok I'm a moron.
I accidentaly told my nook to forget a wireless network and now I can't get it back. I've looked all through settings and don't see anything that would allow me to reset this. I've tried scanning as well.
I'm running gingerbread the CM7 mod.
Sorry I tried searching but when you look for something like 'resetting' you get a lot of threads about resetting back to stock which is not what I want to do.
Is there a way to I don't know purge the wireless settings so it will search for networks that it has been told to forget?
Click to expand...
Click to collapse
When you tell it to forget it doesn't blacklist a Network, it just Removes it from your preferred Networks and forgets the Password. It should reapear on the list of Available networks if in Range.
If it won't show up even when standing next to it do this.
-Download Wifi Analyzer from Market.
-Open App Punch Menu and Tap View. Select AP List.
-Look for the Network and Tap it. It might prompt for a Plugin from Market. Just Download and continue.
-When Window pops up put in Password and hit Connect. TaDa it should now work.
____________________________________________________
Sent from NookColor CM7 using Tapatalk
Well I don't know if its a glitch in system or the mod itself but when I got home my nook wouldn't connect to my home network either. It kept saying I was out of range even when I was sitting in the room with the router.
So I ended up just reinstalling gingerbread. My instal was only a week old do no real biggie for me just annoying.
Ill just make sure not to ever forget a network again as it apparently Jones up my system
Thank you for the advice though.
twopossums said:
Well I don't know if its a glitch in system or the mod itself but when I got home my nook wouldn't connect to my home network either. It kept saying I was out of range even when I was sitting in the room with the router.
So I ended up just reinstalling gingerbread. My instal was only a week old do no real biggie for me just annoying.
Ill just make sure not to ever forget a network again as it apparently Jones up my system
Thank you for the advice though.
Click to expand...
Click to collapse
Hey I have the same problem going on right now. My system wont connect to anything. The wifi status just keeps saying connecting and then will eventually turn off. I think I am going to use this as an excuse to try out Deeper-Blue's Honeycomb preview.
Has anyone been able to get any version (2.0.7 or 3.x beta) of Google's WiFi Tether app working on their rooted Droid Bionic? Link to app
It didn't seem to work for this guy at the end of the video: Link
For me tethering is critical for work and I don't want to activate my Droid Bionic (which is coming tomorrow) until it can be confirmed working. Will keep using Thunderbolt for now... I can also imagine this is a huge issue for many other users.
However, I am aware that Motorola devices need some kind of device profile in the "Change Device-Profile" option in the settings of that app, has anyone played around with that, maybe choosing the Droid X or other Droid?
Any feedback greatly appreciated...
I hope you find a solution soon, I also have the same problem
Don't bother until a custom ROM comes out that can "hide your ass".
Since it is for work, paying for the monthly tether should be a business expense.
I tried some of the work-arounds on the net... barnacle did not work for me... choosing the droid x profile in device setup at least showed my wifi hot spot, but I could not obtain an IP... I had also noticed errors about dhcp in the log.
kierandill said:
Since it is for work, paying for the monthly tether should be a business expense.
Click to expand...
Click to collapse
exactly, in the mean time your going to be stuck using PDAnet and a USB cable.
Got it, rooted it, figured it out. Use version 2.0.7. Change the LAN option to 10.10.1.x
Also it only works in ad-hoc mode but at least its a start. I'm sure updates will fix it.
open1your1eyes0 said:
Got it, rooted it, figured it out. Use version 2.0.7. Change the LAN option to 10.10.1.x
Also it only works in ad-hoc mode but at least its a start. I'm sure updates will fix it.
Click to expand...
Click to collapse
Woot! I don't own one but I am glad you got it going perhaps a screenie of some data transfer?
Also try this with the 3. beta if you don't mind
Brenardo said:
Woot! I don't own one but I am glad you got it going perhaps a screenie of some data transfer?
Also try this with the 3. beta if you don't mind
Click to expand...
Click to collapse
Can't get 3 beta to work at all but it doesn't offer anything other than ad-hoc mode also. Also doesn't show data going through on the app. But hey at least it works.
Can anyone confirm the 2.0.7 wireless tether working?
not working
2.07 not working for me even using the 10.1 network. clients fail to obtain an IP address.
Same problem here - wifi tethering not working...
The newest 3.x didn't work for me. Has anyone tried manually setting the client's IP/Gateway/DNS? I don't remember what the dhcp issued on my incredible, otherwise I'd go grab my laptop and mess around with different static settings.
RawNis said:
2.07 not working for me even using the 10.1 network. clients fail to obtain an IP address.
Click to expand...
Click to collapse
It takes a long time I noticed. Wait for the little blue notification icon to appear that shows the device is connected. Can take as long as 3 minutes sometimes but it works for me I assure you. The key thing is the 10.10.1.x network which is still unblocked because VPN's can use that network, anything other than that won't work.
I can't get wifi tehthering to work but just using the phones built in usb tehering option works and does not send me to a page to subscribe for tethering. Don't know why this works but if I try the built in wireless tethering it says I have to sign up. EDIT Was working on launch day but tried again today and won't work so I guess the system wasn't updated the first day I tried it.
Hi,
I found way to enable Hotspot without Verizon Provisioning. I used SQLLite Editor to modify settings.db for "Settings Storage" application ( com.motorola.android.providers.settings ). Set entitlement_check to 0 and reboot the phone.
Dmitry
ddv2005 said:
Hi,
I found way to enable Hotspot without Verizon Provisioning. I used SQLLite Editor to modify settings.db for "Settings Storage" application ( com.motorola.android.providers.settings ). Set entitlement_check to 0 and reboot the phone.
Dmitry
Click to expand...
Click to collapse
I just tried this. It appears to be working. I was able to connect and browse from my laptop. Now the question is, does Verizon still know I'm tethering even though I'm not paying to tether?
I second. Works for me a well, with no warning or pop up. Cudos to you my good man
Sent from my DROID BIONIC using xda premium
Just did it and all seems fine so far.
btw, WOW. Ive never poked around the databases like that. Everything from the hdmi overscan to wifi info is in there. That is So cool.
Works for me too! However, only works properly with WPA security. If Hotspot is set to "open", you can connect but get no internet...