Develop Bugs

[ROM][X720|X727][7.1.X[TS] LineageOS 14.1 for Le Pro3

Hey!
We've published our LineageOS 14.1 for everyone. You can found ROMS in Team Superluminal website.
Thanks and enjoy!

ekkilm said:
Hey!
We've published our LineageOS 14.1 for everyone. You can found ROMS in Team Superluminal website.
Thanks and enjoy!
Click to expand...
Click to collapse
Many thanks for your work :good:

We just recognize that the Safetynet compatibilyty is broken. But no worries. We’ll release update soon where that will be fixed.
And…
IR blaster will work too. ?
Stay tuned folks!

Good job

ekkilm said:
We just recognize that the Safetynet compatibilyty is broken. But no worries. We’ll release update soon where that will be fixed.
And…
IR blaster will work too.
Stay tuned folks!
Click to expand...
Click to collapse
Flashed and running well. :good:
I do not have VoLTE though. Hope that is added in the future. Everything else running smooth. Going to keep stay on this ROM for a bit.
Thanks for sharing!

ROM UPDATE
-Fixed SafetyNet compliancy
-Fixed IR Blaster
Edit.
Update is also available via OTA, so check your updaters!

Would it be possible to provide a ZIP to get IR working also for users of the "vanilla" LOS 14.1 weekly builds? Or will that not work due to missing kernel requirements?

Thanks for your rom!! Why you didnt create this post in the rom section?

What's the difference between this and stock LineageOS 14.1?

chemicalboyxda said:
Thanks for your rom!! Why you didnt create this post in the rom section?
Click to expand...
Click to collapse
Because we have our own forum in TS site. This is just a note/info that we've published our build

darkmuck said:
What's the difference between this and stock LineageOS 14.1?
Click to expand...
Click to collapse
Try and see

darkmuck said:
What's the difference between this and stock LineageOS 14.1?
Click to expand...
Click to collapse
Some minor tweaks.
For example:
- SafetyNet compliant by default (banking apps, etc.. works)
- Easy root install/uninstall in ROM Extra Settings
- IR Blaster works
- No cracking audio
- Prevent accidental wakeup works (also when waking w/ fingerprint)
- Browser that actually works by default (SWE Browser)
- Better snap camera by default (OmniRom snap)
- OTA
Probably forgot something..

I have a few questions about this ROM since I had installed a ROM from Lineage OS website (lineage-14.1-20170512-nightly-zl1-signed) yesterday and it has bugs in the most basic and essentials things... The most ridiculous bug is the phone app that doesn't show the call screen when I try to call someone or when I receive a call from someone, it only shows the notification that I missed my call... And my camera stopped working after I change the resolution to a higher one, that was currently available... I had managed to fix that after I installed an app called open camera from Play Store.
Besides that I loved the ROM it self since it was my first time trying a Lineage OS ROM, but before I try to flash the one that you have in your website I would like to know if there are any bugs related to the phone calls, alarm clock, music player and notifications...
Thanks in advance

rijrg4 said:
I have a few questions about this ROM since I had installed a ROM from Lineage OS website (lineage-14.1-20170512-nightly-zl1-signed) yesterday and it has bugs in the most basic and essentials things... The most ridiculous bug is the phone app that doesn't show the call screen when I try to call someone or when I receive a call from someone, it only shows the notification that I missed my call... And my camera stopped working after I change the resolution to a higher one, that was currently available... I had managed to fix that after I installed an app called open camera from Play Store.
Besides that I loved the ROM it self since it was my first time trying a Lineage OS ROM, but before I try to flash the one that you have in your website I would like to know if there are any bugs related to the phone calls, alarm clock, music player and notifications...
Thanks in advance
Click to expand...
Click to collapse
We haven't face those kind of issues in our rom Sounds pretty strange issues overall. Did you do full wipes before installation? What gapps? Any mods?
I recommended you to check our site, download the rom and READ install instructions before installation. Those are the basic steps for rom/gapps installation.

I installed today. The first problem that i have is that the root option of this rom didnt work right. I have to manually install supersu to get root.
Second the adaptative brigthness didnt work ok, like other 7.1 roms.
Third i installed in a x727 and the signal is weak. I installed the modem version of the 19s rom but didnt change. I selected LTE/WCDMA, the same.
And the last one and for me is a problem, its that CDLA headphones didnt work. I get the sound over the speaker of the phone.
Sorry for my english.

chemicalboyxda said:
I installed today. The first problem that i have is that the root option of this rom didnt work right. I have to manually install supersu to get root.
Second the adaptative brigthness didnt work ok, like other 7.1 roms.
Third i installed in a x727 and the signal is weak. I installed the modem version of the 19s rom but didnt change. I selected LTE/WCDMA, the same.
And the last one and for me is a problem, its that CDLA headphones didnt work. I get the sound over the speaker of the phone.
Sorry for my english.
Click to expand...
Click to collapse
No no no no... And no supersu.. read the FAQ. There is a guide how to enable root. It is addonSU

ekkilm said:
No no no no... And no supersu.. read the FAQ. There is a guide how you enable root. It is addonSU
Click to expand...
Click to collapse
?? Easy root (install/uninstall in ROM Extra Settings)
And the cdla??

chemicalboyxda said:
?? Easy root (install/uninstall in ROM Extra Settings)
And the cdla??
Click to expand...
Click to collapse
1. Still that is pretty easy, you just have to enable it.
2. Unfortunately we don't have CDLA headphone for now so we're unable to test it. But we might bought those so we can maybe fix it in the future.

ekkilm said:
1. Still that is pretty easy, you just have to enable it.
2. Unfortunately we don't have CDLA headphone for now so we're unable to test it. But we might bought those so we can maybe fix it in the future.
Click to expand...
Click to collapse
1. I did that but when the phone reboots root not present. I have to install manually.
2. Thanks!

chemicalboyxda said:
1. I did that but when the phone reboots root not present. I have to install manually.
2. Thanks!
Click to expand...
Click to collapse
So you did with this guide TS FAQ?

[ROM][2017-10-22][UNOFFICIAL] XenonHD ROM for Mix 2 (Chiron) [7.1.2]

XenonHD ROM for Xiaomi Mi Mix 2
A Team Horizon ROM
Based on AOSP r36 7.1.2
This ROM has all the features XenonHD has to offer.
All hardware functions including:
NFC
Bluetooth Audio
Fingerprint Scanner
Doze & Wake-up Gestures (dtw works after the first reboot)
And...many more things.
Magisk is no longer built in, so you'll need to flash it when first installing, and after every dirty flash.
VoLTE doesn't work (at least on T-Mobile). I believe most of the pieces are in place, but there may be something in the firmware that's preventing it? If I could figure out how to tap into the stock cust files, I might be able to figure out how to get it working.
Proximity Sensor is working:
Notification Light:
I have slowed down the notification light so it isn't all amped up. To make it completely usable, go to:
Fixed default notification blinks for built-in apps so they are slowed down without needing to go to settings.
For use-installed apps, add them to custom notification list in settings > notifications > gear icon > notification light > + in upper right corner > select app. Apps added to that list will have slow notification blinks.
I simply cannot find a way to make user-installed app notifications behave the same as built-in apps. Grrr!!
I have also made the light sensor wait longer before dimming the screen. This helps with left-handed activities blocking the light sensor and almost immediately dimming the screen.
Reduced time to go back from dim to bright. Screen will dim after 5 seconds, returns to bright after 2 seconds.
I've remove configpanel & pocketmode...they did little to nothing, and may have caused more battery drain than I care for.
Required prior to installing:
Unlock Bootloader
Install custom recovery: https://www.androidfilehost.com/?fid=962021903579490303
HUGE thanks to IceMan for bringing this to Mix 2!
A quirk with this TWRP: This one looks for backups in TWRP/BACKUPS/MIX_2 folder. Normally, the MIX_2 folder is named after serial number of your device.
So, you existing backups won't be found until you rename the folder in BACKUPS to MIX_2.
Installation Instructions:
Dirty flash is now available with the above TWRP and 10-26-2017 rom.
Download the most recent build: https://www.androidfilehost.com/?fid=673791459329071426
Download Gapps (I use Open Gapps Mini) --> http://opengapps.org/
All versions from 10-24-2017 are now encryptable.
From TWRP Recovery:
IF COMING FROM MIUI-BASED ROM: FULL WIPE AND FORMAT DATA!!
If you encounter ERROR 7, during XenonHD install, install Global MIUI ROM, then do full wipe and data format again, then install XenonHD rom.
If coming from AOSP-based ROM:
- Full wipe (Cache, Davlik/ART Cache, System & Data)
- Flash ROM zip
- Flash Gapps zip
Huge thanks to Mokee for bringing this device up and making a great place to start.
Also a very HUGE thanks to @Arasthel for his work on proximity sensor and figuring out the bluetooth reboot stuff and other hints, suggestions and incalculable work.
I'd also like to thank all of you folks here for trying this ROM and providing constructive feedback.
In addition, I appreciate your patience when issues come up that need to be fixed. I am not a developer, and I have a full time job and a wife that takes precedence most of the time
Sources:
Vendor:
https://github.com/hondajohn88/android_vendor_xiaomi_msm8998-common
https://github.com/hondajohn88/android_vendor_xiaomi_chiron/tree/xenonhd
Kernel:
https://github.com/hondajohn88/android_kernel_xiaomi_msm8998/tree/xenonhd
Device:
https://github.com/hondajohn88/android_device_xiaomi_chiron/tree/xenonhd
https://github.com/hondajohn88/android_device_xiaomi_msm8998-common/tree/xenonhd

reserved

reserved 2

Does safety net pass with or without magisk?

subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
With magisk its working
Gesendet von meinem MI Mix 2 mit Tapatalk

THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs

Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)

