yashsingh1/xdaforums huggingface dataset:
[Magisk] Setialpha:
13.3

Version 13.3 is now available.

It changes the way Magisk is detected, should solve installation issues with 14.0 for a few users.

ChangeLog

* Bug Fixes
* Full, microG, F-Droid packages:
* `magisk.img` is not always created by Magisk 14.0
* change the way Magisk is detected
* create `magisk.img` if required
* General Changes
* build-package Script
* check SHA256 hash of apks downloaded from
* F-Droid
* microG repository
* APK Mirror
* other internal improvements
* Updates (manual)
* Play Store (8.2.36.T)
* microG GmsCore (0.2.4-105)
* Updates (automatically)
* (Simple) Calendar (2.7.4)
* F-Droid (1.0-alpha2)

Download from AFH.

In case of errors, please provide

your device's architecture

your device's Android version (not ROM version)

whether installed as Magisk Module or in System Mode

used Magisk version

recovery.log or logcat or both (whatever is applicable)

____________________________

No, I've not forgotten about the reported issues. I'll post as soon as I've got something to post.
[Magisk] Anarchy16:
sadly, playstore FC still happen in my end :crying:
[Magisk] jay-cp:
Hello,

I am using version 13.2.20170906 with Magisk 14.0 (on a Redmi Note 4, installed via Magisk as a module -- downloaded and then made Magisk install it), and since I see that version 13.3.20170910 updages microG and contains some bug fixes, I'd like to upgrade. What is the correct (or the less risky) way? Should I first uninstall the current version, then install the new one via Magisk? Or should I instead just install the new version over the old one?

Thank you!
[Magisk] Setialpha:
Just update.
[Magisk] gimpy1:
You mean all I had to do was just update, no clean wipe, no reinstalling the rom? Oh well, a clean wipe can't hurt anything.:)
[Magisk] demonoidmaster:
Then why ask if you're going to just wipe even after being told you can update the normal way :/
[Magisk] gimpy1:
Sorry, for being unclear. I had already done the install earlier with a clean wipe, before that question was asked and answered. At the time i answered, I was still in the process of installing and updating my settings, etc.
[Magisk] Anarchy16:
[MENTION=4187311]Setialpha[/MENTION] hey dev, i think i know what the culprit to my PStore FC issues, its because of the old school nanomod-setup .

i flash with nanomod-setup : PStore FC

i flash without nanomod-setup : no FC

edit: my nanomod-setup only to enable sync function
[Magisk] akoyaxd:
Everyone, who has Play Store Crashes, try to wipe App Data+Cache. Fixed it for me! :)
[Magisk] capasoxe:
Thanks a lot devs...

Everything worked alright and there haven't been much of a mishap except for some, regarding contact sync and location services which was dealt with after help from reading some posts in the thread.

But I have got to ask this.

I am a privacy freak, and carrying out this procedure I came to know that the user obviously still gets access to playstore, contacts sync, calender sync and stuffs (except for play services ofcourse).

But what I am concerned is that, is google still going to have access over my data because of these apps ? I mean, I know, no playservices (phew..), call me paranoid, but I still am worried if google can get track of me through these apps.

or any services running beneath the surface.

Well I switched over to here maps but

* Location is on high accuaracy.

* there is the android systemwebview

* google backup transport service ( I dont know what that is:D)

and

* google contact sync too

Forgive me if my concern seemed absurd, but advices are highly appreciated.:)

Also while we are on that subject I also need one other help.

Is it possible to completely anonomize my device ? Let me say an example.

When I had playservices I once used orbot to download an app unavailable in my country, yet when trying to run it (a radio app that I tried to stream) ,(orbot still active), it said not available in my country. Why could this be?

Is it because

1. of playservices ? (now with nanomod installed, is it possible ?)

2. the app has access to my device id, imei or sim location(country) ? (ok.. how

do I get past this one ?)

3. Any other reason ? (do enlighten me)

