Database Info

[ROM][UNOFFICIAL][UBER 4.9.4][Surnia ][7.1.2 r29] HalogenOS CAF [OMS]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Android, Reimagined.
For the best experience, view the thread on a web browser like Chromium or Firefox.
Desktop: Brilliant. Mobile: Good. Tapatalk: OK. XDA-Labs: Horrible.
Code:
YOU are doing modifications to your device.
YOU are responsible for what you do.
We are not responsible for any damages, data loss or any type of unexpected,
bad or damaging results! If you have SERIOUS problems with this software,
please contact the developers or maintainers. We are not liable for anything
bad that happens to your device.
As long as you are responsible, some companies such as OnePlus
WILL HONOR IT. Some people occasionally describe them as heroes.
Don't be stupid and bet on that though, please be responsible for what you do.
We prohibit you from overclocking to 1337 GHz thinking, that an OEM would
replace your glorious space heater etc.
We recommend you to take the advice above regardless.
halogenOS Checklist
Although no data should be lost or damaged by the flashing process,
we advise you to follow the following steps if you are coming from another rom:
Please take a full nandroid backup!
Please copy your back up to an external device.
Backing up your Internal Storage is also recommended.
When completed, please clean flash the build!
XOS is a new generation cutting-edge OS for Android based on Code Aurora Forum releases.
What is XOS?
halogenOS, also known as XOS is a new Android ROM which ships with the global aim to
become a modular ROM which keeps as high as potentially possible operating
performance on your mobile device while still maintaining a sufficient feature
base of nice, small and minimal features that would not be available via any
external feature base, extension, mod or plugin.
We hope you have a truly halogenified experience!
Internals of XOS
At core, the ROM is composed mainly of components from CodeAuroraForums (CAF),
featuring only extremely minor set of components from CyanogenMod (CM) which
have been added to source in order to allow for better cross-device compatibility.
Our LOVE to others
A huge thanks goes to those behind the CodeAuroraForums (CAF), the CyanogenMod
organization and all of its
contributors for the sources used in the development of the base ROM which we
started with inclusive of all the work and dedication their team puts in order to
keep us updated on the awesome contributions that they make.
We will be keen on ensuring that we be up to date with the code from our base sources,
with regular ROM updates hopefully coming from time to time.
Please do not ask for ETA's (else you shall be spooked by Mr Skeltal). Almost all of us are
students, and with the current lifestyles and routines we have, it is not that easy to acquire
time to develop the ROM, though we'll be sure to keep you updated and release OTAs as
soon as they are available and ready for publication. If you want to be really updated quick,
then join us on Telegram: http://telegram.me/halogenos
Visit our website for features such as: Downloads, Information etc.
http://halogenos.org
(Not finished yet)
​
Common stuff
The ROM is super stable as of now and we'll maintain a clean and proper ROM.
Known issues are going to be fixed as soon as possible. We don't have infinite time.
Highlights :
Substratum
Full media support (FFMPEG, video codecs, ...)
Great Audio quality, no distortions, no crap
Optimized many portions of the system including surfaceflinger, inputflinger, System Server, and more
Super fast boot
Superuser-capable
Great battery life
Soundmod support (not all soundmods work on Nougat, it's not our fault)
addon.d support (backups your gapps etc. when flashing new build - don't wipe system before flashing!)
init.d support
BusyBox
Disabled Access Time for all partitions (We don't need access time. When access time is enabled, it will store the exact date of the access when a file is accessed, what just wastes write cycles (in theory) and has impact in I/O performance.)
Super smooth
Signature Spoofing toggle (Support for MicroG)
Support for trusted third-party WebViews like Chrome
Long press on home for assist toggle
Security Patches in kernel
OpenGapps (Mini/Micro/Nano recommended) and Banks GApps support
Full KeyHandler & KeyDisabler support
Dexpreopt for faster (first) boot time and less space consumption on data partition
Upgrade & Boot the ROM in just 5 minutes - no more endless waiting for flashing a new build
Very high compatibility with other ROMs
How to update the ROM:
Download the latest zip
Reboot into TWRP (Please use official TWRP)
Do not wipe anything
Flash the ROM
Flash SuperSU 2.79 or newer if you want (Download 2.82 here)
or
Flash Magisk v13.1 if you want from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot
You don't need to wipe Cache/Dalvik.
You don't need to flash gapps again. There is some magic going on which keeps your GApps. Just make sure that you don't wipe system before flashing.
You don't need more than 5 minutes.
How to install the ROM for the first time:
Download the latest zip
Reboot into TWRP (Please use official TWRP)
Wipe system, data and cache (If you want to try a dirty flash, dont wipe anything)
Flash the ROM
Flash gapps if you want
Flash SuperSU 2.79 or newer if you want (Download 2.82 here)
or
Flash Magisk v13.1 if you want from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot
@regalstreak
@xdvs23 (actually xdevs23, but that was already taken on XDA)
@sewer56lol
@jbw716
@marpe
@dango99
@hunter_bruhh
@MSF-Jarvis
@keessonnema
​
ROM Download Links
Download halogenOS now
ROM Sources
All sources incl. ROM @ GitHub Organisation
Kernel source-https://github.com/LineageOS/android_kernel_motorola_msm8916
Device source- https://github.com/LineageOS/android_device_motorola_surnia
https://github.com/LineageOS/android_device_motorola_msm8916-common
Vendor source- https://github.com/theMuppets/proprietary_vendor_motorola
​
Join our
Telegram group
Telegram News Channel
Telegram Off-Topic Group
​
Credits
CodeAurora
CyanogenMod
And everyone else who contributed and helps us!
In case you feel left out here, please contact us! ​
XDA: DevDB Information
HalogenOS, ROM for the Moto E 2015 Surnia
Contributors
amarc78
Source Code: https://github.com/halogenOS
Change Log: https://github.com/halogenOS/android_vendor_xos/blob/XOS-7.0/Changelog.md
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Cm 14.x firmware
Based On: CAF
Version Information
Status: Stable
Current Stable Version: 7.1.2
Stable Release Date: 2017-05-24
Created 2017-05-24
Last Updated 2017-08-17

Reserved

Reserved

I should mention that you'll have no nav bar when you first boot. You'll have to go into settings and enable it. So don't freak out when you get stuck in an app, just go into settings from quick settings. I'll try to enable it and upload a new build asap.

amarc78 said:
I should mention that you'll have no nav bar when you first boot. You'll have to go into settings and enable it. So don't freak out when you get stuck in an app, just go into settings from quick settings. I'll try to enable it and upload a new build asap.
Click to expand...
Click to collapse
I was stuck in the initial configuration because I did not have a lower navigation bar, I restarted the power button for a long time and I started the bootloop. I tried twice to blink the rom and I could not get out of bootloop. Waiting for new construction .... thanks, nonetheless. good job.

ENRIQUEMM said:
I was stuck in the initial configuration because I did not have a lower navigation bar, I restarted the power button for a long time and I started the bootloop. I tried twice to blink the rom and I could not get out of bootloop. Waiting for new construction .... thanks, nonetheless. good job.
Click to expand...
Click to collapse
That's strange. I flashed a few builds and didn't have that problem. I'll see what I can do.

I'm running a new build now, the nav bar should be activated on first boot. If so, I'll post it shortly.

Wonderful ROM Works to perfection

RubenPCA said:
Wonderful ROM Works to perfection
Click to expand...
Click to collapse
It does run great. Very quick and smooth.
Sent from my LGLS755 using XDA Labs

Great job
My steps
All wipe
Flash ROM
Flash gapps
Flash supersu
Reboot
Init and freezing then reboot and bootloop
Reflash only ROM and gapps
Run
This ROM is fantástic
Just an observation, try to install it from the official twrp 3.1.1 and after doing the backup I was unable to access the recovery. Nor restarting in recovery mode even from the fastboot. I had to put back the squid twrp through adb ...
Sorry my bad english
Enviado desde mi XT1524 mediante Tapatalk

Thanks man rom works perfectly ! No issues on first boot!

Has anyone else noticed a bluetooth connection failure?
Connecting to my smart clock turns off in seconds.
I regret not being able to attach the log, but due to bootloop problems when installing supersu I do not have it rooted.

ENRIQUEMM said:
Has anyone else noticed a bluetooth connection failure?
Connecting to my smart clock turns off in seconds.
I regret not being able to attach the log, but due to bootloop problems when installing supersu I do not have it rooted.
Click to expand...
Click to collapse
I forgot to mention some Bluetooth issues, but I haven't had any trouble staying connected to anything. I thought the only problem was inbound file transfer. I'm working on it. I've been using Magisk without any issues by the way.

After installing magiks v12 I play the connection to my smartwatch and the same problem is disconnected in seconds

ENRIQUEMM said:
After installing magiks v12 I play the connection to my smartwatch and the same problem is disconnected in seconds
Click to expand...
Click to collapse
I think you misunderstood. I didn't mean installing Magisk would fix your Bluetooth problem. You can take a log now though right? I don't have a smartwatch and I haven't had problems staying connected to devices I have so a log may be helpful.

amarc78 said:
I think you misunderstood. I didn't mean installing Magisk would fix your Bluetooth problem. You can take a log now though right? I don't have a smartwatch and I haven't had problems staying connected to devices I have so a log may be helpful.
Click to expand...
Click to collapse
I wanted to have robot access for the registration of the bug attach it to the previous post. Thank you

ENRIQUEMM said:
I wanted to have robot access for the registration of the bug attach it to the previous post. Thank you
Click to expand...
Click to collapse
There is an updated SuperSU I see. https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
I haven't tested it yet though.

New build is up. Bluetooth should be all fixed now. @ENRIQUEMM I don't have a smart watch to test with if you want to try again and let me know if your problem is fixed.

Hi. You guys work hard I know it. I couldn't get past the get started screen no matter what I tried.

801legend said:
Hi. You guys work hard I know it. I couldn't get past the get started screen no matter what I tried.
Click to expand...
Click to collapse
Sometimes old Gapps or a bad data connection can make the setupwizard hang. If you weren't using up to date Gapps try updating them. I'f that doesn't work. Try selecting not using any data or WiFi connection on setup. It worked fine for me with 6-17 Open Gapps before I uploaded the build.
Sent from my Motorola XT1526 using XDA Labs

[ROM][H830,H850][UNOFFICIAL] LineageOS4Microg 15.1 [8.1] - 2020 Build (by Bernie_nix)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), 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.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/​
Click to expand...
Click to collapse
Rom Built by Bernie_nix​Why build Oreo Now? What about other variants of the G5?:
Oreo is very stable on the h830 and works great with microg. I'm using this build now. This is also a build I am interested in maintaining and comparing to a future Pie build with microg built-in. Unfortunately, Android 17/Q is not yet fully compatible with microg.
Working:
5ghz WiFi, camera, calling, bluetooth, great battery life. USB-C audio earbuds work great. Reported that NFC works.
You tell me.
Known issues:
Please test WiFi, NFC. IR blaster not working for me but I may need to find a suitable app; please test. FM radio reported not working.
Automatic updates not yet implemented but will be in next build.
You tell me.
Install Instructions (If coming from another rom):
Prerequisites: Coming from another rom with Developer settings enabled, android debugging enabled.
(1) Boot into twrp (or ofox)
(2) Wipe your device. Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache, Data, Internal Storage, System. Then Swipe to Wipe all of these (if in twrp. if in ofox, wipe system but do not wipe system 10)
(3) Select Format Data Button. Type yes
(4) Select Install button. Choose rom zip. Swipe to confirm flash.
(5) Install Magisk if you choose.
(5) Press back arrow button 2x to get back to main screen. Select Wipe button. Select format data button. Type yes.
(6) Reboot. Phone may or may not mention "no os installed." Ignore it. Proceed with reboot. Phone will boot twice, then boot into lineageos4microg.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM. Reinstall of TWP/Ofox should not be required if upgrading (at least on Ofox).
Upgrade Instructions (If coming from my previous build):
Prerequisites: Developer settings enabled, android debugging enabled.
(1) Boot into twrp (or ofox)
(2) Select Install button. Choose rom zip. Swipe to confirm flash.
(3) Wipe caches.
(4) Magisk should persist after reboot but if not, go back into twrp/ofox and flash it.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM. Reinstall of TWP/Ofox should not be required if upgrading (at least on Ofox).
Tips for Use
1. Root can be enabled in this build (if not installing Magisk) by going to Developer Settings->Manage Root Access->Apps and ADB
2. To turn off battery led when charging, Settings>Apps & notifications>Notifications>Battery Light
3. To set up Microg,
(1) open MicroG app,
(2) press self-check, press battery optimizations ignored and allow,
(3) go back one screen, select unified nlp settings, configure location backends, press the checkbox next to mozilla location service and ok, configure address lookup backends, press checkbox next to nominatum and ok,
(4) then go through Google services from top to bottom and enter your information.
(5) Enable location from pull-down shade. Open maps, get your location. Go back to Microg. Run self-check. All boxes should show a check.
(6) Microg is setup in less than 5 minutes and fully working.
(7) Turn off location from pull-down shade bc they're tracking you ​4. Want a better GPS experience? Install Deja Vu Location Service, GSM Location Service and Radiocells.org Unified Network Location Provider Backend from F-Droid. Works great with Google Maps or OSM.
5. I've found Hypercam to take excellent pics with our cameras. Please download for the G5 here: https://gcambrasil.com.br/lg
Reporting bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed.
Please report bugs in this thread.
Logcats are helpful but not required. Grab a full logcat right after the problem has occurred.
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.
Thread Purpose & Limits
This thread has been created to discuss the installation and use of this rom. If you have questions about building roms, this thread is not the place to do it. Please create a thread under Q/A; doing so allows many users to assist you and will help to keep this thread on-topic. Failure to follow this request will result in a warning followed by report to XDA if continued. Some excellent resources for building microg include https://lineage.microg.org/ and https://8192.one/post/lineage_build_with_docker/.
New Builds:
Mar. 5, 2020 Change log
1. Latest security update
Status: Stable
ROM OS Version: 8.x Oreo
Security Patch level: Mar. 5, 2020
H830 Download link: https://www.androidfilehost.com/?fid=4349826312261742170
H830 MD5: 8bd86770d84b94a5d999489c7f993db6
H850 Download link: https://www.androidfilehost.com/?fid=4349826312261742710
H850 MD5: 6fe7febb5b4f994a1f32af18390a988c
Older Downloads:
Feb 29, 2020 Change log
1. Latest sources
2. Root option enabled in development settings
Status: Stable
ROM OS Version: 8.x Oreo
Security Patch level: Feb. 5, 2020
H830 Download link: https://androidfilehost.com/?fid=4349826312261734920
H830 MD5: 017e4f8352f670e1d409bbce34490178
H850 Download link: https://www.androidfilehost.com/?fid=4349826312261735367
H850 MD5:fb428e8a245e06d66037a4254b519ebf
Source and Additional Links
https://github.com/LineageOS
https://github.com/LineageOS/android_device_lge_msm8996-common
Last Updated Mar. 11, 2020
Thanks to x86cpu's posts, Dark98, Electimon, Gabi and the countless others who helped me out!​

Will test the h850 build as soon as you release it! :good:

I would love this for the h840! Oreo and security patches sounds great.

ml11ML said:
Will test the h850 build as soon as you release it! :good:
Click to expand...
Click to collapse
Build posted. See link in first post.

LollipopLover said:
I would love this for the h840! Oreo and security patches sounds great.
Click to expand...
Click to collapse
I would love to build for the h840, unfortunately it seems harder to build for. Not seeing a whole lot of sources or development on that variant.

Thank you anyway. I'll always have hope.

Thanks, @Bernie_nix this rom is super stable I was wondering how you build LineageOS4Microg the instructions on their website didn't make sense to me. Thanks so much for this rom. Will you make Pie builds?

ROMSG said:
Thanks, @Bernie_nix this rom is super stable I was wondering how you build LineageOS4Microg the instructions on their website didn't make sense to me. Thanks so much for this rom. Will you make Pie builds?
Click to expand...
Click to collapse
Yes I will continue forward to make an los 16 microg build. As far building yourself, please read the first post. I will not answer any questions related to building in this current thread after my response below.
I'm going to put together some info on GitHub with required files and some instructions to build on Ubuntu. In a nutshell, you install docker on Ubuntu, install the microg docker container and then supply a manifest file for the docker to download sources, etc.
I don't provide support for building in my threads because it's off-topic and really adds quite a bit of support that is better provided in its own unique thread where many members can help. I would be happy to answer questions in a Q/A thread of its own, on GitHub or in a telegram group.
If anyone is reading this and knows of an active telegram group for the g5 please message me and I'd be happy to provide assistance there. Otherwise wait until I update on GitHub. I have my reasons but do happily share in the spirit of open source. A ROM release thread is not the place to do it.

Amazing rom! Just installed on my h850 and it works great! The suggested GCAM is also very good. I have tested NFC and it does work fine (tested only between 2 phones). The IR however seems to work very strange... I tested with the app irplus which does seem to transmit something the first time you press a button but then it just starts loop blinking the IR led like a notification led on off on off on off about every second until a reboot. You can see this by pointing another camera at it. Also i was just wondering if it's possible for you to somehow add fm radio? It worked great on the stock rom but I noticed that no custom roms seem to have it. It isn't something that would cause me to not use this great rom but it would be nice to have. Also.. I wiped everything in orange fox before installing including system10 before I noticed the warning about keeping that but it works fine so far. Do I need to do something about it or can I just ignore it? What even is system10? First time I've ever seen it on any device.

ml11ML said:
Amazing rom! Just installed on my h850 and it works great! The suggested GCAM is also very good. I have tested NFC and it does work fine (tested only between 2 phones). The IR however seems to work very strange... I tested with the app irplus which does seem to transmit something the first time you press a button but then it just starts loop blinking the IR led like a notification led on off on off on off about every second until a reboot. You can see this by pointing another camera at it. Also i was just wondering if it's possible for you to somehow add fm radio? It worked great on the stock rom but I noticed that no custom roms seem to have it. It isn't something that would cause me to not use this great rom but it would be nice to have. Also.. I wiped everything in orange fox before installing including system10 before I noticed the warning about keeping that but it works fine so far. Do I need to do something about it or can I just ignore it? What even is system10? First time I've ever seen it on any device.
Click to expand...
Click to collapse
Thank you for your kind words! I've been testing it on my h830, and it really has brought some new life to my device. Even my pictures aren't coming out yellow like they were on stock! Thank you for testing NFC, and I am glad to hear that works for you. I had similar results with the IR blaster, and that's one of the features I love about this phone; I will try to see if I can improve the functionality as at least it does turn on but unfortunately can't give an ETA; this will involve looking into some lg and lineage sources if they are available. I will also look into fm radio. As most custom roms are built off of a similar base, that explains why it doesn't work in most. It may not be possible to pull the files and include them in the rom, but I may be able to create a magisk module with some lg files; again can't give an ETA as I don't know what I will find or how long it will take. I will investigate though. As for system 10 in ofox, I haven't been able to find much if any documentation on it. As I didn't erase it on install and it booted, I figured best to be on the safe side

Bernie_nix said:
Thank you for your kind words! I've been testing it on my h830, and it really has brought some new life to my device. Even my pictures aren't coming out yellow like they were on stock! Thank you for testing NFC, and I am glad to hear that works for you. I had similar results with the IR blaster, and that's one of the features I love about this phone; I will try to see if I can improve the functionality as at least it does turn on but unfortunately can't give an ETA; this will involve looking into some lg and lineage sources if they are available. I will also look into fm radio. As most custom roms are built off of a similar base, that explains why it doesn't work in most. It may not be possible to pull the files and include them in the rom, but I may be able to create a magisk module with some lg files; again can't give an ETA as I don't know what I will find or how long it will take. I will investigate though. As for system 10 in ofox, I haven't been able to find much if any documentation on it. As I didn't erase it on install and it booted, I figured best to be on the safe side
Click to expand...
Click to collapse
I see. Anyway thank you for looking into the IR issue as I agree that it's a great feature and also the fm radio. I would not have any problems with it being a magisk module if it can't be added to the rom. And yes, the phone runs great with this rom so far. Very responsive and minimal battery drain even with my half dead battery that dies at 50%. It is definitely my new daily driver.

New build released to update to March 2020 security update. See 1st post for download links.

Bernie_nix said:
New build released to update to March 2020 security update. See 1st post for download links.
Click to expand...
Click to collapse
Installed on my h850 over the old build and wiped cache and it works. :good:

ml11ML said:
Installed on my h850 over the old build and wiped cache and it works. :good:
Click to expand...
Click to collapse
Great to hear. Thanks for your feedback!

Cnt install googleplay store.

mie_ayam said:
Cnt install googleplay store.
Click to expand...
Click to collapse
Its microg....a Google play replacement. Read the first post. That's the whole point of this ROM! I think you may be looking for regular lineageos.

this rom have low mic issue and low sound issue?

Zorcnecrophades said:
this rom have low mic issue and low sound issue?
Click to expand...
Click to collapse
I know that Los usually has lower sound. Haven't experienced the lower mic myself but I could be wrong. You could probably easily edit some mixer_path volumes if it is not to your liking.

Hi, real cool rom. thanx a lot. But: PicoTTS does not work. App shuts down in test. And Hdmi (or Slimport??) on an OTG does not work.
And the LG Camera Plus add-on-piece is not recognized
Is H850_v2.2-mk2000.zip compatible with this rom? or maybe H850_v0.3-BETA2-mk2000.zip?
(after Test) No its not, camera is not working with both kernels and Android says, thats the Vendor Image is not right, when i reboot. What ever that means
P.S. The rest is really stable after 2 days of testing.#
P.P.S. Changing BT Connections from one (Airpods Gen 2) to another (JBL Charge 2) while playing music reboots the phone.

Bernie_nix said:
Its microg....a Google play replacement. Read the first post. That's the whole point of this ROM! I think you may be looking for regular lineageos.
Click to expand...
Click to collapse
yes. because I am accustomed to downloading apps on Playstore. and some applications when we want to log in using a google account. can't log in using a google account that is included in the Google Microg app.
Thank this rom great . mybe this is litel bug.

[ROM][10]Android Open Source Illusion Project[perseus][Official]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
Android Open Source illusion Project
About us:
AOSIP is a quality custom ROM based purely on AOSP. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Harsh Shandilya
Anirudh Gupta
Bug reporting:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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 dmesg . (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.
Source code:
AOSiP Gerrit Review
AOSiP Github
Kernel Source
Latest Downloads:
Official Server | SourceForge Mirror
Credit/Thanks:
Mike Williams (founder and creator of AOSiP)
Google for Android and AOSP
LineageOS
ABC ROM
AquariOS
BootleggersROM
Dirty Unicorns
PixelExperience
OmniROM
CarbonROM
nathanchance
---------
Other projects whose work helped us to create this
And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible
Hosted and built on
​

INSTALLATION PROCEDURE:
CLEAN (This is also solve Mi Logo Bootloops)
1) In TWRP, Format Data
2) Reboot TWRP
3) Wipe System, Data, Cache and Dalvik
4) Flash Xiaomi EU (Stable v11.0.2.0 or Weekly v20.5.7)
5) Format Data
6) Reboot TWRP
7) Wipe System, Data, Cache and Dalvik
6) Flash AOSiP
7) (Optional) Flash Gapps & Magisk
7b) Don't flash Gapps package if you chose to flash the Gapps AOSiP build
8) Reboot into the system, and enjoy the illusion!
DIRTY (At your own risk)
1) In TWRP, flash AOSiP
2) (Optional) Flash Gapps & Magisk
2b) Don't flash Gapps package if you chose to flash the Gapps AOSiP build
3) Wipe Dalvik & Cache only
4) Reboot into the system, and enjoy the illusion!
KNOWN ISSUES:
NONE! All sensors, slider function, and AI button are all working!
If you find an issue, please let me know. Either via Telegram or here.

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. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Include your firmware versions in reports.
Mention any and all Magisk modules you might be using along with the Magisk version
If it is a random reboot, grab dmesg . (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.

FREQUENTLY ASKED QUESTIONS:
COMMUNITY?
We have a community of over 600 helpful Mix 3 users around the world.
Join us on Telegram if you need help or want to chat: https://t.me/MiMix3Global
FIRMWARE?
AOSiP will not flash unless you are on any Android 10 based firmware.
xiaomi.eu ROM includes firmware, so this is not needed if you flashed that during a clean install (unless you want to try a different firmware version).
If you like to be on the latest firmware or try different versions, you can grab it here.
Personally, I like the latest available global variant (stable or beta).
You can flash firmware at any time, without affecting your current installation.
WHICH GCAM WORKS BEST?
Urnyx05 v1.7
WHICH TWRP SHOULD I USE?
Mauronofrio v3.3.1-17
CLEAN OR DIRTY?
If you're coming from unofficials, you'll need to clean flash since these builds are SIGNED.
Once you're in, you can just take OTAs, no more need to clean flash.

Great ROM! Congratulations on obtaining the "Official" status.

Hello, thanks for this Rom ! I have issues with Android Auto and screen laggy and flickering when my phone is connected to my car. Also some elements of the UI are missing like navigation bar on the screen of the car. No problem with ArrowOS which is CAF based Rom. Is there any solution ? I desactivate material superposition on develloper settings and it's not changing.
Thanks in avance

romano64 said:
Hello, thanks for this Rom ! I have issues with Android Auto and screen laggy and flickering when my phone is connected to my car. Also some elements of the UI are missing like navigation bar on the screen of the car. No problem with ArrowOS which is CAF based Rom. Is there any solution ? I desactivate material superposition on develloper settings and it's not changing.
Thanks in avance
Click to expand...
Click to collapse
]
Thanks for reporting, I will look into this issue.

Constrabus said:
]
Thanks for reporting, I will look into this issue.
Click to expand...
Click to collapse
Thank you

Hey guys, happy to announce AOSiP 10 Stable officials!
Please see the announcement on the Twitter post for changes and info about this release.

Hi everyone! been quietly following the community for quite some times already and I figured I could register and give you some insights on this rom.
I've wiped everything, installed the latest firmware, rom, gapp and magisks.
Everything went smoothly, except magisk giving me some headache about the ctsprofile... a ****ing nightmare... I've had custom rom for the last 10 years or so, I know my way around and always find the tricks to make things works... but this time I almost gave up.
I ended up on youtube and found this gem.
S-TaGmNfKMg
Use termux and manually assign the fingerprint for the mix 3 and there you go.
So far everything is working fine, Bluetooth, gps, selfie slider, dt2w, nfc.
Now I'm monitoring for a battery drain. if the battery could last a typical day, that'l be great.
And thank a lot for everyone involved!
I'll keep you posted

bearminator91 said:
Hi everyone! been quietly following the community for quite some times already and I figured I could register and give you some insights on this rom.
I've wiped everything, installed the latest firmware, rom, gapp and magisks.
Everything went smoothly, except magisk giving me some headache about the ctsprofile... a ****ing nightmare... I've had custom rom for the last 10 years or so, I know my way around and always find the tricks to make things works... but this time I almost gave up.
I ended up on youtube and found this gem.
S-TaGmNfKMg
Use termux and manually assign the fingerprint for the mix 3 and there you go.
So far everything is working fine, Bluetooth, gps, selfie slider, dt2w, nfc.
Now I'm monitoring for a battery drain. if the battery could last a typical day, that'l be great.
And thank a lot for everyone involved!
I'll keep you posted
Click to expand...
Click to collapse
Just tested this on 1 MiMix 3 with AOISP [Unofficial] and on another MiMix 3 with ArrowOS 10.0 and it works on both devices like a charm.
Finally: ctsProfile true
Thank you for the hint including the little gem :good:

