yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] scott_doyland:
When I had the problem (in OP) I had connected to only WiFi networks that had visible SSID's.

Initially I connected to my home WiFi, all OK. Then I went on holiday and connected to a public WiFi in the hotel. That night I had battery drain on aeroplane mode (10-20% I think).

I didn't think such of it as phone was new so put it down as a one off.

Same issue once I got home and used home WiFi and then gym WiFi.

Narrowed issue down as described in my posts throughout this thread.

Hard to say what the real issue was especially as its not something easily tested. Some WiFi weirdness but apart from that its a mystery.

I'm not convinced I won't have the same issue at some point if I connect to another WiFi network other than home and gym but for now its OK.
[Moto G Q&A, Help & Troubleshooting] niekvans:
I too connected to home wifi (last night/morning) and then work wifi later in the day, so I'm curious to see what happens after tonight. Was your problem consistently reproducible? I.e., did it always happen after going on another wifi, or only sometimes?

You may be able to obtain more detailed driver information (e.g. about your battery and wifi components) through adb:

Google for: What's Android ADB shell 'dumpsys' tool and it's benefits?

By comparing before/after, you may find something standing out. But if you solved your issue fully with the factory reset, it's probably no longer helpful. Still, I would like to get to the bottom of this, because if we don't know what's causing this, it may simply return at some point, even after a factory reset.

E.g., some sample wifi information you can get that way:

Wi-Fi is enabled

Stay-awake conditions: 3

Internal state:

interface tiwlan0 runState=Running

SSID: XXXXXXX BSSID: xx:xx:xx:xx:xx:xx, MAC: xx:xx:xx:xx:xx:xx, Supplicant state: COMPLETED, RSSI: -60, Link speed: 54, Net ID: 2, security: 0, idStr: null

ipaddr 192.168.1.xxx gateway 192.168.x.x netmask 255.255.255.0 dns1 192.168.x.x dns2 8.8.8.8 DHCP server 192.168.x.x lease 604800 seconds

haveIpAddress=true, obtainingIpAddress=false, scanModeActive=false

lastSignalLevel=2, explicitlyDisabled=false

Latest scan results:

Locks acquired: 28 full, 0 scan

Locks released: 28 full, 0 scan

Locks held:

DUMP OF SERVICE wifi:

Wi-Fi is enabled

Stay-awake conditions: 0

Internal state:

current HSM state: ConnectedState

mLinkProperties InterfaceName: wlan0 LinkAddresses: [1.1.2.3/24 ] Routes: [0.0.0.0/0 -> 1.1.2.6,] DnsAddresses: [1.1.2.1,] HttpProxy: [ProxyProperties.mHost == null]

mWifiInfo SSID: Google, BSSID: 00:08:0a:02:03:08, MAC: 00:00:00:00:00:80, Supplicant state: COMPLETED, RSSI: -63, Link speed: 13, Net ID: 1, Explicit connect: true

mDhcpInfoInternal addr: 1.1.2.3/24 mRoutes: 0.0.0.0/0 -> 1.1.2.6 | dns: 1.1.2.6, dhcpServer: 1.1.2.6 leaseDuration: 7200

mNetworkInfo NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason:(unspecified), extra: (none), roaming: false, failover: false, isAvailable: true

mLastSignalLevel 3

mLastBssid 00:00:00:00:00:00

mLastNetworkId 1

mReconnectCount 0

mIsScanMode false

Supplicant status

bssid=00:00:00:00:00:00

ssid=Google

id=1

mode=station

pairwise_cipher=CCMP

group_cipher=CCMP

key_mgmt=WPA2-PSK

wpa_state=COMPLETED

ip_address=1.1.2.3

address=00:00:00:00:00:00
[Moto G Q&A, Help & Troubleshooting] scott_doyland:
My problem was reproducible.

Could reproduce on gym WiFi every time, ie get back on home wifi and battery drain happened. I did it three times on the trot.

What I don't know is if the drain started when I got home OR when I connect to to the gym WiFi as I was never there long enough to tell.

Then I factory reset after three issues (four issues inc time at hotel).

I'm technically competent to use ADB and test stuff etc (I'm a Unix sysadmin of over 10 years) but as you say its a bit late now. If it happens again i at well look into it further now that I know i can fix with a factory reset.

BTW I also tried deleting all WiFi networks before I reverted to a factory reset but that didn't work.
[Moto G Q&A, Help & Troubleshooting] snowboard:
I deactivated google search and now I get record time battery.

