Database Develop

[Q] Xposed causes WiFi to stop working...

So I decided I should to a factory reset on my Moto X today to clean it up and make it run better. Anyway I downloaded Towel Pie Root, rooted the phone, and backed up my apps with TB. My phone hadn't been rooted up to this point. Anyway I did the app backup and pulled my /sdcard/ contents to my laptop with adb and did the factory reset. Afterwards I got everything updated, restored the apps I wanted with TB(after rerooting with TPR), and got the phone set back up like I wanted. I also decided I'd give Xposed a try being that rooting was fairly simple with TPR. I downloaded Xposed 2.6.1, installed the framework and did a soft reboot. After doing that I can't connect to WiFi anymore; I just get a "Failed to Connect to Network" toast notification when I try. A Hard Reboot fixes the issue until I reinstall Xposed then WiFi breaks again.
Any ideas on why this is happening or how to fix it? I know I read in the TPR thread that people were using Xposed with TPR like I'm trying to.
Sent from my MacBook Pro using Chrome
Phone: Moto X(XT1053) running Stock 4.4.3

Xposed causes WiFi to stop working... fix
NOW firstly uninstall your xposed installer ,And the download the latest version v7.1 from repo.xposed.info/module/de.robv.android.xposed.installer
& install it..
IT SHOULD WORK..
& SORRY FOR MY ENGLISH

prashantsingh480 said:
NOW firstly uninstall your xposed installer ,And the download the latest version v7.1 from repo.xposed.info/module/de.robv.android.xposed.installer
& install it..
IT SHOULD WORK..
& SORRY FOR MY ENGLISH
Click to expand...
Click to collapse
No luck....
{
"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"
}
Now it's not even seeing that there are networks in the area. [emoji20]
Sent from my Moto X (XT1053) using Tapatalk

Now it's not even seeing that there are networks in the area. [emoji20]
Sent from my Moto X (XT1053) using Tapatalk[/QUOTE]
first uninstall the xposed installer & then check if it catches the wifi network or not ..... :good::good:

Deleted

The WiFi starts working after a hard reboot which makes xposed not work because I lose root after a hard reboot. Whether or not the xposed installer is installed or not doesn't make a difference. My WiFi is fine now that I did a hard reboot.
Sent from my Moto X (XT1053) using Tapatalk

tnp9008 said:
The WiFi starts working after a hard reboot which makes xposed not work because I lose root after a hard reboot. Whether or not the xposed installer is installed or not doesn't make a difference. My WiFi is fine now that I did a hard reboot.
Sent from my Moto X (XT1053) using Tapatalk
Click to expand...
Click to collapse
NOW ,root your moto X by root master .
& check if it catches the networks or not if it catches.
the install xposed installer v7.0 not the latest (v7.1).
then check ...
SHOULD WORK ......
BEST OF LUCK....

Does your phone reset the system partition after reboot?
If so... Try flashing xposed... Switch install method to manual recovery flash... Run the installer... Then reboot to recovery and flash the zip...
MotoX has a nasty system reset thingy... You have to look for the workaround in your device thread...
Why its borking WiFi... I'm not sure

rignfool said:
Does your phone reset the system partition after reboot?
If so... Try flashing xposed... Switch install method to manual recovery flash... Run the installer... Then reboot to recovery and flash the zip...
MotoX has a nasty system reset thingy... You have to look for the workaround in your device thread...
Why its borking WiFi... I'm not sure
Click to expand...
Click to collapse
I know my system partition is read only. The only way to have read/write is to unlock my bootloader which I could do but I don't want to lose my warranty so that's not an option right now. When the warranty runs out I plan to get an unlock code and obtain full root with system read/write but that's a ways off. I don't have custom recovery installed so I can't flash manually in recovery; the root access I gain is temporary. I have to re-root with Towel Pie Root after every full reboot. From what I read in the TPR thread people have had success using xposed on the Moto X like I'm doing, but for some reason it borks my WiFi.
Update: After digging through the TPR thread it looks like this is a somewhat common issue with TPR + 4.4.3 + Xposed. The TPR dev is looking into the issue.

Android Pay

