Related
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!
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?
The S2 wifi blobs have now been incorporated into the Aug 25 17.1 builds.
Please take 10 minutes to read all of post #1 and #2. lpedia and I have spent 5 days troubleshooting this together and want to present our wifi findings. DO NOT USE this thread to report any other problems, it's only for exynos5433 S2 tablet wifi. If this is unreasonable, then stop reading. Thank you.
If your device's wifi is not connecting after a restart and/or wake from sleep, and/or dropping out at random, this could be because the 17.1 code is using Samsung Galaxy S6 wifi blobs instead of its stock S2 wifi blobs. This commit was made in 17.1 at
gts2: Import Galaxy S6 BCM4358 firmware · universal5433/[email protected]
@lpedia has confirmed that LineageOS 17.1 on his T710 has the wifi problems when using S6 blobs, but not after the S6 blobs have been replaced with stock S2 blobs. This appears to fix both non-connection at boot and not reconnecting on wake from sleep. Random dropouts are less common and were not seen during the limited testing, so it's not certain that they're gone.
FAQ
Q1. Will changing from S6 wifi blobs solve all my wifi no reconnect or disconnect problems?
A1. This has only been tested on the T710, and there's no guarantee it will help the other devices. If you want to try, follow the instructions below. Before you try, make sure to back up all your data. The following should write the stock S2 blobs to the /system partition only, but if you make a mistake you could lose your data! Back up first.
It's an easy test to see if the stock S2 blobs will help or not. If your current rom does not connect to wifi after a restart, try our proposed solution. Before you do, reboot your current rom 5 times in a row. After each reboot, see if your wifi connects. After you install stock S2 blobs, reboot your device again 5 times in a row and see if wifi connects. This will easily tell you if the S2 stock blobs have solved this one particular problem or not.
As for wifi not connecting after long/deep sleep, you should notice over 2 or 3 days if wifi connects or not after deep sleep.
Q2. Will this work on SM-T710, SM-T810, etc?
A2. Same answer as A1. It should work on any S2 tablet exynos5433 device that uses the S6 wifi blobs that are the default in 17.1 or Android 10. These instructions are only for exynos5433 devices.
As the thread grows bigger, you can see who is responding back with either positive or negative feedback and what model they have.
Q3. Will this work on RR, Havoc or LineageOS (Android 10 or 17.1)?
A3. The instructions below replace the S6 blobs with the original stock S2 blobs. The instructions provided should work regardless if it's Havoc, RR or LineageOS. All these variant OSes share the same repo (i.e. code and blobs) on github.
Q4. Is this post relevant to Android 9 or LineageOS 16.0?
A4. NO. The github repos show that Android 9 or LineageOS 16.0 used the stock S2 wifi blobs. This was changed to S6 wifi blobs in Android 10 or LineageOS 17.1. I don't know why it was changed to S6 blobs as I'm not involved with that change.
Q5. Why do I need my model and code name?
A5. In order to follow the instructions below, you need to know your model number and it's code name. The model number or device name is settings, about tablet.
You can find the code name at (scroll almost all the way down to the bottom)
Samsung
This is the Team Win website and the official home of TWRP! Here you will find the list of officially supported devices and instructions for installing TWRP on those devices.
twrp.me
For example, SM-T710 is gts28wifi.
Q6. Does it matter if my wifi is 2.4Ghz or 5Ghz or a mix of both?
A6. When reporting back to us, please state whether your network is 2.4Ghz only, 5Ghz only, or a mix of 2.4Ghz and 5Ghz. In addition, if its a mix, please let us know if it's one wifi network (same ssid) or two separate wifi networks. That is, 2.4Ghz is one ssid and 5Ghz is another ssid.
Q7. If this works, how will this be fixed for the next release of code and the future?
A7. If enough people say it fixes their wifi problems, I can submit a git pull request to Anan to revert the S6 wifi blobs back to S2 wifi blobs.
Instructions
1. Make sure adb debugging is enabled in developer options. To enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.
Note if you are running Magisk, see posts regarding Magisk if you cannot see rooted debugging.
2. You will need git. There are instructions and download links for installing git on Windows, MacOS, and Linux at Git Guides - install git | GitHub.
3. After you install git, follow the instructions exactly below.
Bash:
# make temporary vendor directory
mkdir temp
# cd to that directory
cd temp
# git the 16.0 stock drivers
git clone https://github.com/universal5433/proprietary_vendor_samsung -b lineage-16.0
# change directory to proprietary_vendor_samsung/<your device>/proprietary/system/vendor/etc
# or if Windows, to proprietary_vendor_samsung\<your device>\proprietary\system\vendor\etc
# where "<your device>" is your device's code, for example gts28wifi for the T710:
cd proprietary_vendor_samsung/gts28wifi/proprietary/system/vendor/etc
# start adb root
adb root
# remount /system as rw (it's read only by default)
adb remount
# start adb shell
adb shell
# delete S6 blobs from wifi directory
cd /system/vendor/etc/wifi
rm bcm*
rm nvr*
# There should be only .conf files left now
ls -al
exit
# you should be back at your desktop terminal prompt now
# now push all stock drivers to /system/vendor/etc/wifi
adb push wifi /system/vendor/etc
# check to make sure it got pushed okay
adb shell ls -al /system/vendor/etc/wifi
# now reboot Android
adb reboot
If the above does not work for you, or if it causes other problems, just reflash the last rom. That will overwrite the /system partition and everything will be restored.
If you do try this, please report back to this thread about whatever happened and include your device and what wifi network you are running.
Reserved.
Thanks for the instructions!
I had to boot my T810 (gts210wifi) into TWRP and mount /system from there before adb root and adb remount was possible. Everything else worked as described.
Observations after 5 reboots: WiFi available after reboot each time! Much better than before!
I will observe it now for a while regarding wifi-off after sleep or sporadical wifi-off.
Btw. for the random reboots of the unmodified linageos17.1 (ripee) I'm pinging my DNS-server all 2mins using Tasker. Fixed reboots since 2 month at least on my system.
Yogi555 said:
I had to boot my T810 (gts210wifi) into TWRP and mount /system from there before adb root and adb remount was possible.
Click to expand...
Click to collapse
The above might be due to you not having adb root enabled in developer options. I will update the instructions to make sure that's enabled.
Strangely the setting seems not there in my system. But I remember that in some system its available. Can the installed Magisk be the reason?
Yogi555 said:
Strangely the setting seems not there in my system.
Click to expand...
Click to collapse
It's there.
Short update: The S2 wifi blobs are a huge improvement. With S6 blobs I had reliable dropoffs at medium router-signal combined with heavy wifi-load (no dropoffs with full router signal). With the S2 blobs no single dropoff even at weak router-signal and heavy wifi-load for several hours now.
Again, to enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.
As I said earlier, the routed debugging option is missing in my developer-options (with installed Magisk). Everything else is looking identical to the attachement of post 6. But maybe we should not cover this thread with the different ways to adb root. The really important thing is that the proposed fix works really great! At least for me and hopefully for everybody else who is willing to try it
Yogi555 said:
As I said earlier, the routed debugging option is missing in my developer-options (with installed Magisk). Everything else is looking identical to the attachement of post 6. But maybe we should not cover this thread with the different ways to adb root. The really important thing is that the proposed fix works really great! At least for me and hopefully for everybody else who is willing to try it
Click to expand...
Click to collapse
Thanks, @Yogi555! It's great to know that replacing the blobs works on one of the other S2 models! We could only test it on gts28wifi (T710).
@Yogi555, about the Rooted debugging option: my T710 doesn't show that option, either, and I think it's because I have Magisk installed (@retiredtab doesn't).
If the device is not rooted, "adb root" temporarily restarts the adbd daemon on the device as root (there's a timeout period after which it will remove root access again).
I'm guessing that if the device is rooted, that isn't necessary - because adbd is probably already running as root . The Rooted debugging option is therefore unnecessary, and isn't shown.
In either case, when you do "adb root" on the PC, there should be a prompt on the device asking you if you want to allow access. Did you see the prompt? If you don't explicitly allow it, root access won't be given.
Also, "adb root" works on Windows (for an account that's in the Administrators group) without needing to be Run As Administrator, but I think Linux requires the command to be run as root (eg, sudo adb root).
Update2: after the night the T810 with S2 blobs was immediately connected to wifi this morning. Great!
Regarding "adb root" with Magisk: I'm running it from Win10 PC. Independent if normal commandline or commandline as administrator - after "adb root" there is no output at all, but a sound like connecting or disconnecting a device. After "adb remount" next, an error is displayed:
Not running as root. Try "adb root" first.
remount failed
Maybe my adb is too old (version 1.0.40)
However "adb reboot recovery" works and "adb root" then in TWRP as well. So strange, but no problem
Yogi555 said:
Update2: after the night the T810 with S2 blobs was immediately connected to wifi this morning. Great!
Regarding "adb root" with Magisk: I'm running it from Win10 PC. Independent if normal commandline or commandline as administrator - after "adb root" there is no output at all, but a sound like connecting or disconnecting a device.
Click to expand...
Click to collapse
Did you check the device to see if it's prompting you to allow this access? The prompt times out fairly quickly, so you might not see it if you don't check straight away. It does give a notification sound.
The prompting came yesterday at the very beginning of the activity and I allowed it (including the always checkbox). "adb device" shows the device id.
I don't understand why you'd see anything different from what I see. I use a Windows PC, I have Magisk (version 23.0) installed on the T710, and have previously allowed adb root access "always".
What I see is this:
Code:
> adb version
Android Debug Bridge version 1.0.41
Version 31.0.2-7242960
> adb root
adbd is already running as root
> adb remount
remount succeeded
> adb root
gts28wifi:/ #
I think there could be something wrong with your Magisk configuration. What version is it?
Downloaded adb version 1.0.41. Now I get "ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options"
Updated Magisk from 20.4 to 22.1. and App to 23.0 => No difference :-(
In Magisk App adb is not listed in Superuser-tab. Can I add it somehow?
Yogi555 said:
Downloaded adb version 1.0.41. Now I get "ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options"
Updated Magisk from 20.4 to 22.1. and App to 23.0 => No difference :-(
In Magisk App adb is not listed in Superuser-tab. Can I add it somehow?
Click to expand...
Click to collapse
I think I know what's going on now.
I've just uninstalled Magisk, and (after the enforced reboot) I can now see the "Rooted debugging" setting in Settings > System > Developer Options > Debugging.
Mine was ON, but had been hidden by Magisk's presence, as I suspected.
If you uninstall Magisk, I think you will find that your "Rooted debugging" is OFF. If so, turn it on, then try "adb root" etc. You don't need to root the device in order to use adb root functions. If you want the device to be rooted, by all means re-install Magisk - but with that setting still ON.
I'll be very interested to hear what happens.
The simplest way to check that adb root has actually given you root access is to "adb shell". The prompt will end in a "#" if the shell's running as root. As mentioned in an earlier post.
Want to also quickly confirm in here that the S2 Blobs are working real fine for me as well.
lpedia said:
I think I know what's going on now.
I've just uninstalled Magisk, and (after the enforced reboot) I can now see the "Rooted debugging" setting in Settings > System > Developer Options > Debugging.
Mine was ON, but had been hidden by Magisk's presence, as I suspected.
Click to expand...
Click to collapse
I've just re-installed Magisk and proved to myself that Magisk 23 is hiding the setting. I found that Magisk 22 didn't hide it - I re-installed using a version 22 zip that I had on hand, checked the "Rooted debugging" setting, which was still visible, then updated to Magisk 23 via the app. After the reboot, the setting had disappeared again.
I have installed the Lineageos on my oneplus 8t and the Android Auto is not working.
lineage-18.1-20210715-nightly
open_gapps-arm64-11.0-pico-20210724.zip
After flashing i have installed the Android Auto from the store. I can open it on my phone but on the car it shows that its that i should check the phone if the phone supports Andorid Auto.
Can some please help me?
Kampfwurst said:
I have installed the Lineageos on my oneplus 8t and the Android Auto is not working.
lineage-18.1-20210715-nightly
open_gapps-arm64-11.0-pico-20210724.zip
After flashing i have installed the Android Auto from the store. I can open it on my phone but on the car it shows that its that i should check the phone if the phone supports Andorid Auto.
Can some please help me?
Click to expand...
Click to collapse
Gapps problem.. search xda forum for solution..
drnightshadow said:
Gapps problem.. search xda forum for solution..
Click to expand...
Click to collapse
I have searched for hours. Can you post the solution. I thinks im not the only one with this problem. ;-)
Kampfwurst said:
I have searched for hours. Can you post the solution. I thinks im not the only one with this problem. ;-)
Click to expand...
Click to collapse
I have a similar problem and I've tried everything, including multiple USB-C cables, but my Moto Power G8 2020 phone won't connect to my Chevy Bolt EV. The infotainment screen always displays the same error message: "Connect a supported device by USB to use this feature." AA is installed on my phone and toggled on in the infotainment system. My phone is rooted, uses Open Gapps Pico for Android 11, and is running the Havoc 4.6 Android 11 Custom ROM. I can connect via Bluetooth which is OK for podcasts, but Maps won't display on the car's screen. I sure would appreciate some help to solve this problem.
I have the same problem with Project Sakura 5.1 what based on Lineage OS 18.1. I found "Android Auto for Phone Screens" what I could start manually and that found my car manufacturer, but doesn't connect to it.
Kampfwurst said:
I have searched for hours. Can you post the solution. I thinks im not the only one with this problem. ;-)
Click to expand...
Click to collapse
I think that we need the OpenGapps stock / super for Android 11, but that didn't released until now or we must use NikGapps (https://sourceforge.net/projects/ni....1-full-arm64-11-20210725-signed.zip/download).
@drnightshadow Is this right?
hkalman said:
I think that we need the OpenGapps stock / super for Android 11, but that didn't released until now or we must use NikGapps (https://sourceforge.net/projects/ni....1-full-arm64-11-20210725-signed.zip/download).
@drnightshadow Is this right?
Click to expand...
Click to collapse
Yap, you're right. Clean flash highly recommended!
drnightshadow said:
Yap, you're right. Clean flash highly recommended!
Click to expand...
Click to collapse
Clean flash with which Gapps??
ok
For anyone having problems with OpenGapps and Android auto, try this, it's a matter of placing the android auto apk into the right place, I've had android auto stub apk updated from Play Store (bc opengapps's one contains the bare minimum code to connect to car which won't work) and still didn't work
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
jhford said:
Clean flash with which Gapps??
Click to expand...
Click to collapse
Nik Gapps. However LineageOS suggest MindTheGapps for 18.1 versions
nicosafull said:
For anyone having problems with OpenGapps and Android auto, try this, it's a matter of placing the android auto apk into the right place, I've had android auto stub apk updated from Play Store (bc opengapps's one contains the bare minimum code to connect to car which won't work) and still didn't work
Nik Gapps. However LineageOS suggest MindTheGapps for 18.1 versions
Click to expand...
Click to collapse
Nope. The new OGApps packages pico/nano for A11 already take account of the requirement, that the stub has to be placed in system/priv-app folder.
What happens after flashing pico/nano and connecting it to the head unit of the car is this:
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
Questions? Use Q&A! Please read the FAQ before reporting any bugs or errors! If you post in the main thread not having read the FAQ or error message itself, not included a debug log when reporting a malfuction or reporting a Force Closure without...
forum.xda-developers.com
And in the latest AA build, the following error message shows up which proves that the stub app (or something else in the installation process) is broken:
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
Questions? Use Q&A! Please read the FAQ before reporting any bugs or errors! If you post in the main thread not having read the FAQ or error message itself, not included a debug log when reporting a malfuction or reporting a Force Closure without...
forum.xda-developers.com
@Kampfwurst:
All I know is, that this problem is not device specific an you're not the only one who is affected by this. On my dipper it's exactly the same...
Do you have Telegram?
Update - forget what I wrote above about what was taken into account by the OGApps Team.
They knew what they had to do, but made a mistake and didn't do it right. The priv-app-folder-thing is in deed the cause of all trouble with AA in the new OGApps builds with the included stub app.
The fix is coming soon as you can see here:
Fix gearheadstub by moving it to priv-app (!49) · Merge requests · OpenGApps / all · GitLab
Architecture-independent sources for OpenGApps https://opengapps.org
gitlab.opengapps.org
So all please just w8 a few days and do no wipes/clean flashes! It's not necessary!
G A S T said:
Nope. The new OGApps packages pico/nano for A11 already take account of the requirement, that the stub has to be placed in system/priv-app folder.
What happens after flashing pico/nano and connecting it to the head unit of the car is this:
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
Questions? Use Q&A! Please read the FAQ before reporting any bugs or errors! If you post in the main thread not having read the FAQ or error message itself, not included a debug log when reporting a malfuction or reporting a Force Closure without...
forum.xda-developers.com
And in the latest AA build, the following error message shows up which proves that the stub app (or something else in the installation process) is broken:
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
Questions? Use Q&A! Please read the FAQ before reporting any bugs or errors! If you post in the main thread not having read the FAQ or error message itself, not included a debug log when reporting a malfuction or reporting a Force Closure without...
forum.xda-developers.com
@Kampfwurst:
All I know is, that this problem is not device specific an you're not the only one who is affected by this. On my dipper it's exactly the same...
Do you have Telegram?
Click to expand...
Click to collapse
I've seen that AA bundle is just bad/incomplete, I don't get any USB connection switch as I monitor it's always on "transfer data", I've also seen that MindTheGapps bundle works I just flashed it over OGapps pico version, gonna try later to see if it works or not but I highly doubt it
nicosafull said:
I've seen that AA bundle is just bad/incomplete, I don't get any USB connection switch as I monitor it's always on "transfer data", I've also seen that MindTheGapps bundle works I just flashed it over OGapps pico version, gonna try later to see if it works or not but I highly doubt it
Click to expand...
Click to collapse
Pls recognize my update at the end.
Everything will be all right in the next days.
G A S T said:
Pls recognize my update at the end.
Everything will be all right in the next days.
Click to expand...
Click to collapse
yeah, they've merged the change about 50' ago, and a new version was just released 10 hours ago, so I don't know if it's fixed there or not as it's difficult (at least for me) to track a changelog on each versions
nicosafull said:
yeah, they've merged the change about 50' ago, and a new version was just released 10 hours ago, so I don't know if it's fixed there or not as it's difficult (at least for me) to track a changelog on each versions
Click to expand...
Click to collapse
It is definately not fixed yet in the existing builds, but it will be fixed in the builds of the next days, probably with the one on friday.
nicosafull said:
I've seen that AA bundle is just bad/incomplete, I don't get any USB connection switch as I monitor it's always on "transfer data", I've also seen that MindTheGapps bundle works I just flashed it over OGapps pico version, gonna try later to see if it works or not but I highly doubt it
Click to expand...
Click to collapse
I can confirm this, flashing MindTheGapps over OGapps fixes AA, having it working now
Kampfwurst said:
I have installed the Lineageos on my oneplus 8t and the Android Auto is not working.
lineage-18.1-20210715-nightly
open_gapps-arm64-11.0-pico-20210724.zip
After flashing i have installed the Android Auto from the store. I can open it on my phone but on the car it shows that its that i should check the phone if the phone supports Andorid Auto.
Can some please help me?
Click to expand...
Click to collapse
I have AA working fine on an Android 11 AOSP-based GSI rom (I use CAOS11, on a Blackview BV9600E, Mediatek 6771).
Since AA comes as a system app in Android 11 (no need to flash an app) it may be that the problem is with Lineage-18 OS, if it does not include AA as a system app? Try an AOSP Android 11 rom and it should work.
Update: I have now installed an Lineage-based Android 11 GSI called LiR from the same dev as CAOS11, with GApps included - that seems to work also. It may be the vanilla versions of Lineage-OS 18 that throw problems because they don't have the AA stub.
With LineageOS 18.1, I couldn't SEE and Launch AA at all. after multiple attempts.
I am running 14th August update on Lenovo Z6 Pro.
after the AA installation, the "Open" button is disabled and failed to locate AA icon in the app drawer.
however it appears in the list under Apps and Notifications.
"Everything will be working in a few days", it's been several months now and this problem is very much still here. I've tried MindTheGapps, NikGapps, as well as OpenGapps (full, stock and super). All to no avail. I attempted the "unisntall all android auto from system" (essentially from ADB), and copy an apk to a system folder, reinstall from the play store...
Nothing.
LineasgeOS 18.1 on Sony Xperia XZ1 Compact.
Mod edit - translated by https://www.deepl.com/translator
Have the same problem with lineage 18.1 or 19.1 it does not work Message USB is read more not
*******************************
Habe das gleiche Problem mit lineage 18.1 oder 19.1 geht es nicht Meldung USB wird gelesen mehr nicht
LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T710 ONLYModel: SM-T710 (wifi) - gts28wifi - 8" screen, Exynos 5433 SoC, no LTE
This is the ONLY model that the ROM will work on.
There is NO ROM for the T715 or T815 in this thread. Questions about T715 or T815 will be completely IGNORED.
You MUST READ posts 1-4 (about 10 minute read) before deciding to install this rom. If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
DISCLAIMER
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.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
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. DRM level 3 (SD definition)
10. deep sleep
What doesn't work
1. fingerprint. As I wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
I will not spend anymore time looking at fingerprint. If you need fingerpint to work, stay with stock Samsung rom.
2. DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your $treaming media, stay with stock Samsung rom.
3. If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems such as the touch screen not working.
4. Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
1. LineageOS team for source code.
2. @retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin for spending nearing 1 month fixing the 2 most biggest bugs in 17.1 that plagued users for nearly 10 months: the wifi instability and random reboots. These are discussed in detail at
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308193/
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308203/
3. All past contributors of the exynos5433 code.
4. @rINanDO for his lmkd spam fix in 18.1.
5. beta testers: lpedia, Yogi555 and CuckooPenguin
6. lpedia for building the public T710 monthly roms starting April 2022
7. lpedia for suggestions, proof reading and FAQ table format in post #2.
Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. Can I build this ROM for myself? Where are the source and kernel source files?A1. Yes, you can. The source files are listed below.
Kernel
https://github.com/retiredtab/android_kernel_samsung_universal5433-selinux
Device Tree
https://github.com/retiredtab/android_device_samsung_gts2-common-selinux
https://github.com/retiredtab/android_device_samsung_gts28wifi
Vendor
https://github.com/retiredtab/proprietary_vendor_samsung-selinux
In addition, there is a repo diff file for device-specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself. The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5eQ2. Is this ROM suitable as a daily driver?A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since mid August 2021 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. You MUST use my unofficial TWRP 3.5.2_9. Get it from
https://sourceforge.net/projects/retiredtab/files/SM-T710/TWRP/Q6. Why should I use this ROM?A6. You don't have to! If you don't like it, go back to your old ROM.Q7. Will you offer monthly updates with security patches?A7. We plan to do so. lpedia will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be tested to make sure all the "What's working" functionality listed in post #1 still works, before it's made available (which might in some cases delay the release).Q8. I'm a newbie. Can you provide step by step instructions?A8. We simply don't have the time to do this, but there are lots of tutorials, videos, etc online showing how to flash custom ROMs and how to deal with common problems. Newbie questions are also accepted in the XDA General Questions and Answers forum. Having said that, @pflyaz has kindly make a guide in post #37.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.
Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password.
To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
Q10. How long will you build 18.1 for this device?A10. For now, 18.1 will be built for all of 2022. After that, we will make a decision depending on a number of factors.Q11. Do I need to erase everything and format my data before installing this ROM for the first time?A11. Under most circumstances, yes.
If you're coming from stock Samsung Android, or an earlier version of LineageOS, or a different custom ROM, you MUST 'clean flash': boot to TWRP recovery, wipe system, data, dalvik/art cache, and cache partitions, then Format Data, then install this ROM.
If you don't do this you're likely to run into problems, such as getting stuck at the boot animation for more than 5 minutes.
The ONLY exception is that if you are coming from LOS 18.1 with the April 5 2022 security patch or later, you can dirty flash the latest security patch build.Q12. What Gapps should I use?A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, OpenGapps, and MindTheGapps. OpenGapps is being removed as per post #11. Do your own research as to what is the most reliable gapps option for you.
I recommend installing the SMALLEST version of any of these, preferably with just the minimum Google services needed to access the Play Store and run apps that depend on Google services.
You could also consider Google alternatives, such as Aurora Store, which mirrors the Google Play Store apps but doesn't need any Google services itself. Many Play Store apps do not actually depend on Google services.
If you are going to install any Gapps package, follow the installation instructions given for that particular package.Q13. I'm having problems with Gapps. Can you tell me why it's not working?A13. I can't answer any questions about Gapps, because I don't use them. Ask your questions on the XDA thread for the Gapps package you're using.Q14. Why isn't my post answered?A14. There are several possible reasons: the question is answered in the FAQ (in which case it will be ignored completely); or it involves apps or operating systems that I don't use; or it's about Gapps, which I don't use; or I simply have not had time to answer any questions.Q15. What speed up/optimization tips do you suggest?A15. These steps can make a big difference to performance:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
Q16. Does this ROM support Magisk so I can root my device?A16. Magisk works with this ROM as reported by beta testsers, but that could change with any revision and changes by Google. However I don't use it myself and can't help with any related issues. Direct any questions about Magisk to the XDA Magisk forum.Q17. Will this ROM ever become official?A17. Never. Official maintainers have onerous responsibilities, and I know my device trees, code organization and git commits will NOT meet LineageOS standards. I'm not able or willing to take on the responsibilities and commit the extra time to supporting an official build.Q18. What is the difference between this ROM and others?A18. This ROM tries to be pure LineageOS with little or no modification. Other ROMs may come with a different UI, different bundled apps, etc.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 slight tweaking to the SEpolicy, small bug fixes and minor code cleanup, but all the hard work - getting the rom up and running, and fixing all the major bugs - has been done. This doesn't mean the code is perfect or well organized, but I won't be making any major changes.Q20. Why did you fork the trees?A20. I wanted my own private branch where I could make changes that would only affect my own personal builds.Q21. Can you build a variant of this device? For example, a LTE or S-pen version?A21. I cannot and will not try to build for a variant device if I don't physically have that device. I have to be able to boot and test it myself, and there's no guarantee that I can get those variant features working. So I will NEVER build T715, T810 and T815.Q22. Can I load this ROM on a variant device like LTE or S-pen version?A22. This ROM is for the device explicitly listed and will only work on that device. Do not try to install it on any other device.
ONLY if you are an advanced user and understand TWRP, adb, odin, heimdall, etc, you could try loading it on a LTE or S-pen variant by modifying the updater-script, but be warned: there are likely to be problems, including a bricked device, bootloops, or the ROM not being able to support the functionality of LTE/S-pen.Q23. Does this ROM have any wifi connection issues?A23. This ROM's wifi has been stable on the specified device ever since lpedia and I determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1.Q24. Is this ROM secure so I can do financial transactions?A24. Although Android monthly security patches do improve general security, this ROM's outdated kernel and old proprietary vendor blobs/drivers will NEVER get updates of any kind, and could have significant security holes.
In addition, although the ROM is SElinux enforcing, there's a good chance that the rules written (about 800+ lines of code) have some errors.
If the device is rooted, this would further weaken the security.
With this information, it's up to you to make an informed decision about whether you trust this ROM to be secure enough for your financial transactions.Q25. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the BETA rom?A25. Downloads are at
https://sourceforge.net/projects/lpedia-sf/files/gts28wifi/
Monthly release notes
June 10, 2023 release notes
1. Incorporates June 5 as per https://review.lineageos.org/q/topic:R_asb_2023-06
May 8, 2023 release notes
1. Incorporates May 5 as per https://review.lineageos.org/q/topic:R_asb_2023-05
Apr 18, 2023 release notes
1. Incorporates Apr 5 as per https://review.lineageos.org/q/topic:R_asb_2023-04
March 19, 2023 release notes
1. Incorporates Feb 5 and Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02 and https://review.lineageos.org/q/topic:R_asb_2023-03
Jan 8, 2023 release notes
1. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
Dec 12 release notes
1. Incorporates Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
Nov 12 release notes
1. Incorporates Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
Oct 9 release notes
1. Incorporates Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
Sept 11 release notes
1. Incorporates Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Fixes non working touchscreen and hardware buttons when powering up with power cable plugged in and device turned off. However, the recommendation is still to unplug your charger, wait 30 seconds before pressing power button when your device is turned off.
https://github.com/retiredtab/andro...mmit/7e0657629efedc7f06f6f6fb57199fca0b4e8ea6
https://github.com/retiredtab/andro...mmit/e17c44d2e282d67b243a1c99ce62127e83052c4f
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/6db8e690141a98e5cf9e6952c3572c127c0cf8ea
Aug 10 release notes
1. Incorporates Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Fixes saving of color profile in live display during a reboot/shutdown.
https://github.com/retiredtab/andro...mmit/01b1ed6ba8c268a19762031415fde1b4e45d4ac3
3. Fixes offline battery charging by writing rules to allow charger to access certain files. This removes the previous workaround. Thanks to @simon-edwards for providing an adb logcat that showed the denials.
https://github.com/retiredtab/andro...mmit/041ae45960170e68410b059f4f709e9c14b79a99
July 23, 2022
1. Added argosd to improve wifi throughput as per https://github.com/retiredtab/andro...mmit/c181aa0c5192e46a5a03d4451e2648481a520c0f
2. Incorporates July 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
3. Incorporates a workaround for offline charging.
https://github.com/retiredtab/andro...mmit/9d019f0a3be789850a9add18d042990631f05b44
Previously, if the device was off and you plugged in a charger, it would show a battery icon and this would display indefinitely giving no sign of charging animation. With this workaround, the battery icon is displayed for a few seconds and then a white circle with a charge symbol inside it is shown to indicate it's charging.
After a few seconds, the screen will go blank and continue charging. The side effect of this workaround is that in order to turn on the device, you first must unplug the charger and then turn on your device. If you try to turn on the device with the charger cable plugged in, it won't turn on.
June 12, 2022
1. Removed vibrator code from gts2-common as wifi only models don't have vibrator motor (only LTE models).
https://github.com/retiredtab/andro...mmit/e54aee73a98e3cef6e74f96c1815cec9c82ff10d
https://github.com/retiredtab/andro...mmit/dd846b06378182398c55b57b2edc2537369bd509
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
May 12, 2022
1. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
2. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
April 11, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T710 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ.
Reserved.
Initial public build called lineage-18.1-20220411-UNOFFICIAL-gts28wifi.zip. The sha256sum file is provided as well to ensure integrity of download.
lpedia has 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.
April 11, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T710 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ Q11.
Congratulations on the awesome release!
New build called lineage-18.1-20220512-UNOFFICIAL-gts28wifi.zip
lpedia has 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.
May 12, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already
2. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
3. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
4. If you are upgrading from the April 11 build, you may dirty flash the May 10 build. If you are NOT coming from the April 11th, 2022 build, you MUST BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA. You cannot dirty flash at all. See FAQ Q11.
Hi there, thanks for your ROM. I would like to report a bug with using it.
May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".
All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."
I've included my logcat, if you need more info or another reproduction please let me know.
Thanks!
Kim
kimrosebush said:
Hi there, thanks for your ROM. I would like to report a bug with using it.
May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".
All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."
I've included my logcat, if you need more info or another reproduction please let me know.
Thanks!
Kim
Click to expand...
Click to collapse
Hi, @kimrosebush. Thank you for sending a logcat.
This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:
Code:
05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.
A few questions about the process you followed:
1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?
2. Did you install the correct version of TWRP (see Q5 in the FAQ)?
3. When you say "All factory resetted through TWRP", what did you actually do?
4. When did you install the gapps package? Just after the ROM, before first boot?
Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]
lpedia said:
Hi, @kimrosebush. Thank you for sending a logcat.
This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:
Code:
05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.
A few questions about the process you followed:
1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?
2. Did you install the correct version of TWRP (see Q5 in the FAQ)?
3. When you say "All factory resetted through TWRP", what did you actually do?
4. When did you install the gapps package? Just after the ROM, before first boot?
Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]
Click to expand...
Click to collapse
Hey @lpedia thanks for the reply.
1. LineageOS 17.1 I believe was the build.
2. Yes I installed the provided version.
3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.
4. Just after the ROM.
I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.
Thanks for the hint in the right direction. Am glad to be on Android 11 now.
Kind Regards,
Kim
I will be removing opengapps from the FAQ because for several months now (starting around Oct 2021), the opengapps project has been releasing UNTESTED builds that results in bootloops or non working gapps services. Despite numerous requests/posts from the community to slow down the releases and actually TEST THEM BEFORE release, the latest May 3, 2022 shows there is still room for improvement.
This thread in the opengapps forum is just the latest example. Details of UNTESTED builds are also in the same megathread below.
https://forum.xda-developers.com/t/...rsions-devices.3098071/page-367#post-86885091
It's also shown up in other roms like
https://forum.xda-developers.com/t/...7-1-04-30-2022.3937956/page-100#post-86885353
This would be a good time for user to do their own research on which gapps is best for them or use NONE at all. I use Aurora Store myself.
Just a reminder that the builds we release are TESTED and verified to have all the functionality as listed in post #1.
kimrosebush said:
Hey @lpedia thanks for the reply.
1. LineageOS 17.1 I believe was the build.
2. Yes I installed the provided version.
3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.
4. Just after the ROM.
I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.
Thanks for the hint in the right direction. Am glad to be on Android 11 now.
Kind Regards,
Kim
Click to expand...
Click to collapse
Good to hear!
Note that you don't have to be quite so brutal about wiping absolutely everything for a 'clean' flash. I manually wipe Dalvik / ART Cache, Cache, and System, and then Format Data. I have never reformatted the SD.
If you have any further trouble, I suggest you try starting again with a clean flash and a different gapps package, or try doing without any gapps, as @retiredtab has recommended in the post above.
In my experience, some gapps packages, or sometimes just a particular version of a gapps package, don't work with some ROMs. I have not tried opengapps, but I can confirm that BiTGApps-arm-11.0.0-R45_signed.zip does work on my T710 with this particular ROM version.
I personally like BiTGapps because it installs only the bare minimum needed (Google services and Play Store; doesn't even automatically run Google Setup) and doesn't have to be installed before first boot. So it's possible to install LOS, boot the system, make sure everything's working, then go back into TWRP and install gapps. If any problems turn up, this approach also makes it easier to tell whether it's something to do with LOS or with gapps.
You could also try running LOS without any gapps, and if you decide you want gapps after all, install BiTGapps without having to clean-flash and start again.
I just installed this rom two days ago. It has been working great. Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message. Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Would you have any idea what is going on or how I should deal with this?
Thanks,
MC
Dr_MC said:
Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message.
Click to expand...
Click to collapse
On April 6, @lpedia and I had a PM discussion about signing builds.
lpedia wrote
Code:
"About signing builds ... an issue with just using the default test-keys signature is that someone can easily create
their own builds and pass them off as someone else's, possibly adding malicious or just plain bad code, and their
package would look just like the original."
I replied
Code:
"For our purposes, maybe we should just include the sha256sum and recommend that the users verify
them to ensure the file downloaded correctly and it wasn't modified?"
To get stop seeing that trust message, goto settings, privacy, trust, turn off build signature.
Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Click to expand...
Click to collapse
I can't see the Crave app in Aurora Store. I use the app devcheck to check for root access and the screenshot clearly shows it's not rooted.
There's nothing in my code to enable root. In fact, I don't even want root on my devices.
For Crave, you can try using Magisk and it's hide root function to see if that will fool Crave into thinking the device is not rooted.
Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted.
Click to expand...
Click to collapse
I did installed the above root checker app and got the same message. That is, the T710 rom, by default is NOT rooted. I don't know why Crave would say it's rooted.
I believe root checker's main function is to verify that your rom is "rooted" so when it says "root access is not properly installed.", it's trying to tell you that your attempt to use Magisk or similar type app to root the rom was unsuccessful.
BTW, you are better off using devcheck as it's an excellent ad-free utility that I use on a regular basis to help develop this rom vs the ad-infested root checker app. While devcheck isn't open source, it's written by flar2 who is a xda member here.
Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted.
Click to expand...
Click to collapse
Root Checker Basic says "Sorry! Root access is not properly installed on this device" when asked to confirm root status on an unrooted device. So as far as that app's concerned, it just means "I can't confirm it's rooted". Which is to be expected if it isn't rooted and you haven't even tried to root it.
If that isn't the app you're using, see if you can find out what it means to your particular root-checker app.
Dr_MC said:
Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Click to expand...
Click to collapse
Did the CRAVE app work on this device when it had the stock Samsung ROM? Do you have to register devices to receive this service? If so, might it need to be re-registered? Because its device ID will have changed.
Thanks for suggesting devcheck. It says I'm unrooted. Perhaps Crave noticed the unlocked bootloader or the custom ROM.
It did work with stock. It was registered, twice in fact. I deleted both, registered it again. The ap still says I'm rooted. Oh well, that's ok, I can use crave through a browser.
BTW do you know where I can find the stock keyboard?
Thanks
Dr_MC said:
BTW do you know where I can find the stock keyboard?
Click to expand...
Click to collapse
If you mean the Samsung keyboard - sorry, no, I don't. I switched to a different keyboard years ago. Google's GBoard has similar functionality, I think. MS SwiftKey is OK, too - has the best (most relevant) suggested text of any of the keyboards I've tried.
ROM working fine for me after trial and error with various gapps. FWIW I ran into the "just a sec " with opengapps. I finally had some joy by flashing the rom, but not gapps. Boot the ROM and completely setup it up Lineage. Then I restarted and flashed open gapps. When I rebooted everything came uo fine and has been solid eversince. Kudos your you gentlemen for fixing the Wifi ! Its been nice to have it work stably.