Database Users

DNS issue in n1 android?

every morning when i wake up, i use home wifi to surf a bit before i go out
the n1's network *always* get stuck, as if it can't resolve any hostname
Using that "Phone Info" app (*#*#4636#*#*), i ran a ping test:
Ping IpAddr: Pass
Ping Hostname(www.google.com): Fail: Host unreachable
I suppose this means either my dns setting is incorrect or the dns is down,
so i did another test using "DNS lookup" app from market,
i tried resolving hostname with 8.8.8.8 (google's public dns) or my network operator's dns
both's working fine
rebooting the phone always fix the problem, and the problem seems to appear after wifi usage
I suppose this means the switching between wifi / 3g some how get the phone into a stuck situation?
Is anyone experiencing anything like this? I guess I am not the only one
mods: yea this might not be exactly android development, but this is the closest sub forum
please move this thread as you see appropriate

Same here.
There was another thread on this issue, suggesting clearing the cache and using setprop (or some command like that) for dns settings through GScript Lite. But a reboot always works for me, when the other methods fail.

glad that i m not alone : )
are you referring to this?
http://forum.xda-developers.com/showthread.php?t=640029&highlight=dns
i will try that app and see how it works,
is there any easy way to do a setprop whenever i need? i m unrooted

I had this problem (and not just between WiFi and 3G, but 3G and Edge, 3G and no service, etc.) on the stock Nexus 2.1 software, and also on my Milestone under 2.0 and 2.0.1 (though MUCH less frequently under 2.0.1).
You don't typically need to reboot, just go to airplane mode and back.
This might be a reason to unlock and install another ROM, because I have never had this problem under any Cyanogen build I've used (just 5.0.4.1, 5.0.5 and 5.0.5.1).

Setprop doesn't seems to work without root
$setprop net.dns1 8.8.8.8
$getprop net.dns2
192.168.0.1
I will file a bug report to see what google says
n1 is a good computer but not such a good phone, its been months since initial release but they have yet to fix many basic bugs
I had no problem with my god old g1 back then

got this issue too, but no need to reboot the phone, just disable and enable the wifi again will work.

Wifi - getting address, no connection at the end

Hi, in case this has been already solved I apologize in advance, however I searched all the post on this and could't find real solution to my problem and from what I have read I am not alone...
The think is that if I install any build of Androud to my Leo everything works perfect except the WiFi connection - after enabling WiFi and pointing it to my router it recognizes it, accepts the password (WPA-PSK protection) and then after some time of getting IP it never connects and it goes on and on.
I tried every single thing I have found all around this forum and many others, unfortunatelly nothing could make it work (forcing static IP, opening the network without protection, changing networks SSID, leaving WiFi on and restarting, etc.)
It is really pitty as I really like the way Androind moves on HD2, but as I use the Wifi a lot to unload a bit my data plan I cannot stick with it at the moment. So, is there any real solution to this problem?
Thank you in advance.

I have the same problem. But the connection is fine when I was under Winmo.

The only time I've experienced a similar issue was when I upgraded to a new kernel, without pushing the new modules. What builds and kernel are you using?
Sincerely,
Mac

Try updating your builds or just modifying the mac adresses

I already have this issue when upgrading or changing build. I resolved the problem with Airplane Mode. switch on/switch off. Let us know the result. ^^

I was having the same problem. It wouldnt connect to my home network, but it would connect to every other network. Turns out my router was too old. I recently got a new router and it works fine. Also, when I had my G1, it also wouldnt connect to my home network via wifi, but it does with the new router.

wangshuokevn said:
I have the same problem. But the connection is fine when I was under Winmo.
Click to expand...
Click to collapse
On WinMo no problem.

white-energy said:
Try updating your builds or just modifying the mac adresses
Click to expand...
Click to collapse
As I wrote before, I tried many different builds with no succes. At the moment I installed MCCM SE V3.4(FroyoStone Sense)[kernel hastarin r8.5]. As I have nothing to save I do everytime clean install on reformated card.

lamario said:
I was having the same problem. It wouldnt connect to my home network, but it would connect to every other network. Turns out my router was too old. I recently got a new router and it works fine. Also, when I had my G1, it also wouldnt connect to my home network via wifi, but it does with the new router.
Click to expand...
Click to collapse
IMHO the router is not the problem even it's a bit outdated - Linksys WRT54GL - as I tried to connect to friend's network, I also created AP from my notebook - with the same result.

hatchy77 said:
I already have this issue when upgrading or changing build. I resolved the problem with Airplane Mode. switch on/switch off. Let us know the result. ^^
Click to expand...
Click to collapse
The Airplane mode you toggle in WinMo or Android? I tried it in WinMo - no success.

oh yes...
... I know this kind of problem.
Tried so many builds of Froyo. Most wlan-stable was indeed MCCM SE V3.4(FroyoStone Sense)[kernel hastarin r8.5] - with this build I had no wifi drops or hsdpa drops.
From today on I try the MDJ FroYo HD v.4.1[kernel:MDJ S7.3HD]. Most time it holds the connection, but sometimes when waking up from stand-by I have to disconnect and reconnect wifi.
Router: Linksys WRT54G.

mac-nukem said:
... I know this kind of problem.
Tried so many builds of Froyo. Most wlan-stable was indeed MCCM SE V3.4(FroyoStone Sense)[kernel hastarin r8.5] - with this build I had no wifi drops or hsdpa drops.
From today on I try the MDJ FroYo HD v.4.1[kernel:MDJ S7.3HD]. Most time it holds the connection, but sometimes when waking up from stand-by I have to disconnect and reconnect wifi.
Router: Linksys WRT54G.
Click to expand...
Click to collapse
Thanks for the answer, unfortunatelly I have nothing to drop as I cannot connect. On the other hand either EDGE and HSDPA works like charm - solid connection.

snekoza said:
The Airplane mode you toggle in WinMo or Android? I tried it in WinMo - no success.
Click to expand...
Click to collapse
Into Android my friend

I also had this problem. It's easily solved by loging into your router and setting up the access list (under adv wireless settings on mine). You can add the device in with its specific mac address and by doing this I was instantly able to use wifi.

It's not an issue with mac address filtering. I know this issue because I have the same problem with the wifi router at the office. I can connect without any problem at home but It just won't work at the office.
DHCP server assigns an IP, but if you try to ping any IP outside LAN you'll get network unreachable.
I didn't have time to test a bit more, but I'll try to change the mac address of my wlan in order to test if the problem relies in there. The idea is to assign the same MAC Adress I have on WinMo. This will be very useful also to people with 2 HTC HD2 using the same ROM and Kernel.
BTW, I'm not using MAC Address filtering, this issue has nothing to do with it.

I have the same problem here ..
Please help me buddy!
thank you in advance
hassohd2

I tried this switching in and out of Airplane mode in Android with varying degrees of success. The problem itself seems intermittent for me - sometimes I get a decent amount of time with successful access and sometimes I don't. Similarly a reboot (of Android) may or may not work for me. I am using kernel version 2.6.32.15-gd09adbb gcc version 4.4.0 and is dated Thu Dec 30 19:14:35 CET 2010 for me. I notice I am more inclined to have an issue with Market even than with Firefox. Also it is more of a problem now than with a previous kernel version (but it had problems too if I recall correctly). I upgraded because I am having difficulties with getting the USB link to work under Android (but that problem is still there). It did seem to work well for the first few hours after the upgrade, but since then...
I did notice that under MS WM, the MAC address is quite different to that recorded by my DHCP server (a unix box the other side of my wireless router) for Android. The Android one looked like it was a stock standard number sequence, so fabricated. I wonder where that is set on the phone?
I also noticed that the phone does not have the usual (for Linux) resolv.conf file that often gets configured by the DHCP connection process. Further, entering a host IP in the /etc/hosts file does not necessarily mean that a command like ping will find it every time. Of recent I have not been checking that - I have been using the IP address of my unix box to do ping tests to. The network does (of course) shut down when the phone goes into sleep mode, but does wake up, even responding to a ping from the unix box. Running up Market, though, seems to kill the connection every time now (but a weather update won't).
A further observation: if I get the Wi-Fi network connection to reset itself (straight forward when the lease expires), it is hard to get it to reset itself until after the next lease expiry for some reason.

I did some further tests. I don't have a pipe (|) key on my HTC HD2 that works so the following commands are a little long winded.
localhost / # getprop > /data/tmp/props
localhost / # grep dns /data/tmp/props
[net.change]: [net.dnschange]
[dhccp.eth0.dns1]: [192.168.10.1]
[dhccp.eth0.dns2]: []
[dhccp.eth0.dns3]: []
[dhccp.eth0.dns4]: []
[net.dns1]: [192.168.10.1]
[net.dnschange]: [49]
localhost / #
Now 192.168.10.1 is my (Unix) DNS server.
When I do the following on the phone
localhost / # nslookup 192.168.10.1
(or even localhost / # nslookup cicada or even the fqdn of the server)
and I tail -f /var/tmp/named.log on the server (where I set up logging for queries and resolver categories for this test)
I see no action at all on the server and on the phone I get
localhost / # nslookup 192.168.10.1
Server: 192.168.10.1
Address 1: 192.168.10.1
Name: 192.168.10.1
Address 1: 192.168.10.1
localhost / #
localhost / # nslookup cicada
Server: 192.168.10.1
Address 1: 192.168.10.1
nslookup: can't resolve 'cicada'
localhost / #
and the same for the FQDN.
The DNS server does not even see the request for forward or reverse lookup, strangely enough. But it is seeing the requests from other machines with logs to the reverse lookup from those other machines looking like:
10-Jan-2011 22:21:57.953 queries: info: client 192.168.10.20#38971: query: 1.10.168.192.in-addr.arpa IN PTR +
So, not only does the wi-fi link drop when Market is run, the DNS is behaving strangely to terminal based testing. Further, an update of the weather does not show any traffic in the DNS server log (at least for the logging level I have set up) even though the weather does get updated. It makes me wonder what DNS it is really using.
The other avenue I want to check is DHCP time-out, which I have been keeping an eye on (it does seem to time out and not update, but there are also other issues that suggest the problem is not a time-out one). That will have to be another day at this stage, though.

what channel is the router using for wifi?

[HOWTO] Team EOS & USB Tethering

Hello all,
I am unable to respond to the person requesting this help, so I thought I would post a howto. In order to get your Team EOS Xoom to do USB tethering, you need to do a few steps:
1) Install a kernel from their development thread
a) Download kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1488059
2) Install the drivers for the kernel you just installed
a) Download both overlay revs and both driver revs from this thread: http://forum.xda-developers.com/showthread.php?t=1513490
b) Reboot into recovery
c) Flash in order: kernel, overlay rev 1, overlay rev 2, driver rev 1, drivers rev 2.
d) Reboot into EOS. After the updating Android message, reboot again for good measure.
You may have to repeat step 2)c) minus the kernel if your drivers are missing.
3) Standard steps for acquiring IP address from USB master.
a) Plug in your phone
b) On your phone, go to wireless and networks, and enable USB Tethering
c) On your Xoom, open terminal
d) su
e) dhcpcd usb0
f) setprop net.dns1 8.8.8.8
If you get an error about usb0, try usb1. If neither work, make sure your drivers are installed and working correctly.
If you need additional help, reply below and I will respond as I'm available.
Thanks to all you dev teams making dreams come true.

