• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[UNOFFICIAL] LineageOS 18.1 For A310, A510, and A710

Search This thread

danwood76

Recognized Developer
May 23, 2015
1,305
2,104
2okPze5.png


Introduction

LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

This is a combined thread for the A series Exynos7580 based devices.

What works
Everything
What doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.

Any issues will be ignored if you do not provide:
a) Logcat
b) /proc/last_kmsg
c) LineageOS bug report
d) dmesg

Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications

Installation

  • Install the latest TWRP for your device
  • Make a full backup (just in case something goes wrong)
  • Do a full wipe (Cache, Data, System)
  • If this is your first time on a LineageOS ROM format data, you also need to have been running your latest stock OS version
  • Flash the latest LineageOS 18.1
  • Opengapps
  • (Magisk if required)
  • Do NOT install the TWRP app if prompted, this will most likely cause a bootloop
Upgrade from official 17.1
  • Make a full backup
  • Flash in this order:
  • LineageOS-18.1
  • OpenGapps 11
  • (Magisk if required)
  • And then this migration zip available HERE
Downloads
Latest unofficial releases HERE
OpenGapps HERE
TWRP is available HERE
Magisk is available HERE

Thanks
@Stricted
@dariotr
@Androbots
The LineageOS team
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and present

If you like my work consider buying me a coffee:


Source Code: https://github.com/LineageOS

Device trees:
https://github.com/LineageOS/android_device_samsung_a3xelte
https://github.com/LineageOS/android_device_samsung_a5xelte
https://github.com/LineageOS/android_device_samsung_a7xelte
https://github.com/LineageOS/android_device_samsung_universal7580-common

Kernel: https://github.com/LineageOS/android_kernel_samsung_universal7580

ROM OS Version: Android 11
Based On: LineageOS

Version Information
Status:
Stable

Created 2020-08-20
Last Updated 2020-08-20
 
Last edited:

danwood76

Recognized Developer
May 23, 2015
1,305
2,104
Changelog:

Changes 19-10-2021:
  • Synced to latest Lineageos (October security patch)
Changes 25-09-2021:
  • Fixed SDFat bug that caused reboots when accessing sd card (thanks to Ícaro Albuquerque for testing)
Changes 21-09-2021:
  • Resysnced source (includes updated webview)
  • Fixed Wi-Fi hotspot (broken in last build)
  • Added slow/fast charging detection (indicates on lock screen)
Changes 16-09-2021:
  • Synced LineageOS sources (includes September security patch and AOSP WFD)
  • Fixed WiFi direct
  • Added further ZRAM improvements (thanks @alexax66)
Changes 28-08-2021:
  • Updated ZRAM implementation from Linux 4.1.52
  • Switched to LZ4 ZRAM compression (should be faster and better)

Changes 24-08-2021:
  • Synced latest LineageOS sources (includes new lineageos charger animation)
  • Cleaned up device overlays
  • Fixed tethering overlays
  • Disabled BPF offload for tethering (as we dont support it)
  • Added a7xelte to thread
 
Last edited:

vrobo

Senior Member
Feb 26, 2018
55
8
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?

Any major changes that break app compatibility?
 

danwood76

Recognized Developer
May 23, 2015
1,305
2,104
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?

Any major changes that break app compatibility?
Hi,

A search on XDA reveals this write up:

On top of this we have a lot of fixes for our devices from security to ram management. The list is too long, if you are interested take a look at the device trees and kernel source on GitHub.

With regards to app compatibility, Android 11 has been out for nearly a year now. If an app you use isn't compatible then to be honest it isn't worth using.

Kind regards,
Danny
 

kurtn

Senior Member
Jan 28, 2017
4,241
1,842
Small town in Bavaria
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?

Any major changes that break app compatibility?
Mail app is missing. Make sure you have your mail account details to setup a different client. I recommend FairEmail
 

kurtn

Senior Member
Jan 28, 2017
4,241
1,842
Small town in Bavaria
A3 2016 Upgrading from lineage.microg.org 17.1 to this unofficial 18.1 (no GApps) went smoother as expected. Only one error in flashing the migration zip. No problem with booting.

How are the plans for going official? That determines how to handle forks with signature spoofing.
 

