microG + Android Auto fully working - General Topics

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!

hellcat50​I 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:
hellcat50​I 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!

Related

GApps for Galaxy S6 SM-G 9200

Has anyone had success in getting google play store / gapps running on the Chinese SM-G 9200 with Android 6.0.1?
Flashing gapps in TWRP fails due to insufficient available storage, all kind of installations i tried (rooted / unrooted) are just leading to crashing google services framework. I set the maximum permissions including change of system settings in the app config. No success.
Anyone had success? Or can extract the google packages from another S6 to test if i can install?
I had success but the path is everything else than straightforward and i would call it a dirty hack and i do not give any guarantee that this will work and not brick your phone.
1. Flash firmware CHC-G9200ZCU2DPL1-20170105164838 with Odin
2. Install TWRP (i used 3.0.0.0). This will result in boot-loop
3. Re-Flash the firmware above
4. Boot up the phone, should work now
5. Restart into TWRP, install SuperSU (i used 2.46)
6. Boot up the phone
7. Use Root Explorer to free up some system space to install gapps. (I deleted the Chinese apps in /system/preload which should give sufficient space but deleting might have side effects)
8. Download pico arm64 Android 6 gapps from opengapps
9. Boot into TWRP, install gapps
10. Boot up the phone. Play store should be there, you can open but i was not able to login
11. I downloaded the Google Installer_2.0.apk typically used for Xiaomi phones and run the app. It will update ServicesFramework, Install Loginmanager and fail with Playstoreservices, but this is fine. Probably it is just sufficient to install the Loginmanager, did not try that.
12. Re-boot the phone. Now It should work fine

[DEV][TOOL] Shadow53's Flashable Zip Builder

