yashsingh1/xdaforums huggingface dataset:
[Moto X General] rmead01:
Yeah, having used to work for one that's the general statement when people ask what a ceritifed preowned device is. When they are this new he's most likely right, but down the road don't let it fool you. They are the same devices they used to call FRU's (field replacement units) that were reworked and sent into the stores.

I have a friend that I go to at ATT consistently. I told him I lost root and was hoping to swap for a non updated model. He said the same thing, outside of 14 days and there's really nothing at the store they can do.
[Moto X General] jayboyyyy:
while this is off the topic of this thread so ill keep it short. Basically the verizon reps are told that refurb phones are not what verizon sells as certified preowned. They say that certified preowned are just that. preowned devices that were returned but not for faulty units. Faulty units get sent to Motorola under the manufacturers warranty. That being said the rep did say that is what they are told, that doesn't necessarily mean that is what always happens. I saw this listed on other forums that Vzw reps have said the same to others so I got no idea but I definitely am weary of that fact. Further, I don't really think there are many manufacturing problems with the x besides this battery drain so a certified preowned is fine with me if it fixes the battery drain.
[Moto X General] rmead01:
yeah, sorry for the OT. I used to be one of those reps. Early in device life they are generally new. But there's no way for a person to tell it's it's remanufactured or a "like new" replacement. People saw the words "remanufactured" and it was a negative thing. "Certified pre-owned" went much better in regards to customers trusting what was handed to them.
[Moto X General] Rask40:
Newer phone, seemingly better performance.
[Moto X General] ranick01:
I easily get 5+ screen time. Battery rocks.

I used GPS for a 3 hour road trip, 3 hours screen time, and still had 30% or so battery left.
[Moto X General] scottshebs:
can someone help me figure out why my battery life isn't too good?
[Moto X General] Turb0wned:
The battery on my GSM DE is much better than my tmobile version was somehow..
[Moto X General] razattitude:
im satisfied with my battery. thanks to greenify.
[Moto X General] phositadc:
Any idea why? Does better battery stats show any differences between the two?

Sent from my XT1053
[Moto X General] jayboyyyy:
it would help osting kernal wakelocks and partial wakelocks but it looks like you were in a place with terrible cell reception to me. Like terrible. Basically 0 cell reception and it searched like a mofo the entire time looking for one. that will kill a phone real fast like.
[Moto X General] rman18:
Is this a joke? You had no signal for 11 hours straight, that will rape your battery. :eek:
[Moto X General] scottshebs:
how can I go about this? there shouldn't be any reason why I have no reception in my area.
[Moto X General] jayboyyyy:
well either you are wrong and there is a reason. you have the most FUBARed moto x they have sent to anyone. Or you flashed some different firmware on your phone than the stock firmware and it has incompatible radios.
[Moto X General] scottshebs:
besides tweaking around with nav bar and quick settings tiles this is stock. is there anything that could be causing it to search for signal the entire time my phone is on?
[Moto X General] jayboyyyy:
did you take an update or try to do something else weird. I mean your phone is searching for a signal because it doesn't have one. Are you in the devils dungeon? Do you have some app that turned data off that you don't know about? IDK man, but it isn't that difficult to diagnose. I mean if you haven't done anything to the fun then you must just be somewhere with bad cell reception lol. If you think you are not in the devils dungeon, and you actually have only done nav bar tweaking and some other stuff... then undo all of the tweaking you have done see if it helps, when that doesn't work return the phone. But since you are the first person ever to have this problem, I'd bet it is something you did, downloaded, or you are in a dungeon or maybe someone was running something that shut cell service off where you are working/going to school/ or lounging around playing Halo.
[Moto X General] hermeshhn:
Having a bad signal even if the phone is on 2g affect the battery?

