work-flow after CM upgrade?

[Diapolo]

• upgrade to a new CM13 nigthly
• re-do Needle and call patch.py

Will this work or is any reinstall of microG necessary?

[Catfriend1]

For me, re-applying the su commands for granting permissions via "pm grant" were necessary after CM upgrade. Because of more tasks I like to re-apply after upgrade, I wrote a Task in Tasker for "Boot". The task automatically patches the DIR_VOLUME for my headset, /etc/hosts file, permissions, cleans temp files from /data/data and so on. No problems after upgrade I have to care about.

Often, MicroG worked after upgrade, but signatures were wrong. It would be cool, if I could run patch.py in a Tasker Boot-Task.

[Diapolo]

Thanks for that reply, can you explain to me, what "For me, re-applying the su commands for granting permissions via "pm grant" were necessary after CM upgrade." really means?

I had the problem, that my CM install contained GAPPS and I have /data encrypted. So I formatted /system to remove GAPPS and applied patch.py and installed microG, but had problems installing APKs from my phones storage (no matter if SDCard or internal memory). It turned out that CMs com.android.packageinstaller didn't have storage access rights. By trial and error I found out, that via the Apps menu I had to grant that right in order to be able to install APKs. So in the end it feels like a wipe would have been the best idea for me :-/.

[Catfriend1]

I have a Tasker Bootscript which issues following commands for my apps to work correctly with A 6.0.1, CM 13 and MicroG GMS.

pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
pm grant de.komoot.android android.permission.ACCESS_FINE_LOCATION
pm grant com.sygic.aura android.permission.ACCESS_FINE_LOCATION
pm grant com.sygic.aura android.permission.ACCESS_COARSE_LOCATION