Because I would like to set up my device in such a way that it provides total anonymity.

I mean I could use orbot, mock location app, yet somehow apps get hold of my ip address and then pulls me up.

Thanks a bunch in advance..:)
[Magisk] Oswald Boelcke:
I'm also extremely privacy concerned. Maybe my thread here is useful including hints of possibly helpful applications (e.g. AFWall+, Network Log, MyAndroidTools, SD Maid etc.)

Thanks to microG and Nanomod I'm completely GApps free except the Google Play Store.

You can (hopefully) see my signature block that includes my system configuration. Additionally, I'm using the unofficial Franken-Xposed framework (until rovo89 comes up with the official Xposed for Nougat) and the Xposed module XPrivacy (Pro) that fakes e.g. device ID, IMEI etc. for all the enabled applications including system applications if desired. You need to play with XPrivacy in the beginning to recognise its full capabilities.

However, I'm getting too much off-topic in this thread - and I apologise. If interested, check the linked thread and come back there.
[Magisk] capasoxe:
Thanks pal,:)

Its really great to find someone who shares one's thought. Also I just peeked into that other thread you mentioned, will take some time to go through all of it.

and if I gather any doubts, is it alright to pm you ? because I too feel it is better NOT to populate this thread.:D

Thanks.
[Magisk] kurtn:
Or we start a new threat for paranoiacs ? I would join :eek:
[Magisk] Oswald Boelcke:
No PM please just post in my thread. This way others can possibly benefit from the discussion. And I suggest not to post to simply say thanks - for that, the posts carry a thanks button.

---------- Post added at 15:51 ---------- Previous post was at 15:50 ----------

I'm paranoiac. Just check my thread How did I enhance the battery duration, privacy and security of my GT-i9305?
[Magisk] capasoxe:
Will do.:good:
[Magisk] Reylom:
Same here, also after the update from yesterday. It sounds a little bit strange, that only two users do have problems with playstore fc :confused:

Sorry, i dont understand what do you mean

Tried several times without success.

Temporary i 've installed the play store as normal app (data located "/data/app/com.android.vending-1") whatever that means :eek: but it works.
[Magisk] Anarchy16:
do u flash microg with .nanomod-setup ?

if yes, try flash it without .nanomod-setup, and check. for me that was the culprit & now no more PStore FC
[Magisk] Reylom:
Nope, i flash without .nanomod-setup, only the "NanoMod-microG" zip
[Magisk] rohitdave:
Yes thats what I am planning to do.

Thanks

---------- Post added at 08:28 AM ---------- Previous post was at 08:08 AM ----------

Hi

I have been using MicroG only a couple of months, but I can say this my 2 year old battery gives me 0 drain overnight 8 - 9 hours.

I am using Greenify too on my rooted MI4 W.

Wifi, Data, Bluetooth off overnight.

Wakelock and Alarms extensively blocked using the wakelock and alarm blocker on my Official RR latest cancro rom.

Phone works perfectly with the Official RR rom, I have tried many roms but best result with MicroG is with this one.

MicroG is one of the best hacks :):):)
[Magisk] meistr91:
Mine too
[Magisk] pokipokipxorn:
thank you for the great work! Everything works,

- no more Play Store crash/FC, solution is replacing the Phonesky.apk with ale5000's version (microG unofficial installer)

- key to successful google apps sync is to

: setup microG without errors, reboot

: assign permissions from Settings > Apps > 3-dot menu > Show System for google related apss/services,

: add new google account

: install google apps, assign the respective permissions from Settings > Apps > 3-dot menu > Show System,

: go to Settings > Accounts > Google > myaccount > 3-dot menu > Sync now

: finally only launch google apps when all permissions, account sync have been performed

detailed steps here

notes:

- roms does matter, even if it claims to support microG/signature spoofing, so try a few. I wasn't successful with AEX (stuck at gmail sign-in) but got better luck with CosmicOS

