[DISCONTINUED][ROM][UNOFFICIAL][gta4xl][10] LineageOS 17.1 for Galaxy Tab S6 Lite (LTE) - Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri

[DISCONTINUED][ROM][UNOFFICIAL][gta4xl][10] LineageOS 17.1 for Galaxy Tab S6 Lite (LTE) - Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri

{
"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.
*/
FEATURES
SELinux enforcing
Improved Performance
Flip cover working
Touchscreen input disabled while using SPen
SPen tilt orientation working
Latest Linux 4.14.x kernel
ROM is signed with my developer keys
KNOWN ISSUES
Miracast not working (Google removed it in AOSP Pie)
You tell me
DOWNLOAD
Warning: 17.1 is now discontinued, please use 18.1 instead
Galaxy Tab S6 Lite LTE: lineage-17.1-20201215-UNOFFICIAL-gta4xl.zip
INSTALLATION
Follow the instructions at the TWRP Thread to install TWRP
If coming from another ROM (Stock ROM, GSI or whatever) you need to wipe data and cache
Also be sure your /data is ext4, if not format /data to ext4 (in TWRP at "Advanced Wipe" -> Select Data -> "Change Filesystem")
Put the ROM zip on your external sdcard (if you are already on my LineageOS and have decrypted /data you might also put it in internal storage) and flash it using TWRP
Optional:
Flash GApps
Flash Magisk
SUPPORT
Telegram support group
THANKS TO
@modpunk
@derf elot
I used their source code for LineageOS for Galaxy S10 series (which I have also contributed to) as base for my ROM.
XDA:DevDB Information
lineage-gta4xl, ROM for the Samsung Galaxy Tab S6 Lite
Contributors
Linux4
Source Code: https://github.com/gta4xl
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 0.8
Beta Release Date: 2020-09-23
Created 2020-09-23
Last Updated 2020-12-15

FAQ
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:

CHANGELOG
2020-12-15
Update to Linux 4.14.210
Add glove mode / high touch sensitivity mode
2020-12-05 system securitypatch
Netflix now works without liboemcrypto disabler (L3 only, Samsung doesn't seem to allow L1 with custom ROM installed)
2020-11-01 vendor securitypatch
2020-11-19
Fixed RIL on LTE variant
2020-11-08
Fix SPen tilt orientation issue (tilt_x and tilt_y were swapped)
Don't limit system inode count (should fix flashing bigger gapps packages)
Update Linux to 4.14.203
2020-11-05 system securitypatch
2020-10-15
Turn display off when closing flip cover
Fix audio output over usb-c
Improve audio quality
2020-10-08
Change SPen pointer to stock one
SELinux enforcing on LTE variant
Fix DT2W on LTE variant by updating dtbo sources from decompiled stock ones
Fix display bugs on LTE variant by updating dtbo sources from decompiled stock ones
Update to Linux 4.14.200
Fix bluetooth issues
2020-10-05 system security patch
2020-09-25
Enable nightlight (thanks to erfanoabdi)
Fix /system_root mounting issues in TWRP
2020-09-24
Update blobs to P61*XXU2BTI3, 2020-09-01 vendor security patch
Improves GPS speed
2020-09-23
Initial release

Reserved

Linux4 said:
FEATURES
SELinux enforcing
Improved Performance
Flip cover working
Touchscreen input disabled while using SPen
ROM is signed with my developer keys
KNOWN ISSUES
Miracast not working (Google removed it in AOSP Pie)
You tell me
DOWNLOAD
Galaxy Tab S6 Lite WiFi: lineage-17.1-20200923-UNOFFICIAL-gta4xlwifi.zip
INSTALLATION
If coming from stock or the other LineageOS ROM (GSI) you need to format /data with TWRP
Put the ROM zip onto your external sdcard (if you are already on my LineageOS and have decrypted /data you might also put it in internal storage) and flash it using TWRP.
THANKS TO
@modpunk
@derf elot
I used their source code for LineageOS for Galaxy S10 series (which I have also contributed to) as base for my ROM.
XDA:DevDB Information
lineage-gta4xl, ROM for the Samsung Galaxy Tab S6 Lite
Contributors
Linux4
Source Code:https://github.com/gta4xl
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2020-09-23
Created 2020-09-23
Last Updated 2020-09-23
Click to expand...
Click to collapse
Thanks your work cheers :highfive:

Installed Lineage and it was booting, but had some problems with installing Gapps.
After 3 attempts succeeded with installing Open Gapps pico from sd-card.
In the first 2 attempts, TWRP gave error "failed to mount '/system_root"
I found this: https://github.com/topjohnwu/Magisk/pull/2496 , probably due to dynamic partitions.
Wifi, Bluetooth, pen are working, but gps is not working.

Iceman66 said:
Installed Lineage and it was booting, but had some problems with installing Gapps.
After 3 attempts succeeded with installing Open Gapps pico from sd-card.
In the first 2 attempts, TWRP gave error "failed to mount '/system_root"
I found this: https://github.com/topjohnwu/Magisk/pull/2496 , probably due to dynamic partitions.
Wifi, Bluetooth, pen are working, but gps is not working.
Click to expand...
Click to collapse
Yes, TWRP's support for dynamic partitions is still not fully finished.
Gps is working for me, but it takes a very long time initializing, that should be fixed with the next update (I'm currently working on including Samsung's september secpatch update on which gps seems to work faster)

Linux4 said:
Yes, TWRP's support for dynamic partitions is still not fully finished.
Gps is working for me, but it takes a very long time initializing, that should be fixed with the next update (I'm currently working on including Samsung's september secpatch update on which gps seems to work faster)
Click to expand...
Click to collapse
Thx, keep up the good work!

I have uploaded an updated version with september vendor security patch which should also fix the gps issues

Dirty flashed the 0924 version, but i ran into the issue with system_root and got a bootloop.
After format with TWRP, clean flashed from SD-card and booted successful.
GPS is fixed!

I have uploaded a new version which fixes the /system_root mounting issues in TWRP (yes it was caused by LineageOS) but (only for this update, for the next ones it will work without reboot) you will have to reboot to recovery once the update finished to be able to install e.g GApps.

MicroG nanodroid doesn't work yet ? any alternative ?

StuKaGel said:
MicroG nanodroid doesn't work yet ? any alternative ?
Click to expand...
Click to collapse
I think nanodroid patcher is not supported on Q yet. You can build this rom yourself with signature spoofing patch or you can also use xposed + fakegapps module, but I dont know if it works on Q, you can try it out.

Fakegapps with microg via magisk worked wonders
Are there any way to customise the cursor? It's quite hard to see using the default cursor

StuKaGel said:
Fakegapps with microg via magisk worked wonders
Are there any way to customise the cursor? It's quite hard to see using the default cursor
Click to expand...
Click to collapse
It don't think it can be changed by user. Btw do you really mean cursor or the pointer used for spen?

Linux4 said:
It don't think it can be changed by user. Btw do you really mean cursor or the pointer used for spen?
Click to expand...
Click to collapse
The S-pen pointer
I found this guide https://daniel-baker.photography/asus-fonepad-7-change-mouse-cursor/ , but I don't want to revert to stock and don't understand how to extract the image file

StuKaGel said:
The S-pen pointer
I found this guide https://daniel-baker.photography/asus-fonepad-7-change-mouse-cursor/ , but I don't want to revert to stock and don't understand how to extract the image file
Click to expand...
Click to collapse
It can be changed using an overlay, but that would also change the pointer when using e.g Bluetooth mouse because both use the same pointer. I'll probably add that in the next build.

Linux4 said:
It can be changed using an overlay, but that would also change the pointer when using e.g Bluetooth mouse because both use the same pointer. I'll probably add that in the next build.
Click to expand...
Click to collapse
I think for most people using a mouse is not really important on this device (due to the s pen), thank you very much tho
btw, do I need to clean flash the next build or could I just dirty flash it + magisk when the next build rolls out (I don't particularly like google, so no Gapps for me) ?

StuKaGel said:
I think for most people using a mouse is not really important on this device (due to the s pen), thank you very much tho
btw, do I need to clean flash the next build or could I just dirty flash it + magisk when the next build rolls out (I don't particularly like google, so no Gapps for me) ?
Click to expand...
Click to collapse
Dirty flash should work but you should still make a backup! The other user only had to wipe because gapps failed to install and removing gapps requires a wipe.

Linux4 said:
Dirty flash should work but you should still make a backup! The other user only had to wipe because gapps failed to install and removing gapps requires a wipe.
Click to expand...
Click to collapse
Of course, a backup is always important for everything
Will await for your next release then, keep up the good work
on an unrelated note, SElinux is disabled on mine, is it because of magisk or is it because I haven't yet encrypted my device ?

Related

[ROM][OFFICIAL]LineageOS-15.1[Albus][Moto Z2 Play]

{
"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, after-market firmware distribution of Android re-branded CyanogeMod, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* 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 and CyanogenMod with extra contributions from many people within the Android community. 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.
Warning!!!
BackUp EFS partition before installing. .If you lose IMEI , use this backup to retrieve it in future.
Installation
First time LineageOS installation on your Moto Z2 Play:
Unlock your bootloader if you haven't done so already
Flash a custom recovery via Fastboot (64 bit TWRP is needed)
Copy Gapps (64 bit) and Lineage OS flash files to sdcard
Boot into Recovery
Format Internal Memory . I repeat Format.. (Not Wipe) (after format reboot to recovery)
Flash the LineageOS zip from SD card
Flash GApps from SD card
Reboot
Upgrading from earlier version of LineageOS :
Push the new LineageOS zip to your SD card
Boot into Recovery (64 bit TWRP)
Flash the LineageOS zip from SD card
Flash the most recent GApps (64 bit) for 8.x
Reboot
Downloads
- LineageOS : Weekly Builds
- Google Apps (arm64) : GApps
Bugs
You tell me
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
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.)
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg > dmesg.txt
If it is a random reboot, grab kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Code:
adb shell cat /sys/fs/pstore/console-ramoops
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 or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* LineageOS version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all DO NOT flash any SuperSu/SuperUser/SuperMan zip package to get root. Go to Settings>Developement Settings>Root access and select "Apps Only"
Why no nightly today?
Build failed. Check again tomorrow
When do I have to wipe data?
You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
Will you add <insert awesome feature here>?
I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Kernel Source : Here
Device Tree: Here
XDA:DevDB Information
LineageOS, ROM for the Moto Z2 Play
Contributors
rahulsnair, vache
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2018-09-17
Beta Release Date: 2018-01-13
Created 2018-01-06
Last Updated 2018-09-17

06-Jan-2017
Initial Release
13-Jan-2017
Fixed Camera
Fixed audio/headphone related issues
Tweaked haptic feedback
Downstreamed kernel to minimize bugs
Blobs updated to leaked oreo
24-Jan-2017
Fixed lag in audio playback
Fixed Vo-LTE support
Added lineage features (recording, hide navigation bar etc.. )
Fixed blue-tooth device name
Model specific init changes
27-Jan-2017
SeLinux Enforced
Implement 64 bit sensors libs
Ambient display reboot fixed
4-Feb-2017
Motorola Mod Support Added (verified battery mod , gamepad working)
Swicthed to permissive (Temporarily : TODO : fix moto mod denials)
Live display color issue fixed
Audio libs updated
Haptic feedback tweak
10-Feb-2017
Clean flash requires power source to initial boot fixed
Selinux switched to enforcing
Display color fixed
Kernel built with Clang (thanks to @Alberto97 )
Kernal Re-based to MMI-NPSS26.118-19-18
Greybus/V4l5_hal drivers updated to MMI-NPSS26.118-19-18
f2fs updated to MMI-NPSS26.118-19-18
prima updated to LA.UM.5.6.r1-06700-89xx.0
Camera blobs updated
18-Feb-2017
Running in minimal kernel
Mod driver updated
Lineage adaptive icons
Camera improvements
Selinux permissive

Reserved

Unable to boot flashed via the 64bit recovery did a clean wipe also formatted internal storage. Started to boot showed lineage os then reboots back into recovery.

Cleanser2012 said:
Unable to boot flashed via the 64bit recovery did a clean wipe also formatted internal storage. Started to boot showed lineage os then reboots back into recovery.
Click to expand...
Click to collapse
Same here
Sent from my [device_name] using XDA-Developers Legacy app

We have the same problem
Enviado desde mi Moto Z2 Play mediante Tapatalk

I pulled these logs after it rebooted back into twrp recovery

I've managed to boot in after the format and flash. But data was disabled, screen off sent a shut down signal and went directly to the recovery. I'll flash stock and try another way around. props

Those who experience reboot .. disable ambient display.

I came here to say what I'm finding, I'm using it on the bike xt1710-07, the automatic theme works using the launcher pixel2, I found it very cool, using a dark wallpaper, the theme darkens and the theme turns white, turn off the screen only in the power button of the device, the rom supports the magisk as I am using it and I have root access, as you mentioned the device does not stay reigning alone, I had to disable the display environment, it's a shame the camera does not work, in my opinion this was the that I found so far, if the camera by at least the other problems work does not affect much, I loved this rom.
---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------
sorry my english because I'm from Brazil and I'm writing on google translate

carlinhossp said:
I came here to say what I'm finding, I'm using it on the bike xt1710-07, the automatic theme works using the launcher pixel2, I found it very cool, using a dark wallpaper, the theme darkens and the theme turns white, turn off the screen only in the power button of the device, the rom supports the magisk as I am using it and I have root access, as you mentioned the device does not stay reigning alone, I had to disable the display environment, it's a shame the camera does not work, in my opinion this was the that I found so far, if the camera by at least the other problems work does not affect much, I loved this rom.
---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------
sorry my english because I'm from Brazil and I'm writing on google translate
Click to expand...
Click to collapse
Hey mate, could you please just backup your EFS partition and send it to me? i lost my during the format and now i have no mobile data. Thanks in advanced!!!

Thank you and good work.

13-Jan Release Note
New build has been released.
Link has been updated in the main post.
Change logs has been updated in the second post
Overview
Fixed up camera
Fixed up audio/headset related issues
Tweaked haptic feedback
Bugs left:
Ambient display needs to be turned off. (Otherwise device restarts)
Flashlight chop chop gesture doesn't work
Quick download link : here
Make sure you take EFS backup before flashing any custom rom...

just backed up stock and flashed latest build.... hooray for camera and FM Radio Ambient display still causing reboot to recovery, but I never use that feature on any of my devices so I disable it. I'll report any bugs I find and provide logcat(s) if needed.
I have the wireless charging moto mods addon. I did some looking around on the moto z (griffin) forum and found an addon to flash. I might try it after I get this build setup and backed up.
*edit* addon does not work without modding since it's looking for griffin.

I applaud you.!

I think no custom ROMs have supported MotoMod features yet. I'm so eager to try this ROM. It seems much more stable now. Good job,rahulsnair...:good:

huatz84 said:
I think no custom ROMs have supported MotoMod features yet. I'm so eager to try this ROM. It seems much more stable now. Good job,rahulsnair...:good:
Click to expand...
Click to collapse
Im this ROM, moto actions, like biometric gestures works fine.
Gesture to open camera too

About root, magisk works fine. Tested:!

huatz84 said:
I think no custom ROMs have supported MotoMod features yet. I'm so eager to try this ROM. It seems much more stable now. Good job,rahulsnair...:good:
Click to expand...
Click to collapse
Does that include the power Mods, like Turbopower?
I love custom Roms, but I can't live without my battery Mods. On the z1, that wouldn't be so bad, but z2......

bgochoa said:
Im this ROM, moto actions, like biometric gestures works fine.
Gesture to open camera too
Click to expand...
Click to collapse
Only twist to capture works. Hopefully,Motomods will be supported. I just ordered incipio power pack.
kewlzter said:
Does that include the power Mods, like Turbopower?
I love custom Roms, but I can't live without my battery Mods. On the z1, that wouldn't be so bad, but z2......
Click to expand...
Click to collapse
Yeah..there are some roms which have supported Moto Mods in griffin (Z Play).
Sent from my Moto Z2 Play using XDA Labs

[ROM][OTA][10.x] LineageOS 17.1 Unofficial [wayne/ Mi 6X]

#ISSUE #Persist
People who is on Android 10 or testing 10 are willing to go back to Pie will get their persist folder deleted causing(wifi ,hotspot , no signal issues)...so backup your persist from TWRP , revert to pie then flash the backup
Thanks

You sir are a legend, thanks for supporting wayne!

Thanks!!

Nice! Let's take a look.

rcstar6696 said:
#ISSUE #Persist
People who is on Android 10 or testing 10 are willing to go back to Pie will get their persist folder deleted causing(wifi ,hotspot , no signal issues)...so backup your persist from TWRP , revert to pie then flash the backup
Thanks
Click to expand...
Click to collapse
how to backup persist on twrp sir?

HSaputra_ said:
how to backup persist on twrp sir?
Click to expand...
Click to collapse
To backup persist, simply go into twrp recovery, select Backup, tick on persist partition, then backup.
To restore a backup, simply select Restore in twrp, choose your backup-ed file before, then restore.

smooth, works perfectly

The only thing I've been having issues with so far is that the System UI (that is, status bar, notifications area and stuff, not the volume and power popups tho) becomes laggy after some time (like once every 12 hours for me, so far). I don't know what causes this, but when it starts lagging, the non-functioning Digital Wellbeing app states that it's crashed.
Force stopping System UI sadly doen't fix this, but resets the background image for some reason.
Does anyone else have this issue and/or know how to fix this? Thank you!
Otherwise it's a great ROM, btw!
Edit: I do have Xposed installed. And, using the System UI doesn't trigger any exceptions whatsover, judging the logcat. Sadly I can't provide logs for when the problem starts to occur.

Wow! I like this ROM, was my fav when i had the note 5. I hope it makes it to the official version.
Sent from my Xiaomi MI 6X using XDA Labs

##### Android 10 Beta Lineage Build #####
Xiaomi Mi 6X (wayne) Update 01-11-2019
Maintainer: @rcstar6696
Device Changelog:
• Updated Kernel to last CAF Release
• Updated Wifi Driver to last CAF Release
• Updated Qcom Configs from LA.UM.8.2.r1-04800
• Unified some Vendor Blobs
• Updated Kernel to 4.4.198
• Fixed Ui Lag after some days
• Added Snapcamera
• Updated Round Corner Configuration
• Set default Wifi country code (5Ghz for all)
• Fixed Encyrption
• Minor Improvements and Cleanup
Download Link: https://mega.nz/#!HRIjjSIb!WgFDFwuZArb3B621IW9eUvsIfsTAm8qtp4mlc7FynqQ
Recommand TWRP: https://mega.nz/#!zZBjUIQL!skoSxdQSCKMe0xwBCOcN0BIWS2jHePJYJDFaOawLehE
Only Magisk higher than 19.5 supported
Note: Don't except that everything is working smooth and perfect. All is Work in Progess and not officialy releast by Lineage. Keep that in mind.
The Build contains no Gapps. Gapps have be installed again.

rcstar6696 said:
##### Android 10 Beta Lineage Build #####
Click to expand...
Click to collapse
Is it alright if I just dirty-flash this build over the last build?

emperor8696 said:
Is it alright if I just dirty-flash this build over the last build?
Click to expand...
Click to collapse
Yup fine in case you see some crpytic words in settings use file manager to delete /data/system/package_cache

rcstar6696 said:
Yup fine in case you see some crpytic words in settings use file manager to delete /data/system/package_cache
Click to expand...
Click to collapse
I already updated and I can confirm that the ui lag issue is still there. Not only that, it seems that when the lag is at its peak the system ui will reboot by itself. Other than that, the rom is pretty much daily driver material.

emperor8696 said:
I already updated and I can confirm that the ui lag issue is still there. Not only that, it seems that when the lag is at its peak the system ui will reboot by itself. Other than that, the rom is pretty much daily driver material.
Click to expand...
Click to collapse
There is no lag issue. We verfied that on 5 tester devices and not a single problem so it must be something on your end. One think you should keep in mind its just a midrange phone not flagship and it has only a snapdragon 660. so don't except any big performance increase in future updates

Can i use this as a daily??
Sent from my Xiaomi MI 6X using XDA Labs

Why I get only 30 40 MB download and upload on Wi-Fi?

Is this version from the other post redundant? Is this rom to be used on original mi a2s as well?

##### Android 10 Beta Lineage Build #####
Xiaomi Mi 6X (wayne) Update 29-11-2019
Maintainer: @rcstar6696
Device Changelog:
• Updated Kernel to 4.4.205
• November Security Patch
• Bring inline with Xiaomi sdm660 Source (Same Base as CarbonRom)
• Minor Improvements and Cleanup
Download Link: https://mega.nz/#!uZQhhYrC!JOphxEnJTB2Rwx619CmxQY3DPI0tQ__3a9_2_uoyOIY
Recommand TWRP: https://mega.nz/#!zZBjUIQL!skoSxdQSCKMe0xwBCOcN0BIWS2jHePJYJDFaOawLehE
Only Magisk higher than 19.5 supported
Note: Don't except that everything is working smooth and perfect. All is Work in Progess and not officialy releast by Lineage. Keep that in mind.
The Build contains no Gapps. Gapps have be installed again.

Kernel WiFi Speed fix for all 10 Roms
It restores pie Wifi driver and upstreams kernel to newest Release

[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][UNOFFICIAL][10][lavender] LineageOS 17.1 with MicroG

{
"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 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working:
Everything (if it's not true - tell me)
Known issues:
Buggy longshot app (if you find better and open-source longshot app - write me)
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:
With MicroG: here
Without MicroG: here
Firmware: here. All firmwares for lavender are supported (Prefer latest Global Stable)
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 10
ROM Kernel: Linux 4.4
Based On: AOSP
Version Information
Status: Stable
Telegram links: Support chat && Channel
Created 2020-04-07
Last Updated 2021-01-25

Please move this thread to development.

great, better than Google bloat.

Update (15.04.2020)
Changelog:
Rebased on latest device tree by letsmakecakes
April security patch
Wireguard updated to version 1.0.20200413
Google Camera updated to version V4 Stay Safe (wipe data of this application if you updating from old version of this ROM)
Added RadiocellsNlpBackend
Download: SourceForge

Update (18.04.2020, noMicroG)
Changelog:
Build without MicroG
Download: SourceForge

beautiful rom..thanks a lot.
only network indicator is cut by notch, anyways thumbs up for your effort

Hello, impossible to find the partition vendor with orangefox, is it really important to wipe it?
Thanks in advance for your answer

zenat said:
Hello, impossible to find the partition vendor with orangefox, is it really important to wipe it?
Thanks in advance for your answer
Click to expand...
Click to collapse
You can try to flash ROM without wiping vendor. How I think, when you flash ROM vendor will be override automatically.

zenat said:
Hello, impossible to find the partition vendor with orangefox, is it really important to wipe it?
Thanks in advance for your answer
Click to expand...
Click to collapse
1. Which OrangeFox version are you talking about?
2. You have no reason to wipe vendor manually

ElXreno said:
You can try to flash ROM without wiping vendor. How I think, when you flash ROM vendor will be override automatically.
Click to expand...
Click to collapse
Thank you ! I will test that later
DarthJabba9 said:
1. Which OrangeFox version are you talking about?
2. You have no reason to wipe vendor manually
Click to expand...
Click to collapse
1. The latest version seems to me
2. In the installation instructions on the first post it is written: Format data, wipe system, vendor, cache, dalvik

zenat said:
1. The latest version seems to me
Click to expand...
Click to collapse
I'm afraid this statement is meaningless. Each release has a specific version number. Tell us the version number and then we will all know whether it is "the latest version".
zenat said:
2. In the installation instructions on the first post it is written: Format data, wipe system, vendor, cache, dalvik
Click to expand...
Click to collapse
1. https://wiki.orangefox.tech/en/guides
2. https://twrp.me/faq/whattowipe.html

hi, i have the latest version of orange fox and there is the wipe vendor

DarthJabba9 said:
I'm afraid this statement is meaningless. Each release has a specific version number. Tell us the version number and then we will all know whether it is "the latest version".
1. https://wiki.orangefox.tech/en/guides
2. https://twrp.me/faq/whattowipe.html
Click to expand...
Click to collapse
Actually you are right, sorry, I did have an earlier version of orangefox, I updated the latest version, the vendor partition is available now
Edit 20/04 : I just tested the rom, it runs in loop on the Lineage loading screen without ever succeeding

Update (30.04.2020, MicroG)
Changelog:
Rebased on the sdm660 common tree
Wireguard updated t oversion 1.0.20200426
Google Camera updated to version V5 (wipe data of this application if you updating from old version of this ROM)
Fixed traffic indicator (not checked)
Notes:
Kernel still by letsmakecakes (it's the best kernel FOR ME)
If you don't receive any push notifications try to enter *#*#2432546#*#* in a phone dialer. It's start background service which required for Google Cloud Messaging
Download: SourceForge

Update (02.05.2020, MicroG)
Changelog:
Fixed D2TW
Fixed LED notification
Fixed video recording
Fixed traffic indicator
Added long screenshot
Google Camera updated to fixed version V5
Wireguard updated to version 1.0.20200429
Changed kernel to common sdm660 (EAS)
Notes:
Temporary doesn't work changing of haptic strenght, flash another kernel if you need it
By default mobile data disabled when wifi enabled and connected (again)
Download: SourceForge

Update (02.05.2020, noMicroG)
Changelog:
Build without MicroG
Download: SourceForge

I use the Build (with Microg) from 15.04.2020, without any issues as my daily driver. Everything works fine. Thanks a lot for a really good and stable rom.
I wanted to update it to the newest build. The installation process worked without a problem. But it doesn't boot in the system. It brings me always to the fastboot screen. I tried it with the build (02.05.2020 and 30.04.2020). When I flash it back to the build from 15.04.2020 everything is working fine.
I am using the newest orangeFox-version, and wiped cache, dalvik.

What are the steps to update to newer version?
So I have an older build installed and want to update to the newer version.
I would like to know what steps are neccesary to update this ROM. Do I have to wipe soemthing on the recovery or do I have to just flash it without any other steps?
Also, does the changelog with MicroG apply to the one without it?
Thanks for the answer and thank you for your nice ROM.

dauerchiller said:
I use the Build (with Microg) from 15.04.2020, without any issues as my daily driver. Everything works fine. Thanks a lot for a really good and stable rom.
I wanted to update it to the newest build. The installation process worked without a problem. But it doesn't boot in the system. It brings me always to the fastboot screen. I tried it with the build (02.05.2020 and 30.04.2020). When I flash it back to the build from 15.04.2020 everything is working fine.
I am using the newest orangeFox-version, and wiped cache, dalvik.
Click to expand...
Click to collapse
Please, try to flash latest update with full wipe. Here is changed device tree, and it might be incompatible with older versions.

Manu5463 said:
So I have an older build installed and want to update to the newer version.
I would like to know what steps are neccesary to update this ROM. Do I have to wipe soemthing on the recovery or do I have to just flash it without any other steps?
Also, does the changelog with MicroG apply to the one without it?
Thanks for the answer and thank you for your nice ROM.
Click to expand...
Click to collapse
If you coming from update with date 20200415, full wipe required. Next updates you can flash without full wiping, I just recommend you clean Dalvik-Cache and Cache before update.
And yes, changelog from MicroG version also applied to the version noMicroG (excluding MicroG modules in changelog).

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

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.

Database Develop

welcome