Making flashable zip files for Android devices can be… frustrating.
For those who have never tried, here are some of the more irritations:
You use a very limited scripting language called edify to write your install scripts. So limited, that some people replace the binary (update-binary) used to parse the script (updater-script) with a normal shell script that performs the installation instead. What’s the point of having update-binary and updater-script, then?
Any app installed to /system/ with bundled libraries in the apk need to have those libraries extracted in order to not crash.
Various system files need to be created to grant certain permissions to apps by default, and you need to know the syntax of each one (usually some dialect of XML).
If the correct permissions are not set on an installed file, it can cause the system to bootloop.
The Solution:
I’ve created a program in Go that reads entries from a configuration file and builds a flashable zip for you, while taking care of the implementation for you. The name is simple: Zip Builder.
Features:
Configuration files can be written in JSON, YAML, or TOML.
Supports Android versions since 5.0 Lollipop
Automatic generation of updater-script and an addon.d persistence script.
Automatically extracts libraries from apps being installed under /system/.
Can specify different file or app sources for different versions of Android and/or CPU architectures. updater-script will only install the files for that particular system.
Validate downloaded files with md5, sha1, and/or sha256.
F-Droid interoperability: Specify the repo URL and app’s package name, and zip-builder automatically gets the rest of the app’s information from F-Droid’s repository, including a download link for the latest version of the app.
Remove any files you specify, e.g. apps that you are replacing with your own version or apps/files you just don’t want on your system.
Standalone binaries available for Mac OS X, Linux, and Windows. Android binaries (to use in a terminal app) coming soon.
Linux binaries may be usable with Termux on Android, though this is not tested or supported.
Links
Latest release announcement
Download zip-builder
Example configuration files
Complete documentation
Zips built with this tool
EmojiOne Emojis - Replace the NotoSans emojis with the ones from EmojiOne
F-Droid installer - Includes the F-Droid privileged extension, allowing F-Droid to perform automatic installs and updates.
Hacker bundle - Includes the F-Droid builds of Termux with API, Float, and Widget addons, and Hacker's Keyboard.
Google swipe libs - Includes the swipe libraries for the AOSP keyboard. One zip for all Android versions since 5.0 on all architectures.
microG - Installs the FOSS replacement for Google Play Services, microG. Optionally install the Play Store for downloading apps, using the patched version from NanoDroid.
Google Play Store - choose between the vanilla Google Play Store or the patched one from NanoDroid.
Google Sync Adapters - install the Google sync adapters for use with microG. Install contacts sync, calendar sync, or both.
UnifiedNlp - If you want network-based location without Google Play Services or microG, install this zip. Comes with the Mozilla location backend and Nominatim geocoder backend.
No GAPPS app packs - FOSS replacements for Google Apps packages, provides basic system apps for ROMs running without Google Play Services.. There are multiple tiers of zips you can download, matching the OpenGapps flavors. Click on the link to view the contents of each zip.
microg.zip doesn't flash anything in my redmi 2 oreo aosp. log attached
kurtn said:
microg.zip doesn't flash anything in my redmi 2 oreo aosp. log attached
Click to expand...
Click to collapse
I'm currently working on polishing up a new release of a different project of mine, then I'll have time to look it over.
Per your PM, though, you said busybox wasn't in the location that the zip assumed it was. Can you search through your system and tell me which directories contain either busybox or toybox? (I believe busybox was found in two different folders when I flashed Lineage before)
Shadow53 said:
I'm currently working on polishing up a new release of a different project of mine, then I'll have time to look it over.
Per your PM, though, you said busybox wasn't in the location that the zip assumed it was. Can you search through your system and tell me which directories contain either busybox or toybox? (I believe busybox was found in two different folders when I flashed Lineage before)
Click to expand...
Click to collapse
Just have to search with the right tool. In twrp I see busybox in the expected location.
kurtn said:
Just have to search with the right tool. In twrp I see busybox in the expected location.
Click to expand...
Click to collapse
I had a little bit of time to flash a beta Oreo ROM for my phone and had no issues with things getting copied to my system correctly. If busybox is in the location that the script expects it to be, it's not obvious what the problem is.
The log you gave me seems to show that it mounted your system and data partitions correctly, detected that a folder did not exist, and then exited normally.
Have you tried an updated zip recently? A little while back I had the script output the found values for Android version and CPU architecture. It's possible it got fixed along with whatever I was working on at the time.
Re-downloaded microg.zip from @Shadow53's page. Now it works as expected.
Pushed a commit that should hopefully fix the issue @marcdw reported in the MicroG thread at https://forum.xda-developers.com/an...y-services-t3217616/post74531435#post74531435
@marcdw, I rebuilt the zips with a build containing the fix. Can you confirm that the libraries are now loading correctly? Things are working on my end, except for the patched Play Store requiring a reboot before working.
@rottenwheel do you really mean xposed? I have the impression magisk gets more attention.
@Shadow53,
I had actually edited the updater and add-on.d scripts to use the short names on most of your zips and all was good.
After work I'll start anew using your rebuilds. ?
ZTE Axon 7 A2017U, Dark ROM, microG (NoGAPPS), Tapatalk 4.9.5
rottenwheel said:
As read on the microG thread:
Although XDA community and most Android modders tend to side with Xposed-based solutions, I need to emphasize this is not the absolute case. I rather to stay away from it as much as I can, because it's given unstability to my devices as soon as I start tinkering with some modules; as soon as I get it removed from my setup, bugs are gone. I don't want to engage in unrelated discussions here, I just wanted to let you know your zip solutions have been working like a charm and many of us will miss if you lose enthusiasm about it. Keep it up and rocking. Thanks to you, getting microG onto our handsets is easier.
Click to expand...
Click to collapse
NanoMod is optionally a Magisk module and has nothing to do with Xposed, though I appreciate the sentiment.
*If* I were to lose interest in this project or in providing scripts, the code for the zip-builder is open source and contains the build recipes I use for all of the zips I provide, so it shouldn't be too hard for someone to pick up if they wanted to.
That said, I have no intention of stopping providing zips any time soon, though development on the zip-builder itself is slow because university is keeping me busy. I use my zips too, so I gotta be at least a little invested
Shadow53 said:
@marcdw, I rebuilt the zips with a build containing the fix. Can you confirm that the libraries are now loading correctly? Things are working on my end, except for the patched Play Store requiring a reboot before working.
Click to expand...
Click to collapse
Howdy sir. My apologies for not getting back. Work got in the way.
The zips work perfectly. I setup two ROMs on my Axon 7 with microg-playstore, no-gapps, and hacker. Not a single hiccup with the included apps or Play Store. All is good.
Must say again, I like the apps included in no-gapps.zip. Most of those I use and have to get manually from F-Droid.
Perfect with Dark ROM which has no apps or launcher and thus no worries of duplicate functionality (like two cameras, two calendars, etc.).
I see Firefox has replaced Lightning. Haven't used Firefox since v28 so I get to see what the new one is all about.
??
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
Awesome. Been looking into how to get F Droid and Micro G plus most other things to work for my sm-g900p!
Really not liking the way Google has been going.
So looking into HOW to get that this to work for me.
From what I had seen so far....
PLEASE keep working on this!!
Thank you Shadow 53!
marcdw said:
Howdy sir. My apologies for not getting back. Work got in the way.
The zips work perfectly. I setup two ROMs on my Axon 7 with microg-playstore, no-gapps, and hacker. Not a single hiccup with the included apps or Play Store. All is good.
Must say again, I like the apps included in no-gapps.zip. Most of those I use and have to get manually from F-Droid.
Perfect with Dark ROM which has no apps or launcher and thus no worries of duplicate functionality (like two cameras, two calendars, etc.).
I see Firefox has replaced Lightning. Haven't used Firefox since v28 so I get to see what the new one is all about.
??
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
I'm glad to hear that it's working for you. I'll be posting a new release on GitLab around the end of the week (yay finals...)
Regarding the no-gapps zip, most included apps also remove the AOSP equivalent if present, with a couple exceptions such as Silence for SMS not removing the default SMS app and Firefox not removing the built-in browser, both to avoid potential issues.
godofsalt said:
Awesome. Been looking into how to get F Droid and Micro G plus most other things to work for my sm-g900p!
Really not liking the way Google has been going.
So looking into HOW to get that this to work for me.
From what I had seen so far....
PLEASE keep working on this!!
Thank you Shadow 53!
Click to expand...
Click to collapse
Development of the zip builder is stalled right now, largely due to time. It works great for what I need at the moment, but I will work on bug fixes for things that come up. The zips are rebuilt every week by a cron job on the server, though packages containing the official Play Store may not get updated if opengapps updates their version (which changes the URL). I try to catch that, but I don't always have time to check.
I'm considering putting together a comprehensive gapps removal zip that should remove as much trace of Google as possible from the device, including any application data. That will take some investigation, though, and so it shouldn't be expected soon. If/when it comes, it'll largely be for removing installations by opengapps and Beans gapps, as I can't account for all differences between OEMs.
Hey no worries about updates being "stalled"!
I know what your going though believe me. Can be such a frickin headache!!! Not to mention anxiety that some poeple get this time of the year!
AM certainly glad to hear that you are still somewhat working on it though. Plus frim what I can see, this has not been out long, so I don't thing others may even know about it!
I believe they will!!!
Running paid apps having a license verification at runtime
I installed a recent LineageOS for microG (build date 11/29) on my Samsung Tablet SM-T800 (chagallwifi) and added root by flashing the zip provided by LineageOS.
I first tried Yalp Store (version 0.29, downloaded from fdroid), but then figured out that I cannot use any paid apps that make use of a license validation at runtime. However, there are some paid apps that I require.
I did some reading and it seems like the installation of the original Google PlayStore is a solution.
So here are my questions:
1) Can I get paid apps running when I install the original PlayStore as a system app following the procedure described on the blog shadow53 (sorry, cannot post the link cause I am a new user, but it is easy to find when searching for 'shadow53 android downloads')?
2) Is there anything I have to do in addition to flashing the PlayStore zip?
3) Does flashing the original PlayStore give rise to any conflict with the FakeStore that comes installed as part of microG? If so, how do I remove the FakeStore?
ebiel said:
I installed a recent LineageOS for microG (build date 11/29) on my Samsung Tablet SM-T800 (chagallwifi) and added root by flashing the zip provided by LineageOS.
I first tried Yalp Store (version 0.29, downloaded from fdroid), but then figured out that I cannot use any paid apps that make use of a license validation at runtime. However, there are some paid apps that I require.
I did some reading and it seems like the installation of the original Google PlayStore is a solution.
So here are my questions:
1) Can I get paid apps running when I install the original PlayStore as a system app following the procedure described on the blog shadow53 (sorry, cannot post the link cause I am a new user, but it is easy to find when searching for 'shadow53 android downloads')?
2) Is there anything I have to do in addition to flashing the PlayStore zip?
3) Does flashing the original PlayStore give rise to any conflict with the FakeStore that comes installed as part of microG? If so, how do I remove the FakeStore?
Click to expand...
Click to collapse
1. Yes, you will be able to check licenses at runtime with the Play Store installed.
3. Yes, they use the same package name, so having both apps installed causes a conflict. Depending on where the FakeStore is installed, the Play Store zip may recognize where it is and automatically remove it for you. You will see some output while flashing, something like "Deleting existing file /system/priv-app/Phoneksy" if it was discovered (file path may be different).
If it does not automatically remove FakeStore, find the directory it is installed in and delete it, then on next boot modify the playstore addon-d script to delete that directory. You should see where and what to change when you open the file. If you do not make this change,
2. You may have to manually remove FakeStore with the above process. You should also look at https://shadow53.com/android/no-gapps/faq/playstore-not-loading/ regarding other gotchas with getting the Play Store running and https://shadow53.com/android/no-gapps/faq/playstore-incorrect-signature/ if you use the patched version of the Play Store.
The addon.d survival script dosn't work on my rom (play store patched). I use lineageos with microg on nexus 7 (flo).
memarama said:
The addon.d survival script dosn't work on my rom (play store patched). I use lineageos with microg on nexus 7 (flo).
Click to expand...
Click to collapse
Whether addon.d stuff works depends on the ROM. Some ROMs have a backup feature during flashing but a lot do not. Does LOS support addon.d backups?
ZTE Axon 7 A2017U, Dirty Unicorns UNOFFICIAL v11.7.2 ROM, Tapatalk 4.9.5
memarama said:
The addon.d survival script dosn't work on my rom (play store patched). I use lineageos with microg on nexus 7 (flo).
Click to expand...
Click to collapse
LineageOS has addon.d sopport. Maybe you should post a recovery. Log
memarama said:
The addon.d survival script dosn't work on my rom (play store patched). I use lineageos with microg on nexus 7 (flo).
Click to expand...
Click to collapse
After installing the microG Lineage fork on my own device to test, I realized that the Play Store zip marks FakeStore as something to remove on initial installation, but not across system updates. The addon.d script doesn't re-remove FakeStore.
Try downloading the latest version of the zip and installing it. FakeStore should stay uninstalled now.
In other news, I've decided to make my no-gapps zip into multiple, similar to the various OpenGapps zips. This means a larger selection of open source apps that can be installed, including some more replacements for AOSP apps. I'm working through a couple bugs right now potentially related to these zips, then I'll add an update with more details.