Enviado desde mi XT1058 usando Tapatalk now Free
[Moto X General] ranick01:
Yes, your phone will be constantly searching for a cell signal. Data speeds have nothing to do with it. It is all about cell reception. If you go in an area without any signal you should turn to airplane mode to prevent this
[Moto X General] Bilhouse:
Since last weeks update on the AT&T variant, my idle battery drain problems have now completely gone. I have been getting over two days usage with 3-4 hours screen on time. I managed to get 45 hours with over 5 hours screen on time and yesterday I got just over 52 hours with around 3 hours 50 minutes screen on time. Im very happy with the Moto X now as that was my only issue with it.
[Moto X General] rmead01:
Are you running completely default with all options on? I'm guessing you aren't rooted but I disabled A LOT of apps and i'm wondering if I don't have to and can take advantage of a few extra features without battery impact.
[Moto X General] Bilhouse:
Hi. Im completely stock and unrooted.
[Moto X General] phositadc:
With no apps disabled? Could you post some battery screenshots? Curious to see where your android OS usage is at.

Sent from my XT1053
[Moto X General] jayboyyyy:
also when you say stock does could you be more explicit. Do you have google location services on or what location services do you have on? gps/BT/wifi? Also if you are using any apps that sometimes are rough battery drainers please list those like FB, email, anything that syns a lot basically. It would be much appreciated sir.
[Moto X General] Shade21:
Much better than what I've had before and with my personal typical usage. Some bad cell area... Damn small towns

-Sent from my Moto X
[Moto X General] Bilhouse:
The only apps I have disabled are the AT&T ones since I'm in the UK and Quickoffice since I have Quickoffice Pro. Android OS usage tends to sit around 15-20% most of the time.

---------- Post added at 12:11 AM ---------- Previous post was at 12:08 AM ----------

No location services or GPS on at all. Most of the time with WiFi on as well as 3G. No LTE since the UK uses different bands that are incompatible with the Moto X. Gmail and Whatsapp syncing only. No BT. Brightness around 30-35%.
[Moto X General] theraffman:
My battery has gotten significantly better since the ota... I posted earlier in the thread about it, but no one responded. Android os has been consistently 10-13% since the update vs 20+% before the update.
[Moto X General] Kev1000000:
Add me to this list of Android OS being abnormally high...

http://i.imgur.com/i9a3Btm.png
[Moto X General] MajorTankz:
What happens over ~1 hour of screen off time.

Wifi on:

Wifi off:
[Moto X General] Julianocas:
Damm you battery...
[Moto X General] ram130:
So I'm guessing Android OS being high is not a bug? Well according to Moto. Its normal since we still get their estimate usage. Anyways I'm done troubleshooting.
[Moto X General] jayboyyyy:
I had similar problems. My qcom_rx_wakelock was out of control. Some people just had issues with a particular router at their house or work and when they weren't connected to that router they didn't have any battery drain issues. I had battery drain issues when on wifi and when not on wifi. basically the qcom_rx_wakelock disappears when you are not on wifi like yours did but then the new wakelock that replaces it when using cell services was still out of control for me. I returned the phone and it seems to be under control more but I have been able to test it for multiple days so don't quote me on that. Since yours seems to deccrease when you take it off wifi, maybe your problem is just the router you are connected to. Some people would change the router, change the band, or change the channel and it sometimes fixed the problem. If you start getting just as heavy of kernal locks when you are off wifi as when you are on wifi then perhaps you faulty device. Otherwise, many phones across android have this router problem. Don't know why but they do.

Yes, I have been trying to tell people that for awhile. Mainly because "high" is just relative. But just because of this does not mean that your particular android os might not be higher than it should be. I had high android OS and returned the phone but that was because I was getting 2% battery drain in idle do to something crazy that I couldn't figure out for two weeks. If your battery drain is less than .7% per hour when in idle (you must run a long enough test obviously, merely 4 hours might give inaccurate results) then who cares how high android OS is? I sure wouldn't. Barbie Dolls Dancing could be the highest battery drainer if I was getting only 4% battery loss over an 8 hour period. Also, we have to remember that no one knows what google decided to throw under the Android OS umbrella. I think people freaked out about it because previous Android OS's didn't have high android OS usage but it seems the newer realeases do. This could be caused merely because of what google decided to report as android OS usage. that is all.
[Moto X General] Kev1000000:
It is a bug. Something in the kernel is not letting the device sleep. Motorola claims 10 days of standby time. I don't think anyone with Android OS being high will get anywhere near that time on standby.

