yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Lost Dog:
Horrible battery life

I know the batter life on this phone is not the greatest but recently (somewhere in the CM11 nightly builds) it's really gone down hill. I've noticed only a few hours life on minimal usage and it's to the point where if I'm using the phone with it plugged in the I occasionally will even lose charge depending on what I'm doing. When not plugged in the phone will often get very hot.

This is stock CM11 using dalvik and not ART. One thing I noticed this evening is going in to performance/processor and looking at the Current CPU frequency, on any CPU governor (except POWRSAVE) the frequency will rapidly jump from 350 MHz to 700 MHz to 1200 MHz and will often just bounce between 920 MHz and 1200 MHz for long periods of time.

Something is causing the phone to stay at maximum performance causing it to get very hot and drain the battery.

Can anyone else confirm? Right now I'm on the 11-20140203-nightly and seeing this behavior but it's happened for several weeks now...
[Samsung Galaxy Nexus] PCWright86:
I am experiencing the same problem. With sync off, location off, and data off. I will lose 10% in about 10-15 minutes. Noticed the CPU frequency thing today. Tried using multiple different kernels to no avail.

Beamed from a KitKat injected with with Franco goodness
[Samsung Galaxy Nexus] Meticode:
Maybe download Greenify and see if any app is doing it specifically?
[Samsung Galaxy Nexus] .SoFLy.:
I dirty flashed the 2-03 nightly with klobkelosh's rollback.zip (wasn't sure if the bionic fix was built in yet or not).

Compared to the previous nightlies with the bionic bug, this ROM is great. Getting strong 4G where I should be, and the switching/hand offs seem slick. Battery life also seems better.

Anyone having issues with the signal or it heating up an losing battery, I'd try flashing the 2-03 or 2-04 nightly to see how it works. Thanks again klobkelosh for catching this bug. Nice to have my data back :)
[Samsung Galaxy Nexus] jrk190:
I'm using the latest nightly, It's pretty nice!
[Samsung Galaxy Nexus] ulnevrwalkalone:
I flashed the 02-04 nightly and it seems better but not perfect. My LTE signal works but it is inconsistent. If I manually turn off and then turn back on my mobile data it seems to start working again. I will keep playing with it so see if there is any rhyme or reason to the connection issue.

FYI: This was a dirty flash, have not tried a clean install
[Samsung Galaxy Nexus] dm47:
dirty flashed 02/05 + rollback.zip and its running great so far. No 4G issues yet
[Samsung Galaxy Nexus] Big ZD:
I'm just really hoping they get it fixed (not requiring a roll back zip) prior to M3 coming up in the next couple days. I'm on the installer updates. I want my 4G back, but don't want to mess with my generally solid updates which tend to to be quite particular.

EDIT: I've been watching the change logs...they have the fix, and its source....just fix it already(says the guy who doesn't know how)!!!
[Samsung Galaxy Nexus] odmejia:
I am wanting to switch over to CM11.. Are you doing this all at once? Flash 02/05, Gapps, Rollback.zip? Anyone using mpokang with this rom? Thanks in advance
[Samsung Galaxy Nexus] klobkelosh:
Yup, that's it. I've used mpo's anykernel formats on this
[Samsung Galaxy Nexus] dm47:
Yep. But no need to flash Gapps again if you're dirty flashing

Has anyone seen noticeable battery life difference with a given kernel? Sometimes I feel like it's just placebo...
[Samsung Galaxy Nexus] klobkelosh:
No need to flash gapps if he's updating a cm build, but do flash gapps on your first dive into cm11.

Yes, I have seen dramatic battery life difference on custom kernels, properly tuned, versus stock.
[Samsung Galaxy Nexus] jguerdat:
The 20140205 ROM is working for me without the backdate zip. Prior to this, I had to use the backdate to get cell data of any kind.
[Samsung Galaxy Nexus] jguerdat:
Crap. Guess my luck had to do with me not changing cell towers or similar. Out and about today and lost data as before. Merging the backdate once again fixed it.
[Samsung Galaxy Nexus] kspanks04:
hacked hotspotting?

