Database Develop

[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble]

LineageOS 17.x Unofficial for Galaxy A3 2017​
{
"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 10 (Quack), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void. Or not. Depends.
* It's probably expired anyways :D
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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 Gerrit Code Review.​
What's working?
Audio
Calls
Wifi
Hotspot
Mobile data
GPS
Bluetooth
Fingerprint
Camera (both photos and video)
NFC
Sensors
Vibration
Others I have forgot
What isn't working?
Echo present in calls for the other side (no fix currently found)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (possible to fix, didn't have time to debug yet)
Stretched preview in camera, photos are fine (fix has more downsides than upsides)
Supported variants
Galaxy A3 (2017). Dual SIM is also supported.
All variants should be working but only A320FL is well tested since all developers have it.
How to install
Make sure you have latest bootloader and modem before installing this.
Make sure you are using the latest OrangeFox build. (the older ones will fail)
Make sure you have flashed the repartition script.
Download the Lineage build, optionally GApps and Magisk.
In OrangeFox format data. (Menu > Manage Partitions > Data > Format Data)
In OrangeFox wipe everything except SD and OTG.
Flash LineageOS.
Optional: Flash GApps (rightafter).
Optional: Flash Magisk.
Reboot.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
Downloads
• ROM
get.mcfy.fr
Google Drive
• Recovery
OrangeFox
• GApps
OpenGApps (arm64): OpenGApps
BiTGApps (arm64): AFH
• Root
Magisk: GitHub
Credits
Huge thanks to:
@Astrako for all the hours spent on the device tree/kernel/vendor/hardware and making this possible.
@McFy for help along the way and letting me use his server as a mirror.
LineageOS Team
Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here
XDA:DevDB Information
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble], ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
MartinYTCZ
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest modem + BL recommended
Version Information
Status: Beta
Created 2020-02-22
Last Updated 2020-08-26

Telegram group
Join here!
Go also thank @Astrako for his work on the DT, kernel, ports, recoveries and many more
Changelogs
- 20200221
Initial build
- 20200403
March security patches
Many optimisations and smaller fixes
Rootdir updated from A6 2018 Q, along with some proprietary files
Graphics now r29, from A6 2018 Q
Way too much stuff to list here, thx @Astrako for the work
- 20200613
Fixed GPlay crashes
June security patch, and all other LineageOS source changes
SEPolicy Enforcing
Reworked shims
Now using new power HAL
Many smaller optimisations
- 20200713
July security patch and all other LineageOS source changes
Reworked overlays
ROM now passes SafetyNet out of the box
Defined location provider to *hopefully* fix location with MicroG
Updated OMX libs
Other smaller fixes and optimisations
- 20200825 20200830
August security patch and all other LineageOS source changes
Updated FP from coral's April patch to keep passing SafetyNet
Switched to proprietary audio HAL - fixed in-call echo
Other smaller fixes and optimisations
NOTE: Encryption is currently extremely broken and your device will not boot if you'll try and encrypt.
- 20210118
January security patch and all other LineageOS source changes
Other smaller fixes and optimisations

Reserved

Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)

banciii said:
Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)
Click to expand...
Click to collapse
I'm dumb for not testing this, I gotta look at home

Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.

yann29 said:
Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.
Click to expand...
Click to collapse
I am not the author of Lineage 16.0, I only use the same mirror
The maintainer of LineageOS 16.0 is @McFy.
If you have the problems with the camera, this sounds like an app using the camera when you try to use it and I haven't been able to reproduce the problem. Please check all your apps and report back.
Hope you like the ROM

Ok thanks. Another issue : I can't get split-screen working with any apps. And you?

Other issue : the echos in calls...but well-known issue on lineage. Hope you will find something...

That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?

starbright_ said:
That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?
Click to expand...
Click to collapse
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing

MartinYTCZ said:
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing
Click to expand...
Click to collapse
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.

starbright_ said:
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.
Click to expand...
Click to collapse
Yup, ROM is not spoofed out of the box, so your only hope is nanodroid patcher, which doesn't seem to work in Q :/
Also if you've already got Treble, you can flash this with the TWRP you are currently using

Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.

pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I am building myself and running the latest at this time (using the crdroid device tree) and everything is running perfectly for me! (even with a few patches of my own like enabling dark mode in defaults app and a few command-line programs like rtl-sdr, no gapps (f-droid only)). Added screenshots to prove it indeed boots.
If I'm not mistaken this ROM uses the android_samsung_universal7870 device tree as it is on Gitlab?
Then the only few bugs I can talk about are the USB settings unable to be changed live while that worked on the outdated device tree from Github (screenshot can be provided), and the Camera, but I know that's already WIP.
(Sure there's echo in calls but... No one was successful at fixing this and even the crappiest patches I tried myself didn't work)
Thanks to all those who works on this device tree.

The provided Rom of the dedicated XDA thread run fine on my device but when building myself, I have the same problem : traped on bootanim.
Strange, I supose it's my buid env, my laptop is on Debian 10 and I did not make any mod on the standard base.
I will try with a VM and Ubuntu LTS as sugested by AOSP Project.

MartinYTCZ said:
LineageOS 17.x Unofficial for Galaxy A3 2017
How to install
Make sure you have latest bootloader and modem before installing this.
Created 2020-02-22
Last Updated 2020-02-22
Click to expand...
Click to collapse
Thank you for great work, can I ask from where can get latest modem and boot-loader without download whole firmware?

Hello,
Problems are solved ?
Echo present in calls for the other side (investigating)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (investigating)
Stretched preview in camera, photos are fine (probably unfixable)
And stay at home.
Best regards

Migrate doesn't detect it as an installed rom, any help?

pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I have pushed some changes to GitLab yesterday which fix this problem. You should be able to boot a new build just fine now :highfive:

[ROM][DISCONTINUED] LineageOS 18.1 for Xiaomi Mi MIX 2S

{
"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 (R), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
​
Device tree source code: LineageOS/android_device_xiaomi_polaris
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Working:
Camera (and flashlight)
WiFi
NFC
Bluetooth
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
WiFi Display
Broken:
Nothing (?)
Compatibility:
Compatible with all Xiaomi Mi MIX 2S variants.​Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v11.0.4.0 global stable package.​
Downloads:
Official download links
Notice:
No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.
Installation:
Reboot to recovery (TWRP recovery for Mi MIX 2S)
Format /system, /data and /cache
Install LineageOS zip package
Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
Important notes:​
* Required * firmware version must be based on MIUI Q-based builds.
GApps can only be flashed on clean installs.
Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.
Credits & collaborations:
All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!​
Device wiki:
Official wiki link

Thank you very very much for this great rom, works very smooth and snappy!
My twrp installation got overwritten by LOS-Recovery. It is safe to install TWRP again after installation?
So far I noticed three little bugs:
- Google feed is still missing after installing google search. Maybe this commit is missing: https://review.lineageos.org/c/LineageOS/android_packages_apps_Trebuchet/+/289553
- I can't grant sms permission to google play services. Which unfortunately prevent the installation of google pay
- Automatic brightness seems to be buggy: Sometimes the brightness level changes automatically to the smallest possible value. It will automatically get increased again after a few seconds.

pwn1ca said:
Thank you very very much for this great rom, works very smooth and snappy!
My twrp installation got overwritten by LOS-Recovery. It is safe to install TWRP again after installation?
So far I noticed three little bugs:
- Google feed is still missing after installing google search. Maybe this commit is missing: https://review.lineageos.org/c/LineageOS/android_packages_apps_Trebuchet/+/289553
- I can't grant sms permission to google play services. Which unfortunately prevent the installation of google pay
- Automatic brightness seems to be buggy: Sometimes the brightness level changes automatically to the smallest possible value. It will automatically get increased again after a few seconds.
Click to expand...
Click to collapse
1. That Google feed commit hasn't been merged yet
2. Did you install gapps after the first boot? I've seen other people have that problem when they don't flash gapps with the rom. You can factory reset, or do a clean flash again to resolve the issue.
3. I haven't installed it yet so can't help with that one

cvamoose said:
1. That Google feed commit hasn't been merged yet
Yeah, as there are still merge conflicts.
2. Did you install gapps after the first boot? I've seen other people have that problem when they don't flash gapps with the rom. You can factory reset, or do a clean flash again to resolve the issue.
Unfortunately yes, I did a factory reset and flashed gapps before first boot, issues are resolved now.
3. I haven't installed it yet so can't help with that one
Click to expand...
Click to collapse
Seems to be working for now, I'll keep an eye on that.

Tried to download it to give it a go, Google Drive says the file can't be downloaded at this time, too many downloads.
Can you share the link again, please?
Thank you

aurocha said:
Tried to download it to give it a go, Google Drive says the file can't be downloaded at this time, too many downloads.
Can you share the link again, please?
Thank you
Click to expand...
Click to collapse
Sign in to your google account and it will let you download

cvamoose said:
Sign in to your google account and it will let you download
Click to expand...
Click to collapse
Yep, you're right, it did.
Super smooth rom, daily driver material, I'll jump in.
Regards,

cvamoose said:
Sign in to your google account and it will let you download
Click to expand...
Click to collapse
Why sign in before download though ?

Does GPay work ok? And is it PlayStore certified?

The installation deletes the twrp. If I put it back, it won't start. The brightness bounces.

Encryption works? Decrypt from twrp?

bedson87 said:
Encryption works? Decrypt from twrp?
Click to expand...
Click to collapse
It does

tyratron said:
Does GPay work ok? And is it PlayStore certified?
Click to expand...
Click to collapse
I couldn't test gpay in real life conditions yet, but at least I get no error message, so I think it should work. PlayProtect certification is working. :good:
zoral566 said:
The installation deletes the twrp. If I put it back, it won't start...
Click to expand...
Click to collapse
Many thanks for that information, prevented me from reflashing

I can't flash any zip file via the los-recovery. The internal storage seems to stay encrypted. Any idea how to decrypt? Or ist this behavior expected? Is there any other way to flash zip files?

Quick question to the audience. Is BT working properly?

bgcngm said:
Quick question to the audience. Is BT working properly?
Click to expand...
Click to collapse
I was using it and had no issues.

I was not able to connect with my car BT (yatour cd changer) and my headphones Sony wh-1000xm3. However I was able to pair my watch Polar Vantage V (1st gen).

tyratron said:
I was not able to connect with my car BT (yatour cd changer) and my headphones Sony wh-1000xm3. However I was able to pair my watch Polar Vantage V (1st gen).
Click to expand...
Click to collapse
What happened? Did you get a strange error after pairing?

I can check a2dp with my car headunit later. Do you have any advice regarding the encrypted storage? Is there any way to decrypt storage while in recovery?

pwn1ca said:
I can check a2dp with my car headunit later. Do you have any advice regarding the encrypted storage? Is there any way to decrypt storage while in recovery?
Click to expand...
Click to collapse
What recovery, TWRP or Lineage recovery? TWRP should work, but Lineage one doesn't support userdata decryption by design.

[ROM][UNOFFICIAL][11][lavender] LineageOS 18.1

{
"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, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
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.
What's working:
Everything (if it's not true - tell me)
Features:
4.4 EAS kernel with generater energy model
QS panel 3x3, 3x2 when there is not enough space on the screen (TODO: Make a magisk module to change the QS panel)
Fixed traffic indicator location
Removed black QS status bar background
Oldcam blobs
Instructions:
Reboot to Recovery (Prefer OrangeFox)
Format data, wipe cache, dalvik
Flash fresh firmware (optionally)
Reboot to recovery again
Flash the LineageOS build and any other addons you want (for example, Magisk)
Reboot to the system
Downloads:
ROM: here
Firmware: here. All firmwares for lavender are supported (Prefer latest Global Stable)
NanoDroid with MicroG: here. MicroG will work without the need to patch the system, signature spoofing already exists, but only for MicroG! Flash via Magisk recommended.
NikGApps: here
XDADevDB Information
LineageOS, ROM for the Xiaomi Redmi Note 7
Contributors: ElXreno
Source Code: https://github.com/LineageOS
Device Source: https://github.com/ElXreno/android_device_xiaomi_lavender
Kernel Source: https://github.com/ElXreno/android_kernel_xiaomi_sdm660
ROM OS Version: Android 11
ROM Kernel: Linux 4.4
Based On: AOSP
Version Information
Status: Stable
Telegram links: Support chat && Channel
Created 2021-02-01
Last Updated 2021-02-14

LineageOS 18.1 MicroG
Release date: 31/01/'21
Changelog:
Initial build
Traffic indicator moved to the right side
Removed black QS status bar background
Something else
Notes:
MicroG not included (but signature spoofing available, only for MicroG!). Use NanoDroid package if you want.
4.4 EAS with another energy model
Oldcam blobs
IORap enabled
QS 3x3
Download: SourceForge | MEGA

The rom goes very fast, the only thing that is really annoying is that when making or receiving calls the call interface does not appear, is there any way to solve this problem?

WOLFLIFEX said:
The rom goes very fast, the only thing that is really annoying is that when making or receiving calls the call interface does not appear, is there any way to solve this problem?
Click to expand...
Click to collapse
* I am not responsible for what may happen to your device, it is simply a solution that worked for me *
I found a solution for this problem the problem was in the NikGApps the shortest solution is:
1
Flash the rom first then reboot
2
Boot up, set the device normally and turn it off
3
Start recovey and flash NikGApps ( preferably the latest Canary version:
https://sourceforge.net/projects/nikgapps/files/Canary-Releases/NikGapps-R/03-Feb-2021/ )
4
Reboot.

LineageOS 18.1 MicroG
Release date: 14/02/'21
Changelog:
IORap selinux denials fixed
AOSP Surfaceflinger used
Fluence recording enabled
Other changes
Notes:
MicroG not included (but signature spoofing available, only for MicroG!). Use NanoDroid package if you want.
4.4 EAS with another energy model
Oldcam blobs
IORap enabled
QS panel 3x3, 3x2 when there is not enough space on the screen
Thanks:
@VerpaPhallus & @projectfluid for his device tree & kernel
Download: MEGA | IPFS

I'm currently using official 17.1 lineage OS can i dirty flash this ROM to change to 18.1 Lineage OS and is it stable for daily driver? Thanks in Advance

Babloo1989 said:
I'm currently using official 17.1 lineage OS can i dirty flash this ROM to change to 18.1 Lineage OS and is it stable for daily driver? Thanks in Advance
Click to expand...
Click to collapse
I recommend you to make a clean install, but you can try dirty. As for stability: almost everything is stable, but I would not recommend it if stability is critical.

ElXreno said:
What's working:
Everything (if it's not true - tell me)
Click to expand...
Click to collapse
So, everyone writes that even if the ROM has easily discoverable bugs, BUT, how stable is this ROM? I'm trying to find a good one for a daily driver that won't let me down in an emergency but so far it seems that all the ones I've seen are either a beta or have obvious bugs even though they're called "official" The only one I would potentially end up on is MIUI.

Can it be used as daily Driver?

Netflix and other apps thar block rooted phones are working fine?

Hi, I was using LOS 17.1 for MicroG without any issues but recently upgraded to LOS18.1 for MicroG (downloaded from lineage.microg.org and verified the download). Everything works well except for the camera. Out of the box camera app freezes frequently and then I tried Open Camera and a another camera app. Open Camera is a bit stable but still freezes regularly. Problem is worse when the camera app is being called by other apps.
I note that this has been reported in LOS forum but wondering whether there is a quick work around for this problem.
Many thanks.

evil-google said:
Hi, I was using LOS 17.1 for MicroG without any issues but recently upgraded to LOS18.1 for MicroG (downloaded from lineage.microg.org and verified the download). Everything works well except for the camera. Out of the box camera app freezes frequently and then I tried Open Camera and a another camera app. Open Camera is a bit stable but still freezes regularly. Problem is worse when the camera app is being called by other apps.
I note that this has been reported in LOS forum but wondering whether there is a quick work around for this problem.
Many thanks.
Click to expand...
Click to collapse
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.

Walden0 said:
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.
Click to expand...
Click to collapse
Thanks very much for the response. From what you are saying, I feel it may be easier to just downgrade to LOS17.1 which I was using before? I guess the other option I have is to wait for the next update to see whether the issue will be fixed in that release.
Thanks for your suggestion and clarification.

evil-google said:
Thanks very much for the response. From what you are saying, I feel it may be easier to just downgrade to LOS17.1 which I was using before? I guess the other option I have is to wait for the next update to see whether the issue will be fixed in that release.
Thanks for your suggestion and clarification.
Click to expand...
Click to collapse
i am also using los Q because i find it the most stable one. I m using loscam patch in Q as well for better video quality although.
And the camera issue wont get fixed until and unless someone takes over the development of los. currently it has no maintainer and tge builds we get are automated with los source side changes, not device side changes.

Walden0 said:
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.
Click to expand...
Click to collapse
@Walden0, I thought I might give your suggestion a try before downgrading to 17.1 version. Can you please clarify the following?
1. To add the old camera blob, I could install this zip via Yellowfox Recovery?
2. How can I find out which kernel will support this oldcam blob?
Many thanks.

I have never heard of yellowfox recovery but if its based on twrp then most likely it should be able to flash the zip. (maybe you mean orangefox, if yes then you can flash)
The kernel should have "oldcam" or "old" in its name.

Walden0 said:
I have never heard of yellowfox recovery
Click to expand...
Click to collapse
Just being color blind!!...of course, it is Orange Fox Recovery!!
Interestingly, after I did my post, I just opened Settings->Apps->Camera and pressed 'force stop'. Then I started Open Camera which is what I normally use and so far it appears to be behaving OK. I tried a few still shots and one or two short videos - no freezing as yet but it is too early to know. I will keep testing over the next couple of days and see how it goes.
Thanks for your prompt response.

Just to report that the work around by disabling the Camera app so far have fixed the problem.
Any one who has the same problem may want to try out the following steps;
1. Go to Settings->Apps->Camera->Force Stop
2. Then use an installed app such as Open Camera
Note this is not a permanent solution but a work around and this has to be done each time the phone is rebooted.
EDIT: updated to 6 Dec 21 version and the camera behaves even worse than with the initial install! The above fix does not work anymore although it worked most of the time with the November update.

This ROM was abandoned, pitty, much more polished than official https://forum.xda-developers.com/t/...8-1-for-redmi-note-7-lavender.4381893/page-10.
But both suffer from the same issue: no Mass Storage Gadget so that UMS can work to make memory as USB drive.

[ROM] Lineage-OS-18.1 [REDMI 4A/5A] [UNIFIED [UNOFFICIAL

[ROM] Lineage-OS-18.1 [REDMI 4A/5A] [UNIFIED [UNOFFICIAL]
{
"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:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), 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.
What's working:
Boot
Bluetooth
Camera / Camcorder
Double Tap to Wake
IR Blaster
RIL (LTE/Dual SIM/SMS)
FM Radio
VoLTE
GPS
WiFi
WiFi Hotspot
USB (ADB/MTP/PTP)
Video Playback
Touch
Sensors
SELinux enforcing
What's not working:
You tell me.
Gapps - Nik core or Bit gapps
Clean flash necessary to avoid issues
Installation instructions
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system, data, cache and vendor partitions
Flash ROM.
Optional: Install the Google Apps addon package.
Optional: Install Magisk for Root.
DOWNLOAD
Kernel Source - https://github.com/Thagoo/platform_kernel_xiaomi_msm8917/tree/r
Device tree source - https://github.com/Thagoo/android_device_xiaomi_rolex
Rom Source - https://github.com/LineageOS

Reserved

how much bandwidth (to download the repo) is required to build this on my system ?

[email protected] said:
how much bandwidth (to download the repo) is required to build this on my system ?
Click to expand...
Click to collapse
Noob's guide to building AOSP from scratch.
So, I have been an Android developer since 2009 (HTC dream), and have been actively "consuming" XDA, custom ROMs and other tweaks. Surprisingly, never tried to build my own ROM from scratch. Recently, something made me want to build the ROM, so...
forum.xda-developers.com
This thread explains better than me

Is this based on kernel 4.9? can i use the trinton kernel with this one?

Thread closed
Threads without proper source are not allowed.
@op: Please pm me when you can provide the necessary.
strongst
Forum Moderator
Thread open again

When coming from stock to this ROM or one of the other Lineage-based ROMs, yours prompts for a pre-boot decryption password and crashes on attempts to encrypt, while the other doesn't, using the apparently included default. That includes upstream TWRP releases.
Any data I could supply to help get FDE working on this? Might be useful for your other 11/R-based ROMs, if this occurs on them, as I haven't checked.

zer0def said:
When coming from stock to this ROM or one of the other Lineage-based ROMs, yours prompts for a pre-boot decryption password and crashes on attempts to encrypt, while the other doesn't, using the apparently included default. That includes upstream TWRP releases.
Any data I could supply to help get FDE working on this? Might be useful for your other 11/R-based ROMs, if this occurs on them, as I haven't checked.
Click to expand...
Click to collapse
You xan flash magisk to avoid and i recommend you to other recoveries which has extended features for orangefox they disable forcencryption

Thago said:
You xan flash magisk to avoid and i recommend you to other recoveries which has extended features for orangefox they disable forcencryption
Click to expand...
Click to collapse
I know, however I actually find forceencryption valuable, in spite of it's shortcomings, and the linked Lineage 17.1 ROM makes it work (and makes TWRP work with it, too). The solution I would be looking for is not to disable, but rather support it.

zer0def said:
I know, however I actually find forceencryption valuable, in spite of it's shortcomings, and the linked Lineage 17.1 ROM makes it work (and makes TWRP work with it, too). The solution I would be looking for is not to disable, but rather support it.
Click to expand...
Click to collapse
Disk encryption is not stable yet on android 11 you should wait untill it get stable or better go with android 10 ROMs

Seems to be squared off in upstream. Since there's no official support for MSM8917, if you're tracking changes from a different device's tree, which device is it?

zer0def said:
Seems to be squared off in upstream. Since there's no official support for MSM8917, if you're tracking changes from a different device's tree, which device is it?
Click to expand...
Click to collapse
CAF

Update 2021 Apr 07
Changelog:
- audio: Update upto LA.UM.9.6.2.r1-03300-89xx.0
- audio: Update mixer_paths from LA.UM.9.6.2.r1-03300-89xx.0
- Switch to New AIDL Power HAL
- Update CarrierConfig from LA.UM.9.6.2.r1-03300-89xx.0
- Fix device manufacturer & model exif value in Camera apps thanks to iusmac for PR
- Set lmkd configuration properties
- Update Power Profile XML
- Configure PSI for low_ram device
- Block some more wakelocks Fixup deepsleep issue
- Rebased kernel
- merge linux-v4.9.264
DOWNLOAD​

Any changelog from 08.04.2021 build?

suzver said:
Any changelog from 08.04.2021 build?
Click to expand...
Click to collapse
[ROM] Lineage-OS-18.1 [REDMI 4A/5A] [UNIFIED [UNOFFICIAL
[ROM] Lineage-OS-18.1 [REDMI 4A/5A] [UNIFIED [UNOFFICIAL] #include /* * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some...
forum.xda-developers.com

hi, i've been testing this rom, and i haven't been able to make it work with my sim card. The official rom works fine, and other sim cards from other vendors work fine on this rom.
I tried flashing the official firmware fw_rolex_miui_HM4AGlobal_V10.2.3.0.NCCMIXM_69d07208fd_7.1.zip, but I couldn't get it to work either.
Lineageos 17.1 doesn't work either.

jlneder said:
hi, i've been testing this rom, and i haven't been able to make it work with my sim card. The official rom works fine, and other sim cards from other vendors work fine on this rom.
I tried flashing the official firmware fw_rolex_miui_HM4AGlobal_V10.2.3.0.NCCMIXM_69d07208fd_7.1.zip, but I couldn't get it to work either.
Lineageos 17.1 doesn't work either
jlneder said:
hi, i've been testing this rom, and i haven't been able to make it work with my sim card. The official rom works fine, and other sim cards from other vendors work fine on this rom.
I tried flashing the official firmware fw_rolex_miui_HM4AGlobal_V10.2.3.0.NCCMIXM_69d07208fd_7.1.zip, but I couldn't get it to work either.
Lineageos 17.1 doesn't work either.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
jlneder said:
hi, i've been testing this rom, and i haven't been able to make it work with my sim card. The official rom works fine, and other sim cards from other vendors work fine on this rom.
I tried flashing the official firmware fw_rolex_miui_HM4AGlobal_V10.2.3.0.NCCMIXM_69d07208fd_7.1.zip, but I couldn't get it to work either.
Lineageos 17.1 doesn't work either.
Click to expand...
Click to collapse
Update your recovery to the latest orangefox recovery which has 4.9 kernel
Wipe data vendor system cache and dalvik cache before flashing the rom
Restore perisist backup (look for redmi 4a persist backup if you don't have)

Hi. I've been having a problem with this new build. After a while, after waking up the phone from deep sleep, I can't open any app or phone setting. The apps just stay loading. Programmed tasks like alarms don't work, either. I have to reboot the phone every once a while as a workaround. This problem was also present in Lineage OS 17, but it didn't happen with Thagoo's older LOS 18.1 build on Telegram. Maybe it's due to the new blocked wakelocks?

Thago said:
Update your recovery to the latest orangefox recovery which has 4.9 kernel
Wipe data vendor system cache and dalvik cache before flashing the rom
Restore perisist backup (look for redmi 4a persist backup if you don't have
Click to expand...
Click to collapse
Sorry, I guess It was a hardware problem. I had another xiaomi redmi 4a and it worked there so i just switched phones. Thank you anyway.

Nice job Qcom sir

[ROM][12L][UNOFFICIAL] LineageOS 19.1 [STABLE | Permissive]

{
"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:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), 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.
Bugs
What's working:
Boot
Bluetooth
Bluetooth Headphone (Media/In-Call)
Camera / Camcorder
Double Tap to Wake (From Settings>System>Gestures>Double Tap To Wake )
Fingerprint Sensor
FM Radio
IR Blaster
GPS
RIL (LTE/Dual SIM/SMS)
VoLTE
WiFi
WiFi Hotspot (2.4Ghz / 5Ghz)
USB (ADB/MTP/PTP)
Touch
Sensors
ExFAT SDCard
WiFi Display (Cast)
What's not working:
Hardware Encryption
SELinux is permissive
You tell me.
Installation instructions
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system / data / cache partitions
Flash ROM.
Optional: Install the Google Apps addon package.
Optional: Install Magisk for Root.
Supported models:
hydrogen, helium
Downloads
Recovery : Official TWRP or Unofficial TWRP
Firmware : Latest Firmwares
Gapps : NikGApps 12L ARM64
Stable GCAM : HyperCam_E3.0_Q
Rom :
Hydrogen
Helium
Sources
Device/Kernel/Vendor Tree: Sources
Donate
DONATE To Me
Big Thanks
LineageOS Team.
@ Carlos Arriaga
@ TheStrix
@ nijel8
all RedMi Note3 & Mi Max contributors.

Changelogs
2022/08/07
Updated with August security patches.
Upstream updates and fixes.
Updated media configs from LA.BR.1.3.7.c26-04300-8976.0.
2022/07/12
Updated to Android 12.1.0_r11 with July security patches.
Upstream updates and fixes.
Fixed video playback for most video formats.
Updated media blobs from S62Pro RKQ1.210406.002.
2022/06/13
Updated to Android 12.1.0_r7 with June security patches.
Upstream updates and fixes.
2022/05/15 - REUPLOADED
Updated to Android 12.1.0_r5 with May security patches.
Upstream updates and fixes.
2022/04/07
Updated to Android 12.1.0_r4 with April security patches.
Updated stock app icons.
Upstream updates and fixes.
2022/03/20
Updated to Android 12L with March security patches.
Updated to LineageOS 19.1.
Upstream updates and fixes.
Clean flash recommended.
2022/03/12
Updated to Android 12.0.0_r29 with February security patches.
Upstream updates and fixes.
Fixed Fingerprint sensor enrollment.
Fixed Bluetooth In-Call audio.
Bring back FM Radio.
2022/02/05
Initial release of LineageOS 19.0 for Hydrogen/Helium.

Screenshots

Who is this @tarkzim? Superman! That's who!
Thank you so much!

Amazed by your determination to keep MAX UpToDate !
Wish you the happiness you deserve

Thank you so much for keeping this phone alive!

@tarkzim noticed that Google Play Store (nikgapps) do not seem to always properly detect the device is connected through WiFi. Like it is waiting for a mobile connection?
Tried various access points.

The source link of los19, tree kernel and vendor pls share

coffee-turtle said:
@tarkzim noticed that Google Play Store (nikgapps) do not seem to always properly detect the device is connected through WiFi. Like it is waiting for a mobile connection?
Tried various access points.
Click to expand...
Click to collapse
You should just grant it a network use or something like that from an app info page, had the same issue but it solved it

1stWinters said:
You should just grant it a network use or something like that from an app info page, had the same issue but it solved it
Click to expand...
Click to collapse
Thank you. I will check that tonight. I remember that from earlier days now that you mentioned it. Thank you for taking the time to respond. Love this device.

It may be my old 2/16 GB device and it's low performance, but the YouTube app seems to not load videos, and when it does, it's taking an eternity, so I'm trying to understand if it's just my device, or anyone else has this issue. Connection is good btw, the app used to perform better on LOS 18.1

1stWinters said:
It may be my old 2/16 GB device and it's low performance, but the YouTube app seems to not load videos, and when it does, it's taking an eternity, so I'm trying to understand if it's just my device, or anyone else has this issue. Connection is good btw, the app used to perform better on LOS 18.1
Click to expand...
Click to collapse
just curious if your YouTube videos play any better through a browser? That will help narrow things down.

coffee-turtle said:
just curious if your YouTube videos play any better through a browser? That will help narrow things down.
Click to expand...
Click to collapse
Black loading screen, just like the app, tho, sometimes loads instantly, maybe like 1 out of 10 times

1stWinters said:
Black loading screen, just like the app, tho, sometimes loads instantly, maybe like 1 out of 10 times
Click to expand...
Click to collapse
I'm wondering if it's because I've set my SD card as my internal storage, which is usually slow, and the app tries to buffer the video onto it, but I doubt it's actually because of it, just my thoughts

1stWinters said:
Black loading screen, just like the app, tho, sometimes loads instantly, maybe like 1 out of 10 times
Click to expand...
Click to collapse
Could it be the network you're on?
You could try clearing browser's and app's cache, and maybe data too with app.

coffee-turtle said:
Could it be the network you're on?
You could try clearing browser's and app's cache, and maybe data too with app.
Click to expand...
Click to collapse
I even tried reinstalling both of these apps, didn't help unfortunately

1stWinters said:
I'm wondering if it's because I've set my SD card as my internal storage, which is usually slow, and the app tries to buffer the video onto it, but I doubt it's actually because of it, just my thoughts
Click to expand...
Click to collapse
Try on another network, or set device back to defaults using original storage location?
Not sure what is happening there. I expected YouTube through the browser to play fine.

coffee-turtle said:
Try on another network, or set device back to defaults using original storage location?
Not sure what is happening there. I expected YouTube through the browser to play fine.
Click to expand...
Click to collapse
Does yours work alright tho? I'll test it all in the next updates, pretty sure I'm going to be factory resetting (wiping) my device anyways

Amazed to see this, never expected this device to be on the latest Android version at all.
Thanks for this, I'll flash and would let you know.

1stWinters said:
Does yours work alright tho? I'll test it all in the next updates, pretty sure I'm going to be factory resetting (wiping) my device anyways
Click to expand...
Click to collapse
Yes. VERY stable as I load my apps back on! Just had to manually give network access to some gapps.