Database Develop

[ROM][Pie] Unofficial LineageOS 16.0

This is an unofficial build of LineageOS 16.0 for the Motorola razr I, (XT890/SMI).
Lots of thanks to Hazou. This rom is based on his los-14 rom and I got help from him with los-16.
This rom has full hardware support and should run stable. It has been tested by me in daily use. I'm using the rom without google apps, but with microg. Installing google apps requires some apps to move to data partition because of limited system size. See install description for more info.
Special Features
-All features of Hazous 14.1 rom
-MicroG signature spoofing patch is included.
-Adaptive icons can be disabled in homescreen settings.
I can include more features if requested
Known Bugs
-The camera preview image sometimes shakes at random
Download
https://mega.nz/#F!5fBWlIAQ!Jlq9Bj789iJ0iIIptK00tg
Update
If you already run an earlier version of this rom, just boot to twrp and install the latest flashable zip file
Install
1. Backup everything you don't want to loose.
2. Download and install TWRP 3.2.3 (download in attachments. Can be flashed with fastboot or with another recovery)
3. If you come from another rom do a full wipe with twrp
4. Download and install the rom flashable zip (download from mega.nz link is in section download)
5. If you want to install opengapps or need system partition space for other things. Install the move_to_data.zip file from the attachments. This will move the Webview and the LatinIME app to data partition.
6. Choose one of the following options:
-either install google apps (download form https://opengapps.org/. Choose x86 9.0 nano or pico)
-or install MicroG (can be installed with the unofficial installer https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360) this is lighter in ram and cpu usage but you will get problems with google chrome and other apps
7. If you want root access install the addonsu-16.0-x86.zip (download in the attachments)
8. Reboot the phone. First reboot will take some time
Changelog
Code:
20191018:
fixed problem with sms receiving
20191012:
mobile network connection works now after boot
Fixed problems with network switching
Show taps option is working now
intel art extension enabled
Call recording enabled
text relocation warnings disbaled
(untested) encryption. Needs special configuration (see below)
20190819:
SELinux is now enforcing
Notification access feature enabled
solved crashes with houdini emulated apps
20190713:
usb configuration works properly
battery light works now
July security patches
20190704:
first stable release of this rom
DATA Encryption
If you want to enable data encryption this would break the pds partition backup. To prevent this, the cache partition can be used as backup location:
-edit /system/bin/pdsbackup.sh
-change PDS_FILE=/data/misc/pds/pdsdata.img to PDS_FILE=/cache/misc/pds/pdsdata.img
-resize data partition in TWRP:
Code:
umount /data
umount /sdcard
e2fsck -f /dev/block/mmcblk0p17
resize2fs /dev/block/mmcblk0p17 1367079
-reboot the phone
XDA:DevDB Information
unonfficial LineageOS 16.0, ROM for the Motorola RAZR i
Contributors
julianwi, Hazou
Source Code: https://github.com/julianwi/android_device_motorola_smi/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2019-08-19
Created 2019-07-04
Last Updated 2019-08-19

This if I did not expect it, I'll try to see how it goes. Thank you.

Download links and install description are up now. Download from mega.nz because xda download section is broken at the moment. I'm waiting for your test reports

It's really great works, thank you!!
I quickly tried and found several points.
- USB connection with PC
All USB connection option including File Transfer, USB tethering, PTP are grayed out.
Disabling/Enabling android debug in setting didn't work.
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
- SElinux
Although it is designated as permissive in device.mk, it's actually worked as "disabled".
I'm not sure it's related or not, however, when building "user build", it's failed with "ERROR: permissive domains not allowed in user builds".
I know "user build" is not officially supported in Lineage release, however, it's really helpful if we can do it for AFW usage.
Previously I could use Lineage 14.1 smi build for AFW and safetynet app with user build.
BTW, performance is really great, seems to be almost same as Lineage 11.

dumkm said:
It's really great works, thank you!!
I quickly tried and found several points.
- USB connection with PC
All USB connection option including File Transfer, USB tethering, PTP are grayed out.
Disabling/Enabling android debug in setting didn't work.
Click to expand...
Click to collapse
I also noticed that. Will see how this can be fixed. It is just a problem with the option dialog. Usb connection works fine. As a workaround you can set a default USB configuration in developer options
dumkm said:
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
Click to expand...
Click to collapse
I have not tested storage encryption yet. Will have a look at it later
dumkm said:
- SElinux
Although it is designated as permissive in device.mk, it's actually worked as "disabled".
I'm not sure it's related or not, however, when building "user build", it's failed with "ERROR: permissive domains not allowed in user builds".
I know "user build" is not officially supported in Lineage release, however, it's really helpful if we can do it for AFW usage.
Previously I could use Lineage 14.1 smi build for AFW and safetynet app with user build.
Click to expand...
Click to collapse
I think lineage trust doesn't differentiate between permissive and disabled. Selinux support is planned for future releases

Thank you for quick check.
Regarding USB connection, I also confirmed that Ubuntu can recognize as external storage with above option, besides Windows still does not recognize. Maybe depending on my environment.
Also I noticed that Chrome, Chrome Beta and Chrome Canary (therefore another Chrome based apps such as Maps Go) always crash. This is also maybe my environment only, though. BTW, I could install MicroG, besides couldn't install OpenGapps 9.0 pico due to partition size limit.
Additionally, I couldn't find any LED settings, currently LED is always off during charge or any notification.

dumkm said:
Thank you for quick check.
Regarding USB connection, I also confirmed that Ubuntu can recognize as external storage with above option, besides Windows still does not recognize. Maybe depending on my environment.
Also I noticed that Chrome, Chrome Beta and Chrome Canary (therefore another Chrome based apps such as Maps Go) always crash. This is also maybe my environment only, though. BTW, I could install MicroG, besides couldn't install OpenGapps 9.0 pico due to partition size limit.
Additionally, I couldn't find any LED settings, currently LED is always off during charge or any notification.
Click to expand...
Click to collapse
Notification Led should work. Can be configured under settings->apps and notifications->notifications->notification light. I don't know what happened with the battery light. It will hopefully come back if I upgrade the driver to hidl.
Google Chrome is a known problem with MicroG. It requires official gapps. I will check if some of the unprivileged lineage apps can be moved to data partition to make place for google apps

Newbie question
Hi all, I know someone who's selling her old RAZR i XT890 and I'm interested (for experimental reasons but also the oddity that it's Intel powered). I've never owned a RAZR i so I've got some questions:
-The phone is from 2012 so quite old and has 1GB RAM, does it work well with this Lineage 16? Because usually newer software would perform bad on older SoC (I used to have iOS 7 on iPhone 4 back in the day and it was painfully slow compared to 6).
-On Lineage 16, can it run any Android app as a standard new Android Pie phone? I ask because this is an Intel x86 CPU, so can it still run Android apps as normal or are most of them only designed for ARM and therefore unusable?
If I get the good news, I may buy the phone and try this Lineage OS custom ROM.

Regarding LED, maybe it became working after modifying some option of notification light. Battery connection light is still always off.
Regarding opengapps, I moved webview and LatinIME from app directory to external SD in TWRP, then installed as normal app after system boot. Webview worked fine besides LatinIME always crash. I'm using different IME, so it's no problem. With this environment, opengapps nano can be installed, then Chrome, Maps and other google apps worked.

dumkm said:
Regarding LED, maybe it became working after modifying some option of notification light. Battery connection light is still always off.
Regarding opengapps, I moved webview and LatinIME from app directory to external SD in TWRP, then installed as normal app after system boot. Webview worked fine besides LatinIME always crash. I'm using different IME, so it's no problem. With this environment, opengapps nano can be installed, then Chrome, Maps and other google apps worked.
Click to expand...
Click to collapse
That's good. Than we can make a flashable zip to automatically move and symlink them to data partition.
I will provide a new build till end of the week with improved usb and notification LED implementation. I already got it working in my local setup
flameseewa said:
Hi all, I know someone who's selling her old RAZR i XT890 and I'm interested (for experimental reasons but also the oddity that it's Intel powered). I've never owned a RAZR i so I've got some questions:
-The phone is from 2012 so quite old and has 1GB RAM, does it work well with this Lineage 16? Because usually newer software would perform bad on older SoC (I used to have iOS 7 on iPhone 4 back in the day and it was painfully slow compared to 6).
-On Lineage 16, can it run any Android app as a standard new Android Pie phone? I ask because this is an Intel x86 CPU, so can it still run Android apps as normal or are most of them only designed for ARM and therefore unusable?
If I get the good news, I may buy the phone and try this Lineage OS custom ROM.
Click to expand...
Click to collapse
Newer android versions have been designed while keeping low ram devices in mind. Ram hungry special features like the picture in picture mode are excluded from builds for older device. So the situation is much better then on iOS. But a newer phone would run better thought.
Most android apps are available for x86. But some are still arm only and get automatically emulated. The intel houdini emulator integrates these apps natively into the system but they are a bit slower then x86 apps. These are for example Skype and a few unity based games

julianwi said:
Newer android versions have been designed while keeping low ram devices in mind. Ram hungry special features like the picture in picture mode are excluded from builds for older device. So the situation is much better then on iOS. But a newer phone would run better thought.
Most android apps are available for x86. But some are still arm only and get automatically emulated. The intel houdini emulator integrates these apps natively into the system but they are a bit slower then x86 apps. These are for example Skype and a few unity based games
Click to expand...
Click to collapse
Thanks for the response. So I should be alright with it then, hopefully. I just hope it won't lag on that old SoC. I'd love if you could upload a quick video of it in action.

TWRP error 70
julianwi said:
This is an unofficial build of LineageOS 16.0 for the Motorola razr I, (XT890/SMI).
Lots of thanks to Hazou. This rom is based on his los-14 rom and I got help from him with los-16.
This rom has full hardware support and should run stable. It has been tested by me in daily use. I'm using the rom without google apps, but with microg. I don't know how smooth it runs with official gapps.
Special Features
-All features of Hazous 14.1 rom
-MicroG signature spoofing patch is included.
-Adaptive icons can be disabled in homescreen settings.
I can include more features if requested
Known Bugs
-Mobile cell connection doesn't connect after boot. You have to turn airplane mode on and off to let it work.
-selinux is set to permissive for now (reduced security)
Please report more bugs if you test this rom
Install
1. Backup everything you don't want to loose.
2. Download and install TWRP 3.2.3 (download in attachments. Can be flashed with fastboot or with another recovery)
3. If you come from another rom do a full wipe with twrp
4. Download and install the rom flashable zip (download from mega.nz https://mega.nz/#!ICwXRC6D!VZqe3o5zeWbmMiZvka_BtUTW5T_V7_OdMS57Oe9CbMk)
5. Choose one of the following options:
-either install MicroG (can be installed with the unofficial installer https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360)
-or install google apps (download form https://opengapps.org/. Choose x86 9.0 pico)
6. If you want root access install the addonsu-16.0-x86.zip (download in the attachments)
7. Reboot the phone. First reboot will take some time
XDA:DevDB Information
unonfficial LineageOS 16.0, ROM for the Motorola RAZR i
Contributors
julianwi, Hazou
Source Code: https://github.com/julianwi/android_device_motorola_smi/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2019-07-04
Created 2019-07-04
Last Updated 2019-07-05
Click to expand...
Click to collapse
I've installed the OS without problems, but when i try to get GApps Pico or any other version TWRP prompt error 70. How should i proceed? There is any additional configuration needed?

Kazvko said:
I've installed the OS without problems, but when i try to get GApps Pico or any other version TWRP prompt error 70. How should i proceed? There is any additional configuration needed?
Click to expand...
Click to collapse
Yes, system partition size is limited on this phone. To install GApps some files need to be moved to data partition.
I created a flashable zip to automate this process. Take a look at the modified install description in the first post

New build is up now.
flameseewa said:
Thanks for the response. So I should be alright with it then, hopefully. I just hope it won't lag on that old SoC. I'd love if you could upload a quick video of it in action.
Click to expand...
Click to collapse
Sorry don't have enough time to make a video in the near future. Maybe someone else can record a video of it

I could confirm that notification LED and USB storage works fine with lineage-16.0-20190713-UNOFFICIAL-smi. Thanks.
Still WiFi with storage encryption does not work.

julianwi said:
New build is up now.
Sorry don't have enough time to make a video in the near future. Maybe someone else can record a video of it
Click to expand...
Click to collapse
Alright, thanks. I bought my friend's RAZR i and I am planning to use it as a daily driver with this ROM (I'm a light user anyway), I can't thank you enough for making this LineageOS for such an old device. I wonder if such a recent Lineage has been developed for the 2011 Atrix, haven't seen one.
I have questions though, firstly I've never used a custom ROM before, can I simply follow the instructions on this thread to get it working, or is there anything that has to be done beforehand like rooting? Secondly, are any other OSs successfully booting on this x86 phone, as I can't find it on XDA? (it surprisingly hasn't gotten much attention as a hackable device like HTC HD2 or Nokia N900 got).

dumkm said:
I could confirm that notification LED and USB storage works fine with lineage-16.0-20190713-UNOFFICIAL-smi. Thanks.
Still WiFi with storage encryption does not work.
Click to expand...
Click to collapse
I know, haven't looked at the storage encryption for now. It will maybe be in the next update next month
flameseewa said:
Alright, thanks. I bought my friend's RAZR i and I am planning to use it as a daily driver with this ROM (I'm a light user anyway), I can't thank you enough for making this LineageOS for such an old device. I wonder if such a recent Lineage has been developed for the 2011 Atrix, haven't seen one.
I have questions though, firstly I've never used a custom ROM before, can I simply follow the instructions on this thread to get it working, or is there anything that has to be done beforehand like rooting? Secondly, are any other OSs successfully booting on this x86 phone, as I can't find it on XDA? (it surprisingly hasn't gotten much attention as a hackable device like HTC HD2 or Nokia N900 got).
Click to expand...
Click to collapse
If the phone never had a custom rom yet, you have to unlock the bootloader first. Description is in this thread: https://forum.xda-developers.com/showthread.php?t=1928551

julianwi said:
If the phone never had a custom rom yet, you have to unlock the bootloader first. Description is in this thread: https://forum.xda-developers.com/showthread.php?t=1928551
Click to expand...
Click to collapse
That's an old guide, will everything still work?

flameseewa said:
That's an old guide, will everything still work?
Click to expand...
Click to collapse
Yes, it should still work the same. If some links are outdated you can google them yourself

Thank you for bringing my old RAZR i back to life! I really appreciate the time and effort you spent for this obselete phone. Looking forward for more updates and for a bug free ROM. Using it now
dumkm said:
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
Click to expand...
Click to collapse
I'm not sure if I misunderstood but when you said "it required deleting....." and "reducing partition size of data", did you mean you can get WiFi to work if you do those things? I'm no expert at these but I can atleast apply the "fix" (if it really is) given that you guide me, if it's okay with you. Thanks!

Android Auto and Lineage 17.1

I instale the ( Lineage os 17.1.20200415 and Gapps) on my S8+ . All ok ,Thanks to the developer . The only problem is with Android Auto and the usb connection in Lineage software... maybe authorities usb choice is not to file tranfer...
In S8+ with original samsung os "android 9" the application android auto with same version as above function very well.
I think the problem is the way that lineage manage the usb connection with Android Auto!!!
When Android Auto strat in the infotainment the phone usb force (goes) to "without file transfer" and the connection stops
Any help

Deleted member 10657845 said:
I instale the ( Lineage os 17.1.20200415 and Gapps) on my S8+ . All ok ,Thanks to the developer . The only problem is with Android Auto and the usb connection in Lineage software... maybe authorities usb choice is not to file tranfer...
In S8+ with original samsung os "android 9" the application android auto with same version as above function very well.
I think the problem is the way that lineage manage the usb connection with Android Auto!!!
When Android Auto strat in the infotainment the phone usb force (goes) to "without file transfer" and the connection stops
Any help
Click to expand...
Click to collapse
I observe the same behavior when connecting the old Samsung S5 Neo running LOS 17.1 to the HU. The USB connection type switches to "no data transfer" just when plugged to HU's USB port regardless of the type it was set to before. But it does not matter, it connects to HU anyway.
But I still cannot use it as it disconnects from HU some time after. I guess it is not related to the USB connection type as it keeps connection for some time (from couple of seconds to 1 or 2 minutes) before it disconnects from HU.

Me too. I have Redmi Note 7 and lineage 17.1 with gapps (nano i stock tested) and app shows that accessory is not supported and car display shows that application quit unexpectedly. Mayby some google service is broken/uninstalled? I tested also on PixelExperience ROM and it works fine.

also, have moto g6 plus and do the same behaviour... on stock rom andorid auto works great, in pixel experience also work great, just lineage send mi the "device not compatible" popup. does anyone had a work around or do i need to reflash another rom. thanks in advance for your comments.

Me too.
My wife’s stock pixel 4, no problem.
My Samsung A5 2017 when it had stock ROM, no problem.
My Samsung A5 2017 with LOS 17.1, not working with my truck’s Android Auto.
AA app on the phone installs and functions well, but when plugged into the 2018 Chevy, the phone says:
No installed apps work with this USB accessory.
Learn more at www.android.com/auto/.
Any searching and reading shows many having this issue with 16 and 17 but not earlier versions.

McAnik said:
Me too.
My wife’s stock pixel 4, no problem.
My Samsung A5 2017 when it had stock ROM, no problem.
My Samsung A5 2017 with LOS 17.1, not working with my truck’s Android Auto.
AA app on the phone installs and functions well, but when plugged into the 2018 Chevy, the phone says:
No installed apps work with this USB accessory.
Learn more at www.android.com/auto/.
Any searching and reading shows many having this issue with 16 and 17 but not earlier versions.
Click to expand...
Click to collapse
solve the same issue using an opengapps build back from december 2020, i guess is some bug from recent builds

d_g_m_2000 said:
solve the same issue using an opengapps build back from december 2020, i guess is some bug from recent builds
Click to expand...
Click to collapse
Yes, I can confirm that. The latest GApps that works to me with AA on LOS 17.1 is the 20201201 one. All the newest versions I tried so far have the "No installed apps work with this USB accessory." issue.

Oooooh Yeah!
That fixed it! I re-flashed with open gapps 2020-12-01 and the truck picked it up right away.
In the truck, when I plugged it in, I pressed Android Auto on the display and it hung saying it was checking messages. Even after reconnecting the USB a few times. So on my dash I went to settings, AA, where all phones are listed and pressed mine to make it inactive, then again to make it active.
Then everything worked!
Thanks so much.

I have just installed LOS 17.1 on my Pixel 5", but with Microg rather than OpenGapps. Not downloaded AA just yet, and wondered if others have had issues with Microg?

JohnE2 said:
I have just installed LOS 17.1 on my Pixel 5", but with Microg rather than OpenGapps. Not downloaded AA just yet, and wondered if others have had issues with Microg?
Click to expand...
Click to collapse
Go to microg thread for more info.. I think AA is not supported by microg.

sunarowicz said:
Yes, I can confirm that. The latest GApps that works to me with AA on LOS 17.1 is the 20201201 one. All the newest versions I tried so far have the "No installed apps work with this USB accessory." issue.
Click to expand...
Click to collapse
Do you have a link please:? Here https://sourceforge.net/projects/opengapps/files/arm64/ the versions jump from 2020-07-05 to 2020-12-11. Thanks

jo mateix said:
Do you have a link please:? Here https://sourceforge.net/projects/opengapps/files/arm64/ the versions jump from 2020-07-05 to 2020-12-11. Thanks
Click to expand...
Click to collapse
Ah, nevermind; 2020-07-05 worked

McAnik said:
Me too.
My wife’s stock pixel 4, no problem.
My Samsung A5 2017 when it had stock ROM, no problem.
My Samsung A5 2017 with LOS 17.1, not working with my truck’s Android Auto.
AA app on the phone installs and functions well, but when plugged into the 2018 Chevy, the phone says:
No installed apps work with this USB accessory.
Learn more at www.android.com/auto/.
Any searching and reading shows many having this issue with 16 and 17 but not earlier versions.
Click to expand...
Click to collapse
I had absolutely no issues with LOS 17.1 and Android Auto together with my smart EQ, but now since April, after the Upgrade to LOS 18.1 I get exactly the same error output like you.
Is this problem Android 11 or OpenGApps related? I'm on the latest official OpenGApps test build from january since there is nothing newer available atm.

G A S T said:
I had absolutely now issues with LOS 17.1 and Android Auto together with my smart EQ, but now since April, after the Upgrade to LOS 18.1 I get exactly the same error output like you.
Is this problem Android 11 or OpenGApps related? I'm on the latest official OpenGApps test build from january since there is nothing newer available atm.
Click to expand...
Click to collapse
i think it is a opengapps problem related. i had android 11 with pixel experience (with gapps included) on my moto g6 plus and AA worked normally... but when i flashed lineages 17.1 + opengapps newer builds it just fail.

McAnik said:
Oooooh Yeah!
That fixed it! I re-flashed with open gapps 2020-12-01 and the truck picked it up right away.
In the truck, when I plugged it in, I pressed Android Auto on the display and it hung saying it was checking messages. Even after reconnecting the USB a few times. So on my dash I went to settings, AA, where all phones are listed and pressed mine to make it inactive, then again to make it active.
Then everything worked!
Thanks so much.
Click to expand...
Click to collapse
Hi, I am having the same issue with crDroid on Android 11 using gapps aroma and pico build from 2021-01-30. Are you able to provide one from December 2020 for Android 11? Or are you on Android 10? I don't see it here. Or do you know if another build works? I'm hoping to use open gapps aroma. Thanks for the help.

Hey guys I found a solution for those who can't get Android Auto to display on their car screen with Android 11 and gapps.
So after having issues with the gapps I tried MindTheGapps and Android Auto was working on there. I noticed that when I flashed the ROM Android Auto was installed already, but it was just a little stub app, only about 3 mb. So I decided to copy the folder containing the apk file and install it into a ROM with OpenGapps. The original file was placed in system/product/priv-app, so I copied it there using TWRP then rebooted. It did not work. So I uninstalled all the updates to AA and removed it then pasted it back in, and ended up in a bootloop. So finally I tried installing the stub app in /system/priv-app and rebooted. I then updated AA on the play store and it worked! So it seems that in order to get AA working you need this little stub app that must contain the necessary code to connect to your car. Note that AA will no longer show up in your launcher but you can download the "Android Auto for Phone Screen" app if you need to use it both on your car screen and on your phone in a car without an AA head unit. So the steps are as follows
Copy the attached apk file into a folder called AndroidAutoStubPrebuilt
Completely uninstall AA from your phone, both in user apps and system apps.
Boot into TWRP
Mount System in the "Mount" setting in TWRP
Copy the AndroidAutoStubPrebuilt folder containing the attached apk into system/priv-app/ (or your preferred folder but it needs to be in a system folder, I had a bootloop when I installed it into system/product/priv-app so if something like that happens try a different folder)
reboot your phone
install play store update for AA
set up AA on your phone
Connect to your car.
Enjoy.
Hopefully this fixes the issue for you guys as well. If it does, please let me know!
For reference I am using a US Moto G5 plus XT1687 (Potter) running CrDroid 7.5 with Open Gapps Aroma and Magisk.
This stub app comes from flashing the MindTheGapps package and is in no way my creation, I am simply sharing the apk from it for those who are using open gapps and can't get AA working. Thanks MTG, I couldn't have found this solution without it!​

SteveMKII said:
Hey guys I found a solution for those who can't get Android Auto to display on their car screen with Android 11 and gapps.
So after having issues with the gapps I tried MindTheGapps and Android Auto was working on there. I noticed that when I flashed the ROM Android Auto was installed already, but it was just a little stub app, only about 3 mb. So I decided to copy the folder containing the apk file and install it into a ROM with OpenGapps. The original file was placed in system/product/priv-app, so I copied it there using TWRP then rebooted. It did not work. So I uninstalled all the updates to AA and removed it then pasted it back in, and ended up in a bootloop. So finally I tried installing the stub app in /system/priv-app and rebooted. I then updated AA on the play store and it worked! So it seems that in order to get AA working you need this little stub app that must contain the necessary code to connect to your car. Note that AA will no longer show up in your launcher but you can download the "Android Auto for Phone Screen" app if you need to use it both on your car screen and on your phone in a car without an AA head unit. So the steps are as follows
Copy the attached apk file into a folder called AndroidAutoStubPrebuilt
Completely uninstall AA from your phone, both in user apps and system apps.
Boot into TWRP
Mount System in the "Mount" setting in TWRP
Copy the AndroidAutoStubPrebuilt folder containing the attached apk into system/priv-app/ (or your preferred folder but it needs to be in a system folder, I had a bootloop when I installed it into system/product/priv-app so if something like that happens try a different folder)
reboot your phone
install play store update for AA
set up AA on your phone
Connect to your car.
Enjoy.
Hopefully this fixes the issue for you guys as well. If it does, please let me know!
For reference I am using a US Moto G5 plus XT1687 (Potter) running CrDroid 7.5 with Open Gapps Aroma and Magisk.
This stub app comes from flashing the MindTheGapps package and is in no way my creation, I am simply sharing the apk from it for those who are using open gapps and can't get AA working. Thanks MTG, I couldn't have found this solution without it!​
Click to expand...
Click to collapse
Very Interesting! I hope that the OGApps team will take account of your important hint and that we'll find a fix in the next builds.

Thanks for sharing, we'll definitely include this (or something similar) in our next builds.

SteveMKII said:
Hey guys I found a solution for those who can't get Android Auto to display on their car screen with Android 11 and gapps.
So after having issues with the gapps I tried MindTheGapps and Android Auto was working on there. I noticed that when I flashed the ROM Android Auto was installed already, but it was just a little stub app, only about 3 mb. So I decided to copy the folder containing the apk file and install it into a ROM with OpenGapps. The original file was placed in system/product/priv-app, so I copied it there using TWRP then rebooted. It did not work. So I uninstalled all the updates to AA and removed it then pasted it back in, and ended up in a bootloop. So finally I tried installing the stub app in /system/priv-app and rebooted. I then updated AA on the play store and it worked! So it seems that in order to get AA working you need this little stub app that must contain the necessary code to connect to your car. Note that AA will no longer show up in your launcher but you can download the "Android Auto for Phone Screen" app if you need to use it both on your car screen and on your phone in a car without an AA head unit. So the steps are as follows
Copy the attached apk file into a folder called AndroidAutoStubPrebuilt
Completely uninstall AA from your phone, both in user apps and system apps.
Boot into TWRP
Mount System in the "Mount" setting in TWRP
Copy the AndroidAutoStubPrebuilt folder containing the attached apk into system/priv-app/ (or your preferred folder but it needs to be in a system folder, I had a bootloop when I installed it into system/product/priv-app so if something like that happens try a different folder)
reboot your phone
install play store update for AA
set up AA on your phone
Connect to your car.
Enjoy.
Hopefully this fixes the issue for you guys as well. If it does, please let me know!
For reference I am using a US Moto G5 plus XT1687 (Potter) running CrDroid 7.5 with Open Gapps Aroma and Magisk.
This stub app comes from flashing the MindTheGapps package and is in no way my creation, I am simply sharing the apk from it for those who are using open gapps and can't get AA working. Thanks MTG, I couldn't have found this solution without it!​
Click to expand...
Click to collapse
Brilliant!! This just did the trick with LOS 18.1 and opengapps 11 beta 20210130 on my XZ1 compact. I've been holding off on the update because of this. Thank you!!!

SteveMKII said:
Hey guys I found a solution for those who can't get Android Auto to display on their car screen with Android 11 and gapps.
So after having issues with the gapps I tried MindTheGapps and Android Auto was working on there. I noticed that when I flashed the ROM Android Auto was installed already, but it was just a little stub app, only about 3 mb. So I decided to copy the folder containing the apk file and install it into a ROM with OpenGapps. The original file was placed in system/product/priv-app, so I copied it there using TWRP then rebooted. It did not work. So I uninstalled all the updates to AA and removed it then pasted it back in, and ended up in a bootloop. So finally I tried installing the stub app in /system/priv-app and rebooted. I then updated AA on the play store and it worked! So it seems that in order to get AA working you need this little stub app that must contain the necessary code to connect to your car. Note that AA will no longer show up in your launcher but you can download the "Android Auto for Phone Screen" app if you need to use it both on your car screen and on your phone in a car without an AA head unit. So the steps are as follows
Copy the attached apk file into a folder called AndroidAutoStubPrebuilt
Completely uninstall AA from your phone, both in user apps and system apps.
Boot into TWRP
Mount System in the "Mount" setting in TWRP
Copy the AndroidAutoStubPrebuilt folder containing the attached apk into system/priv-app/ (or your preferred folder but it needs to be in a system folder, I had a bootloop when I installed it into system/product/priv-app so if something like that happens try a different folder)
reboot your phone
install play store update for AA
set up AA on your phone
Connect to your car.
Enjoy.
Hopefully this fixes the issue for you guys as well. If it does, please let me know!
For reference I am using a US Moto G5 plus XT1687 (Potter) running CrDroid 7.5 with Open Gapps Aroma and Magisk.
This stub app comes from flashing the MindTheGapps package and is in no way my creation, I am simply sharing the apk from it for those who are using open gapps and can't get AA working. Thanks MTG, I couldn't have found this solution without it!​
Click to expand...
Click to collapse
How can I uninstall the Android Auto from user apps and system apps?

exynos5433 - which gapps to use discussion for 19.1 roms (SM-T710 and SM-T810)

I'm NOT a gapps user so I will NOT be participating in this thread. I'm not supporting or answering any gapps project questions.
This thread is for users who want/need to run gapps with 19.1 on exynos5433 devices like SM-T710 and SM-T810
I opened this thread as a courtesy for users who want/need gapps.
At last count there were 5 gapps projects and they are in various states of "working" wrt to 19.1. It's your responsibility to put in some hours of research to find out what gapps works for you.
All I can say is that some testers report that NikGapps 12.1L arm64 core (May 1, 2022) work. Despite the arm64 name, that version WILL work on exynos5433. Your mileage may vary.
https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-SL/01-May-2022/

Reserved.

I can confirm that I have successfully installed NikGapps Core along with @retiredtab's T170 and T810 LOS19.1 ROMs. I have my complete set of Google Play Apps available to me on the tablet after installing them, including sensitive ones such as Peacock, Netflix, Disney+, etc. All Apps run normally, and when I check Google Play/Settings and scroll to the bottom, I see “Device is certified”.

I've tried to install BitGapps pico + Flamegapps basic (both ARM and ARM64 versions).
NikGapps64 finally worked.

pflyaz said:
I can confirm that I have successfully installed NikGapps Core along with @retiredtab's T170 and T810 LOS19.1 ROMs. I have my complete set of Google Play Apps available to me on the tablet after installing them, including sensitive ones such as Peacock, Netflix, Disney+, etc. All Apps run normally, and when I check Google Play/Settings and scroll to the bottom, I see “Device is certified”.
Click to expand...
Click to collapse
Installed the ROM on clean wipe on Galaxy Tab S2 T810. Then NikGapps Full thru Basic in different tries.
1. With NikGapps Full to Basic there is no onscreen keyboard that comes up to set up wifi or PIN. Only a Google Voice typing error shows up. How is this solved?
2. After set up without Wifi, the tablet says "Tablet starting....." and does not go further.
Any ideas welcome....

chappatti said:
Installed the ROM on clean wipe on Galaxy Tab S2 T810. Then NikGapps Full thru Basic in different tries.
1. With NikGapps Full to Basic there is no onscreen keyboard that comes up to set up wifi or PIN. .....
Click to expand...
Click to collapse
Did you "format data"?
That solved it on mine (with the 2nd flash) testing the prealpha build.
I took only core instead of basic.

I had this in my 19.1 msm8916 post #1, but forgot to add it to exynos5433 post #1. The following is now added to 19.1 T710 and T810 post #1. This would also apply to things like wifi password, etc, not just bluetooth pin.
keyboard bug workaround. When prompted to enter something like a Bluetooth pin, sometimes the keyboard is not shown on the screen or off screen. The workaround is to bring up the built in browser, touch the url panel where the http address is and then press the number key when the keyboard pops up. Leave this browser open like that, then press the home button and try your Bluetooth pairing again.
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438

chappatti said:
Installed the ROM on clean wipe on Galaxy Tab S2 T810. Then NikGapps Full thru Basic in different tries.
1. With NikGapps Full to Basic there is no onscreen keyboard that comes up to set up wifi or PIN. Only a Google Voice typing error shows up. How is this solved?
2. After set up without Wifi, the tablet says "Tablet starting....." and does not go further.
Any ideas welcome....
Click to expand...
Click to collapse
I figured this out and everything runs good.
I used two files (one file in attachment). The zip file is flashed from TWRP. I also installed the Gboard apk from :
Gboard - the Google Keyboard 12.1.06.463429027-beta (arm-v7a) (nodpi) (Android 6.0+) APK Download by Google LLC - APKMirror
Gboard - the Google Keyboard 12.1.06.463429027-beta (arm-v7a) (nodpi) (Android 6.0+) APK Download by Google LLC - APKMirror Free and safe Android APK downloads
www.apkmirror.com
and apk was installed normally. Gboard gets installed and all is good. I think the apk alone should do it, but I did not try that alone. (For some reason attaching the apk file to this post fails). Once this is done and the Wifi is set up one can then download any other keyboard they want from app store.
Also, I don't recommend using NikGapps above "basic", on Tab S2 T810. A Gapp keeps crashing and the tablet is stuck on "Tablet starting.....".
I downloaded Basic NikGapps from here: https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-SL/09-Jul-2022/

retiredtab said:
I had this in my 19.1 msm8916 post #1, but forgot to add it to exynos5433 post #1. The following is now added to 19.1 T710 and T810 post #1. This would also apply to things like wifi password, etc, not just bluetooth pin.
keyboard bug workaround. When prompted to enter something like a Bluetooth pin, sometimes the keyboard is not shown on the screen or off screen. The workaround is to bring up the built in browser, touch the url panel where the http address is and then press the number key when the keyboard pops up. Leave this browser open like that, then press the home button and try your Bluetooth pairing again.
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
Click to expand...
Click to collapse
Please see my post above.

I struggled with Installing Gapps on the latest Nov 11, 2022 release.
Tried:
NikGapps NikGapps-core-arm64-12.1-20220908-signed.zip and NikGapps-basic-arm64-12.1-20220908-signed.zip - both installs without issues in TWRP but no Play store or any other apps in the system.
BiTGApps-arm64-12.1.0-v1.7_signed.zip - fails with error "unsupported platform"
BiTGApps-arm-12.1.0-v1.7_signed.zip - installed and Play Store is visible. Get it here https://bitgapps.github.io/download.html

Pawel_ said:
I struggled with Installing Gapps on the latest Nov 11, 2022 release.
Tried:
NikGapps NikGapps-core-arm64-12.1-20220908-signed.zip and NikGapps-basic-arm64-12.1-20220908-signed.zip - both installs without issues in TWRP but no Play store or any other apps in the system.
BiTGApps-arm64-12.1.0-v1.7_signed.zip - fails with error "unsupported platform"
BiTGApps-arm-12.1.0-v1.7_signed.zip - installed and Play Store is visible. Get it here https://bitgapps.github.io/download.html
Click to expand...
Click to collapse
I installed NikGapps-omni-arm64-12.1-20220709-signed.zip from twrp and it is working well. I have the play store.
I was surprised to see that it is an arm64 version even though ( I thought that) the t710 (exynos) has an arm32 processor.

Phone permission needed to take calls.

Hya,
i have a sagit phone, with lineageos 18.1 on it, pioneer head unit capable of AA and CP. Until last weekend, it worked fine. After an error, where i had to factory default the phone and reinstall the apps again,i get the message "Phone permission needed to take calls. When it's safe, turn on the phone permission in Settings."
But all permissions are set for AA, including phone.
Any hint in how to solve this?
Thx in advance!

Did you check your Bluetooth settings if phone permission is on for your pioneer head unit Bluetooth connection?

Hi, same problem, not tried yet with bluetooth settings as suggested above. Did it work? ('m lazy to make a new attempt with LOS 18.1, I explain why below)
So if it's not working with the tip above, I give here some clues :
I recently upgraded my Sony X Compact from Android 8 to lineageos 18.1 (Android 11) with MindTheGapps installed. Everything works fine except these call permissions.
I decided, after several failures, to test LOS 17 and calls are now possible from AA.
In Android 11, AA is natively integrated. In A10, it's not, it doesn't appear in the bluetoth/NFC settings, like in Android 8. Does this make the difference? A8 and A10 seem using the same permissions process, A11 not.
About permissions, I found another thread close to my issue and could be related: https://forum.xda-developers.com/t/linageos-16-overlay-permission-denied-but-it-is-checked.3924101/ . I tried the second method (Magisk) but it gave nothing and I'm just a newbie in Android world to try the other methods.
Any suggestions ?

Update from last reply
I finally installed LOS 19.1 (Android 12) with still MindTheGapps and everything works perfectly with AA. So it doesn't seem to be an Android version issue but rather LOS 18.1 itself or MindTheGapps. Maybe by using other gapps you'll get it work (I didn't try).

Hi,
I've upgraded my 9 y.o. Galaxy Note 4 to LineageOS 18.1 recently and was very happy with it until I stumbled on the same problem.
Android Auto claimed to have phone permission in the Application settings but the permission was impossible to change (mandatory/grayed out) and the unit in my Civic 10 was showing the same error as pw44's.
Having no UI to fiddle with, I thought maybe that can be tweaked with some ADB command, and after some reading here:
How to Grant Permissions Using ADB in Android
It can be tricky to grant advanced permissions to Android apps without rooting your phone. Here's how you can use ADB to achieve it.
www.makeuseof.com
and there:
Listing permissions of Android application via adb
Using adb, how can I find out the which permissions an Android application requires? Because I want to display the permissions of multiple applications on different devices, viewing them in Google...
stackoverflow.com
I came up with a command that fixed it:
adb shell pm grant com.google.android.projection.gearhead android.permission.CALL_PHONE
Obviously, I googled that exact command and found confirmation here:
Lineage OS 18.1 Xiaomi Redmi Note 6 Pro cant phone calls in Android Auto (#5092) · Issues · LineageOS / issues / android · GitLab
Expected Behavior Realize phone calls in Android auto Current Behavior Android auto...
gitlab.com

[UNOFFICIAL][ROM]BETA LineageOS 18.1 for SM-T813 - June 9, 2023

PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
This is ONLY for the T813. I do not have and will NOT build T713, T719 and T819. See post #2, FAQ 20. Any questions asking to build these will be ignored.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom. If you are new to flashing custom roms, do NOT attempt this. If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
9. deep sleep
10 DRM level 3 (SD definition)
Known issues/What doesn't work/what's not tested
NOTE: If any following features are important to you, don't use this rom as I will not be fixing them because I
i. don't use/need that feature
ii. already tried fixing it and couldn't succeed and won't spend anymore time on it.
1. Stock camera doesn't work at all (reason i and ii). Opencamera version 1.51.1 works for taking pictures and videos BUT with a 10 to 15 second delay when switching between functions.
I have not tested any video conferencing apps so they may or may not work. If they don't work, revert back to old rom as I will not be spending anytime trying to fix/troubleshoot.
2. fingerprint (reason i). I never use it and I see it doesn't even load correctly in the logs.
3. ARM64 gapps (reason i). Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of ARM64 gapps.
There are various gapps projects (at least 5 in 2023). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours/days doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread. As a courtesy to gapps users, I have opened a new thread at
https://forum.xda-developers.com/t/...o-use-discussion-for-18-1-rom-sm-t813.4540423
so you may discuss gapps. I will NOT be participating in that thread as I do NOT use gapps.
4. disk encryption (reason i). Never tested.
5. If you restart the device with the purpose to reboot it and the usb cable is plugged in, the device will not reboot and stay in charging mode. Simply unplug the usb cable, wait 15 seconds and restart the device.
Source code
All the source code including the kernel is provided in post #2 FAQ1.
Thanks
1. LineageOS team for source code.
The rest in alphabetical order.
2. @Deltadroid for updating the msm8976 kernel for branches 14.1 and 16.0 with bug and security fixes. I'm using his 16.0 branch.
3. @lifehackerhansol for suggesting that I kang the pm-* proprietary blobs from another rom and making suggestions for possible fixes to the camera.
4. Team Infusion Developers github.

FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
https://github.com/syphyr/android_kernel_samsung_msm8976/tree/lineage-16.0
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8976-common
https://github.com/retiredtab/android_device_samsung_gts210vewifi
The vendor tree files are at
https://github.com/retiredtab/proprietary_vendor_samsung_msm8976
The manifest.xml (or roomservice.xml) and build instructions for 18.1 are at
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/18.1
Q2. Is this BETA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since Oct 2022 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this ROM BY ITSELF (no gapps, magisk, etc) and see if you like it.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. Your tablet will also run slower when you use gapps. You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use TWRP 3.6.2_9-0. Do not use any other version for these reasons.
https://forum.xda-developers.com/t/...or-sm-t810-jan-11-2023.4430349/#post-86745013
https://dl.twrp.me/gts210vewifi/
I will not answer questions if you don't use this exact TWRP version.
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. I don't have the time to help newbies, so please do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here. In addition, I don't run Windows OS at all.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Will you build 19.1 and higher for this device?
A10. Any questions on higher Android versions will be completely ignored. I do this in my free/spare time and will not be subject to any ETAs or demands. If you want a higher version, the source code is freely available as per FAQ #1 and you can build it yourself.
Q11. Do I need to erase everything and format my data?
A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
You MUST FORMAT DATA in TWRP so backup your files first to some external storage (external microsd or PC).
NOTE: After you do the above, first boot (without gapps, magisk, etc) will take about 90 seconds. It may pop with a message saying "System UI isn't responding". Hit close app and then reboot the tablet again.
Q12. What gapps should I use?
A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various ARM64 gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
In addition, some of the gapps may not install properly when using TWRP and say "cannot /mnt/system".
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I WILL NOT answer any questions regarding gapps. This thread is about the rom, not gapps. Android does not depend on gapps in order to work.
Questions about gapps, for your courtesy, should be asked in the thread below.
https://forum.xda-developers.com/t/...-use-discussion-for-18-1-rom-sm-t813.4540423/
Q14. Why isn't my post answered or ignored?
A14. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q15. What speed up/optimization tips do you suggest?
A15.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Use a web browser like Brave that has built in adblock and privacy features.
4. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
5. Look for apps that are open source, ad free and lightweight.
Q16. Does this rom support Magisk for root?
A16. I don't use Magisk. Magisk is always being updated to fool Google's certification process which may or may not work.
Q17. Will this rom ever become official?
A17. Never. I don't want the responsibilities that come with being an official maintainer.
Q18. What is the difference between this rom and others?
A18. This rom tries to be pure LineageOS with little to no modifications.
Q19. Will there be any major 18.1 code modifications in the future?
A19. I don't anticipate any major modifications. There may be some small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 18.1 is working.
Q20. Can you build a variant of this device? For example, a LTE or S-pen version.
A20. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working. To be clear, I will NOT build T713, T719 and T819.
Q21. Can I load this rom on a variant devivce like LTE or S-pen version?
A21. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q22. Does this rom support OTA updates?
A22. No and I have no plans to add that functionality.
Q23. Okay, I understand the consequences and that this is BETA rom and willing to take the risks outlined, now where can I find the rom?
A23. You can download it from
https://sourceforge.net/projects/retiredtab/files/SM-T813/18.1/

Release Notes
I have personally tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
June 9, 2023 release notes
1. Incorporates June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-06
2. Whatever LineageOS changed since May 5th patches (about 5,600 files had to be recompiled).
May 7, 2023 release notes
1. Incorporates May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-05
2. Whatever LineageOS changed since Apr 5th patches (about 6,600 files had to be recompiled).
Apr 15, 2023 release notes
1. Incorporates Apr 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-04
2. Whatever LineageOS changed since Mar 5th patches (about 4,500 files had to be recompiled).
3. Updated aptX code so that it works and stops crashing (broken in 17.1) as per https://github.com/retiredtab/propr...mmit/3f6bd0d979ae25e3ba23e2c214fa7207c81f6b32
March 17, 2023 release notes
1. Incorporates Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-03
2. Whatever LineageOS changed since Feb 5th patches (about 24,000 files had to be recompiled).
3. Added overlay to control capactive key light buttons to enable/disable or change duration as per
https://github.com/retiredtab/andro...mmit/5a2649a040adfb879fd03076f97dd5321c5e27e6
Feb 13, 2023 release notes
1. Incorporates Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02
2. Whatever LineageOS changed since Jan 5th patches (about 13,000 files had to be recompiled).
3. Updated DRM code so that Disney+ works. See
https://github.com/retiredtab/andro...mmit/6c41d16cf1a8b2e8c436b3bef922a47e606381ee
https://github.com/retiredtab/propr...mmit/fed0f34d48330908165f78051066127b0e1870d8
Jan 7, 2023 release notes
1. Initial release of 18.1
2. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
3. If you are upgrading from a custom rom, stock or any older versions of LineageOS (like 14.1, 16.0 or 17.1) YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA in TWRP. You cannot dirty flash at all. Backup your data first.

Reserved #4

I have personally tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
18.1 has been my daily driver since Oct 2022.
Jan 7, 2023 release notes
1. YOU MUST read posts 1-4 if you haven't already.
2. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
3. If you are upgrading from a custom rom, stock or any older versions of LineageOS (like 14.1, 16.0 or 17.1) YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA in TWRP. You cannot dirty flash at all. Backup your data first.

Thanks for all your efforts. I never thought anything above Android 10 would see the light of days on the T813 model, since it was highly neglected here in my opinion. I will definitly try it out

THANK YOU "RETIREDTAB" this is awesome!
I will try it out on my T813 and report back here if there are any problems, Thanks a lot for this rom!!!

@retiredtab, many, many thanks for this rom. Have done a full clean install, the backup of the previous 17.1 took longer. So far everything I need to use is working perfectly. I mainly read the news, pick up emails and buy too much stuff from amazon.
went with the opengapps pico set, and all my google stuff is working, and it restored my apps from the previous backup. Did have some odd issues giving permissions to to the various google apps but once that was sorted it ran.
keep up the good work, and will keep testing

Further update after a weekend of use, the screen off battery drain seems to be minimal(may be Greenify helping) but appears to be better than I had on the previous 17.1 rom. No other issues found as yet.

will the camera issue be adressed or it will stay like that?

Ferchurito said:
will the camera issue be adressed or it will stay like that?
Click to expand...
Click to collapse
I'd say its unlikely to change, far as I know its never been fixed in the previous 17.1 rom either. As retiredtab mentions in point 1, camera use is not a big need or he has alrady tried to fix it and not been able to.

I did everything wrong with a working result:
-My Starting point: LineageOS 17.1 (ripee) installed
- Backup of User Data @ Android System (copy to MicroSD)
- Updated the TWRP version to the recommended in TWRP (coming from ripee version for 17.1)
- Boot to System to ensure it's still working
- Backup everything in TWRP
In one batch without booting in between:
- I dirty flashed "lineageOS 18.1" over "lineageOS 17.1 (from ripee)"
- Flashed the Arm64 version for Android 11 of "mindTheGapps" over existing "OpenGapps (for Android 10)"
- Flashed Magisk *.zip
- Deleted Cache and Dalvik
Boot to system and it's working perfectly so far
FYI.: Camera App "ProcamX" is working as well.
FYI.: Especially for lineageOS 17.1 users: I can confirm GPS is working (GPS Test Plus)
For sure I wouldn't recommend this procedure and maybe I will do a clean install later to gain smoothness and to make it stable in general but so far it's super nice, no bootloop, random restarts (BUT it's based on a few hour usage only) or whatever and a big thank you to ritiredtab

I have Magisk and safetynet pass flashed. I can download Netflix from Playstore but it doesn't play any content. It seems that Widevine / DRM is not part of the ROM at all as the App "DRM Info" doesn't show any Widevine information. In consequence Netflix doesn't play and stuck in "loading". Anyway it seems to enable some old DRM blobs can fix the issue like at least for L3 which is SD playback. Something like here needs to be added I think....:
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/339185
Didn't dig deeper into the topic so far. Just want to share the info.

Renzke said:
It seems that Widevine / DRM is not part of the ROM at all as the App "DRM Info" doesn't show any Widevine information.
Click to expand...
Click to collapse
As I listed in post #1, DRM L3 works as I check/test/verify ALL my public xda builds for the functionality in post #1 before uploading.
Here's the results of checking DRM with 4 different programs. Devcheck by flar2 is what I use to check all my ROMS for a variety of values and widevine DRM L3 (along with clearkey) is clearly shown. Device Info HW and DRM Check also show widevine properly.
DRM Info by Android Fung is the only one that cannot show the widevine information which may be due to a bug in this program or it's poorly written and being denied by selinux enforcing.
DevCheck and Device Info HW are both ad free while DRM Check and DRM Info are infested with ads. The latter 2 are programs I will never use again.
In addition, DRM Info by Android Fung shows this in the logcat
Code:
GooglePlayServicesUtil: com.androidfung.drminfo requires the Google Play Store, but it is missing.
As I mentioned several times, I do NOT and will NOT install any gapps.
Your link to gerrit regarding DRM is already in my code (done a bit differently, but works as clearly shown by Devcheck).
https://github.com/retiredtab/propr...mmit/92ecf0f7615a291281e4b39da6be956e92e66d82
https://github.com/retiredtab/andro...mmit/5a91ac3d5d14510b335f8d6ec650b254edcdb2dc

@retiredtab Thanks for the detailed reply. You are right. I See Widevine L3 in other Apps as well. Shame on me '-'. Even Netflix itself gives this Info... Anyway... Playback is not starting while preview videos are working. Tried already a couple of versions without success and checked the permissions. As I'm customized with Magisk the rootcause could be on my side for sure. Prime Video is working by the way. Would be nice to know if a clean install has the same behaviour.

Renzke said:
@retiredtab I See Widevine L3 in other Apps as well.
Click to expand...
Click to collapse
There's a reason why I always recommend clean installs. When you don't do it, it leads to unexplained problems. If Prime is working, that suggests DRM L3 is working.
If a clean install doesn't work with Netflix, then see FAQ 9 and send me the logs (zipped). There's no guarantee that it will show anything wrong or if I can fix it. I don't have/use Netflix or any other $treaming service.
Having said that, I do build other roms like the T810 (S2 2015 exynos model) and others have commented that they do not need Magisk hide, root, etc to get Netflix shown in the playstore because my T810, like this T813, is selinux enforcing. They report that the T810 shows up as "device is certified".
Again, since I don't use gapps, I cannot confirm if "device is certified" is true for T813, but if it is, then Netflix should show up without Magisk/hide, root, etc. If it does show up, it's a bonus. If the T813 shows up as "device not certified", I have no plans to fix this as I don't use gapps.

@retiredtab I'm not sure if I will do a clean install as the system is working quite well expect Netflix and at the end of the day it's not super important for me. In case I do a clean install I will provide a log and be thankfull for the offer to fix things
The chances to have an indication is maybe low in the logs as Netflix loops in the loading screen without an error at all. Anyway I don't want to waste your time with this topic currently as I cleary didn't follow your instructions by doing a dirty flash and so on. And again... Super nice to have this rom which gives my tablet a 2nd life. Thanks a lot.

Renzke said:
@retiredtab I'm not sure if I will do a clean install as the system is working quite well expect Netflix and at the end of the day it's not super important for me. In case I do a clean install I will provide a log and be thankfull for the offer to fix things
The chances to have an indication is maybe low in the logs as Netflix loops in the loading screen without an error at all. Anyway I don't want to waste your time with this topic currently as I cleary didn't follow your instructions by doing a dirty flash and so on. And again... Super nice to have this rom which gives my tablet a 2nd life. Thanks a lot.
Click to expand...
Click to collapse
I don't really care about using Netflix on this device, but figured I'd let you know that I'm having the same issues after a clean flash. Will try and grab a log later.

I have this strange problem
I have two tablets SM-T813 and SM-T819.
I installed Lineage os 18.1 on SM-T813 and SM-T819 (I modified the installer). On the T813 it booted without any problems. On the T819, on the other hand, it stands in bootloop. I went into recovery and there were no files in INTERNAL STORAGE, it was empty. To T819 I need to install some file or something so that it can start reading Memory and come out of bootloop?

K-BOX2022 said:
On the T819, on the other hand, it stands in bootloop.
Click to expand...
Click to collapse
As I mentioned in the FAQ, there's nothing I can do without the T819 physically in my hands. If the T813 worked on T819, then it's a bonus. If not, it was worth a try.