• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

LineageOS 18.1 for SM-T580 (gtaxlwifi)

Search This thread

Pat33170

Member
Mar 19, 2021
10
0
We're currently using a build fingerprint for the Google Pixel C. It would appear that app is no longer marked as compatible with the Pixel C. It shouldn't say that it's incompatible if you change the build fingerprint to one from another device on which that app is marked as compatible. There's a magisk module called "MagiskHide Props Config" which allows for changing the build fingerprint. You can also edit /system/build.prop, although changes will be removed every time you update to a new build.

I don't have another better build fingerprint with which safetynet will pass without changing the security patch level date, so I can't change the default fingerprint. I could get the latest fingerprints from devices with the latest security patch level, but keeping up would be a massive pain.

You're welcome. Of course. I release a new build more or less every month.
 

Echo_2000

Senior Member
Dec 1, 2015
53
8
Hi @TALUAtXDA and thanks for keeping this device alive.
I saw that you mention in OP that sooner or later a version for the LTE variant will come. I just wanna ask if this version will come anytime soon or if I should just flash the current build in the meantime.
 

TALUAtXDA

Senior Member
Nov 8, 2018
347
573
Hi @TALUAtXDA and thanks for keeping this device alive.
I saw that you mention in OP that sooner or later a version for the LTE variant will come. I just wanna ask if this version will come anytime soon or if I should just flash the current build in the meantime.
You're welcome. I'm planning to attempt to setup sources and build for the LTE variant in around more or less 1-2 months.

I think you should be able to install a build for the LTE variant over an installation originally from a build for the WiFi-only variant for whenever I have one ready, and with that, you can install my current build for the WiFi-only variant if you want to in the meantime, and you wouldn't need to start fresh whenever you install a build for the LTE variant.

Do note that I'm going to release a new build in a few hours from now, so I suggest waiting until then.
 
Last edited:

Echo_2000

Senior Member
Dec 1, 2015
53
8
You're welcome. I'm planning to attempt to setup sources and build for the LTE variant in around more or less 1-2 months.

I think you should be able to install a build for the LTE variant over an installation originally from a build for the WiFi-only variant for whenever I have one ready, and with that, you can install my current build for the WiFi-only variant if you want to in the meantime, and you wouldn't need to start fresh whenever you install a build for the LTE variant.

Do note that I'm going to release a new build in a few hours from now, so I suggest waiting until then.
Thanks for your replay. I will wait for the new build to enjoy Android 11.
 
We're currently using a build fingerprint for the Google Pixel C. It would appear that app is no longer marked as compatible with the Pixel C. It shouldn't say that it's incompatible if you change the build fingerprint to one from another device on which that app is marked as compatible. There's a magisk module called "MagiskHide Props Config" which allows for changing the build fingerprint. You can also edit /system/build.prop, although changes will be removed every time you update to a new build.

I don't have another better build fingerprint with which safetynet will pass without changing the security patch level date, so I can't change the default fingerprint. I could get the latest fingerprints from devices with the latest security patch level, but keeping up would be a massive pain.

Oh, that's really interesting info. I never thought you had to select one existing model to bypass the ROM, or however it works.

So... basically, to Google Play Store, we have a Google Pixel C tablet, and it will show everything that would be shown in a Pixel C, correct?
 

dskiller

Member
Oct 12, 2012
48
4
Orlando
Great rom but have problem with app called video downloader from inshot when used along with other webbrowers causes major system lag causing firefox and chrome to stop responding. Could be memory related as dev tools reports zero free memory when it happens
 

TALUAtXDA

Senior Member
Nov 8, 2018
347
573
New release for 20210617

Download:

Changelog:
  • Latest updates from LineageOS, including the 20210605 Android security updates.
  • The WiFi and Bluetooth firmwares have been updated from Samsung's A720SKSU5CTL2 firmware.
  • The qcom_cfg.ini configuration file for WiFi has been imported from Samsung's A720SKSU5CTL2 firmware - A change within it appears to have made WiFi more reliable.
  • The sensors.universal7870.so library has been updated from Samsung's stock P580ZSS1CTI1 firmware.
  • The health HAL has been upgraded to version 2.1.
  • There are a few other small miscellaneous changes (mostly small cleanups).
  • There are many updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
  • Some unnecessary drivers have been disabled in the kernel.
  • The sdfat driver in the kernel, which is used for exFAT filesystem support, has been updated to version 2.4.5.
  • A few changes have been imported to the MMC block device driver in the kernel from Samsung's M105GDXS6CUD4 kernel that fix extremely rare kernel panics that occurred when there was an error with a MMC device (mainly with SD cards).
  • The fix for an issue where the duration of videos that are taken is lengthened by the time spent in deep sleep/suspended that was previously used has been replaced with a better fix in the Exynos fimc-is2 driver in the kernel.
As usual, enjoy.
 
Last edited:

Archaide

New member
Jun 18, 2021
2
1
Thank you very much for the effort to bring the latest android to this old device. Much appreciated. I've only registered to say this.

Btw: just flashed over the last rom. no wiping no nothing. Same thing for the last 2 roms. Works flawlessly everytime so far. Great job.
 

Demonpanda8

New member
Nov 4, 2020
1
0
small problem, how do i unpin apps?

i clicked the app logo from overview and it said that i need to press back button and home button and it isnt working. will i have to wipe everything and install the rom again?
 

Raggamuffin86

New member
Oct 17, 2018
2
1
Hey TALUAtXDA,

A couple of days ago I installed your Lineage OS 18.1 on my tablet. So far everything works just fine .....

....However I do have a question:

Ever since I set up my device with my Google account .... My Google account lists a new device that has logged into it: "Google Pixel C"

.... I don't own such a device ....

... To me it only makes sense that instead of "Galaxy Tab A (2016)" Google registered my tablet as "Google Pixel C" .... or worst case scenario, my account got hacked and it has nothing to do with the install of your ROM ...


Please note I'm a complete layman / idiot concerning everything you guys on here seem to be experts in. I just wanted to update my tablet and with the help of a YouTube tutorial I was lucky enough to be successful, despite having no idea about what I was doing ;) ... So, if it's okay could you respond to my question like you were talking to 3rd grader ? ;)

Cheers
Ragamuffin
 
Last edited:
  • Like
Reactions: rambomhtri
Hey TALUAtXDA,

A couple of days ago I installed your Lineage OS 18.1 on my tablet. So far everything works just fine .....

....However I do have a question:

Ever since I set up my device with my Google account .... My Google account lists a new device that has logged into my account: "Google Pixel C"
.... I don't own such a device ....

Please note I'm a complete layman / idiot concerning everything you guys on here seem to be experts in. I just wanted to update my tablet and with the help of a YouTube tutorial I was lucky enough to be successful, despite having no idea about what I was doing ;) ... So, if it's okay could you respond to my question like you were talking to 3rd grader ? ;)

Cheers
Ragamuffin
Yeah, it's simple, although this answer is not 100% correct, but gives you an idea: when you flash a custom, not original, not stock ROM, sometimes the name Google recognizes and alerts you is the name the device (in this case Pixel C tablet) this custom ROM is based on. So, AFAIK, the developer of this LOS 18.1 ROM took as a base/start the Pixel C ROM or structure or scheme, and adapted it to the Samsung Tab A6. That's why Google will recognize this tablet as Pixel C.
 
Last edited:
  • Like
Reactions: Raggamuffin86

TALUAtXDA

Senior Member
Nov 8, 2018
347
573
Hey TALUAtXDA,

A couple of days ago I installed your Lineage OS 18.1 on my tablet. So far everything works just fine .....

....However I do have a question:

Ever since I set up my device with my Google account .... My Google account lists a new device that has logged into it: "Google Pixel C"

.... I don't own such a device ....

... To me it only makes sense that instead of "Galaxy Tab A (2016)" Google registered my tablet as "Google Pixel C" .... or worst case scenario, my account got hacked and it has nothing to do with the install of your ROM ...


Please note I'm a complete layman / idiot concerning everything you guys on here seem to be experts in. I just wanted to update my tablet and with the help of a YouTube tutorial I was lucky enough to be successful, despite having no idea about what I was doing ;) ... So, if it's okay could you respond to my question like you were talking to 3rd grader ? ;)