bearminator91 said:
Hi everyone! been quietly following the community for quite some times already and I figured I could register and give you some insights on this rom.
I've wiped everything, installed the latest firmware, rom, gapp and magisks.
Everything went smoothly, except magisk giving me some headache about the ctsprofile... a ****ing nightmare... I've had custom rom for the last 10 years or so, I know my way around and always find the tricks to make things works... but this time I almost gave up.
I ended up on youtube and found this gem.
S-TaGmNfKMg
Use termux and manually assign the fingerprint for the mix 3 and there you go.
So far everything is working fine, Bluetooth, gps, selfie slider, dt2w, nfc.
Now I'm monitoring for a battery drain. if the battery could last a typical day, that'l be great.
And thank a lot for everyone involved!
I'll keep you posted
Click to expand...
Click to collapse
Awesome, so glad everything is working for you.
Yes that is the magisk props module. I recommend anyone who is having SN issues to use this (You can technically set to any device and it will work).
I am actually using the same fingerprint that it sets for persues. The reason you pass with the module, is that It also modifies your security patch date - another validation requirement for cts is that your fingerprint date and your security patch date must be within the same month. However, since this is an official build, we do not want to change the security patch date in the build.
Anyway...... I am coming up with a way to satisfy both requirements and will hopefully be implemented into the next build.
Until then please use the module + 'props' command via any terminal to set any fp if you need SN.

ctsProfile false
Constrabus said:
Awesome, so glad everything is working for you.
Yes that is the magisk props module. I recommend anyone who is having SN issues to use this (You can technically set to any device and it will work).
I am actually using the same fingerprint that it sets for persues. The reason you pass with the module, is that It also modifies your security patch date - another validation requirement for cts is that your fingerprint date and your security patch date must be within the same month. However, since this is an official build, we do not want to change the security patch date in the build.
Anyway...... I am coming up with a way to satisfy both requirements and will hopefully be implemented into the next build.
Until then please use the module + 'props' command via any terminal to set any fp if you need SN.
Click to expand...
Click to collapse
Unfortunately, it didn't work here. Tested it, using the latest AOSiP Version (5/6/2020), Magisk/Props/BusyBox/Termux >> picked Xiaomi Mi Mix 3 (Android 10) fingerprint >> reboot:
ctsProfile false
What did I miss/do wrong? Do I have to pick a fingerprint which is different from the Xiaomi Mi Mix 3 one?

chromanju said:
Unfortunately, it didn't work here. Tested it, using the latest AOSiP Version (5/6/2020), Magisk/Props/BusyBox/Termux >> picked Xiaomi Mi Mix 3 (Android 10) fingerprint >> reboot:
ctsProfile false
What did I miss/do wrong? Do I have to pick a fingerprint which is different from the Xiaomi Mi Mix 3 one?
Click to expand...
Click to collapse
I have done this with 3 different MiMix3 now always following *exactly* the video and all the devices are showing "ctsProfile true" after the procedure. The instructions is showing 6 - Google and at the step thereafter 23 - Google Pixel 4 XL (10) so I picked the same.
Worth noting that with one of the devices I had to repeat the process because after rebooting the first time it somehow failed and Magisk was still showing "ctsProfile false".

