I can't say that I completely understand how but the issue was solverd after I changed the DNS settings of my phone (for my home WiFi).
I set it to Google default DNS 184.108.40.206 and 220.127.116.11.
And since that never this problem again.
Why the phone was loosing the whole connection is still unclear to me (though it remains now pure theoretical question)
That's not worth the trouble.
It's not supported out of the box by Android and you would have to (re)compile and configure and script many things. The dedicated router is the more reasonable and stable solution (and it's also cheap).
Reasons are the following. You would need:
USB host support
finding a USB wifi module that's supported by linux
Compile a ...
Maybe I am not understanding correctly, but you could set your phone as a Mobile Hotspot and configure a wireless router as a bridge between your existing network and the hotspot. In this scenario, all devices on your network would be using the wifi signal of the router and only the router would need to be configured to reconnect to the hotspot.
Using wi-fi and hotspot at the same time is not a standard feature introduced in stock Android or custom ROM's so far (AFAIK). There are apps that makes it possible using Wi-Fi Direct. However you can do this manually too if you are comfortable with commandline usage. Even a USB Wi-Fi dongle is not needed if managed and AP modes are supported simultaneously ...
I bet your home router supports WiFi. It's the same wireless networking technology that laptops use to connect to the Internet. Android devices have WiFi too, you can enable it and connect to your router to use its Internet connection.
Lucky for me, my router has a connection log, that I could look through.
From my phone that was trying to download an app, there were many connections, but these brought up my interest:
tcp 192.168.1.174:51959 18.104.22.168:443 SYN_SENT
tcp 192.168.1.174:51974 22.214.171.124:443 ...
You would be able to ping a local host by name only if your Wi-Fi router (or some other local host) is running a DHCP/DNS server which does know the name of the host you are trying to ping. This is a screenshot from my router:
Also make sure your Android device is sending DNS queries to local server and not on internet. Android loves Google ...
A Hotspot is simply a space where a device (an access point) is hosting a Wi-Fi. When it is in public we call it public [Wi-Fi] hotspot. When it is for private individuals only it is simply Wi-Fi to us. Either way, the difference is in the name only.
When you ask a friend to create a hotspot, you are asking them to host a Wi-Fi using their mobile device. ...
I solved changing the modem setting. The last versions of Android has problems with the WiFi channel 1 and 13, so the better way is to setting the transmission channel NO automatic, but fixed to an intermediate channel like 5, 7, etc... Since I've done this change the connection works great.
Bluetooth tethering might also be a solution.
That truly works out of the box on Android 3.0+ (and with 3rd party apps on 2.2+). It'll be just fine if you can tolerate the low data rate (BT 2.0 offers 2.1MBit data rate) and the distance between phone + bluetooth-tether client is not too far. In this mode the wifi operates normally and the 2nd (client) ...
Looks like the settings were fine.
I even had that Samba thing set up right.
I turned that Samba on-off from the router, then I removed the "Computer" from SyncMe, re-added, and it worked.
The error actually happened again, later on, with the "could not delete + sharing violation". Then I did the above steps again, and it worked.
I didn't have long ...
You can connect a PC to a phone via USB and use phone carrier data or wifi internet on which you connect via phone. That option is called USB tethering (sharing your Android device's internet connection via USB), and custom ROMs have it, don't know for stock, that option is in the same place as wifi hotspot. I'm sorry if I understood you wrong, and if this ...
Improvement on previous Answer:
Well i do partially agree with @Divin3 only a slight glitch i found was: All new routers are fully backward compatible with older devices hence a router built on Wireless-N will be fully compatabile with device capable of receiving only Wireless-G or older version. Difference will be that while serving to a device with W-G the ...
As you can access the NAS fine via its IP address, the NAS is reachable from your Android device – but the issue is, your Android device cannot resolve its name. That is because Android, by default, always uses Google's name servers, no matter what the DHCP server tells it. You will have to override those settings:
Open Settings (e.g. from your app drawer) ...
This is sometime because your phone save the paswrd of your wifi and sometime it doesnt connect it just show this that it is connecting to but does not become successful in doing so . . . . so remove or forget your wifi connection
restart you phone
and try to connect again with that wifi
may this can help you
worked fine with me many times