KOLIOSIS said:
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Click to expand...
Click to collapse
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.

subashchandran said:
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
Click to expand...
Click to collapse
Glad everything is working for you so far. Bluetooth audio in car should work (it does on mine), but I found the volume on the car set to zero so needed to turn that up. That was a brief "oh crap" moment that I thought it wasn't working lol

subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
I think it fails without it, but magisk is built in, so if have to remove it to find out for sure.

hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
IT'S ALL GOOD @hondajohn88 . :good:
This ROM is daily-driver material,every update from here on out is a bonus & very much appreciated. :good:

hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.

Arasthel said:
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Click to expand...
Click to collapse
That's cool you got the Bluetooth working on RR, knocking little things out one by one ?
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ??
By the way, does android auto work on your rr?

Everything except proximity sensor works and works as good as stock. I have installed custom font, black swift substratum OMS theme without any hiccups. The rom is buttery smooth and I've been getting a better battery drain trend on this compared to resurrection/mokee. I have naptime doze installed to see if i can ooze out more battery goodness to the levels of epic Rom(miui 9)
Overall this is super encouraging to see a daily driver rom this early for mi mix 2.
There is one edge case which might be a bug, when connected on car Bluetooth and watching something on YouTube.. And then you get a call, i pressed answer on the car knobs/buttons.. I couldn't hear the person talking.. Car was displaying "audio disabled message ”. But talking/call and video/music in isolation works just fine.

Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel

slyyke said:
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
Click to expand...
Click to collapse
Thanks for the info about android auto on RR. I'll take a look at their repo and see if I messed up a USB setting somehow.
As far as I'm concerned, other ROMs can be discussed here.
Open source should be crowd sourced for maximum problem resolution.
RR probably (?) Did the same as me... Mokee made a commit in qcom/audio that did the trick.

hondajohn88 said:
That's cool you got the Bluetooth working on RR, knocking little things out one by one
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ?
By the way, does android auto work on your rr?
Click to expand...
Click to collapse
Hi... Thank you again for the wlan.ko tip. I deleted all instances of that in my out folder, dirty built and it's all good. Sped up my test time considerably! Woohoo! :good:

Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!

stu5797 said:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
Click to expand...
Click to collapse
I haven't used rr for this phone, but I think at this point rr probably has more options. This one has quite a few, and as son as I get most of this ROM straightened out, I'll try adding more options.
I'll add some screen shots of the settings to help people decide.
Thanks ?

Great work by a great Dev,
Thanks for putting in the work, smoothhhh rom~

Anyone working on LineageOS 17 support?

Considering there are no maintainers right now, is anyone interested in picking up?
I have no Android rom development experience myself but I would really like to see continued support.
Anyone tried yet and stumbled upon any hurdles? Perhaps we can figure this out together.