My guess is something to do with the wifi driver, but this IS a bug of some sort.
[Moto X General] jayboyyyy:
just curious. do you have any idea if the "stand by time" that phone companies report is a stand by time when the phone is actually in stand by? Meaning that they know how much battery the phone uses when in stand by (not including when things screw up kernels wake the phone up or partial wakelocks) then do an estimation of how long that is based on the usage or pull from the battery in that state? Clearly they don't think it will do that because they only advertised it as a full 24 hour use phone. If the phone actually could go 30 days in standby then the average user (using the screen prob 2.5 hours a day would get like 4 days use (obviously an extremely rough estimate). I would predict the marketed stand by time is manipulated in some way so that they can say it is 30 days.
[Moto X General] Kev1000000:
Sorry, it's actually 10 days that Moto claims.

Either way, my Moto X is reporting that it is being held awake by Android OS. This is a bug. It's not touchless controls, it's not active notifications, it's not Moto Assist.

If we had CM 10.2 available, it would be very interesting to see if Android OS was high with that ROM/Kernel combo.
[Moto X General] rmead01:
People need to stop reading into the standby times that any phone mfg posts. They are ridiculous. But if you really want to test...

factory reset the phone-setup and turn everything off-put into airplane mode - This would be how to achieve the standby time they are describing. perfect conditions with nothing running.

for comparison, iphone standby time is like 250 hours. When was the last time you saw an iphone last 10 days either? you don't..
[Moto X General] Kev1000000:
Standby time aside, the Moto X ROM has a bug... This isn't "normal" nor "acceptable."

http://imgur.com/6iWEcIg
[Moto X General] rmead01:
I'm facing the same thing as every other user here. But when it comes down to it last weekend I had 1 day 10 hours off charger. That's sat morning until Sun night. Had 3 hours 45 min SOT and 14% left when I plugged it in. Android OS was second highest if not first, can't remember.

Regardless of what it is reporting, the batt life is still better than 90% of the other devices on the market.
[Moto X General] Kev1000000:
Imagine how much better it would be if this bug was fixed. Just because it's better than your older device, doesn't mean this bug should be left untouched. There is some great potential here for this phone to get pretty amazing battery life, not just "good."
[Moto X General] rmead01:
Everyone keeps saying "it's a bug" but no bug has even been found. It could be as simple as a calculation is off a decimal (which has happened GS3 AHEM) and is falsly reporting the system usage. Until someone can even find a bug to discuss it's all kinda redundant.

Even with my android usage that high, my wakelock detector tells me my phone is in deep sleep about 95% of the time.

If you really want to test it, install wakelock detector. Charge your phone to full, take if off charge and try not to use it for a few hours. Then look at how high the system usage is and what % of time the phone was in deep sleep. Let's start seeing some actual screenshots instead of all this finger pointing with assumptions.
[Moto X General] Kev1000000:
Look at my screenshot above. In just over an hour, I lost 6% battery SOC. Look at what consumed the most of that battery... Android OS.

This is not a calculation error.
[Moto X General] rmead01:
For isntance, this is updated OTA unrooted, everything running. Wifi/google now/gps/nothing frozen.

---------- Post added at 11:24 AM ---------- Previous post was at 11:22 AM ----------

But you are telling me this is because the OS is holding a wakelock, which it isn't.

Also want to add what I've mentioned before. It seems like the Moto X has a much more stable curve than other devices. When actually in use the batt drop isn't as drastic as other devices. I'm wondering if it's actually reporting a truer batt life. Comparing to my N4, it would have a near flatline idle drain which was great but when I turned on the display and did something as simple as look at a gallery picture, the drop would be much more substantial. Sometimes I couldn't even load XDA or reddit without dropping 2-3% for only using it for a minute.