setecastronomy

New member
Jul 29, 2021
4
2
Thanks for the build! I tried compiling on my own a week ago but it failed at the kernel.

So far the experimental 18.1 release works "okay". The system performance is slightly better compared to 17.1. It's still not great but I guess this is the best one can expect from an underpowered phone. At least the responsiveness of the inputs has improved, e.g. keyboard is not totally locked while swapping right after start of Maps. And the swap usage in "top" is not jumping crazy between 300-900mb like before, now about 250mb after startup (previously: ~500mb) and remains at around 500mb after a while.

Also, could you please cherry-pick https://review.lineageos.org/c/LineageOS/android_system_vold/+/258169 ? My MicroSD is reported as Unsupported, I saw that mentioned somewhere in the search results of 17.1 thread. I also have an ext4 filesystem there and would like to continue without converting it to exfat.

No glitches found yet apart from the mentioned SD issue. The update from 17.1 went almost smoothly. There was a scary message in TWRP output (something like "mount: command not found") in the teardown process, but it was eventually reported as success.

Edit:

the recommended Magisk source is https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/ ? I used that one since it wasn't linked in the top post here. Sadly, its documentation now declares the simple just-sideload-the-apk-file method deprecated but it worked for me just fine.
 

mihancad

Member
Dec 6, 2016
18
5
31
tehran
www.pasargadsuperior.ir
2okPze5.png


Introduction

LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

This is a combined thread for the A series Exynos7580 based devices.

What works
Everything
What doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.

Any issues will be ignored if you do not provide:
a) Logcat
b) /proc/last_kmsg
c) LineageOS bug report
d) dmesg

Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications

Installation

  • Install the latest TWRP for your device
  • Make a full backup (just in case something goes wrong)
  • Do a full wipe (Cache, Data, System)
  • If this is your first time on a LineageOS ROM format data, you also need to have been running your latest stock OS version
  • Flash the latest LineageOS 18.1
  • Opengapps
  • (Magisk if required)
  • Do NOT install the TWRP app if prompted, this will most likely cause a bootloop
Upgrade from official 17.1
  • Make a full backup
  • Flash in this order:
  • LineageOS-18.1
  • OpenGapps 11
  • (Magisk if required)
  • And then this migration zip available HERE
Downloads
Latest unofficial releases HERE
OpenGapps HERE
TWRP is available HERE
Magisk is available HERE

Thanks
@Stricted
@dariotr
The LineageOS team
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and present

If you like my work consider buying me a coffee:


Source Code: https://github.com/LineageOS

Device trees:
https://github.com/LineageOS/android_device_samsung_a3xelte
https://github.com/LineageOS/android_device_samsung_a5xelte
https://github.com/LineageOS/android_device_samsung_universal7580-common

Kernel: https://github.com/LineageOS/android_kernel_samsung_universal7580

ROM OS Version: Android 11
Based On: LineageOS

Version Information
Status:
Stable