Hi gnet26
Many thanks for your PM and your post and thread here.
I will follow your instructions and try again once I get home and report back either way.
Many thanks again for your willingness to help out.
I'll post back on this thread. ( not my Q&A thread ) so it is all in the one place.
All the best,
Ben

Hi gnet26
You are a LEGEND !!! It WORKS !!!!!!!!!!! Woooo Hoooo.
I had forgotten just how much snappier and smoother USB Cable Connected Tethering is compared to WiFi Tethering.
Thank you BIG TIME !!!
One minor issue remains, which hopefully can be resolved.
=> no matter how I discconect - uncheck tethering on the phone or close the Terminal session or unplug the cables at either end, the Xoom freezes up and reboots ?!?!??!
Any idea how to ghet around or fix this ?
The phone itself is unaffected.
All the best,
Ben

ben ifin said:
Hi gnet26
You are a LEGEND !!! It WORKS !!!!!!!!!!! Woooo Hoooo.
I had forgotten just how much snappier and smoother USB Cable Connected Tethering is compared to WiFi Tethering.
Thank you BIG TIME !!!
One minor issue remains, which hopefully can be resolved.
=> no matter how I discconect - uncheck tethering on the phone or close the Terminal session or unplug the cables at either end, the Xoom freezes up and reboots ?!?!??!
Any idea how to ghet around or fix this ?
The phone itself is unaffected.
All the best,
Ben
Click to expand...
Click to collapse
Couple things. You don't have to mess with USB tether in network settings. That's to pass mobile data from xoom to a client. Also, the only driver you need is rndis_host.ko. The hard reboot is something wonky with the driver being used as a module. If I can find a way to cook it inside the kernel without breaking other things I will. Also, I'm pondering a helper app to manage usb1 and eth0 interfaces.

