Database Develop

Magisk Manager Has Stopped. (Crashing on open)

Phone: LG Aristo (LGMS210)
ROM / Android version: Android 7.0
Root (yes/no): Yes
Xposed, or any other modifications: no
Any physical damage prior to defect: no
Magisk Manager keeps stopping. I opened it today and I got the message "Magisk Manager has stopped, open app again" I can't open it without it crashing. I've tried clearing cache, clearing data, reinstalling the APK. What do I do? This is a very big problem as i cannot run any rooted apps without getting the message that magisk has stopped.

Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?

Have you tried uninstalling Magisk and then reinstalling?[/QUOTE]
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.

MMJv3 said:
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.
Click to expand...
Click to collapse
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?

I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,

dafreaking said:
I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,
Click to expand...
Click to collapse
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.

Clear Repo Cache
Disconnect from internet, go to settings and clear the repo cache helped me to open it again

Didgeridoohan said:
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?
Click to expand...
Click to collapse
I am facing the same issue. Magisk Manager crashes as soon as I open it (precisely within 3-5 sec of opening the app). Though the root is working perfectly and all apps requiring root behave as intended.
I am attaching a magisk log taken from the magisk manager within the 3-5 seconds window.
Kindly let me know if it's the correct log. I am a noob and still learning the intricacies.
Any help/guidance will be greatly appreciated

Magisk Manager works for me when I wait for a few seconds after opening the app. Cool Tool shows high CPU activity right after starting MM. Once the CPU idles again, MM works without crashing.
This is not a fix, but it may help until a new version gets released.

Didgeridoohan said:
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.
Click to expand...
Click to collapse
v5.8.0 just released does fix this.

Didgeridoohan said:
Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?
Click to expand...
Click to collapse
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader

zfk110 said:
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader
Click to expand...
Click to collapse
I encounter the same issue today !!

eric672913 said:
I encounter the same issue today !!
Click to expand...
Click to collapse
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5

zfk110 said:
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5
Click to expand...
Click to collapse
Great! Thanks a lot.

For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.

JoostA said:
For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.
Click to expand...
Click to collapse
Thanks for this! Was exactly my problem.

Phone: Sony Xperia Z3 Compact (D5803)
ROM / Android version: Android 7.1.2 (LineageOS)
Root (yes/no): Yes
Xposed, or any other modifications: AFwall+ 3.0.4 (IPv6 disabled)
Any physical damage prior to defect: no
After flashing new LineageOS + Magisk.zip and installing the Magisk Manager Apk, the app is also crashing with no internet connection for me. But if I make airplane mode on, then it does work for me.

Magisk not opening or crashing again and again.
First of all desable or uninstall your superuser app and then open magisk manager app again it's very simple. When you done all of magisk installation then you can again activate or install your superuser app.
If it is not working then please tell me i can help you.

Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?

Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing SOLVED
jhavron said:
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?
Click to expand...
Click to collapse
Updated Magisk Manager and was able to download the updated apk using the manager. I then rebooted to recovery and installed the new APK, cleared delvik, & cache, rebooted. Bam! SOLVED

[ROM][Pie] Unofficial LineageOS 16.0

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Android Auto and Lineage 18.1 Oneplus 8t

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

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

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

Reserved.

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

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

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

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

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

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

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

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

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

Phone permission needed to take calls.

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

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

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

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

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