yashsingh1/xdaforums huggingface dataset:
[Magisk] DoR3M3:
Ask Google, LOL, how the heck does someone ask Google anything... hmm

But where did you see these new permissions from, how did you find out about them?

Sorry for not explaining myself better, I understand you don't update from FakeStore to Play Store, I was only mentioning this in case someone might do it by mistake, not sure then if it cause any problems, and I understand you can ignore the updates in F-Droid. My comments were more in case of accident is all...

Thanks
[Magisk] Klizi:
Can I flash beta fdroid zip over running stable fdroid version?

And also the opposite?
[Magisk] slipstreamer88:
I have installed 20.5 NanoDroid on OnePlus 3 SkyDragon 9.0 ROM. Need help installing phonesky correctly.

I have tried clean installing with different setup (Yalp+Fake Store), Unofficial Play Store but my phonesky is set up incorrectly and few apps don't run without it. What am I doing wrong?
[Magisk] saedlar93:
Enable signature spoofing for fake store/play store.
[Magisk] Reaven27:
Great work thanks, it's a very good solution for privacy with an opensource rom. Discord doesn't work an idea?
[Magisk] Setialpha:
They are in the Manifest. I've checked the logcat to see all that priv-app permission whining and added them.

Yes, but there's no recent beta.
[Magisk] Tomatot-:
If it's like most ROMs nowadays you need to go to settings => apps & permissions => apps permissions => signature spoofing => top right "show system apps" and then toggle fakestore or whatever it is.
[Magisk] d1n0x:
[MENTION=4187311]Setialpha[/MENTION] Bromite F-Droid repo seems to have changed. The one that is added with your zips doesn't work anymore. The new one is available at

https://fdroid.bromite.org/fdroid/r...B2B45FB78B86DF2EB39A3B6C56BA3DC292A5E0C3B9504
[Magisk] guest4711:
Thank you for reporting.

Yes, it has been changed. From their website https://www.bromite.org/news/2018-12-21-new-fdroid-repository-url :

New F-Droid repository URL

Starting from release 71.0.3578.104 the official F-Droid repository URL has changed to:

https://fdroid.bromite.org/fdroid/r...B2B45FB78B86DF2EB39A3B6C56BA3DC292A5E0C3B9504
[Magisk] Lithesis:
As much as I would like to, I do not have Fused Location in Battery Optimization section. Also search under com. and did not find anything.
[Magisk] Shobit Joura:
Thanks for telling , but my location was working fine bt network location only work whenwifi is on ,it doesnt work on mobile network....

Is there any fix ....or iam doing somethingwrong?
[Magisk] Setialpha:
20.5.1.20190116 "USS T'Plana-Hath"

Hi all,

version 20.5.1 Codename: "USS T'Plana-Hath" is now available. See this post for 20.5 announcement.

What's new?

fixed bootloops on a few custom Pie ROMs

improved compatibility for unified Nlp on custom Pie ROMs [MENTION=7489364]oF2pks[/MENTION]

update Bromite WebView repository URL

Note: unified Nlp still refused to work for me on OmniROM Pie. Havoc OS Pie still has broken signature spoofing.

## 20.5.1.20190116 "USS T'Plana-Hath"

### Bug fixes

* Installer
* add privapp-permission files for Fake Store, Yalp Store and Aurora Store
* fixes bootloops on some Android Pie ROMs
* applies to: Full, microG packages

* Unified Nlp
* improve default sysconfig whitelists by [MENTION=7489364]oF2pks[/MENTION]
* fixes unified Nlp not registering on some Pie ROMs
* applies to: Full, microG packages

### General Changes

* Installer
* improve App Store installation routine

* Signature Spoofing Permission
* add permission files to tell ROMs with native signature spoofing to enable it by default for microG GmsCore and Play Store or Fake Store
* applies to: Full, microG packages

* Bromite WebView
* update repository URL
* applies to: Full, F-Droid packages, build-package script