Ben,
I'm glad you got it to work! My Xoom also reboots when I unplug.
Bigrushdog,
If you need a Guinea pig for testing a kernel, pm me
The usb tethering checkbox step is on the phone side. Are you saying that step is unnecessary?
Also, what would the helper app do? Would it work like the auto-usbdrive mounter where it checks for rndis connection and automatically does a dhcpcd request and sets dns?
Thanks for the interest!

Bigrushdog,
Do you know how to make everything go through usb0? Things such as Google market downloads and vpn connection refuse to use the usb0 interface. Care to shed some light on the matter?
Thanks,
Gnet

Aml
gnet26 said:
Bigrushdog,
Do you know how to make everything go through usb0? Things such as Google market downloads and vpn connection refuse to use the usb0 interface. Care to shed some light on the matter?
Thanks,
Gnet
Click to expand...
Click to collapse
Ok I misunderstood you. Yes you have to tell the phone to start USB tether. First, rndis_host will always be on usb1. Usb0 is reserved by the system for complex reasons. And I'm working on the exact issue you describe. I've been busy learning new things the last couple week's and have been distracted. Basically, Android does not know to monitor these interfaces for a default tcpip route. Some smart apps like Dolphin find these routes on their own but the system does not. I think I can seamlessly add these interfaces to androids list without breaking anything. That would be the best solution. Otherwise, a small helper app can do it in the background. This applies to eth0 for ethernet and data dongles too.

