Malware Buster
Intro:
This is a Xposed module. It helps to prevent malwares to register service/receiver which were disabled in My Android Tools before.
Manual:
Use My Android Tools/3C Tools to disable service/receiver of your target Apps Install this module, enable it in Xposed Installer, you need to reboot device at the frist time. Check the target Apps you want to disable in Malware Buster UI.
Troubleshoot:
Look at log of Xposed Installer, many runtime information will be shown there.
Reference:
http://developer.android.com/refere...tEnabledSetting(android.content.ComponentName, int, int) https://android.googlesource.com/pl...va/android/app/ApplicationPackageManager.java Some UI codes come from https://github.com/rovo89/XposedAppSettings
Download Link:
http://repo.xposed.info/module/com.rexpress.xposed.malwarebuster
流氓终结者
介绍:
Android上有很多流氓App, 比如xx地图, xx输入法, xxx钱包, xx点评, 会注册一堆service和receiver常驻后台, 即使在App的设置里关掉各种推送也没用. 常见的方法是使用绿色守护. 对于高级用户来说使用My Android Tools/3C Tools, 可以更有效地关闭不必要的service和receiver. 可是这些顽固的App会在运行的过程中重新注册这些service/receiver, 而My Android Tools只是静态地禁用, 没有常驻进程, 无法检测是否被重新开启了. 本App的解决方案是使用Xposed Module, 通过Hook setComponentEnabledSetting方法, 改写参数为DISABLED, 让流氓App无法重新注册service/receiver.
使用方法:
使用My Android Tools/3C Tools禁用service/receiver 初次安装在Xposed Installer里勾选后需要重启 打开本App的界面, 勾选需要和谐的App
Reference:
http://developer.android.com/refere...ting(android.content.ComponentName, int, int)
https://android.googlesource.com/pl...va/android/app/ApplicationPackageManager.java
Some UI codes come from https://github.com/rovo89/XposedAppSettings
Download:
http://repo.xposed.info/module/com.rexpress.xposed.malwarebuster
Source Code:
https://github.com/twilightgod/MalwareBuster
? good thx for share
来自我的 LG-D802 上的 Tapatalk
This module really caught my eye but I can't find "my android tools". Is this app only available for specific devices or in some countries? Can you post a play store link to "my android tools"?
[size=-4]Sent from my Boeffla powered Slim (4.4.4) GT-I9300[/size]
https://play.google.com/store/apps/details?id=cn.wq.myandroidtools
bravo
nice and neat, thank you developer
Is it possible to enable this also for System Apps?
I can see in Amplify that Play Services tries to use Services I have disabled.
Thanks!
need help
@twilightgod Some instruction with details would really be nice. What does it do? Does it just stop the components from loading, shut them down, bypasses them, or what? I already use My Android Tools, awesome app.
I don't have a plan to hack system app, it's dangerous in my local test.
Google Services work well and costs not so much battery without GFW, disabling some of them while keeping basic functionality work will not help to your battery in if you don't have a stable way to get off GFW (like shadowsocks) in my experience.
Sorry, I didn't put much details in English.
The use case is, some apps will register service/receiver when it's running, so even if you disable bad service/receiver in my android tools, they will be registered again in next run, because my android tools will not run all the time in background.
This app will help to prevent them from registration.
Myandroidtools is flagged as malware/Trojan/PUP by 4 different virus scanners and together with appstart and agree to the permissions of the app is a script invoking "qihoo", searching for x86, x64 and a few more libraries on your device.
I seldom buy applications, but this one seemed fine before I got to know it.
Hi!
This module may be mainly interesting for developers. This module alone does nothing if not properly used together or within another app. Only use it if you know what you are doing.
Overview:
I created a Xposed module which overrides the Access Rule Checks within the SIMalliance Open Mobile API. These checks normally determine which app is allowed to access a SIM-card based Secure Element (SE) and which is not. Normally within the Secure Element (SIM card) there exists a special "Access Rule File" (also called "ARF") or a special card applet called "Access Rule Application Master" (also called "ARA-M") which has the AID A00000015141434C00) and (basically) contains application signatures and according access rules. So the maintainer of the Secure Element can define (and also update) the access rules with these mechanisms: which app is allowed to access the SE and which not. (see reference [1] for details below).
So while the access rules are securely stored in the hardware module (SE) the enforcement of these rules is done in software (within the Open Mobile "SmartcardService.apk"). And this is where this Xposed module hooks into. By using this module (or by integrating it into your app) you may access the SIM-card-based Secure Element with your app, even if the access rules within the SE would not allow it.
Here's the code:
https://github.com/johnzweng/XposedOMAPIOverrideSEAccessRules
This module does not globally disable the access rule checks but instead only grants full access to a single package name (app) which you manually have to define in code as TARGET_APPLICATION_PACKAGE_NAME.
More details and background story:
A few months ago the banks here in Austria started to roll out NFC-based tap'n'pay solutions which allow you to pay with your Android smartphone worldwide at every NFC-capable payment terminal. In contrast to Android Pay this is not a cloud-based software solution (using Host Card Emulation) but instead really uses a hardware-based secure element (like the chips used within EMV (chip'n'pin) plastic NFC banking cards). Austrian Banks decided to use Secure Elements located within the SIM-card (which is basically the same technology as your banking-card chip) so they don't need cooperations with all the phone manufacturers (and also not with Google), but only with the three mobile network operators (MNOs) here in Austria (which control all the SIM cards).
Unfortunately Google has not included an API in current Android which allows accessing SIM-card-based Secure Elements from an app (I guess they don't want banks and MNOs to develop their own independent payment solutions but instead want to push Android Pay). For this reason one of the largest smartcard manufacturers (Giesecke & Devrient - G&D) started to work on a third-party system API which is nowadays known as SIMalliance OpenMobile API (OMAPI). The SIMalliance is a group of industry players which want to push the use of Secure Elements in mobile phones. See also: Members of SIMalliance.
As this API is not part of official Android API the phone manufacturers (OEMs) have to include this API additionally on the phones. A lot of manufacturers do this already. You can check on your phone if this 3rd-party API exists by looking for these files:
/system/etc/permissions/org.simalliance.openmobileapi.xml
/system/framework/org.simalliance.openmobileapi.jar
/system/priv-app/SmartcardService/ (which hosts "SmartcardService.apk")
(and optionally in newer versions: /system/priv-app/UiccTerminal/)
As Google currently doesn't support this type of access to the SIM-card Secure Element you will not find this API on the Nexus phones. One exception was the Nexus 6 running Lollipop where Google included the SIMalliance Open Mobile API because they supported the Softcard (formerly Isis Mobile) wallet. After Google has acquired Softcard in 2015 they removed again the OpenMobile API from Nexus 6 in Android 6.
As I personally used a LG Nexus 5 and now use the Motorola Nexus 6 I started to work on integrating the Open Mobile API myself (which should be possible now on every phone since Android Lollipop (API level 21) as the TelephonyManager system class has got a few interesting new methods including one for sending APDUs over a logical channel to the SIM card: iccOpenLogicalChannel(String AID). As every phone running Android 5 or newer must implement this API you now can get the OMAPI working on every phone running Android 5 or newer (with minor restrictions). (Also the phone needs to have a special hardware wiring between the SIM card and the NFC chip - see "Single Wire Protocol" for details - to get a NFC payment working). But this is a different story which doesn't belong in this thread. For the interested, look at my Github repo which contains a fork of OMAPI working on unmodified Android versions (and two pre-built releases for OMAPI 2.05 and OMAPI 3.0 under the "releases" section - including a short How-To). This worked for me on a Nexus 5 and a Nexus 6.
But back to this topic:
After I had worked out the integration of OMAPI into Android 6.0.1 I finally was able to use tap'n'pay with my Nexus 6 using the banking card within my SIM card Secure Element. But as I am curious I was also interested in exploring my banking-card within the SIM Secure Element using a self-written app. This was when I realized that there is some kind of access control within the Secure Element which blocks my own test-app but not the app of my bank. (See reference [1] for details on these access rules.) To circumvent this I wrote this Xposed module and voilá, now we also have the possibility to talk with the Secure Element over OMAPI.
Final notes:
This Xposed module will only work if your device has the SIMalliance Open Mobile API (OMAPI) installed
This Xposed module may not work if the OMAPI on your device has been compiled using code obfuscation or was modified otherwise by your phone OEM (as the OMAPI is not part of official Android, every OEM may include its own version)
This Xposed module also may not work on other versions of OMAPI (it was tested with OMAPI v2.05 and should also work with OMAPI V3.0)
I hope this might be useful for someone. Have a nice day.
References:
[1] GlobalPlatform Device Technology - Secure Element Access Control (PDF)
[2] Open Mobile API specification - V2.05 (PDF)
[3] Open Mobile API specification - V3.0 (PDF)
[4] my Github repository for this Xposed module: XposedOMAPIOverrideSEAccessRules
[5] my Github repository with OMAPI fork for working on unmodified Android 5 or newer
I'm very impressed! Love your 'investigations'
I installed OMAPI 2.05 with adb on my xperia sp with cyanogenmod 13 (android 6.0.1).
After that I installed the elba-pay app, but it's not working. May you help me?
polo_joe said:
I installed OMAPI 2.05 with adb on my xperia sp with cyanogenmod 13 (android 6.0.1).
After that I installed the elba-pay app, but it's not working. May you help me?
Click to expand...
Click to collapse
Hi polo_joe:
This doesn't directly match the topic of this thread. But send me a PM then we can continue to communicate on a different channel (email, etc.). Most interesting would be a output of "logcat":
On your computer enter the command: "adb logcat -v time > logcat_debug.txt" in a terminal window then try to start the ELBA Pay app and afterwards look in the "logcat_debug.txt" logfile for errors.
john
androcheck said:
Hi polo_joe:
This doesn't directly match the topic of this thread. But send me a PM then we can continue to communicate on a different channel (email, etc.). Most interesting would be a output of "logcat":
On your computer enter the command: "adb logcat -v time > logcat_debug.txt" in a terminal window then try to start the ELBA Pay app and afterwards look in the "logcat_debug.txt" logfile for errors.
john
Click to expand...
Click to collapse
thanks, will do!
This is LineageOS built from official sources (cm14.1 and lineage-15.0 branches), featuring two patches that allow for Signature Spoofing and Network Location providers to be used outside of /system. These two conditions allow for easy installation of microG and related-services, along with the modular location provider platform UnifiedNlp.
I also include a few other extras (see ROM Features below), and experiment with things every now and then. Suggestions are welcome!
What is microG and UnifiedNlp? microG is a free re-implementation of Google's proprietary apps and libraries. UnifiedNlp serves as a replacement to Google Location Services and helps your device find its location (more info).
Benefits of microG and UnifiedNlp:
FLOSS
Lightweight
Modular
Can run with relatively-limited permissions
Improved device performance and battery life
Lower data usage
Faster GPS locks and better location accuracy
Significantly more control over privacy
No max-brightness bug (related to Google Location Services; when you wake the screen and it goes max-bright for a short period of time)
ROM Features:
Upstream up-to-date LineageOS builds
Location Providers can be installed outside of /system (intended for UnifiedNlp and allows microG to provide that)
Can toggle Signature Spoofing on or off for applications that can use it (intended for microG and FakeStore)
Native 493 DPI (see compatibility notes below)
Steven Black's Unified Hosts File built-in (gambling and fakenews filters)
Various Tweaks
Latest Nougat Version (recommended):
2017/10/31
Latest Oreo Version (testing):
2017/11/02
Older Versions:
Google Drive Archive
Instructions:
Can be found in the 2nd post down or by clicking here
Recommendations and Tips
Can be found in the 3rd post down or by clicking here
Known Issues
Can also be found in the 3rd post down or by clicking here
Reporting Problems and Issues
I'm not too knowledgeable in Android development and likely can't help directly with most ROM, kernel, and/or hardware issues
The best advice I can give is to post issues in this thread and hope others can share a solution, and/or report the issue upstream to LineageOS developers/maintainers if applicable
Changelog:
Nougat/cm14.1 (at the bottom of the page)
Oreo/lineage-15.0 (at the bottom of the page)
LineageOS shamu Changelog
Compatibility Notes:
The latest Nougat/cm14.1 version of this ROM passes SafetyNet (last checked: 2017/10/31)
The latest Oreo/lineage-15.0 version does not pass SafetyNet (last checked: 2017/10/29)
LineageOS and the default kernel support F2FS, however, the unofficial TWRP projects that support F2FS for shamu currently don't support F2FS decryption. Unless you know what you're doing, I suggest using a custom kernel with forced-encryption disabled if you want to have Data and Cache partitions with F2FS
493 DPI is used on this ROM. The default DPI for a Nexus 6 is 560. Some apps from Play Store may not show when the DPI is not set to an expected value. Theoretically, apps acquired from F-Droid and Yalp Store (when spoofing a N6) are not affected by this, but reports about this are welcome (a quick fix is wm density 560)
Other Notes:
This ROM should work fine with GApps, but I don't test this kind of set-up. If you choose not to use microG nor go GApp-less, I recommend using Open GApps
This ROM is signed with my key and the build type is userdebug
I use this ROM daily with microG and primarily to play Pokemon GO and Ingress; I should be able to notice any SafetyNet, location, or other issues quickly but all reports are welcome!
The patches and my notes for compiling (below) should be easily adaptable for any device capable of running LineageOS, or any ROM theoretically (change the Motorola manifest for other non-moto devices or remove it and supply your own vendor blobs if applicable)
Modifications Done:
Notes for Nougat/cm14.1
Notes for Oreo/lineage-15.0
Additional Support:
microG on xda-developers
UnifiedNlp on xda-developers
microG Website
microG Wiki
Other Resources:
How this ROM is built
My Nexus 6 configuration and other notes
Reddit guide for setting up microG + UnifiedNlp
Shadow53's notes on flashable zips for microG and Play Store, Google Cal/Contact sync, and other information
Shadow53's NO GAPPS initiative
XDA:DevDB Information
LineageOS for easy microG + UnifiedNlp, ROM for the Nexus 6
Contributors
espionage724
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-07-06
Last Updated 2019-01-06
Instructions
Initial Instructions:
Wipe device (TWRP -> Wipe all partitions and Format Data)
Flash ROM (copy the zip over to the Internal Storage of the N6 over USB)
Format Data and Cache to F2FS (optional; need a supporting TWRP; note you cannot decrypt F2FS-encrypted partitions in TWRP currently)
Flash GApps (optional; DO NOT do this if wanting to use microG)
Flash a custom Kernel (optional)
Flash Magisk (optional)
Reboot to System
Update Instructions:
Boot to TWRP
Flash updated ROM zip
Flash custom kernel (optional; but if you've used a custom kernel before, it'll be replaced with the default LineageOS one when you update; I recommend using the same kernel or an updated version of it)
Reboot to System
Core microG + UnifiedNlp Apps Package
This will provide the microG Services Core, Services Framework Proxy, DroidGuard Helper, NominatimNlpBackend, and MozillaNlpBackend APKs for convenience (these can also be downloaded from F-Droid)
These are the core applications needed to get the most out of microG and can be installed either over adb or just manually installed one-by-one on the phone
You will still need to read the instructions below in order to get things working
F-Droid will update packages as needed; no need to worry if the date on this package appears old
Compatible with both Nougat and Oreo builds
2017/10/31
microG Application Descriptions:
microG Services Core: Core services and UnifiedNlp (required)
microG Services Framework Proxy: Google Cloud Messaging (GCM) support
microG DroidGuard Helper: SafetyNet support
UnifiedNlp Application Descriptions:
NominatimNlpBackend: Looks up location based on geo-data (required)
LocalGsmNlpBackend: Notes cellular towers you connect to and refers to a local database (created from online sources) to determine location
LocalWifiNlpBackend: Scans nearby WiFi APs, links them to GPS coordinates, and stores them in a local database to determine location
Apple UnifiedNlp: Scans nearby WiFi APs and uses Apple's database to determine location
MozillaNlpBackend: Scans nearby WiFi APs and uses Mozilla's database to determine location (less work to set-up than LocalGSM and LocalWifi)
microG + UnifiedNlp Instructions:
Install F-Droid
Enable Unstable Updates (F-Droid Settings -> Expert mode -> Unstable updates; it's currently required to install the latest unstable microG Services Core)
Add the microG repository (visit https://microg.org/download.html)
Install the following: microG Services Core, NominatimNlpBackend, location backend(s) of choice, and other microG applications of choice for additional features (see the above list)
Enable Signature Spoofing for microG Services Core (Settings -> Apps -> ⚙ -> App permissions -> Spoof package signature)
Grant all permissions available for microG Services Core and location backend(s) of choice Settings -> Apps -> (application) -> Permissions)
Open microG Settings and enable desired features (if using Google SafetyNet, you must do ⋮ -> Advanced -> Use official server)
Configure UnifiedNlp Settings (check Nominatim from address lookup backends, and check desired location backend(s) under location backends)
Verify Self-Check has confirmation on all checks (UnifiedNlp being registered in system may require a reboot to start working)
Recommended microG + UnifiedNlp Packages:
Install microG Services Core, microG Services Framework Proxy, microG DroidGuard Helper, NominatimNlpBackend, and MozillaNlpBackend
If you want to run location resolution locally, install LocalGsmNlpBackend and LocalWifiNlpBackend instead of MozillaNlpBackend, or alternatively, install all three and keep MozillaNlpBackend disabled until required
App Store Notes:
You'll likely either want Yalp Store and FakeStore, or legitimate Google Play Store
If you're trying to avoid Google services, Yalp Store + FakeStore is what you'll want
Play Store will likely be wanted if you want a higher chance at being able to use paid apps and IAP (no guarantees; untested)
Play Store needs to be installed as a privileged application to work properly, and also assigns itself high permissions
You can also choose to install Play Store and Yalp Store; note that FakeStore should not be installed at the same time as Play Store though
You can also use any other app store(s) instead of Play Store or Yalp Store or even choose to not install a store at all, but any apps you install that check if Play Store exists will need FakeStore installed still
Yalp Store Application Descriptions:
FakeStore: Fakes the existence of Google Play Store for applications that require it
Yalp Store: Allows downloading and updating of apps from Google Play Store, serves as an alternative to official Google Play Store, and if signed-in with your real Google account, allows for paid-apps to be downloaded; apps that do license checks post-install will fail, and IAP isn't possible currently
Yalp Store Instructions:
Open F-Droid
Install FakeStore and Yalp Store
Enable Signature Spoofing for FakeStore (Settings -> Apps -> ⚙ -> App permissions -> Spoof package signature)
Configure Yalp Store (⋮ -> Settings -> Pretend to be a Nexus 6; this is potentially required to avoid this)
Download desired applications
Enable only updating of applications acquired through Yalp Store (optional; sometimes versions differ from Play Store and F-Droid; ⋮ -> Settings -> Change app white list -> (select apps), and also set the Black or white list of apps for update to Only the chosen apps will be checked for updates)
Play Store Application Description:
Phonesky.apk: This is the name of the Play Store apk; allows for traditional Play Store behavior; apps that do post-install license checks and IAP are personally untested (feedback from anyone who tests this would be awesome)
Play Store Instructions:
Download the latest open_gapps-arm-7.1-pico archive (GitHub or the main site) (use 8.0 for Oreo; untested)
Extract it somewhere temporary
Go into the Core folder and find vending-all.tar.lz
Extract its contents
Go into the vending-all/240-320-480/priv-app/Phonesky folder
Take Phonesky.apk and move it somewhere temporary or just note its location
Reboot your device to Recovery
Mount /system on the Android device and use adb push to copy Phonesky.apk from local storage to /system/priv-app/Phonesky.apk
Reboot to System
Issues, Recommendations, and Tips
Known Issues (Nougat/cm14.1):
PowerHAL errors flood the log when using a custom kernel with mpdecision removed such as FrancoKernel
Known Issues (Oreo/lineage-15.0):
Cannot decrypt storage from TWRP if using Encryption
vndbinder SELinux denial and crash occurs every 5 seconds (should be fixed with 2017/11/01)
Double-tap to wake is unreliable
Security patch level is old (August 5, 2017)
Recommended Apps:
Email: K9 (incompatible with webmail encrypted providers like Tutanota and ProtonMail)
Store: F-Droid, Yalp Store
Calendar and Contacts: DAVdroid (with a self-hosted Radicale server or a provider like Posteo)
Social: AndStatus with Mastodon or GNU social (choose a server or self-host one)
Chat: Conversations (choose a XMPP server or self-host one with something like Prosody)
Browser: Firefox Klar (Klar is on F-Droid and is also known as Focus; both are the same thing)
Weather: Forecastie
Password Database: KeePassDroid
2FA: andOTP
Maps: OsmAnd~
Recommended Settings:
Developer Options -> Disable Mobile data always active (Oreo/lineage-15.0)
Oreo/lineage-15.0 Findings (2017/10/29):
AsteroidOS Sync with a LG G Watch (dory) seems to work fine
A good bit of LineageOS-specific settings are missing (no Caffeine tile, no Expanded Desktop settings, no lockscreen digit scramble)
SELinux is Enforcing by-default
Only one wallpaper is included
When previewing a Ringtone, it starts out super quiet, then goes full volume (full being whatever the Ring volume is set at)
Thanks for the support.... What are some benefits of
"microG and UnifiedNlp" and/or how is different? I read the link about Floss which is really cool.
Sent from my Nexus 6 using Tapatalk
andrewjt19 said:
Thanks for the support.... What are some benefits of
"microG and UnifiedNlp" and/or how is different? I read the link about Floss which is really cool.
Click to expand...
Click to collapse
I notice GPS locks and accuracy seem to be a bit better; I use the LocalGSM and LocalWifi backends.
I particularly like that microG doesn't require a lot of permissions. Plus since I don't entirely use a lot of Google services, I don't need to have them installed or running in the background either.
I also like the better control over location. With the local backends, my location data doesn't have to be sent off to an online server somewhere. I grab a large database for cell towers from OpenCellID and Mozilla, and that has me covered for the GSM backend. And for Wifi, I just scan for access points as I travel around and build my own database. For first-time visits, I have to rely on the GSM backend first, but for return visits, the Wifi backend should work.
And finally, it's also just kind of neat using this kind of set-up I've tried to go without GApps in the past, but ever since I started playing Pokemon GO and Ingress, I didn't like having to lose those games. Plus there was a few apps I wanted from Play Store too. But now, I can be without GApps, and also have PoGO and Ingress, and even more surprisingly, I pass SafetyNet.
New build available; changes include resync with sources, 493 DPI set (I don't believe this will be a problem outside of Play Store app compatibility; in which case, it can be set back to 560 from the Local Terminal), and the target build changed from userdebug to user.
New build: Resync, previously removed default apps are re-added, and now the ROM includes Steven Black's Unified Hosts File built-in with the gambling, fakenews, and porn filters enabled
Interesting.... I may try this out.
For those who don't know, I provide flashable zips that ease the installation process of microG and/or the Play Store. I'm actually the site linked to on that Reddit post (kinda curious who linked to me).
The microG zips should completely check all boxes in the self-check checklist EXCEPT for the one about setting up the UnifiedNlp backends. The zips come with the Mozilla location backend and the Nominatim geocoder backend, I just haven't figured out how to get them enabled yet.
Those who are stuck using Google to sync contacts/calendar have an add-on zip that can be flashed to be able to sync those. Note that, as of last testing, you may need to go into Settings > Apps and manually enable permissions on one or both sync adapters in order to get it to work.
Finally, @espionage724, if it helps any I also provide a standalone PlayStore zip for people who want to install microG as a user app. It is the patched PlayStore from NanoMod that *should* support (in-)app purchases.
Links:
My own No Gapps/microG setup guide: https://shadow53.com/no-gapps/setup-guide/
FAQ for common issues while setting up microG:
https://shadow53.com/no-gapps/faq/
Table displaying alternatives to "all" Google apps:
https://shadow53.com/no-gapps/alternatives/
And the zip installer downloads
https://shadow53.com/no-gapps/downloads/
New build (2017/07/09) available: Resync with sources, and Steven Black's host file now only uses the default lists (removed gambling, fakenews, and porn filters)
Shadow53 said:
Interesting.... I may try this out.
For those who don't know, I provide flashable zips that ease the installation process of microG and/or the Play Store. I'm actually the site linked to on that Reddit post (kinda curious who linked to me).
The microG zips should completely check all boxes in the self-check checklist EXCEPT for the one about setting up the UnifiedNlp backends. The zips come with the Mozilla location backend and the Nominatim geocoder backend, I just haven't figured out how to get them enabled yet.
Those who are stuck using Google to sync contacts/calendar have an add-on zip that can be flashed to be able to sync those. Note that, as of last testing, you may need to go into Settings > Apps and manually enable permissions on one or both sync adapters in order to get it to work.
Finally, @espionage724, if it helps any I also provide a standalone PlayStore zip for people who want to install microG as a user app. It is the patched PlayStore from NanoMod that *should* support (in-)app purchases.
Links:
My own No Gapps/microG setup guide: https://shadow53.com/no-gapps/setup-guide/
FAQ for common issues while setting up microG:
https://shadow53.com/no-gapps/faq/
Table displaying alternatives to "all" Google apps:
https://shadow53.com/no-gapps/alternatives/
And the zip installer downloads
https://shadow53.com/no-gapps/downloads/
Click to expand...
Click to collapse
Thanks for the links and information!
Last Updated 2017-07-09
The Latest Version is not found on google drive.
gmzhouh said:
Last Updated 2017-07-09
The Latest Version is not found on google drive.
Click to expand...
Click to collapse
Thanks; I thought that URL looked like it was missing a bit of text, but it loaded fine for me when I added it at the time.
Fixed the URL in the first post, and it (2017/07/09) can be found here: https://drive.google.com/file/d/0B9CekGWwY1hjMEdhYmJoeGE2TlU/view?usp=sharing
New build (2017/07/11); just a resync from sources
Do I need to use MicroG to pass Safetynet? And do I need to use f2fs?
xNotta said:
Do I need to use MicroG to pass Safetynet? And do I need to use f2fs?
Click to expand...
Click to collapse
I believe you'll need either microG (and DroidGuard) or GApps to pass SafetyNet, otherwise, apps can't check for SafetyNet compatibility (Magisk's test throws an error if I try doing the check without either).
As for F2FS; you don't have to use it. By-default, /data and /cache partitions use ext4 which works fine.
espionage724 said:
I believe you'll need either microG (and DroidGuard) or GApps to pass SafetyNet, otherwise, apps can't check for SafetyNet compatibility (Magisk's test throws an error if I try doing the check without either).
As for F2FS; you don't have to use it. By-default, /data and /cache partitions use ext4 which works fine.
Click to expand...
Click to collapse
Thank you.
I was going to use BeansGApps full to flash gapps.
So, I can just ignore all the MicroG stuff and still pass Safetynet and have a working rom that plays Pokemon go?
I'm not ready to try f2fs yet.
xNotta said:
Thank you.
I was going to use BeansGApps full to flash gapps.
So, I can just ignore all the MicroG stuff and still pass Safetynet and have a working rom that plays Pokemon go?
I'm not ready to try f2fs yet.
Click to expand...
Click to collapse
Yep you can ignore the microG stuff, flash a GApps package, and pass SafetyNet, but if this is your only objective, you can also accomplish this on most other ROMs (including official LineageOS).
On the note of Bean GApps though, unless there was an update, the June Full package is broken. You'll have to use either May's Full package, or June's Mini package. I'd probably just recommend a variant of Open GApps depending on what packages you want.
eh this is great thanks, and thanks the people with microG and UnifiedNlp too. I didn't know anything about these. This is great
I trust that this will work fine for Verizon users?
Christopher8989 said:
eh this is great thanks, and thanks the people with microG and UnifiedNlp too. I didn't know anything about these. This is great
I trust that this will work fine for Verizon users?
Click to expand...
Click to collapse
I believe it should be fine for Verizon users (at least as fine as a regular LineageOS build would be anyway), but I haven't tried it.
New build (2017/07/13): https://drive.google.com/file/d/0B9CekGWwY1hjcWlFX01sRk12MmM/view?usp=sharing
New build (2017/07/16): https://drive.google.com/file/d/0B9CekGWwY1hjYXFyX0o2QWlJRGs/view?usp=sharing
I believe upgrades will be unaffected by this, but for fresh installs, I forgot to set 493 DPI. If you want this (or any other value; replace 493), you can run the following over adb shell while booted in TWRP (can be at any point after you flash the zip but before rebooting into System):
Code:
mount '/system' && sed -i 's/'ro.sf.lcd_density=560'/'ro.sf.lcd_density=493'/g' '/system/build.prop'
Or you can do it after booting into the ROM via normal means:
Code:
wm density 493