• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

Gigantkiller

Member
Jan 22, 2019
9
0
Extract dtb.img from my latest LineageOS build, pack it into a .tar flash that (I think for making Odin flash it you will need to rename it to dt.img and then pack it into a tar archive), should resolve that issue.
Hello,
thanks again for your help. I did it, flashed with odin ap. Now, the message changed to Check Fail. Device: 11, Binary:8 (DTBO)

I flashed you DTBO too, now i can access the lineageos recovery :D
 

Linux4

Senior Member
Hello, On no, it stopped with 47% serving on cmd, (for 10 minutes no change), on mobile there is writen "Restoring Google Services Framework". Any idea? Thank you very much.
That 47% thing is a common "bug" when using sideload (also on other devices) but it's not really a problem, the output on device's display is what really matters
Where do you get that message? For sure that's not from recovery
 

Gigantkiller

Member
Jan 22, 2019
9
0
That 47% thing is a common "bug" when using sideload (also on other devices) but it's not really a problem, the output on device's display is what really matters
Where do you get that message? For sure that's not from recovery
I don't know what i did wrong, i repeated whiping and installing, now LinageOS bootscreen apppears correctly and system boots
 
Last edited:

wora92

Senior Member
Sep 19, 2019
75
28
@Linux4 I took your 18.1 branch and built the rom myself. Its security patch level is still May. I can see that you updated your 18.1-experimental branch which includes security patch level June and also a newer kernel. Is it safe to pull and build your experimental branch or would I run into problems doing so?
 

Linux4

Senior Member
@Linux4 I took your 18.1 branch and built the rom myself. Its security patch level is still May. I can see that you updated your 18.1-experimental branch which includes security patch level June and also a newer kernel. Is it safe to pull and build your experimental branch or would I run into problems doing so?
You would break at least camera by doing so
Should be safe to use lineage-18.1-testing tho (which already includes june secpatch too, experimental is for some other stuff)
 
  • Like
Reactions: wora92

UsernameNotRecognized

Senior Member
May 17, 2012
205
36
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.
 
  • Like
Reactions: exaveal

Linux4

Senior Member
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.
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
 

Top Liked Posts

  • 1
    FYI official downloads now available:

    Galaxy Note10+ 5G - d2x -- https://download.lineageos.org/d2x

    Galaxy S10+ - beyond2lte -- https://download.lineageos.org/beyond2lte
    ***
  • 6

    Official support for the s10 and note 10 family is coming soon! thanks linux4
    3
    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
    1
    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.
    1
    Ah sorry didn't notice your edit until now
    Maybe try on telegram (group link is in OP) or in pm here on xda?
    Since the OTA I've done yesterday I haven't seen it happen again. Maybe that fixed it?
    I'll send you the kmsg if it happens again.
    1
    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 ?
  • 35
    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
    12
    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!
    12
    Features

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

    Known issues

    • Miracast not working (Google removed it in AOSP Pie)
    • 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?
    6
    Update on feedback on the ROM, its been a couple of days, and this is easily my daily driver. Only issue I encountered was through Gapps not having the dialer app set as the default. Bizarrely the dialer was still semi functional. The finger print sensor is now fixed as well.

    This is a an easy successor to ModPunks great work, and I hope that Linux4 finds the time to become a maintainer for our device. Thanks for the great work