### Updates

* automatic
* F-Droid Priviledged Extension (0.2.9)
* Simple Gallery Pro (6.2.2)
* Simple Calendar Pro (6.2.1)

Download links

Download from Nanolx or AFH.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE

SysTest package logfile

logcat (if applicable)
[Magisk] azakosath:
[MENTION=4187311]Setialpha[/MENTION], about HavocOS and crDroid pie ROMs, signature spoofing is working when you patch them with the NanoDroid patcher 20.4, at least on my device (Xiaoni Mi A2). I'm mentioning this as a temporary workaround, until they fix their patches.

The patcher from NanoDroid 20.5 recognizes them as patched and aborts.
[Magisk] Setialpha:
... I really don't know what's up with all those Pie ROMs, on OmniROM uNlp doesn't work, signature spoofing does. On Havoc OS and crDroid it's exactly the other way round. NitrogenOS properly works, but luckily isn't available for my OnePlus 5T. As you already found out self-patched ROMs work, so I'll personally stick with OxygenOS for now.

Maybe I'll take the time this weekend to provide full bug reports.
[Magisk] iacchi:
This might not be the problem. Recently my mother changed phone, and I got her old phone to play with. I installed the AEX rom on it (which is pre-patched for signature spoofing), Oreo version. After installing nanodroid (same config files I use for my phone) the microG self-check says that Phonesky is installed but is not spoofed. However, when I go to the list of apps, microG can be spoofed by enabling the authorisation request, but for Phonesky (FakeStore in the app list) it says that it requires no authorisation, so the menu to enable signature spoofing is disabled. This was true for nanodroid 20.4 (first version installed) and is still true for 20.5.1.

Setialpha, do you have any idea about this? Which kind of log may you need to help you troubleshoot this issue?
[Magisk] Setialpha:
you can always grant permissons without UI. In this case

pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE

as root, on-device, should do the trick.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] getting back to com.android.vending if we are using microG, I'm not understanding the need for all these permissions in regards to com.android.vending since microG and Play Store have their own set of permissions.

I was looking over Lineage microG ROM to get an idea of what they were doing, and this one permission is all that is being used for com.android.vending

hmm

<?xml version="1.0" encoding="utf-8"?>

<permissions>

<privapp-permissions package="com.android.vending">

<permission name="android.permission.FAKE_PACKAGE_SIGNATURE"/>

</privapp-permissions>

</permissions>
[Magisk] jenslody:
Bootleggers Pie has working signature spoofing and provides builds for dumpling (5t), but I don't know if μNlp works on it(it works on my J5FN with bootleggers).
[Magisk] Setialpha:
You seem to forget that com.android.vending doesn't need to be Play Store, it might also be Fake Store.

Indeed

Fake Store

only needs FAKE_PACKAGE_SIGNATURE, but

Play Store

needs much more.
[Magisk] iacchi:
Thanks, this did the trick.
[Magisk] DoR3M3:
Ok thanks
[Magisk] Setialpha:
Maybe Jan 19 securoty patch breaks uNlp location service? After updating OxygenOS I get the same crashes as with OmniROM. Rolling back to December build eveything's fine again.

Needs further investigation
[Magisk] Tomatot-:
Did you manage to make Nanodroid work with OOS? What did you have to do for that? Isn't OOS odexed?
[Magisk] Klizi:
These are my back ends and I can see the location is accurate enough on Stat stats.

And when I open Google maps, it shows the location too.

