You can forget it with the default kernel. You can change the charging speed with custom kernels like NGK-kernel.Any way to boost charging speed? I'm getting realy good battery backup so I'd like to not change the default kernel.
Best to start by looking in the LOS19.1 forum thread. This here is for LOS20. Pretty sure there'll be correct instructions there.Hi
Can anyone lay out the officially correct way to upgrade my LOS?
I’m currently on lineage-19.1-20220709-nightly-beryllium-signed wanting to go to lineage-19.1-20221224-nightly-beryllium-signed.
Thanks.
Based on what I see in the picture, yes.View attachment 5819127Is Bluetooth LE audio disabled on lineage too?
But our device support Bluetooth LE, isn't it?
Maybe, BLE Audio is a new thing since API 33 (Android 13) - reference: https://developer.android.com/guide/topics/connectivity/ble-audio/overview. I will need to check if BLE Audio can be enabled. Nonetheless, that doesn't mean that that device can't currently connect to LE-enabled devices.
Use reignz twrp 3.7.0 12.0Hi, I install LOS 20, from stock ROM, with LOS Recovery, Magisk, SafetyNet, ANXCamera, Encrypted, ... and for me all is working great.
Only missing IR Face Unlock!
But, yesterday I do OTA update and Magisk was unistaled and modules disappear...
Any way to keek Magisk when make OTA update?
VoLTE would workhello,
could you tell me if the VoLTE/VoWiFi works with the French operator Bouygues Telecom ?
thank you
That's your stable. There used to be monthlies or sth similar. Those builds where somwhat stable, but didn't have the latest features. But I feel that was quite a long time ago.Could someone please let me know where do I find link for stable ? I can see nightlies under https://download.lineageos.org/beryllium
Nevermind, I have figured it out. Turns out that the "latest" update to the touchscreen driver introduced this issue. The touchscreen was being flashed with a wrong firmware, which in my case was leading to these touchscreen issues from time to time. I have just pushed the fix and it will be available in the next build.
Yes, March's ASB was not merged in time for that build. Next one will already include it.Installed 18032023 build just fine. Android security patch date is still 5th February. No issues so far.
No, we are still testing.Good news then. Will March security patch be in tomorrow's build?
It will be fixed in upcoming builds.Yes, that turned out to be my problem with bluetooth. Turning off the AAC HD setting fixes the audio issue. I dont know how big of an issue that is for audiophiles, in my headphones i dont notice any difference on and off. In any case, its a bug.
Nevermind, I have figured it out. Turns out that the "latest" update to the touchscreen driver introduced this issue. The touchscreen was being flashed with a wrong firmware, which in my case was leading to these touchscreen issues from time to time. I have just pushed the fix and it will be available in the next build.