[abqnm]

Jake, is this the stock kernel or what kernel is included?

Sent from my brain using human to phone transport technology.

 

[abqnm]

I was having the deep sleep issue. Better Battery Stats indicated it was gps-lock holding the wake lock. Opening the free app GPS Status and letting it download a-gps data and lock for the first time (takes a while) caused the wake lock to go away. Sleeping normally now.

Sent from my brain using human to phone transport technology.

 

[abqnm]

Just some information in case anyone sees this. If you reboot/boot up and the phone seems stuck at the Google logo for a long time don't worry too much. At random boots it seems to take a very long time to get to the boot animation. This has happened on all JB roms I have tried. It will boot from here but it may take a long time. In excess of 5 min long. So if this happens to you, just set it down and walk away. Go do something else and come back and it will have booted. Paranoia can set in if you sit there watching it stay on the Google boot logo for a long time.

Sent from my brain using human to phone transport technology.

 

[abqnm]

Yep, this is an easy fix. I'll have it in 1.4 when I get home in a bit.

Sent from my Galaxy Nexus using RootzWiki

The odd thing is that it was working fine an hour ago. Now it is off. Also there are a lot of reports of the exact same thing happening in the AOKP thread. Wonder if something is screwy network side...

If so, I guess I should hang out on reddit today for the inevitable pictures of idiots blindly following their gps into places cars shouldn't go.

Sent from my brain using human to phone transport technology.

 

[abqnm]

Jake,

It seems that init.d is not functioning. Do you see this as a possibility in an upcoming release? With JB, apps like SetCPU don't work because the app writes to sysfs and leaves the permissions at 0666 and the OS reverts them back to stock after a minute or two or anytime the screen is off. After setting them, we have to change the permissions to 0444 so the OS doesn't revert them. This means for now the best solution is an init script but they don't seem to load even with the proper permissions on the script. Right now I am just manually running it as a shell script after boot but would love to be able to have it automated.

Thanks for the awesome work as always, sir. Cheers!

Sent from my brain using human to phone transport technology.

 

[abqnm]

I believe the init.d issue comes from the stock kernel being a secure kernel...popcorn kernel only attaches to the stock ramdisk so it would also probably be a secure kernel as well

Understood. Just posting here to see if it may be changed for a future release.

Sent from my brain using human to phone transport technology.

 

[abqnm]

Do I need to flash this with the Touch version of clockworkmod recovery only?

I used TWRP just fine. Not sure about regular CWM though.

Honestly if you haven't tried TWRP it is fantastic. So many options and easy to use. Backups complete in about half the time of CWM as well.

Sent from my brain using human to phone transport technology.

 

[abqnm]

is Apex working?

No. Force closes on launch. The dev will need to update it. Nova works though.

Sent from my brain using human to phone transport technology.

 

[abqnm]

I had an issue where I swapped a fresh battery into my phone, and lost 4G when I booted back up. 3G worked fine when I changed the network mode, but when I changed it to LTE/CDMA I couldn't connect at all. I powered down, pulled the battery again and made the sure the SIM card was seated right, and powered back up and 4G worked fine again.

I am having an issue connecting to BT Audio in my car. It'll connect, give me the confirmation, and then immediately drop the connection. Is anyone else having an issue with BT?

Can't speak to the BT issue but as for the loss of 4G, I have that happen periodically on just about every ROM including ICS. Usually just a reboot will bring it right back.

Sent from my brain using human to phone transport technology.

 

[abqnm]

Just to note for everyone, I had already fixed the issue that other JB roms are having with some recoveries and boot loops. With my Jelly Belly ROMs, you can use whatever recovery you want, make and restore backups, etc. No extra script flashing required. It's all good!

Thanks. I wasn't sure about the recovery issues but the boot issues are definitely gone. No more 5+ minute wait at the google boot logo. Awesome work! I have been advocating this in the kernel threads since a lot of people believe it is tied to the kernel.

Sent from my brain using human to phone transport technology.

 

[abqnm]

thanks for the quick replies everybody! now i just gotta decide whether to flash 1.3 or wait for 1.4 decisions decisions

Go for it. Unless you are concerned with bandwidth. Since this is for all intents and purposes stock and there won't be framework changes it is easy to flash the new one without having to worry about wiping.

Sent from my brain using human to phone transport technology.

 

[abqnm]

I'm curious as to this too (mostly because I'm one of those that always wipes when updating even for minor things)
And second, is there any real reason behind separating gapps??? I know Google doesn't like roms that include them but this really isn't a normal rom, all the jb "roms" are nandroid hacks (not built from source) so it shouldn't matter and doesn't separating them increase the risk of something getting broken?

It is just more of a formality and also compliance with RootzWiki policy although that doesn't seem to be enforced much anymore. As long as you flash the right gapps immediately after flashing the rom it shouldn't increase the chances of anything breaking as they all wind up in the same place anyhow.

Sent from my brain using human to phone transport technology.

 

[abqnm]

Google Play Music isn't seeing any of the songs on my phone. Any ideas?

Sent from my Galaxy Nexus running Liquid Linaro 1.5, 4,000+ Quadrant Scores!

For local files not displaying I would download the free app Rescan Media from Play. Run it and wait a few min depending on how much music you have and then try again. If it is server side, go to settings in Play Music and choose refresh.

Sent from my brain using human to phone transport technology.

 

[abqnm]

Should we flash gapps on every update?

Yes or you will not have them. The rom formats /system so you need to do it each time.

Edit: ninja'd

Sent from my brain using human to phone transport technology.

 

[abqnm]

Loaded 1.4 ...everything seems peachy except it still displays T-CDMA 64. Minor, but annoying. Thanks for all the hard work!

Try turning off the phone and removing the SIM and then booting back up with no sim. Then power down again and boot with the SIM installed. It should re download the prl and update the eri and show Verizon.

Sent from my brain using human to phone transport technology.

 

[abqnm]

Gonna give this one more shot lol. Any help would be appreciated.

Sent from my Galaxy Nexus running Liquid Linaro 1.5, 4,000+ Quadrant Scores!

I have sounds in the same place as ICS and they show up.

/sdcard/Ringtones
/sdcard/Notifications
/sdcard/Alarms

Sent from my brain using human to phone transport technology.

 

[abqnm]

Unless it got broken between 1.4 and 1.5 then yes its working just fine here

Do you have a tethering plan or has it been modded to remove the restriction? I am not at my PC but that would make my day if it works without a plan.

Sent from my brain using human to phone transport technology.

 

[abqnm]

Those with an R instead of 4G, did you have T-CDMA 64 as the carrier name instead of Verizon Wireless? Sounds like an eri issue still.

Sent from my brain using human to phone transport technology.

 

[abqnm]

gapps: http://www.mediafire...2ubsgwf5y6n41ek
jb 1.5: http://www.mediafire.com/?0ec0smcd9vwfa4x

Also... is it still a bad idea to restore with TiBu?

Tibu should be fine. Just don't restore any system data. Apps and app data should not hurt anything.

Sent from my brain using human to phone transport technology.

 

[abqnm]

SIM trick didn't help either. Still seeing the "R". Weird. No biggie, but just a little annoyance.

I am hesitant to recommend this since I will probably get flamed for it but you could try a manual PRL update by dialing *22899. Many people still believe this will fry sim cards but that hasn't been the case since about a month after the Thunderbolt launch.

Sent from my brain using human to phone transport technology.