My remedy is shsu -- a very simple patch on top of the standard recovery image that will prevent loss of root access when applying an OTA update. Here's how to install and use it: read more
Back to my "favorite" Android Issue 82. It seems Android engineers prefer Wi-Fi Direct over ad-hoc as illustrated by this thread.
Ad-hoc has slipped in priority in favor of other superior solutions keeping power constraints and security in mind. Soft Ap support exists and wi-fi direct support will come in the future.read more
Despite all the excitement about custom ROMs, my Android phone is running the vanilla (Google experience) ROM that shipped from my network operator. However, I want to be both up-to-date and rooted, so I apply each OTA update but not without caution.
An OTA update typically removes the setuid bit from all executables on the system partition (the only one allowed to have the setuid bit set). To avoid losing root, I crafted my own recovery image which differs from the vanilla recovery image in one major aspect: before it reboots, it installs shsu: a shell-only su. Thus, even after unintended OTA update (happened before), I keep my root access.
read moreWhen working on Android, I found it useful to be able to unpack a boot image, replace a few files and repack it. unbootimg is the perfect complement to the mkbootimg tool that is used to create Android boot images.
read moreAs explained by Android Police, rooting an Android phone does not necessarily mean installing a custom ROM. Do you want to root the phone but avoid the hassle of custom ROMs? read more
Suppose you want one Android phone to connect to another. Unfortunately, the WifiManager in stock Android ignores ad-hoc networks. There are a couple ways around this: