[ROM][EXYNOS] LineageOS 18.1 for S10e|S10|S10+ - v2.2 (UPDATE: 2021-07-23)
- Thread starter modpunk
- Start date
Titanium Backup problems on LOS17.1
Have anyone tried using Titanium Backup on this LineageOS 17.1 for S10e?
I'm having trouble with Titanium Backup not asking for root permission, and here is what I have tried:
1) Reinstalling Titanium Backup.
2) Trying multiple version versions of Titanium Backup.
3) Deleting /data/data/com.keramidis.Titanium~ folder, and then reinstalling.
4) Setting Titanium Backup mode to interactive.
5) Temporary setting SELinux mode to permissive.
6) Trying to use built-in BusyBox (ToyBox in LOS).
I hope someone can guide me in the right direction.
From what I have read so far, it can be something with Titanium Backup looking for SU in the wrong path, but I'm not at all sure about all this, and my efforts haven't been fruitfull.
Have anyone tried using Titanium Backup on this LineageOS 17.1 for S10e?
I'm having trouble with Titanium Backup not asking for root permission, and here is what I have tried:
1) Reinstalling Titanium Backup.
2) Trying multiple version versions of Titanium Backup.
3) Deleting /data/data/com.keramidis.Titanium~ folder, and then reinstalling.
4) Setting Titanium Backup mode to interactive.
5) Temporary setting SELinux mode to permissive.
6) Trying to use built-in BusyBox (ToyBox in LOS).
I hope someone can guide me in the right direction.
From what I have read so far, it can be something with Titanium Backup looking for SU in the wrong path, but I'm not at all sure about all this, and my efforts haven't been fruitfull.
I think you need to look into issue of Titanium Backup with Magisk.
Just enter Magisk manager, go to Superuser tab, enable TB (hacky, true, but should work).
Thanks, I will try and see if there is a thread about that, and my issue is wrongly posted here, looking in the lights of clarity.
Titanium Backup isn't pressent in Superuser tab, it never asks for root permission, and Magisk doesn't register annything about Titanium Backup.
Problem is only related to Titanium Backup.
Try reinstall Magisk Manager app, had similar issue on another ROM.
---------- Post added at 08:11 PM ---------- Previous post was at 08:03 PM ----------
@modpunk, running your rom for a few days on s10e, at the moment is the best daily driver, only bluetooth (compression in calls) issue makes som difficulties, others everything works perfect. On the other phone S10+ currently testing other roms, maybe my experience can be usefull - tried partially clean AOSP rom form phhusson and his team, bluetooth and powersharing is working there, not sure how, but maybee if you have time you can take a look at their github?
Last edited:
modpunk has reportedly fixed the bluetooth issue, we are patiently waiting for his next release :angel:
Ahh, ok missed it) The only rom, that is free and secure) I would like better there not to be nlpbackends,aurora and fdroid privileget ext, but it's not a problem)
You want free and secure, but don't want nlpbackends? You know, they need to be system apps in order to work...
Yes, but if i need gps, i can wait for gps connect, buy ok, maybee nlp is not bad in some situations)
but aurora can be installed later, i dont like the only thing - i can only disable it, but not delete) F-Droid privileged doesnt work properly often, sometimes it can break cathegories and often makes problem in installing apps - sometimes they still asking for permission to install, sometimes it can hang on installing.
No, im using it something like 5 days, but tempereture is ok and sensors working good. Sometimes auto-brightness is aukward, but others is good...
Mb try to make backup and reflash. Not shure if it can help but try another dialer app, for example Simple Dialer (currently is only in Aurora/Play Store) and Simple Contacts (F-Droid).
Temperature can be the result of GApps, im ROM with no GApps, with almost all apps open-source and no problems with it.
Same here. I guess our sensor is to slow and we need to improve the proximity check in the dialer to check more then once. Our sensor only has a binary state, near and far and doesn't really measure a distance.
See also https://review.lineageos.org/c/LineageOS/android_hardware_samsung/+/275767 which should improve AOD/Ambient display
Nice one. I see you reviewed and verified that commit already. Let's hope it makes its way into your beta2 release.
It will be in BETA2. I'm just waiting that Samsung releases the Kernel for CDT1. It should be out in the next days.
One more small issue i noticed today: when i put the phone on wireless charger it appears charging animation, then when it is charded to 100% charge stopps and begin discharging, after some seconds (something like 15-20s) charging animation appears again and so on. I recognized it at night, any ideas about it?
On opensource.samsung.com there is a file called SM-G970F_QQ_Opensource_G970FXXS5CTD1.zip available. That's not the sources for CTD1?
Ups, I totally missed that. It is just a change for the files they touched.
Ok, the camera is not working and needs fixing then we can do a release.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
61- - - - - -
This project provides LineageOS with SELinux for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte).
- - - - - -
FEATURES
We provide a secure and up to date ROM, check the Lineage Trust status of your phone!
Secure ROM
- Fine-grained SELinux policy
- Latest 4.14 Linux Kernel release
- Improved performance
- Wireguard support
- USB restrictions
- AES-256-XTS File Based Encryption (FBE)
- Signed with developer keys
Nice features
- FDroid and AuroraStore preinstalled
- Bluetooth phone calls
KNOWN ISSUES
Don't be scared by the "BETA" label. Our ROMs are always rock solid.
- Some audio effects are missing
- Miracast not working
- Wideband SCO
- IMS not working (No AOSP solution yet)
Some minor issues are described in the FAQ below.
DOWNLOAD
You can download the latest version under the following links:
S10e
S10
S10+
INSTALLATION
Put the zip file of the ROM on your external SD card boot into recovery. If you use our TWRP recovery, you should use that one to flash the ROM.
Make sure you select: Zip signature verification.
This will verify that the signature of the ROM will match the one in TWRP recovery. A more detailed step by step description is in the FAQ below.
SECURITY ADVICE
Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
Do not flash Multi Disabler on this ROM!
What a Wurst!
This ROM is developed by derf elot, linux4 and modpunk
Contributors
modpunk, derf elot, linux4
Source Code: https://github.com/whatawurst
ROM OS Version: Android 11
ROM Kernel: Linux 4.14.236
ROM Firmware Required: XXSBFUF3
Based On: LineageOS27REQUIRED FIRMWARE: XXSBFUF3
CHANGELOG
2021-07-23 | 2.2
- Update to Linux 4.14.239
2021-06-23 | 2.1
- Update to Linux 4.14.236
- Fixed GPS
- Improved autobrightness (Thanks to linux4)
OUR UPSTREAM EFFORTS
22Features + Known Bugs Summary:
This ROM does already support most features of the hardware. If you need specific features, please check the list below. Each feature was manually tested, so it is possible that it does not match your experience with the ROM. In this case please tell us, see the "Getting Help" section at the end of this post.
Installation:
How do I install this ROM on my phone for the first time?
Below you find a brief checklist of the required installation steps. Installation is more complicated than other ROMs because we take device security very seriously. If you are unfamiliar with installing custom roms , please click the links and read the additional details there.
- Confirm the firmware version
- Check the top of the ChangeLog which firmware version is required for the ROM release to work well
- Go to settings/software-update and update only if the new version matches the requirement!
- Alternative: flash with odin/heimdall (details see below)
- Unlock your device
- Backup all data, unlocking will factory reset your phone
- Enable developer mode to and enable the OEM-unlock switch there
- Turn off device and boot to bootloader (hold VolumeDown + Bixby, then connect USB cable)
- Follow instructions on-screen
- Finish the initial setup after unlock. You must connect to WiFi, but can skip everything else. Do not specify a pin/pattern during setup afterwards, otherwise TWRP may cause the "try again after 86400 seconds" issue (see below)
- Confirm in the settings that the bootloader is actually unlocked. (greyed out, telling you its unlocked)
- Install our TWRP (official thread) | more details (thanks @AndrOdin)
- Download our TWRP recovery and the vbmeta-disabled.img file
- Unpack the .xz file with 7zip
- Check integrity of TWRP (optional, but important for security)
- Rename files to recovery.img and vbmeta.img; then pack both files together in a .tar archive with 7zip
- Install Samsung USB drivers and odin, (direct link)
- Start odin as admin, disable "Auto Reboot" and click "AP "to select the .tar archive
- Turn off device, boot to bootloader and, once odin detects it, click "Start"
- When the screen turns off, immediately hold (and keep holding) VolumeUp + Bixby + Power to enter recovery mode
- When the secondary warning appears, release everything but VolumeUp
- Swipe slider to allow for modification
- Install LinageOS
- copy the ROM ZIP file an external SD card
- Boot into the recovery
- Wipe cache + dalvik (wipe->advanced and select cache + dalvik)
- Format data (wipe->format data, use the dedicated button, wipe->advanced does not work)
- Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
- Optional: Flash GAPPS (e.g. OpenGAPPS)
- Reboot to system
How do I update LineageOS?
Updating LinageOS is a lot less work and you can keep all user data. The process is similar to the last part of the installation:
- Backup all important files optional, but very helpful if something goes wrong)
- Remove any pin/password/pattern to prevent "retry after 86400 seconds"
- Copy the ROM ZIP file an external SD card or internal storage; download the new firmware files to PC (if needed)
- Boot into the recovery, do not reboot until you've installed the new ROM and firmware
- Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
- (Optional: Update GAPPS to the latest version)
- Wipe dalvik and cache
- Reboot to download
- Flash new firmware with instructions below
- (Optional: if you use Magisk, flash the new BOOT file. You can also do this in previous step instead of using Stef4n82's "BL.tar" file.)
- Reboot to system
How do I update the firmware?
On the stock ROM you can update from the settings menu. You can't do this on lineageOS (yet), so ypu need to use use Odin or Heimdall instead.
How do I update the firmware manually?
Thanks to @Stef4n82's new instructions and repacked firmware files installation is easier than ever. Below you find a copy of his post:
If you use Heimdall:
- Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Heimdall_????.tar.gz"
- Extract the package
- Flash the firmware files with this command:
Code:heimdall flash \ --BOOTLOADER sboot.bin \ --PARAM param.bin \ --UP_PARAM up_param.bin \ --CM cm.bin \ --KEYSTORAGE keystorage.bin \ --UH uh.bin \ --DTB dt.img \ --RADIO modem.bin \ --CP_DEBUG modem_debug.bin
If you use Odin:
- Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Odin_????.zip"
- Extract the package and you will get an AP.tar, a BL.tar and a CP...tar.md5
- Flash the 3 files with Odin (tested with latest Odin 3.14.x)
You can download the repacked firmware from the links below.
If you don't want this repacked firmware packages and want to download the whole firmware by your own. Make sure if you flash it via Odin that you use this files:
- From AP_G97?FXX*.tar.md5 take the dt.img and create a new AP.tar
- CP_G97?FXX*.tar.md5
- Extract BL_G97?FXX*.tar.md5 and create a new BL.tar without the vbmeta.img.lz4
Try again after 86400 seconds?
With newer version of the Samsung blobs, if you unlock the storage (/data) with TWRP (ie. you enter your pin/password/pattern in TWRP), the trustzone thinks it is a failed attempt and will lock the storage unlocking for 1 day (86400 seconds). To prevent this do not enter your pin (press cancel) and you can still flash an update. If you tripped the trustzone you can either wayt for 1 day to unlock your device (do not power it off) or try rebooting the phone a few times (thanks @Stef4n82), or this slightly more detailed guide (thanks @Exilion90)
You can prevent this completely by removing any pin/password/pattern before entering recovery. This does remove all stored fingerprints, so you'll have to set the up again after the update.
3rd Party Software:
How do I install Google apps?
You can download and install the Google Apps from Open Gapps Project. You need ARM64 and 10.x. We suggest to always use the pico package. If you need additional apps you find them in the Play Store.
Put the Open Gapps ZIP file on your SD card and flash it directly after you flashed LineageOS and before the first boot!
Can I use GPay? What about other banking apps
GPay as well as some other banking apps check if the device passes safetynet and will not start if it doesn't. Safetynet fails when the bootloader is unlocked and therefore this ROM will not run GPay and other applications that need it. This official LineageOS statement explains why safetynett will never by bypassed (by default).
Safetynet used to be easy to bypass with Magisk, but since an Update eralier this year Google uses the TPM module and that can't be circumvented easily. However there might be a workaround with "MagiskHide Props Config", please check out this post and this one. (thanks @Stef4n82) Please note that this has not yet been tested and we can not provide any support. If you got it working on your device, please share how you've done it so we can add it here!
How do I get MicroG with this ROM?
MicroG is an open source alternative to GAPPS., but unfortunately not recently updated and therefore not recommended.
If you want to install it anyway, read this guide by @JoeRifle and this post (appendum) by @ned14. Update: It has been reported that the new MicroG version works without issues. (thanks @ichmyselfandi)
Does this ROM have root?
Not by default. If you need root (eg. for AFWall) you can get it through Magisk.
How do I install Magisk?
Important security Advice: Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
Option 1 (recommended):
- Download the boot image for Magisk: S10e -- S10 -- S10+
- Verify the integrity of the file -> See INTEGRITY
- Unzip the boot image using xz or p7zip
- (Needed for Odin) Rename the file to boot.img and use 7zip to pack it into a .tar file
- Flash the boot image to the BOOT partition using Odin, Heimdall or TWRP
- Install https://******************/
Option 2:
Which camera app do you suggest?
OpenCamera:
Great open source app that supports a lot of the camera's features with the camera API v2 (select this option in the settings):
- All cameras supported (except telephoto, this is a issue with the ROM)
- Manual change of exposure, aperture, shutter speed, ISO
- The (main) developer uses an S10e himself so you can expect good HW support
GCam Variants:
There is no "official" GCam for this ROM, but there are some that work. Please read this excelent post by @ned14 for more details. The current recommendation is "GCam_5.1.018.177470874.41362666_IDan_N6_3.5_fix.apk" from (IDan). You need GAPPS, microG (post) or the Google Service Framework(post).
In comparison to OpenCamera it sacrifices manual controls + extra lenses for:
- simpler user interface
- better single-shot HDR
- better panoramas + photospheres
- SlowMo video (1080p @120/240fps)
Getting Help:
General:
Before you post, please check this FAQ, use the search function and skim the few last pages of this thread. We want LinageOS to work on your device, that's the whole point of this thread, but this way you can get the fastest help. If you did not find an answer, feel free to ask here We do this in out free time and it may take us some time to answer, so please be patient.
How to report a bug?
To fix any bug we first have to be able to reproduce it. Please include all relevant information:
- device (S10e/S10/S10+)
- ROM version
- is gapps/ microg/ magisk installed?
- steps to reproduce the issue
When in doubt it's better to include to 0much information than too little. A good example is @Sheffield Steve's bug report. Check out Simon's "How to Report Bugs Effectively" to write even better reports (and thus get better help).
How to create a logfile?
To get an even better insight into your issue, a logfile can help us a lot. On Android this is called "logcat". Short logcats are best. They contain less fluff which makes finding the issue easier. Here are the steps how to create a log with adb:
- install adb drivers
- open cmd and navigate to the adb file eg. cd C:\Users\<user>\Desktop\platform-tools
- Connect your phone via USB
- Select "Allow USB Debugging" on the popup on the phone (see below how to activate it)
- Clear the log using: adb logcat -c
- Start loggingwith: adb logcat | tee beyond.log
- Reproduce the issue
- Stop logging by pressing CTRL+c
- Send us the log (in a PM)
How do I enable USB Debugging?
To enable USB Debugging you need to do the following steps:
- Go to Settings -> About Phone
- Look for Build number
- Tap on Build Number several times till you get the message that Developer Options have been enabled
- Go to Settings -> System -> Advanced -> Developer Options
- Enable USB Debugging
About this FAQ:
This FAQ is originally written by modpunk and partly maintained by me (ctrej) to reduce modpunk's workload. We try to keep the FAQ as up-to-date as possible, but it may lag a few days behind. Please read the last posts in this thread for latest information.
Changelog:
20200813 (v1.0)
- update: this changelog, now with ROM version at time of posting and a hide section for older changelogs
- update: firmware update section (thanks @Stef4n82!)
- update: ROM update section
- update: getting help section, rewritten for clarity
- update: proximity sensor, slow sample rate (thanks @Lav64)
- update: audio section with my test and @El Dun's report
- add: gpay/safetynet explanation
- change: link formating to stay under the 30k character limit
17
The most obvious one is that we provide SELinux enforcing and care about security and privacy. For the rest I can't give you an answer as Ivan doesn't want to release the source of his device tree. It would be great if Ivan would join our effort and contribute.
