[ROM] Android Open Kang Project- Jelly Bean Style

No lockscreen targets, yet? Bummer. I really liked build 2 otherwise. Hope it's on their to-do list.
 
Greetings wise and all-knowing crack flashers! I come seeking counsel.

Yesterday I did a clean install of AOKP release 3, coming from Euroskank Jellybro. I had tired AOKP release 1, had a few issues, and went back to Skank.
At first, everything was GREAT! I could tell that there had been marked improvements from 1 to 3, everything was extra buttery and smooth, and I really felt like this was going to be my daily driver for a while.

Then, this morning happened. I took my phone off the charger at 4am, and it was unresponsive (the power button wouldn't wake it). Had to do a battery pull to get it to reboot. After the gym, around 6:15, the same thing, had to actually do 2 battery pulls. Then, just now after getting to work, I had the SAME THING happen, had to pull the battery.

Now, I played with this extensively last night with zero issues, but maybe since I was setting everything back up it never had a chance to go into this unresponsive state. As I mentioned, it was a clean install- wiped data, cache, Dalvik, and system, flashed JB Bootloader, flashed the ROM, flashed GAPPS.
I want to like it, AOKP ICS M3 was my first custom ROM, so it holds like a high school sweetheart kind of place in my heart, but I can't live with this...

So, has anyone experienced this? Is it maybe a kernel issue? Any help, as ALWAYS, is much appreciated...
 
I just woke up and found my phone unresponsive. It wasn't until my third battery pull that I got the phone to wake (I was starting to get nervous). I did a clean install of AOKP B3 yesterday as well. Still the stock kernel, is that the weak link here?
 
Brianr and Ottscay - I'd definitely try another kernel. Give francos nightlies or even milestone 5 a shot. Flash it via his app or someone can hopefully provide a link, I'm away from my computer right now :)

Sent from my Galaxy Nexus using Tapatalk 2
 
Thanks guys - I actually had Franco M5 stored on my phone, I just like to give stock kernels a shot for a day or two as a baseline - so I flashed it shortly after reading this. But I appreciate the link and feedback very much.

Everything seems fine, but then everything seemed fine last night when I went to sleep,so we'll see.
 
I flashed Franco almost immediately after flashing B3, so unfortunately I can't replicate your guys' issues. That said, because I can't do so, and the difference appears to be kernel-related, I would definitely give it a go.

Either the nightly r275 or the M5 would work.
 
I did a clean flash of build 3 (as well as Franco M5), and battery life seems kinda disappointing. I don't think its necessarily the ROM or kernel, though, because I recently had started noticing that on CNA 3.5 (with Trinity kernel). I'm thinking maybe it has something to do with the last set of radios that came out? I flashed those, and while I can't remember for sure, that might be about the time I started noticing battery being a little worse.
 
I've clean installed build 3. Can I now flash the JB bootloader with no issues? What will I gain by doing this?

Sent from my Galaxy Nexus using Android Central Forums
 
I've clean installed build 3. Can I now flash the JB bootloader with no issues? What will I gain by doing this?

Sent from my Galaxy Nexus using Android Central Forums

You'll gain having all of your software line up--it'll all be 4.1.1.
 
Brianr and Ottscay - I'd definitely try another kernel. Give francos nightlies or even milestone 5 a shot. Flash it via his app or someone can hopefully provide a link, I'm away from my computer right now :)

Sent from my Galaxy Nexus using Tapatalk 2

I've got the Franco App, I'll give it a shot. Thanks.

EDIT: on the nightly downloads, it asks me to choose between 384 and 512 mhz GPU. Need a little guidance here... :-)
 
I usually go 384, but 512 won't hurt. I don't think you'll see a big difference in speed/performance. 384 is safer, but if you're feeling lucky --and often times, I am-- go with 512.

EDIT: if you see any wonkiness on 512, you could always reflash and choose 384 to see if that helps.
 

Latest posts

Trending Posts

Forum statistics

Threads
956,767
Messages
6,969,939
Members
3,163,614
Latest member
Stephenb1979