Hi bigrushdog and Gnet
bigrushdog - massive thanks to you - without all your efforts this would never be happeneing !!
Same Google Market / Play Market issue here.
All the best,
Ben

Hmmmm ....... I wonder ......... if we use
su
dhcpcd usb1 [ instead of 0 ]
setprop net.dns1 8.8.8.8
will this still connect *and* make Google Market downloads and vpn connection functional ?
Ben

ben ifin said:
Hmmmm ....... I wonder ......... if we use
su
dhcpcd usb1 [ instead of 0 ]
setprop net.dns1 8.8.8.8
will this still connect *and* make Google Market downloads and vpn connection functional ?
Ben
Click to expand...
Click to collapse
...... well I can report that this does *not* work.
Ben

ben ifin said:
...... well I can report that this does *not* work.
Ben
Click to expand...
Click to collapse
This guy knows his stuff
http://forum.xda-developers.com/showpost.php?p=23299408&postcount=31
Look into that and report back

Success
I thought I would share with everyone what I did to get my 4G USB dongle to work. This dongle only requires the RNDIS drivers as it simply appears as an ethernet connection over USB. I had this working previously on a Tiamat 3.2 ROM, but until now I could not get it working. This may help others trying to use ethernet adapters.
I flashed BRD's Development Overlay Rev. 4 and rebooted.
I then plugged in my dongle through a USB host cable and waited for it to boot and connect.
Then in a terminal window
su
dhcpcd eth0
After this command is entered the IP address that is assigned to eth0 is displayed. I guessed that the gateway would be the first two digits of the assigned IP address followed by "0.1". If you know the gateway of this connection I would try substituting that in for the IP address below.
I then entered...
ip route add default via X.X.0.1
setprop net.dns1 8.8.8.8
Once I did all that the connection was up and working.
I hope this helps someone
[EDIT] Well it works for the most part. Web surfing, general data access and email work but both the Google Market and Amazon market fail to download applications over this connection.
For me it is still better than nothing.

Try adding in the busybox route command in the link in my post a couple posts up. It may help Android see the data path.

