Database Users

GPS Tether via USB with simultaneously tethering Internet via Ad-hoc WiFi

I have searched several times, usually while on the road, so only now and then, but all total I must have searched for weeks worth of days trying to find an answer.
I found one.
What I wanted to do was take my T-Mobile G1's GPS receiver AND its Internet connection and forward both of these on to my laptop running Windows XP. I really would prefer a Linux solution, and I found one, but while in Linux my needs change slightly enough that the solution I found wasn't worth trying at that time. So I used Windows. As will most other people reading this, so.... >shrug<
I know it's not a very popular topic (not that it's non-popular; it's just that most people don't care enough to worry about it). However, that said, I know some poor pleb is out there trying to do exactly the same thing I found out how to do with exactly the same hardware and software, so I wanted to post how I did it.
MODS: I've not found anything detailing specifically this method on XDA and I did search before, but Google and I have been having communication problems in our relationship so I haven't been as proficient with results as usual. Therefore, if this has already been posted by someone else somewhere else, please forgive me, and feel free to pop a link in here, or merge, or whatever is appropriate. -- Thanks.
--------------------------------------------------
Required:
Rooted phone. which will require...
A computer with a USB port AND a WiFi device of some kind.
Install on the computer:
* the Android SDK
* com0com
* com2tcp - Which MIGHT be included in com0com, I don't remember.
* Something to use it with (Google Earth, for instance)
And on the phone, install the following:
* Android-Wifi-Tether (WiFi Tether for Root Users)
* ShareGPS <-- Just a link to a page with a QR code. The dev's page says to get it from Android Market.
That's a lot of stuff, but if you NEED this, it's worth it.
First and foremost, get ADB working. Beyond the scope of this post, go to Google for more info on doing this. Make sure, though, that your phone's debugging is enabled (Menu > Settings > Applications > Development).
Once ADB works, install the software above in the appropriate places. For com2tcp, put its executable file somewhere in the system path. I used c:\windows\system32 for it (and for ADB, come to think of it) but many people might balk at this, as though it's some holy ground on which lowly mortal files shalt not tread. Whatever. Find a hole it'll fit in and make sure it's in your system path.
After installing ALL of the above software, do this, in this order:
1) Connect the phone to the laptop via USB.
ON THE LAPTOP
2) Open com0com from your start menu.
3) Either remember these names for the com ports (at the top of the com0com window) OR name them more memorably. I'll use COM1 and COM2, but ONLY BECAUSE MY LAPTOP DOESN'T ALREADY HAVE THESE TWO PORTS. You can call them PORT1 and PORT2 if you want, or CHUNKY1 and CHEWY234 but I used COM1 and COM2. So, the rest of these instructions will be the way I did it -- you'll have to adjust them accordingly, and if you're not smart enough to figure out how to do so or what I mean by that, then I can't help you. After naming them, hit APPLY.
3b) On your first time running com0com, it'll want you to install new devices, twice. LET IT. Just let it do the automatic thing and you'll be fine.
4) Open the command prompt (Windowkey-R, "cmd", ENTER) (or Start, Programs, Accessories, Command Prompt).
5) In the command prompt, type in:
Code:
adb forward tcp:50000 tcp:50000
and hit enter. This creates the forwarding of the phone's internal communications to the USB (I think). Assuming there are no errors (if there are, you either did something wrong or you did something wrong (like getting ADB working)) then type in the following
Code:
com2tcp --telnet \\.\COM1 127.0.0.1 50000
and hit enter. This uses the above-created forward of comms and attaches it to the virtual COM port made with com0com in step 3. This time, assuming there are no errors, you should see some diagnostic output.
ON THE PHONE
6) Open ShareGPS.
6b) In ShareGPS, Menu > Settings, select Use USB and deselect Use Bluetooth. The Format is irrelevant to what we're doing, and Create NMEA is not needed for the HTC Dream hardware as the output already is in NMEA format AFAICT. Back out of the settings screen.
7) Tether your Internet connection. OPTIONAL: If your laptop already has Internet access somehow else, you can ignore this step.
8) Open and connect your mapping application on the laptop. YMMV, depends on your software, I can't help you here. In Google Earth, go to Tools, GPS, and click the REALTIME tab. Select NMEA, not Garmin. Select other options as appropriate (like auto follow). Hit start. You should, if it works, see diagnostic output in your command prompt window as well as a connection message on the phone in ShareGPS. In Google Earth, YMMV, but I at first saw no icon, and second I saw a little blue dot. Problem is, in GE, it quickly disconnects and reconnects. You might have better luck with GooPs Free.
If you use GooPs Free, it might not pop up in front. Look down in your system tray, and you'll find the GooPs icon. Right-click it, and select "Open GooPs". you'll be presented a small window. Click options. For the COM port, use one of the two that you made with com0com (if one doesn't work, try the other). Default rate worked for me, Hardware flow control. Autoconnect, Autoscan are set for me. The rest of the options should be pretty self-explanatory. If not, I can't help you (it's midnight here and I'm oh so tired right now) (but I REALLY wanted to get this posted to help anyone else). IF everything works, you'll have an obnoxiously large 3D arrowhead right where you are in Google Earth. If not, you'll have to troubleshoot the errors.
-----------------------------------------
Feel free to ask questions in reply, as I'll of course subscribe to this thread, but understand that I can't answer all questions as I barely understand enough to get this working myself.
ALSO, KNOW THIS: YOUR PHONE WILL BECOME LESS STABLE. I noticed a significant increase of unprompted reboots of my phone after futzing with these programs. Sometimes it lasted a few minutes, but usually it goes for hours. Further, they don't seem to be an issue until I start GPS tethering, so maybe it's not so bad.
You CANNOT use GPS Tether and USB Internet Tether at the same time. If you need to tether your phone's Internet, install WiFi Tether for Root Users (link above) and set it up accordingly. You should be able to launch WiFi tether at any time, but I would recommend doing it before forwarding the ADB GPS ports.
I do sincerely hope this helps someone, and if not, hopefully it will save time and not waste it.
Best Regards to All
Edits below:
WARNING: IF YOU PERFORM THIS HACK, AND THAT'S WHAT IT IS, YOU **WILL** SEE SUCH A HUGE DRAIN ON YOUR G1'S WIMPY LITTLE BATTERY THAT EVEN WITH IT PLUGGED IN AND "CHARGING" YOU WILL STILL HAVE A DRAIN UPWARD OF 35 PERCENT PER HOUR. ALSO, YOUR PHONE WILL GET HOT. NOT WARM. HOT. THINK ABOUT IT: YOU'RE CHARGING, YOU'RE RUNNING WIFI, AND YOU'RE RUNNING GPS ALL AT THE SAME TIME YOUR CUSTOM HACK ROM IS RUNNING YOUR CPU AT ITS MAXIMUM SPEED.
YOU HAVE BEEN WARNED.

How to in Linux
Hai
I am using an Ubuntu desktop...and might am interested in knowing hw to do it in Linux?
Regards
kumar

I wish I could help with that. While I use Linux too (Ubuntu, I think, on my laptop and Sabayon on my desktop), and used to use it as my primary OS, I do not know enough about it to do this. For starters, I've never gotten a decent working load of Google Earth on my laptop in Linux. When I was researching this, I found that 99% of what I found was based in Windows, and I was short on time so trying things in Linux was an unaffordable luxury. Everything takes me forever in Linux because I have to learn it first, and then start screwing with it.
For starters, though, you have to get ADB working, and then port forwarding the GPS to the phone's USB (done through ADB). From that point, I think Linux might *just* be able to handle getting the data visible to apps like Google Earth natively. I would start my search with "usb-to-telnet forwarding". Or "accessing USB with telnet", since really once you do the ADB forward, the phone is sending data direct to the USB port.
Edit: Of course, you'll also still need ShareGPS on the phone... I think...
I really don't know enough though to be able to provide the help I'm thinking you need/want, but hopefully this can at least get you started on the right track. If you figure it out, please post back to this thread...
Cheers,
CJ Chitwood

Linux Solutions???
I am going to dive into getting this working with Ubuntu on my EeePC. Right off the bat I'm thinking why not send the GPS to the netbook over bluetooth and use use the USB tether for the internet access? I'll see what my untrained brain can come up with.
Thanks for the post on this issue, I've been looking into this for 2 years.

Right, that should work if your Asus can receive GPS over bluetooth, and the USB tether for internet would save you a little on battery as you could kill the WiFi on both devices. My only problem was that my laptop did not have a bluetooth transceiver on it, so I was stuck doing it the bobo way. Story of my life, really
Glad it helped!

Thank you for this guide, I used some other applications though.
For my HD2 (running on Android 2.3.5) I used BlueNMEA, you can get it from the Android Market
I connected my phone with my laptop (running Win. 7), installed SDK and used ADB).
With ADB I used the commands from the BlueNMEA guide:
Code:
Using BlueNMEA over USB
-----------------------
Needs the Android SDK.
Connect your phone to a computer with the USB data cable. On the
computer, type "adb forward tcp:4352 tcp:4352". Now you can get NMEA
data by connecting to TCP 4352 on your computer.
For virtual ports I used HW VSP, quite simple to setup, I used COM9, typed 127.0.0.1 as address and the port 4352. It creates a service so this is a 1 time job.
At first I used GPSGate, but this didn't work with BlueNMEA.
GPSGate works with ShareGPS, same principle I guess.
For testing my GPS on my laptop I use OpenCPN, it shows my location perfectly.
The phone is also very stable, no problems at all.
The internet part doesn't concern me, because I have internet at my laptop .
I've been searching for a method to use my Android as a GPS mouse and I found this, thought I'd share my findings with you.
The fastest way to do this is via Bluetooth I think, but my laptop has no Bluetooth, ordered one @ Ebay for 5$, hope this saves me all the hassle.
The only thing I'm wondering, since I'm not familiar with Android SDK, is the ADB forwarding still alive after a reboot?
BTW, for people still searching for a Linux guide: http://sharedroid.jillybunch.com/user_linux.html

