Since I cannot post in the other forums, I will post this problem in here.
I flashed AOKP Build 23 Wednesday and ran the stock kernel that came with it with no problems all that day. Then yesterday I flashed Franco's 17.1 and purchased and installed the Franco Kernel Updater and set the governor to the turtle governor and within just 3 hours I had 3 reboots.
I thought maybe it was a governor issue and I tried changing from the turtle governor to the the interactive and as soon as I did then the phone rebooted and got stuck at the Google screen. I got into the stock recovery and then rebooted into CWR flashed back to my last good image of AOKP build 23 I made right before installing the Franco Kernel and Kernel Updater.
Is anyone else having any issues with the 17.1 or the updater app?
Guess it must just be me then.
Related
I couldnt post in the kernel thread because I don't have enough posts yet..
I installed clean Rom a month or so ago and have been updating to the new versions ever
Since, everything had been running perfectly on the stock kernel. I got the itch to try a new kernel and
decided to try out the elemental kernel (later tried the beast mode as well). Ever since I flashed the new
kernels in recovery my phone keeps stuttering and the screen jumps a bit every couple of seconds, also the
browser keeps reloading when I am on google.com.
I have tried flashing both kernels with different options as well as clearing cache before and after flashing, plus
fixing permissions but the problem continues. I also did a factory reset and reinstalled clean Rom and both kernels.
Has anyone had this happen to them before and know of a solution?
Thanks in advance.
Are you overclocked? Not every phone can handle oc'ing.
No. At first I tried the kernels with the oc to 1.7 option, but then I tried both kernels with no oc, no gpu oc, no sweep to wake, and no
Under volt but the screen kept flickering and the apps kept having hiccups.
I flashed the stock kernel from viperxl and now the phone is back to normal.
I am on 2.20 with the hboot 1.14 by the way.
Hello, some of you might recognize me as the one who was having trouble installing PA last night.
Now I've got it installed, and it runs very smoothly.
Specs off the bat...
TF700T Infinity
VoltageControl Overclock system set at 370-1800
Very latest gaps, installed last night from g+
MaxKernel V4 Reloaded RC2
Installed and flashed through TWRP
ParanoidAndroid 3.15
Likely enough for myself, all of a sudden, a few hours into having the ROM, kernel and gapps freshly flashed, the screen starts giving random graphical flashes and blips here and there, and it's grown to a point where I can't use my tablet without a flash every three seconds.
To explain exactly what is happening, when I switch from app to app or UI section to another UI section or any of the mix, it will brightly flash what I am switching to/from while I do it. For example, I will be opening up PIE and it will flash the app screen in full for a split second if PIE is over it.
Anything that I am doing wrong? I have a restore from a few hours ago set up, will I have to use that?
If anyone has any advice/assistance, please let me know.
Thanks,
Neb
EDIT: I tried resetting the overclocking system to stock clock. No change whatsoever.
Also did a restore. No luck
Turn off the corresponding setting in the developer options.
Also Max's kernel is a stock based kernel. I'm surprised PA even boots off it. I'd switch to a PA compatible kernel of I were you.
Thank you for helping me out on this. I saw some posts stating that Max was a PA based kernel. My bad. Got it taken care of by reverting to PA stock kernel
I bought the FKU app and I've been using it with the kernel updates for a good amount of time, but now I installed AOKP and used the app to auto-flash r34 and I got stuck at the the Google with the open lock screen. I thought it was a corrupt download or something, so wiped it and installed r33 from franco's archives. Same thing. r32, same thing. I even installed CM11 and retried and got the same result.
If anyone is having the same problem let me know!
Franco's kernel does not work with CM11 anymore, it's written all over Franco's kernel thread.
I'm not sure about AOKP, but if it's based on CM11, or if they went the same road as CM, that will not work as well.
I recently installed franco.Kernel R15 on my stock OPO with TWRP and I noticed when I plugged in my headphones, there is a full second delay of it being detected (this was also present on R14). Is this normal? This occurred on several other kernels on my OPO as well such as stock Mahdi's, stock CM11 M9/nightlies, and so on. I've tested these combinations and are without the aforementioned problem, PA stock, Franco R13 on all the ROMs I've tested with (PA, DroidKang, Mahdi, CM11S), CM11S stock.
This issue is definitely related to the kernel and I have tried to flash the official recovery image and same results after flashing franco kernel R15. And I would inquire about this in his thread but as of now, I'm not eligible to do so.
Thanks for the help! Cheers!
No one?
Hello everyone!
I apologize if this is a poor quality post as it's my first, but my issue is pretty much as it says in the title. I'm currently using an SCH-i535 with CyanogenMod 12.1 nightly 9/6. I want to give the latest DKP kernel a go as I've been experiencing some force reboots, and would like to over and underclock my phone a bit as I did with the BMS kernel when I was on Android 4.4.1.
I downloaded the kernel from decimalman's thread and renamed it to dkp-min-1050.zip. When I flash it in CWM Recovery Touch 6.0.4.5 (after clearing Dalvik and cache, of course), I get a message that the new minimum voltage is 1050 mV, which is expected, but my phone still declares it's running the cyanogenmod-g6bceda8 #1 kernel and Adiutor doesn't give me any CPU speed or governor options that aren't included in CM 12.1 by default.
So, essentially, it doesn't seem that the kernel is actually being flashed despite my recovery saying it flashes successfully. Has anyone encountered this before or notice anything I'm doing incorrectly? Thanks so much in advance for your help!