Sent from my SGH-I777 using xda premium
I flashed his Firmware which was working ok except root being messed up. However after I flashed this kernel it just sits on a black screen after the samsung screen. I had to restore a previous back up. Something in my configuration is not right.
P.S. I am using the sammy kernel.
P.P.S. Oh whow some how the leak that I was flashing was LC2 no LD3. Have to pay more attention.
Like I said feed back don't take it personal.let's just stick to giveing feed back on this kernel and not have you get all sensetive like a women. All I said was that the battery life seem to be going very fast that is my experiance you don't like it then that is your problem. So I will leave it at that you move on
Sent from my SGH-I777 using XDA
I installed this kernel last night right after release on AOKP, and didn't have any issues, except for a SOD after I set the minimum clock speed to 100MHz. Since I'm waiting on an important phone call (family member on his deathbed), I swapped back to Siyah for use overnight, just so I wouldn't miss any calls or my alarm for work. Now that I'm at work with a spare phone, I reinstalled the NEAK kernel (after running the kernel cleaning scripts AND manually clearing caches through recovery), but I've run into an issue and I'm wondering if anyone has any ideas as to what could be going on. When I reboot my phone, if I don't immediately unlock the screen and keep moving between home screens or provide some kind of phone input, the phone will completely freeze during the process where it checks the SD card for errors. Once that notification goes away, I can let the phone sit and everything works as normal, but if I leave the phone alone after a reboot it won't finish the error check and I have to power off the phone manually and power it back on to get it working again.
Here's what I've tried.
I removed all of the startup tweaks.
I disabled the CPU settings
I repaired permissions through recovery
I rebooted without my SD card installed.
Cleared caches (regular and Dalvik)
Nothing has seemed to fix the issue. Since it's more or less a "minor" bug (only happens during a reboot), I can live with it, I just have to remember to keep the CPU active during startup.
|best kernel, blazing fast|
|Thread Tools||Search this Thread|