Thank you very much for that! Nicely informative.
AFAIK, the adb forward is gone after a phone reboot. However, I've never actually tested it. I've also not looked for a way to undo it...

cj chitwood said:
Thank you very much for that! Nicely informative.
AFAIK, the adb forward is gone after a phone reboot. However, I've never actually tested it. I've also not looked for a way to undo it...
Click to expand...
Click to collapse
I've fooled around a bit with the phone, every time I disconnect/connect I have to forward the port using ADB, ow well, I'll use Bluetooth as soon as I have my dongle.
The best part is this works, so I'm sure it will also work with Bluetooth.
I know for Windows Mobile it is possible to tether GPS through activesync,
which I used for my HD2 when it was stock Windows Mobile.
I use this when I'm at sea, I'm a sailor so it's nice to track my course.

3G USB Solution; Verizon Dumbphones, Possible Other Devices

I don't post much (obviously, and keeping me from putting this in Dev forum or posting external links :| ) but I do work a lot on the sides and figured out how to get a Verizon non-smartphone to act as a 3g dongle for the Acer A500. This is a copy of my tutorial originally posted on TegraOwners.
First off my setup;
Acer Iconia A500; Running Thor v14.2 ROM (Possible to work on other ROMs/kernels that support 3g dongles)
Build.prop mod installed from -snipped because of limit, will edit when able-
Phone; LG EnV2 Verizon prepaid.
Solution should work for any tether enabled verizon phone, POSSIBLY Verizon Dongles, and other brands of phones besides LG.
This guide assumes you either have, or know how to flash Thor's rom, and other flashable zips. I will not provide ADB instructions, but if someone would like to send me instructables how; I will add them into this post.
From a 'fresh' or unmodified version of Thor's ROM (I used v14.2, follow the build.prop install instructions in the link above. (Link removed because of limitations on posting)
Then using root explorer (or equivalent root browser) remount /system rewritable and open the build.prop file in a text editor.
Comment out ro.carrier=wifi-only and uncomment the rest of the block. It should match the following when done;
#ro.carrier=wifi-only
picasso.3g=true
rild.libpath=/system/lib/libhuawei-ril.so
rild.libargs=-d /dev/ttyUSB2
ro.pad.features.modem=true
Save the file and check permissions; they should still be rw-r--r-- and reboot the tablet.
This enables the 3g menus, and using the previous build.prop, lets your A500 read as an A500 instead of an EPAD.
Note: You DO NOT need to set an APN, Verizon, being a CDMA network, does not use APNs. The 'login' information is in the phone itself. It just needs the commands to initiate a data connection.
Now is where it got tricky to figure out; If you open a terminal emulator as root (type su at the prompt) and type ppp-start.sh you will get a couple of lines with this error;
pppd: In file /system/etc/ppp/peers/3g: unrecognized option '/dev/ttyUSB2'
or similar.
In the terminal prompt, type dmesg | grep tty it will return several lines, I noticed I had a device on ttyUSB0 not ttyUSB2.
On study, some modems make several ports for control, monitoring, etc. mostly data connections are on ttyUSB2, which is my guess why it was default.
I figured out by editing the ppp config file that ttyUSB0 wouldn't error, but wouldn't start either. I looked back at the grep and noticed something else that matched and I had seen before in my studies; ttyAMC0
So using the same method as editing build.prop, edit /system/etc/ppp/peers/3g it should read as follows;
ttyACM0
921600
crtscts
defaultroute
modem
noauth
noipdefault
persist
updetach
usepeerdns
connect 'chat "" AT OK ATD#777 CONNECT'
Note the ttyUSB2 being changed to ttyACM0, apparently the data serial for the phone, and atd number being changed to #777, Verizon's 3g number. (Speculation that you could increase the 921600 for higher USB bus speed, but I've not tested this).
Save the file and confirm the permissions are; r-xr-xr-x
Open terminal emulator with root permissions and again try ppp-start.sh
This time after it says pppd, after about 5 or so seconds, it should list your IP and other information confirming the connection. You should see TX and RX packet info on the phone screen. If so, congrats you are now connected via 3g with the phone.
To turn off the connection, use the command ppp-stop.sh I suggest making a couple script manager widgets to 'shortcut' these.
Note; If the screen turns off, the phone will disconnect and you will have to unplug the phone, restart the ril daemon, plug the phone back in, and run ppp-start.sh again.
You can install the ril-daemon_restarter.apk to easily restart ril, or in terminal emulator; stop ril-daemon then start ril-daemon
(Had to remove link for limitation, google for now, will add in when I can. suspected credit goes to dmatusek76 on XDA.)
Things that I've tested;
Browser works despite saying 'no connection' at the start.
Market can browse apps, but not download them.
GMail seems to receive, but not send emails.
Netflix works.
Edit: OpenVPN works.
Google Maps/Navigation works (downgrade to stock, latest update FCs)
Best part; The Portable Wireless Hotspot option in Settings > Wireless & Networks > Tethering & Portable Hotspot menu works to create a 3g Wi-Fi hotspot.
All connections through the hotspot are NOT BLOCKED; i.e. using my android to connect to the tablet, I was able to browse apps, download them, send emails, etc.
My theory on the reason the tablet won't; Some apps (like Google Voice and AndroIRC), check for an internet connection BEFORE TRYING, and if it isn't 'available' it just gives you a warning and stops without actually TRYING. Other apps just try to access the internet without checking for a connection first (Like Netflix), and they work.
This theory is backed up by the Browser first checking for a connection (hence the 'no connection available' popup), but then loading as it continues to try anyway after the check.
Using the wireless hotspot, the phone sees it as a full connection, so nothing stops during the 'network check'.
I hope this information might be useful in getting other devices, phones, dongles, etc. working with this masterful tablet.
Please let me know if it works and if you use other equipment.
Credits;
Thor for his awesome rom that supports USB 3g in the first place
pimpmaneaton for the build.prop