bigrushdog said:
Try adding in the busybox route command in the link in my post a couple posts up. It may help Android see the data path.
Click to expand...
Click to collapse
Are you referring to this?
/system/xbin/route del default
/system/xbin/route del default
/system/xbin/route add default gw $IPREMOTE dev ppp0
I tried simply entering those commands in the terminal window and they were not recognized. Is there something else I need to do?
Thanks!

He is using the route command from busybox. So try
busybox route
Or
/system/xbin/busybox route

bigrushdog said:
He is using the route command from busybox. So try
busybox route
Or
/system/xbin/busybox route
Click to expand...
Click to collapse
Ok thanks for the info, as I have told you I really am a newbie but I can follow instructions.
So I tried a few combinations and here are my results.
su
dhcpcd eth0
Responds with eth0 IP information
busybox route del default
Responds with "route:SIOCDELRT: No such process
busybox route add default gw $IPREMOTE dev ppp0
Responds with "route: resolving dev"
setprop net.dns1 8.8.8.8
This did not work, I did not have any connection. I was not sure if I should have done the setprop net.dns1 before the busybox commands so I rebooted and tried it this way...
su
dhcpcd eth0
Responds with eth0 IP information
setprop net.dns1 8.8.8.8
busybox route del default
Responds with "route:SIOCDELRT: No such process
busybox route add default gw $IPREMOTE dev ppp0
Responds with "route: resolving dev"
This did not work either.
I then went back, without a reboot and entered...
ip route add default via 50.9.0.1
After adding this command I can browse the internet and a few applications work such as WeatherBug, but it does not seem that anything else can see the connection (email, markets, touchdown, etc.). It is strange that WeatherBug can see the connection, but other apps like Accuweather could not.
So I rebooted again and tried it in this order...
su
dhcpcd eth0
Responds with eth0 IP information
ip route add default via 50.9.0.1
setprop net.dns1 8.8.8.8
busybox route add default gw $IPREMOTE dev ppp0
Responds with "route: resolving dev"
Same result, I can surf the web but nothing else sees the connection.

dev usb1
ppp0 is for something else
EDIT; and I'm not sure that will resolve it. Just throwing it out there

bigrushdog said:
dev usb1
ppp0 is for something else
EDIT; and I'm not sure that will resolve it. Just throwing it out there
Click to expand...
Click to collapse
Should I actually use eth0 then?
Do you think I need to do the IP route command as well or should this take care of it?

This may be a very stupid question but will this, or something like this work on EOS 4 (I'm on 177 but I'd do whatever to get this to happen).
Thanks

usb to ethernet adapter

Hi!
So I am in college and they do not allow more than one device to be connected over internet per person in a dorm, so i cannot set up any wireless routers. My iconia is running the jb cm10 preview port and i was wondering if a usb to ethernet jack would work and if so, which adapter should I buy?
any suggestions/ ideas would be appreciated

cullenmq1 said:
Hi!
So I am in college and they do not allow more than one device to be connected over internet per person in a dorm, so i cannot set up any wireless routers. My iconia is running the jb cm10 preview port and i was wondering if a usb to ethernet jack would work and if so, which adapter should I buy?
any suggestions/ ideas would be appreciated
Click to expand...
Click to collapse
I dont believe it would but im not sure how can they tell whos device it is? Cant you just spoof your mac address or use one device at a time or a vpn......

they could tell if more than 1 device is connected by doing a simple network scan and seeing that there was 2 ip addresses assigned to a dorm. they found my wireless router as soon as i plugged it in

cullenmq1 said:
they could tell if more than 1 device is connected by doing a simple network scan and seeing that there was 2 ip addresses assigned to a dorm. they found my wireless router as soon as i plugged it in
Click to expand...
Click to collapse
sorry theres ways to get around that but im pretty sure were not allowed to talk about it on the forums im nlt sure if a usb to ethernet adapter would work to me it seems drivers program or something would be missing

okay... does it involve external hardware or does the "other thing" involve using a wifi router b/c i cannot set up a wireless router as anyone with a wireless device will be able to see it. I know that the transformer infinity has built in ethernet adapter compatibility, but is that an android ics/jb thing or is it a manufacturer add-on?

