GoMo experiences battery drain issues with Moto G update

We need to install some serious tools after KiTKat 4.4.4 upgrade

battery probs with moto g after update

Initially, here at GoMo Towers we were over the moon [joyous] when our loan Moto G from Motorola received the message that an update existed that would take this iconic smartphone up to the very latest version of the Android mobile OS – v4.4 KitKat.  We’d hoped for significant improvements and in one sense we weren’t disappointed. We really like the Updated Phone dialler. However, the downside was that the poor little Moto G’s processor almost went into meltdown mode (literally). The handset got very hot an battery life dropped sub 12 hours. So we got in touch with Motorola.

In terms of usability, the updated Phone dialler with its new graphical layout and colours is a vast improvement.

But something has to be done about the low battery life because the upgrade to v 4.4.4 is irreversiable. Hence we’ve got to find a fix.

Luckily, Motorola came back to us (as a regular Moto G owner) very swiftly indeed and with very detailed suggestions.

Now we’ve decided to print Motorola’s official advice in full below and it is very much along the sames lines that we ourselves were thinking. Namely, the handset is running too many third party apps.

Now, it would be possible to start disabling or completely uninstalling some of the suspected third party apps.

However, Motorola suggested starting the handset in ‘Safe’ mode – just like on a Windows based PC.

Safe mode would disable all the third party apps automatically. So if the handset stops overheating and battery life recovers – then that’s very definitely the problem.

We’ve followed the advice and so far the handset hasn’t even got warm let alone hot and battery life looks like it has recovered.

But what’s the point of having a really neat smartphone like the Moto G if you aren’t running brill apps on it?

Now there is one place where you can look to get a clue as to what may be causing the problem.  That’s by looking at data usage.

We do this by tapping on the network signal icon in the top right of the Moto G’s screen twice. It’s the fastest way.

But what we really need to do is run a tool which indicates which apps are consuming the most processing power. And cut down the number of them doing so.

Sadly, we suspect is Scoopshot – the app which authenticates the handset’s time, date and location so you can sell your photos to the newspapers.

We’ll let you know the results of our investigations later.

Meanwhile, here’s what Motorola said ….

Start the phone up in Safe Mode by pressing the power key then pressing and holding on Power Off, you will then be asked if you want to start the phone up in Safe mode, select OK.

Safe mode temporarily disables all 3rd party applications so you can not see them – they have not been deleted.

Use the phone in Safe mode without starting or installing any 3rd party apps for 24 hours to see if the issue persists.

If the issues persists after having the phone in Safe Mode then you will need to perform a reset.

Factory Data Reset is a tool used to remove everything that was imported, added or installed on the device. The reset does not affect the contents of your SIM.

Keep in mind, when using this feature everything is deleted. This includes all Messages (SMS, MMS and Emails), contacts and 3rd party apps.

Also, multimedia files that are stored in the internal memory might be removed. Due to this, we recommend that you backup your data.”

About Tony Dennis

Tony is currently Editor of GoMobile News. He's a veteran telecoms journalist who has previously worked for major printed and online titles. Follow him on Twitter @GoMoTweet.
This article was published in Mobile Devices, Mobile OS, Motorola, hardware clinic, mobile news and tagged , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>