Related
Maybe this is a very stupid question but I really have no idea why this problem occurs
My phone (HTC One S Ville mit Resurrection Remix (Android 5.1)) worked perfectly fine until last Friday.
At this date a new update of Telegram Messenger was released. I installed it and while installation of this app my phone did a restart and got stuck in a bootloop.
I restored using TWRP and retried - same problem. I also deleted the app and its data to do a fresh install - bootloop after installation.
Furthermore I noticed the exactly same behavior for the last update of WiGLE. All other apps could be updated to their latest versions without problems.
I used Google Play to update these apps.
What could be a problem for that? Is android just too old to these apps or could there be a collision with something installed on my phone/the ROM? How can I debug this?
I am not an android expert and I am very thankful for any kind of help :')
Thank you! =)
Same Problem with LG G2 mini / Android 6
Hello,
I'm facing the similar problems since a few days. Running Resurrection 6.0.1 on LG G2 Mini.
It started with installing maxdome-app at thursday, last week. Phone went into bootloop.
Wiping and or deinstalling the app in safe-mode did not work. So I restored to an older backup. This worked some time but ran into bootloop after a while ( I do not know what I've done exactly to get into this, this time).
I tried around a little. One part was a fresh install of cyanogenmod 13. This worked some time and I could find out that installing telegramm messenger had the bootloop-effect repeatable.
Sorry for not giving any help to the thread-creator but I hope we can give any more information to each other or anyone else can help?
Right now I am installing apps and backing up all the time to get some half-working system, but better ideas would be appreciated
Good to know that I am not alone
I figured out that there are a few more apps causing the bootloop. Here is a list:
WiGLE Wardriving
Telegram Messenger
pr0gramm.com app
Playstore Changelog (XPosed Module)
Statusbar Download Progress (XPosed Module)
Maxdome
I already updated Xposed Framework, Google Play Services and Google WebView to prevent incompatibilities. Problem still exists.
I updated everything as far as possible and made a backup using TWRP so I can restore my OS at any point. Further you could backup your apps using Titanium Backup. I it worth its price!
I started facing a similar problem of app updates causing bootloops on my device which was running CandySix ROM / 6.0.1. Apps causing bootlooping included Greenify and Nova Launcher. I had another device which has a factory 6.0.1 ROM rooted with Xposed and that device didn't have bootloop issues with these same versions of apps. Fortunately I was able to update the first device to a LineageOS 14.1 7.1.2 ROM and once again continue using the latest version of apps without bootlooping issues - but I never did understand exactly what was causing the bootlooping problem. That was a rather frustrating experience.
When the first bootloop happened, I was updating one single app, so I knew it was probably the one I should roll back to the previous version to fix the problem - so I didn't have to resort to a full TWRP restore.
How did you do a rollback of an app while you are in a bootloop? I would be glad to know that
Unfortunately my Device One S Ville does not get any updates anymore
In my case I can boot to custom recovery/TWRP to delete the app apk from the its /data/app folder - which basically prevents it from running when I reboot the phone. I also use an apk extractor app to save the apk of all apps I install and I also use Titanium Backup - so between those two I have copies of the older apk versions to install. You can also find older apk versions on apkmirror.com.
Depending on the severity of the bootloop, you can also connect your phone to a PC and use adb to disable/uninstall the app causing the problem if you know which one it is.
-kw said:
How did you do a rollback of an app while you are in a bootloop? I would be glad to know that
Unfortunately my Device One S Ville does not get any updates anymore
Click to expand...
Click to collapse
Thank you for your explanation! This sounds a bit more stressful to me than rather restore via TWRP but could me more time efficient for larger ROMs. I will keep this in mind
Thanks and can confirm that deleting the app folder/apk via twrp can help. I got back into my android 6 again. For me seems more that DavDroid caused it (but Telegram was suspicious, too).
DavDroid mentioned in the last update on 4th November, that they released a workaround against crash and bootloops on some custom roms
Depending on how old your TWRP backup is, restoring from TWRP is an option. But often I have not made a backup in a while or made many recent changes that I didn't want to lose, so the other ways I suggested are more time efficient in some cases.
-kw said:
Thank you for your explanation! This sounds a bit more stressful to me than rather restore via TWRP but could me more time efficient for larger ROMs. I will keep this in mind
Click to expand...
Click to collapse
Upgrade to Android 7
I can add EDS app to the non-working programs.
As far as I could install Telegram (same Version) by downloading .apk I suspect the problem is something depending with playstore. This would explain the many affected apps. But of course I don't know it for sure.
Inspired from divineBliss I upgraded to Android 7 (LineageOS 14.1) and could install everything as I wanted without problems so far. Thanks for that. Looks good, but I will wait some days after I'm convinced.
@-kw: did you try the following link for upgrading to higher android-version?
https://forum.xda-developers.com/htc-one-s/development/7-1-lineage14-1-htc-one-s-ville-t3540981
Glad you were able to update ROMs and escape the bootlooping problem
I have been running LineageOS 14.1 for about a month now without any bootlooping issues due to app updates - so I expect you won't have any issues. I did cause some dread time consuming to resolve bootlooping due to some bad substratum themes, but that's a different issue altogether .
michibr said:
I can add EDS app to the non-working programs.
As far as I could install Telegram (same Version) by downloading .apk I suspect the problem is something depending with playstore. This would explain the many affected apps. But of course I don't know it for sure.
Inspired from divineBliss I upgraded to Android 7 (LineageOS 14.1) and could install everything as I wanted without problems so far. Thanks for that. Looks good, but I will wait some days after I'm convinced.
@-kw: did you try the following link for upgrading to higher android-version?
https://forum.xda-developers.com/htc-one-s/development/7-1-lineage14-1-htc-one-s-ville-t3540981
Click to expand...
Click to collapse
@michibr:
I am very pleased with my Resurrection ROM; but this is stuck on Android 5.1. I will give a new ROM a try when I have the time for that
At this time it seems like this is the only solution of escaping the bootloop-problem
FYI
I updated to Android 7.1 RR and now I can update all my Apps without problems
I am sorry that this is the only solution I can provide, but still better than nothing
Hi all,
I'm having exactly the same problem, it all started with FB, then some other apps.
I had to reboot into Safe Mode to uninstall those apps.
I'm running on cm12.1 and I have my own reason not to upgrade to higher Android.
Am hoping someone can come out with a solution.
For now, here's my list of apps:
- Facebook (Facebook Lite is fine)
- Telegram
- Bluemail
- Local telco app
I am sorry to inform you that I did a lot of research and was not able to find any other solution than upgrading to a higher android.
The problem is with appt2 someone reported it in google's issue tracker and someone from goole descriped it in detail here's it :-
CyanogenMod has this function getPkgName (https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/libs/androidfw/AssetManager.cpp). It creates a ResXMLTree on the stack and points it at a buffer from an asset without making a copy. Then it closes the asset before the ResXMLTree is destroyed.
For apps built by aapt, this is benign. However, aapt2 produces UTF-8 string pools, which cause the ResXMLTree's ResStringPool(mStrings)'s mCache to become non-null in ResStringPool::stringAt (https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/libs/androidfw/ResourceTypes.cpp). Then ResStringPool::uninit dereferences mHeader (which is now dangling), and a crash ensues.
This crash shows up in different ways. On one Cyanogen OS device, the launcher crashes when an app built with aapt2 has been installed, but only if the manifest is large (probably due to how deallocation happens for small vs large blobs). On another device, system_server crashes at boot if an aapt2-built app is installed.
We're attempting to work around this with a custom build of aapt2 that always produces a UTF-16 string pool for the manifest. Results so far are promising.
Can this be patched somehow at the OS via xposed for all of the roms that won't get updated?
The fix for this issue is available here (CM13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM12.1:
The fix for this issue is available here (12.1):
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Is this .zip patch for any device with any Lollipop 5.1.1 ROM?
Because I just installed it and my HTC one X with Resurrection Remix ROM (Lollipop 5.1.1) goes black after the HTC logo.
lescht said:
The fix for this issue is available here (CM13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM12.1:
The fix for this issue is available here (12.1):
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Click to expand...
Click to collapse
Hello what is about cm11 kitkat 4.4.4 sameissue but no fix-
could anyone make a fix? Please help.
Hello Guys,
I come in need of a help,
I'm writing from my computer now,
Yesterday my phone was working fine,
Today morning, I updated the apps on my phone; amongst the updates was android system webview.
After a reboot, my phone is unresponsive, it won't open any of the apps from that point.
I reboot again, since keyboard doesn't work, I used the OTG cable to use the physical keyboard to enter the password and get in. Tried entering setting to uninstall that crap app, settings is unresponsive.
No SIM services, no keyboard, no fingerprint, no settings etc.. basically nothing works and everything says "unresponsive and asks to either wait or close".
The only thing I have now is TWRP Recovery, and I'm inside it now.
I've wiped Cache + Dalvik / ART Cache : Result still same, nothing works.
I mailed [email protected] (which is provided in the app's "Developer" section) about this and got a reply that the mail is no longer being monitored.
Can someone please let me know how I can remove android system webview by using TWRP ? So that I can enter the phone back again as normal..
Device Details:
Lenovo K8 Note
Android 7.1.1 Nougat, (Never updated the OS)
Device has been rooted and has recovery options.
I think you can find WebView module in Magisk respiratory so I suggest you give that a try. Flash it and I think it will be fine as long as you have Magisk installed, of course.
dedq said:
I think you can find WebView module in Magisk respiratory so I suggest you give that a try. Flash it and I think it will be fine as long as you have Magisk installed, of course.
Click to expand...
Click to collapse
Thanks, I couldn't quite understand that..
I've never read/seen a need for Magisk so far.. so may I know what is the procedure to be done here...?
I do read Magisk is a systemless Root, (I already have SuperSu, is that the same functionality? (though I can't open anything that is))
Find the Magisk zip on Google and flash it over TWRP.
Head over to the Magisk module site and you will be able to find an alternate WebView module you can flash. It will be in zip format so I guess you will need USB to transfer those files to your phone since you cannot use it to download modules.
dedq said:
Find the Magisk zip on Google and flash it over TWRP.
Head over to the Magisk module site and you will be able to find an alternate WebView module you can flash. It will be in zip format so I guess you will need USB to transfer those files to your phone since you cannot use it to download modules.
Click to expand...
Click to collapse
Understood, thanks..
Will try this out.
KillerBeeSama said:
Understood, thanks..
Will try this out.
Click to expand...
Click to collapse
Give it a try and come to tell if you have sorted it out.
If not, you will probably need to flash your ROM again hoping the application won't stay updated but to back to stock version.
dedq said:
Find the Magisk zip on Google and flash it over TWRP.
Head over to the Magisk module site and you will be able to find an alternate WebView module you can flash. It will be in zip format so I guess you will need USB to transfer those files to your phone since you cannot use it to download modules.
Click to expand...
Click to collapse
Oh, one more thing,
Does this procedure mean, I'll lose TWRP and SuperSu?
Can I not just downgrade the android system webview manually itself?
KillerBeeSama said:
Oh, one more thing,
Does this procedure mean, I'll lose TWRP and SuperSu?
Can I not just downgrade the android system webview manually itself?
Click to expand...
Click to collapse
You won't lose TWRP but I am not sure about SuperSu since it's very old and people don't use it from the time Magisk appeared. I don't think you will be able to have both TWRP and SuperSu.
It would be good for you to just uninstall the updates of WebView if you can use your phone at all. That would solve the problem.
TWRP basically is a menu what allows you to select and apply ADB and/or Fastboot commands.
SuperSU is a Superuser access management tool: it requires SU binary got installed on Android.
Both mentioned sofwares are completely different things, don't depend on each other.
BTW:
I always root Android without the need to make use of Magisk or SuperSU.
So, I went through these
[MAGISK] [MODULE] Webview Manager
Welcome to the XDA home of Webview Manager by Androidacy Read about it on our blog: https://www.androidacy.com/tag/webview-manager/ What is this? This magisk module allows to install several webviews and browsers, replacing the stock one with...
forum.xda-developers.com
Android system Webview installed but not used by apps
I downloaded and installed the latest version of android system WebView from the app store on my android tablet (running 5.0.2). But apps still go on using the old webview version (39.0.0.0). Ho...
android.stackexchange.com
SystemWebView releases
SystemWebView releases
www.bromite.org
Installing SystemWebView
Bromite is a Chromium fork with ad blocking and privacy enhancements; take back your browser! - bromite/bromite
github.com
I got is, .. the adb and appt command says "not found". so.. confusion. and I also see that Bromite System Webview might or might not work on some apps..
So,
Is there a way to downgrade an app through recovery mode
or delete that app's data and start from scratch for that alone?
or is there a way to flash an old Android System Web View through TWRP?
Please help, I have spent the whole day trying to fix this.
I already have SuperSu and it seems if I need to goto Magisk (which is just for that other webview application, I have to do a lot of rolling back and applications going away, ) I don't want that..
Let's keep the Magisk idea as last resort and please let me know if there is any other way to delete the entire Android Webview related stuff and start from beginning.
<bump>
Attached the attack of errors. (these are just few of the ANR popups, there are lots more.. at the last screen you can see even settings won't respond)
My recommendation: Reflash phone's Stock ROM to get rid off of all modifications you applied so far, then restart modding from the scratch.
jwoegerbauer said:
My recommendation: Reflash phone's Stock ROM to get rid off of all modifications you applied so far, then restart modding from the scratch.
Click to expand...
Click to collapse
Just because of one application?
I just want that android webview gone/replaced with a stable one, is that not possible without destroying everything?
Thanks everyone.
we have a solution,
In my case, uninstalling the Xposed framework fixed it for me..
So, while working on this issue I had made a flow map and a log of what is done and its results, may be someone else can benefit from it in the future..
Spoiler: Tries and results
Even starting the entering phone itself is a big issue, because the keyboard applications don't come up; fingerprint doesn't work on first boot as a security measure as well; connected physical keyboard to OTG to phone to enter password... then greeted with lots of errors of all the applications.
Asking people blowed over 'to buy a new phone'
Posted to Reddit, no replies
Posted to Google support, got crappy bot_ish answers; who even hires these people!
Posted to XDA, have some ideas worth trying
Unpacking the system web view.apk on computer gives crap details as it is almost completely encrypted.
Going rabbit hunting through the rabbit hole, checking each folders on "/"
found something similar /system/app/WebViewGoogle/WebViewGoogle.apk
Quick google search confirms that I’m on the right path to finding it...
May be data or XML is somewhere too?
Deleted(copied and deleted) /system/app/WebViewGoogle/WebViewGoogle.apk
Result, Same
Then Reverted
PS: Original Copy at ext_sdcard
Replaced the existing one (92.0.4515.115 with 90.0.4430.210)
Result, no changes.
Then reverted with the crappy original
May be adb will install properly?
Tried adb commands on phone on TWRP, doesn't work
Tried adb from computer to phone, unable to connect to phone.
Was doing it wrong, while in TWRP, I need to initiate "ADB Sideload" and then connect from PC (with Firewall allowed)
then "adb devices", shows connected device with serial number
after the above, the adb push keeps saying "error: connect failed: closed"
turning phone ON and connecting for additional settings (USB debugging) pops "mtp host failed" as soon as I wire..
Started the phone, switched over to Guest account, (oddly seems stuff there are kind of better with lesser error messages), tried launching playstore and wifi, both need password which I don't have, entering settings, hangs for a while, quickly go to apps and uninstall updates for android system web view.. web view becomes 0.0.1
results, fail
Created a temporary user account on phone whilst booting, (because of the observable lesser apps running if I switch over from main..)
added my gaccount on it,
launched playstore to update the android system web view..
the update is stuck at 60%~70 %each time and is unable to complete..
took the v90 application that is on pendrive, connected otg.. and started to install application manually from there..
it said, no space.. even though there is around 4 GB free... continued to disable other applications, such as chrome, youtube, drive etc..
still unable to install the v90 application
even installing other apps (sudoku example) have the same issue,
and then I see a popup that package manager has stopped working (aha! so that itself doesn't work, then can't install),
Went to see if I can change something on developer options, developer option wont come up even after 7+ taps.. hmm strange, may be only main account can have dev options.
While at it, swapped out the Gboard with older AOSP keyboard (retaining Fleksy though).
Rebooted and tried again.. no fix yet..
Atleast I don't have to switch to physical keyboard now for every reboot, since the inner older keyboard comes for first boot.
By TWRP, removed existing app and replaced with v87; doesn't seem to be any different, same errors...
Was about to install the Magisk but it seems to have lots and lots of catches to it, and things to-do before I can go to that...
Continuing investigation on how to downgrade and get back to older state
Through TWRP, deleted the app folder from /system/app/WebViewGoogle/WebViewGoogle.apk
researched to see if there is something else to delete, couldn't find much... proceeding from what we know...
Removed ATSystem.apk (3C's helper) from /system/priv-app just in cast (copy placed at ext_sdcard)
result no change..
Started at around 31-Jul-21 13:00 and went on till 01-Aug-21 01-26 pausing to for the day to rest...
Restored App Folder back to /system/app/WebViewGoogle/WebViewGoogle.apk
WebViewGoogle.apk is v90 again.. (the original seems to be missing, meh, not like it's going to fix)
reboot, result, no changes.
Starting step to install magisk
Removing xposed now..
wiped dalvik cache
rebooting
Kind of stable!!!
Everything seems to work?!?!
Firewalled all app except playstore and mail,
mail seems to work, but can't open the mails (just the headers are received), clicking on the mail says "unable to inflate webview"
aha, I forgot that I have v87 still, if I update that again, will it work (if it doesn't we know how to revert now)
proceeds to update v87 to latest
reboots,
I guess issue resolved by uninstalling xposed, next step to enter phone and move data to safe zone and think about next step.
Are you using xprivacylua?
VD171 said:
Are you using xprivacylua?
Click to expand...
Click to collapse
No, I do remember hearing about it.
GUys, i have installes a system webview on my Samsung J2 core, after restarting my phone stuck on int boot animation, then i do the hard reset combination keys and keeps from restarting. what should i do.
TUPANGPUTi23 said:
GUys, i have installes a system webview on my Samsung J2 core, after restarting my phone stuck on int boot animation, then i do the hard reset combination keys and keeps from restarting. what should i do.
Click to expand...
Click to collapse
Oh... sorry to hear that.
I don't know the solution to that, because mine is rooted I was able to get into the custom recovery and fix things.. not sure what can be done here for your case, (I do know that the old samsung's default recovery is kinda unreadable for English speakers)
So, I think it's best for you to start a new thread in the forum, because if you make a new thread there's a higher chance of reply than this thread which is already marked solved.
(plus. please do attach any photos even crude it may be, still will help people see and suggest actions)
This is how you can use Android Auto with microG and connect your phone with your car.
Prerequisites:
Android 10+
Newest microG core (https://github.com/microg/GmsCore/releases)
A custom recovery to flash a zip file
Let's begin:
For Android Auto we'll use nikgapps Android Auto add-on and modify one file in the flashable zip.
Download nikgapps Android Auto add-on here: https://sourceforge.net/projects/nikgapps/files/Releases/
Dpending on your Android version, choose the correct Addons-(Q/R) folder, then, you want to download "NikGapps-Addon-10/11-AndroidAuto-date-signed.zip"
Now open the downloaded package and open the folder "common". In there you'll find "nikgapps_functions.sh". This file needs to be modified as follows:
Open this file and search for "is_on_top_of_nikgapps"
Remove the following (this code checks if you have installed nikgapps core already, but since we don't want to install that, it must be removed):
Code:
is_on_top_of_nikgapps() {
nikgapps_present=false
# shellcheck disable=SC2143
if [ "$(grep 'allow-in-power-save package=\"com.mgoogle.android.gms\"' "$system"/etc/sysconfig/*.xml)" ] ||
[ "$(grep 'allow-in-power-save package=\"com.mgoogle.android.gms\"' "$system"/product/etc/sysconfig/*.xml)" ]; then
nikgapps_present=true
fi
addToLog "- Is on top of NikGapps: $nikgapps_present"
if [ "$nikgapps_present" != "true" ]; then
abort "This Addon can only be flashed on top of NikGapps"
fi
}
It should look something like this now:
Code:
.....
else
addToLog "- Failed to write $install_location"
abort "Installation Failed! Looks like Storage space is full!"
fi
fi
}
# Check if the partition is mounted
.....
That's it! Now you can flash this zip with your recovery and you'll have fully working Android Auto!
hellcat50I have attempted your tutorial using lineageOS 18.1 + microg rom one a oneplus 8 pro and have some issues.
If I follow you instructions exactly, I can sometimes get android auto to connect to my car after I manually install android auto from the aurora store. It gets stuck, however, at my car's screen saying something like - please follow the instructions on your phone to complete the android auto setup. Android auto app does show car connected, and car shows android auto icon, but only the message to complete setup on my phone.
So, I am guessing that I should not have to actually install android auto, and it should have been installed via the NikGapps file..... However after making the changes to the NikiGapps-android-auto.....zip file and flashing, I get errors (probably why android auto didn't actually install).
Error is:
Error in /sideload/package.zip (status 1)
It also says something about no space left of device as the script rolls ....
Can you give a little more detail in your instructions, and perhaps note if you are using android 11 or android 10.
Keep in mind that I am flashing this zip using lineageos recovery, as twrp is not yet available for the oneplus pro 8 that works with android 11.
Glad you were able to get this working. I have everything working perfectly other than Android Auto... (I did make sure to install google maps, speach services, and search as I know they are required by AA.
Hoping to get this working. Thanks.
D.u.G. said:
hellcat50I have attempted your tutorial using lineageOS 18.1 + microg rom one a oneplus 8 pro and have some issues.
If I follow you instructions exactly, I can sometimes get android auto to connect to my car after I manually install android auto from the aurora store. It gets stuck, however, at my car's screen saying something like - please follow the instructions on your phone to complete the android auto setup. Android auto app does show car connected, and car shows android auto icon, but only the message to complete setup on my phone.
So, I am guessing that I should not have to actually install android auto, and it should have been installed via the NikGapps file..... However after making the changes to the NikiGapps-android-auto.....zip file and flashing, I get errors (probably why android auto didn't actually install).
Error is:
Error in /sideload/package.zip (status 1)
It also says something about no space left of device as the script rolls ....
Can you give a little more detail in your instructions, and perhaps note if you are using android 11 or android 10.
Keep in mind that I am flashing this zip using lineageos recovery, as twrp is not yet available for the oneplus pro 8 that works with android 11.
Glad you were able to get this working. I have everything working perfectly other than Android Auto... (I did make sure to install google maps, speach services, and search as I know they are required by AA.
Hoping to get this working. Thanks.
Click to expand...
Click to collapse
it could actually be that your system partition is full, that's why you got the error message. but if that isn't the issue and android auto is installed as a system app after reboot, it should work flawlessly. you only need to install google maps, the google app and google speech services manually. if you still getting problems, try and choose file transfer as the usb connection option (if you connect your phone with cable). and make sure android auto has all the permissions (especially microphone since it refuses to launch without it)
btw i flashed the zip with lineageos recovery too, it isn't a problem
hellcat50,
Thanks for responding. Interesting that you flashed with lineage recovery also...
Did you get no errors installing? Someone mentioned that to install google apps it needs to be done right after flashing the OS. Is this the way you installed?
In my case I had already installed the OS and apps before I saw your method - No clue how system partition could be full - as my phone has tons of space and only lineage and a few apps installed. It's basically a clean install.
Does it make sense for me to reflash OS and then magisk, and then Nikgapps before booting into OS? I don't want to do this if not necessary.
Also, can you elaborate a bit on what is "special" about Nikgapps-android-auto package that makes this work as opposed to just downloading android auto from Aurora?
Finally, I do have all the dependancy apps installed (gogole, tts, maps) and changing to file transfer does trigger android auto and shows connected on car and in app - but on the car it is stuck at something like "please complete setup on your phone.
As for permissions I will double check that mic has permissions. I did allow all permissions during setup.
Setup does seem to keep asking for google maps to have "location permissions" which I have made sure are on all the time.
Is there anything that you did to get by this location permissions other than making sure google maps has them? Google maps works fine.
The location modules I have in MicroG are the default ones, Mozilla location services and Nominatim address lookup modules. Any chance you have something different or additional?
D.u.G. said:
hellcat50,
Thanks for responding. Interesting that you flashed with lineage recovery also...
Did you get no errors installing? Someone mentioned that to install google apps it needs to be done right after flashing the OS. Is this the way you installed?
In my case I had already installed the OS and apps before I saw your method - No clue how system partition could be full - as my phone has tons of space and only lineage and a few apps installed. It's basically a clean install.
Does it make sense for me to reflash OS and then magisk, and then Nikgapps before booting into OS? I don't want to do this if not necessary.
Also, can you elaborate a bit on what is "special" about Nikgapps-android-auto package that makes this work as opposed to just downloading android auto from Aurora?
Finally, I do have all the dependancy apps installed (gogole, tts, maps) and changing to file transfer does trigger android auto and shows connected on car and in app - but on the car it is stuck at something like "please complete setup on your phone.
As for permissions I will double check that mic has permissions. I did allow all permissions during setup.
Setup does seem to keep asking for google maps to have "location permissions" which I have made sure are on all the time.
Is there anything that you did to get by this location permissions other than making sure google maps has them? Google maps works fine.
The location modules I have in MicroG are the default ones, Mozilla location services and Nominatim address lookup modules. Any chance you have something different or additional?
Click to expand...
Click to collapse
1. you don't need to reflash the rom. i installed the android auto package after i had already setup the system, just like you. as for the full system partition, it depends on the device how large the system partition is. you can check this with fx file explorer for example.
3. the special thing about this package is that it contains not only the android auto apk, but other library files that cannot be installed with just an apk. you can have a look at what files will be installed by opening the nikgapps package and inside the file AppSet/AndroidAuto/AndroidAuto.zip.
4. for the location thing, you just need to activate your location. you can ignore the warning, it should work anyways.
5. i use the same modules with microg, but you don't need them anyways as it works with or without these modules.
just a reminder that the nikgapps package needs to be flashed in order to get android auto fully working. without it you can only use android auto locally on your phone, and you get these car connection problems.
sorry but if you cannot flash the zip due to this error i can't help you. the only thing i could recommend to you is to try and flash other zips that modify the system partition, check if your system partition is actually full and/or ask the rom developers for assistance.
hellcat50 said:
1. you don't need to reflash the rom. i installed the android auto package after i had already setup the system, just like you. as for the full system partition, it depends on the device how large the system partition is. you can check this with fx file explorer for example.
3. the special thing about this package is that it contains not only the android auto apk, but other library files that cannot be installed with just an apk. you can have a look at what files will be installed by opening the nikgapps package and inside the file AppSet/AndroidAuto/AndroidAuto.zip.
4. for the location thing, you just need to activate your location. you can ignore the warning, it should work anyways.
5. i use the same modules with microg, but you don't need them anyways as it works with or without these modules.
just a reminder that the nikgapps package needs to be flashed in order to get android auto fully working. without it you can only use android auto locally on your phone, and you get these car connection problems.
sorry but if you cannot flash the zip due to this error i can't help you. the only thing i could recommend to you is to try and flash other zips that modify the system partition, check if your system partition is actually full and/or ask the rom developers for assistance.
Click to expand...
Click to collapse
Ok,
I have checked and the /system partition is indeed full. Seems like lineageOs makes the /system partition about 1 gb, and then fills it....
Anyone know a way to increase / resize the system partition? Oneplus 8 pro with Lineage + microG rom installed....
Hello and thanks,
I tried on my redmi note 10 with dotOS rom but when i try to open AA, the application it's closed and icon has hidden on interface.
Are you the same problem ?
Sorry for my bad english
McFlyPartages said:
Hello and thanks,
I tried on my redmi note 10 with dotOS rom but when i try to open AA, the application it's closed and icon has hidden on interface.
Are you the same problem ?
Sorry for my bad english
Click to expand...
Click to collapse
When i plug the phone on my car Android Auto to run so it's ok.
Sorry
McFlyPartages said:
When i plug the phone on my car Android Auto to run so it's ok.
Sorry
Click to expand...
Click to collapse
you need to download this app on order to access android auto on your phone again: https://play.google.com/store/apps/details?id=com.google.android.projection.gearhead.phonescreen
flashed the modified zip with twrp on a new install on microg lineageOS 17.1. on a Zenfone 6. The android auto app appears for a few moments after restart in my app drawer but when i tried to access it the app closed and is now hidden. settings for AA are still available. when i plug it into my headunit i get a "No installed apps work with this usb accessory" warning. i have a logcat output but the biggest error seemed to be a wirelesscharging notifcation ogg file not found
D.u.G. said:
Ok,
I have checked and the /system partition is indeed full. Seems like lineageOs makes the /system partition about 1 gb, and then fills it....
Anyone know a way to increase / resize the system partition? Oneplus 8 pro with Lineage + microG rom installed....
Click to expand...
Click to collapse
I also wanted this feature, pretty badly and have just been down a very long rabbit hole and managed to get it working.
Firstly, instead of modifying the Nikgapps, I built a custom package which only includes android auto here: https://sourceforge.net/projects/ni...apps-aa-arm64-11-20210826-signed.zip/download
So you don't need to mess with any configuration files.
Now, the hard part was lack of sizing in the system partition after installing lineageOS + microg. I'm using a pixel 5 (redfin). The microg + lineageOS image doesn't leave any extra room to install gapps on the system partition once its flashed and installing the NikGapps package always fails. In order to leave some extra room on the system partition, I rebuilt the lineageOs + microg package from source, modifying the reserve partition size (https://github.com/LineageOS/androi...l/blob/lineage-18.1/BoardConfigLineage.mk#L63)
I removed the if clause around this (which checks for google mobile services) and had to decrease the reserve size down about 10MB (because with microg it makes the system partition too large to fit in the super partition).
After re-compiling lineageOS with microg (I can share the image (for pixel 5's) if anyone is interested) I flashed that, rebooted to recovery, flashed the Nikgapps and boom, everything is working as expected.
Although building android from source isn't a fun endeavor. For those with pixel 5's who want a lineageOS + microg rom with about 1g reserved on the system partition I can post the image I built.
@D.u.G. - Had a quick look. Looks like its a similar design for you. https://github.com/LineageOS/androi...tnoodlep/blob/lineage-18.1/BoardConfig.mk#L39
You could remove the if statements around this and build from source for your device. If the build fails, reduce the reserve size for system. Its kinda annoying to build tho.
For those of you with rooted devices: You can also just create a privapp stub by systemizing (magisk module) the stub apk found here. Then update AA from aurora store.
It works fine for me on Los 18.1 altough for some reason not all AA compatible apps show up. I also haven't found a mirroring app yet that works.
hellcat50 said:
This is how you can use Android Auto with microG and connect your phone with your car.
Prerequisites:
Android 10+
Newest microG core (https://github.com/microg/GmsCore/releases)
A custom recovery to flash a zip file
Let's begin:
For Android Auto we'll use nikgapps Android Auto add-on and modify one file in the flashable zip.
Download nikgapps Android Auto add-on here: https://sourceforge.net/projects/nikgapps/files/Releases/
Dpending on your Android version, choose the correct Addons-(Q/R) folder, then, you want to download "NikGapps-Addon-10/11-AndroidAuto-date-signed.zip"
Now open the downloaded package and open the folder "common". In there you'll find "nikgapps_functions.sh". This file needs to be modified as follows:
Open this file and search for "is_on_top_of_nikgapps"
Remove the following (this code checks if you have installed nikgapps core already, but since we don't want to install that, it must be removed):
Code:
is_on_top_of_nikgapps() {
nikgapps_present=false
# shellcheck disable=SC2143
if [ "$(grep 'allow-in-power-save package=\"com.mgoogle.android.gms\"' "$system"/etc/sysconfig/*.xml)" ] ||
[ "$(grep 'allow-in-power-save package=\"com.mgoogle.android.gms\"' "$system"/product/etc/sysconfig/*.xml)" ]; then
nikgapps_present=true
fi
addToLog "- Is on top of NikGapps: $nikgapps_present"
if [ "$nikgapps_present" != "true" ]; then
abort "This Addon can only be flashed on top of NikGapps"
fi
}
It should look something like this now:
Code:
.....
else
addToLog "- Failed to write $install_location"
abort "Installation Failed! Looks like Storage space is full!"
fi
fi
}
# Check if the partition is mounted
.....
That's it! Now you can flash this zip with your recovery and you'll have fully working Android Auto!
Click to expand...
Click to collapse
a) Is there any culprit on microg's privacy protections?
b) What version of AA is it and will it update? (I use Fork LOS 17.1 with microg)
c) Also how can i uninstall it afterwords?
hellcat50 said:
This is how you can use Android Auto with microG and connect your phone with your car.
Prerequisites:
Android 10+
Newest microG core (https://github.com/microg/GmsCore/releases)
A custom recovery to flash a zip file
Let's begin:
For Android Auto we'll use nikgapps Android Auto add-on and modify one file in the flashable zip.
Download nikgapps Android Auto add-on here: https://sourceforge.net/projects/nikgapps/files/Releases/
Dpending on your Android version, choose the correct Addons-(Q/R) folder, then, you want to download "NikGapps-Addon-10/11-AndroidAuto-date-signed.zip"
Now open the downloaded package and open the folder "common". In there you'll find "nikgapps_functions.sh". This file needs to be modified as follows:
Open this file and search for "is_on_top_of_nikgapps"
Remove the following (this code checks if you have installed nikgapps core already, but since we don't want to install that, it must be removed):
Code:
is_on_top_of_nikgapps() {
nikgapps_present=false
# shellcheck disable=SC2143
if [ "$(grep 'allow-in-power-save package=\"com.mgoogle.android.gms\"' "$system"/etc/sysconfig/*.xml)" ] ||
[ "$(grep 'allow-in-power-save package=\"com.mgoogle.android.gms\"' "$system"/product/etc/sysconfig/*.xml)" ]; then
nikgapps_present=true
fi
addToLog "- Is on top of NikGapps: $nikgapps_present"
if [ "$nikgapps_present" != "true" ]; then
abort "This Addon can only be flashed on top of NikGapps"
fi
}
It should look something like this now:
Code:
.....
else
addToLog "- Failed to write $install_location"
abort "Installation Failed! Looks like Storage space is full!"
fi
fi
}
# Check if the partition is mounted
.....
That's it! Now you can flash this zip with your recovery and you'll have fully working Android Auto!
Click to expand...
Click to collapse
I modified the file using 7zip, i tryed to flash it with PBRP 3.1.0 but no luck, says "invalid zip file format". any idea?
Xiaomi Redmi 3s 2GB - Fork LOS 17.1 with microg
Update, I installed the original zip from nickgapps without editing the file mentioned with pbrp 3.1.0 without a problem. Thing is, i don't see any icon in the app drawer but its there on settings, apps and i can enter settings of aa.
Is that the way it works? I haven't tried it in the car yet...
Update, i used this app mentioned above from hellcut
Android Auto for phone screens - Apps on Google Play
Must-have smart driving app with maps, media, messaging, and voice actions
play.google.com
AA now working on phone but i get the same message with user 36iii, "No installed apps work with this usb accessory".
Searching for a solution...
AgeManning said:
I also wanted this feature, pretty badly and have just been down a very long rabbit hole and managed to get it working.
Firstly, instead of modifying the Nikgapps, I built a custom package which only includes android auto here: https://sourceforge.net/projects/ni...apps-aa-arm64-11-20210826-signed.zip/download
So you don't need to mess with any configuration files.
Now, the hard part was lack of sizing in the system partition after installing lineageOS + microg. I'm using a pixel 5 (redfin). The microg + lineageOS image doesn't leave any extra room to install gapps on the system partition once its flashed and installing the NikGapps package always fails. In order to leave some extra room on the system partition, I rebuilt the lineageOs + microg package from source, modifying the reserve partition size (https://github.com/LineageOS/androi...l/blob/lineage-18.1/BoardConfigLineage.mk#L63)
I removed the if clause around this (which checks for google mobile services) and had to decrease the reserve size down about 10MB (because with microg it makes the system partition too large to fit in the super partition).
After re-compiling lineageOS with microg (I can share the image (for pixel 5's) if anyone is interested) I flashed that, rebooted to recovery, flashed the Nikgapps and boom, everything is working as expected.
Although building android from source isn't a fun endeavor. For those with pixel 5's who want a lineageOS + microg rom with about 1g reserved on the system partition I can post the image I built.
@D.u.G. - Had a quick look. Looks like its a similar design for you. https://github.com/LineageOS/androi...tnoodlep/blob/lineage-18.1/BoardConfig.mk#L39
You could remove the if statements around this and build from source for your device. If the build fails, reduce the reserve size for system. Its kinda annoying to build tho.
Click to expand...
Click to collapse
First I tried to modify the zip file but upon flasing i got an error also, somthing like "not a valid zip"...
Then I flashed the original nickgapps aa extra zip succesfully with pbrp but got no aa icon in the app drawer, then i flashed your zip but still same problem, no icon.
then i installed android auto for phone screens, mentioned above.
i got aa on phone but upon connection with car a get a message on phone "No installed apps work with this usb accessory".
a) is your zip file for aa for android 10 or it doesnt matter?
b) did i totally mest up my flos 17.1 + microg installation after all this flashing?
c) can i repear any damage?
d) is there a way to make it work in the car?
Thanx, i reposted to you hoping for an answer, because you seem to know what your doing...!
PanosT said:
First I tried to modify the zip file but upon flasing i got an error also, somthing like "not a valid zip"...
Then I flashed the original nickgapps aa extra zip succesfully with pbrp but got no aa icon in the app drawer, then i flashed your zip but still same problem, no icon.
then i installed android auto for phone screens, mentioned above.
i got aa on phone but upon connection with car a get a message on phone "No installed apps work with this usb accessory".
a) is your zip file for aa for android 10 or it doesnt matter?
b) did i totally mest up my flos 17.1 + microg installation after all this flashing?
c) can i repear any damage?
d) is there a way to make it work in the car?
Thanx, i reposted to you hoping for an answer, because you seem to know what your doing...!
Click to expand...
Click to collapse
i think the latest android auto version of nikgapps is causing this issue. try and use the august 4th version (https://sourceforge.net/projects/ni...n-11-AndroidAuto-20210804-signed.zip/download)
hellcat50 said:
i think the latest android auto version of nikgapps is causing this issue. try and use the august 4th version (https://sourceforge.net/projects/ni...n-11-AndroidAuto-20210804-signed.zip/download)
Click to expand...
Click to collapse
I already tried, same issue...
Thing is when i mess with the file and re zip, i get error 2...
doudoune144 said:
For those of you with rooted devices: You can also just create a privapp stub by systemizing (magisk module) the stub apk found here. Then update AA from aurora store.
It works fine for me on Los 18.1 altough for some reason not all AA compatible apps show up. I also haven't found a mirroring app yet that works.
Click to expand...
Click to collapse
In the settings of AA you can set it to accept apps from unknown sources and that should allow you see the extra apps.
PanosT said:
First I tried to modify the zip file but upon flasing i got an error also, somthing like "not a valid zip"...
Then I flashed the original nickgapps aa extra zip succesfully with pbrp but got no aa icon in the app drawer, then i flashed your zip but still same problem, no icon.
then i installed android auto for phone screens, mentioned above.
i got aa on phone but upon connection with car a get a message on phone "No installed apps work with this usb accessory".
a) is your zip file for aa for android 10 or it doesnt matter?
b) did i totally mest up my flos 17.1 + microg installation after all this flashing?
c) can i repear any damage?
d) is there a way to make it work in the car?
Thanx, i reposted to you hoping for an answer, because you seem to know what your doing...!
Click to expand...
Click to collapse
Hey. Yeah, sorry i forgot to mention, I built that aa version for android 11.
You can build your own version with the latest by following the guide here: https://github.com/nikgapps/config
This will build a custom suite of NikGApps. Essentially, in the configuration, I set everything to false and just included android auto.
The flashing should be fine. If I were you, I'd try remove any version of android auto from the phone (if an icon exists). Try and build your own NikGApps package for whatever android version you are using. And try re-flash that.
You shouldn't need to download android auto from any store, if the app icon doesn't appear, it seems its not working on your rom.
As a last resort (depending on how much you want it), I'd try re-flash your original rom (formatting your phone) and immediately after, flash the AA zip before booting into android.
If it works correctly, you should see an AA app icon, when entering, it will tell you you have to download gMaps and a few others apps. Download them from the store then limit their access. You may also have to enable unknown sources for apps in the AA settings. Once connected to your car it should work fine (at least it did for me).
Again, my setup is for Pixel 5, Lineage OS 18.1 android 11
AgeManning said:
Hey. Yeah, sorry i forgot to mention, I built that aa version for android 11.
You can build your own version with the latest by following the guide here: https://github.com/nikgapps/config
This will build a custom suite of NikGApps. Essentially, in the configuration, I set everything to false and just included android auto.
The flashing should be fine. If I were you, I'd try remove any version of android auto from the phone (if an icon exists). Try and build your own NikGApps package for whatever android version you are using. And try re-flash that.
You shouldn't need to download android auto from any store, if the app icon doesn't appear, it seems its not working on your rom.
As a last resort (depending on how much you want it), I'd try re-flash your original rom (formatting your phone) and immediately after, flash the AA zip before booting into android.
If it works correctly, you should see an AA app icon, when entering, it will tell you you have to download gMaps and a few others apps. Download them from the store then limit their access. You may also have to enable unknown sources for apps in the AA settings. Once connected to your car it should work fine (at least it did for me).
Again, my setup is for Pixel 5, Lineage OS 18.1 android 11
Click to expand...
Click to collapse
Thank you so much! Very helpful tips!
Hi,
I was following this amazing guide about debloat your phone https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/ and um I removed some system apps. stuff like xclub and xclone and xaccounts (mostly by infinix) and carlcare and phone master plus some google apps like google play and google play servers and google maps
Now after this, I noticed when I go to system updates and click 'online update' nothing happens like it's broken. usually it leads me to system update application (which is still installed btw) but that do not happen so I'm little unsure which app I removed caused or broke my phone update functionality. so if you could help me determine which package actually I removed caused this or a way to fix it without hard reset and uninstall and reinstall applications again.
Thanks in advance.
Refllash phone's Stock ROM to get rid off of all mods you applied so far.
Removing system apps - what requires Android is got rooted - is never a good idea because they are part of Android OS.
xXx yYy said:
Refllash phone's Stock ROM to get rid off of all mods you applied so far.
Removing system apps - what requires Android is got rooted - is never a good idea because they are part of Android OS.
Click to expand...
Click to collapse
Yeah...I made factory reset again and updates was handled by google play (this is super weird)
I downgraded a system app on my MIUI 13 through adb install -r -d command and it seems to keep resetting to the upgraded version everytime I reboot.
Is there any way to keep the changes, preferably without having to root?
Deleting / replacing system apps requires Android is got rooted.
notBradPitt said:
I downgraded a system app on my MIUI 13 through adb install -r -d command and it seems to keep resetting to the upgraded version everytime I reboot.
Is there any way to keep the changes, preferably without having to root?
Click to expand...
Click to collapse
let me Guess, You re trying to downgrade miui.systemui.plugin package??
michel090428 said:
let me Guess, You re trying to downgrade miui.systemui.plugin package??
Click to expand...
Click to collapse
Yep
Ok I suppose you re doing this in order to get back the Miui 12 Control Center that gets fully themed when applying a theme which is not the case in Version 13.
I am facing the same problem, after reboot it reverts back to the original version stored in sys image i guess.
The Solution that i have found is to uninstall the Sytemui.plugin package completely. this way you ll get the system fully themed and it wont revert back to the newer version after restarting. BUT I find it annoying that the volume control UI becomes stock android which i m not used to it yet. You may try that and see if you can live with it. if no you can simply reinstall the Plugin usiing ADB it causes no problems at all
michel090428 said:
Ok I suppose you re doing this in order to get back the Miui 12 Control Center that gets fully themed when applying a theme which is not the case in Version 13.
I am facing the same problem, after reboot it reverts back to the original version stored in sys image i guess.
The Solution that i have found is to uninstall the Sytemui.plugin package completely. this way you ll get the system fully themed and it wont revert back to the newer version after restarting. BUT I find it annoying that the volume control UI becomes stock android which i m not used to it yet. You may try that and see if you can live with it. if no you can simply reinstall the Plugin usiing ADB it causes no problems at all
Click to expand...
Click to collapse
Thanks for this! My actual reason was the inconsistent capitalization with the labels and everything feels slightly smaller than usual. This wan't a big issue in previous MIUI because the labels are normally hidden.
I also didn't like the implementation of A12 on MIUI 13 as it feels unfinished for the most part and had performance issues. So I hit two birds with one stone by downgrading to Xiaomi.eu Android 11 version. I'll just wait until MIUI 14.
Thanks for your answer, it might help someone facing the same issue
notBradPitt said:
I downgraded a system app on my MIUI 13 through adb install -r -d command and it seems to keep resetting to the upgraded version everytime I reboot.
Is there any way to keep the changes, preferably without having to root?
Click to expand...
Click to collapse
Turn off automatic system app updates in your system settings, turn off auto updates in PlayStore.