fredddii said:
Considering there are no maintainers right now, is anyone interested in picking up?
I have no Android rom development experience myself but I would really like to see continued support.
Anyone tried yet and stumbled upon any hurdles? Perhaps we can figure this out together.
Click to expand...
Click to collapse
https://github.com/LineageOS/android_device_nextbit_ether

Unofficial LineageOS 17.1
I've just found this unofficial version of LineageOS 17.1 for Robin.
Haven't tried it yet though. Maybe anyone tried it already?
The latest build is from beginning of September.
It's maintained by lennertfranssens and you can find it on Android file host.
If you Google the developer's name you can easily find it.
(As I'm new I can't post links here, sorry...)

blackuriel said:
I've just found this unofficial version of LineageOS 17.1 for Robin.
Haven't tried it yet though. Maybe anyone tried it already?
The latest build is from beginning of September.
It's maintained by lennertfranssens and you can find it on Android file host.
If you Google the developer's name you can easily find it.
(As I'm new I can't post links here, sorry...)
Click to expand...
Click to collapse
Just flashed and it works. Here's the link for anyone interested: https://androidfilehost.com/?fid=10763459528675557410
Have no idea what works and what doesn't. I'll play around with it today

xWolf13 said:
Just flashed and it works. Here's the link for anyone interested: https://androidfilehost.com/?fid=10763459528675557410
Have no idea what works and what doesn't. I'll play around with it today
Click to expand...
Click to collapse
On my part everything is working. I make the builds with the sources of Nolen Johnson and Paul Keith with some small additions.
Nolen told me he stopped his work because some testers said they faced deadlocks when entering their passcode and he was never able to recreate that situation.
I also never had that problem. But if some of you do and are able to make a logcat of it you may always post it here or send a message to me.

Lennert_F said:
On my part everything is working. I make the builds with the sources of Nolen Johnson and Paul Keith with some small additions.
Nolen told me he stopped his work because some testers said they faced deadlocks when entering their passcode and he was never able to recreate that situation.
I also never had that problem. But if some of you do and are able to make a logcat of it you may always post it here or send a message to me.
Click to expand...
Click to collapse
Idem on my part,
Maybe is a core control/interactive parameters fault?

linckandrea said:
Idem on my part,
Maybe is a core control/interactive parameters fault?
Click to expand...
Click to collapse
edit: this probably should fix the issue:
device tree:
https://review.lineageos.org/c/LineageOS/android_device_nextbit_ether/+/289972
https://review.lineageos.org/c/LineageOS/android_device_nextbit_ether/+/289973
vendor:
https://github.com/linckandrea/proprietary_vendor_nextbit/tree/lineage-17.1-timekeep

Hi,
I have also installed version 17, but it did not work properly for me. After successful installation, i got to the initial screen with the settings (Set up Android). As soon as I entered my wlan password, the "Android APP" crashed. I rebooted and skipped the wifi settings, so android started. But as soon as I entered the wifi password again, android crashed again. So I had to go back to 16.0.

Thanks for this Info's... Really interesting to update to lineage 17 if it could be use for daily driver

17.1 is official now - fixed the deadlocks and fingerprint.
18.1 everything but RIL works - and I'm working on that.

npjohnson said:
17.1 is official now - fixed the deadlocks and fingerprint.
18.1 everything but RIL works - and I'm working on that.
Click to expand...
Click to collapse
Like in the email, thank you again for your efforts.
RIL not working sounds like a serious issue. Is it something that can be easily overcome by LineageOS developers or does it require aid from the OEM to make it possible on a newer Android for an older device?