The downside is that on homescreen the google search bar remains up on top with a gray color.
[Moto G Q&A, Help & Troubleshooting] niekvans:
Just got OTA 4.4.2 (was 4.3): seems to have fixed it

Just a little update about my issue that I reported earlier. Nothing really has fixed it so far, and I didn't try a factory reset. I started imagining that maybe I was overreacting and that this sort of drain is 'normal'. However, last night, I got a notification that there was an update to 4.4.2, System version: "175.44.1.falcon_umts.Retail.en.DE" (Kernel version: "3.4.0-gc6fc9e1-00001g6ff871f hudsoncm@ilclbld23 #1 Mon Jan 13 04:48:46 CST 2014")

This has fixed the issue! All last week, I took screenshots every day of my battery usage after 10 hours, and the line was always sloping downward quite a bit (never horizontal), even when not doing anything. Now, the same graph (even after 10 hours) still shows a long horizontal line when not in use.

Now, this could also be because I obviously had to reboot the phone to install kitkat (and a reboot sometimes used to help, according to some). However, I was at home this morning on my own wifi, then to work and went on wifi there, now back home on my own wifi. Still everything works great (though I'm not sure it was related to that).

I also thought it might be related to a calibration issue of the battery. One peculiar thing that happened was that even though I installed the update this morning after charging it to 100%, after the required reboot, it was suddenly down to 48%. After plugging it back in however, it quickly "charged" back up to 100% in about 1 or 2 min.

Note the exact system version (and the recent date it was created, Jan 13) and let us know if anyone with this system version still has the battery issue, or if maybe they have fixed it.

---------- Post added at 01:03 AM ---------- Previous post was at 12:21 AM ----------

I looked around some more (based on the new system version), and found out that quite possibly this drain was caused by GPS. Apparently, after using GPS (even if done by the system), even just once, it would start draining battery. I suppose it wouldn't stop the GPS antenna circuitry or something after using it. You can find someone else complaining about it by searching for this: "Battery drain after using gps" posted by sineokiq:

"if I'm using the phone normaly with data conection, wifi always on etc, when the screen is off and the phone is in deep sleep in consums like a 1-5 mA ( 10 min scale). The problem cames when I use google maps GPS navigation, after I turn the apk off , turn the gps off etc, it consumes in stand by/deepsleep, 30-40mA ... if reboot the phone returns to normaly 1-5mA"

You can also find a huge thread in a German forum about the battery drain issue:

search for "moto-g-akku-laufzeit-probleme-diskussion-rund-um-den-akku"

People there also seem to hope that this new release will fix the "erhöhter Akkuverbrauch nach GPS Nutzung", which is apparently a well known bug in that forum.

So, let's see.. I hope the issue won't return in the coming days/weeks/years? ;)
[Moto G Q&A, Help & Troubleshooting] Mr.Scrooby:
Sounds great. Was your update from 4.3 to 4.4 or did you only update 4.4 to this new release? I have the French version. Does anyone see this particular kernel version elsewhere?

Regards
[Moto G Q&A, Help & Troubleshooting] niekvans:
I was on 4.3 still: never got an option to upgrade until yesterday. Even though I had manually checked for system updates every day, it always said I was up to date (with 4.3). So I never used another 4.4.

---------- Post added at 11:57 AM ---------- Previous post was at 11:36 AM ----------

By the way, from what I read on the German forums: if you are already on 4.4.2, you should also get this update to 175.44.1: the update will just be smaller (only 2MB).
[Moto G Q&A, Help & Troubleshooting] Mr.Scrooby:
Which german forum do you refer?
[Moto G Q&A, Help & Troubleshooting] niekvans:
Here's one article that refers to it:

google for: motorola-moto-g-erhaelt-bugfix-update-175-44-1-en-de

---------- Post added at 03:22 PM ---------- Previous post was at 03:15 PM ----------

