yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mfdemicco:
Try lean kernel, don't under clock and under volt. Only use the interactive governor.
[Samsung Galaxy Nexus] allcity187:
I use to have the same issue until I install Franco mile 5 kernel.
[Samsung Galaxy Nexus] iconaw1:
Google movies stream fine for me on build 4. Just tried and worked with no problem. I have had this issue on other roms though.
[Samsung Galaxy Nexus] anotherdroid:
absolutely. check back a few pages under my name. we talked in length about this. only thing that fixed it for me was wiping everything 3 times over and flash from scratch and DO NOT, under ANY circumstances, restore any data via Titanium Backup or something of the sort. you will not get deep sleep and frankly, this is your only fix at this point.

if you no longer go into deep sleep, make a nandroid and then go ahead and restore any data if you wanted. it's not the kernel. i assure you. if it's not from data restore, then get a hold of betterbatterystats and see what's happening (i hate BBS! :)
[Samsung Galaxy Nexus] cmajpwc:
Interactive. I don't have his app installed either, so its all the default settings.
[Samsung Galaxy Nexus] Kimusubi:
Build 4 and 3 have consistently given me issues. I've done clean installs every time and made sure that each step is done properly, but my phone still crashes. I'm mainly having issues with bluetooth or OS crashing. Sometimes the system will self reboot as well. Build 4 is much better than 3, but still buggy for me. Anyone else have these issues or is it just my phone?
[Samsung Galaxy Nexus] David522d:
Woah been on build 2 for weeks? Today my battery just dropped from 86 to 12 in mins?!

Hows build 4?
[Samsung Galaxy Nexus] danwguy:
That's probably what it was then, I was restoring a game backup via titanium backup since I can't save it any other way. That really sucks though, I'm so close to getting all challenges
[Samsung Galaxy Nexus] dubyajaysmith:
If you've read the forum you know it all but I have been very happy with it being it's the only ROM/radio combo that has given me 4G everywhere I've tried. If I ever flash anything else, this will be my fall back Nand for sure.

[Edit] note I haven't used Every combo but damn near and as always YMMV...
[Samsung Galaxy Nexus] hlaalu:
I've been using this rom since some of the first nightlies, and this rom just feels slower and more laggy to me compared to ics aokp. I've done clean flashes, and I'm still getting lag issues. I use the Franco m5 kernel because I was having problems with the stock kernel topping out at 700mhz. I've uninstalled most apps and games that I don't use everyday but am I the only one with this observation? If so I'm not sure where else I should be looking for problems.
[Samsung Galaxy Nexus] stillthisguy:
Same thing for me, build 3 was a disaster on my phone, 4 was better but still had issues. Back on CM10 nightlies.
[Samsung Galaxy Nexus] dubyajaysmith:
Was your problem that your CPU seemed to top out @700MHz for some reason or you were underclocking and that gave you troubles? I don't use Google Now, I didn't underclock/volt, I wiped data>cache>dalvik and flashed Build 4 through recovery. Kept stock kernel and settings for the most part. Can't really think of anything else that would help :confused: but I can't say I have lag.

[Edit] Incase you want to check out how an updated nightly performs: http://goo.im/devs/DizzyThermal/toro/AOKP_Nightlies
[Samsung Galaxy Nexus] fullmetal509:
From my experience Build 1 has been the most stable ROM, Build 2,3 and 4 have just been awful from blackouts, random reboots, lag like no other and battery just been horrendous.

Sorry if I sound like I'm bashing on AOKP but I'm not!! Just that recently it hasn't been treating me nicely :(

Moved to CNA and I love it!

