yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sway40:
Still a lil early to tell but ima say it anyway, battery blows on v3 r210. I'm at 63% with 30 min screen on time and 7hrs battery. Stock clock, just some gamma changes and stuff, half brightness. I was getting over a day and 3hrs screen on time with same setting im using now.

I can live with this for now, but anyone who needs really good battery should watch out with this combo...just fyi.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mursepaolo:
Damn what setting is that?
[Samsung Galaxy Nexus] sway40:
Im on ondemand, wheatley is what I was on and the only thing I changed now that I think about it bc it seemed a lil laggy. Usually I can tell by now what's doing good or not...this isn't. When I was getting awesome battery, I was on cm9 and franco180 kernel, haven't seen good battery with jb yet.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] distortedloop:
I'd prefer that bland boot animation to the Franco Kernel boot animation, since I'm not running it, but can't get it to go away even though I flashed the stock kernel and the stock boot animation is in the proper location on the phone. :(
[Samsung Galaxy Nexus] thelowend:
Has anyone tried maxing out the volume settings in franco's kernel updater app?
[Samsung Galaxy Nexus] clovis_ll:
yeah I have been using V3 and 210 kernel combo since last night and i have been using it normally since last night and i still have 70% battery left!
[Samsung Galaxy Nexus] thelowend:
Have you seen a noticeable difference in battery between v2 and v3?
[Samsung Galaxy Nexus] tacosrdelicioso:
There probably is because v3 has beats.......which seems to eat some battery a little
[Samsung Galaxy Nexus] diamond_4g64:
I am on telus network. Hspa. Will this rom work? I have tried the jelly belly on another tread and it does not boot.
[Samsung Galaxy Nexus] enik_fox:
CDMA phones only. It will not have the proper radios to work with hspa.
[Samsung Galaxy Nexus] diamond_4g64:
OK so I AM GSM that means
[Samsung Galaxy Nexus] DirgeExtinction:
Go to the GSM Galaxy Nexus Development forum. They have JB there too. :)
[Samsung Galaxy Nexus] 105437:
Same setup for me today and I haven't noticed this. Since I just switched from Franco 210 to Faux 19, things seems smoother than ever before.
[Samsung Galaxy Nexus] clovis_ll:
don't really know coz i started with v3.
[Samsung Galaxy Nexus] hogowner:
Can someone post a link to faux 19.. I mean all the other links that people posted. Goes to a pave where there are a lot of kernels....and the dummy that I am....not sure which one to download.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Dakota0206:
http://thesuperusersguide.weebly.com/everything-jelly-bean.html

There is a direct download link in the kernels section

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mark manning:
The very bottom of the list tuna faux 19b6 or something like that but its the last one

http://faux.androidro.ms
[Samsung Galaxy Nexus] KJW979:
http://db.tt/fTmHOfaN

Try here

Edit: sorry here

http://db.tt/fTmHOfaN
[Samsung Galaxy Nexus] j.bruha:
I have a silly request if anyone has the time to help me.

I flashed the /audio folder from AOKP M5 over the /audio folder on this ROM, and while almost all of them are the same, it seems that Themos has been changed for Jelly Bean. Can someone pull it with a file browser and post it here? If not, I'm just going to backup, wipe, reflash, pull it, post it here, and restore my backup.
[Samsung Galaxy Nexus] Papa Pearce:
USo reading up on the Project Butter UI, I've noticed that it's supposed to basically ramp up the CPU to max when the user touches the screen after being idle, as well as some other things.

Now, I assume that changing the governor will override this default action right?

I guess the thing I really want to know is if you have to run stock kernel to get the full effect of Project Butter. I wouldn't think that were the case (always love Franco's kernels by the way), but ya never know. Currently using Franco's and haven't tried stock yet, but I'm not so sure I'm getting the Buttery experience as advertised. I mean, it seems faster, but that speed isn't always there as consistently as I expected it would be. Thoughts?

Oh, and don't get me wrong, this ROM is sick! So impressed at how quickly this was pumped out. Props!