My thought is that is because the battery is calculating better on overall use and not instantaneous use. Something along those lines.
[Moto X General] MajorTankz:
You're only looking at partial wakelocks not kernel wakelocks...
[Moto X General] phositadc:
Fwiw better battery stats for me reports 98% deep sleep overnight but I STILL lose 1% or more per hour. And android OS is at the top of the list in settings.

So it may not technically be a "wake lock" that is reported in better battery stats, but losing that much per hour when the phone is supposedly deep sleeping is definitely concerning.

Sent from my XT1053
[Moto X General] rmead01:
Here are the kernel wake locks.
[Moto X General] jayboyyyy:
I think pointing out the Android OS uses a lot of power seems kind of silly until some engineer says they found a problem. With some posts above I notice your signal was two bars which drains the battery way more than anything else. That could be the explanation. The phone is searching is hard as it can to get a signal. But beyond all of that, pointing out that Android OS usage is high means you must be comparing it something right? So what are you comparing it to exactly? I hope it is a phone with hardware and processors set up like the moto x (the only phones that compare are the Droid lines). Clearly everyone here knows that we have different low power processors doing different things. It also seems clear that people think by turning off active notifications and touchless control that it would turn the phone back into how a normal phones processors work. Do we know that those processors are only running if those apps are running? I don't know that personally. But all that is just said to bring up the fact that comparing how the Moto X uses the Android OS to how a phone that we designed and engineered to run the Android OS differently, doesn't seem like the best idea to me. Motorola doesn't seemed surprised that the usage is that high, most likely because they know exactly why it is that high. They aren't speculating and guessing and comparing it to the Nexus like we are because they actually know. So maybe there is a bug maybe there isn't but no one seems to have a true idea and our attempt to diagnose it seems very poor.
[Moto X General] Kev1000000:
PowerManagerService is keeping your device awake. As is mine. The question is... why?
[Moto X General] rmead01:
But my device isn't awake at all. Look at the % at the top. I wonder if some of this power is coming from the low power cores that don't sleep like the main 2. That would go along the lines of android OS being higher because it's constantly running, just on a must lower freq core that is practically idle.
[Moto X General] Kev1000000:
Those separate processors are designed specifically to keep the main CPU asleep, not awake. If the low power processors were keeping our devices awake, and Android OS high, it would go against the entire reason for them to exist.

Also, not everyone seems to have high Android OS use. Some people claim after returning their device and receiving a new one, the problem went away.

Something is going on. I find it extremely hard to believe that > 2% per hour idle drain is by design.
[Moto X General] jayboyyyy:
I completely agree with 2% statement. I also returned my phone for a new one and it seems it may have better battery life but Im not going to say that yet. Also, those people I saw that returned there phone and got better usage never said the Android OS got better just that their phone stopped losing 2% per hour in idle (at least that is what I thought). And sometimes their is a placebo affect where you get a new device pull it out and think it is working better than your old one. I never saw wakelock or partial wakelock comparisons between someones old device and then their new device.

Also, that would mean there is a hardware issue if the returning the device thing were true, not a bug to fix...

Finally, the low power processors are there to save battery life and be able to do what they are doing. If the main CPU did what they were doing then it would drain battery massively. That means that what ever they are doing, phones with normal set ups are not doing that because they would drain the battery to drastically. This does not mean they are saving battery life. This means they are using more battery life than a normal phone, but they have just reduced it to such minimal levels that they didn't believe it would affect the device in the long run.

Normal phone you must wake up to see whats going on, our phone has active notifications. Android OS might show high usage on our phone because of this, where as another phone might have lower OS usage because it uses battery when you unlock it to wake it up. So if that scenario were true, you might see a moto x with high OS usage but it could burn through less battery than a normal phone that has lower Android OS usage but you woke up so many times to check things that the screen time or something else is now the main power user. Get what I'm saying when I say it is difficult to compare the phone to other phones. I'm not sure how everything works but unless you are it seems difficult to compare.