And once again, there's no doubt that right now my phone has a *much* better battery life than before the update. The difference is night and day: when I just leave my phone on my desk not using it, the battery usage is completely flat. Maybe 1% every 4 hours or so, at most. Before the update, it would use like 5-10% easily in the same time frame. I just hope that the issue won't return, but I'm a bit more hopeful that they actually fixed it because even users already on 4.4.2 get this 'bugfix' update, so obviously they thought it was important or they wouldn't have gone through that trouble (though unfortunately I haven't seen any official confirmation from Motorola).
[Moto G Q&A, Help & Troubleshooting] eemgee:
well I hope the uk gets it soon. I'm losing around 2% a hour in airplane mode, and about the same just idle. I was losing nothing over night in airplane mode and around 1% a hour idle.
[Moto G Q&A, Help & Troubleshooting] niekvans:
What you can try for now as a temporary workaround (if you haven't received the update yet) is to switch off GPS, then reboot the phone (and don't switch GPS on again). Let me know if this 'fixes' it for you. Of course, the ultimate fix will be the 175.44.1, allowing you to use GPS again. I'm not sure this fix will work, but you can try.
[Moto G Q&A, Help & Troubleshooting] Mr.Scrooby:
That does the trick! But I hope to get the update soon because I need GPS to play ingress ;)
[Moto G Q&A, Help & Troubleshooting] theoneofgod:
I have 2G drain with my Moto G, maybe that could be your issue.
[Moto G Q&A, Help & Troubleshooting] niekvans:
Scrooby: glad that fixed it for you, for now! What you can try is run the Moto Care app in your phone, and ask Motorola in a chat (or call) about this new release, and if it will come to you soon (and while you're at it, you can ask them if that release indeed fixes this gps drain issue, as seems to be the case).

theoneofgod: your drain is probably not related, although you can try the same fix. However, it's not uncommon for different network settings to influence battery life, just because the radio transmitter in the device will use more power if it's further away from the base station. Potentially in your specific case, the 2G transmitter is further away or transmits with a weaker signal. However, I noticed you wrote you have good signal in 2G, so in that case it may be that you're constantly transmitting at least some data (check your data usage): with 2G, this will take longer, so the radio will stay on longer than with faster 3G, so using more battery. You can still try the GPS fix, as this is generally considered to be the real issue behind most people's battery drain.
[Moto G Q&A, Help & Troubleshooting] niekvans:
The following article also discusses the battery drain (including GPS fix) but it seems to be a more general Android issue, not just a Moto G issue:

http://www.android-user.de/Apps/Android-OS-verbraucht-viel-zu-viel-Akku-was-tun
[Moto G Q&A, Help & Troubleshooting] theoneofgod:
Thanks. I don't have data enabled.
[Moto G Q&A, Help & Troubleshooting] niekvans:
A quick update: my phone is still behaving well. However, I read in some German forum that certain users who got the same 175.44.1 update are still having the issue. This means the reason that I don't have it could just be down to luck (because the update reset something, similar to how the issue resolves for some people when they do a factory reset).

I attached two images, one on 4.3 where I had this issue, and another on 4.4.2 where I don't have the issue: even though I used more screen time on the 4.4.2, it used much less battery.

With the issue, I would never have horizontal stretches in my battery meter after 10 hours: they would always slope downwards quite a bit. With the issue solved, now I can have horizontal stretches in the graph (when the phone is on my desk and I don't use it), also after 10 hours.
[Moto G Q&A, Help & Troubleshooting] Mr.Scrooby:
Why should I use MotoCare? What does it do?

Today I spoke with the German support chat from Motorola. The guy told me (after quite a lot of explanation) that the 175 update only is for the german market and it does only fix the apk install issue. He did not could me say anything about updates for other versions.

Btw. does the factory reset from the settings format the cache? If you go into the boot menu you can do a factory reset and wipe the cache. Maybe it helps to wipe the cache. Thing is I don't like to do a factory reset just to try this out.

Regards
[Moto G Q&A, Help & Troubleshooting] niekvans:
Scrooby: did your disable-GPS-then-reboot fix still work after these days? About the cache, you can also reset that by just going to Storage -> Cached Data and then clean the cache. This could help, you can try it. I would do that and then a reboot for good measure.

What can also help is remove your google account. It's not a permanent solution of course (because you then don't get automatic backup, etc.), but you can give it a try: I have these tips from: http://www.android-user.de/Apps/Android-OS-verbraucht-viel-zu-viel-Akku-was-tun

It seems related to this bug: https://code.google.com/p/android/issues/detail?id=22878, although that one is closed, so Google is no longer looking at it. Maybe it's time to reopen it...
[Moto G Q&A, Help & Troubleshooting] Mr.Scrooby:
Fix is still working. Are you sure we are talking about the same cache? After wiping cache on my old phone Android does upgrade / optimise all apps.
[Moto G Q&A, Help & Troubleshooting] niekvans:
I'm not sure what the cache wipe does from the boot menu, but you can safely do it in the way I described (from the settings -> storage). But still, if that helps, it would probably only be a temporary fix (I wouldn't do a factory reset, because even if that fixes it, it will most likely only be temporary too).