But when I start navigation mode in Google maps, it asks to turn on the high accuracy in location settings. Is there any way to use Google maps' navigation with these back ends? I mean without using GPS at all?
[Magisk] Setialpha:
You can always manually deodex and the use the Patcher. On Pie it's done using vdexExtractor on PC (there's no CDEX to DEX converter for use on-device yet).
[Magisk] Tomatot-:
Ok thanks. How is it? It's running well and stuff? I like OOS but I "can't" use it because I thought it was complicated to deodex it. But with all these infos I might give it a try.
[Magisk] Setialpha:
You only deodex servicres.vdex, rename the resulting dex file to classes.dex and add it to the empty services.jar of OxygenOS. Then push the new services.jar with classes.dex inside to /system/framework, chown root:root, then chmod 0644. Last step is to run the patcher.

I'll update the deodex instructions in the NanoDroid docs later today, for Pie, for older ROMs it's still uptodate.
[Magisk] Ivy123:
Upgraded from Oreo 8.1 to pie cdroid 5.0 on my op5 yesterday . Wasn't able to run microg properly.

I used microg and full package installer via twrp. Still some boxes left unchecked in self-check. Furthermore signature spoofing seems to work, but using signature spoofing tester from f-droid shows disabled.

Any suggestions?
[Magisk] Tomatot-:
Amazing, thank you!

Also, I saw you updated nanodroid to include the fixes for Omni, that's awesome as well. Appreciated.
[Magisk] Setialpha:
No, as I said a few posts ago, several Pie ROM give me headache currently.
[Magisk] Ivy123:
No worries. I just found a list (don't remember if it was from you) where cdroid 5.0 was confirmed to work.

May you recommend a Rom which is working 100% except oos rom. I prefer aosp.

Thanks for the great work by the way.
[Magisk] Reaven27:
Discord does not start, do you have an idea to solve the problem?
[Magisk] oF2pks:
The opposite: I'm searching for an old app that relies on MapsV1 & com.google.android.maps.jar to test my Treble/GSi. I read old post explaining FlightRadar24_v6.6.0 was using it ?

For v2 test I always use : (fdroid) OpenFixMap , SatStat or even SkyMap (for commercials: Maps9.84.2 or Here_WeGo)

(glad if I can help...) for oneplus5/5t, I looked into framework/base...config.xml (or framework-res.apk/...xml) the determination of the "location provider" depends first on bool values :

config_enableFusedLocationOverlay (missing in OP6 oos)

config_enableNetworkLocationOverlay

If they are true: FusedLocation is used, otherwise false: will search a String PackageName replacement

https://github.com/aosp-mirror/plat...b/master/core/res/res/values/config.xml#L1565 ->1687

Strangely LineageOS for OP5 missed to set bool values to false which means FusedLocation is used (despite String PackageName=com.qualcomm.location) , conversely to omnirom (& oos) which really switch to com.qualcomm.location https://github.com/omnirom/android_...orks/base/core/res/res/values/config.xml#L433 (like oos)

, but both seems to use com.android.location.fused in string-array config_locationProviderPackageNames

You should check original OxygenOS/pie values in framework-res.apk, and probably add missing lines for <com.qualcomm.location> to microg-a5k.xml, to test Pie won't let it in doze/sleep optimized mode (like FusedLocation): redundancy here should not hurt (?). I guess that microG uses FusedLocation (+ Oneplus uses QualcommLocation) means that if one is asleep then location failed (?).

Finally devs could consider to add com.qualcomm.location to string-array name="config_locationProviderPackageNames"

btw; noticed that 3x originals com.qualcomm.location, com.google.android.gms & com.android.location.fused manifests have

<uses-library android:name="com.android.location.provider" android:required="false"/>

maybe we should add it to microG apk(?)

I check your uploaded framework-res.apk : FusedLocation (english) is used (all bools are true & gmscore correctly added to config_locationProviderPackageNames), give a try to my fdroid app_PackagesInfo and use search with [location] to check all corresponding package names.
[Magisk] Setialpha:
I'll look into this later today, thanks for your input. Redundancy in sysconfig files shouldn't matter, it simply does nothing if a package doesn't exist or nothing faulty if it isn't in use.
[Magisk] Setialpha:
As I expected, it's already part of unifiedNLp which gets built into microG GmsCore.
[Magisk] Jungfred:
I'm on Skydragon OS Pie for OP3:

- In-build signature spoofing

- January 19 security patches

- Installed Nanodroid 20.5.1

Everything works fine :)
[Magisk] Setialpha:
Yes, OnePlus 3/T is an older device where indeed everything's fine, I have one, aswell. The Problem is the OnePlus 5T. There are internal differences between location handling in their ROMs.