Android pay doesn't seem to work with my bootloader unlocked rooted MotoX14. Is this a result of the root? Kinda bummed, has anyone else tried it?
Edit: disregard I fixed it. Simply uncheck "Enable Superuser" in the supersu app - Then verify your cards then recheck the "Enable Superuser" - Profit (err spend money)

I tried this, but I'm still getting a message that Google cannot verify that my device or the software running on it are Android compatible. Was this the same issue that you encountered? Are you running a custom ROM, and if so, which one? I'm on the latest Nexus Experience.

Guys you have to be on pure edition, and non rooted devices.
Sent from my XT1095 using XDA Free mobile app

Yes I was able to get my cards verified but when I tried to checkout it gave me an error at the register. I will try again at a different store, but it appears that the service does not like to play well with root/unlocked phones. I am on the stock Moto X lollipop 5.1 software, no ROM. I think ROMs are more temperamental in reference to Android Pay.
Thought, would turning off superuser through the SuperSU affect daily activities? I used root mainly to get tethering as well as some system modifications like volume panels and such. Would turning root off cause those to not work or only services that routinely need to access root (ie: Greenify)

I am having the same issue. Tried disabling superuser but get the same error. Also tried the xposed module No Device Check, didn't work.
Unlocked bootloader, stock rooted rom and xposed.
Need a way to get around this.

Same problem here. Stock Rom 4.4, super User disabled,no luck.

I'm having the same issue with the stock 5.0 rom, with unlocked bootloader, supersu disabled, twrp recovery, and xposed.
I've tried with rootcloak and no device check xposed modules too.
From what I've gathered reading other threads android pay doesnt like custom roms so I'm wondering if it's the changes that xposed makes that's causing issues or if it could be the custom recovery. Many people are having success just unrooting but that didn't work for me so there's more that's being flagged as not compatible in my setup. I've seen people saying they have no issues with unlocked bootloaders as well so really thinking it's recovery or xposed. I just don't use tap and pay enough to try wiping the phone and playing with settings though.

Same problem here. . . XT1095, stock 5.1, rooted, no XPosed. . . disabled SuperSU, rebooted, re-loaded credit card, same error. I even tried "permanently removing root". Same error.
Too bad. . . I've been geeking out since 2012 paying for items using Google Pay and NFC. . . guess I have to revert to the swipe

WOP_Drive said:
Same problem here. . . XT1095, stock 5.1, rooted, no XPosed. . . disabled SuperSU, rebooted, re-loaded credit card, same error. I even tried "permanently removing root". Same error.
Too bad. . . I've been geeking out since 2012 paying for items using Google Pay and NFC. . . guess I have to revert to the swipe
Click to expand...
Click to collapse
Did you reboot your phone after you disabled SuperSU? It worked for me and I had xposed installed

Yes.... I did reboot after disabling SuperSU.

I tried rebooting after disabling superuser and it still didn't work, I wonder if TWRP is causing the issue.

Never got it to work by disabling SuperSU. I even restored an old unrooted backup, but still no luck. However, I'm sure it's not TWRP. I loaded up a clean image, still using TWRP, and Android Pay worked. Go figure. Not sure what was wrong with my unrooted backup, but I can confirm Android Pay works when unlocked and on TWRP recovery.

Wonder if it has to do with the settings showing the system is "modified"?
Settings -> About phone -> Status
{
"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"
}

GatorsUF said:
Wonder if it has to do with the settings showing the system is "modified"?
Settings -> About phone -> Status
Click to expand...
Click to collapse
Mine does not show modified, doesn't show that box at all actually.
I'm on 5.0 though, was that added to 5.1?

I am on 5.1, guess it's a new addition.

