Yesterday I installed xposed and a few modules: GravityBox, SystemUI Patcher, Xperia Dialer Mods and XperiaFMwoHS. Now the 2 vpn type apps that I have on my phone (private internet access and DNSet Pro) no longer work: the warning popup message when making a vpn connection no longer appears and no connection is made - the apps hang or crash.
I don't know if this was caused by xposed, but I didn't make any other changes to the phone since last time I used the vpn apps without problems.
Can anybody help? Thanks!
It looks like the problem may be with the latest rom update (eXistenZ Ultra 3.3.0). I reinstalled the update, without xposed enabled and I have the same problems with vpn apps ...
I was being stupid .... I figured it out. It was because speedydroid removed VpnDialogs.apk :silly:
Just curious to know if any moto x users have tried some of the more popular xposed modules. Is this device aosp enough to expect most, if not all, modules to work properly?
Most of them work. I'm using app settings, gravity box, Halo FloatingWindow, Xprivacy, and adaway without problems.
I use GravityBox, Greenify, Exchange Security Bypass, and AppOps. They all work great.
Hi guys,
I actually made this module for my personal own use, but who knows, someone here might find it useful as well.
PIE & Magisk v19 Compatible Update
https://drive.google.com/file/d/1-Nw6xHIhOPz06j4FqD-geAnMCz2NzPKX/view?usp=drivesdk
UPDATE NOTES :
OOS Nougat & Oreo User might not be able to find system app on Battery Optimisation list, you can work around this by using 3rd party app like Greenify or Naptime to open Doze Whitelist, you will see Google Play Services already listed as "Optimised App". Or go to App Info from setting, choose "Battery" and scroll down to "Battery Optimisation" - if the module work, it should written "Optimising Battery Use"
OREO User, PLEASE USE OREO version. v6 Update is already in the Magisk Repo.
BACKGROUND :
I always find that Google Play Services is way too aggresive in doing its activities in the background. And its no secret that this main services from google is oftenly one of the main culprit for the sub par battery performance on most stock or even custom ROM across devices.
THE IDEA & THE BARRIER :
Starting in Android 6.0, Google has introduced one of my favorite features in battery saving : DOZE (quick read about this Here), it help us to make apps go into a "shallow" hibernation state. Where it use less energy but retain it's functionality.
Thing is, this feature is NOT applicable for Google Play Services. Thus, it cant help you to save the battery from being eaten by Google Play Services. And this is not for no reason of course (read SIDE EFFECT/NOTE section bellow for further explanation)
THE SOLUTION :
Quick study (if you are interested, one of the discussion can be found Here) reveal that Google put simple configuration is /system/etc/sysconfig/google.xml that WHITELISTING Google Play Services from the DOZE Mechanism.
So to make DOZE able to work on it, we simply need to remove the whitelisting.
This is WHAT THIS MODULE DO - SYSTEMLESSLY (obviously)
By installing this module, you can move Google Play Services from the "App Not Optimised" list to "App Optimised" which mean DOZE mechanism will work its magic on Google Play Services, thus should saving you more juices/batt throughout the day.
THE SIDE EFFECT/NOTE :
Saving energy never come without side effect. Same goes with this method.
By enabling Doze on Google Play Services, it will theoritically delay/pause some it's services. Most noticeable might be the GCM (cloud messaging) services.
App that use this services might experience delay in notification when Doze already kick in.
Although, in my experience (i use this mod on all of my three devices) my notif for LINE, WhatsApp and Telegram (my main comm app) is never been delayed. ( I put all these apps in my whitelist btw)
The one i noticed had slight delay is GMail. But i check my mail regularly throughout the day, so i need no real time notif for that.
As for all other main services like Accounts, Alarm, Location and elses, i never have any issue with them when i got this module active. GPS work fine, Alarm ringing, Account Syncing normally.
HOW TO INSTALL :
SO if after reading all the PROs and the probable CONs above , you still interested in trying this mod,
Simply dowmload it from the attachment, and install it through your MAGISK MANAGER. And reboot.
After reboot, go to "Setting" - "Battery" - tap the tri-dot menu on the top right and choose "Battery Optimisation"
Choose "All Apps" and switch ON the toggle for Google Play Services (in most ROM, it will be automatically switched to ON once this mod is installed)
ENJOY THEN ! :highfive:
Addendum :
WHAT IS THE DIFFERENCE between (+) and standard module ?
• Plus (+) version modified by @VR25 has an extra feature, which removing Google Play Services from Background Data Access Whitelisting. Thus enabling data saver or restricting background data will impact Google Play Services as well. This might save you extra juice, but BEWARE for interrupted background data activities.
Choose the one suit you most.
COMPATIBILITY :
This Mod should compatible with any Marshmallow and Nougat ROM (Official & Custom) that has Google Play Services Installed on it,
Tested on :
OOS, LOS, CM13, MIUI, EMUI, and TouchWiz
If you found that this module causing issue for your set up, simply uninstall it from magisk manager, or use the TWRP Uninstaller.
Screenshot of expected level of Google Play Services Battery Usage :
{
"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"
}
Simple and work fine with RR rom, Thanks :highfive:
Sent from my Nexus 6 using XDA Labs
Htc 10 on viper rom. This breaks fingerprint sensor/home button for me
JohnFawkes said:
Htc 10 on viper rom. This breaks fingerprint sensor/home button for me
Click to expand...
Click to collapse
Thats weird,
My S8, OP3 and P9 all has fingerprint scanner, and work normal.
Can you try,
Before placing finger on the scanner, turn on your screen first by pressing lock button,
If it managed to scan, then it means it doesn't actually break FP, it just the phone go to deeper sleep (since GMS is now hibernated as well) and refuse to wake up simply by placing finger.
But if it atill refuse to scan even with screen on. Send me a logcat
otonieru said:
Thats weird,
My S8, OP3 and P9 all has fingerprint scanner, and work normal.
Can you try,
Before placing finger on the scanner, turn on your screen first by pressing lock button,
If it managed to scan, then it means it doesn't actually break FP, it just the phone go to deeper sleep (since GMS is now hibernated as well) and refuse to wake up simply by placing finger.
But if it atill refuse to scan even with screen on. Send me a logcat
Click to expand...
Click to collapse
I don't have any FPs set up but waking screen and using it as a home button does not work and I get no vibration either even though it's set to 90 in exkm
edit give me a few minutes to reinstall and I'll get a logcat for you
Works great on my nexus 6p, thank you!
Sent from my Nexus 6P using Tapatalk
so after flashing this time I lost root and no cell serviceafter reboot. Looked at your module.prop and from my understanding with v12 modules are supposed to use versioncode 3 not 1. So I changed it 3 and zipped it back up. Booted into twrp used magiskmount to delete this module and flashed the one with 3 as versioncode and after booting up I have root and cell service and my home button is working like it should.
JohnFawkes said:
so after flashing this time I lost root and no cell serviceafter reboot. Looked at your module.prop and from my understanding with v12 modules are supposed to use versioncode 3 not 1. So I changed it 3 and zipped it back up. Booted into twrp used magiskmount to delete this module and flashed the one with 3 as versioncode and after booting up I have root and cell service and my home button is working like it should.
Click to expand...
Click to collapse
Crap, so that's where the issue belong,
although am using v1 myself on v12 Magisk, since it's supposed to have backward compatibility. And so far there's no issue.
I think ROM combination might have something to do as well,
but as for now i'll update the installer zip.
Thx for the debug!
otonieru said:
Crap, so that's where the issue belong,
although am using v1 myself on v12 Magisk, since it's supposed to have backward compatibility. And so far there's no issue.
I think ROM combination might have something to do as well,
but as for now i'll update the installer zip.
Thx for the debug!
Click to expand...
Click to collapse
No problem! Happy to help. If you need a tester for anything just let me know
Works successfull, thanks for works :good:
Hi. I tried installing it. Installation worked and module appeared in the list, but on reboot it disappear. I'm on Galaxy Note 3 with custom kernel and custom magisk. I've asked if it could be that magisk's problem, but maybe could be this module fault?
My rom is Unofficial LineageOS 7.1.2.
P.S. I also tried flashing it with TWRP without success. I'll try this module in my tablet to check too (Lineage 7.1.2 too).
Inviato dal mio SM-P605 utilizzando Tapatalk
asusgarb said:
Hi. I tried installing it. Installation worked and module appeared in the list, but on reboot it disappear. I'm on Galaxy Note 3 with custom kernel and custom magisk. I've asked if it could be that magisk's problem, but maybe could be this module fault?
Inviato dal mio SM-P605 utilizzando Tapatalk
Click to expand...
Click to collapse
Well, all i can say is that i only test it on official Magisk
But, try use the new module attached, and whether it solve your issue
otonieru said:
Well, all i can say is that i only test it on official Magisk
But, try use the new module attached, and whether it solve your issue
Click to expand...
Click to collapse
Just for information, with modified magisk didn't work, but it works in both devices with official magisk 12.
And now let's test its impact on battery life![emoji1]
Inviato dal mio SM-N9005 utilizzando Tapatalk
Thanks a lot bro .. Working fine . Improved my battery life a lot :fingers-crossed:
Thanks:good:
Works like a charm.
BTW, there is also Download Manager which cannot be optimized. Can you add it to your module?
Shished said:
Works like a charm.
BTW, there is also Download Manager which cannot be optimized. Can you add it to your module?
Click to expand...
Click to collapse
You do realize if you're downloading a big file and download manager is optomize your download will stop soon after you turn off the screen when doze starts. Download manager doesn't produce any wakelocks or alarms.
DroneDoom said:
You do realize if you're downloading a big file and download manager is optomize your download will stop soon after you turn off the screen when doze starts. Download manager doesn't produce any wakelocks or alarms.
Click to expand...
Click to collapse
Hidden downloads such as play store or play services are also downloaded with this app.
Shished said:
Hidden downloads such as play store or play services are also downloaded with this app.
Click to expand...
Click to collapse
What is your point?
---------- Post added at 04:21 PM ---------- Previous post was at 04:17 PM ----------
Shished said:
Hidden downloads such as play store or play services are also downloaded with this app.
Click to expand...
Click to collapse
Download manager is independent from those services. If everything is optomize, nothing should be invoking download manager in the first place during doze. Thus download manager shouldn't be bothered with the battery optomize option.
DroneDoom said:
What is your point?
---------- Post added at 04:21 PM ---------- Previous post was at 04:17 PM ----------
Download manager is independent from those services. If everything is optomize, nothing should be invoking download manager in the first place during doze. Thus download manager shouldn't be bothered with the battery optomize option.
Click to expand...
Click to collapse
This is true @Shished
I even put ADM to whitelist. I dont want any of my downloads interrupted when the screen is off or when am sleeping
Thus, it shouldnt be bothered.
Hello,
my Oneplus 7+ is running stock Android 11. Magisk has been installed and since a month ago everything was working fine (even DKB TAN2go and other banking apps). Last month an update for Comdirects Photo TAN was released and it stopped working. Luckily I was not the only one to encounter it and the description from @ralphabt here solved the issue for me.
Since this morning Google Pay stopped working (of couse I only noticed when I tried to pay and had my wallet nearby). SafetyNet fails (basic and cts). If I disabled the modules that I installed for the PhotoTan fix, SafetyNet is working again.
I found the MagiskHide Props Config, which I don't have a problem installing and testing, but I was wondering if there anything else I can try before fixing an issues that is caused by a solution for another issue.
Thanks a lot!
If SafetyNet now triggers from the Riru/EdXposed stuff you'll likely have to wait for an update to those modules (or try the latest beta/alpha/canary releases). Or try LSPosed instead (seems like more people have success with that). It's a cat and mouse game...
Im still waiting for anyone to give me a valid reason to use Xposed of any sort....
I pulled it out recently after jettisoning Xposed back in Marshmallow days, and was completely unsurprised that in my attempts to avoid root detection when i was having bank app issues it just broke things harder
Your biggest issue is getting SafetyNet pass...
Getting Google Pay and banking apps is another level...
My current setup for working bank apps (my bank at least) and working Samsung Pay & Google Pay is, should you wish to have a crack:
Magisk Alpha - here (second most recent at time of posting) or here for latest:
Riru - here
Riru-Momohider - my own mod of that module attached to my post here (where i just added creation of the 4 optional config options to the installations script, to avoid manual jiggery pokery, touching 4 files in a terminal every ROM flash didnt seem like a fun thing after the 3 ROMS i tested that week i started using Riru-Momohider)
Im talking those are the only modules i use. Even a simple font replacement module will give up a system modification to most root detection apps. So no fonts, no emojis swapping, no fiddly shizz. Keep it simple.
You can get an idea of what may be setting things off via Magisk Detector here, or VD Infos here (apologies to Didge, as mentioning that may be a trigger )
And i now get to tell you that this only currently works on 2 ROM's for my device, all the others cough up the existence of root through modifications made by devs to build.prop etc
So even in the best circumstances, and with all the right magisk and riru modules, the ROM youre using can still betray you.
Isnt that fun?
Worth pointing out (so frequently am i pointing this out these days im thinking of removing the link to my GPay Magisk Module from my sig) that for like 6 months now its been unnecessary for a lot of people to
a) Use the Google Pay db fix originally sussed out by @BostonDan, or my Magisk Module that does the same thing
and
b) Enable MagiskHide for Google Pay...
Actually getting SafetyNet is rather easy - if I remove EdXposed and XPrivacyLua it is working again and Google Pay as well. I only installed (my only reason) it, as it was required to get that banking app running.
I am using different banking apps and it the past the one from german DKB was rather difficult, but with newest Magisk (23) and Magisk Hide it is working.