Great ROM, thanks so much. Everything seems solid, there is just one thing that spoils it for me - is it possible to add a toggle for the charging light? Keeps me awake at night.

Tamsy said:
I have done this with 3 different MiMix3 now always following *exactly* the video and all the devices are showing "ctsProfile true" after the procedure. The instructions is showing 6 - Google and at the step thereafter 23 - Google Pixel 4 XL (10) so I picked the same.
Worth noting that with one of the devices I had to repeat the process because after rebooting the first time it somehow failed and Magisk was still showing "ctsProfile false".
Click to expand...
Click to collapse
Thanks for your advice but it's still not working. I assigned the Google Pixel 4 XL - fingerprint as described (also re-checking the instructions from within the youtube gem), rebooted, ctsProfile: false > did the same again, still no success. Any (other) ideas?
Appreciate your help!

chromanju said:
Thanks for your advice but it's still not working. I assigned the Google Pixel 4 XL - fingerprint as described (also re-checking the instructions from within the youtube gem), rebooted, ctsProfile: false > did the same again, still no success. Any (other) ideas?
Appreciate your help!
Click to expand...
Click to collapse
Have you checked with Magisk --> Settings --> Magisk Hide (<-- this should be set to "ON")?
Also below Settings --> Magisk Hide I set Magisk to hide itself from "Google Play Services".
It is worth a try.

