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?
Related
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 flashed Cyanogenmod 12 on my GPe 5.0.1 converted XT1033 using Phillz Touch Recovery and then flashed Donkey kernel.One of my sims is working and all other features are also working but "WIFI is not TURNING ON".It gets stuck on "TURNING ON" and doesn't open.I have tried reflashing CM12 as well as DOnkeyKang kernel but doesn't work.
Please Help.
modifan14 said:
I flashed Cyanogenmod 12 on my GPe 5.0.1 converted XT1033 using Phillz Touch Recovery and then flashed Donkey kernel.One of my sims is working and all other features are also working but "WIFI is not TURNING ON".It gets stuck on "TURNING ON" and doesn't open.I have tried reflashing CM12 as well as DOnkeyKang kernel but doesn't work.
Please Help.
Click to expand...
Click to collapse
1). There is a Q&A subforum where this question should have been posted. No offense.
2). The size and colors, just, why? You have a problem with your eyes or something? (< this is a serious question)
And, this is because CyanogenMod has changed the way the kernels are built, kernel modules are now built into the kernel; DonkeyKang (and almost any custom kernel) loads the kernel modules from files. Which, in my opinion, is the stupidest change ever made in CM.
And the Wi-Fi support on the kernel was provided by a kernel module; from which CM12 has disabled the "loadable modules support" and has been now integrated into the kernel.
In short: You will have to wait until the kernel author corrects this, or use a older CM12 version, older than 08/01/2015. On that, you will be able to install your custom kernel.
Okay Thanks!!
That's all I wanted to know...I'll install a Nightly released before 8th Jan.
Hi all,
Was wondering if anyone else is experiencing the same problem? My OPO has no backlight after it boots up. The backlight is fine during the initial boot up (the powered by android page) but it disappears right after that page. Everything else works fine! How do I know? I shine torchlight onto the screen and I can see the LCD pixel to be working but NOT the backlight. Any help? Thanks!
Unlocked and rooted with CM12 nightlies installed before backlight disappeared. Done everything suggested for corrupted memory, bootloop, hard bricked etc. I am currently on stock unrooted CM11s with stock recovery.
How did you flash CM11S back onto your device?
Transmitted via Bacon
Fastboot mode, unzipped CM11S and flash images.
You flashed everything from within the stock image zip?
Transmitted via Bacon
Yup I did. I followed the exact instructions for changing from colour OS to cm11s, I reckon that is the best way to restore the OPO to original state.
It definitely is. Seems like it's possibly a kernel issue, have you tried a custom kernel to see if it changes the situation?
Transmitted via Bacon
Sigh I tried both franco and boeffla and it still does not work. Thanks anyway!
If not working, I suggest you flash Calkulin's Stock CM11S XNPH44S. It's all stock with root. I always use this build when I need go back to stock, saves all fastboot hassle.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph44s-t2932551
That was what I did before creating this thread. Maybe I should play around with other CM11 roms+their other kernels see which one works
Does the backlight work in recovery?
And I assume (sounds like yes) you did a full factory reset?
Once had a similar problem caused by an 3rd-party app that controlled the backlight. If you did a factory reset that shouldn't be the case, though. logcat?
I tried franco and it works! Not sure why though. At first I was having system ui fc which is a bug with r37+cm12 roms. I reverted to cm11 roms+r37 and it worked. Still, no backlight while booting though, but the backlight turned back on once it finishes booting up. Thanks all!
Hello,
I searched for this issue but couldn't find the exact problem being experienced by others, so I'm asking about it now.
So I'm using the latest MultiROM and Lollipop firmware (the 02/09 one). I simply can't get any Lollipop ROM to stop bootlooping with a recent kernel. Boeffla, AK, Tyr, etc. all bootloop with every LP ROM I've tried, regardless if they're set as primary or secondary in recovery.
The only way I can get a ROM to boot is with a kernel meant for CM11/S, like AK r77 and Sensei r77, though I can't get the radios to work with these. But newer kernels simply won't work, period.
Am I missing something here? I thought the latest firmware and a recent kernel with kexec-hardboot was all I needed.
Edit: Also seems to happen with a fresh install of the latest CM nightly. Using the default kernel that comes with CM, too. There must be something that I am missing here...
Hello,
I am facing a weird problem regarding the proximity sensor on all CM11 roms.
I was using lollipop roms for a long time now, and have been following latest builds, until I decided that I liked KitKat more. I already had a backup of temasek's last CM11 build, so I reverted to that one, after flasing the cm11 firmware. All was working perfect until I reverted a backup of my 5.1.1 rom, to try xposed. Again, before doing so, I flashed the latest cm12 firmware. After a couple of days experimenting with xposed, I eventually went back to my kitkat rom. After boot, I noticed that the proximity sensor wasn't working. I had already flashed the cm11 firmware before restoring, but I went and flashed it again. Problem was still there. I then tried cm11s 44s firmware, 05Q firmware and 05Q modem only. The proximity sensor problem was there in all cases. (Shows 0.0cm, like I always have my phone in my ear or pocket). I then tried flashing a complete cm11s rom (05Q) with no success.
This is not a hardware problem, as the sensor is working FINE on ALL lollipop roms. I used sensor box in all my tests. I even tried proximity fix from play store, but it did nothing. I also tried to install it as secondary on multirom, then flash the firmware, but again, no success.
I really really need some help on this one, I can't troubleshoot it on my own, I am out of ideas.
Thanks in advance.
(My device is OnePlus one - always using boeffla kernel on both lollipop and kitkat roms.)
EDIT: Solved. Look at my last post.
Flash again only modem but matching http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 I had the same problem, flashing again modem solved this issue for me.
chazxt said:
Flash again only modem but matching http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 I had the same problem, flashing again modem solved this issue for me.
Click to expand...
Click to collapse
Hello,
Which modem did you flash from that thread? I have only tried the 44s from there but it was a no go.
Thanks in advance.
XNPH44S for me it worked
Hello,
Finally found a fix for my problem.
It seems that I had to flash from fastboot the CM11 nightly modem from here: http://forum.xda-developers.com/showpost.php?p=57125376&postcount=389
The process doesn't wipe anything in case anyone is wondering, it just flashes the modem ( NON-HLOS.bin)