- rebooting phone in between is important, it allows settings to register & prompts for microG permissions upon next login

- some quirks still exists ie microG still prompt for sign-in during Google Calendar launch, I just select Cancel and it works anyway. Funny coz my google account was created before I rebooted the phone

btw, how do I check for Battery Drain? especially the blue text below? specifically, how do I check which offending app is the one?

( microG fails to register applications to GCM (Google Cloud Messaging) if they were installed before microG, but the apps keep trying to register and that causes the battery drain)

much thks
[Magisk] MarcoBobolo:
I tried to install microG (as a user‐app, a system‐app and a Magisk module) on two OnePlus 5 ROMs (A.I.C.P. & AospExtended) but had an error in each case: UnifiedNlp does not get registered in system (no binding of the UnifiedNlp service). This is quite frustrating… Does anybody have any advice to give?
[Magisk] Wo11ven:
So you are not using nanoMod?
[Magisk] MarcoBobolo:
I tried different ways to install microG, including NanoMod (“Magisk module”).
[Magisk] Wo11ven:
How did the patching go?
[Magisk] MarcoBobolo:
Completely fine. I also tried to apply Haystack patch from my computer.
[Magisk] Wo11ven:
I see. I used to have problems like this when using microG only. NanoMod wasn't working in my x86 device using Magisk back then but it did work when I forced the installation to the system. When you said that you have tried installing it as a system app, did you do it flashing nanoMod microG package? If not, I suggest you to do it
[Magisk] MarcoBobolo:
Yes, I also tried that. I always get the same problem, regardless of the installation method: UnifiedNlp is not registered in system.
[Magisk] Wo11ven:
Are the backends properly installed and enabled?
[Magisk] MarcoBobolo:
They are. (The checkbox is checked on microG self‐check page.)

Addendum — I have been using NanoMod for months on other phones; this is not my “first time”.
[Magisk] super-drone:
I have the same problem, I tried to install nanomod on 3 ROMs (including a signature spoofed one) and I always get the same problem, unifiednlp is not registered in system and my location won't work because of that
[Magisk] Wo11ven:
Damn, sorry guys, don't know what can be done now :(

---------- Post added at 07:16 PM ---------- Previous post was at 07:14 PM ----------

I know for a fact that permissions problems can cause it to not register, but it doesn't seems like being the problem now.
[Magisk] super-drone:
I searched and found out that installing fake gapps(xposed) would solve the problem, too bad I'm on nougat :eek:
[Magisk] Islam Mu:
How can i make google photo aync& backup ?
[Magisk] Trademark97:
It still doesn't seem to be supported for anyone on microG. You can (after awhile of waiting) view your photos, but syncing them still seems to be an impossibility, due to Google accounts handling being somewhat incomplete.
[Magisk] Islam Mu:
Tx dude for fast answer and hope to see nanomod going from better to better.
[Magisk] kurtn:
Works in redmi 2 aosp oreo. Patcher seems to take longer and device getting warmer.
[Magisk] capasoxe:
Hey,

One other thing. I used the nanomod fdroid zip file to get fdroid on my device. Now there is an update to Fdroid, and whenever I tried to download the update, it crashes itself. I tired an update for orbot too and it crashed again.

In addition to that there are also random bugs in Fdroid, like when downloading heavy files like OSM maps, it force closes.

Any suggestion ?

Also, can I get the 'on body detection' feature with this setup ? Or is that a google service ?

Thanks.
[Magisk] capasoxe:
Forgive me for the sudden judgement. Because after a few hours of usage I came to realise it just isn't Fdroid alone that 'keeps closings. Apps like sound waves (podcasts app), T-UI launcher, seal note etc.. keeps on force closing at times. And not always, but sometimes only. Any idea why ?
[Magisk] Oswald Boelcke:
How about only to use Nanomod-microG? Then download and install the F-Droid.apk from the F-Droid site. Finally, try to reproduce the issues. I doubt you require F-Droid with the raised privileges.

