First alpha of M-Kernel plus available in the OP. :victory:
Thx! Running it on PA 2.20 with no problems. It seems that I don't have no more problems to reboot (before, I could stay stuck on Google screen...)
I'm already wiating for a 520MHz version !!
Thanks. I do need time to make sure it is stable and to see how battery life/performance is before I start adding more GPU options.
Lots of little patches and fixes here and there, but I need to see how the LP overclock affects things. Also need time to get feedback that isn't just "I flashed it and it didn't bootloop/break my device" ...although it is good to know haha.
Sent from my Nexus 7 using xda premium
Well, let's see, here..
Last night, I was getting stuck on the Google screen a lot - even in situations that made no sense. For example, I flashed PA2.2, then flashed the ramdisk you sent me, then flashed the mc446 and it got stuck on the Google screen. THEN I flashed PA, booted it up, then flashed the ramdisk and mc484 and it worked. THEN I flashed mc446 and it worked for one reboot but the reboot after that resulted in stuck at the Google screen...
So, today, I flashed PA2.2, then rebooted, then flashed the ramdisk you sent me yesterday, then the mc446 kernel and it booted right up.
When you announced the alpha, I loaded it right up and it's running great
All of this is undervolted -75mV @ 100-1300, interactive/deadline
Seems like it's happening to people running PA. *shrug* I don't know. I did my testing on the rooted 4.1.2 OTA and never experienced this. .
Hopefully it doesn't happen again with the alpha.
Sent from my Nexus 7 using xda premium
I've rebooted with the alpha several times and no issues...
Okay, so here's what would make sense for me:
I'd rather not have people flashing ramdisks here and there. The whole point of Koush's AnyKernel is that you can replace the kernel and leave the rom's ramdisk intact. I don't really see the benefit to having all these different ramdisk packages.
Sent from my Nexus 7 using xda premium
got a problem to report..
when i did a shutdown (by pressing the power button and selecting power off), the device shut down apparently normal..
however, when i tried to turned it on, it just stayed at the screen with google text and the unlocked icon (first boot screen)..
waited for 10 minutes and nothing happened.. at this point i pressed and held the power button for a few seconds and the device booted up normally..
tried 3 times and all got the above behaviour..
then tried 3 times to shut down, enter CWM, and reboot from there.. same problem..
my device is stock 4.1.2, with m-kernel (484 MHz) as well as FishingFon's circular battery mod applied..
also had a custom bootanimation at /data/local/
---------- Post added at 01:09 AM ---------- Previous post was at 12:45 AM ----------
flashed the stock kernel available in the first post, rebooted twice and both times the problem was gone..
err.. i guess probably my post got misunderstood..
i meant i reverted to stock kernel by flashing the zip file provided in the first post (but its now removed from the post, which i think should be kept in case any one wants to return to the original stock kernel), and the device booted up without problem..
however, my problem with M-Kernel (getting stuck in google screen) remains..
btw, i did not flash the kernel with init.d support.. not sure if this will cause problem as its optional as stated..
So, you can boot on the stock kernel no problem, but the M-Kernel sticks you at the Google screen?
Try flashing the stock kernel with init.d support, then flash the m-kernel of your choice. See what that does for you
So, you can boot on the stock kernel no problem, but the M-Kernel sticks you at the Google screen?
Try flashing the stock kernel with init.d support, then flash the m-kernel of your choice. See what that does for you
I flashed the kernel with init.d support first but was hung at Google screen the method I posted above is what fixed it for me.
I'm on stock 4.1.2 rooted and I was stuck at Google screen as well. What I did to fix it was:
Cleared Cache
Cleared Dalvik Cache
Flashed the 446 (not alpha)
Cleared Cache
Cleared Dalvik Cache
Fixed Permissions
Afterwards it booted super quick, and it has continued to boot since then as well.
Right on.. I think it might be a fix permissions issue. From what you've said so far, you're running the 446 kernel with the stock+init.d ramdisk. I'll almost guarantee the fix permissions is what cleaned you up, as that's about the time my problems stopped as well
Just curious, does overclocking the LP core affect overall device performance? It was my understanding that it's only active when the device sleeps, watching videos etc. Or is it in use when total cpu usage goes below a certain threshold?