• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos

Search This thread

UsernameNotRecognized

Senior Member
May 17, 2012
205
36
If you grab /proc/last_kmsg after it happened I can maybe even figure out a proper fix
I just don't have a wireless charger myself so can't test
If you have any problems with getting that log feel free to pm me
When I tried getting the kmsg it didn't really say anything at all. I've attached it here. But maybe you can use it?

I've disabled ACC, rebooted and put the phone on the charger. This shouldn't take much longer than a couple hours to get a fresh last_kmsg.

Edit: I've tried like 10 times to attach a file. How would you like me to send you the file?
 

Linux4

Senior Member
When I tried getting the kmsg it didn't really say anything at all. I've attached it here. But maybe you can use it?

I've disabled ACC, rebooted and put the phone on the charger. This shouldn't take much longer than a couple hours to get a fresh last_kmsg.

Edit: I've tried like 10 times to attach a file. How would you like me to send you the file?
Ah sorry didn't notice your edit until now
Maybe try on telegram (group link is in OP) or in pm here on xda?
 

starbright_

Senior Member
Apr 11, 2010
1,327
223
Hi folks. It's me again, the one guy who kept complaining about random resets. I finally figured out how to prevent this from happening.

I primarily use wireless charging for charging the device and let the device "be" for hours on it. Most things I can access through my PC (e-mail, calls, whatsapp, etc). When it is on this charger the device used to randomly reset every now and then.

After installing ACC:
And setting a config using ACCA:
To 5-85-90 (shutdown, start, stop) I no longer got resets.

It seems that the random resets have to do with the battery being near full and being on a wireless charger.

Is there anyone else who can test this?

For me this is an acceptable solution as I wanted to have ACC anyways to improve battery life.
Using the App batteryChargeLimit (FDroid). Maybe that works better for you instead of Magisk Module.
 

starbright_

Senior Member
Apr 11, 2010
1,327
223
Oh, new release is out! Thanks @Linux4 .
I just don't remember how to update (Magisk/micgroG installed). I think it was somewhat like (please correct me if I am wrong).
- disable Magisk (or even uninstall ?)
- do OTA
- reboot
- boot to recovery
- sideload Magisk
- boot
- enable modules / reinstall microG.

And it needs do generate the spoofing patch. @Linux4: would be great that would be included in ROM. It doesn't harm if not used.
 

starbright_

Senior Member
Apr 11, 2010
1,327
223
Anyone else use that ROM with microG?
I do have problems that phone doesn't wake up and rings/notify my (WA, Signal, Fritzphone) after around 30min of no usage. Maybe many use it often enough, but for me this is a problem. The only I think I could do (disable battery optimization) is done already. Any idea? I just don't know which part (me, ROM or microG or just some setting) is responsible for this misbehaviour.
 

Spyop3

Member
Jun 29, 2010
29
9
Samsung Galaxy S10e
Anyone else use that ROM with microG?
I do have problems that phone doesn't wake up and rings/notify my (WA, Signal, Fritzphone) after around 30min of no usage. Maybe many use it often enough, but for me this is a problem. The only I think I could do (disable battery optimization) is done already. Any idea? I just don't know which part (me, ROM or microG or just some setting) is responsible for this misbehaviour.

I'm also using it with magisk /microG, my experience is that it works but with a barely ok reliability.
My current set-up is magisk sideloaded from recovery and microg and spoof as magisk module.
Sometimes when updating I have strange behaviour with all the app disapering from microg cloud messaging but still able to provide notification for some. Usually after a while (~1-2 months) they come back

Seems to me that I don't experience your 30 minutes issue
 

starbright_

Senior Member
Apr 11, 2010
1,327
223
I'm also using it with magisk /microG, my experience is that it works but with a barely ok reliability.
My current set-up is magisk sideloaded from recovery and microg and spoof as magisk module.
Sometimes when updating I have strange behaviour with all the app disapering from microg cloud messaging but still able to provide notification for some. Usually after a while (~1-2 months) they come back