So, the most 'permanent' way to fix it is just disable GPS I'm afraid. You can still get location from wifi/network. If you do GPS, just remember to disable it and reboot it afterwards :). But very good you told Motorola: I did the same. Hopefully, if they get enough reports, they will start investigating this (or more generally Google, as it could be a general Android issue, not a Moto G issue).

Good luck!
[Moto G Q&A, Help & Troubleshooting] scott_doyland:
Regarding cache - wiping cache from a custom recovery will wipe the /cache partition.

This is different from wiping app cache from the storage menu. This does NOT wipe /cache but just app cached data held in individual files generated by the apps - these files are NOT in /cache.

/cache is normally empty anyway. It holds the OTA files and a few log files and that's it.

Wiping dalvik cache via custom recovery (so not /cache or app cache) will force android to rebuild the dalvik cache for each app on reboot. This is when you get the 'apps optimising' message when you boot.

A factory reset wipes dalvik and /cache.

I haven't looked to see which cache (either dalvik or /cache or both) can be wiped from stock recovery or bootloader but it won't be app cache.
[Moto G Q&A, Help & Troubleshooting] Mr.Scrooby:
I think this issue is not necessarily related to GPS. I have the same problems when the wifi location is on. Only disabling location service helps with the battery draining problem. In this case the google service apps that are running in the background are closed aswell.

Another problem that I have observed: with play services 4.1 when I switch from GPS only to wifi location the service does not work, until I manualy stop the app (and it restarts automaticaly). With the stock version of the services I don't have this issue. Anyway, neither of the two versions help to save battery...

regards
[Moto G Q&A, Help & Troubleshooting] niekvans:
That's a very interesting observation. Maybe we should try to get a google engineer to look into this. It shouldn't be too hard to debug this, since it's quite easily reproducible, and even directly measurable (by hooking up the battery to a meter and checking how much current the phone draws, as a last resort). Also your statement about switching from GPS to wifi location should be easy to verify.

By the way, how do you know that the google play "service does not work"? I.e. what can you not do, when this service isn't working? I mean, I know this service is responsible for a whole bunch of things in Android, but what specifically makes you conclude that it doesn't work?

Removing the google account has also been reported to help (although that was in that more general Android OS drain article), which would suggest it has something to do with google's services, which your observations also seem to corroborate. They had issues with this before, and quite recently claimed to have fixed them: http://androidandme.com/2014/01/new...-includes-support-for-turn-based-multiplayer/