Can anyone confirm that WiFi tethering works with Verizon plans that aren't setup for it?
[Samsung Galaxy Nexus] Lost Dog:
Yes it does. I do it all the time.
[Samsung Galaxy Nexus] klobkelosh:
Looks like snapshot m3 is live. Does data work correctly?
[Samsung Galaxy Nexus] Shadow Death:
I'm about to find out. The last nightly that I got from this thread had better data handling than the stock 4.2.2 rom that my Gnex had the other day.
[Samsung Galaxy Nexus] Merman1983:
So any word on this? I mean I've made a Nandroid and updated my TiBu backups and downloaded the snapshot, but it would be nice to know if the data issues (or other issues) are present.
[Samsung Galaxy Nexus] peterlemonjello:
Any info on M3 and data hand off?
[Samsung Galaxy Nexus] jguerdat:
The change log Indicates a rollback for bionic which seems to be the one in question. I've loaded it up but haven't had a chance to test it. Fingers and toes crossed!
[Samsung Galaxy Nexus] Shadow Death:
It's running fine for me so far. I'm having occasional data connect issues but I'm not sure if that's related to the location or not. I came over from a different phone which had stronger radios than this but not by much.

Edit: SwiftKey is officially garbage now. I had to edit and correct so much stuff.
[Samsung Galaxy Nexus] jguerdat:
Nope. Just got back from a short run and data is still hosed. Reflashed the backdate again...

Edit: switched to 3g and no data connection. 4g/LTE works fine.

Edit of the edit: just spent an hour or so swapping ROMs, adding the backdate flash and switching between 3g and 4g and get the exact same issue every time. I know the older Roms worked fine with the backdate it switching connections causes the same problem every time. Maybe more time is needed when switching to 3g is needed to get a data connection for some reason? So, I'm back to the snapshot to give me some time to see what works and what fails over time rather than trying to force it.
[Samsung Galaxy Nexus] General Crespin:
Opposite for me, 4G doesn't work at all, only 3G. If I switch the mode to LTE it never gets data at all.

Not too relevant but this finally pushed me over the edge. Ordered a Moto X. It's been fun.
[Samsung Galaxy Nexus] Shadow Death:
I think that you may regret ordering that might x. Its just too small in my opinion. I've been on M3 since its release yesterday and I haven't had too many issues. Data can be a pain to get to connect at first but after it does connect it stays for me.
[Samsung Galaxy Nexus] JPorter900:
I've been having trouble getting the phone to charge on the latest nightlies (2/08 at the moment). Occasionally I can get it to start charging after a while bit usually I have to power the phone down to get it to charge. Anyone else having this problem?
[Samsung Galaxy Nexus] webeougher:
Did you revert back to a rom where charging worked properly before to make sure it's not your charging port? I've never heard of that being a rom issue before, but I have had to replace two charging ports on my GNex.
[Samsung Galaxy Nexus] klobkelosh:
Data appears to be working on m3 without the rollback zip
[Samsung Galaxy Nexus] Shadow Death:
I'm seeing crazy fast battery drain with M3

I didn't notice until I took the phone with me to work today. 6 hours it went from 99% to 6%
[Samsung Galaxy Nexus] jrk190:
I'm on M3, going to test the battery on My Toro and Friend's Toroplus. I haven't noticed bad battery.
[Samsung Galaxy Nexus] Shadow Death:
I may have a bad battery then. I'm on the official aokp right now and my phone is at 95% after being off the charter for a few minutes.
[Samsung Galaxy Nexus] jguerdat:
No battery problems here, either. However, I can't use cell data without losing all data, regardless of using the backdate or not with M3. I can force it back by switching between 3g and 4g but I have to do that every time I lose data while running around town. When it works I get data on both 3g and 4g but when it fails I have to toggle. Not sure if toggling airplane mode would work.
[Samsung Galaxy Nexus] jrk190:
I had a bit of a battery drain, but I can't tell with my new battery...
[Samsung Galaxy Nexus] Big ZD:
Did you ever change the prl settings using the phone dialer? Just curious...
[Samsung Galaxy Nexus] jguerdat:
Nope, don't even know what that is or how to do it...
[Samsung Galaxy Nexus] benjewman:
so i'm running cm 11 snapshot m2 on the stock kernel and i am having horrible battery life. today for example, i have 47 mins 52 s of screen on time out of 14 hrs with barely any use, some light music listening mostly is what i do. i had wifi off all dya but the radios were on the whole time. ive checked all running apps but cant find the culprit which leads to me to think i cant find it at all or it is the rom. anyone have any idea whats up?
[Samsung Galaxy Nexus] EvanVanVan:
I was having a very similar issue since yesterday after flashing the 2/07 nightly... It *seems* to be better after wiping /system and then flashing 2/11. A couple other things I noticed were all of a sudden my lock screen would constantly open in landscape mode (when it used to be locked to portrait orientation) and when making calls it would start with the speaker phone on. Have you noticed anything like that?

