[ROM][UNOFFICIAL][13.0][OTA][Signature Spoofing][Open Source][Encryption] LineageOS 20 for Galaxy S10e/S10/S10+/S10 5G Exynos
- Thread starter Linux4
- Start date
Good morning to all,
can anyone tell me how is the battery drain with ambient display always on?
For what I think, battery drain is really high, when always active I see "Android System" is at the first position for battery drain.
Anyone have the same result? Or anyone know how to optimize the AOD.
For all other stuff, the ROM is absolutely awensome!!
Thanks
can anyone tell me how is the battery drain with ambient display always on?
For what I think, battery drain is really high, when always active I see "Android System" is at the first position for battery drain.
Anyone have the same result? Or anyone know how to optimize the AOD.
For all other stuff, the ROM is absolutely awensome!!
Thanks
Can anyone tell if LineageOS's Aperture camera app is included in the build by default? I'd like to use LOS 20 as my daily driver as OneUI is no longer updated, but waiting for an official release seems to take a bit too long
I feel like the same kind of issue, as I was saying in an old message.
I have also some battery drain from Signal, not sure why (I use always-on VPN, maybe that's the rootcause).
How long do your battery last without using your phone too much ? like a day, half a day, a few hours, ... ?
without AOD with Signal Messenger, K9 Mail and overnight in Airplane Mode at least 3-4 days
Does anyone else get black screen when watching 1440p video (non HDR) fullscreen on youtube?
I thought it was because of Revanced, but it also does it with regular YT application. Someone said that it might be a bug from some change made in the custom ROM so I'm checking.
Pinching to zoom brings the picture back, but pinching it back results in the black screen again.
I thought it was because of Revanced, but it also does it with regular YT application. Someone said that it might be a bug from some change made in the custom ROM so I'm checking.
Pinching to zoom brings the picture back, but pinching it back results in the black screen again.
Last edited:
Hum, that's good. So it"s my install which is not good. Same conf and I barely can get one day.
Currently stats say that Android OS takes around 50 % of the battery ...
Currently used 25% after the last recharge, of which only 1% Android-System, display 8%, mobile data 5% and the remaining rest the used apps...
- Galaxy S10+
- Firmware HVG
- According to flashing instructions December build with linked GApps installed
- Update January via OTA
- no root
As a daily driver, I can only recommend this ROM to a limited extent.
- my notification app does not work, required permissions cannot be granted.
- occasionally the screen cannot be opened, neither with double tap nor with the button. A forced restart is required.
- it is UNofficial
Thanks for the details. I have to check which firmware I'm using, I've installed the ROM a long time ago now.
No gapps on my side. Google is evil.
And root is on indeed. But I have this issue since the last OTA or the one before (or maybe a new app install, hard to say), so that's strange.
SafetyNet is now irrelevant as it has been replaced by Play Integrity. It is possible to pass SafetyNet yet fail Play Integrity. More information here
Just checked. It passes the first two checks but fails STRONG INTEGRITY. From what I've read that's due to an unlocked bootloader. Everything should be working as usual even though it fails? Will it complicate things in the future?
As long as you're passing BASIC and DEVICE integrity you should be fine; I'm not aware of any app that requires STRONG...yet.
Hi experts,
I'm trying to build this ROM with the lineageos4microg docker image (https://github.com/lineageos4microg/docker-lineage-cicd) but struggling with the manifest.xml for S10.
In case anyone has a working manifest with the S10 specific stuff, could you please share?
Thanks,
Georg
I'm trying to build this ROM with the lineageos4microg docker image (https://github.com/lineageos4microg/docker-lineage-cicd) but struggling with the manifest.xml for S10.
In case anyone has a working manifest with the S10 specific stuff, could you please share?
Thanks,
Georg
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1Seems to be already in a good state. Thanks for bringing this to us. Is it intended to make it an offical LOS? If so what are the open points that prevents that as of now?
-
20
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
- Follow the instructions here
Downloads:
- Builds: https://lineage.linux4.de
- GApps: MindTheGapps
Reporting Bugs
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- DO NOT Report bugs if you're using TWRP
- DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/Linux4/android_kernel_samsung_exynos9820/tree/lineage-20.013Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
- Connect the device to a Wi-Fi network.
- Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
- From within the Developer options menu, enable OEM unlock.
- Power off the device, and boot it into download mode:
- With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
- Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
- Your device will reboot, you may now unplug the USB cable from your device.
- The device will demand you format userdata, please follow the onscreen instructions to do so.
- Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
- Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
- Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot - Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power. - Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage! - Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional: - Sideload GApps and Lygisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!
I also strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.6For everyone who upgraded to HVJ1 firmware, for all models there's a HVI4 build that has binary version 'G' too, at least for some CSCs, you should be able to downgrade to that and have it working again.
I'd recommend to use samfw.com over sammobile tho since that one has faster free download.
FYI that problem cannot be resolved without first getting new kernel sources from samsung... and next time: Don't update your firmware manually anymore, I will take care of it on 20.