Wifi not working

Creating a new topic, because the other one is tagged as solved, but it doesnt solve my problem however.
So my wifi is not working, it's connecting to any wifi hotspot but not sending data thru that, which ends in failing loading any pages on IE, cannot download any apps from market and so on...
Anyway this is what I tried so far:
1. Flashed to stock rogers (also tried different Tango roms)
2. Did hard reset procedure via hardware keys (Format all Yes)
3. Did hard reset procedure via About menu
4. Did hard reset procedure via Samsung Diagnosis code sequence
5. Logged to my wifi network, everything looks fine at this point.
6. Opened IE and entered google.com:
"We're having trouble connecting to this webpage" (sometimes no error message but white page with scrolling bars appearing on touch)
7. Tried to access my wifi router via IP address (192.168.1.1) - the same results like above
8. Tried to ping my Samsung Fous IP (192.168.1.18) from my PC with success
9. Disabled wifi network security on home wifi router, the Focus still not working
Additionaly tried a method that fix issues with wifi after using latest wp7 tools, but it didnt help at all.
When using my providers APN there is no problem with opening pages on IE etc., but it's not Wifi.... Internet is also working if I have USB cable plugged in, but again it's not wifi.
Cannot use warranty, the phone is from the USA and I'm in Europe... without any warranty service.
What else I can do, maybe there are some diagnosis codes that can actually help with real diagnosis on what happened with wifi on my phone?