Cheers
Ragamuffin
Alright, here goes. Something called the "build fingerprint" is set to an old one for the Google Pixel C tablet. This is so that we can bypass a check put in place by Google, called "safetynet", used by apps to tell if any system-level modifications have been made. "Safetynet" will pass with this fingerprint provided some other conditions are met. The build fingerprint is used to identify which device you have. As a result of this, your device will be shown as a Pixel C.
 
Last edited:
  • Like
Reactions: Raggamuffin86

Raggamuffin86

New member
Oct 17, 2018
2
1
Yeah, it's simple: when you flash a custom, not original, not stock ROM, sometimes the name Google recognizes and alerts you is the name the device (in this case Pixel C tablet) this custom ROM is based on. So, AFAIK, the developer of this LOS 18.1 ROM took as a base/start the Pixel C ROM or structure or scheme, and adapted it to the Samsung Tab A6. That's why Google will recognize this tablet as Pixel C.
Great! Thank you for the quick response. So nothing to worry about ...what a relief! Thanks!
 
By the way, that reply is technically not right. Look at my reply for the correct answer. We don't take anything from the Pixel C, except an older build fingerprint from an older version of its firmware.
I knew I wasn't right, I've edited my message warning it's not 100% correct. Thank you.

By the way... why not all ROM's that don't pass safetynet put PIXEL C in the fingerprint?
Although... I guess it's more complex than typing pixel C in the system file...
 
You're welcome. I'm planning to attempt to setup sources and build for the LTE variant in around more or less 1-2 months.

I think you should be able to install a build for the LTE variant over an installation originally from a build for the WiFi-only variant for whenever I have one ready, and with that, you can install my current build for the WiFi-only variant if you want to in the meantime, and you wouldn't need to start fresh whenever you install a build for the LTE variant.

Do note that I'm going to release a new build in a few hours from now, so I suggest waiting until then.
Hi, I have bought recently the LTE variant to be able to use WhatsApp. I've been using the original Samsung stock ROM and it was way worse than LOS 18.1, as I expected. Didn't like it at all. So...