EDIT: Okay, maybe I was just expecting too much. It is noticeably smoother, especially when tapping recent apps, though there are still occasional slowdowns I guess it's just waiting for apps to be updated to take advantage of the new Project Butter features? Been running V3 for almost 24 hours now (screen on time totals of roughly 6-8 ours lol)
[Samsung Galaxy Nexus] RonnieRuff:
Mine is far snappier than any ICS ROM I have run.
[Samsung Galaxy Nexus] kimboinatl:
It's not a silly request, I'd really like this back too, LOL. I had it set as my alarm ring. Makes me think of ice cream trucks.
[Samsung Galaxy Nexus] njd15:
Idk why but every time I shut off the phone it stays in Google boot loop..a d I have to go to the mounts and storage and manually place it to where it says unmout for system..data..and cache...why does that happen? I did a clean install followed all steps
[Samsung Galaxy Nexus] mark manning:
What recovery are you using?
[Samsung Galaxy Nexus] illcat2000:
This rom is running very well and i am thoroughly enjoying it. It is a bit snappier then stock ics but project butter may be a bit much. I dont have many apps i stalled and im definitely getting lag. And ghats with the stock kernel. Definitely not as snappy as ANY custom rom.
[Samsung Galaxy Nexus] njd15:
Touch clockwork recovery? Should I flash the regular clockwork mod and take off the touch recovery?
[Samsung Galaxy Nexus] super_dk:
Here you go
[Samsung Galaxy Nexus] njd15:
Clockwork touch ? Should I remove it and flash the regular clockwork recovery?
[Samsung Galaxy Nexus] mark manning:
No just trying to see if there is a common reason as to why this happens to some and not others. I have touch cwm and it works perfectly
[Samsung Galaxy Nexus] kimboinatl:
I think that's the new Themos, not the old one. The old one sounded like this:

http://www.youtube.com/watch?v=CZB6WXDuM1g
[Samsung Galaxy Nexus] anotherdroid:
just a random thought... complaining about battery usage after less than 24 hours from flashing is pointless. you simply cannot judge a ROMs battery usage until you've stopped ****ing with your phone and started to using it in a normal capacity for at least 2 days.

just putting that out there for anyone who comes here and reads "i just flashed this ROM and the battery sucks!".
[Samsung Galaxy Nexus] Papa Pearce:
This.

I get the same battery life as before on ICS. 2-3 hours screen on time.
[Samsung Galaxy Nexus] veloslave:
I sure wish it did.... :(

I wonder if mine is not working because i used the "fix file" that was sugested a while back?

Speaking for me and I am sure for some others... can someone post the stock text in the conf file or even a link to the stock file? Sure would be nice to see if that is what the problem is.

Good ol hind sight... should have backed it up.
[Samsung Galaxy Nexus] tgreenstein:
Problems with *228 programming

Using V3 with no problems -- fast and smooth. Had GPS problem yesterday but seems to have cleared up today.

One issue, though: when I dial *228 to reprogram, I can't get a dialpad (there's no button or icon for it) which makes pressing "2" a bit difficult. Anybody else have this problem?
[Samsung Galaxy Nexus] 105437:
Running v3 and Faux 19 kernel... anyone have any luck overclocking this ROM? I'm currently running at 1350MHz and see nice performance. Anyone else pushing this baby a little harder with good results?
[Samsung Galaxy Nexus] KJW979:
I tried it at 1800 for about an hour, flew, opened and closed apps almost instantly, but phone did start to feel a little warmer to touch. For that hour no negative results that I could see, also didn't try to set and reboot, so not sure how it would handle that.
[Samsung Galaxy Nexus] BeardedB:
How is the battery life?

Simba was moving too slow, so I told him to Mufasa.
[Samsung Galaxy Nexus] mursepaolo:
I've been flashing roms since the G1 and I've literally never had a dramatic battery increase by "waiting a few days". I'm a very heavy user at all times, so if the battery sucks from the get go, it sucks. Plain and simple. My phone never stops working for me, so how I use it after flashing is how I use it all the time.
[Samsung Galaxy Nexus] kimboinatl:
Been running it at 1800 (screen on) for a good bit of the day. No problems and seems pretty responsive.
[Samsung Galaxy Nexus] Firerouge:
Wow you're right, that seems to be an actual jelly bean problem.
[Samsung Galaxy Nexus] 105437:
Wow... are you running ondemand or interactive?
[Samsung Galaxy Nexus] njd15:
I kinda found a fix...temp.. I got quickboot app..which is the widgets to reboot...power off and reboot in recovery...a d its working fine.... but when I power it off normally. It boot loops in the Google unlock screen..and I have to pull battery out and put data, system, cache.and set them all to Unmount and then it works fine...any suggestions?
[Samsung Galaxy Nexus] kimboinatl:
Ondemand.
[Samsung Galaxy Nexus] KJW979:
Same here, no dial pad. Tried backing out to see if opening phone during call would bring it up, nada.
[Samsung Galaxy Nexus] lioryte:
Yes. Next time WAIT
[Samsung Galaxy Nexus] DirgeExtinction:
*228 does nothing for LTE phones. I've heard it may mess up your SIM.
[Samsung Galaxy Nexus] AuthPineApple:
Anyone having a problem with Doubletwist? Can't get ANYTHING to play through doubletwist. Resynced and everything numerous times.
[Samsung Galaxy Nexus] lioryte:
Dudes, ya might fry your Sim calling #228. That's why. Y'all might wanna do a lil research before posting. Y'all gots a fancy google phone why ain't y'all using it to search before posting? This is xda Dev. You should post stuff like this in the general or q&a or even better nowhere