npjohnson said:
17.1 is official now - fixed the deadlocks and fingerprint.
18.1 everything but RIL works - and I'm working on that.
Click to expand...
Click to collapse
So excited to try it out!
Man it's amazing this phone still lives on! It makes me genuinely happy
fredddii said:
Like in the email, thank you again for your efforts.
RIL not working sounds like a serious issue. Is it something that can be easily overcome by LineageOS developers or does it require aid from the OEM to make it possible on a newer Android for an older device?
Click to expand...
Click to collapse
AFAIK it doesn't. Plus we have the chance to have maintainers that aren't just enthusiasts but actual professionals. So I'm confident he should not have that hard of a time fixing this.
It feels good to see that device enjoying its youth again

fredddii said:
Like in the email, thank you again for your efforts.
RIL not working sounds like a serious issue. Is it something that can be easily overcome by LineageOS developers or does it require aid from the OEM to make it possible on a newer Android for an older device?
Click to expand...
Click to collapse
I'll figure it out - OEM is long gone - and not that helpful when they were around.

npjohnson said:
I'll figure it out - OEM is long gone - and not that helpful when they were around.
Click to expand...
Click to collapse
RIL now works, - Tethering is broken - I'm debugging it, but Tethering is the last hurdle to promoting ether to 18.1

Hotspot is fixed. Just need a platform commit merged and ether is good to go on 18.1 - I'll look at IMS somewhere down the road.

Ether is now in the 18.1 ship list whenever we're able to ship.

npjohnson said:
Ether is now in the 18.1 ship list whenever we're able to ship.
Click to expand...
Click to collapse
Thank you for keeping Robin alive for us!

[ROM][UNOFFICIAL][10.0]LineageOS 17.1 beyond1qlte

LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.
What's not working:
IMS (no volte)
Bixby button currently not set
Instructions:
Make sure twrp by afaneh92 is installed and functional.
Download the latest build (and optionally gapps).
Reboot to recovery
Wipe system, data, and cache (required if you switch from other ROMs)
Flash the latest build, gapps, and magisk.
Reboot
Downloads:
Galaxy S10 Snapdragon (G973U): https://github.com/klabit87/OTA/rel...eage-17.1-20201114-UNOFFICIAL-beyond1qlte.zip
Google Apps: https://opengapps.org/
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred.
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).
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. For now please report any bug below.
Group:
Join this group for contacting me and bug reporting (typically fast response )
Unlocked Samsung US devices
https://t.me/joinchat/CG3Ojlb0TwDDrN-RY5UqmQ
Also dont forget to hit the thanks button!
Contributors
Thanks to @jrkruse and @afaneh92 for testing initial builds.
ROM Firmware Required: Minimum of Android 10 firmware
Based On: LineageOS
Version Information
Status: Beta
Source:
https://github.com/klabit87/android_device_samsung_beyond1qlte
https://github.com/klabit87/android_device_samsung_sm8150-common
https://github.com/klabit87/android_kernel_samsung_sm8150-common
https://github.com/klabit87/android_vendor_samsung_sm8150-common
Created 2020-11-14
Last Updated 2020-11-14

Reserved

Got it installed. Haven't had a chance to use as a daily driver, since I use volte. Hope it gets working eventually! Would definitely love to use as a daily driver after that!

Same. would love to see volte.

illspiritX said:
Same. would love to see volte.
Click to expand...
Click to collapse
I also had issuess with GPS on the sm-g973u, but that's something I testing with op, when he gets a new build made

Hi. I'm new here and I need some information. Do the fingerprint sensor and all the cameras work for this custom rom?

I am trying to root Lineage 18.1 on my S10.
Tried differtent versions of magisk without result. Is there a guid available for Lineage 18.1 for Galaxy s10?

pitchdown said:
I am trying to root Lineage 18.1 on my S10.
Tried differtent versions of magisk without result. Is there a guid available for Lineage 18.1 for Galaxy s10?
Click to expand...
Click to collapse
I've been working on a beta for s10. I'm hoping to share it this week. I planned to publish last week but I got busy with work.

klabit87 said:
I've been working on a beta for s10. I'm hoping to share it this week. I planned to publish last week but I got busy with work.
Click to expand...
Click to collapse
what will be shared?
Is it on a s10 not possible yet?

pitchdown said:
what will be shared?
Is it on a s10 not possible yet?
Click to expand...
Click to collapse
I have been working on a lineage 18.1 build for s10. Just be patient.