Seems to me that I don't experience your 30 minutes issue
For push notification re-register do:
find /data/data/*/shared_prefs -name com.google.android.gms.*.xml -delete
I reduced in microG/CloudMessaging/Extended the time in wifi from 30min to 10min. Maybe this helps.... Do you use Fritzphone app ?
 
  • Like
Reactions: Spyop3

starbright_

Senior Member
Apr 11, 2010
1,327
223
Some note about OTA update of this ROM. This is fairly easy (only italic steps below).
But I am using Magisk/microg - with that some additional steps are required - all is listed below. Don't be afraid, it is done in less than 5 minutes.

* Make sure your firewall allows the "Updater"
* If you uses Magisk, download the apk and rename it to zip and put it to SDcard (otherwise a PC is needed for sideload - see below)
* Go to Settings/System/Extended/Updater
* Search for update and download

* I recommend disable data traffic now until the FW-update is completed and microG/firewall is operational again, otherwise your system might be open for some time.
* start update

Device will boot into recovery and does the upgrade. It seems that the update is not completely finished in case of Magisk is installed. In this case force a restart by "Vol- + Power" for a few seconds if update hangs at around 95% (can bee roughly seen in the timeline)

* After update has finished: boot again to recovery
* Now Either
a) just do the update with already downloaded Magisk.zip (Apply Update/Update from SD_card) or
b) Enable ADB sideload by Apply Update/Apply from ADB and do an adb sideload from PC of Magisk.apk or zip (no matter here)
* boot into system
* in case of microG check (and give if required) microG give all the required permissions
* If all is set and done you can enable data connection again

On thing I was thinking about:
There are is one module needed for spoofing (spoof_AVDapi30). I found that an update of it is not required. Not sure whether this will be the case for other updates of 18.1 too, but keep an eye on it.
Enjoy the ROM and thanks to @Linux4
 
Last edited:

EvanEvans

New member
May 31, 2021
2
1
Some note about OTA update of this ROM. This is fairly easy (only italic steps below).
But I am using Magisk/microg - with that some additional steps are required - all is listed below. Don't be afraid, it is done in less than 5 minutes.

* Make sure your firewall allows the "Updater"
* If you uses Magisk, download the apk and rename it to zip and put it to SDcard (otherwise a PC is needed for sideload - see below)
* Go to Settings/System/Extended/Updater
* Search for update and download

* I recommend disable data traffic now until the FW-update is completed and microG/firewall is operational again, otherwise your system might be open for some time.
* start update

Device will boot into recovery and does the upgrade. It seems that the update is not completely finished in case of Magisk is installed. In this case force a restart by "Vol- + Power" for a few seconds if update hangs at around 95% (can bee roughly seen in the timeline)

* After update has finished: boot again to recovery
* Now Either
a) just do the update with already downloaded Magisk.zip (Apply Update/Update from SD_card) or
b) Enable ADB sideload by Apply Update/Apply from ADB and do an adb sideload from PC of Magisk.apk or zip (no matter here)
* boot into system
* in case of microG check (and give if required) microG give all the required permissions
* If all is set and done you can enable data connection again

On thing I was thinking about:
There are is one module needed for spoofing (spoof_AVDapi30). I found that an update of it is not required. Not sure whether this will be the case for other updates of 18.1 too, but keep an eye on it.
Enjoy the ROM and thanks to @Linux4
Thanks for this description, yesterday I just did an OTA update on good luck, and root stopped working (using Magisk/MindTheGapps). I just followed the following steps and now it all works again!

I (only) used:
- boot again to recovery
- just do the update with already downloaded Magisk.zip (Apply Update/Update from SD_card)
- boot into system
 

doeternietoe

Senior Member
Dec 31, 2010
68
27
Hi,

Just installed this ROM and it all looks great. Thanks, Linux4 !

I use Magisk and microG. I can confirm that signature spoofing following the guide mentioned by flortsch works fine. The guide tells you to use Linux, but with powershell (I expect cmd would also work), 7zip and a little bit of adaptation you can do it in windows as well.

I have just one question: Would it be possible to open the camera app from the lockscreen, without unlocking? On previous Modpunkt builds this was definitely possible.
 

mikk150

Member
Oct 29, 2008
31
4
Tartu
I have been using this rom for quite some time. been happy with it BUT today out of random I took my phone from wireless charger, and it was SCORCHING HOT and it was actually discharghing while on wireless charger.

I did adb shell inside phone, did htop to see what process was using CPU but nothing there.. everything was nice and idle(CPU wise) but I noticed that load was through the roof(probably some IO issue?)

I have logcat before I did reboot
 

Attachments

  • 2021-07-27 19.10.21.png
    2021-07-27 19.10.21.png
    168.4 KB · Views: 43
  • 2021-07-27 19.10.28.png
    2021-07-27 19.10.28.png
    158.8 KB · Views: 44
  • 2021-07-27 19.10.47.png
    2021-07-27 19.10.47.png
    191.7 KB · Views: 45

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I've been thinking of migrating to this particular build for some time, so thank you for sharing your experience. Did you have microg / magisk / signature spoofing as part of your old install? And did you disable those before migrating?
    No, I did not disable something before.

    I did this now and it works. Just be aware that you will get error messages about signature verification. And the update stucks after the image itself (if you do have magisk installed). That is normal. Just do a force reboot and do the installation (just the image) again. After that you can reboot to system and install Magisk again (out of recovery). Not sure whether you can do that in one step - I describe how I did it.

    Now I have a official microg los with OTA. :)
    Thanks to Linux4 and the team around LineageOS and LineageOS for microG.
    1
    After @Linux4 get it to make this ROM official (congrats and many thanks!):

    As I am using microG I would like to give https://lineage.microg.org/ a try. As I understand this it is almost 100% of the official LOS with some minor changes for spoofing. The interesting thing is, it provides a "dirty" upgrade path from a LOS by means of a "migration-zip" that provides a key-change. (More detauls at the linked site.) That sounds very promising to me.
    Question to the community: anyone did this starting from an unoffical Linux4 LOS image?

    Edit:
    I did this now and it works. Just be aware that you will get error messages about signature verification. And the update stucks after the image itself (if you do have magisk installed). Just do a force reboot and do the installation (just the image) again. After that you can reboot to system and install Magisk again (out of recovery). Not sure whether you can do that in one step - I describe how I did it.

    Now I have a official microg los with OTA. :)
    Thanks to Linux4 and the team around LineageOS and LineageOS for microG.
    1
    Thank you Linux4 keeping the monthly release on this one despite your official now :)
  • 36
    1607247455067.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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:

    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
    • 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/exynos9820-dev
    Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820
    13
    Requirements:
    • Any Q or R based firmware installed on your device.

    Pre-Install Instructions

    Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.

    1. Connect the device to a Wi-Fi network.
    2. 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.
    3. 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”.
    4. Your device will reboot, you may now unplug the USB cable from your device.
    5. The device will demand you format userdata, please follow the onscreen instructions to do so.
    6. Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
    7. 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
    1. 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
    2. 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.
    3. Factory reset using Factory reset -> Format data/factory reset
      Warning: Unlike TWRP this will also erase internal storage!
    4. Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
      Then run adb sideload <path to your lineage.zip> on your PC
      Optional:
    5. Sideload GApps and magisk 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!
    13
    Features

    • SELinux enforcing
    • AES-256-XTS FBE encryption
    • Latest Linux 4.14.x kernel
    • All cameras are working
    • Ramdisk is working
    • Dolby atmos is working

    Known issues

    • VoLTE/VoWiFi
    • You tell me
    7
    LOS 18.1 for our S10 device? SELinux enforcing? FBE? Open-source device tree? Where can I donate for this awesome work?
    7

    Official support for the s10 and note 10 family is coming soon! thanks linux4