OK, i know that most roms have the static on boot problem, which in itself isnt a big deal. But, i have found that the werewolf kernel doesnt have that issue. could someone help me find out why that kernel doesnt have that problem so we may fix other kernels? the kernel ends up freezing my UI and i have to reboot. Not sure if its related or not. I havent seen this anywhere so i thought i would post it. i am willing to test the kernel if i can get some help. Or just point me in the right direction on what i would need to look for if i tried to edit the kernel myself
It's open source isn't it? Look at the difference between the unmodified kernel source. I use that kernel as well to fix comfort view while not having static. The first time I tried the kernel my screen didn't respond to touch at all, not sure why it works now
lg kernels have the issue. werewolf is build from qualcomm sources with drivers added for our phones(same way lineage does it which is why theirs is fixed also) The fixes for those kernels cannot be applied to a standard kernel.
Related
Hey all, I have a Red lens Motorola Defy. I bought it a while back, it started having the earpiece problem, and when i tried to fix it, it messed it up even more. long story short, i fixed it now and im looking at putting this rom on it, with the jellyx kernel.
I have seen several people in the rom's thread stating that the 22/12 build of the rom still worked with the kernel but later versions of the rom did not, so that is the version i would like to get.
what im confused on is, I can't find any files that say 22/12 or anything close to it in the OP's dl link. also, can i just use the latest kernel build, or is there a specific version of that i need as well?
some info:
it is currently running cm7
I think it is running clockwork recovery (probably pretty old version)
as stated above, it is a red lens version
EDIT: i got it working. I found the 22/12 rom build. turns out i was looking in the wrong folder. for anyone else with the same kind of questions:
-yes you can just flash the cm10 nightly
-no you dont need a specific build of Jellyx (as of 01/09/12)
-yes is it smooth as hell
Ok guys, the rom is awesome. Installed it on my HTC One... But: Changing the Kernel is really hard and you cant enjoy it... cause of one bad bug.
First, i installed the ElementalX Kernel for 4.4.2... jep, not usable... graphic-bugs whilst opening apps. Also the start-menue (reboot, power off, etc...) doesnt display itself.
There are black stripes all over the lower part of the display...
Okay, restored the default kernel: Everything good.
Installing all other 4.4.2 HTC One kernels: Same bug every time...
Is there any way to install kernels without this damned bug?
Greets: Reavie
FunDaReav said:
Ok guys, the rom is awesome. Installed it on my HTC One... But: Changing the Kernel is really hard and you cant enjoy it... cause of one bad bug.
First, i installed the ElementalX Kernel for 4.4.2... jep, not usable... graphic-bugs whilst opening apps. Also the start-menue (reboot, power off, etc...) doesnt display itself.
There are black stripes all over the lower part of the display...
Okay, restored the default kernel: Everything good.
Installing all other 4.4.2 HTC One kernels: Same bug every time...
Is there any way to install kernels without this damned bug?
Greets: Reavie
Click to expand...
Click to collapse
Kernels other than the one included with omni are not supported, as the team can't test every kernel in existence.
If there's a specific feature from a kernel you want, it can be submitted to code review: http://docs.omnirom.org/Main_Page - read the items under Development
Q&A for [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
4 cores working with the screen on... battery life....
stuck at logo after kernel flash
I am on the liquid milestone 3.2. I saw that this is the same kernel but updated version that came in the rom so i wanted to update. No matter
Now i am stuck in a boot loop. phone powers on, stays at the LG logo, goes no further. I can get to Download mode, but no recovery.
Is there a way to recover this thing with out having put a locked stock rom on it??
DT2W double tap to wake
I love the Kernal so far however i've got a question about the double tap to wake features. Is there a way to have the screen turn off by double tapping somewhere OTHER than the notification bar at the top of the screen? Also it takes me about 4 or 5 double taps to get the screen to actually wake up, any ideas on any of this ? Thanks!
Hear myself in the phone... rom or kernal problem?
hello love the work you guys do its exciting and interesting. Ive relatively recently started playing with custom roms and kernals etc. love this one because i get excellent battery life as well as a solid LTE signal (two things ive had trouble finding with lollipop so far.. might just be me). Anyway ive got an issue with hearing myself in my phone when im on the phone... its like everything i say approx half a second after i say it.. needless to say its rather annoying, is this a rom or kernal problem? volume settings issue? not sure.. Also my proximity sensor occasionally wont register that my ear is near it.. baaically the screen stays on if im say checking my voice mail or on the phone.. not sure why this happends.. Everything else works great.. some info: d801 lg g2, lastest rr build for lp and i have the lasest blackbird for lollipop. its a really solid combo and im loving it.. thanks for any information you may have
asustweaker said:
I am on the liquid milestone 3.2. I saw that this is the same kernel but updated version that came in the rom so i wanted to update. No matter
Now i am stuck in a boot loop. phone powers on, stays at the LG logo, goes no further. I can get to Download mode, but no recovery.
Is there a way to recover this thing with out having put a locked stock rom on it??
Click to expand...
Click to collapse
did you flash kitkat version or lollipop version? Sounds like you flashed lollipop version
Nicholi85 said:
I love the Kernal so far however i've got a question about the double tap to wake features. Is there a way to have the screen turn off by double tapping somewhere OTHER than the notification bar at the top of the screen? Also it takes me about 4 or 5 double taps to get the screen to actually wake up, any ideas on any of this ? Thanks!
Click to expand...
Click to collapse
Update the touch screen firmware....there's an echo call via android terminal emulator or in my updated version in synapse
Nicholi85 said:
hello love the work you guys do its exciting and interesting. Ive relatively recently started playing with custom roms and kernals etc. love this one because i get excellent battery life as well as a solid LTE signal (two things ive had trouble finding with lollipop so far.. might just be me). Anyway ive got an issue with hearing myself in my phone when im on the phone... its like everything i say approx half a second after i say it.. needless to say its rather annoying, is this a rom or kernal problem? volume settings issue? not sure.. Also my proximity sensor occasionally wont register that my ear is near it.. baaically the screen stays on if im say checking my voice mail or on the phone.. not sure why this happends.. Everything else works great.. some info: d801 lg g2, lastest rr build for lp and i have the lasest blackbird for lollipop. its a really solid combo and im loving it.. thanks for any information you may have
Click to expand...
Click to collapse
These are ROM related errors...the call echo especially... Depending on ROM I could help....also see if it still persists in my latest update
Love this kernal, and I flash when installing a new LP build, but I've been having problems lately. After initial setup or reboot I get the" NO UCI SUPPORT " message. I'm running LiquidSmooth's latest build for the LS980, is anyone else having this issue.
Run om g3 based roms?
VictorAKAx said:
Run om g3 based roms?
Click to expand...
Click to collapse
No. This kernel is for AOSP-based ROMs. G3 ROMs are stock-based.
Typos courtesy of my Ice Cold LG G2 (D803).
just flashed your kernel, got stuck in a boot loop.
VS980, liquidsmooth 3.2 milestone.
what can i do? was excited to try out your update
Great kernel, running super smooth on AICP.
Thanks!
He's working on the fix for cm 12.1.
I sent my files on hangouts, just wait
edit: figured it out
does anyone have a dt2w fix for vs980? i just flashed liquidsmooth 4.0 and everything was working fine, flashed the kernel and it broke my knock on support. i found the zip posted in the main kernel thread (this one) and twrp tells me the file is corrupted
perforatedpaper said:
does anyone have a dt2w fix for vs980? i just flashed liquidsmooth 4.0 and everything was working fine, flashed the kernel and it broke my knock on support. i found the zip posted in the main kernel thread (this one) and twrp tells me the file is corrupted
Click to expand...
Click to collapse
Use the 0 init method:http://forum.xda-developers.com/showpost.php?p=56948464&postcount=73
I'm using F320K with BlissPop v2.3 rom, when flash this kernel for lp 5.0.2, it cause loopboot. Pls up kernel fix for lolipop 5.1. Hope to see it soon. Thanks u
llamas612 said:
I'm assuming that those are 5.0 based, since they're from January, right?
Click to expand...
Click to collapse
I think they're KitKat based. I tried already and it caused my d800 to go in a boot loop.
I wonder if anyone has got, perhaps, the 5.1 d800 version? I'm getting kinda desperate since my fav rom switched to a kernel that makes my phone really really hot.
Really need a link to latest 5.1 B14ckB1rd kernel for D800 :/
Pls...
So some newer devices have been shipped with different components from the older ones and while everything works fine on recent miui versions, most custom roms have issues. So I'm creating this thread to document all the issues caused by these new components and any solutions to them in one thread. Please reply if you have any other issues caused by the new hardware or any solutions to them.
Fingerprint
Description:
Option to add fingerprints doesn't appear even after setting pin, pattern or password on non miui based roms.
/data folder contains goodix folder with contents on miui.
Cause:
Some devices have a new fingerprint sensor manufactured by Goodix which is not yet supported by non miui based roms.
Solutions:
miui and any miui based roms such as xiaomi.eu should still work fine.
The newest build of Santosh's CM has a fingerprint patch available that will fix it.
Wait for CM to add support for the new hardware to its source code.
Battery
Description:
Battery is stuck at either -2% or 50%.
TWRP does not show battery percentage at all or constantly shows 50%.
Cause:
Possibly new battery controller hardware, by the looks of it the issue is related to the kernel, older CM kernel builds seem fine and so do newer miui builds however any rom using a new CM kernel build or based off it has the issue.
Solutions:
Fix was added to CM source code so the problem should be solved on all newer roms and kernels based on it now.
Flashing Radon 1.9 or above will fix it on any CM source based roms.
miui and other miui based roms such as xiaomi.eu should be fine.
Santosh's CM13 plust the camera fix works.
Mokee works fine.
Unofficial Ressurrection Remix works fine up until the 06/08 build.
This is the patch applied to Radon to fix the bug.
If you know of any other issues caused by newer hardware or solutions please tell me so that I can add it to this thread.[/QUOTE]
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
dmemon said:
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
Click to expand...
Click to collapse
Added for the fingerprint sensor, using TWRP is still probably the easiest way to check for the battery bug.
dmemon said:
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
Click to expand...
Click to collapse
The sensor of fingerprints with aida64, it is possible to identify.
The battery only if flash the TWRP, for the present.
Santhosh's CM13 battery bug is gone if you flash his camera fix.
razr96 said:
Santhosh's CM13 battery bug is gone if you flash his camera fix.
Click to expand...
Click to collapse
Ok cool I'll add it to the post and test it out if I get a chance.
I hear of that Mokee is using Xiaomi device tree, I guess that is why it don't has the "-2% or 50%" issue...
NTRNSTR said:
Description:
Battery is stuck at either -2% or 50%.
TWRP does not show battery percentage at all or constantly shows 50%.
Cause:
Possibly new battery controller hardware, by the looks of it the issue is related to the kernel, older CM kernel builds seem fine and so do newer miui builds however any rom using a new CM kernel build or based off it has the issue.
Solutions:
Santosh's CM13 plust the camera fix should fix it.
Click to expand...
Click to collapse
The camera fix works only with Santosh's CM13, not with other CM/AOSP roms
the new kernel Radon V1.8 by Umang96 does not fix the battery problem
EkiFox said:
The camera fix works only with Santosh's CM13, not with other CM/AOSP roms
the new kernel Radon V1.8 by Umang96 does not fix the battery problem
Click to expand...
Click to collapse
I would expect it to work on all Santosh based roms, the camera fix must have modified something that flashing a new kernel overwrites, if we can figure out what the camera fix changes we might be able to get a fix for all roms.
---------- Post added at 02:11 PM ---------- Previous post was at 02:10 PM ----------
dna1982 said:
I hear of that Mokee is using Xiaomi device tree, I guess that is why it don't has the "-2% or 50%" issue...
Click to expand...
Click to collapse
Well that would explain it, but at least we have roms without the bugs, that should help figure out the problem.
any working custom kernels for -2% or 50% battery bug?
mega-samu said:
The sensor of fingerprints with aida64, it is possible to identify.
The battery only if flash the TWRP, for the present.
Click to expand...
Click to collapse
as far as i know AIDA64 is not a good way to see your fingerprint sensor it shows fpc102x for me but i have a goodix sensor, in fact i think the other ones with fpc sensors have a fpc 1035 not a 102x. i think a good was would be checking kernel log you should see the module name or checking data partition ( if you have root) or system/etc/firmware if you dont (i'm not sure about the second one but i can see some goodixfp data there)
just saying maybe it saves someone from lots and lots of confusion as i had when i bought my device
The new Radon kernel doesn't have the -2%/50% battery bug!
For the cm13 based roms : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Reno_kun said:
The new Radon kernel doesn't has the -2%/50% battery bug!
For the cm13 based rom : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Click to expand...
Click to collapse
:victory: Now we can use any Official-CM based rom. Definitely adding this to the top of the list.
Reno_kun said:
The new Radon kernel doesn't has the -2%/50% battery bug!
For the cm13 based rom : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Click to expand...
Click to collapse
Yep just flashed official RR with this kernel and no battery bug!
Yes, there is just the lack of the support ou goodix fp and it will be perfect !
KaciPL said:
any working custom kernels for -2% or 50% battery bug?
Click to expand...
Click to collapse
Now there are, just updated the post.
Radon V1.9 Kernel does not cause the battery bug .......
Radon V1.9 Kernel does not cause the battery bug on "MIUI 8 by Xiaomi.eu 6.7.28 | Beta".
I got a test version from @Umang96 and successfully got below 50% battery level.
Any custom kernel working with goodfix fp ??
Sent from my Redmi Note 3 using Tapatalk
I lose data connection on any cm custom rom. It goes away for 50-60sec then it gets back
And if i flash radio zip, then security options crash
LiRi2000 said:
Any custom kernel working with goodfix fp ??
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
I don't think so, still a work in progress getting it to work.
Hi there,
I build my first custom kernel for my Sony Xperia Tablet Z (SGP321 Pollux) and I flashed it successfully. It works, meaning device is booting the kernel, but I don't have Wifi anymore. Although this problem seems to be common I couldn't find a solutions yet. I'm not sure what driver/net my device needs and if this is all i need to do. Can someone guide me what I can do to fix the issue?
Ulf123 said:
Hi there,
I build my first custom kernel for my Sony Xperia Tablet Z (SGP321 Pollux) and I flashed it successfully. It works, meaning device is booting the kernel, but I don't have Wifi anymore. Although this problem seems to be common I couldn't find a solutions yet. I'm not sure what driver/net my device needs and if this is all i need to do. Can someone guide me what I can do to fix the issue?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=66601984&postcount=520