No need
Thank you. Any idea if I can flash this via Arrow Recovery?
For the kernel itself, no, but if you want to use the app, yes of course.
Nope, I cant do any battery charging modifications on x3pro hence why the battery page has no feature for this phone. I cant mess with PMIC and risking to cause your devices to brick.Could you please add an option to regulate the battery charge, since the fast charge is deactivated when the cell phone takes a little temperature
Shouldnt be a problem
Hello, first one I've encountered it on my moto g 2013, my oneplus 2 as well. I dont think I've faced it on my f1 and never did on my x3pro. But, this usually happens when cpu cant process audio, either stuck in a very deepsleep state or for older phones, at min frequencies. Little trick for that is to change value of the sleep_disabled kernel module in sys. To do so, better use fkm so it can apply on every reboot. Most ROMs set this to Y on boot but maybe your rom doesnt and leads to your issue. So add a new tunable : /sys/module/lpm_level/parameters/sleep_disabled and set to Y and tick apply on boot (just check in a file manager to make sure the path is correctly written, I typed it by memory but should be close enough).Hello pierre! Thanks for the amazing kernel, improving this already amazing phone. Been using it for a couple days with the new LineageOS 19.1 (sticking to it after flashing other roms and not liking them). However, I have 2 issues that I found in my experience. They're nothing major, but they're still annoying.
1. On Battery profile (which is great btw, same perf for longer batt and that's my priority), all sounds became garbled when the screen is off. Song playback, notifications, anything sounds will have a massive static-like crackle and stutter. This doesn't happen in Balanced, but since I prefer battery life over everything, I tend to stick to Battery profile.
2. I cannot take a partial screenshot with the kernel installed on Android 12 roms, tested on crDroid 8, ArrowOS 12.1 and Lineage 19.1. Holding power button, then holding the screenshot button, then selecting the area I want to take a shot of will result in the phone throwing a "Couldn't take screenshot, please try again" message. Works as normal on A11.
Have you heard of others encountering these issues? I would love it if someone does and can help me with them. You've done a great job with this kernel mate.
I'll check that in a bit. I found the file, but I can't edit it.Hello, first one I've encountered it on my moto g 2013, my oneplus 2 as well. I dont think I've faced it on my f1 and never did on my x3pro. But, this usually happens when cpu cant process audio, either stuck in a very deepsleep state or for older phones, at min frequencies. Little trick for that is to change value of the sleep_disabled kernel module in sys. To do so, better use fkm so it can apply on every reboot. Most ROMs set this to Y on boot but maybe your rom doesnt and leads to your issue. So add a new tunable : /sys/module/lpm_level/parameters/sleep_disabled and set to Y and tick apply on boot (just check in a file manager to make sure the path is correctly written, I typed it by memory but should be close enough).
For the screenshots welp I never heard of that, I can take long screenshots fine on arrow with NGK.
You of course need root access for that.I'll check that in a bit. I found the file, but I can't edit it.
And the screenshot thing, it's not long screenshot, that works fine. It's partial screenshot, where you select a region on the screen you want to capture instead of the whole thing.
Alright, checked the file, it's already on Y. I'll reflash the kernel (on stock Lineage now) and the ROM again in a bit. Any other clue on why it doesn't work?You of course need root access for that.
Seconds seems more of a rom issue.
Cant really tell I havent faced those nor heard others having those issues. Are you using any force doze or anything?Alright, checked the file, it's already on Y. I'll reflash the kernel (on stock Lineage now) and the ROM again in a bit. Any other clue on why it doesn't work?
I want to say it's a rom issue too, but I've tried it on 3 different roms and all of them has the same issue, as said on my original post.
Huh, weird. I reflashed the rom and kernel and all, and everything is working just fine now. Maybe there was a conflict with some of my other software that I uninstalled before the reflashing. Thank you for the assistance anyway!Cant really tell I havent faced those nor heard others having those issues. Are you using any force doze or anything?
For the kernel version thats normal if you look at the compile datetime its ok and you are right for the touch firmware one isnt working and will be fixed.I'm having a problem when downloading version 2.2.1 and installing, it remains at version 2.2.0 and I can't use the miui 13 touch firmware. I've tried several times and nothing, it's like the last firmware link was wrong
because?
Good day to you, Sir.@Pierre2324 Thank you very much for the extreme quality of your work. Asking something not directly related to this Kernel but that you have much more knowledge than me to, it is interesting to install files that update the GPU driver, v530 for example ?
Sorry for the inconvenient question, but you give me a lot of credibility and I really appreciate your opinion.