BTW: I'm still using F-Droid v0.102.3 because I absolutely don't like the "new" UI.
[Magisk] Setialpha:
It's a known Magisk issue, see the general Magisk Troubleshooting thread for more infos about how to fix WebView related app crashes with Magisk.
[Magisk] Setialpha:
Issue found. Stay tuned for beta build (soon™).
[Magisk] Didgeridoohan:
Well... To be fair, the issue you're talking about is an issue with the ROM. Magisk (MagiskHide actually) just brings it out into the light. :)
[Magisk] Setialpha:
Yes, you're right.
[Magisk] Setialpha:
13.4 beta1

The first beta release for 13.4 is here. I've started looking into reported issues.

The first issue that should be fixed are Play Store crashes on arm64, x86 and x86_64, the changes to the Installers that fix that issue /might/ as a side-effect also fix other (minor) issues. I've also refined the Installer functions a bit.

Additionally DroidGuard Helper is now installed as user app, instead of system app, which fixes the crashes when trying to attest SafetyNet.

Full ChangeLog since 13.3:

* Bug Fixes
* Full, microG packages:
* install DroidGuard Helper as user app (fixes it crashing)
* Full, microG, F-Droid packages:
* fix that under certain circumstances installation errors don't cause the installer to abort
* fix that arm libraries are not properly installed on arm64 devices
* affects applications that have arm libraries, but not arm64 (namely: Play Store)
* fix that x86 libraries are not properly installed on x86_64 devices
* affects applications that have x86 libraries, but not x86_64 (namely: Play Store)
* on x86 / x86_64 try to extract arm libraries, if no x86 / x86_64 libraries are found
* fix that the installer doesn't clean up if installation of libraries fails in Magisk Mode
* more verbose recovery.log regarding library installation
* Full package:
* when `.nanomod-apps` contains an application that is not included don't abort
* instead just print a message
* General Changes
* Full, microG, F-Droid packages:
* minor internal improvements
* Full package:
* switch to official F-Droid build for Lightning browser
* SetupWizard:
* updated
* build-package Script:
* Fix repo index.xml downloading
* force-debloat Script:
* support `.nanomod-overlay` configuration file
* uses fallback values, if none found, which are in the script itself and can be edited
* no longer abort when Magisk is installed
* suggest the user to pseudo-debloat instead when Magisk is installed
* change the way Magisk is detected
* add the ability to only test what would be done
* other minor internal changes
* Documentatation:
* updated
* Updates (automatic)
* F-Droid Privileged Extension (0.2.6)
* (Simple) Gallery (2.14.1)
* (Simple) Calendar (2.7.5)
* Substratum (842)
* XDA Labs (1.1.3.2b)
* Removed Applications
* Hacker Keyboard
* New Applications
* BeHe Keyboard

Download from AFH.

In case of errors, please provide

your device's architecture

your device's Android version (not ROM version)

whether installed as Magisk Module or in System Mode

used Magisk version

recovery.log or logcat or both (whatever is applicable)
[Magisk] pandavova:
(framework-patcher)

Was spending the last 3h to change some stuff in the "pull-fileset" file, cause it didn't work for me. It just didn't want to do the adb pull stuff. Somehow i got to do it, then i saw: i dont have a framework2.jar and a core.jar. oh... wasted time...

remembered that the zip showed "odexed ROMs are not supported", didn't get why, i was deodexed. thats why i started to look into framework-patcher. looked into the code. it checks just for all .odex files *facepalm*.

i had 4 folder with no apk, but the folder left where the odex file was.

feelsbadman

(its applying hook patch right now)

Edit: The SecSettings was named SecSettings2 for me, renamed it.