So, maybe they didn't fix them after all ;)
[Moto G Q&A, Help & Troubleshooting] niekvans:
Scrooby: did you try enabling only GPS, and not wifi location? (as suggested here: http://xdaforums.com/nexus-4/help/solution-to-google-services-android-t2385843)
[Moto G Q&A, Help & Troubleshooting] Mr.Scrooby:
I will try this and report back.

I notice that the service is not working when I switch back from GPS to wifi location I get no location fix in ingress. After I kill the service it works again.

So, looks like it is much better this way. In standby I now have about 1% an hour with wifi and 2G on. I'll do some testing with 3G to see if it is true what some people say that they have better battery with 3G.
[Moto G Q&A, Help & Troubleshooting] if0rg0t:
I voided the warranty and rooted my phone to confirm a similar observation, sigh.

See this: (Tricky battery drain problem) http://xdaforums.com/showthread.php?p=50467389

FYI, my wifi was off, and always scanning disabled.
[General Topics] jaceuk:
I own an MDA compact on t-mobile uk,

whilst on there homepage i saw a "update your MDA software"alert,

i downloaded the software and ran it.

the MDA then went off and when turned back ran a hard reset.

the MDA then runs thru the set up,when thats complete is shows a grey type screen with serail v1.02

its frozen on this screen and unuseable any effort to do anything makes a repeat cycle of the above

please help me turn my paperweight back into a pda

thank you very much

(i think im best sticking to a standard phone from here on in,im not techy enuff to have a pda.doh!)
[General Topics] virus247:
ur just in bootloader..go read wiki

u gotta press the reset,power and record camera btton together..thats wot i do for my 9090
[General Topics] jaceuk:
thank you very much for your help

its appreciated .

ill try that

thanks again friend.
[General Topics] oltp:
Jace,

the power & camera & soft-reset button will bring you in bootloader, just where you're now.

You'd better connect USB & run the update again. Something got broke the previous time, that's why you're in bootloader now.

Regards, M
[General Topics] jaceuk:
brill guys ta

only problem(sorry guys still learning)from the bootload screen the pc wont see the device is connected and if i try to run the device to get to a standard screen to sync it just reboots?

how do i actisync while in bootloader?

ta
[General Topics] oltp:
Jace pls don't try Act.sync. Run the update again :!:
[General Topics] jaceuk:
ive manged to get the pc to see the pda and ran it under a guest partnership,

once it had seent he pda, i re-ran the update,but each time it goes thru the motions then gives and error msg.

man im goin back to a normal handset next time
[General Topics] oltp:
What rom nr are you flashing? & what's the error message?

Cheers, M
[General Topics] jaceuk:
Thanks for all your help sorry to be such a pain.

i got the file from the tmobile uk site .

file name ma-tmuk-11300-128-11200

when connectiong its says

updating from

device ce image:1.13.00

device ext image:(this is blank)

deivce radio:1.12.00

up dating to

device ce image:1.13.00

device ext image:1.13.128

deivce radio:1.12.00

it runs thru then stops and says

error 101:connection error

thanks
[General Topics] jaceuk:
when booting up the bottom right shows

R 1.12.00

G t1337.42

D 1.13.00wwe
[General Topics] oltp:
Ok that's the 1.13WWE rom, which is available sine october last year. Should be a normal rom without problems. If you never updated before & still in your warranty period, return your device.

BTW have you rebooted your PC during your sequence off tries?

Guess your no pain, but you got bad luck in upgrading this time. You did the right steps to cure everything.

Cheers, M
[General Topics] jaceuk:
great thanks,

i have rebooted pc but ill do that then retry nothign to loose at this stage thanks mate
[General Topics] oltp:
Did you ever make a rom-dump of your working device? Otherwise you can try to make one now & do a SD-update.

Cheers, M
[General Topics] jaceuk:
no i didnt mate doh

ta for all your help mate appricated
[Java for Android App Development] krikor1:
I have google nexs 4, kitkat 4.4 updated to

I have debugger mode enabled

I try to reset abd from my eclipse i get

[2013-12-24 23:18:49 - DeviceMonitor] Adb connection Error:An existing connection was forcibly closed by the remote host

[2013-12-24 23:18:50 - DeviceMonitor] Connection attempts: 1

my device is detected by my computer..but when i try running application, my eclipse doesnt detect it?

please help
[Java for Android App Development] krikor1:
my project build target android 4.4

jdk compliance 1.6
[Java for Android App Development] krikor1:
minmiunm required sdk android 2.2 froyo chosen

target sdk: api 18

compile with: api 19 android 4.4 kitkat
[Java for Android App Development] krikor1:
so anyone?

my winbdows is windows 8
[Java for Android App Development] krikor1:
problem is not from device, because it works on windows 7...and another pc.
[Java for Android App Development] krikor1:
I also done this http://developer.android.com/sdk/win-usb.html#top
[Java for Android App Development] SimplicityApks:
Hi

Are you sure you have ADB set up properly? You may want to get to know ADB here. At least run the devices command to see where the problem is. What you should try is restarting both Windows and your phone (we all know windows...). If that doesn't work you'll want to try a different USB cable and socket but as you are saying the device is detected by windows so the hardware shouldn't be a problem. A complete reinstall of eclipse may be needed as well.

There is an edit button so no need to post 5! times.
[Java for Android App Development] krikor1:
i fixed it by updating driver software in device managers..and selecting the google usb driver location i donwloaded via the sdk manager

thanks
[Java for Android App Development] SimplicityApks:
Great! Have fun developing!
[AT&T, Rogers HTC One X, Telstra One XL] beppomarx:
As I try and get the identifier token from my evita, it keeps changing...

I am attempting to unlock again from htcdev (currently relocked) and ive tried 3 times already. I get the unlock_code.bin and go to unlock it, hit confirm on my phone and it reboots and i am still locked. Like right now i am in fastboot and type "fastboot oem get_identifier_token and get the code. then i can type it again 2 seconds later and I have a different token. iys like it is being randomly generated. any ideas?