Google has released its latest version of Android OS several weeks ago, Android Jelly Bean 4.2.2. This new update has no significant changes, only few new feature updates and bug fixes. I’ve updated my Galaxy Nexus to Android 4.2.2 via OTA updated. The update was about 44MB so it was easy to download using my Telkomsel Flash packet data .
Changes in Android 4.2.2:
So far i found only two new features that most useful for me, the Wifi and Bluetooth toggle via Quick Settings and ADB Whitelist.
Wifi and Bluetooth toggle via Quick Settings
This feature is very usefull for me since i use wifi frequently. I frequently need to disconnect Wifi connection with my pocket wifi to save data usage and sometimes i have to disable and enable the Wifi connection to make the connection works for some bad Wifi connections. For bluetooth i also frequently disable and enable it for transfering photo files with my Blackberry and MacBook. To disable or enable Wifi and bluetooth just long press on their icons until the status changes (on or off).
ADB Whitelist (Secure USB Debugging)
Android debugging, as provided by the Android Debug Bridge (ADB) gives us almost complete control over a device when enabled. This is very usefull for developing or testing an application , but can also be used for other purposes such as install and remove apps, copy files to and from the device and execute shell commands on the device. If you have a rooted device, you have complete control over system files. You can get some applications specific data such as stored password, disable or enable specific settings in an application, disable or crack device lock even log in into your Google account. So even though your device is locked, either using password or face unlock, someone can easily access your device by connecting the usb cable and crack or disable the lock.
In Android 4.2.2, a proper solution was introduced with the so called ‘secure USB debugging’. With this feature, only hosts explicitly authorized by the user can now connect to the adbd daemon on the device and execute debugging commands. Therefore, if someone tries to connect a device to another one via USB in order to access ADB, they need to first unlock the target device and authorize access from the debug host by clicking ‘OK’ in the confirmation dialog. You can make your decision persistent by checking the ‘Always allow from this computer‘ and debugging will work just as before, as long as you are on the same machine.