cullenmq1 said:
okay... does it involve external hardware or does the "other thing" involve using a wifi router b/c i cannot set up a wireless router as anyone with a wireless device will be able to see it. I know that the transformer infinity has built in ethernet adapter compatibility, but is that an android ics/jb thing or is it a manufacturer add-on?
Click to expand...
Click to collapse
Haha i dont understand how they could detect where each device is coming from unless they have a separate wifi for each dorm or a different sub-net i know they could pick up another wireless router easily even if they were reading you ip that's easily spoofed even Mac address is via a proxy or vpn but anyways im pretty sure that's an manufacturer add-on ill look and let you now if i find anything the Acer might have it, if not im sure a dev could make it so somehow
This is straight quoting darkdragone make sure you thank him Here
not sure if it works with honeycomb, but on ICS I have used a usb ethernet adapter with the tablet, mind you that some applications dont work with it, but the browser and market place do. What you'll need to do first is have your tablet rooted, then download either android terminal emulator or Gscript lite (with gscript lite you can save the script for use again.) In the terminal you will want to run netcfg, this will show you all of your interfaces and will tell you if your usb to ethernet adapter is detected. If it is detected there will be an interface called usb and then a number aka usb0 or possibly even eth0. next you will want to take that interface and make sure it is up by running ifconfig usb0 up. next you'll need an ip address, if yours is assigned dynamically then run dhcpcd usb0 then setprop dns1 8.8.8.8 (or use whatever DNS server you wish). Now if you need a static address, such as 192.168.0.2 or something you would run ifconfig usb0 192.168.0.2. Also all of these commands will need root so make sure you type in su beforehand.

gears177 said:
Haha i dont understand how they could detect where each device is coming from unless they have a separate wifi for each dorm or a different sub-net i know they could pick up another wireless router easily even if they were reading you ip that's easily spoofed even Mac address is via a proxy or vpn but anyways im pretty sure that's an manufacturer add-on ill look and let you now if i find anything the Acer might have it, if not im sure a dev could make it so somehow
This is straight quoting darkdragone make sure you thank him Here
not sure if it works with honeycomb, but on ICS I have used a usb ethernet adapter with the tablet, mind you that some applications dont work with it, but the browser and market place do. What you'll need to do first is have your tablet rooted, then download either android terminal emulator or Gscript lite (with gscript lite you can save the script for use again.) In the terminal you will want to run netcfg, this will show you all of your interfaces and will tell you if your usb to ethernet adapter is detected. If it is detected there will be an interface called usb and then a number aka usb0 or possibly even eth0. next you will want to take that interface and make sure it is up by running ifconfig usb0 up. next you'll need an ip address, if yours is assigned dynamically then run dhcpcd usb0 then setprop dns1 8.8.8.8 (or use whatever DNS server you wish). Now if you need a static address, such as 192.168.0.2 or something you would run ifconfig usb0 192.168.0.2. Also all of these commands will need root so make sure you type in su beforehand.
Click to expand...
Click to collapse
Glad I was able to help lol. I'm currently trying to find out if a USB wireless will work to but haven't found much info other than drivers need to be in the kernel for it to work

Yeah, if u figure out the usb wireless adapter problem, let me know too pls. :thumbup:
Sent from my A500 using xda app-developers app

How do I assign a permanent static IP address to hotspot in Android 10