Has anyone tried re-locking the bootloader and then try getting Android Pay to work? I haven't yet. Here's an article that walks you through it using a Nexus device (not sure if it'll work on my XT1095).
article/video
I'm running stock 5.1 on a rooted XT1095 (bootloader unlocked) with TWRP. If anyone has step-by-step instructions that'll get Android Pay to work on this configuration, I'm "all ears"! THX!

Relocking the bootloader does not affect it.
Sent from my XT1095 using Tapatalk

I'm on 5.1 on an XT1095. I ended up restoring that stock OTB system image I mentioned over the non-rooted Nandroid backup I had. Works fine now. Still unlocked. Still using TWRP. I don't see that software status message under about phone though. Weird.
Sent from my XT1095 using Tapatalk

GatorsUF said:
Wonder if it has to do with the settings showing the system is "modified"?
Settings -> About phone -> Status
Click to expand...
Click to collapse
I'm on 5.1 pure edition, mine doesn't have "modified"

ksd316 said:
I'm on 5.1 pure edition, mine doesn't have "modified"
Click to expand...
Click to collapse
Does android pay work on you phone?

Journey between ROMs is PAINFUL!

This is a question - NOT a complaint.
I was able to unlock, reroot and get to CF newest 5.1 with no issues (was on Mofo Root version). I saw RR and CM12 Rom conversations pop up, so I gave RR a run. I downloaded ROM and Gapps, wiped all dalvik, cache, system, etc (not internal card), installed and it started up without issues. At first. Started to get services closing, then play store closing, etc. It snow balled. Was able to key my way into recovery.
I said heck with this, I must've screwed up. So I wiped caches again - and same thing happened restarting. Back to recovery, wipe all, reinstall CF's that I had nandroid of.
Restart - same thing!!! WFT.
Back to recover, wipe all, install clean CF version and start up - no issues. So, I'm back at square 1.
Question - I recall years ago, I used to get into trouble going back and forth between CM and AOSP ROMs on same phone. I forget what I did to cause the issues, or how I fixed them. Can some one tell me, is this the same thing happening?
Is there something one needs to do to go back and forth between RR and CF ROM? Does wiping system cause issues? Should I wipe system all the time?
Having BL unlock is amazing as it is really hard to kill this thing following even the most basic instructions - but seems I'm causing some issues.
Any help appreciated!

What gapps are you using?
Sent from my DROID Turbo using XDA Free mobile app

Also, after you did the factory reset in TWRP, then installed RR and Gapps, did you try to restore anything from previous CF installation to your new installation? One guy tried to do that. He tried to use TWRP to restore data and I guess apps from old Verizon-based ROM to his new ROM. Stuff from a totally different ROM!
So, just asking.
Because if you did a factory re-set in TWRP, then flashed Resurrection Remix and the recommended GAPPS, and then re-downloaded any apps you need from the Google Play store, that's what we call a clean install and everything should work fine...
{
"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"
}

ChazzMatt said:
Also, after you did the factory reset in TWRP, then installed RR and Gapps, did you try to restore anything from previous CF installation to your new installation? One guy tried to do that. He tried to use TWRP to restore data and I guess apps from old Verizon-based ROM to his new ROM. Stuff from a totally different ROM!
So, just asking.
Because if you did a factory re-set in TWRP, then flashed Resurrection Remix and the recommended GAPPS, and then re-downloaded any apps you need from the Google Play store, that's what we call a clean install and everything should work fine...
Click to expand...
Click to collapse
Did you hear that? That slapping sound? That was me smacking my forehead and nearly passing out.
D'oh!!!!!!!! Yes. I TIBU'd my apps/data. After following RR install steps (including the enclosed gapps from that RR OP), I reloaded everything from TIBU restore. Crap. Makes me wonder too if that did enough "damage" that my restore of CF did work right then either. Nuts.
So, thanks for the idea. As a closet flash addict, I'll try again. I mean......... I just have to, right?

[Guide] How to fix Android OS battery drain (stay awake) without root!

Hello guys! It has been a long time since I have been trying to sort out my drain issues on my S6 Edge+ , a couple of days ago I finally figured out to use Wakelock Detector without root then it comes out that it was actually the maps keeping the phone awake via "NLPWakelock" through Android OS. I will cover out the process step by step to found out which app is causing the drain and why! We will need ABD, so we must have a computer.
1)First we are gonna need the app; "Wakelock Detector [Lite]" root users may use normal version too.
Play store link: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=tr,
2) We should open USB Debugging option in developer settings. And connect our phone to computer via USB.
{
"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"
}
3) To check if we have adb installed, you can simply run command promt ( windows/run/cmd ) and write
Code:
adb devices
If the output is similar to the image below, it means you have ADB installed and if you have device entry you have your ADB device drivers installed too.
If ADB is not installed, please kindly check Snoop05's thread to use his perfect tool - 15 Seconds ADB installer ( Yes, 15 seconds, actually less )
4) Once you make sure you have your device entry after writing " adb devices" , we gonna need to write this command to give Wakelock Detector battery history permissions:
Code:
adb -d shell pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS
At this point we may see a popup dialog on our phone like this:
You need to allow it and preferably you can check always allow option.
5) That's it guys. Now we have Wakelock detector working!
Most of the important drains caused by CPU wakelocks and Kernel Wakelocks. With or without root, the things we can do to kernel wakelocks are limited, afaik. So lets come to CPU Wakelocks. What you should do is use your phone regularly a couple hours after you gave permissions to the app and run it. Then you will see which apps , and which wakelocks they have called both individually. After that you can pinpoint the issue with a google search! Hope it helps you guys. I fixed my drain, I was getting 3hours of SOT before now I have more than 4-4.5 hours through my daily usage.
Notes:
Here is an awesome guide about wakelocks by T.J. Bender , you can check your wakelock there too.
Please feel free to ask any questions or unclear points. Hope your phones deeper sleeps!