Will 18.0 qork
klabit87 said:
I have been working on a lineage 18.1 build for s10. Just be patient.
Click to expand...
Click to collapse
Will 18.0 work with Magisk?

I don't see why not. I haven't tested that yet though

klabit87 said:
I don't see why not. I haven't tested that yet though
Click to expand...
Click to collapse
until now magisk isn`t installed after flashing with 18.1
I hope your new version will have a help to this.

I am using 18.1 with magisk and have root and everything, my only issue with this rom is several of the google play apps i use won't even install on it saying it is incompatible, but they worked fine on stock. I do like the theme though and the personalization, great job! Just need to make it more compatible and i would love it.

Replicatorz said:
I am using 18.1 with magisk and have root and everything, my only issue with this rom is several of the google play apps i use won't even install on it saying it is incompatible, but they worked fine on stock. I do like the theme though and the personalization, great job! Just need to make it more compatible and i would love it.
Click to expand...
Click to collapse
You have to use the Magisk Hide option, and select everything with "com.google" in the package name.

Does this work with G9730 Chinese / Hong kong snapdragon variant?

Just got so sick of OneUI crashing all the time so I thought I'd give this a whirl. All good so far except for Google Maps can't seem to properly display. All the elements get huge when Maps is active, including the phone interface itself. Switching to any other app returns the normal look. I have googled as many different search terms as I could think of to see if anyone else is having this issue but I have come up with nothing. Screengrabs attached.
Google Photos has a similar issue only it just crashes after some screen difficulty.

BWhitmore said:
Just got so sick of OneUI crashing all the time so I thought I'd give this a whirl. All good so far except for Google Maps can't seem to properly display. All the elements get huge when Maps is active, including the phone interface itself. Switching to any other app returns the normal look. I have googled as many different search terms as I could think of to see if anyone else is having this issue but I have come up with nothing. Screengrabs attached.
Google Photos has a similar issue only it just crashes after some screen difficulty.
Click to expand...
Click to collapse
I encountered the same problem for Google Map when I'm in battery save mode.

Can i install this rom via TWRP? I cant see Install Lineageos Rom via TWRP guide. Thanks!

aceqdl0925 said:
Can i install this rom via TWRP? I cant see Install Lineageos Rom via TWRP guide. Thanks!
Click to expand...
Click to collapse
Yes, it's just like how you flash every other ROM. Check this.

Development [ROM][13][ENCRYPTION] Official LineageOS 20 for A72

Link to original thread: A52 4G forum

Updated to Lineage 19.0!

Hey man! Everything is working great as far as I can see right now. Only one big drawback is the fingerprint scanner not working on Galaxy A72. It's not that it's registered and then it's failing. You can't even register it sadly.
Any fixes soon? Or is there a workaround which I am supposed to do, that I don't know about?
Thanks!

nadtonii1 said:
Hey man! Everything is working great as far as I can see right now. Only one big drawback is the fingerprint scanner not working on Galaxy A72. It's not that it's registered and then it's failing. You can't even register it sadly.
Any fixes soon? Or is there a workaround which I am supposed to do, that I don't know about?
Thanks!
Click to expand...
Click to collapse
Sorry, sadly I only own A52 which makes it really hard for me to fix it on A72.

Simon1511 said:
Sorry, sadly I only own A52 which makes it really hard for me to fix it on A72.
Click to expand...
Click to collapse
There are some suggestions.
Google Camera does not start, crashes. On GSI it helped to turn on the vendor Q.
In the screen settings, can you add a graph of picture saturation settings?
And is it possible to add a system backup to Lineage Recovery?

Realees56 said:
There are some suggestions.
Google Camera does not start, crashes. On GSI it helped to turn on the vendor Q.
In the screen settings, can you add a graph of picture saturation settings?
And is it possible to add a system backup to Lineage Recovery?
Click to expand...
Click to collapse
1. Which version of GCam? BSG works fine for me.
2 & 3: No, such features don't exist.

Simon1511 said:
1. Which version of GCam? BSG works fine for me.
2 & 3: No, such features don't exist.
Click to expand...
Click to collapse
Also BSG
Is it by any chance due to the rise kernel?

Realees56 said:
Also BSG
Is it by any chance due to the rise kernel?
Click to expand...
Click to collapse
No, it shouldn't be related to the kernel.
I'll investigate soon.

Simon1511 said:
No, it shouldn't be related to the kernel.
I'll investigate soon.
Click to expand...
Click to collapse
Of course it's a pity lineage recovery won't have a backup function, it's inconvenient to flash twrp every time.
And the colour saturation setting as on oneui is missing. I don't understand why you chose LOs, there's nothing in it at all, you can't even choose colours in styles. I was sitting on GSI 12A CrDroid before your firmware, great firmware in terms of customization. Never used google services. Never used google services.
Unfortunately when upgrading to GSI v402 the phone is extremely hard to start. About 8 times on reboot out of 10, 8 times caught bootloop. And this is on any v402 firmware.
In any case your firmware is better, even without having to patch separately the boot for magisk in order to run it on 12A GSI

Realees56 said:
Of course it's a pity lineage recovery won't have a backup function, it's inconvenient to flash twrp every time.
And the colour saturation setting as on oneui is missing. I don't understand why you chose LOs, there's nothing in it at all, you can't even choose colours in styles. I was sitting on GSI 12A CrDroid before your firmware, great firmware in terms of customization. Never used google services. Never used google services.
Unfortunately when upgrading to GSI v402 the phone is extremely hard to start. About 8 times on reboot out of 10, 8 times caught bootloop. And this is on any v402 firmware.
In any case your firmware is better, even without having to patch separately the boot for magisk in order to run it on 12A GSI
Click to expand...
Click to collapse
If you're unhappy with lineage feel free to build any other ROM on your own, the device trees are all on my Github.

friend! please don't stop developing this system, it's the best I could find for me a72, as soon as I can I'll send support through paypal

¿Funciona en Samsung A71?
Translated by GT: Does it work on Samsung A71?

usuario888 said:
¿Funciona en Samsung A71?
Translated by GT: Does it work on Samsung A71?
Click to expand...
Click to collapse
No. As the thread says, this is exclusively for A52 4G and A72.

Is this Rom still in development I have the A72 4G. Want to load the custom OS

GoldenJet said:
Is this Rom still in development I have the A72 4G. Want to load the custom OS
Click to expand...
Click to collapse
Yes, it is.

tried this rom its quite unstable loads of issues, still its the only rom at the moment. I reverted to stock.
Ok this was posted in haste and a bit in irritation what I meant is simply this is not useable as stable rom,
Its unstable and has issues. This is not meant as a revieuw or judgement of said rom. Its the first and currently only one avalible and kudo's to the creator. Its listed as development. Its just a quick feedback for those like me that just like to know if its stable or not.

Spacecabbie said:
tried this rom its quite unstable loads of issues, still its the only rom at the moment. I reverted to stock.
Click to expand...
Click to collapse
Would you mind telling me about the issues you experienced?
From my point of view (and from what others told me) it runs pretty stable and mostly bugless on both A52 and A72.

I have it running for weeks now as second device. Only real issue is fingerprint sensor and camera, could not find any gcam mod that would work properly. Apart for it - runs stable.

Simon1511 said:
Would you mind telling me about the issues you experienced?
From my point of view (and from what others told me) it runs pretty stable and mostly bugless on both A52 and A72.
Click to expand...
Click to collapse
Sorry Muyst have missed this,
Also edited initial post cause it was imho blunt and to negative. Sorry about that I have nothing but respect for mod creators.
I din't extensivly test but:
Vingerprint reader but this was known.
I had some screen issues (swiping up from bottem wouln't work so couln't close apps.
pixel launcher kept crashing (yes this might not be rom related but nova launcher also had issues)
General instability possibly all related to screen.
There where some other issues but as said my intention was not to extensivly screen it the above combined with the other small issues made me decide to remove it again.

I was using lineage os 19 in my Samsung Galaxy A72. It's better than pixel plus ui rom. It has 90hz screen refresh rate. But this rom has the following bugs also:
1. Proximity sensor not working at all;
2.Fingerprint or face unlock not working;
3. No safety net pass.