Hello again (from the other thread). For completeness, add the following:
- current OS version
- did/not use WindowBreak
- when did the problem start (if you can identify an event and OS version/revision) - or you noticed
There might be a test for wireless in the "diagnosis codes"... Good luck!

After you use the diagnosis fix, it might take some time, mine didn't work immediately but after some time, it detected my home network. But it seems you are able to connect but internet does not work, this is certainly issue with router/DNS settings in your phone, because I have faced these problems in iPhone, it might wrongly mapped to unreachable ip, but never faced this issue in Windows Phone, you might try changing the default gateway/dns settings, you should also reset your modem/router, and try basic setup before WPA/WPA2 setup

EnderPsp said:
Hello again (from the other thread). For completeness, add the following:
- current OS version
- did/not use WindowBreak
- when did the problem start (if you can identify an event and OS version/revision) - or you noticed
There might be a test for wireless in the "diagnosis codes"... Good luck!
Click to expand...
Click to collapse
Hi there
Currently using 7.10.8773.98, (MAGLDR 2.0) but tried different versions, even vanilla pre-mango ones, they didnt work well with wifi on my phone either. I checked it at friends home wifi, which is totaly different network and routers.
I never used WindowBreak, never had to because my phone was already unlocked long time ago with ChevronWP7 application.
Noticed the problem about 2 weeks ago, but I didnt use wifi too much, so it could started much earlier. Last installed application was WP7 Tools 0.8 alpha, and all I did back then was using some built-in tweaks (3G?) if there is any, cant remember to be honest but for sure I wasnt editing registry or anything like that, I just play some games from time to time, cant event tell why I installed it, maybe because I noticed there is a new version. I cant tell because I never paid attention to it especially with rare wifi usage at a time.

