amazing !Thank you @alonsoj636, the build lineage-20.0-20221113-UNOFFICIAL-mojito.zip seems to be running fine.
Pixel Experience Kernel have terrible ram management also not good battery life in my tests so i'm not planning to use that if westcoast end it's support (i'll probably stick with westcoast foreverhttps://github.com/PixelExperience-Devices/kernel_xiaomi_mojito might be an alternative.
When I saw the system update option in the settings tab, I felt the need to ask, thank you.a
as you can see above ... ota updates need official status to apply... thing not possible for now
Some other things I found, the light sensor to adjust the screen brightness is too sensitive, as well as the gyroscope sensor(s) for automatic screen rotation. Don't know if it's kernel related, but it would be nice if LOS had an option to adjust the sensitivity for both.Tested the new LineageOS 20 build (clean flash) and i have to say it's awesome performing!
Tested some other A13 ROMs and this will be my final choice for daily usage.
Works much better than my old trys with different A12 ROMs (performance, smoothness).
One little bug I've found: Setting an action for "Long Press home" in the settings doesn't work, but "Double Tap home" Setting is working on my device.
Only one whish: Would be really cool to make an official buld out of it to get OTA Updates for LineageOS 20.Good work!!
One hint to others : To get Google Assistant working with the smaller NikGapps Packages (not enough space for full install): Get the latest "Terminal App Systemizer" for Magisk and a terminal App like "Termux" and systemize the "Google" App (installed from Playstore before) to " /system/priv-app/" and "Hey Google" Voice Command works perfectly.
That would be nice indeed, and it is even possible with non-official LOS releases. I don't know how it works on V20 or how it applies the updates to A/B devices like this one. The Crdroid version for Mojito supports it if you need an example. Some more info, Don't know if it still applies now: https://github.com/LineageOS/android_packages_apps_Updater
That says enough for me.... too much customization without knowing about possible the impacts. I'll go with your choice in that case.amazing !
Pixel Experience Kernel have terrible ram management also not good battery life in my tests so i'm not planning to use that if westcoast end it's support (i'll probably stick with westcoast forever)
while i saw some unofficial lineage threads claiming ota updates (patching los source code afaik)... i don't have the time to dig into that (and now will have even less time) so i won't be able to ship ota updates either...Since @alonsoj636 says it needs to be an official build these days for this OTA updates to work, I'm not really sure if you can even make it work without patching the LOS source-code.
Have you considered using NetErnels?well , that's a new kernel which i'm using coz i heard that anush will drop support for rom and kernel eventually , so i switched to this one.
i'm not a kernel-man so i don't know about kernel stuff
yes , i'm using amazon ec2 services which are paid
I used it in some experimental builds I did and I was very impressed with the work you put into it.
In all honesty from a kernel developer perspective, upstreaming does not provide any benefits to an android device running old LTS (4.x kernels). It only mostly tends to break things like some of the patches broke games built with unity, caused vague app crashes, broke some platform tooling and etc. This is why I don't upstream at all infact, gregkh - Linux-stable maintainer don't even backport most important patches half of the times. It's up to kernel devs to backport them manually and have it in our kernel tree. Feel free to continue using WCS but I have to say this not only as a kernel dev but as a user of mojito aswell, that kernel is really filled with alot of debugging, there's alot of logspams, call traces (backtraces for failing APIs) and etc. I've seen it a bazillion times already shown by other users to me and I've told him about this but oh well you're not really on TG so I suppose you do not know how things are going on. Basically they treat me as the bad guy lolz. This is just my opinion tho, carry on w your workI used it in some experimental builds I did and I was very impressed with the work you put into it.
but in the end i went with westcoast because i like the fact that it is always updated to the latest linux kernel version and because it also worked very well...
yes, neternels is in my plans for sure.
didn't know that ... tnx for the explanationIn all honesty from a kernel developer perspective, upstreaming does not provide any benefits to an android device running old LTS (4.x kernels). It only mostly tends to break things like some of the patches broke games built with unity, caused vague app crashes, broke some platform tooling and etc.
didn't know that too...that kernel is really filled with alot of debugging, there's alot of logspams, call traces (backtraces for failing APIs) and etc.
well i know that some tg communities are toxic AF but don't listen to them... keep it up with your hard work as neternels is a great kernel in my opinion.
Cooldidn't know that ... tnx for the explanation
didn't know that too...
well i know that some tg communities are toxic AF but don't listen to them... keep it up with your hard work as neternels is a great kernel in my opinion.
for now will keep wcs but will be happy to use neternels in future LOS builds![]()
I fully understand, hopefully I'll have my other projects on schedule soon so I can (help you) build and patch (on my own).while i saw some unofficial lineage threads claiming ota updates (patching los source code afaik)... i don't have the time to dig into that (and now will have even less time) so i won't be able to ship ota updates either...
just the corresponding monthly update if i'm free enough and with my server running
Same goes for the Rockchip kernels for the ARMv8 / ARMv9 chipsets as for this Qualcomm SDM678 of the Mojito. It mostly depends on the manufacturer to update and maintain the kernel, and other devs can only follow up properly when the soc/kernel/modules are opensource. Too much tinkering and introducing partial patches / updates to the kernel etc. will often result into more trouble unless you spend a huge amount of time in testing and developing.In all honesty from a kernel developer perspective, upstreaming does not provide any benefits to an android device running old LTS (4.x kernels). It only mostly tends to break things like some of the patches broke games built with unity, caused vague app crashes, broke some platform tooling and etc. This is why I don't upstream at all infact, gregkh - Linux-stable maintainer don't even backport most important patches half of the times. It's up to kernel devs to backport them manually and have it in our kernel tree. Feel free to continue using WCS but I have to say this not only as a kernel dev but as a user of mojito aswell, that kernel is really filled with alot of debugging, there's alot of logspams, call traces (backtraces for failing APIs) and etc. I've seen it a bazillion times already shown by other users to me and I've told him about this but oh well you're not really on TG so I suppose you do not know how things are going on. Basically they treat me as the bad guy lolz. This is just my opinion tho, carry on w your work.
waiting for december patch so i can update the romhelooo, how is dev going?current build with wc kernel is great
connect phone with usb debugging to pc, go to fastboot, go to cmd in adb folder and use command fastboot boot recovery twrp.img (download img to that folder before)..Complete installation guide including gapps please?.ive arrow os recovery installed and im unable to install twrp/ofox
Twrp doesn't flash and the phone turns offconnect phone with usb debugging to pc, go to fastboot, go to cmd in adb folder and use command fastboot boot recovery twrp.img (download img to that folder before)..
after that you can adb sideload rom.zip and gapps.zip trough twrp from that folder on pc to phone
its not flashing, my method boots it to memory for one time use
not anymore... i'm preparing the next release with big improvements + neternels kernel
everything is working... i'm using this rom since release and i finally found my daily driver rom...Finally.
I'm gonna have to wait a bit, my device is still locked and I want to wait and see a bit before I **** something up.
What isn't working yet? Really dumb to ask at this point, but what is missing from the ROM to become official?