I understand that until you release LOS 18.1 for the LTE variant, with this ROM version for the WiFi variant I won't be able to put the SIM card and be able to set up WhatsApp, right?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    New release for 20210709

    Download:
    https://drive.google.com/file/d/1ej8JYTZzcdQzwHtJHiBFwVC-rm5ytBq1/

    Changelog:
    • Latest updates from LineageOS.
    • Merges of the latest changes from AOSP for repositories forked by Lineage have been picked to skip the wait for them to be merged (repopick -t android-11.0.0_r39), and the rest of the repositories not forked by Lineage were additionally switched to the android-11.0.0_r39 tag, for the 20210705 Android security updates.
    • A patch to the PermissionController app has been applied that adds the FAKE_PACKAGE_SIGNATURE permission group to it - The signature spoofing permission can now be managed through the permission management interface at Settings -> Privacy -> Permission manager.
    • The audio outputted from the audio jack while playing media will now be noticeably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • A few patches have been applied to the qcacld-2.0 WiFi driver in the kernel, which are mainly vulnerability fixes.
    Enjoy.
    3
    Been using lineage 18.1 since it first became available and have updated it every month give or take since.

    There is not a more stable rom for this device and I for one fkin love :cool: it!!!

    Excellent work @TALUAtXDA

    We really appreciate your work and time dedicated to this amazing tablet..
    1
    Hi everyone!
    just installed this rom, connected the device to the computer, the device was recognized but appeared empty, what can I do for the storage to be accessible from the PC like before?
    There should be a notification saying:
    "Charging this device via USB
    Tap for more options."
    ...while your device is connected. Tap on it and select "File transfer".
    1
    New release for 20210709

    Download:
    https://drive.google.com/file/d/1ej8JYTZzcdQzwHtJHiBFwVC-rm5ytBq1/

    Changelog:
    • Latest updates from LineageOS.
    • Merges of the latest changes from AOSP for repositories forked by Lineage have been picked to skip the wait for them to be merged (repopick -t android-11.0.0_r39), and the rest of the repositories not forked by Lineage were additionally switched to the android-11.0.0_r39 tag, for the 20210705 Android security updates.
    • A patch to the PermissionController app has been applied that adds the FAKE_PACKAGE_SIGNATURE permission group to it - The signature spoofing permission can now be managed through the permission management interface at Settings -> Privacy -> Permission manager.
    • The audio outputted from the audio jack while playing media will now be noticably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • A few patches have been applied to the qcacld-2.0 WiFi driver in the kernel, which are mainly vulnerability fixes.
    Enjoy.
    Updated just now. Works pretty fine :).
    1
    Thnx alot. As always smooth sailing. Download, boot into twrp, flashing, reboot, done.
    The volume is much louder now.
    Really good job.
  • 24
    This is LineageOS 18.1, which is based on Android 11, for the WiFi-only variant of the Samsung Galaxy Tab A 10.1" (2016), codenamed gtaxlwifi. LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android distribution.

    As was always planned, my LineageOS 18.1 builds are a continuation from @followmsi's builds that were intended for use by users. To update from his builds, my builds can simply be installed on top of his builds without doing anything further.

    Downloads:
    Note: These builds are intended to be used on the WiFi-only variant of this device, however, they can be installed and used on the LTE variant if you can go without mobile networking (of course), GPS and vibration. I'm planning to try to make builds for the LTE variant sometime in the future when I have time to setup sources for it.

    Latest build from 20210709 (security patch level 20210705): https://drive.google.com/file/d/1ej8JYTZzcdQzwHtJHiBFwVC-rm5ytBq1/
    Some previous releases: https://drive.google.com/drive/folders/1PmxsmmtNo7NwqMpBYKZ9b-sBs5-m9QRG
    Folder for these builds (includes text files with MD5 and SHA256 checksums for builds): https://drive.google.com/drive/folders/1wuirD9cyoguv7CQdEO5ymZ911k2ASKKD

    Changelogs:
    Release for 20210709:
    • Latest updates from LineageOS.
    • Merges of the latest changes from AOSP for repositories forked by Lineage have been picked to skip the wait for them to be merged (repopick -t android-11.0.0_r39), and the rest of the repositories not forked by Lineage were additionally switched to the android-11.0.0_r39 tag, for the 20210705 Android security updates.
    • A patch to the PermissionController app has been applied that adds the FAKE_PACKAGE_SIGNATURE permission group to it - The signature spoofing permission can now be managed through the permission management interface at Settings -> Privacy -> Permission manager.
    • The audio outputted from the audio jack while playing media will now be noticeably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • A few patches have been applied to the qcacld-2.0 WiFi driver in the kernel, which are mainly vulnerability fixes.
    Previous releases:

    Release for 20210617:
    • Latest updates from LineageOS, including the 20210605 Android security updates.
    • The WiFi and Bluetooth firmwares have been updated from Samsung's A720SKSU5CTL2 firmware.
    • The qcom_cfg.ini configuration file for WiFi has been imported from Samsung's A720SKSU5CTL2 firmware - A change within it appears to have made WiFi more reliable.
    • The sensors.universal7870.so library has been updated from Samsung's stock P580ZSS1CTI1 firmware.
    • The health HAL has been upgraded to version 2.1.
    • There are a few other small miscellaneous changes (mostly small cleanups).
    • There are many updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • Some unnecessary drivers have been disabled in the kernel.
    • The sdfat driver in the kernel, which is used for exFAT filesystem support, has been updated to version 2.4.5.
    • A few changes have been imported to the MMC block device driver in the kernel from Samsung's M105GDXS6CUD4 kernel that fix extremely rare kernel panics that occurred when there was an error with a MMC device (mainly with SD cards).
    • The fix for an issue where the duration of videos that are taken is lengthened by the time spent in deep sleep/suspended that was previously used has been replaced with a better fix in the Exynos fimc-is2 driver in the kernel.
    Release for 20210508:
    • Latest updates from LineageOS, including the 20210505 Android security updates.
    • New SELinux denials with Android 11 have been addressed, and with that, SELinux is now set to enforcing by default, and the sepolicy, which contains the SELinux rules, has been rewritten almost entirely, and is now of much better quality.
    • Some changes have been imported to libbt-vendor from https://github.com/LineageOS/android_hardware_qcom_bt on branch lineage-18.1-caf.
    • BPF offloading for tethering has been disabled.
    • The audio HAL has been upgraded to version 6.0.
    • The rampatch_tlv_tf_1.1.tlv firmware for Bluetooth has been updated from Samsung's stock T585XXS6CTJ7 firmware.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • Some tcp_info-related patches have been applied to the kernel, and with that, a workaround, a patch titled "TcpSocketTracker: Opt-out for TCP info parsing on legacy kernels", is no longer used since it's no longer necessary.
    • A workaround that was used to get USB tethering and Bluetooth tethering to work is no longer used, and has been replaced with a proper fix (enabling CONFIG_NETFILTER_XT_TARGET_CT in the kernel).
    Release for 20210407 (My initial 18.1 build. This changelog continues on from @followmsi's last 18.1 build that was intended for use by users):
    • Latest changes from LineageOS. The crashes that occurred when setting a new wallpaper that were discussed earlier in this thread appear to have been fixed.
    • Merges of the latest changes from AOSP, including the 20210405 security updates, have been picked to skip the wait for them to be merged. (repopick -t android-11.0.0_r34)
    • The same workaround that was used on 17.1 to get USB tethering and Bluetooth internet access sharing to work has been forward-ported and applied.
    • vintf manifest override enforcement is now enabled.
    • The vendor/lib[64]/egl/libGLES_mali.so blobs are now symlinked to vendor/lib[64]/vulkan.exynos5.so, rather than copied to vendor/lib[64]/hw/vulkan.exynos5.so - This is a proper fix for Vulkan support.
    • RSA key verification for ADB is enabled again, and ADB isn't enabled by default and on boot anymore.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.



    Known issues and workarounds (if any):
    Issue 1: Occasionally, when trying to select tiles in the notification panel, it will crash to the lockscreen.
    I have no idea about this issue at the moment. It seems like generic systemui crashes. Todo: test LineageOS 18.1 on another device to see if the same issues occur.

    Issue 2: Images and videos that are taken in a resolution with an aspect ratio of 16:9 are actually stretched from 4:3.
    Somewhat of a workaround to issue 2: Use a resolution that has an aspect ratio of 4:3.

    Issue 3: the on-screen navigation bar feature that can be enabled with the option at Settings -> System -> Buttons -> "Enable on-screen nav bar" doesn't work properly.

    Issue 4: If the WiFi hotspot is enabled without first enabling and disabling WiFi, it will not work.
    Workaround to issue 4: Simply enable and disable WiFi before enabling the WiFi hotspot.

    To report further issues, get a log from logcat and dmesg. If you are unsure on how to get either, there is good documentation out there for how to do so.


    Sources:
    manifests - https://github.com/TALUAtGitHub/gtaxlwifi-manifests
    device tree - https://github.com/TALUAtGitHub/android_device_samsung_gtaxlwifi
    kernel sources - https://github.com/TALUAtGitHub/android_kernel_samsung_exynos7870
    vendor tree - https://github.com/TALUAtGitHub/android_vendor_samsung_gtaxlwifi
    hardware - https://github.com/LineageOS/android_hardware_samsung
    android_frameworks_base fork - https://github.com/TALUAtGitHub/android_frameworks_base
    android_frameworks_av fork - https://github.com/TALUAtGitHub/android_frameworks_base
    android_system_core fork - https://github.com/TALUAtGitHub/android_system_core
    BSP sources - The BSP sources consist of 3 parts in these 3 repositories:
    ...all on branches lineage-18.1

    Thanks to:
    @Valera1978 - for all of the previous work for these devices, and for providing his old BSP sources without which the open BSP sources wouldn't have been possible.
    @followmsi - for fixes to various issues and other improvements, for useful information, and for working with me on much of this stuff.
    LineageOS - for the Android distribution itself.
    ...and everyone else who has worked on anything that is in use.
    12
    New release for 20210617

    Download:

    Changelog:
    • Latest updates from LineageOS, including the 20210605 Android security updates.
    • The WiFi and Bluetooth firmwares have been updated from Samsung's A720SKSU5CTL2 firmware.
    • The qcom_cfg.ini configuration file for WiFi has been imported from Samsung's A720SKSU5CTL2 firmware - A change within it appears to have made WiFi more reliable.
    • The sensors.universal7870.so library has been updated from Samsung's stock P580ZSS1CTI1 firmware.
    • The health HAL has been upgraded to version 2.1.
    • There are a few other small miscellaneous changes (mostly small cleanups).
    • There are many updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • Some unnecessary drivers have been disabled in the kernel.
    • The sdfat driver in the kernel, which is used for exFAT filesystem support, has been updated to version 2.4.5.
    • A few changes have been imported to the MMC block device driver in the kernel from Samsung's M105GDXS6CUD4 kernel that fix extremely rare kernel panics that occurred when there was an error with a MMC device (mainly with SD cards).
    • The fix for an issue where the duration of videos that are taken is lengthened by the time spent in deep sleep/suspended that was previously used has been replaced with a better fix in the Exynos fimc-is2 driver in the kernel.
    As usual, enjoy.
    10
    New release for 20210709

    Download:
    https://drive.google.com/file/d/1ej8JYTZzcdQzwHtJHiBFwVC-rm5ytBq1/

    Changelog:
    • Latest updates from LineageOS.
    • Merges of the latest changes from AOSP for repositories forked by Lineage have been picked to skip the wait for them to be merged (repopick -t android-11.0.0_r39), and the rest of the repositories not forked by Lineage were additionally switched to the android-11.0.0_r39 tag, for the 20210705 Android security updates.
    • A patch to the PermissionController app has been applied that adds the FAKE_PACKAGE_SIGNATURE permission group to it - The signature spoofing permission can now be managed through the permission management interface at Settings -> Privacy -> Permission manager.
    • The audio outputted from the audio jack while playing media will now be noticeably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • A few patches have been applied to the qcacld-2.0 WiFi driver in the kernel, which are mainly vulnerability fixes.
    Enjoy.
    3
    -onscreen navigation bar works for me, just the "disable hardware buttons" part does not.
    For workaround I use Srgrusso's patch from here.
    I'm referring specifically to the "Enable on-screen nav bar" option at Settings -> System -> Buttons, that doesn't require any system-level changes as made by that package that you've linked. When enabling it, no touch input is accepted anymore for some reason. It needs to be locked and unlocked a few times for it to accept input and the on-screen navbar added through that feature to work temporarily.
    -Safetynet fails where it hadn't before. (no biggie for me, just a thing I noticed)
    I have no idea about this. I'd have thought that it's now more likely to pass.
    The first custom rom for this device where Ableton Link works!!
    Hmm, wow.... I didn't expect that to be fixed in this release. That's great. :)
    My needs are very basic, I just need something stable, no need for root, sd-card storag etc..

    Would this be the preferred ROM? Or is the 17x release a better for my needs?

    Regarding Gapps, I noticed that users are using Flame Gapps and NikGapps, but I guess the regular Open Gapps could be an option as well.

    What is the recommended Gapps variant?
    For stability, 17.1 would be slightly better. With 18.1, there are certain occasional crashes (see issue 1) that I'm not sure about at the moment, which you may or may not be able to tolerate.

    As for Google apps, it's whichever is the smallest variant. For nikgapps, that would be core, and for opengapps, that would be pico. Something to note is that opengapps seems to often be more problematic for Android 11 than other google app packages, so it could be better to go for something else.
    Anyone else check this yet? It's working for me on @TALUAtXDA's previous version (202010407). I use this feature quite a bit as internal storage is too small, don't want to lose it if I dirty flash this version.
    I actually didn't know if adoptable storage was working in my previous release. I just assumed it didn't considering that it never worked properly with 17.1. Knowing that it did in my previous release of 18.1, it would probably(?) also work with my latest release.
    3
    Been using lineage 18.1 since it first became available and have updated it every month give or take since.

    There is not a more stable rom for this device and I for one fkin love :cool: it!!!

    Excellent work @TALUAtXDA

    We really appreciate your work and time dedicated to this amazing tablet..