Created 2020-08-20
Last Updated 2020-08-20
Hi
Why was it not Build for (a7xelte) A710 2016? :(
 
Last edited:

danwood76

Recognized Developer
May 23, 2015
1,305
2,104
Thanks for the build! I tried compiling on my own a week ago but it failed at the kernel.

So far the experimental 18.1 release works "okay". The system performance is slightly better compared to 17.1. It's still not great but I guess this is the best one can expect from an underpowered phone. At least the responsiveness of the inputs has improved, e.g. keyboard is not totally locked while swapping right after start of Maps. And the swap usage in "top" is not jumping crazy between 300-900mb like before, now about 250mb after startup (previously: ~500mb) and remains at around 500mb after a while.

Also, could you please cherry-pick https://review.lineageos.org/c/LineageOS/android_system_vold/+/258169 ? My MicroSD is reported as Unsupported, I saw that mentioned somewhere in the search results of 17.1 thread. I also have an ext4 filesystem there and would like to continue without converting it to exfat.

No glitches found yet apart from the mentioned SD issue. The update from 17.1 went almost smoothly. There was a scary message in TWRP output (something like "mount: command not found") in the teardown process, but it was eventually reported as success.

Edit:

the recommended Magisk source is https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/ ? I used that one since it wasn't linked in the top post here. Sadly, its documentation now declares the simple just-sideload-the-apk-file method deprecated but it worked for me just fine.
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card. You are much better off switching to exfat. The patch you linked will not be added to LineageOS 18.1.
Hi
Why was it not Build for (a7xelte) A710 2016? :(
I will add the a7 on Tuesday, although I am not the maintainer of that device.
A3 2016 Upgrading from lineage.microg.org 17.1 to this unofficial 18.1 (no GApps) went smoother as expected. Only one error in flashing the migration zip. No problem with booting.

How are the plans for going official? That determines how to handle forks with signature spoofing.
The error on the migration zip is actually because of a difference between TWRP and lineage recovery, ignore it.

Official status is going to happen, just need some thorough testing and I haven't had the time to start a thread (until now).

Kind regards,
Danny
 

setecastronomy

New member
Jul 29, 2021
4
2
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card.
So they told me but I beg to disagree. The card is almost 6yo, no IO errors found yet, reading/writing speed maxes out the USB2.0 speed. It's good Samsung PRO. Its predecessor (some AData model) was almost trashed within two years (almost means: no IO errors but so slow in certain regions that it's not fun to use anymore).

And the reason for using ext4 is the storage API madness which has hit Google devs with Android 6.0 or so, using this (for permission management) and a specific user as filesystem owner made the life a lot easier.

You are much better off switching to exfat.
And so I tried. tar everything, mkfs to exfat, untar. Results: tried to configure the card as "portable storage" and it worked Kind of. Navi app fails to use it's data folder there, music app (MortPlayer) finds to find the media data there. File manager can browse through the files, though.

When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.

Tried to investigate what happened, and cannot see much, only this:

08-23 19:43:03.737 2275 2275 D vold : exfatprogs version : 1.1.2 08-23 19:43:03.738 2275 2275 D vold : ERROR: /Android/data/net.osmand.plus/files/rendering/default.render.xml: first cluster is wrong. Truncate (y/N)? n 08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: checking stopped. directories 1256, files 12597 08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: files corrupted 1, files fixed 0
then some other stuff and after few minutes this:
08-23 19:55:04.231 2479 2494 D installd: Device /data has 129531904 free; requested 1048576000; needed 919044096 08-23 19:55:04.633 2479 2494 D installd: Refusing to clear cached data in reserved space 08-23 19:55:04.634 2479 2494 E installd: Failed to free up 1048576000 on /data; final free space 129531904: Success 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: java.io.IOException: Failed to free 1048576000 on storage device at /data 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.pm.PackageManagerService.freeStorage(PackageManagerService.java:5200) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.check(DeviceStorageMonitorService.java:193) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.access$100(DeviceStorageMonitorService.java:72) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService$1.handleMessage(DeviceStorageMonitorService.java:257) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Handler.dispatchMessage(Handler.java:106) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Looper.loop(Looper.java:223) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.HandlerThread.run(HandlerThread.java:67) --------- beginning of kernel
(and the boot sequence, apparently)

After the reboot, there is the "card setup" wizard coming back, asking again "portable storage" or "internal". Selecting "portable" tells that the card needs to be formatted. WAT? How did it work the first time? I went to the shell, and I can mount the block device just fine and read random files from there.

So now, I am at the brink of formatting it as "internal storage" to have my peace again. Google managed to kill this Android feature, it took a while but they got me.
 

danwood76

Recognized Developer
May 23, 2015
1,305
2,104
So they told me but I beg to disagree. The card is almost 6yo, no IO errors found yet, reading/writing speed maxes out the USB2.0 speed. It's good Samsung PRO. Its predecessor (some AData model) was almost trashed within two years (almost means: no IO errors but so slow in certain regions that it's not fun to use anymore).

And the reason for using ext4 is the storage API madness which has hit Google devs with Android 6.0 or so, using this (for permission management) and a specific user as filesystem owner made the life a lot easier.


And so I tried. tar everything, mkfs to exfat, untar. Results: tried to configure the card as "portable storage" and it worked Kind of. Navi app fails to use it's data folder there, music app (MortPlayer) finds to find the media data there. File manager can browse through the files, though.

When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.

Tried to investigate what happened, and cannot see much, only this:

08-23 19:43:03.737 2275 2275 D vold : exfatprogs version : 1.1.2 08-23 19:43:03.738 2275 2275 D vold : ERROR: /Android/data/net.osmand.plus/files/rendering/default.render.xml: first cluster is wrong. Truncate (y/N)? n 08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: checking stopped. directories 1256, files 12597 08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: files corrupted 1, files fixed 0
then some other stuff and after few minutes this:
08-23 19:55:04.231 2479 2494 D installd: Device /data has 129531904 free; requested 1048576000; needed 919044096 08-23 19:55:04.633 2479 2494 D installd: Refusing to clear cached data in reserved space 08-23 19:55:04.634 2479 2494 E installd: Failed to free up 1048576000 on /data; final free space 129531904: Success 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: java.io.IOException: Failed to free 1048576000 on storage device at /data 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.pm.PackageManagerService.freeStorage(PackageManagerService.java:5200) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.check(DeviceStorageMonitorService.java:193) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.access$100(DeviceStorageMonitorService.java:72) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService$1.handleMessage(DeviceStorageMonitorService.java:257) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Handler.dispatchMessage(Handler.java:106) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Looper.loop(Looper.java:223) 08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.HandlerThread.run(HandlerThread.java:67) --------- beginning of kernel
(and the boot sequence, apparently)

After the reboot, there is the "card setup" wizard coming back, asking again "portable storage" or "internal". Selecting "portable" tells that the card needs to be formatted. WAT? How did it work the first time? I went to the shell, and I can mount the block device just fine and read random files from there.

So now, I am at the brink of formatting it as "internal storage" to have my peace again. Google managed to kill this Android feature, it took a while but they got me.
Try formatting the card from the phone. I have had issues formatting using Linux and Windows before, even for my stock S9.

Kind regards,
Danny
 

mihancad

Member
Dec 6, 2016
18
5
31
tehran
www.pasargadsuperior.ir
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card. You are much better off switching to exfat. The patch you linked will not be added to LineageOS 18.1.

I will add the a7 on Tuesday, although I am not the maintainer of that device.

The error on the migration zip is actually because of a difference between TWRP and lineage recovery, ignore it.

Official status is going to happen, just need some thorough testing and I haven't had the time to start a thread (until now).

Kind regards,
Danny
Will it be ready for download for A7 (a7xelte) today?
 

danwood76

Recognized Developer
May 23, 2015
1,305
2,104
When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.

Tried to investigate what happened, and cannot see much, only this:
I have just done this on my test A5 and everything worked perfectly, I downloaded 300MB of maps of my region and it all works well. There was a permissions pop up when I first opened the app which i accepted.

The card is my old Samsung 64GB, I wiped the card in my desktop and then allowed the phone to format it, I think Windows/Linux sets some exFAT options that android doesn't like so it is best to let the phone do it.

Kind regards,
Danny
 
  • Like
Reactions: mihancad

danwood76

Recognized Developer
May 23, 2015
1,305
2,104
I have just uploaded a small update and added the a7xelte build.

Changes 24-08-2021:
  • Synced latest LineageOS sources (includes new lineageos charger animation)
  • Cleaned up device overlays
  • Fixed tethering overlays
  • Disabled BPF offload for tethering (as we dont support it)
  • Added a7xelte to thread