Ill report back on my phone that I returned in comparison to the phone I have now. Saved screen shots from the previous phone and am letting this one settle in before I start running tests. It does seem my qcom_rx_wakelock that I was having before has drastically reduced, but too early to tell IMHO.
[Moto X General] bugsy:
Just a general comment about battery drain from my experience. I was getting decent battery life, but nothing compared to what others were seeing. I finally decided to hard reset and it has made a dramatic difference and I even have some additional services turned on that I had turned off prior to the hard reset, most notably the location services for google now. Everything is setup the same and it is a night and day difference. The only real difference is that I did not do the migrate from an old phone like I did when I first set it up. My gut feel is that the migrate process is messing something up, but I only have my before and after experience to back that up.
[Moto X General] rmead01:
I also haven't done any migrate. Original setup or hard reset
[Moto X General] jayboyyyy:
So that is an interesting observation. I did many factory resets but used moto migrate each time that I did them. When I just received my new phone this time I didn't use moto migrate and just manually moved everything. Perhaps that was the underlying reason the entire time and I didn't need to return my phone. Wish I had seen this a few days ago and I would have tried it out to see if I could confirm this. that sucks. It would have been a great test because my phone was draining 2% per hour consistently for a couple weeks in standby.
[Moto X General] ram130:
Damn. That's insane. I suggest a reset. Or try clearing data from Play Services, Network Location(both) and reboot. Yours is abnormal as hell.

How did you do that hard reset? By settings or recovery?

Only I did when I got my phone was restore app data via helium.
[Moto X General] MajorTankz:
PowerManagerService is supposed to be a collection of partial wakelocks from what BBS says. bam_dmux has something to do with bluetooth.

Even though i have bluetooth turned off, I see bluetooth related activity regularly when I look at my logcat through ADB with my screen off.
[Moto X General] ram130:
So how much is your drain now per hour?
[Moto X General] bugsy:
I did it via settings, 3 times and then set it up from scratch. Pain in the butt to set everything up again, but it seems to have been worth it.
[Moto X General] jayboyyyy:
so idk about the BT stuff because I enver use it and have it frozen. But with my old phone I would have severe kernal wake lock called qcom_rx_wakelock with the wifi on. If i turned the wifi off I would get a different kernal wakelock (just as bad battery drain) but it was labled the bam_dmux. Not sure BBS has got it right when it comes to it being a BT thing because it seemed to be a data related thing to me. ubt perhaps Im wrong, just sharing my experience.

---------- Post added at 03:01 PM ---------- Previous post was at 02:56 PM ----------

well im on my first full day of use with it right now and so I don't really want to give a definitive answer because certain things are happening with the phone as it settles and gets things working appropriately. I like getting my configuration and apps and everything up and running. Do a dalvik-cache wipe. wait for two days or three days then do another wipe. Let it set for another day or something like that, then start running battery tests. But for now, I think my drain was around 1% in idle last night but some back up services were running that I saw. Today Im at 2% per hour but I'm texting with mighty text and have bad cell service so its not a good benchmark. I probably wont be able to give a full report back until next week because I got wedding stuff al weekend and will be too drunk to remember to do all the bbs stuff.
[Moto X General] ram130:
Ok thanks. Keep us posted.
[Moto X General] rmead01:
Are you clearing dalvik cache with root on your device? Trying to find a way to clear it without root.
[Moto X General] sh0ebox:
Had my VZW DE for about a week now, and this is typically what I see for my battery usage. It seems subpar from what I expected based on reviews and raves about excellent battery life. What do you guys think? Is this normal? Did I set my expectations too high, or is my battery life not as good as it should be?
[Moto X General] ram130:
That's low. Compared to me 15hr on battery with 3 hr screen on time. And 30% left.
[Moto X General] sh0ebox:
That's pretty much what I figured. Wonder what could be causing the battery life to be lackluster. I came from iOS so I didn't migrate anything over... basically started from scratch. Not rooted and bootloader is not unlocked yet. Any ideas/suggestions on things to try?
[Moto X General] ram130:
Do a factory reset. 3 times. Set up again. Also disable Location reporting in the Google Settings app
[Moto X General] mickeyd1488:
well i learned my lesson about leaving WiFi on when there's no WiFi to use....