How does this wakelock detector differ from better battery stats? Can i see more info with wld?

Thanks for this instruction, especially with the ADB command. For that command it is clear to me what it does (grant a permission) and that the permission is relatively safe.
I wouldn't have installed it with the Chrome extension. Running it is basically a 'feel free to rummage around my phone' permission. So again thanks for that adb command.

jutezak said:
Thanks for this instruction, especially with the ADB command. For that command it is clear to me what it does (grant a permission) and that the permission is relatively safe.
I wouldn't have installed it with the Chrome extension. Running it is basically a 'feel free to rummage around my phone' permission. So again thanks for that adb command.
Click to expand...
Click to collapse
You are welcome!

TuBBe2 said:
How does this wakelock detector differ from better battery stats? Can i see more info with wld?
Click to expand...
Click to collapse
It needs root afaik. If you have root, you might try and see. If you don't, you should get more detailed info.

Hello i got wld to work on my nonrooted note 5 and i have 220+ wakeups from google playservices how do i stop it or lower the amount of wakeups?

Hi! Will it trip Knox? Thanks.

This isn't a real fix for previous rooted users. Before I rooted my note 5 N920C, it had normal battery life. I rooted to try out the note 7 roms and then decided to go back to stock. I flashed official firmware and saw quick draining caused b Android OS. I factory resetted and reflashed and set the phone up with no accounts and on airplane mode. No location services or anything. The drain was still there. I installed BattleHero's prerooted stock rom and the drain was gone. I am assuming the stock non rooted kernal knows about Knox being tripped and causes this drain on purpose.

jetbruceli said:
This isn't a real fix for previous rooted users. Before I rooted my note 5 N920C, it had normal battery life. I rooted to try out the note 7 roms and then decided to go back to stock. I flashed official firmware and saw quick draining caused b Android OS. I factory resetted and reflashed and set the phone up with no accounts and on airplane mode. No location services or anything. The drain was still there. I installed BattleHero's prerooted stock rom and the drain was gone. I am assuming the stock non rooted kernal knows about Knox being tripped and causes this drain on purpose.
Click to expand...
Click to collapse
It is related my friend... we are all doomed until Samsung fix this in the stock software. Dr. Ketans fix kills this bug on stock rom but you lose NFC because of the custom rom indication. No more NFC tap payments...

angelfacekiller said:
It is related my friend... we are all doomed until Samsung fix this in the stock software. Dr. Ketans fix kills this bug on stock rom but you lose NFC because of the custom rom indication. No more NFC tap payments...
Click to expand...
Click to collapse
Can you tell me what Dr. Ketans fix is? I can't seem to find it and I want to try this.

Quick and easy, thanks for sharing!
Once you figured out the cause of your wakelocks, what exactly did you do to fix it?

Thanks! I was looking for the command to use with adb, because I have used this method for bbs and its working fine too. So I hope I can use it with wld as well.
- Enviado desde mi Pepinote4 -

I have the same problem anyone who know how to fix please help me