http://bit.ly/KMXXVY
[Samsung Galaxy Nexus] brooklyn718941:
Sorry if this was mentioned but Is it me or the speakers are extremely lower then ics??
[Samsung Galaxy Nexus] mark manning:
Yes download volume+ from the play store
[Samsung Galaxy Nexus] hedcayce:
Any thoughts on getting the vzw login client working? I tried a titanium of it that I had and it won't install at all. Just freezes. I kinda need my data widget.
[Samsung Galaxy Nexus] KJW979:
Well thanks for that info, can never learn enough.
[Samsung Galaxy Nexus] Vegasden:
Verizon upgraded their app, so even if it did work, there is no longer a data widget.

You could use the one in settings as an alternative.

I installed a new login (my backup didn't work either) and, like has been reported in numerous JB threads, it won't connect.

......
[Samsung Galaxy Nexus] J.Max:
The data widget has been retired by Verizon because it doesn't work right with the new data plans. A new one is supposed to be out soon though.
[Samsung Galaxy Nexus] anotherdroid:
only that... as also someone who has been flashing Android ROMs since 1956, the moment after you've flashed, you spend the next 6 hours dicking around with it.

i'm pretty certain it's just a safer burn time over 24 hours or so. and surely i never said "a few days". don't get dramatic on me ;)

---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------

sure feels/sounds that way to me...
[Samsung Galaxy Nexus] ktownhero:
Well, my phone is officially FUBAR because of this ROM or more likely the unstable kernel they decided to include with it. My speaker and mic stopped working, media no longer plays and I get major performance hiccups. I even did a full wipe and restored to my previous 100% smooth and stable AOKP M5 + Franco M4 but the problem still persisted. I went back to factory stock and even relocked the phone, still the same problem. Something that this ROM changed permanently affected my phone, so fair warning. I also tried all of the typical measures like fixing permissions and cleaning up root apps.

I know there will be somebody that replies to this thread claiming that it is my fault somehow, it's the internet after all. But I've been hacking Android phones for several years and am well experienced. This specific ROM/Kernel did something and I can't quite figure it out. Fortunately I'm within my 30 day window so I am able to exchange it for a new phone. I will be staying away from anything that isn't AOKP or CM from now on. I really appreciate that this team made a working ROM so quickly, but I'm not thrilled that I now have no sound on my phone except through headphones (not even my call speaker works). :(
[Samsung Galaxy Nexus] bL33d:
odin the phone and quit whining. i ran jb roms for the past 2 days and had my phone lockup and not get past bootloops and or the google screen i just used odin to fix it and im running liquid ics v1.5
[Samsung Galaxy Nexus] Deekayy:
I can't view my pictures via gallery. When I take an actual picture the gallery shows my old pictures again. But the problem persist after reboot. Any recommendations?
[Samsung Galaxy Nexus] mark manning:
Trinity kernels have color mod baked in. Super smooth too!!!

http://www.derkernel.com/jbtuna.php#

Under "experimental" tab
[Samsung Galaxy Nexus] ktownhero:
And there he is, "that guy", on the internet. I'm not whining, I'm informing. I've already restored to stock and locked the phone, all of the problems persist. People should be aware of issues that others are having, even if its not what you (or others) might want to hear. If I came on here saying hey this rom is awesome and I'm having no problems then I'd be a liar and would be doing a disservice to this thread.
[Samsung Galaxy Nexus] thelowend:
OK, informing done.

Would you like some help fixing your problem or are you moving on? Shame your experience was bad. Hope it works out.
[Samsung Galaxy Nexus] mark manning:
Your story sounds fishy to me. Tons of people soft bricked their phones and I even heard of the speaker cutting out once. However, everything went back to normal with a factory image. Not saying your lying but your claim is hard to believe good sir
[Samsung Galaxy Nexus] landrian18:
@deekayy, I had the same problem.. did everything except factory reset.. but I fix it by doing dirty flash...
[Samsung Galaxy Nexus] FlameEffex:
The only issue I've found so far is when I first installed it, the phone was REALLY laggy. I couldn't figure out what was wrong... I decided to Install SetCPU to see what my processor was clocked at since I had it overclocked on my previous ROM, and it was clocked way down to like 192Mhz for some odd reason. Kicked it up to 1000 to 1300 and bam, this thing is amazing :)
[Samsung Galaxy Nexus] zeke1988:
OP please put up a disclaimer to let people know.
[Samsung Galaxy Nexus] player911:
I'd recommend a superwipe. Sounds like something is carrying back with you. Superwipe should really nip it in the bud.

Hope this helps.
[Samsung Galaxy Nexus] Ohleo:
Still trying to figure out how to get good battery life tho.
[Samsung Galaxy Nexus] sway40:
Ok you know the warnings these devs give before you flash rom/kernels or anything else. This is the risk you take doing this, so yes it is your fault for flashing this and it causing issues, but it does suck and I've had the same problem on another phone before so some of us feel your pain.

Anything could happen or break while flashing stuff it's the name of the game...just be glad your in your return period, or have insurance like anybody should on a phone.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shiznu:
No the widget no longer works but here is a login apk you can try.

http://db.tt/cvrewzTn
[Samsung Galaxy Nexus] mursepaolo:
Better than faux?
[Samsung Galaxy Nexus] veloslave:
Wow....

THANK YOU!!!

I would nominate this to the OP for inclusion to instructions.

Unfortunately for me this success only lasted one or two uses... back to borked
[Samsung Galaxy Nexus] mursepaolo:
Ditto on this.

Just flashed latest faux and seeing if it'll do better.

I know with the amount of use I have, there won't be a kernel that will work wonders. Just hoping for the best and waiting for more releases!

This ROM is still running great though
[Samsung Galaxy Nexus] veloslave:
Know WHAT?

(Kettle calls pot black about not having a descriptive thread... :silly: )
[Samsung Galaxy Nexus] Zorachus:
Thanks, would be nice if it stayed in notification bar.
[Samsung Galaxy Nexus] hogowner:
Is it just me that has lower volume on jelly????

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Zorachus:
Not digging the white Google bar on top on each screen. Too distracting.
[Samsung Galaxy Nexus] gaming09:
running smooth, any idea what command besides time and weather get a response from the voice search
[Samsung Galaxy Nexus] aardvark502:
How tall is Kevin Durant
[Samsung Galaxy Nexus] fchowd0696:
"navigate to"

"nearest <insert place>"

basic questions like "how tall is the empire state building"

"set alarm"

"text<contact> <text body>"

"call<contact>"

just some of the one that are the most useful.
[Samsung Galaxy Nexus] Lincolnmking:
Looking good so far, notice "browser" is still the default browser. Guess Chrome will only be default on the Nexus 7.

Gonna miss some of the tweaks from custom ROMs, but Jelly Bean goodness, yummy.
[Samsung Galaxy Nexus] gaming09:
i dont believe mms is working

edit: MMS is working, apparently you cant send outbound when an inbound one is happening
[Samsung Galaxy Nexus] kkeller87:
Just flashed. Everything is glorious. What is everyone doing for contact pics. Haxsync doesn't work.

Like I said, everything is glorious. Amazing work to the devs that brought it to us in less than 24 hours.
[Samsung Galaxy Nexus] mordrukk:
Has anyone figured out how to enable the "Stay Awake" option under Developer Options?

Another interesting bug: in the notification pull down, instead of saying "Verizon Wireless" it says "T-CDMA 64".
[Samsung Galaxy Nexus] Snakehn:
Oh great i was enjoying JB in all of its glory and while on a call my phone muted on its own :(

i know this ROM is not official but i guess this particular issue is still not resolved.
[Samsung Galaxy Nexus] tacosrdelicioso:
The only thing I want is scrolling cache disable
[Samsung Galaxy Nexus] philsfan:
Haxsync works fine for me...
[Samsung Galaxy Nexus] 1.4hitachi:
Wow Jelly Bean in less than 24hrs? Awesome!
[Samsung Galaxy Nexus] Santinelli:
FYI!!!

If your having issues with WIFI, Go into Wifi settings, and choose Advanced. Turn OFF Avoid Poor Connections.

Found it kept dropping my connection because of that... :)
[Samsung Galaxy Nexus] ethatch2100:
Have you tried switching channels for your 5 ghz network who knows just a suggestion
[Samsung Galaxy Nexus] metasage:
As the OP suggests, WiFi signal is significantly weaker. I went from Good to consistently Poor. Turned off Avoid Poor Connections to keep Wifi from dropping, but still a very weak connection. EVERYTHING else is working flawlessly so far.
[Samsung Galaxy Nexus] truelove79:
Is this 100% stock?
[Samsung Galaxy Nexus] J33per:
Thanks for the super fast port! This is why I love Android!

I do get a force close when I try to go into mail after setting up an Exchange account, has anyone else setup an Exchange Mail account successfully? Might do a re-flash just for kicks.
[Samsung Galaxy Nexus] ztkryan:
Was def fun to play with jelly bean I can't live without the akop stuff however:p so I had to restore my nan
[Samsung Galaxy Nexus] ianflo:
had some weird problems running faux. there was no rhyme or reason as to why, but my phone would occasionally shut off and wouldnt wake back up. pressing the power button did nothing also, not until i did a battery pull then reboot as normal.

went to linaro and things have been better (similar to franco 210 but definitely better than the stock included)
[Samsung Galaxy Nexus] mark manning:
that people somehow find a way to screw their phones up quite easily would be my guess...

I personally, can't figure out what they are doing or are not doing. Rom works perfect for me and have never had a single problem. I used the instructions I posted in the op and everything's great. I have found that when people assume they know everything because they have been flashing for years they are typically the first to mess up. Where as noobs are scared so they follow instructions to the T.
[Samsung Galaxy Nexus] jonstrong:
Definitely a fan of "search before ask", but the idea of #228 frying a SIM in one of these new devices is really not a concern at this point. Some knowledgeable (2nd level) VzW support folks have chimed in recently in other forums noting that this currently has urban legend status, and that they're still frustrated to learn that various level 1 CSR's continue to spread this story as fact.

Related item: #228 is still not the preferred way to update an LTE PRL. As dopey as it may sound, latest info from VzW is that you should pull both the battery and SIM and then replace them in order to force the device to request an updated PRL. Related experience: a couple of months ago I was traveling from the US to Canada, and knew I'd need to refresh my PRL on arrival in Canada. The first VzW CSR I spoke with while in the US told me to use #228 when I powered up in Montreal. I tried several times - and could not properly roam on the Montreal carrier. BTW: dialing #228 directly did nothing -- I had to assign it to a contact name and save it, and then "dial" the contact -- but even doing this, I was unable to authenticate on the Montreal carrier.

I called VzW, got level 2 support and could almost hear the sigh of frustration as this guy patiently told me that #228 is NOT the right approach for an LTE device. He told me about the battery and SIM pull. I did this, and was immediately able to authenticate on the local carrier in Montreal as a roaming user. Also noted that I had a new/different PRL.

Interestingly - the battery pull wasn't necessary on return to the US (Newark, NJ). On arrival, I powered up the phone, apparently got an updated US PRL immediately, and was just fine.
[Samsung Galaxy Nexus] veloslave:
Just discussing... not trying to pick a fight, really.

Considering that you are the only one I have heard of having this issue... no I do not everything or everyone but I do eat and sleep this stuff and I have NOT heard of a bunch of people having messed up hardware... you are the first.

So.... maybe it is just a bad piece of hardware??? It does happen you know.

Seems to me, given the amount of evidence that is LACKING to indicate software damaging hardware (which is very hard to swallow on theory alone) that the "gun has been jumped" on crying fowl here.

Use your warranty, give it another try... if it is true (and it would take more than two instances to make it so) than you are a hero for bringing it to light. If not... maybe you need to admit it.

If you have had a chance to think this over and have cooled off a little... what are the real "odds?" What would you bet your months paycheck on?

Hardware failure

or

Software damaging hardware

Let's keep it friendly ya'll
[Samsung Galaxy Nexus] metallicant:
Even though you get the unsupported device message the app should still work. If you want to get rid of that annoying message all together run Google Wallet and go into settings, and reset the app. Next go into Root Explorer app and find and click on the system folder, then click on app, find Google Wallet and delete it all together from the app folder. Next do a search for Modaco's patched Google Wallet version 1.1-r67-v5.apk. Once you download the file copy and paste it in the app folder (push the .apk) then viola your good to go.
[Samsung Galaxy Nexus] DirgeExtinction:
Loving this kernel. :D