Categories
News Updates/Software

Mobile radio active bug to be solved in time for Android 6.0

It appears that some bugs like to linger around for the entire duration of an OS lifetime, but things may change come Android Marshmallow, as the mobile radio active bug from Lollipop will finally be fixed. Users usually report bugs on the Android public issue tracker but this does not mean that every report will be fixed in a matter of hours, days or even months.

 

Android lollipop mobile radio active

 

 

One of the more annoying bugs still lingering on Lollipop is the battery drainage caused by the radio remaining active for way too long. It seems that Google is finally doing something about it and the mobile radio active bug has its days numbered. The fix will roll on Android 6.0.

 

This problem appears in apps that use mobile data, which could mean virtually anything. When you check the usage details on an app, it can show you large amounts of mobile radio active time. This is due to the fact that the system decides not to let the radio sleep after it was used by other apps and this leaves the device active or it makes it wake up repeatedly.

 

You will have to wait for a little while longer for the mobile radio active bug to get fixed though, because it will come with a big system update i.e. Marshmallow. Even if there are lots and lots of users still starring the bug on the tracker, it appears that it cannot be rushed into being solved. At least we know it is being done and it will be implemented soon-ish.

 

Source: Dev Preview Issue

Categories
News Updates/Software

Android 5.0 Nexus rollout halted by WiFi battery drainage bug – issue was fixed and rollouts restarted

The Android 5.0 Nexus rollout had a little problem yesterday when a WiFi battery drain bug almost put a halt in the rollouts. Most Nexus devices were delayed in updates and another speculated release date was November 12th. That is no longer the case as the bug was quickly fixed and updates have restarted rolling out.

 

Lollipop bug

 

It appears that users experienced the problem firsthand as their devices kept waking up rather frequently when WiFi was turned on, which meant Miscellaneous began rocketing to the top of the battery use menu. It appears that, in some cases, the bug is draining up as much as 60-70% of the battery and in some cases the drainage gets to 100%.

Google managed to defuse the bomb and the bug is marked as fixed in the Issue Tracker.

Source: Google Issue Tracker

Categories
Apps News Updates/Software

KitKat issues on encripted ADB backup restores – a fix to come soon

KitKat seems to have some bugs that will be dealt with, but until then you can find out more about them here. Android devices have numerous apps that allow system backups if the user has superuser privileges, but if users don’t have rooted devices they have the only option of backup-ing their data though Android backup service. Some people seem to have a problem with restoring encrypted data backups made with backup apps.

How can you detect this bug

Generally, the symptoms that surround this bug are easy to spot. When users backup data with ADB and encrypt them with a password they can find themselves unable to restore their encrypted data! Backups can’t be restored if they are protected by a password. Such a bug should not affect lots of people, but the few that encountered this bug may be the only ones using the Android proprietary backup service.

Android, source nKauscher/Flickr
Android, source nKauscher/Flickr

No one knows what is causing this bug to happen but some speculate it may be related to the KitKat crypto manager.

There is a simple workaround users can try: adbextractor is a tool that unpacks the archive and repacks it without using a password. A normal adb restore after this action should work and users should get their encrypted data back.

Apparently, the Android ADB backup service is far from perfect and needs a lot of work. Google is trying to solve problems, but they take a while, especially since Google has tons of projects to take care of at the same time. This particular bug now even bears a name: FutureRelease, which hints at a solution from Google itself.