I have isolated the problem I guess, and it's not the phone's fault. Something wrong with the main access point (Mikrotik) at my place. This is weird because everything is working just not on Samsung Focus. I digged thru many options and couldnt find anything that blocked or stuff like that. Well took it to totaly different place and another wifi network, and guess what - it's connecting to wifi with data flow...
Anyway consider this topic as solved.

[Q] New S5 not automatically connecting to WiFi

Hello everyone,
Last week I upgraded my S4 to a brand new S5 on T-Mobile and currently it's stock and unrooted. It works great, except it won't automatically connect to WiFi. Every time I encounter a known WiFi it'll say Sign in Required. I'll press Connect and it'll then connect and function perfectly.
This smells like a software bug to me, but then I'd expect more posts on this topic (I didn't see any posts on XDA, and posts elsewhere were unhelpful).
What I'd ultimately like to know is if this is a hardware defect and I should get my phone replaced before it's too late, or if this is something that a software update (or rooting and flashing) will fix. Or of course it could be neither...
Thanks!

I have the same probblem and I am dying for a solution. I've spent hours googling and testing different things to no avail.
I am going to try to bring as much detail as I can, hopefully someone can pitch in.
Things I have read might work:
"forgetting" the connection and recreating it
Turning off and turning back on
Turning off, removing the battery
Turning off, removing the battery and the sim and waiting a minute (seems like voodoo to me)
Factory reset
I've tried everything, bar the factory reset which I am reluctant to do, specially when people's answers on forums said it wasn't a solution.
To try and shed more light, I would also add that:
It does this with any network (so it's not channel/router issue)
It does this consistently (and since I got my phone)
It finds networks, but just won't connect
It always connects fine if I pick the network (so it's not a distance/bad reception issue)
My phone is unrooted and stock and I have no weird apps (only popular/regular ones, social media, news, and so on)
My options are set correctly (notifications for open networks is checked and wifi is on)
I really hope someone can help as I rely on wifi a lot, and this is kind of a deal-breaker for me.

So I found a psuedo-fix here: http://forum.xda-developers.com/showthread.php?t=2723486
The key part being:
1. >Wifi >Advanced >Disable (uncheck) Smart network switch.
2. Forget connection, then establish connection again. Works no issues.
Click to expand...
Click to collapse
This has "fixed" it for me, but it also means I no longer have Smart Network Switch which is kinda annoying, albeit less annoying.
A true solution would be lovely.

ForestHunter said:
So I found a psuedo-fix here: http://forum.xda-developers.com/showthread.php?t=2723486...
Click to expand...
Click to collapse
Tried, didn't work for me.
I now have factory reset and let google reinstall all my apps.
Until now, auto-connect works.
The only thing I didn't do this time that I did last time is deactivate a bunch of samsung apps that come pre-installed.

wi-fi won't auto connect to S5
ForestHunter said:
Hello everyone,
Last week I upgraded my S4 to a brand new S5 on T-Mobile and currently it's stock and unrooted. It works great, except it won't automatically connect to WiFi. Every time I encounter a known WiFi it'll say Sign in Required. I'll press Connect and it'll then connect and function perfectly.
This smells like a software bug to me, but then I'd expect more posts on this topic (I didn't see any posts on XDA, and posts elsewhere were unhelpful).
What I'd ultimately like to know is if this is a hardware defect and I should get my phone replaced before it's too late, or if this is something that a software update (or rooting and flashing) will fix. Or of course it could be neither...
Thanks!
Click to expand...
Click to collapse
I have been having the same issue. I can't get any answers either. It really is frustrating. I am going to keep trying to find out. When I called the T-Mobile store they said that I could bring it back w/in the 14 days & replace it and I may do that if I can't get an answer for the problem! If you happen to find out what the answer is PLEASE post and let us know! Thanks

My wife has the same issue with not auto connecting. She has a AT&T S5 that is not rooted....thanks to AT&T putting her in prison lockdown. I think it could be something with the last update because her phone used to auto connect just fine and now it doesn't. The strange thing is that she just now noticed it not connecting and she had took an update that was a few weeks ago or whenever it actually was and now we don't really know for sure if it's really just now an issue or has been since the update....imo I think it could be something with the update.
I have an S5 as well with no issues, but then again, I have the TMO that's rooted and carrier unlocked running custom rom.....thanks TMO for not being D***'s like at&t

Solution!
Long story short, there's a problem with Android and DHCP. Specifically, an IP associated with a router doesn't die when it should and attempting another connection goes back to this IP instead of using the correct (new) IP.
The good news is to forget the problematic wifi connection, head into /data/misc/dhcp/ and remove the files, reboot then connect to wifi. That flushes the DHCP lease information and life should be good.

omarriachi said:
Long story short, there's a problem with Android and DHCP. Specifically, an IP associated with a router doesn't die when it should and attempting another connection goes back to this IP instead of using the correct (new) IP.
The good news is to forget the problematic wifi connection, head into /data/misc/dhcp/ and remove the files, reboot then connect to wifi. That flushes the DHCP lease information and life should be good.
Click to expand...
Click to collapse
I seem to be having this problem now, however I tried doing what you suggested and I don't have the path you mentioned, how do you get to it?

cgdart said:
I seem to be having this problem now, however I tried doing what you suggested and I don't have the path you mentioned, how do you get to it?
Click to expand...
Click to collapse
use a program like "root explorer" or "ES file explorer" and navigate to your root folder ( / )
then follow the path /data/misc/dhcp/ , you will find the files i mentioned there.

omarriachi said:
Long story short, there's a problem with Android and DHCP. Specifically, an IP associated with a router doesn't die when it should and attempting another connection goes back to this IP instead of using the correct (new) IP.
The good news is to forget the problematic wifi connection, head into /data/misc/dhcp/ and remove the files, reboot then connect to wifi. That flushes the DHCP lease information and life should be good.
Click to expand...
Click to collapse
Im reviving this thread, I have this issue also. And with my "unlimited" tmobile bandwidth of 2gb, this bug is completely screwing me over.
I quoted this post since you just claim its Android and DHCP, if thats the case, wouldnt all android phones just not work like the S5?

omarriachi said:
Long story short, there's a problem with Android and DHCP. Specifically, an IP associated with a router doesn't die when it should and attempting another connection goes back to this IP instead of using the correct (new) IP.
The good news is to forget the problematic wifi connection, head into /data/misc/dhcp/ and remove the files, reboot then connect to wifi. That flushes the DHCP lease information and life should be good.
Click to expand...
Click to collapse
Finally..it's work for me..tqvm

Hey I'm having the same issue, only with my work open wifi. The phone will be aware there is a wifi and it tells me to sign in. I go to the wifi settings and tell it to connect it does, but if it drops for any reason it won't automatically connect again, I have to go through the same thing every time.
I read this in a previous post:
"use a program like "root explorer" or "ES file explorer" and navigate to your root folder ( / )
then follow the path /data/misc/dhcp/ , you will find the files i mentioned there."
I have X-plore and went to the root/data folder, but there was nothing in the data folder - Do you have to be rooted for this to work?
Any help would be appreciated.
Samsung Galaxy S5 - Koodo - Unrooted

solved mine by follow this guide
http://forum.xda-developers.com/showthread.php?t=2547356
Sent from my SM-N9005 using Tapatalk

It works fine on my home network and others that I have a username and password for. The issue is WIFI hotspots at coffee shops and work and such, where I don't have access to the router settings.
I have an app that does an auto login when it recognizes that you need to sign in once it connects to wifi, and it works when I tell the phone to connect, but the phone will never connect automatically - I have to go into the WIFI settings and tell it to connect manually every time.
I have the 'Smart Network Switch" unchecked, and I have 'forgotten' and reconnected several times but it still happens.
Samsung Galaxy S5 (SM-G900W8)- Koodo - Unrooted

omarriachi said:
Long story short, there's a problem with Android and DHCP. Specifically, an IP associated with a router doesn't die when it should and attempting another connection goes back to this IP instead of using the correct (new) IP.
The good news is to forget the problematic wifi connection, head into /data/misc/dhcp/ and remove the files, reboot then connect to wifi. That flushes the DHCP lease information and life should be good.
Click to expand...
Click to collapse
Thanks. This solved my problem ?

I had a corrupt .keystore on my S5 and the fix I found by googling was to do a reset of the device.

[Sprint/others?] Hotspot now functions correctly with root

Hi there, before now some people were having issues with the hotspot workarounds, where they could enable the hotspot but attached devices received no actual internet. I didn't do any polling but it seemed to be mostly a Sprint phenomenon, as after doing the magic hotspot trick most other people had no issues.
I just tested it, and the new root will get you functioning hotspot on Sprint, and possibly for other people too who were having the same problem. I ran the following code while the hotspot happened to be off, and after turning it back on I was able to get internet through it on other devices. If you try this with the hotspot already enabled please report back so we know if it needs to be either particular setting. Use a normal command line where you have adb.exe and run this command while the phone is on and no further action should be needed once you turn on the hotspot.
Code:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
Just having root itself has not enabled the normal hotspot switch locations, like in the notification drawer or in the tethering settings, and I still had to use the network refresh trick to get them to work. This may need another command to insert/change the correct protection setting, or something else entirely.
I also went back to the APN settings through the shortcut maker and received the same error I had before, about this user not being able to access them.
On a related note, I saw some people mention that their hotspot would automagically turn off after 10-20 minutes, so I'll post this now and keep an eye on whether it does so here, as I never watched before.

lafinjack said:
Hi there, before now some people were having issues with the hotspot workarounds, where they could enable the hotspot but attached devices received no actual internet. I didn't do any polling but it seemed to be mostly a Sprint phenomenon, as after doing the magic hotspot trick most other people had no issues.
I just tested it, and the new root will get you functioning hotspot on Sprint, and possibly for other people too who were having the same problem. I ran the following code while the hotspot happened to be off, and after turning it back on I was able to get internet through it on other devices. If you try this with the hotspot already enabled please report back so we know if it needs to be either particular setting. Use a normal command line where you have adb.exe and run this command while the phone is on and no further action should be needed once you turn on the hotspot.
Just having root itself has not enabled the normal hotspot switch locations, like in the notification drawer or in the tethering settings, and I still had to use the network refresh trick to get them to work. This may need another command to insert/change the correct protection setting, or something else entirely.
I also went back to the APN settings through the shortcut maker and received the same error I had before, about this user not being able to access them.
On a related note, I saw some people mention that their hotspot would automagically turn off after 10-20 minutes, so I'll post this now and keep an eye on whether it does so here, as I never watched before.
Click to expand...
Click to collapse
This didn't work for me. Any other ideas. Says hotspot service not provided? I can't even switch it on?

An easier command to type that does the same thing is:
Code:
adb shell settings put global tether_dun_required 0