Although just now, opening up root explorer to check which nighties I had flashed, the charging seemed to stop (the circle battery indicator was no longer spinning) and I had to back out of root explorer and put the phone down for charging to resume. So it's definitely working better than it was this morning, but not perfect yet. Since putting the phone down seemed to help I'm not sure if it is if fact rom related, or the USB charging port...but I did just replace my USB charging port a couple months ago after having similar issues, so I know it's a new port at least...
[Samsung Galaxy Nexus] domenci:
Being connected to LTE instead of WiFi can kill the battery pretty quick... you never said what percentage you were at after those 14 hours but that doesn't seem too bad for this phone if you still had 10-20% left
[Samsung Galaxy Nexus] benjewman:
sorry i forgot that part. those times i stated were after 2 full batteries. and i am on lte but the wifi radios stay on even when i have manually shut off the radios and as many services as i can
[Samsung Galaxy Nexus] Yianaki:
Galaxy Nexus KitKat 4.4 Data handoff issues Try ForkMyLife

The latest Fork My Life is working fine handing off data. 4g itself seems more reliable in general. After doing a Titanium backup in Cyanogen, wiping and doing a Titanium Restore everything good.

Fork My Life is a KitKat Rom based off OmniRom (haven't tried OmniRom).

I tried Cyanogen milestone 3 and nightlys and was having data handoff issues.

Same handoff issues with LiquidRom.

Otherwise all they are great.

Where I work it is better to manually force 3g because LTE is even slower. Every other KitKat rom has had handoff issues.

Was going Nuts and I think I found a solution in above. Don't know about general stability just flashed it.
[Samsung Galaxy Nexus] domenci:
No offense to that developer, but I saw a lot of evidence in the thread that he's a pretty new developer, many questions where he just doesn't have an explanation to what's happening. I had a lot of random reboots on that ROM as well as the data problems that he'd say the fixes were merged then weren't merged, going to be merged, etc, lots of inconsitensies. I liked some of the features, but for a DD it's just not there. Official CM11 (just flashing the ROM and Gapps) hasn't let me down yet (no crashes at all), and I haven't had the data issues since the 2/07 build that others seem to have.
[Samsung Galaxy Nexus] robbnsade:
Had an issue like this on my rezound and it was the port making contact somehow and the phone thinking it was docked. Not sure if this could be the case but I'm using the nexus now BC of this. I could push the port down a bit and it would go out of landscape...hope this helps ya

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] EvanVanVan:
Thanks, yeah I think that's the issue. My next available upgrade is march 3rd, this phone just needs to hold on a little longer...
[Samsung Galaxy Nexus] peterlemonjello:
Does anyone else have issues with the dialer keypad not showing up? The only way I can get it to display is if I select keypad, then return, then select it again. It never shows up the first time.
[Samsung Galaxy Nexus] domenci:
pops right up for me on 2/13

I wish there was a default to go straight to the keypad.. have I missed something?
[Samsung Galaxy Nexus] klobkelosh:
Do you by chance have animations turned off? If so, turn them on...
[Samsung Galaxy Nexus] peterlemonjello:
That got it. Thanks!
[Samsung Galaxy Nexus] jguerdat:
Does anyone have the 0117 Toro ROM available? I'd appreciate being able to flash back to that version.
[Samsung Galaxy Nexus] klobkelosh:
I do. Uploading now...

https://www.dropbox.com/s/afdtbb36sy7dg8h/cm-11-20140117-NIGHTLY-toro.zip
[Samsung Galaxy Nexus] jguerdat:
Hot damn! Thanks, downloading now...
[Samsung Galaxy Nexus] Shadow Death:
A buddy of mine over on the HTC One section said that the CM11 builds they have now with the Unified kernel kill their batteries like crazy. So.. it's not just us it seems.
[Samsung Galaxy Nexus] Rushead:
Contrarily, I have never had any problems with FML builds. His have always worked well on my phone. @ MWisBest is busy with school, and sometimes it takes him a while to get to stuff. But I've found his cm builds were simply smoother than anything else on my phone. Of course, YMMV.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] Big ZD:
By kill, do you mean damages the battery? Or just causes poor battery life. If you're talking about poor battery life, I don't feel like I've been seeing too many people running M3 on the gnex complaining about bad battery (in fact, I feel like it's been the opposite).
[Samsung Galaxy Nexus] Shadow Death:
In my case... full battery dead in 5 hours. If I use the Pre-M3 release I can get a good 6-8 hours out of it.
[Samsung Galaxy Nexus] jguerdat:
Crap. After flashing back to Toro 0117 it still drops data if it switches from 4g to 3g. I found that setting the mode to 3g only works fine but...