Tamsy said:
Have you checked with Magisk --> Settings --> Magisk Hide (<-- this should be set to "ON")?
Also below Settings --> Magisk Hide I set Magisk to hide itself from "Google Play Services".
It is worth a try.
Click to expand...
Click to collapse
That did the trick: Magisk Hide wasn't enabled.
Thanks a lot!!

Found a bug... Gboard needs camera permission to create minis (personalised stickers like mimoji) but doesn't request it and can't be given it.

Is it possible to remove the google search bar from the home screen with this rom?

[ROM][UNOFFICIAL][prague][9] LineageOS 16.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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 :
You tell me
Instructions :
Download the latest build, gapps and nfc fix
Reboot to recovery
Flash the latest build, gapps and nfc fix
Reboot
Downloads :
Lineage Builds : https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/P8 Lite 2017/Pie/LineageOS/
Lineage Recovery : https://sourceforge.net/projects/da...ge-16.0-20201119-recovery-prague.img/download
Nfc fix : https://sourceforge.net/projects/da.../Pie/LineageOS/Nfc Fix LineageOS.zip/download
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
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. (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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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:
XDA:DevDB Information
LineageOS , ROM for the Huawei P8lite/P8 Lite
Contributors
DarkJoker360
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 16.0
Stable Release Date: 2020-11-17
Created 2020-11-17
Last Updated 2020-11-20

NOTE: Those builds require Emui 8.

Installed using Pretoriano80's TWRP but the pone doesn't boot past the warning screen.

Jhon_Locke said:
Installed using Pretoriano80's TWRP but the pone doesn't boot past the warning screen.
Click to expand...
Click to collapse
Bootloops for me as well.
Installed the rom from TWRP after wiping system and formating data, to no avail.
EDIT: It finally worked for me after a couple of additional reboots, not sure why. Testing right now...
EDIT2: BLE works, even if I received a couple of error messages at the start, it managed to sync my Mi Band 3 with this ROM.
So, the steps that worked for me are:
- Install Haky86's TWRP v3.4.
- From TWRP, wipe system.
- Install Lineage OS + NFC Fix + OpenGApps v9.0 ARM64 Nano.
- Do normal wipe.
- Format /data.
- Reboot into system.
- If it reboots twice and gets into eRecovery, reboot normally again.

So, today Bluetooth Low Energy (BLE) doesn't work, I'm constantly receiving the "Bluetooth keeps stopping" error message.
Tried to reboot the phone, but it didn'help.
I will try to provide logs this afternoon after work.

Hi,
Can you help me. I've stuck on this...

Released a new update with January 2021 security pathces, fixed occasional lags/junks and properly fixed the hwc blur issue !

Hello everyone and thank you for the work you do, especially thanks to DarkJoker360 for this and the other Rom.
Can you help me please I installed the latest Rom on S2 with cyanogenmod it's been some time.
Latest Stock Rom: PRA-LX1 8.0.0.370 (C55)
I installed:
-TWRP_3.4.0-0-prague_DarkJoker360_20200801
-lineage-16.0-20210109-UNOFFICIAL-prague
-Nfc Fix LineageOS
-open_gapps-arm64-9.0-nano-20210110
After rebooting it stops on the home screen and after waiting it enters Huawei eRecovery.
I would like to install this Rom because I read that it is not possible (I have tried and confirmed) to use "sm set-force-adoptable true" in fact I get this "Error: java.lang.IllegalStateException: Adoptable storage not available on device with native FBE", this feature is only available from android 9 (https://source.android.com/security/encryption/file-based).
I would like to install apps on SD by any method (even Stock).
Can you help me solve this problem?
I uploaded some logs I don't know if they are fine.
Thanks again
Ps: sorry but I use goggle translate

Hi, are we flash LineageOS with normal TWRP, or with Lineage Recovery?

İts okay I understand

Oğuz Karagöz said:
Hi, are we flash LineageOS with normal TWRP, or with Lineage Recovery?
Click to expand...
Click to collapse
Hello
1 HAVE STOK
2 INSTALL WITH FASTBOOT lineage-16.0-20201119-recovery-prague.img
3 Wipe cache data system dalvik / art cache
4 INSTALL WITH FASTBOOT TWRP 3.2.1-0_Dil3mm 4
5 TWRP INSTALL lineage-16.0-20210109-UNOFFICIAL-prague
6 without exiting FAI -> wipe -> advanced -> system -> resize (DO NOT FORMAT THIS TIME!)
7 flash Nfc fix, Root addon, Google Apps
8 reboot
Used very little just to see that it was not possible to use Adoptable storage.
Problem I solved by returning to stok with Android 7.
Bay

aragorn2931 said:
2 INSTALL WITH FASTBOOT lineage-16.0-20201119-recovery-prague.img
3 Wipe cache data system dalvik / art cache
Click to expand...
Click to collapse
hi,
are you sure for this one ?
when booting on lineage-16.0-20201119-recovery-prague.img, there is no possibility to wipe
EDIT : I finally found the options.
ask for confirmation for data and system, not for cache so I don't know if it really wiped cache.
and no option for wiping dalvik
after all that, result : I'm stuck on "your device is booting now..."
only difference, I used TWRP_3.4.0-0-prague_DarkJoker360_20200801.img instead of Dil3mm4
I also tried with dil3mm4 : same result

Hello, when I try to pair an external bluetooth device, such as a scale or a smartwatch, the device is recognized by the mobile phone but I cannot pair it
the message "the bluetooth app keeps interrupting" appears
the bluetooth headphones are paired correctly
how could i solve?

does anyone notice that theyre phone starting to get rlly hot after flashin this rom?

Everywhere I go said:
does anyone notice that theyre phone starting to get rlly hot after flashin this rom?
Click to expand...
Click to collapse
yes , my phone was burn. now it's ok
I think this is magisk problem.
disable the magiskhide & re-enable it.
Magiskd high CPU usage. · Issue #1279 · topjohnwu/Magisk
Magiskd is keeping the CPU running high all the time till I disable the magiskhide & re-enable it. Lineage OS 16.0 here, using Magisk canary 19.0. Its observed since 18.0 till latest build. Log her...
github.com

Is it possiible to fix to ise netflix? I had magisk root hide saftynet passes every thing is ok even serticified on play store i can download netflix login but cant watch anything.

Just a noob question
Why is the nfc fix not integrated in the rom
And why is system partition set so small I have to resize system partition or use gapp nano.
Also I am unable to boot this rom, keep saying
your device has been unlocked and can't be trusted
it does not boot custom rom.

B3rtm3n said:
Just a noob question
Why is the nfc fix not integrated in the rom
Click to expand...
Click to collapse
It was before and it still is, but since latest LineageOS updates I wasn't able to get this working anymore.
It can be turned on/off but it's not really working without the fix zip, even if files are the same included.

ok thx a lot for your answers, it has been quiet some years I flashed a smartphone and things have changed.
I have 3 more questions
1) I noticed that not only twrp made specially for the hardeware specs is needed nowadays but also adapted for each rom, is this correct?
2) do I need to be root to install a customs rom on a p8 lite 2017 or is bootloader unlocked enough?
3) does lineage recovery replaces twrp ? and if yes, how do I install it.
Ok found already that root is not needed.
I have a huge problem with resizing system partition, unable to have it resized using twrp. According to another dude I found on Youtube this can happen so I need another version of twrp.
I am using this one
Huawei P8 Lite 2017
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
and resizing does not work so each rom I flash has a too small system partition.
Is there another good twrp I could use?