[GUIDE] MicroG on OnePlus 6 (open source and ligthway alternative to Google services)

Updated and tested for Android 10 (with Omnirom)
Why MicroG?
Here is a great explanation from the official wiki itself: https://github.com/microg/android_packages_apps_GmsCore/wiki
There are different and good reasons to move away from Google services and get microG services:
1) More privacy: all Marvin's work is open source and focused on privacy. The "Google Play Services" app is probably the worst app you can have on Android when it comes to telemetry, spying, etc. It's always running tons of services to know all your comings and goings. As a side note, it's also good to not rely on Google too much.
2) More RAM available: Google Play Services use a lot of RAM when GMScore uses almost nothing.
3) More battery life, especially while idling: you'll avoid all the wakelocks related to Play Services (whether they are intentional or not)
CREDITS / Thank you:
@MaR-V-iN, for his wonderful and amazing work to free us from Google. One of the most underrated dev in the Android world.
@Setialpha , for his nanodroid module and his availability to help.
@topjohnwu for Magisk
How will your Android experience change?
Actually, not so much. If you're only interested in MicroG for the reasons 2) and 3), you can still use all Google apps, including the Play store (you need a patched version). Be aware, some apps don't work or are not working properly. Implementation status of different Android/Google services can be found here: https://github.com/microg/android_packages_apps_GmsCore/wiki/Implementation-Status
If you wonder if an app works or if you've tried and it doesn't work, just check on the issues tracker on Github or on your favorite search engine.
Now, if you want to change your habits, F-Droid will become your new best friend. It's an app store, like the Play Store, but which only delivers controlled, quality and open source apps. Both stores share many apps in common but F-Droid also has apps that the Play Store doesn't, because they're against Google policy for example. It should become your main app store as it's always good to use open source apps, for many reasons. Let's not start a debate here.
However, at least, at the beginning, it's tough to not use ANY app from the play store. For that, you should use Aurora store (whick is a fork of Yalp Store FYI). You get access all apps from Play Store. You can either use an anonymous account or use your own Google account. In the second case, you'll be able to download your paid apps. However, these won't work if they include a license check (most of them nowadays). You can nicely ask the dev if there's a workaround. Some accept, like the team behind Titanium Backup for example. Or SmartPack Kernel Manager's developer.
If you're looking for open source alternatives to the apps you usually use, I could list a few of them but this list is just great: https://github.com/offa/android-foss .
If you don't know how to replace Google services, this list is great as well: https://shadow53.com/android/no-gapps/alternatives/
You can also check on reddit like on this subreddit: https://www.reddit.com/r/fossdroid/
What ROM to use?
Any custom AOSP ROM should work, as long as :
1° it supports signature spoofing
2° it's deodexed
3° it supports alternative location backends, it's
-I wouldn't recommend any ROM that comes with gapps included. It just makes things more complicated.
On Android 10, I would highly recommend OmniROM, which offers an archive with microg prebundled, and also because it perfectly supports microG (signature spoofing, alternative location backends, etc.)
USEFUL LINKS
-MicroG thread: https://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
-MicroG wiki: https://github.com/microg/android_packages_apps_GmsCore/wiki
-UnifiedNlp thread (location): https://forum.xda-developers.com/android/apps-games/app-g-unifiednlp-floss-wi-fi-cell-tower-t2991544
-Nanodroid (provides packages related to open source / microG stuff): https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928/ (you need to download the microG edition) + here to understand how to edit the .nanodroid-setup file: https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md#detailed-description
-microG unofficial installer (doesn't work on our device yet): https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360
-Useful website about installing, getting packages, etc. : https://shadow53.com/android/no-gapps/setup-guide/microg/
-Great list of FOSS (open source software) apps for Android: https://github.com/offa/android-foss
-Alternative to Google apps: https://shadow53.com/android/no-gapps/alternatives/
-Personnal experience feedback: https://forum.xda-developers.com/android/general/gapps-free-samsung-galaxy-s3-lte-gt-t3553620
If you read all these threads you'll start to have a good understanding of what is microG and how to live without Google.
Prerequisites:
-OnePlus 6
-Unlocked bootloader
-TWRP installed
-A ROM supporting microG
-All files downloaded, on your device
DOWNLOAD LINKS
-OOS: https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
-TWRP: https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
-Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
-Nanodroid: https://downloads.nanolx.org/NanoDroid/Stable/ (you need to download the microG file)
-Push Notification Tester: https://play.google.com/store/apps/details?id=com.firstrowria.pushnotificationtester
-Working Google Maps app: https://www.apkmirror.com/apk/google-inc/maps/maps-9-82-1-release/
-F-Droid: https://f-droid.org/FDroid.apk
INSTALLATION TUTORIAL
Italic = recommended, but not mandatory. Do it if something doesn't work properly
0) DON'T RESTORE your apps until everything is set up, otherwise you'll have issues with GCM (getting instant notifications from messaging apps for example)
1) Flash the custom ROM of your choice ( these instructions should work: https://privatebin.net/?42d550f9ae5df09f#imAFxWjM0gW+V9+ex+8nRyYSoSQzLPjhNXsbKIUjzqA= )
2) Flash magisk, reboot to system
3) Reboot to recovery
4) Flash Nanodroid (you need to download the microG edition, and make sure you have made the .nanodroid-setup file at the root of your internal storage, see instructions here https://github.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md) or you can also try MinMicroG (https://github.com/FriendlyNeighborhoodShane/MinMicroG_releases/releases).
If you choose nanodroid, update microG thhis way: https://www.reddit.com/r/MicroG/comments/fd7udr/fork_of_microg_gmscore_with_unifiednlp_working_in/
5) Reboot to system
6) Open MicroG, give it permissions if that's not already the case
7) Click on self-check. Give signature spoofing to all the empty boxed so they get ticked.
For Omni/Arrow/Aex, you can make sure it's allowed in settings/apps & notifications/apps permissions/spoof package signature. for playstore/fakestore make sure you click on the 3 dots and check system apps (if it exists).
8) Give permission to ignore batter optimizations.
9) Enable Google device registration and Google Cloud Messaging.
10) Enable Safetynet if you want
11) Click on UnifiedNlp and active the 3 backends: location backends: Mozilla+ Déjà Vu; adress lookup backends: Nominatim.
12) REBOOT
13) Open your phone app, and type this:
Now try this instead in order to manually enable device registration and connect to Google Cloud Messaging:
Code:
*#*#2432546#*#*
Code:
(old) *#*#42678278#*#*
. Nothing will appear on your screen but it can help. It's probably necessary but I prefer to make all the steps to make everything work. Sometimes logging in on your Google account through settings help. You can then log out if you don't want to use any Google account.
14) Install Push Notification Tester from Yalp Store.
15) Test the app, see if everything works. If it doesn't, ask for advice here as it should at this point. You can try to reboot one more time. Make sure that in the GCM settings you're connected since X time, otherwise something is wrong. Step 23 is the most important step to check if it doesn't work.
16) Go back to the self-check menu, now you can check the self check status and almost all boxes should be ticked. Some are not for me but GPS still works, even on Google Maps. Here is a screenshot of how it looks like for me: https://i.imgur.com/WsPX5RC.png
17) Now you can try to install the apps you want! Don't install apps that need push notifications before all these steps otherwise they might never be registered. Clean installing apps is recommended. You can try to restore them from a backup as well, but it often doesn't work. The middle ground solution is to install the app with the Yalp Store / F-droid and then restore its data with Titanium Backup for example.
18) Now you should see apps being registered in microG.
19) You can make sure your gps work with either OSM (https://f-droid.org/en/packages/net.osmand.plus/) or Google Maps (see apk mirror link earlier, the last version won't work). You should get your location without any isuses at this point.
20) Enjoy your almost Google free phone.
EXTRAS:
α) If you have issues with location, you can try this (on some custom ROMs, Google Maps finds my location but then it doesn't update and so if I move around it won't update my location. Also sometimes I need to reload the app to update my location which is quite inconvenient. It seems that doing the steps following help)
Install a terminal emulator (I recommend Termux)
Make sure your phone has root rights and type :
Code:
su
Authorize the app
Type next:
Code:
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
Then
Code:
pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
iii) Reboot
β) If you have issues in general, try to update Nanodroid (if you used Nanodroid, ofc) apps from F-Droid. Add this repo to F-Droid: https://www.nanolx.org/fdroid/repo/
And then make sure all your apps are updated (including microG GmsCore)
A) DroidGuard uses non-open source stuff. It's in order to pass safety net.
B) GCM is not open source either.
C) If you want google maps to work, you need to install an "old" version and not update it. You can find it here: https://www.apkmirror.com/apk/google-inc/maps/maps-9-82-1-release/. Sometimes, your location might never appear. In this case, restart a few times Maps until your position shows up.
D) You can also try to install MicroG and its dependencies as user apps. I've tried it and wasn't very happy with the results as they don't work as well being user apps. From what I've heard, everything works fince except location. So you can give it a try as well this way.
E) My personal .nanodroid-setup is this one (to understand what it does, check here: https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md#detailed-description ):
Code:
nanodroid_gmscore=0
nanodroid_play=21
nanodroid_overlay=0
nanodroid_mapsv1=1
nanodroid_gsync=0
nanodroid_swipe=1
nanodroid_forcesystem=0
nanodroid_fdroid=1
nanodroid_nlpbackend=1100
Reserved.
Very nice,
too bad that it doesn't support OOS but it's understandable.
nimrodsv said:
Very nice,
too bad that it doesn't support OOS but it's understandable.
Click to expand...
Click to collapse
Maybe it could work with nanodroid patcher for signature spoofing and then manually deodexing the ROM. It would also be necessary to remove all the Google apps. So yes I guess it's just easier to use a custom ROM as a saner base.
nimrodsv said:
Very nice,
too bad that it doesn't support OOS but it's understandable.
Click to expand...
Click to collapse
Like above, it could work. By installing xXx module and choose total gapps removal then try what he said above for spoofing. Tempted to try, but can't atm.
OOS has normally odexed system and do not support signature spoofing.
An option would be to deodex services.jar and the use the nanodroid patcher to enable signature spoofing.
I have done that for some 8.1 OOS roms but not on the latest releases.
whizeguy said:
Like above, it could work. By installing xXx module and choose total gapps removal then try what he said above for spoofing. Tempted to try, but can't atm.
Click to expand...
Click to collapse
NisseGurra said:
OOS has normally odexed system and do not support signature spoofing.
An option would be to deodex services.jar and the use the nanodroid patcher to enable signature spoofing.
I have done that for some 8.1 OOS roms but not on the latest releases.
Click to expand...
Click to collapse
Maybe I'll give a try it seems possible.
@Tomatot- I see that you've tried to working with MicroG on Omni but getting bootloops and that you will try working with it again soon.
Anything I should know before I try this on Omni? Thanks!
nimrodsv said:
@Tomatot- I see that you've tried to working with MicroG on Omni but getting bootloops and that you will try working with it again soon.
Anything I should know before I try this on Omni? Thanks!
Click to expand...
Click to collapse
I had a weird experience on Omni. At first it was working all fine with nanodroid-microG, but then I tried to change the .nanodroid-setup and it broke all my system, I was never able to make it work again on Omni. I also tried once the Nisse .zip and it didn't work either. So I can't really tell what's the pattern to make things work or not work... I really liked Omni so I'm going to try again within the next few days, with a nice clean flash and Nisse zip. I will let you know. If you're impatient and want to try, try to follow the steps from this tutorial and let me know how it goes.
Omni is a bit tricky with permissions, use the latest Nanodroid-microG from https://downloads.nanolx.org/NanoDroid/Stable/ to install on omni, it adds bit more (calendar and contacts sync etc) that i dont want tho
NisseGurra said:
Omni is a bit tricky with permissions, use the latest Nanodroid-microG from https://downloads.nanolx.org/NanoDroid/Stable/ to install on omni, it adds bit more (calendar and contacts sync etc) that i dont want tho
Click to expand...
Click to collapse
Did you manage to make your script work on Omni? I'm not interested in these extras either.
Tomatot- said:
Did you manage to make your script work on Omni? I'm not interested in these extras either.
Click to expand...
Click to collapse
Yes, but some extra work is needed: Open the zip with 7-zip and extract all item from priv-app and delete the priv-app folder from the zip.
Install rom, the modified zip and boot into system.
Install the extracted apps normally.
Use https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851 to convert the 4 installed apps (gms, gsf, phonesky and yalp) to system apps (to priv-app).
Thats bit much but its functional on omni.
NisseGurra said:
Yes, but some extra work is needed: Open the zip with 7-zip and extract all item from priv-app and delete the priv-app folder from the zip.
Install rom, the modified zip and boot into system.
Install the extracted apps normally.
Use https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851 to convert the 4 installed apps (gms, gsf, phonesky and yalp) to system apps (to priv-app).
Thats bit much but its functional on omni.
Click to expand...
Click to collapse
Awesome, thanks, I'll try this asap.
I will update OP but I can tell Arrow OS seems to support perfectly MicroG. And your script works directly @NisseGurra . I've noticed the location apps are a bit oudated, could you update them please? Cheers.
Thread updated with my experiences with the different custom ROMs available on our device. i've also improved instructions a little and make some steps not mandatory but recommended.
Thanks very much for this great tutorial although I've never had an OnePlus. Quite a long time ago, I tried to capture my personal way to become GApps-free from the very beginning by installing µG un to today where I always use NanoDroid. Maybe my thread contains some information useful to you?
Oswald Boelcke said:
Thanks very much for this great tutorial although I've never had an OnePlus. Quite a long time ago, I tried to capture my personal way to become GApps-free from the very beginning by installing µG un to today where I always use NanoDroid. Maybe my thread contains some information useful to you?
Click to expand...
Click to collapse
Yes I read it and it was very useful. Your thread was already included in "useful links" btw.
Updated backends microg installer (attached)
NisseGurra said:
OOS has normally odexed system and do not support signature spoofing.
An option would be to deodex services.jar and the use the nanodroid patcher to enable signature spoofing.
I have done that for some 8.1 OOS roms but not on the latest releases.
Click to expand...
Click to collapse
whizeguy said:
Like above, it could work. By installing xXx module and choose total gapps removal then try what he said above for spoofing. Tempted to try, but can't atm.
Click to expand...
Click to collapse
Bumping you again to give you some news.
So I really don't feel like going back to use Google Play services but I miss OOS for battery life and performance reasons.
However, I feel like deodexing OOS is really not optimal, see these links:
https://i.imgur.com/FRJgqVm.png
https://github.com/anestisb/vdexExtractor/issues/33
https://i.imgur.com/9Y6JBGD.png
So yeah, it's a tough choice...
Tomatot- said:
Bumping you again to give you some news.
So I really don't feel like going back to use Google Play services but I miss OOS for battery life and performance reasons.
However, I feel like deodexing OOS is really not optimal, see these links:
https://i.imgur.com/FRJgqVm.png
https://github.com/anestisb/vdexExtractor/issues/33
https://i.imgur.com/9Y6JBGD.png
So yeah, it's a tough choice...
Click to expand...
Click to collapse
Aw man.. That's just too bad :/ thanks for the update mate.

[ROM]-[10-04-2020]-[microG] Unofficial LineageOS 17 w/ microG support

Info
This thread contains unofficial custom builds of LineageOS 17 for OnePlus 7 Pro based on official LineageOS repositories & PeterCxy's repositories. This ROM has a few additions.
- Includes microG signature spoofing patch
- Removes com.qualcomm.location which interferes with UnifiedNlp
- Added option to configure the height of the back gesture in gesture navigation settings
Please note that I am not an experienced ROM developer, these are simply my own custom builds I'm sharing with you all in case anybody finds them useful.
ROM instructions
If you want to spoof signature of Phonesky you must manually grant it. Do this through a terminal emulator by running the following commands.
Code:
su
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
There is currently an issue with microG UnifiedNlp. If you ever get the "UnifiedNlp has no last known location" error, you must re-enable UnifiedNlp backends. This must be done after every reboot and whenever this error decides to pop back up.
Installation instructions
1. Format data in TWRP
2. Flash ROM, TWRP Installer
3. Reboot > Recovery
4. Flash ROM, TWRP Installer
5. Reboot > System
6. Complete system setup
7. Reboot > Recovery
8. Flash Magisk, flash NanoDroid
9. Reboot > System
Update instructions
1. Flash ROM, TWRP Installer
2. Reboot > Recovery
3. Flash ROM, TWRP Installer
4. Reboot > Recovery
5. Flash Magisk, flash NanoDroid
6. Reboot > System
Downloads
ROM - EDIT: Links removed, no longer working on this project.
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
TWRP - https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
NanoDroid - https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Thanks
Special thanks to @LuK1337 and @PeterCxy for helping me out with the build process and answering all my questions
Kernel Source
https://github.com/PeterCxy/android_kernel_oneplus_sm8150
XDA:DevDB Information
LineageOS microG, ROM for the OnePlus 7 Pro
Contributors
gigatex
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Testing
Created 2019-08-23
Last Updated 2020-04-11
Reserved for OP.
Thank you for this! ??
Update - 30-08-2019
Changelog:
Switched to official LineageOS device repositories
Merged latest changes from LineageOS frameworks/base
Switched hosting from MEGA to Android File Host
Update instructions are in OP
Hi gigatex,
I just wanted to thank you for creating this! I've been using it as my daily driver without any issues. It's rock solid, fast and great on the battery and it's the only rom that works superbly with MicroG, without the hassle of removing Google junk.
If I were to give you one suggestion, it'd be to include links to Magisk, NanoDroid (F-Droid and MicroG packages) and perhaps TWRP. If only for user ease.
Keep up the good work and thanks again!
Doesn't the lineage team provide an official microg version around a week or so after they have an official regular build?
Thank you for this either way! I've been waiting for a microg version of this.
I don't want to sound douchy, but it's actually the MicroG team that forks the LineageOS build and pretty much does to it what gigatex did with this ROM. They will probably add support for our device in a few days, but it's great that we don't have to wait for that, thanks to this ROM.
aeonius said:
I don't want to sound douchy, but it's actually the MicroG team that forks the LineageOS build and pretty much does to it what gigatex did with this ROM. They will probably add support for our device in a few days, but it's great that we don't have to wait for that, thanks to this ROM.
Click to expand...
Click to collapse
As far as I can tell by looking at the docker repo, LineageOS for microG just takes the LineageOS frameworks/base and applies the signature spoofing patch for their builds. If this is the case they might have the same problem with UnifiedNlp as every other OnePlus 7 Pro ROM.
Lineage only merged the "NLP Combo feature" commit in the last month or so, while most other ROMs have had it for a lot longer. If anyone here flashes their build when it becomes available I'd be curious to know if UnifiedNlp works correctly on their ROM.
I'm gonna give this a go tonight. Looking forward to it. Lineage has always been my favorite since I got into the rom community. Glad I can go Google free.
Side note: anyone know of good navigation app? For obvious reasons, I'm not wanting to use Google maps.
adamokari said:
I'm gonna give this a go tonight. Looking forward to it. Lineage has always been my favorite since I got into the rom community. Glad I can go Google free.
Side note: anyone know of good navigation app? For obvious reasons, I'm not wanting to use Google maps.
Click to expand...
Click to collapse
I use OsmAnd~
https://f-droid.org/en/packages/net.osmand.plus/
gigatex said:
I use OsmAnd~
https://f-droid.org/en/packages/net.osmand.plus/
Click to expand...
Click to collapse
I've used osmand before, it's been awhile but for some reason there was something I didn't like about it. I'll give it another shot. Thanks!
This ROM is running great so far. Thank you very much for your work!
Only issue I'm having it getting the oneplus camera app. Whenever I tap the app to open it, it force closes. O can however long press on the icon and tap one of the modes in the pop up menu and it works from there. For some reason it seems to be the standard picture mode that crashes. Did anyone else have issues with it?
Edit: Double post
Sorry for all the questions, but what exactly is the proper way to set this up with microg? I've realized I'm not getting push notifications for email apps.
Basically for my install I wiped dalvik and data,
Flashed ROM and twrp
Reboot recovery and flash ROM and twrp again
Reboot to system
Reboot recovery and flash magisk and nanodroid
Then proceed to configure microg, signing into google account and enabling cloudessagimg, etc.
Any help would be greatly appreciated.
Thank you!
adamokari said:
Sorry for all the questions, but what exactly is the proper way to set this up with microg? I've realized I'm not getting push notifications for email apps.
Basically for my install I wiped dalvik and data,
Flashed ROM and twrp
Reboot recovery and flash ROM and twrp again
Reboot to system
Reboot recovery and flash magisk and nanodroid
Then proceed to configure microg, signing into google account and enabling cloudessagimg, etc.
Any help would be greatly appreciated.
Thank you!
Click to expand...
Click to collapse
As for OnePlus camera, I simply downloaded the APK in PeterCxy's thread and I'm not experiencing any crashes.
I use the same installation procedure as you. Are your apps getting registered under GCM and is your "Current State" showing as connected? Also make sure you go through the entire self check. The "System supports location provider" is the only checkbox that's supposed to be unchecked.
gigatex said:
As for OnePlus camera, I simply downloaded the APK in PeterCxy's thread and I'm not experiencing any crashes.
I use the same installation procedure as you. Are your apps getting registered under GCM and is your "Current State" showing as connected? Also make sure you go through the entire self check. The "System supports location provider" is the only checkbox that's supposed to be unchecked.
Click to expand...
Click to collapse
I'm gonna try again from stock. It says current state disconnected and no apps ever register under GCM. Not sure what the issue is.
adamokari said:
I'm gonna try again from stock. It says current state disconnected and no apps ever register under GCM. Not sure what the issue is.
Click to expand...
Click to collapse
That's definitely the issue then. Also make sure you only open apps that use GCM for the first time after completing the microG setup and GCM is connected, or the app will never get registered.
gigatex said:
That's definitely the issue then. Also make sure you only open apps that use GCM for the first time after completing the microG setup and GCM is connected, or the app will never get registered.
Click to expand...
Click to collapse
Alright I got it working. Thank you very much!
Would it be better to flash MicroG through NanoDroid or by installing the Magisk MicroG Module?
Neffarion said:
Would it be better to flash MicroG through NanoDroid or by installing the Magisk MicroG Module?
Click to expand...
Click to collapse
I don't know what's recommended, but I ended up flashing the magisk module. My reason being is that nanodroid has a ridiculous amount of extra bloat in it.

HELP After updating Android System Webview My Phone is Unresponsive

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)

Categories

Resources