Flashing again ._.
[Magisk] capasoxe:
Yeah, tried it. But seems the problem still persist.:( I've attached a log copied from the soundwave app, will that suffice ? And sorry if the log taken is not correct, because I am such a noob. :D I simply copied and pasted the text.

And I went through that thread you directed me to. And it says there that the issue could be because of

1. the signature error- But I flashed the patch of nanomod to spoof

2. absence of Chrome stable, Chrome Beta or Google WebView - But then the whole point of not using google powered services would be forgotten. (am I wrong?)

Morover these closing mishaps seems to be happening to apps downloaded from Fdroid( but not every app though). Because I tried using backed up apps that were once downloaded from playstore, it seems to be working fine.

Am I doing something wrong ?:(
[Magisk] Setialpha:
a) Report issues in Haystack (pull-fileset) in the Haystack repository at github.com/Lanchon/Haystack

b) there's no other way to check odex status from TWRP

c) I'll adjust to support SecSettings2.apk

c2) it's optional to patch Settings btw.
[Magisk] Setialpha:
You're always using Google or AOSP WebView, may try Chromium WebView. Thing is: it's a ROM issue, exposed by Magisk.
[Magisk] capasoxe:
OK.. Thanks.. :good:
[Magisk] capasoxe:
Ohh.. And I forgot to ask. Is the "on body detection" a google feature ? Because I can't find that option with this setup.
[Magisk] Setialpha:
Dunno what that is?
[Magisk] pandavova:
Yeah, i know that it's optional, but i would be happy to have it. In the end it didn't work. Im using a S5 Neo with 6.0.1. (SE is Enforcing btw)

Some ideas?
[Magisk] Setialpha:
Of course not, it only looks for SecSettings.apk, or Settings.apk. Try again without that option.

If it still doesn't work, I need a logcat.

Next beta will support SecSettings2.apk.
[Magisk] pandavova:
So the renaming of the apk + folder wasn't useful? (As i said, i renamed the SecSettings2.apk to just SecSettings.apk)

Edit: Only that with the Developer Settings didn't work. Everything else works.

It said it did everything.
[Magisk] Setialpha:
Hmmm, then it should have worked.

As I said, if not, I need logs.
[Magisk] pandavova:
Just running adb logcat while installing?

Edit: I might got it. Look into the "75-nanomodpatcher.sh" at line 255. It only applys the patch into the "Settings.apk", not the SecSettings.apk.

(I dont know but why its "Settings.apk-ui" at line 256?)
[Magisk] Setialpha:
No, copy /tmp/recovery.log

75-nanomodpatcher.sh is the addon.d Script.
[Magisk] MarcoBobolo:
I give some feedback (for those who might be interested): I got UnifiedNlp to register in system by debloating com.qualcomm.location through NanoMod overlay. Many thanks to dhnasa!
[Magisk] super-drone:
can you give me a small tutorial on how to do this please?
[Magisk] Oswald Boelcke:
FC of Google Play Store with v13.4-beta.

Nanomod-microG installed as Magisk (v14.0) module on Samsung i9305, arm, with Android 7.1.2 (RR-N-v5.8.4)

In microG settings all tickmarks are checked.

Logcat attached.
[Magisk] Setialpha:
The crash is caused by an Xposed Module (or the Xposed Framework), see this part of the logcat:

09-15 09:12:13.408 D/AndroidRuntime(12799): Shutting down VM
09-15 09:12:13.425 E/AndroidRuntime(12799): FATAL EXCEPTION: main
09-15 09:12:13.425 E/AndroidRuntime(12799): Process: com.android.vending, PID: 12799
09-15 09:12:13.425 E/AndroidRuntime(12799): android.view.InflateException: Binary XML file line #4: Binary XML file line #4: You must supply a layout_width attribute.
09-15 09:12:13.425 E/AndroidRuntime(12799): Caused by: java.lang.UnsupportedOperationException: Binary XML file line #4: You must supply a layout_width attribute.
(...)
09-15 09:12:13.427 E/AndroidRuntime(12799):	at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:102)
09-15 09:12:13.435 W/ActivityManager( 3104): Force finishing activity com.android.vending/com.google.android.finsky.activities.MainActivity