I would like to assign a permanent static IP address to hotspot in Android 10 (Unofficial LineageOS 17.1 for Natrium by LuK1337, rooted with Magisk v20.3 and updated to Jan 11, 2020 build).
Now whenever I turn on the hotspot, it assigns a different IP to hotspot, 192.168.43.xxx (this will be the gateway IP to other devices that connects to this hotspot).
Note: For simplicity, instead of connecting other devices to this hotspot, I'm just gonna find hotspot IP by running "ip r" on the phone itself.
On the phone, when I open Termux (have tried other Terminal app with the same results), and run, "ip r" and "ip a", I get:
Code:
:/ $ ip r
192.168.43.0/24 dev wlan0 proto kernel scope link [B]src 192.168.43.100[/B]
:/ $
:/ $ ip a
25: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 3000
link/ether 78:02:f8:f0:4d:87 brd ff:ff:ff:ff:ff:ff
inet 192.168.43.[B]100[/B]/24 brd 192.168.43.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 fe80::7a02:f8ff:fef0:4d87/64 scope link
valid_lft forever preferred_lft forever
:/ $
Now this "src 192.168.43.100" will be different (e.g: 192.168.43.101, 192.169.43.102 etc) everytime I turn hotspot on and off... and I would like to assign a permanent static IP like ".100"
In LineageOS 16 I used the following workaround, which is no longer working in Android 10 (Unofficial LineageOS 17.1):
Code:
In the Termux (have tried other Terminal app with the same results):
(1)
su
mount -o rw,remount /vendor
nano /vendor/etc/init/hostapd.android.rc
and add:
on property:init.svc.hostapd=running
exec - -- /system/bin/sleep 2
exec u:r:magisk:s0 -- /system/bin/ip address add 192.168.43.[B]100[/B]/24 dev wlan0
Save the file.
mount -o ro,remount /vendor
and
(2)
su
mount -o rw,remount /
nano /etc/dnsmasq.conf
and add:
dhcp-host=78:02:f8:f0:4d:87,192.168.43.[B]100[/B]
Save the file.
Then set the permissions:
chown 0.0 /etc/dnsmasq.conf
chmod 0644 /etc/dnsmasq.conf
chcon u:object_r:system_file:s0 /etc/dnsmasq.conf
magiskpolicy "allow dnsmasq system_file file { read getattr open }"
magiskpolicy "allow dnsmasq system_file dir { search }"
mount -o ro,remount /
Any help is greatly appreciated, many thanks in advance.

I've got the same problem with my Pixel 3 running Android 10, also using Termux.
My use case is SSHing into the phone from my iPad to use VIM.
Previously, I used PDANet for its hotspot functionality, but it doesn't work anymore on my Pixel. Depending on your phone, you could give that a shot.

Unfortunately, starting with Android 9, the gateway is always set randomly. You cannot change it without editing the source code and building the firmware, but you can assign an additional static IP address through which you can connect to the phone. I'm not sure that this will help you, but you can see here three methods to solve this problem:
android.stackexchange.com/questions/213514/how-can-i-permanently-change-my-hotspot-tethering-ip-address
Personally, I use the first method and it is enough for my needs.

It got even worse. I'm not sure this is a thing since Android 11, but whenever I turn my Hotspot off and on again, it changes the last two segments of my gateway IP, so it's always 192.168.x.x. This sucks even twice, because now all static IPs of all clients need to be updated to get in the right scope for the subnet mask that is still 255.255.255.0.
Pretty ****ty move by Google. I wish there was a solution to this nonsense. I want a static gateway IP without root ... (I know, impossible)

Cis# said:
It got even worse. I'm not sure this is a thing since Android 11, but whenever I turn my Hotspot off and on again, it changes the last two segments of my gateway IP, so it's always 192.168.x.x. This sucks even twice, because now all static IPs of all clients need to be updated to get in the right scope for the subnet mask that is still 255.255.255.0.
Pretty ****ty move by Google. I wish there was a solution to this nonsense. I want a static gateway IP without root ... (I know, impossible)
Click to expand...
Click to collapse
You said without root it's impossible but can we do something with root so that we don't have to update gateway ip everytime hotspot is restarted?

Cis# said:
It got even worse. I'm not sure this is a thing since Android 11, but whenever I turn my Hotspot off and on again, it changes the last two segments of my gateway IP, so it's always 192.168.x.x. This sucks even twice, because now all static IPs of all clients need to be updated to get in the right scope for the subnet mask that is still 255.255.255.0.
Pretty ****ty move by Google. I wish there was a solution to this nonsense. I want a static gateway IP without root ... (I know, impossible)
Click to expand...
Click to collapse
Faced the same problem after my mobile got an update to Android 11.
Please let me know if you found any solution.

byquip said:
Faced the same problem after my mobile got an update to Android 11.
Please let me know if you found any solution.
Click to expand...
Click to collapse
legendofrj10 said:
You said without root it's impossible but can we do something with root so that we don't have to update gateway ip everytime hotspot is restarted?
Click to expand...
Click to collapse
I got close...used MacroDroid with root (Magisk) and I was able to create a macro that started the hotspot and then used secure settings to set the wlan0 IP to what I wanted using ifconfig. Using both ifconfig and a network scanner I confirmed the hotspot had the ip I wanted, but I was not able to actually use it for a stable connection - clients constantly dropped the connection.