=== snip ==

I did a afternoon full of testing and I beginn to hate myself for not having bought a different device (lol), as mentioned above on the OnePlus 3T everythings fine, [MENTION=7489364]oF2pks[/MENTION] has pointed out a few things a few posts ago.

Some ROMs did not properly grant signature spoofing, some have problems with unifiedNlp, while AICP 14 (beta) worked properly. I'm doing some more tests.

Nowadays it's pretty difficult to find a custom Pie ROM for the OnePlus 5T that doesn't support microG/uNlp out-of-the-box that's not LineageOS.

I'll see whether I get the time this sunday to post bug reports to the ROMs mentioned above (insert please-kill-me-now-meme here).
[Magisk] StardustDroid:
removed
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] hi

I noticed in NanoDroid-microG-20.5.1.20190116 there are two permissions the same for vending.

com.android.vending.xml & privapp-permissions-google.xml both have;

<permission name="android.permission.FAKE_PACKAGE_SIGNATURE" />

com.android.vending.xml should be also added to ROMS?

Thanks
[Magisk] Tomatot-:
Check if you have a webview selected in developer settings, otherwise download one from Play store / YALP. (Android system webview)
[Magisk] Klizi:
Who else using microG with havoc OS?

And do you ever get telegram notifications?

I have terned the wake lock blocker and alarm blocker off too. But still don't receive telegram notifications. I only get then whenever I open the telegram messenger app. :rolleyes:

But I can see microG service core is running
[Magisk] lucastracq:
patcher failed on a fresh install of lineage 16.0 with error:1

syslog attached. /data/adb is empty, what else can i provide/run for troubleshooting?
[Magisk] Setialpha:
AICP 14 (beta) works perfect for me.
[Magisk] Setialpha:
Whats the recovety.log? Error 1 is meaningless (1 literrally means *something* happened).
[Magisk] Setialpha:
default-permission defines the permissions to grant by default (without user intetaction), while the other file whitelists permissions for a given package.

See install_store() / install_microg() in CommonInstaller what file(s) are installed for which component(s).
[Magisk] lucastracq:
it just said "failed to apply patches" no more info, if i understood what recovery.log is

anyway i'll do it again tomorrow and post it.
[Magisk] Tomatot-:
Hey, why don't you include the contemporary yalp store instead of the classic one? https://github.com/yeriomin/YalpStore/releases

It's really minor but I was just wondering.
[Magisk] AlreadyFree:
Hi, just tried installing the newest release (20.5.1) and it's still failing at installing libs for phonesky. I did figure out that this seems to only affect aosp roms for my phone (moto g3), maybe only oreo & pie aosp roms. It installed fine on a lineage based oreo rom I tried. Again the last installer that works on the aosp roms is 20.2a
[Magisk] Machiav3lli:
have the same problem here, tried to repatch the rom using nanodroid-patcher, but it gives me an error, that the rom already support signature spoofing and so, it does nothing. Is there anyway to force the patching (by changing something in the patcher-script), cause I had this problem before on other ROM and was able to fix it through repatching(it worked, cause the patcher was bad at detecting the signature spoofing- which was fixed in latest releases :D )

---------- Post added at 11:52 AM ---------- Previous post was at 11:08 AM ----------

just went and flashed the 20.4 patcher and it worked like a charm(fixed all the missing spoofing boxes), I would suggest to remove the built-in-support checker or to add an option to force repatching if detected. [MENTION=4187311]Setialpha[/MENTION]