Kind regards,
Danny
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Arm (not 64) Pico, Android 11
    I've noticed that Nano is better for battery performance, for some reason the missing "Device Health Services" from Pico makes the battery drains faster.
    1
    you can try google cam go (its basically a diet google cam) i dont know if it has hdr but at least it can support 32bit devices unlike the normal gcam that supports only arm64 plus the gcam go app quite up to date.

    Give it a shot as i managed to download and install an apk while having a 32bit device but have not used it yet.


    Our devices don't have the necessary hardware to support Google cam. OpenCamera or snap (default LineageOS camera) are probably best for the moment.

    There is talk of switching away from snap because it is an old code base and has a few issues.

    Regards,
    Danny
    Thank you for the suggestions. I tried all of them and opencam seems to work the best for me.
    1
    I seem to have ran into a unique problem though. I was flashing a bunch of things and triggered FRP of the phone. I unlocked it by going back to stock ROM (as it was blocking any custom binary) but now If I want to install Lineage or even TWRP for that matter, I've to make sure that I don't have a google account when the phone restarts as it triggers FRP as soon as my device have any custom binary with a google account on my device(or if I add a google account after flashing it), this means I have to either not use any google services or have to remove google account before even rebooting the phone with anything else than official stock firmware.

    I tried a bunch of solution and searched all over the internet, tried a bunch of remove FRP modules but nothing seem to work. And the thing I hate the most is FRP doesn't even add any layer of security as I can bypass it for logging into the device once I go back to stock rom.

    If anyone have any better solution please tell me.
    1
    To remove frp you need to be on stock ROM and sign out of every account on the phone (mostly google accounts)
    Just sign out and even sign out of ur Samsung account then just flash twrp thru Odin then boot in twrp and flash lineage.
    This is the solution to your problem. Just log out of your Google accounts in stock and you won't have issues.

    You should be able to unlock the phone with a valid Google account in the setup wizard though.

    Regards,
    Danny
  • 17
    2okPze5.png


    Introduction

    LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    This is a combined thread for the A series Exynos7580 based devices.

    What works
    Everything
    What doesn't work
    IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.

    Any issues will be ignored if you do not provide:
    a) Logcat
    b) /proc/last_kmsg
    c) LineageOS bug report
    d) dmesg

    Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications

    Installation

    • Install the latest TWRP for your device
    • Make a full backup (just in case something goes wrong)
    • Do a full wipe (Cache, Data, System)
    • If this is your first time on a LineageOS ROM format data, you also need to have been running your latest stock OS version
    • Flash the latest LineageOS 18.1
    • Opengapps
    • (Magisk if required)
    • Do NOT install the TWRP app if prompted, this will most likely cause a bootloop
    Upgrade from official 17.1
    • Make a full backup
    • Flash in this order:
    • LineageOS-18.1
    • OpenGapps 11
    • (Magisk if required)
    • And then this migration zip available HERE
    Downloads
    Latest unofficial releases HERE
    OpenGapps HERE
    TWRP is available HERE
    Magisk is available HERE

    Thanks
    @Stricted
    @dariotr
    @Androbots
    The LineageOS team
    All the testers on the Discord group (https://discord.gg/8fp9cr7)
    And all others who have contributed to the Exynos projects past and present

    If you like my work consider buying me a coffee:


    Source Code: https://github.com/LineageOS

    Device trees:
    https://github.com/LineageOS/android_device_samsung_a3xelte
    https://github.com/LineageOS/android_device_samsung_a5xelte
    https://github.com/LineageOS/android_device_samsung_a7xelte
    https://github.com/LineageOS/android_device_samsung_universal7580-common

    Kernel: https://github.com/LineageOS/android_kernel_samsung_universal7580

    ROM OS Version: Android 11
    Based On: LineageOS

    Version Information
    Status:
    Stable

    Created 2020-08-20
    Last Updated 2020-08-20
    9
    Just uploaded a new update.

    Main changes 21-09-2021:
    • Resysnced source (includes updated webview)
    • Fixed Wi-Fi hotspot (broken in last build)
    • Added slow/fast charging detection (indicates on lock screen)
    Kind regards,
    Danny
    8
    Just uploaded a new update.

    This should fix your download issue @sajad-tnt , @yarikibeast

    Main changes 25-09-2021:

    • Fixed SDFat bug that caused reboots when accessing sd card (thanks to Ícaro Albuquerque for testing)

    Kind regards,
    Danny
    7
    Another small update, should give more stable and better ZRAM cokmpression:

    Changes 28-08-2021:
    • Updated ZRAM implementation from Linux 4.1.52
    • Switched to LZ4 ZRAM compression (should be faster and better)
    Kind regards,
    Danny
    6
    Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?

    Any major changes that break app compatibility?
    Hi,

    A search on XDA reveals this write up:

    On top of this we have a lot of fixes for our devices from security to ram management. The list is too long, if you are interested take a look at the device trees and kernel source on GitHub.

    With regards to app compatibility, Android 11 has been out for nearly a year now. If an app you use isn't compatible then to be honest it isn't worth using.

    Kind regards,
    Danny