Blind app is detecting root with Magisk Hide

I've got an app I'd like to use that somehow keeps detecting root. It's called Blind (https://play.google.com/store/apps/details?id=com.teamblind.blind)
I've also got Pokemon Go installed, but that works just fine. Not problems with Magisk Hide.
I'm ready and willing to provide logs and such, just not sure where I should start.
Thanks!

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot

mew1033 said:
I've got an app I'd like to use that somehow keeps detecting root. It's called Blind (https://play.google.com/store/apps/details?id=com.teamblind.blind)
I've also got Pokemon Go installed, but that works just fine. Not problems with Magisk Hide.
I'm ready and willing to provide logs and such, just not sure where I should start.
Thanks!
Click to expand...
Click to collapse
Did you ever figure it out?

Just. Tried too. For test lol.
Didn't work for me.
I'm having issue with spay for gear 3.
If you can figure it out and maybe we can also both our issues

It suddenly started working for me today...

I was having this issue too. I eventually got so frustrated, I unrooted my device, relocked the bootloader, and did a factory reset. Still thinks I'm rooted, even though I'm completely factory. I think they get some unique device identifier and block your device server-side
If anyone figures it out, please let me know.
A bit of an annoying workaround: if you can make a comment with a different phone, and you get a notification telling you someone replied, you can open the app by tapping on the notification. However, it won't work if you open it by tapping on the icon

Any update?
Tried a whole bunch of things to hide Magisk. Blind just doesn't work.

Works!
Looks like Blind is detecting if your bootloader is unlocked. I installed this Magisk module called "SafetyPatch", which prevents apps from detecting if your bootloader is unlocked. That fixed it for me!

Darn, tried installing SafetyPatch, but still no luck
I suspect my phone has been blacklisted or something

I had checked logcat and it seems that blind was using com.liapp.lockincomp to detect root and display the alert. after hiding magisk manager and using magisk hide on blind it still didn't work even after clearing data/reinstalling the app. after a few days it magically started working again. guess they blacklist devices for x amount of time after they detect root.

I had Blind 2.5 and Magisk 17 working together. About two weeks ago I updated both and it stopped working. Anyone using Blind 2.6 with Magisk 18? I think my device got banned - downgrading Blind to 2.5 didn't help.

{
"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"
}
Seeing the issue on Blind 2.6.4 with Magisk Hide Enabled. Any other suggestions on a workaround?

Waited one week, installed Blind 2.5 from a backup and it works fine with Magisk 18.

babelus said:
Waited one week, installed Blind 2.5 from a backup and it works fine with Magisk 18.
Click to expand...
Click to collapse
So you uninstalled it & re-installed it after a week?
When you say backup, do you mean an APK that you had backed or a backup taken from TiBackup?

1nv1n said:
So you uninstalled it & re-installed it after a week?
When you say backup, do you mean an APK that you had backed or a backup taken from TiBackup?
Click to expand...
Click to collapse
Correct, uninstall Blind, wait a week, reinstall from backup of APK (TitaniumBackup). I can share the APK, but you shouldn't trust me.

I uninstalled Blind. Uninstalled Xposed. Made sure Magisk was able to pass all SafetyNet checks. Re-installed Blind from the Play Store. Used Magisk to hide it & was able to launch it without issues.

1nv1n said:
I uninstalled Blind. Uninstalled Xposed. Made sure Magisk was able to pass all SafetyNet checks. Re-installed Blind from the Play Store. Used Magisk to hide it & was able to launch it without issues.
Click to expand...
Click to collapse
Thanks for sharing, this worked for me
(Rooted stock Moto Z2 Force with Oreo)

Looks like it's broken again? I tried following the same process; but even after being hidden through Manager, it's still able to detect either root or bootloader unlock.
Anyone got any ideas?

1nv1n said:
Looks like it's broken again? I tried following the same process; but even after being hidden through Manager, it's still able to detect either root or bootloader unlock.
Anyone got any ideas?
Click to expand...
Click to collapse
I can confirm my workaround using the old version of Blind stopped working. New version works for a day or two after installation, then it detects root and I have to uninstall and wait for the ban to expire.

How many days does the ban last for?