4 ms·
> Corrections welcome. I'll point out that rooted Android is an option that grants you much more control. You can even build Android for many devices from sour
by Zak 5y ago
> Corrections welcome.
I'll point out that rooted Android is an option that grants you much more control. You can even build Android for many devices from source if you're so inclined (though perhaps not all of the drivers).
Rooted Android increasingly tends to be an option best reserved for technically-sophisticated users, but compiling OpenWRT from source isn't exactly consumer-friendly.
- 1vuio0pswjnm7 5y agoOf course, there is no requirement to compile OpenWRT. GL.iNet has already done that for the consumer that has no interest in compiling. https://openwrt.org/toh/gl.inet/gl-e750 https://openwrt.org/toh/gl.inet/gl-e750 What are the resource requirements for building Android from source versus building OpenWRT. The option that requires much more significant resources is less consumer-friendly, IMO. It is certainly less friendly for this user. OpenWRT is a smaller OS than Android and less complex. For me, OpenWRT easier to work with than Android. Perhaps I am not "technically-sophisticated". I just want more control. I prefer commandline programs to "smartphone apps".
- Zak 5y agoI am not suggesting a specific course of action to you; if you're happy with the approach you're using, I don't think I have a better one for you. Instead, I am offering corrections as you requested. It is possible to manipulate the hosts file and low-level DNS configuration on Android with root. It is possible to use tcpdump on Android with root. I expect it's reasonably possible to run servers on Android with root, but there seems to be less interest in that (a long-running server is surely bad for the battery life of a typical Android device, for example).
- 1vuio0pswjnm7 5y agoYour correction has been noted. Thank you.