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.
Related
Hi,
I've been doing some interesting reverse engineering work and came across this Xposed module:
http://forum.xda-developers.com/xposed/modules/xposed-disablesignaturecheck-t2783480 to disable signature checking.
This is a an awesome module, but didn't quite do what I needed in that I wanted to have the system believe that my patched APK was 100% original. To this end I built an Xposed module to spoof the JAR verification at a very low level, which allows for all sorts of interesting possibilities.
This is a research tool and should be used accordingly, as with any such subversion of system behaviour, this is not something you want to leave enabled!
I've added a UI based on the same mechanism of the DisableSignatureCheck module to enable / disable the spoofing behaviour.
The module source can be found on my GitHub page:
https://github.com/sweetlilmre/JARVerificationSpoofer
Comments and criticism are welcome, I hope that someone finds this useful.
-(e)
Thanks I will look at this, sounds promising.
Hope you find it useful.
Where the apk. Or did i miss something
Source is on github.
Awesome work!
@sweetlilmre I am developer of DisableSignatureCheck (now XInstaller) and it is open source. Maybe you would like contribute this feature to this module also?
Sounds like a good idea. Where is the source?
https://github.com/pylerSM/XInstaller here
Thanks. I will try to send a pull request soon.
Isn't it the same as the first patch in Lucky Patcher? It would be awesome to implement all its patches as xposed modules.
Thanks for the pull, it's now integrated in the Xinstaller 3.0 modul. ?
CHEF-KOCH said:
Thanks for the pull, it's now integrated in the Xinstaller 3.0 modul. ?
Click to expand...
Click to collapse
Hi,
I see that this has been added to XInstaller, but as "afterHookedMethod", not "beforeHookedMethod".
The original method will throw a "invalidDigest" exception, if executed i.e. not desired behaviour.
I have submitted a pull request to fix this.
-(e)
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
I will add all possibly fixes that are added to switch. This is only a compilation of the contributions that we have found in the official forum of switch root.
UPDATE:08/06 TEMPLATE TO DOLPHIN. THX @SvenDaHacker64 This dolphin has more options than the original, and run at 30 FPS DBZ BT3 (1080p)
08/05 Added Joycon controls for kodI & USB INFO TO ACTIVATE ETHERNET..
APKS:
dock:
Launcher:
--
Hal launcher:
HALuncher
ATV Launcher:
ATV Launcher Free
--
Keyboard(Works with joycons):
LeanKey Keyboard
--
Joycons:
Joycon enable
--
Ethernet:
USB DEVICE INFO TO ACTIVATE USB ETHERNET AND
Ethernet! by @USBhost
---
Additional features:
THIS APP to get rid of the BLACK BORDERS in fullscreen mode
--
FPS COUNTER
--
I WANT PLAY FORTNITE:use GLTools to spoof an Adreno 630, and enable Magisk Hide for the game.
--
Screenshots(or maybe use an Xposed module to enable them even when they're "not allowed")
--
Screen rotation OR Screen Rotation
--
NVIDIA GameStream without the lag: Moonlight Game stream ONLY NVIDIA CARDS.
--
Without NVIDIA CARDS:Steam Link
--
FILES FLASHEABLE
I HAVE SOLVED THE PROBLEM OF THE REVERSED CONTROLS BUT WE CONTINUE TO HAVE L and R flat:
JOYCON FIX FOR GTA WITH STYLE SWITCH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Joycon Fix Flasheable:
Joycon Fix Flasheable(L3 and R3) by Switchroot official site
Joycon Fix GTA:
--
Fix GTA With Invert Controls STYLE XBOX/PS4
--
Bluetooth Auto connect (Lag and autoconnect)
--
Magisk-Root:
Magisk v19.3
--
Uninstaller:Uninstaller Magisk
--
XPosed framework with Gravitybox [O] (Recomend for Reboot without hekate)I HAVE GRAVITY BOX AND XPOSED AND I HAVE NOT HAD A BOOTLOOP BUT VARIOUS USERS HAVE REPORTED THAT THEY HAVE HAD BOOTLOOP, MAYBE IT HAD BEEN THE INSTALLATION ANOTHER APK IN BAD CONDITION. I DO NOT RECOMMEND INSTALLING IT AT YOUR RESPONSIBILITY.
Many have been able to boot straight into twrp from android by enabling developer options and enabling advanced reboot (tapping and holding power button > reboot > recovery).
https://ibb.co/dtTM7y7
Systemless Xposed
Gravitybox [O]
Also, make sure to mount /system in TWRP before flashing OpenGApps, the joycon fix (the GTA one should work for other games, such as TR2), or other zips.
--
FOR KODI:
JOYCON CONTROLLER IN KODI
No root
-
Directory:Android/data/org.xmbc.kodi/files/.kodi/userdata/addon_data/
drag and drop "peripheral.joystick"
The folder is hidden, use ES file manager, or any other of this option I use that one.
Joycon controller for kodi v2
-Fix Directional PAD.
-
Root:
Screen Shift
-
Dolphin:
Dolphin original:https://play.google.com/store/apps/details?id=org.dolphinemu.dolphinemu&hl=es
https://es.dolphin-emu.org/download/
Dolphin weihuoya: https://github.com/weihuoya/dolphin/releases <- I use this
Template
Save as <GameID>.ini and copy to /storage/emulated/0/dolphin-mmj/GameSettings
Example: New Super Mario Bros. Wii, it'll be SMNP01.ini , GMSP01.ini for Super Mario Sunshine.
Tips:
Lockcreen for dock:
Settings > Security & Privacy > Screen lock > None
To remove the Navigation Bar:
https://play.google.com/store/apps/d...on.bar.remover
To add the Navigation Buttons to Quick Settings:
https://play.google.com/store/apps/d...id.shortcutter
Mount FAT32
Mount FAT32
Credits:
@rovo89
@Tungstwenty
@topjohnwu
@langer hans
@bylaws
@AnkitChowdhury
@Gavin_Darkglider
@nastys
I use this app to get rid of the black borders in fullscreen mode: https://play.google.com/store/apps/details?id=com.conena.navigation.bar.remover
FPS counter: https://labs.xda-developers.com/store/app/com.n0n3m4.gltools
Fortnite: use GLTools to spoof an Adreno 630, and enable Magisk Hide for the game.
Screenshots: https://play.google.com/store/apps/details?id=com.symcoding.app.screenshots (or maybe use an Xposed module to enable them even when they're "not allowed")
Screen rotation: https://play.google.com/store/apps/details?id=org.crape.rotationcontrol
NVIDIA GameStream without the lag: https://play.google.com/store/apps/details?id=com.limelight
(non-NVIDIA or non-Windows users can use SteamLink: https://play.google.com/store/apps/details?id=com.valvesoftware.steamlink)
Also, make sure to mount /system in TWRP before flashing OpenGApps, the joycon fix (the GTA one should work for other games, such as TR2), or other zips.
nastys said:
I use this app to get rid of the black borders in fullscreen mode: https://play.google.com/store/apps/details?id=com.conena.navigation.bar.remover
FPS counter: https://labs.xda-developers.com/store/app/com.n0n3m4.gltools
Fortnite: use GLTools to spoof an Adreno 630, and enable Magisk Hide for the game.
Screenshots: https://play.google.com/store/apps/details?id=com.symcoding.app.screenshots (or maybe use an Xposed module to enable them even when they're "not allowed")
Screen rotation: https://play.google.com/store/apps/details?id=org.crape.rotationcontrol
NVIDIA GameStream without the lag: https://play.google.com/store/apps/details?id=com.limelight
(non-NVIDIA or non-Windows users can use SteamLink: https://play.google.com/store/apps/details?id=com.valvesoftware.steamlink)
Also, make sure to mount /system in TWRP before flashing OpenGApps, the joycon fix (the GTA one should work for other games, such as TR2), or other zips.
Click to expand...
Click to collapse
Thanks nastys, I added this.
I can't figure out how to get Fortnite working. I did magisk hide on the installer and used GLTools to spoof an Adreno 630 GPU but still says "device not supported".
Shadowehh said:
I can't figure out how to get Fortnite working. I did magisk hide on the installer and used GLTools to spoof an Adreno 630 GPU but still says "device not supported".
Click to expand...
Click to collapse
Activate the first option, and try again.
Chiveta said:
XPosed framework with Gravitybox [O] (Recomend for Reboot without hekate)
Click to expand...
Click to collapse
Gravitybox is NOT supported on custom roms like LineageOS. It has caused bootloops for many people who didn't read the dev's following warning. From the link you provided:
"- SHOULD NOT be used with custom ROMs like Lineage, AOSPA, or any other derivative - it makes no sense since the most of the features are already in the ROM (may cause conflicts and unexpected behavior)"
Many have been able to boot straight into twrp from android by enabling developer options and enabling advanced reboot (tapping and holding power button > reboot > recovery). Also, the system UI tuner built I to Lineage already provides many of these features; you just have to explore the settings app a bit.
Thanks for this well organized post though. The main thread has many good tips and it's nice having someone consolidate them in one thread.
I haven't installed any Joycons fixes yet. Do i install all of them or is there certain ones that i need?
For Kodi ive found a better solution first Root your Android lineage
https://download.lineageos.org/extras
Download super su arm64 for lineage 15.1
Install Zip via twrp
Go to développer mode activate Root for application
Install this app screenshift https://www.google.com/url?sa=t&sou...BMAB6BAgMEAM&usg=AOvVaw3CNZyMo4Q2G1SZUUN2iUGm
And create a profil 1280 720 activate and go in Kodi everything work perfecto
You Can create a profil 1920 1080 to go back normal
Btw Quick question can't find this path : Directory:Android/data/org.xmbc.kodi/.kodi/userdata/addon_data/
drag and drop "peripheral.joystick"
Some help ?
Count_NOOBula said:
Gravitybox is NOT supported on custom roms like LineageOS. It has caused bootloops for many people who didn't read the dev's following warning. From the link you provided:
"- SHOULD NOT be used with custom ROMs like Lineage, AOSPA, or any other derivative - it makes no sense since the most of the features are already in the ROM (may cause conflicts and unexpected behavior)"
Many have been able to boot straight into twrp from android by enabling developer options and enabling advanced reboot (tapping and holding power button > reboot > recovery). Also, the system UI tuner built I to Lineage already provides many of these features; you just have to explore the settings app a bit.
Thanks for this well organized post though. The main thread has many good tips and it's nice having someone consolidate them in one thread.
Click to expand...
Click to collapse
Sorry to hear all this. but it worked for me and I've never had a bootloop problem. I have the photos here.
jaycounet said:
Btw Quick question can't find this path : Directory:Android/data/org.xmbc.kodi/.kodi/userdata/addon_data/
drag and drop "peripheral.joystick"
Some help ?
Click to expand...
Click to collapse
The folder is hidden, use ES file manager, or any other that gives you this option I use that one.
Oh! Thanks for photo evidence. It looks as if the latest version does support Lineage. I personally experienced a bootloop on gravity box for android 7 and kicked myself for not making a twrp backup. I only found out it wasn't supported on custom ROMs like lineage when I read the dev's description listed in the link you provided.
Out of curiosity, what gravity box tweaks do you use that aren't built into lineage?
Count_NOOBula said:
Oh! Thanks for photo evidence. It looks as if the latest version does support Lineage. I personally experienced a bootloop on gravity box for android 7 and kicked myself for not making a twrp backup. I only found out it wasn't supported on custom ROMs like lineage when I read the dev's description listed in the link you provided.
Out of curiosity, what gravity box tweaks do you use that aren't built into lineage?
Click to expand...
Click to collapse
Gravitybox [O] 8.5.4, Because we are in oreo, surely that's why you had bootloop when installing the Gravitybox, even the Xposed is important to know the SDK(Android version) that has our firmware and always check everything. install the Systemless Xposed
Phillyrider807 said:
I haven't installed any Joycons fixes yet. Do i install all of them or is there certain ones that i need?
Click to expand...
Click to collapse
I'm sorry for the delay, you should install the one you like the Switch Style or XO / PS4 Style. The realease official only fixes the L3 and R3, the Analog didn't work for me.
Chiveta said:
Activate the first option, and try again.
Click to expand...
Click to collapse
I have already done that. I instead did the manual installation via TWRP which fixed the issue. The last question I have is that do I have to do the same thing with the actual Fortnite game as well?
PingSpoofer said:
I have already done that. I instead did the manual installation via TWRP which fixed the issue. The last question I have is that do I have to do the same thing with the actual Fortnite game as well?
Click to expand...
Click to collapse
In theory you should read your joycon, verify that the triggers work for you, if not, you should flash another zip, Style switch or XO / PS4. and in case the controller does not work, it uses octopus.
Any fix for Zr and Zl as RT and LT they dont work for me on GeForce now
@Chiveta The link to Screen Shift app doesn't work..at least not for me.
Googling it I happened to find the app to change resolution and so on...
Now I'm excited, maybe I can fix my screen with it. I have a sony 4k 120 hz tv and no matter how often I dock and undock the switch I get a "scrambled up" output on tv...though tv says it gets 1080p..
Great thread. It would be nice if the op was compressed in hide tags to make it easier to go through though.
Also I know I came here looking for useful stuff for android-switch, and I figure I post this here buried from the main thread:
Count_NOOBula said:
12 Helpful Tips
.. for Switch users new to Android.
1. Place a battery percentage indicatior in the status bar so you can see the number increase in real time while charging. This is a temporary workaround; the current build doesn't indicate whether the system is charging while charging it.
Head to Settings > Battery > switch on Battery Percentage. I often play while charging, so it's helpful seeing this number go up simply by glancing at the status bar.
2. Use TWRP to create a backup image file of the entire android OS, so you can easily restore to it if an app, magsik or xposd module causes any issues, especially issues that cause bootloops. I also recommend using TWRP's built in file manager to move files back and forth between the 2GB fat32 partition and android's own storage system << this is helpful if you find FTP-ing a bit painful in certain circumstances.
Head to TWRP and tap Backup > Slide to initiate backup. (Tap the words "autogenerate" to rename your backup prior to initiating the backup. Note: none of the files accessible via the file manager will be deleted or backed up. Just the OS itself, instslled apps along with their data and settings (e.g your notes in a notes app). To access the file manager, tap Advanced on TWRPs home screen (you can move, copy and rename files and even delete magisk module folders if a particular magisk module is causing bootloops)
You can move this TWRP backup to a PC and even to another switch and restore it to move all your stuff to a second switch. TWRP backup images are stored on the non fat32 partion (fat32 partition is the 2GB partition that shows up on your PC when plug in this LineageOS SD card). To move this backup to the PC, install any free ftp or WiFi file transfer app and navigate it to /sdcard/TWRP/backups.
3. (optional but tricky) Uninstall System Bloatware
...RAM and other resources are precious. As amazing as this build is, the devs have left in some useless apps aren't needed on the Switch like Microsoft email exchanger, phone , call management and default SMS app, contacts app, LineageOS Updater (useless on unofficial builds), call log etc. I used Titanium Backup to uninstall these system apps. The process is tricky cuz system apps are notoriously difficult to remove unless you use apps like these. Also, uninstalling the wrong system app can bootloop your system so don't do this if you don't know what you're doing. MAKE A TWRP BACKUP BEFORE "DEBLOATING". I've saved over hundreds of MBs of ram and improved battery life by uninstalling bloatware that wastes CPU cycles.. Bloatware reduces performance in apps like dolphin, nom gaming apps and even sucks battery while the screen is off, esp annoying since this build doesn't CURRENTLY support deep sleep). A novice user should ONLY uninstall common sense apps (call log backup and restore, exchange, updater etc). And ALWAYS backup your ROM using TWRP beforehand to recover from bootloops secondary to accidental deletions.
4. Backup your apps AND data
..all thanks to Titanium Backup
..you can also restore app data from a TWRP backup using this app, give you two excellent backup options.
5. Enjoy system wide dark mode and other themes
..all thanks to Substratum
...if you've installed Xposd, download "Force Darkmode Oreo" < download via Xposd or the website.
..you can download tons of free and paid themes for Substrstum, including true black and gray themes, and give your eyes a break. System wide dark mode is coming in Android 10 but just because we're all on 8.1, doesn't mean we need to blind our eyes playing at night.
6. Use AdAway to block ads at the host level. Import more lists from the EasyList site. Tap and hold on the txt link then paste them in the app's sources.
7. Use AFwall+ or other firewalls, to allow only select apps access to the internet
8. Use Nova Launcher and download icon packs. The built in app launcher (called Trebuchet) has no customkzariom features but still uses over 160MB of RAM in this build. RAM is key for many demanding apps (eg depth of field/field of view in android games like PUBG, and even in Dolphin games) so every MB helps. Plus a new lanucher like Nova gives you tons of options to customize things to your liking. After installing a launcher and setting it as default, you can uninstall Trebuchet using a bloatware uninstaller like Titanium Backup.
9. Use AppOps (free or pro) to protect your privacy through fine grained permission control (or use the much more limited but still useful Privacy Guard << built into Lineage, simply search for it in settings). This feature is built into android but because unlike Apple, Google makes money through tracking, they've deliberately buried it by giving it no UI a user can easily control. This app provides that UI and simple switches to block clipboard access, prevent apps from waking up or running in the background, preventing unauthorized apps access to the SD card etc. Google officially gives users only like 20% of the privacy variable switches you can toggle off in this app. HIGHLY recommended.
10. Install XPOSD and an xposd module called Prevent Running, to prevent all your installed apps from randomly waking up in the background and wasting valuable RAM and other resources. (Note: may affect notifications so don't use it on messaging apps etc)
11. See which apps are sucking up your ram by using the built in RUNNING SERVICES setting. Head to Settings > System > About Tablet. Then scroll down & tap on the "build number" SEVEN times until developer options are enabled. Then head to Settings > System > Developer Options > Running Services.
12.Boost android launch time by preventing apps from automatically launching at startup. Once you've enabled Developer Options, head to Settings > System > Developer Options > Memory> scroll down and tap "Apps started on boot". Now you'll see a list of apps that have been configured to start up as soon as Android boots.
Alternatively, you can search in Settings for Privacy Guard > tap the three dots in the top right > then Advanced > now swipe all the way to the right til you see "run in background" and "bootup". You can now slide off each app you don't need as soon as the system boots. You can also prevent apps from running the background. You'll see a huge boost in boot times esp if you have tons of apps installed.
Bonus Tip: Upgrade the web rendering engine "Webview". This build has version 72.xxxx while the latest version from google as of July 29th is v. 76.xxx. Since most apps including the browser use Webview, upgrading will pay off. Not only does it boost browsing speed, but it's also essential to be keep our Switch STADIA -Ready, cuz Stadia will rely on the latest webview APIs found in Chrome. I don't use chrome, so this is helpful for people like me. This may be a noob opinion, but i think Stadia will likely rely on the latest Webview APIs, not necessarily the Chrome app. Even if you don't care about Stadia, upgrading webview will boost the internal web browsers of all your apps.
Install the latest Webview apk from the playstore/apkmirror (arm64 variant) > enable developer options > in develop options, you'll find an option to select Webview versions > switch from v72 to v76. Run browsing benchmarks and enjoy the boost! You can uninstall the older v72 webview using Titanium Backup.
..................................
I'd appreciate it if someone started a thread listing tips and recommended apps/tweaks that could really help switch users. For now, enjoy these tweaks from one noob to another.
Thanks to everyone who posted on this thread to help me and esp to the Switchroot team for their wizardry.
Click to expand...
Click to collapse
If I ever get my switch set up, I may start a thread for tips and such for using android on switch.
how do you use joycon enable? even if it works, the button layout is messed up after that.
Full Guide and Download, on GitHub, HERE.
This is for a ROOTED version of Windows Subsystem For Android with the Google Play Store, Services and framework installed. Essentially giving you a rooted android device inside you Desktop. Great for DevOps, CyberSec & DefEng. (Defense Engineering)
Key Points:
-For best results fork and clone.
-SHOULD also work by simply downloading.
-Uses Magisk by @topjohnwu for root.
-Uses The Open GApps Project for playstore.
-Your system MUST support Hyper-V.
-Simple Installation process.
-Working ADB.
-Open-Source (yes, if you want to help, please do - just go check out the Github.
TO-DO:
-System UI
-Allow for replicating Device-Specific Set-Ups (I.e, Mocking a particular devices' security framework, for instance, emulating KNOX, Google FRP, QTI, Etc.)
-VPN Fix
-Cellular network (for this who want to test their apps on live networks)
- Make it self-updating.
Please Post any issues on the github or here and be as detailed as possible and include screenshots. May take some time for a response but will do my best.
Good luck -
-k0mrad3
Never mind, my bad
Hack & install method is so dirty
Repo removed by Github. Might want to find another host