I am currently running mahdi ROM and was experiencing 2 flickering black lines across the screen. I read on the development forum of someone else experiencing anomalies like this and it was recommended the ROM be updated. I have updated to the latest version build 2.8-bacon-20140924 and kernal 3.4.0 dated 21/9 but the Flickering it still there. Any permanent fix for this that you know of? Unfortunately I can't post on the development forum. Cheers.
Update the kernel to a custom one such as Franco or AK and see if the same problem occurs.
I changed to AK kernal and that has sorted the problem. Don't know why the stock kernal was causing an issue though. Cheers.
Related
First of all, Ive searched regarding this error a lot and am hoping someone can clarify.
I "mistakenly" updated to the stock kitkat 4.4.2 that was released for the Galaxy s4 recently and after realising how crap it was, i installed a recovery manager and loaded on the Google play edition rom by Danvdh
http://forum.xda-developers.com/showthread.php?t=2539361
The rom works great and for the most part my phone works. But every now and then randomly it reboots and then will show Kernel is not seeandroid enforcing. Im assuming the error is due to the fact that I installed stock kitkat.
Am I able to circumvent this error by installing a different kernel? and Is the error related to the random bootloops?
Any help would be much appreciated.
Daikonran said:
First of all, Ive searched regarding this error a lot and am hoping someone can clarify.
I "mistakenly" updated to the stock kitkat 4.4.2 that was released for the Galaxy s4 recently and after realising how crap it was, i installed a recovery manager and loaded on the Google play edition rom by Danvdh
http://forum.xda-developers.com/showthread.php?t=2539361
The rom works great and for the most part my phone works. But every now and then randomly it reboots and then will show Kernel is not seeandroid enforcing. Im assuming the error is due to the fact that I installed stock kitkat.
Am I able to circumvent this error by installing a different kernel? and Is the error related to the random bootloops?
Any help would be much appreciated.
Click to expand...
Click to collapse
Hi,
Generally you must flash the same kernal which has come with the installation ZIP, Please check if you are using a different kernal and the ROM.
This happened with me , as i was using a CWM nightly Kernal with a PAC ROM, which didnt worked for me.
It worked when i got a Kernal build by the PAC itself.
Hope this might answer your query
atuldarne said:
Hi,
Generally you must flash the same kernal which has come with the installation ZIP, Please check if you are using a different kernal and the ROM.
This happened with me , as i was using a CWM nightly Kernal with a PAC ROM, which didnt worked for me.
It worked when i got a Kernal build by the PAC itself.
Hope this might answer your query
Click to expand...
Click to collapse
Well I havent changed anything yet. I am using the same kernel that came with the Google play rom that I installed.
The first touch screen issue fix was rolled out with Nightly 20150715-NIGHTLY version, which solved the issue, but had battery drain and heating issues. Then they removed the synaptic fix in 20150718-NIGHTLY update. Later they cam up with fix again with 20150721-NIGHTLY update, where the battery drain was less.
Then the fix was released with AK V-246 (http://http://ak.hiddenbytes.org/) and FrancoR43 Kernels, also Boeffla Kernel (3.0beta3) (For Oxygen OS users ONLY).
After that, god's grace, we got Official Oxygen synaptic fix, where there was less battery drain and heating issue. And then we got finally YNG1TAS2I3, where seems like everything is fixed.
So, now if I flash any other ROMs than these two stocks, how I can fix my touch issues. ROMs flashing over NIGHTLY will have the fix came along with 20150721-NIGHTLY, but what if I want to flash other ROMs like MIUI or COLOR OS or any other which can not be flashed over NIGHTLY? Are there any Kernels which got best fix over this issues, which got the similar Touch fix as in stock CM12 latest update?
All of the cusom CM12 & CM12.1 kernels have this fix. Unfortunately not sure about MIUI and KK Roms in general.
I noticed some strange behaviours these last days on my rooted mi4i.
Sometimes when i get a notification and i try to wake the phone from standby it takes forever or I find out that it shut down all by himself.
Someone know what could cause this?
please be more spesific what your currently rom and/or maybe you flashed custom kernel or anything
i had experienced something like this with custom kernel and custom rom.
Danusyakti said:
please be more spesific what your currently rom and/or maybe you flashed custom kernel or anything
i had experienced something like this with custom kernel and custom rom.
Click to expand...
Click to collapse
I am also facing a similar issue. I was earlier on the AOSPA rom with a custom kernel when this started. I the UBER rom after a clean wipe but the problem is still there.
Please help, I am a noob here.
fadnavismehul said:
I am also facing a similar issue. I was earlier on the AOSPA rom with a custom kernel when this started. I the UBER rom after a clean wipe but the problem is still there.
Please help, I am a noob here.
Click to expand...
Click to collapse
clean install again without custom kernel
The problem is that I've never flashed a custom from neither a custom kernel.
Now I've unrooted the phone and it's not happening, but I'd like go know what it's the source of the problem.
Same problem happened to me
This is regarding my nexus 5, I have been facing some serious heating issues with it,I am running android 5.0 rooted and elementalx kernel.
Would be helpful if someone could help fixing this.
Same thing happens on stock rom and kernel? Possible defective battery? When did the issue start?
Since I've switched back to stock ROM along with elemntalx kernel the device heats up over WiFi and 3G.Do you think it could be due to the stock ROM or the combination of stock ROM and the elemental kernel?
I would think it is the kernel that is the issue. I use stock mm on mine and no problems with heat.
I was wondering if anybody knows how to replace a kernel from a build of cm12.1 to another build, im asking this cause latest build of cm12.1 by the marionette the kernel works great on my device no random reboots really fast, but the only problem is that camera is not working, so i wanna try previous build with the latest kernel, since i tried that build and the camera was working but i got random reboots. hope you guys can help me out