yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] soocold:
At first yes but factoring in the price (its mint used) and my personal situation it was the only choice

Also didn't pay retail ;)

In a perfect world is was about to get the S4 GPE, decided it wasn't financially responsible.
[Samsung Galaxy Nexus] ChazzMatt:
Nexus 5 just passed FCC. 4.96" 1080p screen with smaller dimensions than the 4.7" 720p Nexus 4. And with quad core Snapdragon 800. :good:

Nexus 5, 5": 131.9mm and 68.2mm

Nexus 4, 4.7": 133.9mm x 68.7mm

Which means, of course, Franco kernel Galaxy Nexus support is nearing the end. No more support for Galaxy Nexus (gen 3) when Franco gets his new Nexus 5. Then, last year's Nexus 4 (gen 4) will start to receive sporadic releases while the Nexus 5 will get his full attention. :) I'm moving to the Nexus 5.
[Samsung Galaxy Nexus] bit_imp:
That's already a lot of time has passed, but the problem with stuttering music in PowerAmp still is. read_ahead set 512. There are ideas on how to fix this? Firmware PA3.99
[Samsung Galaxy Nexus] Astug:
Saw the same sheet a couple of hours ago on a dutch tech site, looks amazing!
[Samsung Galaxy Nexus] osm0sis:
You mean Wi-Fi PM Fast? Francisco likely forgot. ;)
[Samsung Galaxy Nexus] okanb3:
My 3 or 4th circle;

http://i.imgur.com/ZfYq38f.jpg

http://i.imgur.com/RoPlZMt.jpg
[Samsung Galaxy Nexus] pkgnex:
You're on the right track! Try read-ahead at 256, or even 128. This seems to have fixed the PowerAmp issue for people in the past.

512 felt "snappier" in our testing (which is why it is the default), but lower values were OK. You probably won't notice a difference... except that it hopefully gets PowerAmp working again!
[Samsung Galaxy Nexus] bit_imp:
Thanks for the reply. I'll try to change the value to your proposed
[Samsung Galaxy Nexus] JBNex:
I set mine to 2048, runs pretty good. :$

What's wrong with higher values?
[Samsung Galaxy Nexus] pkgnex:
Not so much "wrong" as just not optimized... most devices run best at a certain value, and on G-Nex that seems to be between 256 and 1024. There are some utilities that test it, as I recall, (in jrummy's toolbox, I think there is one) and give you the optimized setting for your device.

Testing on multiple devices, along with extensive subjective evaluations, led Franco's Dev Team to select 512 as the optimum. But like I said before, the average user might never be able to tell a difference subjectively between any reasonable value (128 to 2048).
[Samsung Galaxy Nexus] abhishek93:
is this normal? if not then is it kernel related or rom??
[Samsung Galaxy Nexus] TiagoRigueto:
is good kernel but here is very hot...:(
[Samsung Galaxy Nexus] gpzbc:
I also have a very hot phone with r391.
[Samsung Galaxy Nexus] BriVG:
Temps normal here
[Samsung Galaxy Nexus] greyhd:
I flashed your R391 moded kernel and UV after reading your posts, but still getting 4-6% drain per Hour.
[Samsung Galaxy Nexus] Edward Stanbury:
rogue apps ? get better battery stats or wake lock detector something else is going on here that is not kernel related :\
[Samsung Galaxy Nexus] ashclepdia:
what does your battery graph look like for starters?
[Samsung Galaxy Nexus] greyhd:
I have BB stats installed and for some reason I see "wifi" on even though I have it off.

Let me post a screenshot.
[Samsung Galaxy Nexus] Sik-1:
If your on 4.3 make sure u turn off the WiFi scanning always in the advanced settings menu
[Samsung Galaxy Nexus] greyhd:
Thank you, I didn't know about this option. Here are some screenshots.
[Samsung Galaxy Nexus] Edward Stanbury:
can clearly see that your cell signal is not the the best that will deffo be draining a chunk of ya battery for sure and your phone looks likes its sleeping okay :P how often do you use your 4g in one cycle on average ?
[Samsung Galaxy Nexus] greyhd:
Yea I had a brief signal drop a few hours ago. I always have 4G on :)
[Samsung Galaxy Nexus] Edward Stanbury:
i think that may be your culprit ;) if your not using ya data connection you might as well turn it off and save some juice, sadly in new zealand we have terrible expensive data plans so im in a good habit of turning it off all the time unless i really need it haha but yeah the signal strength is not the best either aye a nice fat green bar would be ideal in the battery section but hey i guess we cant have it all sometimes ;) also did this sort of battery drain happen on other kernels/stock rom?
[Samsung Galaxy Nexus] greyhd:
The only other rom I tried was CM, currently on Vanir. I think 4.3 and the signal drops on some roms is what has caused my battery issues. I will turn on wifi when I am at home and hopefully that will help with the battery. I also just turned off "Scanning always available". I still have unlimited data that is why I always have 4G on.
[Samsung Galaxy Nexus] Edward Stanbury:
ahh i see, those little changes should help extend your battery life in the long run especially using wifi at home ! :D omg unlimited i wish i could have that ! GIMMIE ;) haha anyways hope we could help ya out a little at least
[Samsung Galaxy Nexus] greyhd:
Thank you everyone for the help, it's greatly appreciated.
[Samsung Galaxy Nexus] Sik-1:
No problem, that's wat we're here for just hit the thanks button
[Samsung Galaxy Nexus] The Gingerbread Man:
Anyone have any ideas about my screen keep in turning its self on, its especially prone to it if I turn the screen off manually it just turns back on. I can't think of any settings that would cause such behaviour. My power button doesn't feel like its sticking. I'm really confused about this as last time I had this issue it was an app causing it (tablet talk) which I have uninstalled ages ago and the issue went away, now its back with a vengeance and it seriously draining my battery. Stock rooted rom supersu 1.60, fixed 391, nexus louder
[Samsung Galaxy Nexus] okanb3:
I was had this experience earlier, too. It was Greenify, making supersu requests. You can check
[Samsung Galaxy Nexus] The Gingerbread Man:
I don't use greenify though. Googling, apparently its very common. At least its not kernel related anyway which was my original thought.

Edit

Seemed to have fixed it by using the clean up option, reboot, reinstall from play store, used twrp method to update the su binary and converted to system app and I have not had the problem since (fingers crossed).

Edit 2

Now off charger its screen on-ing again...
[Samsung Galaxy Nexus] namelesske:
5 or more reboot on a single day

Hello every one!

The r391 was really bad for me. I had 5 or more reboot at last week on a single day. I had to flash the stock kernel on the bus :( The random game for testing was NFS Most Wanted, also terrible, pumped up the grafix but it was worse than cancer in fps.

Stock 4.3 JWR66Y Maguro
[Samsung Galaxy Nexus] Cheezhead19:
Is there any reason I'd constantly lose root after rebooting? Doesn't happen on stock, didn't happen before I reflashed the same build plus 391. I had been using 391 with no problems...
[Samsung Galaxy Nexus] osm0sis:
Use my fixed version. One of my fixes was to how the root binary service gets called.
[Samsung Galaxy Nexus] Cheezhead19:
Reflash SU after or will it be OK?
[Samsung Galaxy Nexus] gpzbc:
I was experiencing the same thing every time I flashed Osmosis 391 fixed. I eventually gave up and went to the Golden kernel.
[Samsung Galaxy Nexus] Cheezhead19:
Thanks! I flashed it and then su, tested rebooting, after one it kicked me to recovery randomly, after I let twrp fix su permissions it is booting and retaining root!