---------- Post added at 12:03 PM ---------- Previous post was at 11:53 AM ----------

and one more note, I've noticed that the override function of NanoDroid doesn't delete the system apps anymore, just disables them, which leaves sometimes a big shunk of "dead" space in the system partition, is there any plan to change it?
[Magisk] jaymoker:
You're not supposed to use NanoDroid patcher for already patched ROM because you could get big issues.

This is why there's a check before patching the ROM and you can't force the patcher.

Several custom pie ROM currently have problem with signature spoofing.

Just wait until devs fix sigspoof implementation on pie ROM or edit yourself the patcher at your own risk if you can't afford some patience ;)
[Magisk] -Happy Feet-:
Hello [MENTION=4187311]Setialpha[/MENTION]

I installed MicroG manually on my lineage OS Phone.

But the license check fails from different Apps with yalp or Aurora Store.

What must I do to get it work?
[Magisk] Setialpha:
License check only works with Play Store, of course Yalp Store or Aurora Store have no access to Google's Servers to check your licenses.
[Magisk] -Happy Feet-:
Okay thanks. Can I use the original Playstore with microg?
[Magisk] Machiav3lli:
I understand your point of view, but I think it's a must right now, cause the maintainers of the ROMs, with which I forced the repatching, claimed to have fixed the signature spoofing, but still this problem is triggered.

other than that, the ROMs on which I forced the repatching, works as they suppose to do and the MicroG too, so till they get it fixed, I don't see anything wrong repatching things.
[Magisk] jaymoker:
For Havoc OS, for example, it has been stated in the last changelog that sigspoof is fixed but several people, including [MENTION=4187311]Setialpha[/MENTION] and me, have reported that sigspoof is not working on this ROM.

So, the ROM's maintainers are aware that sigspoof is still not working and they're working on it.

Just wait or change the patcher to suit your needs but you can't ask [MENTION=4187311]Setialpha[/MENTION] to make the patcher work as you feel.

When you code an app or whatever else, you do not change the behavior of it because there's a bug on a system which depends on it.
[Magisk] Machiav3lli:
nee, you seem to get me wrong, I didn't say strictly, this is a solution, I just wished to get an option to force -maybe with a notice that, it's on our responsibility to take this step- or to get a tip about where to begin with cause i got an error after removing

if search_fake_package_signature; then
error " ROM has native signature spoofing already!"
fi

from the binary. I too had the same problem with multi ROMs, so at least with this solution "repatching with 20.4", I can at least open the gsf-dependant apps.

so I am sorry if I was misunderstood to be dictacting or so.
[Magisk] DoR3M3:
So are we talking about changes in Android or just microG changes, in regards to now having com.android.vending.xml?

Thanks
[Magisk] Tech 4 9:
Download links in op don't work for me...neither in tapatalk app or Firefox browser. Tapatalk only shows blown up image of file icon...browser just goes to blank white page.

Sent from a xt1644-RezRmx
[Magisk] Oswald Boelcke:
I can confirm that all links in OP are working. Firefox v54.0 (64-bit).

Check here and alter nanomod.gsync=0 to nanomod.gsync=1 in .nanomod-setup!
[Magisk] Setialpha:
Any interessed in having Firefox Focus bundled?
[Magisk] Oswald Boelcke:
Negative but I appreciate the offer. On all of our devices (except Windows PCs), we only use Slimperience and Orfox.
[Magisk] Setialpha:
While Slimperience looks great and is very flexible, there's no source available (yes, that's a requirement for NanoMod and XDA Labs is the only exception to this).

Orfox (or the-like) is something I don't want to bundle, as that's not for the average Joe. TOR is great, but has it's downsides or things to have in mind, too.
[Magisk] Oswald Boelcke:
Yeah, I like this small size (less than 1 MB) browser from Bielefeld very much, especially the latest beta that is only available as an attached apk to one of @SaschaHa posts. I know that Sascha is still (at least reading) on XDA but currently not obvious active to everybody in this project. Too many people on XDA forget what you and other dev's like Sascha are doing for us in their leisure time and that there are families and friends aside who definitely take precedence.