B3rtm3n said:
ok thx a lot for your answers, it has been quiet some years I flashed a smartphone and things have changed.
I have 3 more questions
1) I noticed that not only twrp made specially for the hardeware specs is needed nowadays but also adapted for each rom, is this correct?
2) do I need to be root to install a customs rom on a p8 lite 2017 or is bootloader unlocked enough?
3) does lineage recovery replaces twrp ? and if yes, how do I install it.
Ok found already that root is not needed.
I have a huge problem with resizing system partition, unable to have it resized using twrp. According to another dude I found on Youtube this can happen so I need another version of twrp.
I am using this one
Huawei P8 Lite 2017
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
and resizing does not work so each rom I flash has a too small system partition.
Is there another good twrp I could use?
Click to expand...
Click to collapse
Download TWRP for prague
Download TWRP Open Recovery for prague
dl.twrp.me
this is good one

will therre be a lineage 17?

[ROM][OFFICIAL][11] LineageOS 18.1 for Galaxy Note10/Note10+/Note10+ 5G Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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 on the wiki page for your device https://wiki.lineageos.org/devices/#samsung
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
GApps: https://wiki.lineageos.org/gapps.html
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. (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/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820

reserved

reserved

What is different between this build and your previous one ?

Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available

Vishnarov said:
What is different between this build and your previous one ?
Click to expand...
Click to collapse
Read the thread's title ... It's official now.
[email protected] said:
Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available
Click to expand...
Click to collapse
No, sorry hardware is too different.

builds have been removed from the lineage os website?

Enddo said:
builds have been removed from the lineage os website?
Click to expand...
Click to collapse
Yes, see this for the reason
This affected all devices so builds of last few days were pulled and sadly we had only that one build yet
There will be new ones next week

Does the build support hardware encryption or software encryption?

You should put what models this is for as to avoid confusion

just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch

Enddo said:
just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch
Click to expand...
Click to collapse
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.

CerebralFlex said:
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.
Click to expand...
Click to collapse
certainly no locked bootloader here (have had it unlocked since right after I bought it at launch)
but yea, I'm going to try and reflash the ROM and start from scratch. I was on an outdated version of ONe UI (maybe from December) so maybe that was part of the issue
EDIT - oddly enough, I couldn't get LOS recovery installed via Odin. I tried, got success messages, but a reboot into recovery mode just showed stock recovery (I wasn't missing the button combo, to my knowledge). tried a few times before going back to using heimdall
the second attempt (with a fresh install of OneUI's latest firmware) helped me get past that vbmeta error with heimdall
got LOS recovery installed, the ROM sideloaded, and I'm up and running
thanks for the hard work @Linux4 (and all others involved in working on lineageos)

First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?

Phosphoros said:
First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?
Click to expand...
Click to collapse
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)

is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before

Enddo said:
is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before
Click to expand...
Click to collapse
It is not broken or whatever, see this from my telegram group in case you just don't figure it out on your own:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
All samsung devices using FOD have that issue it seems, only on first enrollment tho, after that it's completely fine

Linux4 said:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
EDIT - was able to get it working through a factory reset with the 'tap fast' being the key thing. it needs to fail that first attempt or something?
but it's quite quick once that hassle is over with

Enddo said:
this worked for me on my first install. describes my exact experience
but yea, it's not working right now. you need a logcat or something?
it's immediately throwing up the enrollment error message right when it attempts the first scan (every time)
Click to expand...
Click to collapse
No need for a logcat, it does work, for retrying you will need to close settings completely, just going *back* is not enough (HAL will stay in that error state)
I'm 100% sure you didn't do so also it works for everyone else

Linux4 said:
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)
Click to expand...
Click to collapse
Ok, thought about waiting for this ... thanks for confirming it!