Via Galaxy Nexus [LTE]
[Samsung Galaxy Nexus] Quod:
Build 4 has been excellent for me. Sorry for your luck guys :(
[Samsung Galaxy Nexus] travisjshepherd:
I agree, with B4 all the random reboot, the rebooting when I unplug it, and lag are all gone. I even had some nfc issues before but not now!
[Samsung Galaxy Nexus] Protibus:
I too have had very good results with B4. The only problems I had were after a dirty flash from B3 but after I clean flashed it, wiping system at least 3 times and installing fresh apps, not from a backup, it has been nothing but absolutly perfect.:D
[Samsung Galaxy Nexus] SirBindy:
I've not had a single issue with Build 4. I guess that just goes to show you how unique each handset actually is.
[Samsung Galaxy Nexus] bobbyinboone:
I bad some issues until I flashed Francis m5....
[Samsung Galaxy Nexus] Tom Kellogg:
Interesting, after a very clean flash from V's stock ROM, I did reinstall the Apps that Play Store missed from Titanium backup. For three or four days I got numerous full crashes during sleep. Power click or click and hold did nothing. Battery pull and a boot got things up and going again. Then another sleep mode crash. There was no indication what was causing the crashes ... WiFi, data and sync were off.

Then, after a few days, the problems just went away. No clue. Things have been just ducky for about a week now. I'd like better battery life like everyone else, but my power usage sure indicates that unless I seriously dim my screen, I am stuck with a device that does a heck of a lot and looks great on a very small battery. My screen usage is typically about 60 - 65% of the battery usage. Watcha' gonna do?
[Samsung Galaxy Nexus] kioshi:
How are people having reboots on build 2-4?

Are you guys using stock kernal or another one??

Stick to Francos, painless and no reboots.

I came for Muzzy's rom onto build 1, then dirty flashed 2-4..wiped and reflashed 4 again.

During those times, i never had a reboot problem. I used Francos kernal + nightlys, switched to trinity's kernal as someone recommended, went to tiny's kernal, then back to francos milestone 5. Never a reboot for my phone running AOKP.
[Samsung Galaxy Nexus] hlaalu:
It wasn't from undervolting, something with the stock kernel. It would keep resetting the Max frequency to 700mhz.
[Samsung Galaxy Nexus] :
I dunno why my phone just doesn't like B4. I tried Franco, Lean, and Glados. No undervolting or anything like that. I was sad to see no build this week but I am sure they are busy on B5. Fingers crossed.
[Samsung Galaxy Nexus] dimsdale:
I'm running Build 4 with a totally clean install and the default kernel. I have had one forced reboot and not a single other problem since its release.
[Samsung Galaxy Nexus] crobs808:
Anyone having problems with this ROM needs to modify their behavior in how they treat their phone. Here are the definitive steps to avoid issues:

1. Flash Touch Recovery (if you don't have it already)

2. Make Nandroid backup

3. Flash JB bootloader (if you don't have it already)

4. Factory Data/cache wipe

5. Format /system

6. Wipe Dalvik cache

7. Flash Build 4

8. Flash 8-31 GApps

9. Flash 4.1.1 Radios

10. Flash Trinity kernel (TNP1536-307-JB-STABLE35)

11. Reboot

Don't modify any OC/governor settings! I have ZERO issues and averaging 16 hrs battery life w/o charging.

As with any ROM: NEVER restore anything from Titanium backup or any other restoration utilities like that. The reason people start blaming ROMs for their troubles is because they don't go about flashing and maintaining their phone the right way. Each ROM has a kernel it works best with. For AOKP that is Trinity.

We've got 50+ pages on this thread of people complaining about problems that are already solved by using the above setup. Complaints from here on out are 100% user error caused by refusal to use the recommended methods.
[Samsung Galaxy Nexus] travisjshepherd:
I do/have done about 3 of those things & I have no problems at all.
[Samsung Galaxy Nexus] Protibus:
I have been flashing any ROM I try out even for a short time using the method above. In all cases I have had little to no problems with any ROM except for any known bugs that the OP may report. In the case of AOKP which I have stuck with because of its stability and customizability I am using Francos M5 right now but have used Trinity Stable35 with same results.

The combination of AOKP and either Franco or Trinity is going to give the ultimate JB experience one can find. I say it is about time the whiners were addressed who are having strange issues because they will not take the little extra time to flash a new ROM as it should be. :good:

Edit: Oh yes I am also running it on Nexus 7 equally as flawlessly.
[Samsung Galaxy Nexus] fullmetal509:
A lot of us are doing the correct procedures! It just comes to show how different each users phone responds different builds and combos.

Via Galaxy Nexus [LTE]
[Samsung Galaxy Nexus] crobs808:
Each Galaxy Nexus has the same hardware. Samsung might source a PROM chip from a different manufacturer but that won't make it act any different than the next phone. There are only two reasons why a phone would act unlike another with supposedly the same setup is: hardware failure or user error. If you do not have a hardware problem (i.e. need a replacement) then it's 100% on you as to why your GNex is acting up.

More importantly: Read forum rules. Not only is name calling against those rules, but it is also immature and a sign of insecurity. You've been warned.
[Samsung Galaxy Nexus] csseale:
Crobs808 you are so wrong. Every phone acts different from another. Some can handle different overclocks or underclocks, some screens handle touch differently. Some GPUs can handle a 512 overclock some can't. I have 2 gnex and one runs jellybelly horribly and one runs it great. Saying its 100% user error is terribly wrong sorry.
[Samsung Galaxy Nexus] crobs808:
Huh? My claim is only about two of the SAME model running the SAME ROM. Not two different phone models.

I was mainly addressing the people of this thread who are all using GNex's yet complaining about elementary issues that were already solved long ago. (i.e. boot loops, freezing, unreasonable lag, etc) - none of these happen on AOKP JB anymore if you are setting up your phone correctly.
[Samsung Galaxy Nexus] anotherdroid:
bottom line is... still no one should be dissuaded from coming here and asking questions. great advice, yes, but don't confuse advice with help ;)
[Samsung Galaxy Nexus] crobs808:
I'm an RC. I help people. Not asking for pats on the back at all but people could save themselves a lot of headaches/trouble with their phone by following the guides and instructions we post. Not getting paid for this :)

My ultimate concern is to get users in a stable fast working environment as quickly and seamlessly as possible. That can't happen when the same question is being answered 5 times over in the same thread.
[Samsung Galaxy Nexus] endomatic:
crobs808,

What backup/restore method are you suggesting for apps? I get the proper flashing and such, but restoring apps?

Playstore, one by one or push adb (will that work?)

Cheers
[Samsung Galaxy Nexus] crobs808:
The Play Store auto re-downloads all the apps that I had previously installed. It is really good about only downloading what I actually had installed up until I re-flashed. I then reconfigure everything manually. It takes me about 30 minutes after flashing to get everything back to normal, but I know for sure it is clean and that I did not restore any junk from an old setup. This may be part of the reason why I never have any issues with ROMs other than features/performance. I've never had boot-loops, freezes, hangups, major lag or anything on my Motorolas or this Nexus. When I was learning Android, hacking the XV6900 (HTC Touch) I had those problems, but that was before I knew my kernels and knew not to restore anything from backup apps.

The only two apps I import settings into are Touchdown and K9 Mail (but those are just text/ini files that contain email server settings).
[Samsung Galaxy Nexus] endomatic:
That is what I have resorted to since coming over to the Gnex from the fascinate. Mostly due to the fact that once the auto download starts there seems to be no way to stop it. That said I'm on Steve's Oct 10 build and it is great.

Cheers
[Samsung Galaxy Nexus] nismology:
AOKP with IMO's minimalistic kernel is working beautifully for me with great battery life. Restored apps and app data with titanium backup after a clean install which came directly after fastbooting the full factory image from Google's site. Best ROM (for me).
[Samsung Galaxy Nexus] crobs808:
Of you really want to stop it, just go into Play Store, Menu, My Apps, then there is a "Stop All" button.

I am holding out for AOKP Build 5, hoping it will be 4.1.2 based. The thing is, I do not have any problems at all now, so not really anxious for a new build.
[Samsung Galaxy Nexus] kioshi:
While crobs makes a good point on the method of going about flashing a rom correctly to prevent zero problems, i dont agree with starting over on some apps instead of restoring them via titanium backup pro.

I have Aedict, LINE, and few other apps that need data recovered for purposes, so i have to recover/restore them completely through titanium.

Honestly, you have to see which apps play nice in restoring back and which apps cause problems. The mentioned apps have NEVER caused problems for me restoring on my old HTC Incredible or Galaxy Nexus LTE toro.

Did a first ever screencaps for LTE on 24/7 with 1 hour usage of WiFi, LINE app running throughout, and Google Now running 24/7.

Francos milestone 5.

Governor interactive

Undervolted 729mhz @ 950mV

230mhz @ 825mV

Battery charge limit set to 97

Few gamma control changes

12% brightness.

Build 4 AOKP w/ 7/29 GAPPS

Stock battery 1800

No reboots

no lag except on mobile facebook website but facebook is POS in general.

**i have flashed milestone 6 now, will see how it does with governor set to dyinteractive.

Going back to hardware vs user error: My phone had problems to begin with, from signal to battery, etc. from owner i bought it from. But hey, I'm making good use of it.

Maybe your phones arent hardware malfunctioning, maybe you are doing something wrong after flashing the rom and running it daily? Try my setup and report back...and yes, each phone is different, but its how you overcome it, like i did..
[Samsung Galaxy Nexus] crobs808:
9hrs is below the low end. While your post pretty much backed me up, I'd have to say you may still be doing something wrong.

For battery life, you should be getting 12hrs on a heavy use day, 16hrs on avg days, and 22-24hrs on low use days. Again, you're doing the kind of stuff I tell people not to do (undervolting and changing mix/max CPU)...just flash Trinity and leave it as is.
[Samsung Galaxy Nexus] kioshi:
Day 2 of trinity kernal stable I wasn't getting the battery hours as you mentioned. Here is build 2 of AOKP with milestone 5 running with 3g on all day.

I have everything on except GPS and WiFi if im not in a classroom/library.

But you're on an extended battery, mines stock. I havent seen anyone pull off 24 hours on a stock battery with minimal usage like texting and few phone calls to be honest.
[Samsung Galaxy Nexus] timrichardson:
With Build 4 & Franco milestone 5&6 my gsm GN crashes to the point where I need to remove the battery. Didn't see this on other custom roms. It does this while in standby. I set max cpu to 1200 Mhz which has never been a problem in on my phone, besides the crash happens in standby. It's happened twice in the last four hours. I'm going to flash the factory 4.1.2 images to eliminate hardware problems.
[Samsung Galaxy Nexus] travisjshepherd:
I'm getting the DT's just waiting for B5, I am a flash junkie, I've even been flashing mods just to help ease the wait.
[Samsung Galaxy Nexus] anotherdroid:
same here. but, i'll be damned if this Build 4 isn't the most stable ROM i've ran in 2.5 years.
[Samsung Galaxy Nexus] kioshi:
You are running maguro version right and not toro like this section is?

Could be just gsm variants, CDMA is fine for me since Sept of this year
[Samsung Galaxy Nexus] xplayerz82:
Gallery

Hey guys, does anyone know how come Gallery does not sync ?
[Samsung Galaxy Nexus] Beamer9408:
Build 5 will definitely be 4.1.2 based the last to builds I compiled since the 10th have been as far as features the only thing really noticeable has been nav bar widgets was merged and there really has been a lot of work done since build 4 but I build every other day and forgot what was in build 4 vs what I have now.
[Samsung Galaxy Nexus] shadowstewie:
Holy f****** ****
[Samsung Galaxy Nexus] shadowstewie:
I'm on Build 4 with Franco Milestone 6....
[Samsung Galaxy Nexus] digitallure:
what does the little hat in the task bar notification do?
[Samsung Galaxy Nexus] crobs808:
It gives you swagger. Toggle it on and you'll get the moves like Jagger.

Translation: it does nothing. First thing I do when I flash AOKP is change the toggle to text+icon and disable that one. See below...
[Samsung Galaxy Nexus] digitallure:
Haha! Nice. Thanks for the info.
[Samsung Galaxy Nexus] bobbyinboone:
Before I flash a new ROM I read threw the thread... so I don't go asking silly questions.... sorry getting flash withdraw....

:p
[Samsung Galaxy Nexus] ba_hamilton:
I have done these steps with very nice results. I'm not much of a kernel expert but since I've flashed the recommended kernel my wifi signal is much stronger. I came from another kernel and I was not getting very good battery life and it seemed my wifi signal was always weak. Maybe it's coincidental but I'll take it.

Waiting for a build on 4.1.2. or even a 4.2 build soon. lol. I did read where jb 4.2 is out in the wilds someplace so I guess we will be seeing it pop up here soon enough.
[Samsung Galaxy Nexus] anotherdroid:
like only a good Buffalonian would do. would ending the lockout help the withdraw? ;)
[Samsung Galaxy Nexus] tattedupboy:
Those steps all work well for me, except for that choice of kernel. Trinity sucks for me; my phone is always laggy and slow whenever I flash it. 007 works much better, at least for me.
[Samsung Galaxy Nexus] daviddemarco79:
Wish there was a toggle for the navigation bar background for transparency
[Samsung Galaxy Nexus] Protibus:
Anyone hear of any updates being available soon to 4.1.2 or 4.2? The test build for 4.1.2 is the last build I have seen for this ROM. Or is this ROM at an end???????
[Samsung Galaxy Nexus] Beamer9408:
No end in sight. New features being merged everyday.
[Samsung Galaxy Nexus] travisjshepherd:
What he really means is "Is there an ETA?" LOL they love that stuff!
[Samsung Galaxy Nexus] crobs808:
There's never an ETA, nor should there be.This is not a licensed/paid product.
[Samsung Galaxy Nexus] Protibus:
No kidding....duh I would have never figured that out on my own. Just asking if anyone had heard of another official release on the horizon based on 4.1.2 or 4.2.
[Samsung Galaxy Nexus] Beamer9408:
Well as far as I know there is no source for 4.2. Aokp is based of aosp 4.1.2. it has been since source was released they just haven't put anything official out yet. One of the good things about aokp is you can sync to their source and build yourself.
[Samsung Galaxy Nexus] Antob125:
AOKP Twitter yesterday said B5 will be out before the next Milestone so we can almost expect B5 Sunday since that's the day of the week they release builds. And 4.1.2 has been merged so expect it in B5. Also 4.2 won't be released until it's released in source just like always.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] travisjshepherd:
Why Sundays? Obviously these guys work during the week, but why not Saturday or Monday? No complaints just wanting to know why that day of the week.
[Samsung Galaxy Nexus] shadowstewie:
If it was on any other day of the week. We could ask this same question as to why it is on that particular day lol.
[Samsung Galaxy Nexus] crobs808:
Got a wife? Got kids?
[Samsung Galaxy Nexus] Antob125:
They posted this a while back on their site and on Twitter. No idea why they chose Sundays, but that is the day of releases if there is one for the week.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] travisjshepherd:
Yeah, Sundays are my family days. Jerk.
[Samsung Galaxy Nexus] deadwolfbones:
Got this installed last night and it was running beautifully. Today at lunch I decided to reboot the phone to show my coworker the lovely AOKP pink unicorn boot animation, and now my phone is inexplicably stuck on the Google logo.

I was able to get into fastboot and then CWM, where I cleared the cache/dalvik cache, but it's still not booting. Just hanging on the Google logo.

Anyone got any ideas?

edit: of course, as soon as I posted it finally went through. weird.
[Samsung Galaxy Nexus] hawkye:
I noticed Google released their Calendar to the Play Store. I figured I would install it that way I could get the updates. First I disabled the Calendar that comes with the ROM and then installed Calendar from Play Store. The Play Store Calendar FCs. Anyone else?
[Samsung Galaxy Nexus] iconaw1:
This is common and is due to new features in Jelly Bean, when your phone boots it first checks for changes, errors, etc. So if you made a change it could cause this. Just let it sit it will usually boot, some have complained of 30 minute waits, so just hold out. It should boots faster after a few boots without changes.
[Samsung Galaxy Nexus] jamontoast1291:
The new calendar showed up as an update for me in the play store. I never disabled the old calendar, the new one just replaced the old one when I updated it from the store. I haven't had any issues with it so far.
[Samsung Galaxy Nexus] deadwolfbones:
Thanks!

I'd flashed the 4.1.2 gapps last night, and when it finally rebooted today it had to "optimize" one app. I'm guessing that was the change.
[Samsung Galaxy Nexus] shadowstewie:
So, I'm on Build 4 with Franco's latest nightly. I was having no problems except the whole getting stuck on the Google logo for up to 7 minutes at a time when I rebooted. I heard from somethere that the 4.1.1 JB Bootloader apparently fixes that problem. I flashed the bootloader in CWM and now I'm getting random reboots like crazy. I flashed it yesterday and I've had my phone screen turn off, not turn back on, flash a white light on the screen for a millisecond and it reboots. I've had this happen about 5 times since yesterday.

I'm guessing it's due to Build 4 maybe? If anyone has any idea on what's going on I would greatly appreciate it. Thanks guys!
[Samsung Galaxy Nexus] crobs808:
Dude. Relax. I meant it playfully. Goodness.
[Samsung Galaxy Nexus] Beamer9408:
My first thought is try a different kernel.
[Samsung Galaxy Nexus] dimsdale:
Nobody ever endorses the default / stock kernel on aokp. Why is that?
[Samsung Galaxy Nexus] Beamer9408:
I don't really care what kernel it is faux works for me but if your getting freezes and reboots I would try a different kernel.

Also I like the color profile in Trinity that's why I use it I don't touch anything leave it at defaults and I get no reboots or freezes and color looks good on my phone yours may be different but that's why I use Trinity.
[Samsung Galaxy Nexus] bobbyinboone:
Tic TOC... have a feeling we are in for some juicy updates. :D:D:D:D:D
[Samsung Galaxy Nexus] King Speedy:
The lengthy wait-times at the with the Google logo aren't a problem, they're a feature (seriously). JB has a filesystem checking protocol in place, and if Android detects any reason that the FS integrity might be compromised, it'll be checked. I've had it take as long as ten minutes, so as long as you aren't getting anything absurdly longer I wouldn't worry about it.

The random reboots after changing bootloaders sounds like a case of correlation vs causation. The bootloader just handles booting Android proper, and doesn't really have anything to do with the function of the OS. You might want to try a kernel update or change and see if that fixes your problems.
[Samsung Galaxy Nexus] ford12acing:
phone keeps switching to silent/vibrate mode. any thoughts?
[Samsung Galaxy Nexus] crobs808:
shadowstewie - DEFINITELY flash the JB boot loader. I had the same exact problem until I flashed it.
[Samsung Galaxy Nexus] kioshi:
Do you have the settings to change to vibrate when sensor is covered or anything?
[Samsung Galaxy Nexus] Beamer9408:
This and check for when phone isface down actions I'm romcontrol