If you have any module modifying the Play Store (or a Substratum Theme) try again with that thing disabled.
[Magisk] Oswald Boelcke:
Thanks very much for the fast and absolutely correct analysis. It was my theme (PitchBlack Origins) in deed.

I themed the Google Play Store with PitchBlack as I'd done with Play Store versions successfully before. Uninstalled/reverted the theming of Play Store; perfectly running now.

I'm a bit ashamed that I didn't realised the origin of the issue without your support, although I very well know how much themes can influence system preformance or be the culprit for crashes.
[Magisk] MarcoBobolo:
Sure. The pseudo‐debloat documentation explains it all:

I added a line with “com.qualcomm.location” to the .nanomod-overlay configuration file (in fact, I also created the file as I was not using the pseudo‐debloat feature before; the documentation indicates where you can save that file);

I applied the modification by entering the following commands in a terminal on the phone:

su
nanomod-overlay --update

After a reboot, everything was fine.
[Magisk] Setialpha:
I should make that default, no?
[Magisk] MarcoBobolo:
That would certainly help!
[Magisk] Setialpha:
13.4 beta2

The second beta of 13.4 is now available.

Changes since 13.4-beta1

* Bug Fixes
* Full, microG packages:
* `com.qualcomm.location` conflicts with microG location backends, so when installing microG
* in Magisk Mode pseudo-debloat `com.qualcomm.location` (if it exists)
* in System Mode move `com.qualcomm.location` (if it exists) to /sdcard
* Full, microG, F-Droid packages:
* fix useless recovery.log messages on post-KitKat ROMs
* General Changes
* Uninstaller:
* if `com.qualcomm.location` was backed up to /scard, restore it
* restore `SecSettings.apk` and `SecSettings2.apk` if it was backed up to /sdcard
* Framework-Patcher package:
* support patching of `SecSettings2.apk` for optional UI patch, aswell
* Updates (automatic)
* F-Droid (1.0-alpha3)
* (Simple) Gallery (2.14.2)
* XDA Labs (1.1.3.3b)
* Yalp Store (0.25)
* Twidere (3.6.29)

See this post for what's new in 13.4-beta1.

Download from AFH.

In case of errors, please provide

your device's architecture

your device's Android version (not ROM version)

whether installed as Magisk Module or in System Mode

used Magisk version

recovery.log or logcat or both (whatever is applicable)
[Magisk] Ex_FallenSkyTear:
i have a problem:

›i have installed a magisk micro-g module, and signature spoofing don't work.

i tried to flash "nano-patcher" in TWRP and now signature spoofing and micro-g work, but isn't present a option to disable it in a developer options.

[sorry for my bad english]
[Magisk] Wo11ven:
I believe the patcher doesn't create an option to disable spoofing. It's included only when the ROM supports signature spoofing by default. I could be wrong though.
[Magisk] Setialpha:
The toggle is optional. There's a setting for that in the SetupWizard, respectivly use 'nanomod_sigspoofui=1', when creating the configuration manually. The toggle will be at the very end of the developer Settings.

But, as I don't see why you'd want it, it's disabled by default. It's not like on pre-patched ROMs a per-app toggle, but only a on-off toggle for all apps at once.
[Magisk] super-drone:
I tried to add that line but it's telling "not found", so if there's not qualcomm.location why I keep getting unifiednlp not registered in system :eek:

Edit: ignore all above
[Magisk] super-drone:
After a lot of stupid tentatives I finally found out how to add an app to nanomod overlay configuration file, but it's saying "com.qualcomm.location" is not installed...
[Magisk] Setialpha:
So, that's what it is; com.qualcomm.location is not installed on all ROMs, plus of course only on devices with Qualcomm chipsets. The cause of why UnifiedNlp does not work for you, seems to be a different one.

Ah and, much shorter than creating the file:

nanomod-overlay --add com.qualcomm.location

.