Aurora store is an unofficial/FLOS frontend to GP.Ah, indeed! Disney+ as well!
But it feels a bit weird. The reason I installed this ROM was to get rid of all Samsung-stuff and get as close to a clean Android as possible, but now I have to use a separate store.
Maybe I'm just being difficult or maybe a custom ROM isn't the way to go for me at this moment and it's better to try stock ROM with a different launcher....
By the way, the front camera is still out of focus. I can see it tries to focus, but never succeeds to focus on me correctly.
[ROM][EXYNOS] LineageOS 18.1 for S10e|S10|S10+ - v2.2 (UPDATE: 2021-07-23)
- Thread starter modpunk
- Start date
I have a question about MicroG. After installing it, it breaks the preinstalled UnifiedNlP. I tried debloating it and systemizing the backends to privapp together alongside MicroG so to speak (ang granting microG background permission in XML). This worked on another rom - but not here.
Is there a way of keeping the preinstalled UNlP and integrating with MicroG (disable MicroG UNlP)? Or did I do sth. wrong debloating / systemizing?
Everything else works very well out of the box 4 me. Nicely done.
Is there a way of keeping the preinstalled UNlP and integrating with MicroG (disable MicroG UNlP)? Or did I do sth. wrong debloating / systemizing?
Everything else works very well out of the box 4 me. Nicely done.
There was an alternate MicroG installer. Somehow I can't find it in Magisk Manager, but you should find it in github.
I'm normally looking at microg from time to time if it is in a useble state. There was a post from marvin that he will development again and grant more users commit rights. However nothing really happened till now. I found only one commit and that's it.
I would like to use it, but not in the current state ...
Is this on S10+? There is no developer which looks into S10+ so that e.g. the fingerprint sensor has the right size or the correct position. I only have a S10e so S10+ is done completely blind
Yeah, I can relate to that
But, ever since governments decided to track humans with the help of global cancer namend GApple ... the need is on for me and a lot of my "partners" (NO, we do NOT sell dope/do illegal ****, if you are going that route mentally. We have a very "legitimate" reason for staying off grid!)
Anyways, I think it has to do with rights assignment and/or install location of the backends/NlP. I managed to fix it with another rom that way.
I actually really like your solution to use UnifiedNlP as a standalone version without MicroG. It did work very well out of the box and disentangled the whole thing.
Unfortunately, I do need to integrate some kind of Googlish behaviour (APIs) and have not found a MigroG that comes either w/out integrated UNlP or can integrate/use yours instead...or maybe I'm not good enough hehe.
I also tried to deny MicroG to bind its Network Listener. But that refused to install
Anyways, I will try to fix this effup manually. If I make it, i.e. if I can get a reliable usage NlP of MicroG as of its current, unpolished state, I will report findings/solution.
--> Very very nice job! And all this development will now become way more important (GApple's Secret Services API)! Just wait and see...but be prepared my fellow community!
PS Forgot sth. In your TWRP folder for the S10+ there is one file which does not belong there cause it is for beyondlte1...dunno how it got there. I suppose you didn't realize yet, but maybe you wanna remove it from that folder @modpunk
Last edited:
Yeah, I can relate to that
But, ever since governments decided to track humans with the help of global cancer namend GApple ... the need is on for me and a lot of my "partners" (NO, we do NOT sell dope/do illegal ****, if you are going that route mentally. We have a very "legitimate" reason for staying off grid!)
I'm using the pico apps and the first thing I do after installation, is that I go to the permission manager and remove the permissions from the gapps and turn off what I can. However I hope microg development get better in the next month. The current state is pretty bad.
Hey Modpunk! Thanks for replying. I just wanted to let you know I'm really new to all this. To be honest, I don't know what I'm doing. I been trying to piece together this puzzle. Originally I said there was a bootloop, so i wanted to provide all the steps I took to get there. But I ran into another issue where I can't decrypt the filesystem in TWRP after backing up.
My end goal is to have your version of LOS running as my daily driver. I want to make sure I can backup and restore so I can switch between ROMs. Right now it dosen't seem like fingerprint unlocking is working for me. How does the Vbmeta and boot (magisk_boot_beyond2_ctd1_beta2.img) image work?
Log File: https://www.dropbox.com/s/5q85cjyk28m1w71/logcat1.txt?dl=0
Appreciate the help!
Did you wait 1 day to be able to unlock? Also why do you patch twrp if there is a boot.img with magisk available?
Yeah. For a savy dude like you, that works well I suppose
But this device goes to the hands of a regular John Doe - nice, but not so savy.
And I have to make sure that Google does not, by the means of update or something in the background manipulating settings way beyond control of this John Doe, that they do not manipulate or change the device. (as a side note: Google might even be hiding in places we do not know about in the system - but at least with MicroG they have no means of regularly introducing new and unwanted stuff into your device, while we as free users keep at least some compatibility with that global kraken.)
Oh, and btw I found a solution to make it work!!!
So in case other people care about it, I will post instructions in a separe post below this.
And also thanks to
this input from Keule-T, I remembered that I had indeed tried a different installer before also.
I will post instructions and links below. Gimme a sec for that though.
PS Anything good to recommend for theming anyone? Does Substratum work well?
Yeah. For a savy dude like you, that works well I suppose
But this device goes to the hands of a regular John Doe - nice, but not so savy.
And I have to make sure that Google does not, by the means of update or something in the background manipulating settings way beyond control of this John Doe, that they do not manipulate or change the device. (as a side note: Google might even be hiding in places we do not know about in the system - but at least with MicroG they have no means of regularly introducing new and unwanted stuff into your device, while we as free users keep at least some compatibility with that global kraken.)
Oh, and btw I found a solution to make it work!!!
So in case other people care about it, I will post instructions in a separe post below this.
And also thanks to
this input from Keule-T, I remembered that I had indeed tried a different installer before also.
I will post instructions and links below. Gimme a sec for that though.
PS Anything good to recommend for theming anyone? Does Substratum work well?
The microG code was last touched in 2018, it isn't ready for Android 10 nor something for the regular John Doe to fix either. So why should I ship something half broken and then get complaints that it doesn't work?
If you wont a half working microG, it is your job to get it half working not mine
There is also a problem with UnifiedNlp it needs a new permission introduced in Android 10 but it doesn't know about this permission. We need to wait till Marvin gets back to developement or grants people who actually fix issues permissions to commit. This didn't happen yet.The microG code was last touched in 2018, it isn't ready for Android 10 nor something for the regular John Doe to fix either. So why should I ship something half broken and then get complaints that it doesn't work?
If you wont a half working microG, it is your job to get it half working not mine
Or you could just patch sig spoofing into your roms. Then everyone can chose to install microG on their own, without being depended on some installers.
Well, actually it's least about the installers. He's addressing the problem that the core of MicroG is outdated (something I wasn't aware of).
The microG code was last touched in 2018, it isn't ready for Android 10 nor something for the regular John Doe to fix either. So why should I ship something half broken and then get complaints that it doesn't work?
If you wont a half working microG, it is your job to get it half working not mine
Hehe, all good. You are doing enough for sure. I understand where you are going with Marvin resuming first: it would be a clean and more appropriate solution for everyone. Nobody knows what hidden incompatibilities else exist. Permissions might not be enough - especially when looking at safetynet. This might be a problem in the long run. But I hope that we (he) can find a way to circumvent it - and be it just to prove his magnificient coding skills and frivolous urge to break into security systems, I do have one at least :angel
Anyways, for me it seems to work what I have installed so far. Instructions coming now so that your users may follow my route - while we wait for good ole Marvin:
0. Pre first boot of OS: after flashing the system in TWRP, rm -r the UnifiedNlP folder in system/app. This ensures no conflicts with MicroG later on, as no other UnifiedNlP ever gets registered.
(probably optional, since it can also be solved by simply deactiving the preinstalled UnifiedNlP, but I wanted that system-app forever gone in case the user needs to factory reset the OS)
After having completely setup Magisk as usual (i.e. installing the Manager app in OS, flashing the include Magisk boot image in TWRP, starting Magisk Manager and downloading the remaining files to setup environment!):
1. Smali patch module for spoofing support.
https://xdaforums.com/apps/magisk/module-smali-patcher-0-7-t3680053
--> Be aware of the security risks though: this OS does not have any dialogue to ask for explicit user consent in order to grant the permission; the permission is openly available throughout the system now!
--> Off-Note: it would be best if the patcher itself could patch in a dialogue - which actually used to work a while ago, I remember some module for that in Smali patcher. A suboptimal alternative would be that custom roms were presenting an option during installation to include such support and apply all needed patches. IMHO the need for MicroG glory will persist and at some point spoofing will then be "needed" again - we do not have reason to believe that Marvin does not resume coding or that such a project would not be continued by other folks just in case!
2. Magisk Busybox module (probably optional, but might help some setups/apps/etc. lazy coding).
3. Then get this MicroG version here:
https://github.com/FriendlyNeighborhoodShane/MinMicroG_releases/releases
4. In the downloaded zip file (I used the NOGOOLAG version of them): edit the defconf by commenting out all backend installations under "stuff", and only(!) there. This will give you:
Close and save the editor. It will ask to update the zip file. Hit yes.
5. In the downloaded zip file also edit the system/etc/default-permissions/microg-permissions.xml by commenting out (<!-- "comment" -->) all unneeded permissions since we are not (yet) installing any backends - but note the explicit permission to run as background for Mozilla and for MicroG:
All but the preinstalled Mozilla backend are commented out and MicroG has been given default access to background location.
Same for Mozilla Backend - while probably it isn't needed here though, as all other backends ask for it anyhow after installation, but it does not harm either. I put it to make sure.
6. One more edit of the system/etc/permissions/com.google.android.gms.xml:
This ensures the actual permissions for MicroG in case default-permissions gets ignored somehow.
7. All the whitelisting in the system/etc/sysconfig/nogoolag.xml can be left alone. It ensures background API and energy savings compatibility once we do install further backends.
8. Install the edited MicroG zip as a module.
9. After reboot, go to MicroG settings, grant missing permissions if any, and setup your Mozilla backend and Nominatim.
All should work now. You are free to install further backends from this point on. They should all work without further tweaks as they are whitelisted and ask for background access under Android 10.
Droidguard can be installed as a user app and then systemized by Systemizer. But this does not help with safetynet. Even when using MagiskHideProps. So IMHO only Pico Gapps might work here.
Thank you Modpunk and contributors again. And Keule-T for making me remember a different release version as my base for the edits.
PS Substratum does not really work. Be it full version or Lite. Modules do not get applied and the amount of free themes is minimal. Forget it atm. Lineage 17.1 does have its own theme engine. But not much in it at all. Hope this becomes alive and lively. And all the free launcher alternatives are basically full of chinese tracking or advertisements. Forget it. For launchers there is either $$$ or the open source variant OpenLauncher. But more I could not dig up...
Last edited:
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.