As far as I remember Sascha's thread, I believe he posted once that he intends to eventually making the code available on GitHub. Don't know what he intends to do with his pro features.

And I fully concur in regard to Orfox/Orbot. I just use them when actually required...;)
[Magisk] Anarchy16:
hey, im sorry to bother u, but i didnt understand about the alter installation .

how can i create ".nanomod-setup" file ?

thx in advance
[Magisk] digitman xxx:
yes bro i notice some guys here face the same issue but donna worry it's not a big deal foe me.

yup, i already did that. wish everything goes right when get stable magisk 13.

NanoMod UP
[Magisk] Oswald Boelcke:
You can create .nanomod-setup with any editor either on PC or on your phone using this instruction, which is a sub-section to the NanoMod-Readme. On PC, I personally use "Notepad++"; on our i9305 I usually use the built-in editor of MiXplorer but other editors will serve the same purpose.

With the editor create a file with the lines shown in the instruction and use the values as desired. Please be aware that nanomod.play not only allows 0 and 1 but also 2. (refer to second screenshot; as I do not sync with Google my file doesn't contain the nanomod.gsync line). When done, save this file with the name .nanomod-setup (or any other name but then you need to rename afterwards). Please be aware that the file doesn't carry any file-extension

I personally always maintain a copy of .nanomod-setup on my ext SD in case I require a clean flash of my ROM i.e. when I also wipe /data and occasionally even internal storage.

From whereever you saved your .nanomod-setup, use now any root explorer (I usually use MiXplorer, but SD Maid or Root Essentials, which I also carry on the device, would do the job, too) and either move or copy .nanomod-setup to /data (as seen in 3rd screenshot) or to any other directory mentioned in the instructions. If you created the file on PC, there are obviously different ways to get the file to /data e.g. first to internal or external storage and then to /data via root explorer or simply through TWRP.

Now, any time you flash the desired NanoMod-package it's going to be populated in accordance to the entries in .nanomod-setup (as long as the file is there).
[Magisk] marcdw:
Anyone here use or heard of DARK ROM (based on LOS 14.1)? I saw it in a list of ROMs for the Axon 7 but there's no thread for it. Knowing nothing about it I flashed it anyway. Found it was totally stripped of apps, not even a launcher. Once I flashed one I saw it only had AudioFX, files, and Settings in the app drawer. After setting it up with gapps and running a couple days I found its Nexus5 thread. Signature spoofing is in the list of features.

Being totally stripped the way it is makes it ideal for a microG / NanoMod setup. Nothing really to hide or pseudo-debloat. Perfect for the DIY types.

I don't know what other devices the ROM is available for but here's the Nexus5 thread...

https://xdaforums.com/nexus-5x/development/rom-dark-rom-t3620086

ZTE Axon 7 A2017U, Dark ROM, Llama Sweet Kernel, Tapatalk 4.9.3
[Magisk] DJ aliasz3d:
I will have to do this it's the only thing I haven't done. Thanks for your explanation I understand it a lot better now:good:
[Magisk] Tech 4 9:
Is this what the op looks like to everyone else? Links don't work for me. I click on little icon and it just shows me a magnified version of icon. I have no idea how to get to links. This is through tapatalk app. In browser it just takes me to blank white page.

Thanks all.

Sent from a xt1644-RezRmx
[Magisk] Setialpha:
I've never had that issue and sorry but, graphic links are 20th century, it's a shame tapatalk and whatever browser you use can't handle them properly.

The link is https://www.androidfilehost.com/?a=show&w=files&flid=150729
[Magisk] Oswald Boelcke:
Deleted. Post wasn't suitable. I apologise.