I tried wiping system, cache and dalvik cache and reloading with no help. Don't really wanna wipe data but can try that when I get a few hours to putz around.

Is it possible that it's the radios doing this? Can I upgrade mine beyond I515.09 V.FK01 and I515.FK02?
[Samsung Galaxy Nexus] domenci:
FML is not CM. It's OmniRom. That's beside the point, however. This is the main problem with being into ROMs in my opinion. Here we are with the exact same phone, and one ROM runs fantastically for you, but for me it reboots at random, whether I'm using the phone or not, screen off, on, wifi, lte, whatever... no rhyme or reason. The common explanation that "every phone is different" is complete BS IMO. We don't have thousands of Dell customers running the same OS with the same hardware each with different random problems, and they run on hardware with individual mass-produced chips just as phone users do. There has got to be something as a community that we are missing for all of these unique issues all on the same hardware.My mileage should not vary.
[Samsung Galaxy Nexus] i8qbert:
Yes, we all theoretically started with the "same" phone from the factory. After that there are thousands of variables. Maybe I dropped mine a bit too hard and knocked something loose. Maybe the verizion rep dropped the box. Maybe my battery had a slight defect. Maybe I deleted/ changed something I should not have. maybe I dl'ed a bad build. So yeah, every phone is different :)
[Samsung Galaxy Nexus] Big ZD:
So dumb. Yeah...mine could have been stepped on by an elephant. But in the real world, it is (rationally) expected that of two phones with the same model number, the one phone is essentially identical to the one in the box next to it.
[Samsung Galaxy Nexus] i8qbert:
Ok lets try a more direct approach..If your phone is having random reboots, then you did something wrong. Something that made your phone different then the thousands of other people using cm. Thousands of people use CM as a daily driver with no problems. I was trying to be subtle. For clarity, we know that the cm code is the same for every one that downloads it. That only leaves the phone itself as being different. That could be hardware (unlikely) or well..you get it.
[Samsung Galaxy Nexus] Big ZD:
No, it leaves a bad download, a dirty flash, and any number of things NOT hardware related. Will there be variation in 1 in every 1000 phones....sure. But again, saying every phone is different is simply not accurate. Users are different. Dirty vs clean installs are different. Access to downloads are different. Google apps can be different. Phones...typically are the same.
[Samsung Galaxy Nexus] i8qbert:
"That could be hardware (unlikely) or well..you get it." I emphasis the word unlikely :) If we are talking strictly hardware, then yes theoretically the physical aspects of the phone are the same. I believe when most people in these forums make the statement "every phone is different" they are referring to the end result of attempting to do a mod of some sort (rom, radio, etc). People ask a question like "why is this blah, blah not working." Then they get frustrated when someone asks them for specific details and they say something like "We all have the same phone so it should work." All the examples you give are what "makes them different". Hope that makes sense :)
[Samsung Galaxy Nexus] domenci:
When we're talking about 2 users both flashing the same ROM (no mods) on the same hardware directly after a factory reset, and one of them crashes all the time afterwards whereas the other doesn't, there is obviously more than a difference in hardware at play.
[Samsung Galaxy Nexus] i8qbert:
Yup that pretty much sums it up. And if thousands of other people flash said rom and have no issues, then the problem is probably in your hand. Maybe it's hardware (unlikely..*side note, 4th mention that hardware is unlikely the cause*) or it is software related. Either way it is the black rectangle in your hand. We could split hairs all night on what makes a phone a phone. I am making the case that the phone consists of both hardware and software components (just like a rap cd and a country cd are both "cd"s). Your opinion may differ and that is ok. But however you feel about it is not CM's fault and to suggest that the "community" is missing something because you can't get it work is disrespectful to the hundreds people that work (for free I might add) to help people like you.
[Samsung Galaxy Nexus] domenci:
You might want to re read what I wrote. First of all, I was saying that I had issues with the FML ROM (the thread of which is rife with rebooting and data problems), not this CM ROM. Even so, I followed the directions exactly, as I have been for years. It's not a case of me not "making it work", it's a case of it "not working" Second, the "community" at large spouts this every phone is different BS, not CM, not me. Every time something works for one and not another it's blamed on the hardware. Then after all that you find that people have flashed a different kernel than what's included with the ROM, basically making the discussion in the thread irrelevant. Also, just because a lot of time and energy is put into something for free, does not mean they are infallible and everyone should ignore the problems they have yet to fix. What's disrespectful is ignoring reports of problems and blaming it on end users' hardware, when there are known issues. If the answer is flashing a different kernel to get things to work, then that should be included in the ROM from the start.
[Samsung Galaxy Nexus] i8qbert:
Yes you starting talking about FML, then you went in to a tagent about "ROMs", as in more than one. You are in a CM thread. One would assume that when you said "ROMs", CM would be included since it is indeed a ROM. Wow, is all I can say about the rest. There is always stock.
[Samsung Galaxy Nexus] domenci:
I was replying to someone about FML vs this ROM re:my experience between the two, then you jumped on board. I love this CM11 ROM, it rules my school. Wowwy wow wow.
[Samsung Galaxy Nexus] i8qbert:
I've been with CM for a LONG time (maybe since the beginning) so I get a little passionate about it.:p I can't speak for the community on other ROMs but the CM community has always been willing to help. I don't mean the actual CM Team, I understand we use their ROM with no guarantees, I mean the XDA members that have nothing vested in helping. Even in the beging when things really didn't work (GPS, camera, landscape mode, etc) Heck you could probably get someone to come to your house and help if things went really bad. The whole "every phone is different" thing really get me going also, so i guess you stuck 2 nerves with me. My apologizes if I stepped out of line. It's all good :)
[Samsung Galaxy Nexus] Big ZD:
It's all good man. I apologize too if I was grouchy. I think we were trying to say similar things...just got crossed up a bit. CM rocks it for me as well (now if they'd just push that damn M3 OTA to me..). Just andumb story....but coming from a fascinate, if I remember correctly, there were two distinctly different hardware variations...every time Sammy/Verizon put out an update, it would break a bunch of phones, but fix the others. Just a mess.
[Samsung Galaxy Nexus] domenci:
I think we're on the same page meow. I want to add that I was not trying to call anyone out, especially not the developer of FML. He's doing the best he can to maintain a ROM that has numerous cherry picks and customizations. I was more trying to address the every phone is different mentality in general, which has been around since before I started messing with my Fascinate years ago.
[Samsung Galaxy Nexus] tbonus76:
I hate to be the party pooper, but isn't this a discussion for the 'general' thread? Seems a bit off-topic and "ranty" for a development thread.
[Samsung Galaxy Nexus] demlv:
So what's the consensus on data drops? I'm running a nightly from early January and haven't wanted to update because of this seemingly widespread issue. Thanks for any info. you can share.
[Samsung Galaxy Nexus] jguerdat:
All i can say is that it's biting me in a big way. I can't even revert back to an old backup and make it work. I've settled on using 3g and WiFi which works fine for me since I'm normally connected to WiFi anyways. Maybe I'll get better battery life out of the deal. I got no help/hope contacting bekit so if it gets fixed, fine. If not, I'm upgrading my phone in a few months anyways. This is just a play thing at the moment...
[Samsung Galaxy Nexus] peterlemonjello:
FWIW, I switched from CM11 because the data drops became too much to deal with. Whatever the reason it's taking CM way too long to fix this. Other ROMS resolved this problem a while ago. Baldwinguy77 the maintainer of ShinyROM, Metalspring maintainer of OmniMetal, etc... all have this fixed and their source in GIT.

I've posted this in the CM forums. Hopefully, someone will integrate the fix into CM.
[Samsung Galaxy Nexus] Rushead:
Just to clarify, FML was cm-based, and those were the builds to which I was referring.

Sorry for drudging up an old OT.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] Enzymaticracer:
For everyone's information... Pretty anecdotal but here is my experience with data drops...

I started to get pretty bad data drops many months back after a few flashes. Nothing I ever did fixed it.

Even after going all the way to stock, re locking bootloader, wiping EVERYTHING in the process, etc. I still had them.

Called Verizon, they did some stuff, and then authorized a new Sim card for me.

Went to the store that night to get it replaced. No more data drops after that.

I suggest that you try getting a new Sim card. My guess is the mini Sim Cards our phones use are prone to random failure.

At minimum, it's worth a shot if going all the way back to stock doesn't fix it.