I'm still on Android 8.1 beacause of this random hotspot IP address issue.
Is there any recent phone or ROM with a static IP address for its hotspot?

Not really THE solution, but I've had pretty good results serving data thru the phones hotspot to an old dd wrt router (set up as a "repeater bridge"). The router/repeater handles all traffic on a local network then looks to the hotspot for data. Basically, just like your home wifi, but swap your modem with the phone.
Behind the router, it functions like a "real" connection. All apps function, push notices come thru, smart TVs, and even Chromecast works! You can assign static IP on the virtual network.
Devices don't seem to notice the random IP changes between the hotspot and router. At the most, you may lose data for a second or two while it .. switches stuff? Idk... but other than a quick lag in chat, if that, you won't even notice anything happened.
A couple sidebars:
The old wifi b/g routers with ddwrt are cheap on ebay. Although, router throughput could be a limiting factor on network speeds. Not just the older wifi protocols, but running repeater mode sets router to half duplex.
With a lot of the older routers, a USB-to-5v cable works to power it from any USB port (charger, battery pack, accessory port). Ideal for hotel/dorm, work, rural or mobile living. Wherever you need a private, fully functional wifi connection.
In dd wrt setup, follow tutorials for repeater bridge setup, but leave the gateway and dns ip blank (all zeros).
Naturally, speed and ping depends on the cellphones signal strength.

I don’t have an Android phone any more, but I noticed on my family’s Pixels, PDANet gave gives out a consistent 192.168.1.XXX address. PDANet hotspots work like regular hotspots as far as I know, so it might be worth a shot for when you’re on the go without a router to use.

DMechnikov said:
I don’t have an Android phone any more, but I noticed on my family’s Pixels, PDANet gave gives out a consistent 192.168.1.XXX address. PDANet hotspots work like regular hotspots as far as I know, so it might be worth a shot for when you’re on the go without a router to use.
Click to expand...
Click to collapse
Good to know. I didn't even know pdanet was still around. I'll have to mess with it sometime and see what's up. It would be nice to have a static IP coming from the phone, just cause.
Are you talking about the free or a paid version (if there are still two versions)??
Right now I'm using a rooted Umidigi A7 Pro with a 'hotspot unlock' magisk module, coupled with the VPN Hotspot app. This setup allows me to have unlimited hotspot data, I believe stops reporting of hotspot activity back to the ISP, while tunneling the hotspot data thru my phone's VPN connection.
I live waaay out in the sticks of West Virginia. My only ISP option at this time is Hughesnet satellite, which is just THE worst connection on the face of the planet, not to mention pricey. Speeds is so slow, and ping so high, you can't stream media, play games, or use it for voice or FaceTime chats. Instead, I use the phone setup mentioned above.
Luckily, there is a sprint tower (now T-Mobile) near enough to get a bar or two in the window. I picked up an 850mhz band5 cell booster / repeater (actually on band 26, which is a subsection if band 5). Got it set up, now can use the device in-hand throughout my home and out on the porches. Also helped improve speeds, reduce ping, and stabilize jitter on the LAN.
Call of duty mobile pings around 60-80ms
My Metro by T-Mobile plan is $40 per month, no data caps, but no hotspot allotment either. With the rooted device, I routinely use 200+ gb per month of hotspot data on devices connected via the router/repeater in my home.
I've been running this setup for nearly a year now and not had any problems from my ISP.

OP, you might want to look at this solution.

Still having the same issue in 2023 on LineageOS 18.1 (Android 11).
Can't find out which of these classes in sources is responsible for address allocation.

cilyrik said:
OP, you might want to look at this solution.
Click to expand...
Click to collapse
Hi,
After two days of trouble, (and multiples flahing operations, and many other concerns, I found a compromise with the solutions given in your link. Only the first one worked on my rooted smartphone (magisk + rom stock doogee s86pro). I did not manage to remount in rw my partitions to modify the hostapd.android.rc file. So I decided to use the automation (MacroDroid in my case) of the first solution. It works perfectly with 2 macros :
macro #1
trigger = hospot on
action = ip address add 192.168.43.1/24 dev wlan0
and
macro #2
trigger = hospot off
action = ip address del 192.168.43.1/24 dev wlan0
That's all. ^^
* rooted phone required *