Restart three to four times, then it works again.
Do any of you know this problem?
My cell phone is a Oneplus 7 pro. Current OxygenOS, TWRP, Magisk, Riru Edxposed ...
Most likely you are having an issue with Esxposed. Turn off all your modules in Magisk and then reboot. Enable one by one and repeat til you find the cause.
Sounds good. I will try that. If I can pinpoint the cause, I will report again. Meanwhile, thank you very much.
I just hit any app quickly before it reboot. This solve the issue. Otherwise it restart three to four times.
whoamanwtf said:
Most likely you are having an issue with Esxposed. Turn off all your modules in Magisk and then reboot. Enable one by one and repeat til you find the cause.
Click to expand...
Click to collapse
Your hint was great. I was able to localize the problem. The trigger was XPrivacyLua. Strictly speaking, the limitation of "Google Play Services" ---> use tracking.
Now the cell phone ALWAYS starts normally.
Many thanks
ghost323 said:
Your hint was great. I was able to localize the problem. The trigger was XPrivacyLua. Strictly speaking, the limitation of "Google Play Services" ---> use tracking.
Now the cell phone ALWAYS starts normally.
Many thanks
Click to expand...
Click to collapse
Awesome glad I could assist! Happy modding
I had this issue with just riru exposed and not the Xposed modules at all. Trust me, it will come back.
mookiexl said:
I had this issue with just riru exposed and not the Xposed modules at all. Trust me, it will come back.
Click to expand...
Click to collapse
I just hope the best
mookiexl said:
I had this issue with just riru exposed and not the Xposed modules at all. Trust me, it will come back.
Click to expand...
Click to collapse
Did you use the SandHook or the yahfa version?
ghost323 said:
Did you use the SandHook or the yahfa version?
Click to expand...
Click to collapse
I think it was sandhook. Everything started off fine then I noticed slight performance degradation. Followed by the double boot you mentioned. To one-day the phone continuously rebooting at any attempt to input pin. I uninstalled modules not Magisk and Xposed one by one to find the culprit and sure enough it was Ed Xposed. No such issues ever happened with TaiChi Xposed. The only reason I was even on Ed was to troubleshoot the AOD app for a dev but this also happened the first time I used Ed
mookiexl said:
I think it was sandhook. Everything started off fine then I noticed slight performance degradation. Followed by the double boot you mentioned. To one-day the phone continuously rebooting at any attempt to input pin. I uninstalled modules not Magisk and Xposed one by one to find the culprit and sure enough it was Ed Xposed. No such issues ever happened with TaiChi Xposed. The only reason I was even on Ed was to troubleshoot the AOD app for a dev but this also happened the first time I used Ed
Click to expand...
Click to collapse
Very interesting. Everything sounds plausible as you say it.
TaiChi is supposed to collect a lot of data ... Can you confirm that?
Related
Am I the only one with stock 4.4.2 whose camera freezes?
I've been battling the problem that if I use the camera on the Nexus 5 it will sometimes freeze the phone. It may happen after a variable amount of pictures are taken. Suddenly the phone freezes and only a reboot will get it back to normal. I've asked in this forum without success and then found this
http://stackoverflow.com/questions/5880096/problem-using-camera-api-on-android?rq=1
Any solutions anyone?
Anderson2 said:
Am I the only one with stock 4.4.2 whose camera freezes?
I've been battling the problem that if I use the camera on the Nexus 5 it will sometimes freeze the phone. It may happen after a variable amount of pictures are taken. Suddenly the phone freezes and only a reboot will get it back to normal. I've asked in this forum without success and then found this
http://stackoverflow.com/questions/5880096/problem-using-camera-api-on-android?rq=1
Any solutions anyone?
Click to expand...
Click to collapse
What's your phone setup? Are you rooted with a custom ROM?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Rooted, stock 4.4.2 ROM.
Nova prime launcher.
No syncing on anything.
Use xprivacy, AFWall+, gravitybox. (but all 3 disabled with no improvement).
Camera is essentially unusable because of need to reboot every few pictures. Screenshots in my other thread.
http://forum.xda-developers.com/showthread.php?t=2761146
http://forum.xda-developers.com/showthread.php?t=2761146
Anderson2 said:
Rooted, stock 4.4.2 ROM.
Nova prime launcher.
No syncing on anything.
Use xprivacy, AFWall+, gravitybox. (but all 3 disabled with no improvement).
Camera is essentially unusable because of need to reboot every few pictures. Screenshots in my other thread.
http://forum.xda-developers.com/showthread.php?t=2761146
http://forum.xda-developers.com/showthread.php?t=2761146
Click to expand...
Click to collapse
dont disable the exposed, delete it(remove everything xposed completely), reboot, then try your camera
I would hate to do that because I really like xposed. But I'll make a nandroid backup, and then do as you say. If it's no better, I could always restore the nandroid. But nobody else has noticed any connection between xposed and Google camera. I "believe" the problems started when I updated to the latest camera update. Wish I could find the pre update camera app.
Anderson2 said:
I would hate to do that because I really like xposed. But I'll make a nandroid backup, and then do as you say. If it's no better, I could always restore the nandroid. But nobody else has noticed any connection between xposed and Google camera. I "believe" the problems started when I updated to the latest camera update. Wish I could find the pre update camera app.
Click to expand...
Click to collapse
xposed causes many many random issues that are undocumented. for many not a single issue, for others its like a phone full of gremlins.
Well, tis done. I'll see if the camera behaves. It takes time for it to act up....
Fwiw, I've used xposed for quite a while and the camera freezing only started about 4-6 weeks ago. Maybe it was a recent update.
I uninstalled xposed. Where should I look for files to delete to ensure a good test?
Anderson2 said:
Well, tis done. I'll see if the camera behaves. It takes time for it to act up....
Fwiw, I've used xposed for quite a while and the camera freezing only started about 4-6 weeks ago. Maybe it was a recent update.
I uninstalled xposed. Where should I look for files to delete to ensure a good test?
Click to expand...
Click to collapse
honestly, i dont know. i have never needed or been willing to use xposed. an uninstall and a reboot should be fine(dirty flashing your rom again would be best, but i think it will be fine without). just give it some time to test. if its not xposed, restore your backup and we will look further.
I'm afraid to say anything, but I think uninstalling Xposed did it. Will wait longer before breathing a sigh.....
Thank you.
A couple of weeks ago I started getting error popups, always at least two (dismiss the first then the same exact error pops up again) in a row, then usually a short pause followed by another two popups. It seems to mainly happen when I start on the move, particularily when driving, but then after the first one, or two sets, it won't happen again for a while. Every now and then it will happen at home when I'm on WiFi, but it's less than once a day that I see that. In case you can't see my sig, I'm running stock Kitkat 4.4.4 with Xposed & Gravitybox.
Steps I've taken to try to resolve this is, freezing various apps that I'd recently updated right before this started, installing both older and newer versions of Google Play Services (currently have 6.1.83), updated Google Play Store (5.0.32), cleared the data and cache of Google Play Store, uninstalled GPS updates (4.8.20), and updated to the latest Franco kernel version (r63).
Still the errors come up. Anything else I can try short of a factory reset? I'd rather not have to do that right before Lollipop, when I'll just be flashing over it again anyway.
the very first thing that you should have tried is completely remove xposed and anything that has to do with xposed. whenever you have an issue, and xposed installed, you cant really check anything else without removing xposed completely. xposed comes with many undocumented issues, it can break just about anything. so, if you have an issue, the very first thing is remove xposed.
I thought about that, but absolutely nothing was changed before the issue and after the issue. Earlier today I updated Gravitybox and a couple of other modules, but that didn't solve the issue. I suppose I'll try completely removing it, although I doubt that will fix anything since as I said, nothing in my Xposed framework had changed when I started having this issue.
Edit: Well slap my mouth and call me Sally. It's definitley an Xposed issue. Now I just need to narrow it down to which module is causing the problem. Thankfully it's not GB.
Thanks, simms22. I guess some change on a Google Services side must have had an issue with one or more of my installed modules. If I had to guess it is probably the "Disable Location Consent" module.
Simply reflash stock 4.4.4. Should end the issue. A fresh start. ?
Nastybutler said:
I thought about that, but absolutely nothing was changed before the issue and after the issue. Earlier today I updated Gravitybox and a couple of other modules, but that didn't solve the issue. I suppose I'll try completely removing it, although I doubt that will fix anything since as I said, nothing in my Xposed framework had changed when I started having this issue.
Edit: Well slap my mouth and call me Sally. It's definitley an Xposed issue. Now I just need to narrow it down to which module is causing the problem. Thankfully it's not GB.
Thanks, simms22. I guess some change on a Google Services side must have had an issue with one or more of my installed modules. If I had to guess it is probably the "Disable Location Consent" module.
Click to expand...
Click to collapse
its always what i ask ppl to do when i help, uninstall xposed first. if the problem still persists, then we try something else. and i swear to you, about 80% of the time its the xposed
Hey guys,
Ever since the latest update 10.0.5, I've noticed that my screen is not timing out and remains on until I press the power button. I am rooted with Magisk and am using EdXposed YAHFA with RiruCore.
I have the sleep settings set to 15 seconds in the display option.
The timeout does work properly in certain apps (I've noticed it works fine when I have Brevent open) but is not working in the majority of applications.
I've tried to boot the phone in Safe Mode and the issue persists even there.
Anyone else experiencing the same issue or have any solutions in mind aside from a factory reset? Should I try uninstalling Edxposed and Magisk?
Delete hidden core module and you will be fine. It is a known issue caised by that app as well as crashing chrome. By the way that module doesnt really work. Only fools magisk safety net check. Other checks qill still fail
I've tried several times, but unfortunately when i root my device,CODM crashes without any warning. It's not like opens and crashes immediately. Sometimes after loading screen, sometimes in the middle of the match. It just closes, not minimized. What could be the problem. I've got, Magisk, EdExposed, CustoMIUIzer.
tapu_afrad said:
I've tried several times, but unfortunately when i root my device,CODM crashes without any warning. It's not like opens and crashes immediately. Sometimes after loading screen, sometimes in the middle of the match. It just closes, not minimized. What could be the problem. I've got, Magisk, EdExposed, CustoMIUIzer.
Click to expand...
Click to collapse
try uninstalling xposed, it is usually the culprit, rooting (Magisk) shouldn't cause that.
Culprit is the "Magisk Manager". Without root, just the app installed the CODM crashes.
has anti root (like super mario)
You have to have magisk I made the game and apart magisk renamed the application, in magisk settings it puts something like recompiling application with a random name, there put the name you want and that's it, it works perfect, it happened to me and I went crazy. Greetings
niosa said:
has anti root (like super mario)
You have to have magisk I made the game and apart magisk renamed the application, in magisk settings it puts something like recompiling application with a random name, there put the name you want and that's it, it works perfect, it happened to me and I went crazy. Greetings
Click to expand...
Click to collapse
Thanks, recompiling app solved the issue.
Got the 7 Pro, Software updated(October patch), rooted and Camera app updated.
*When I first got the phone I updated it immediately and then rooted it, the GCam app worked fine. but it was soo slow switching between camera modes, so I uninstalled and then reinstalled(updated) the app. after doing this the app just doesn't want to work.
*I also "disabled" root - updated the phone without the patched init-boot. still, didn't work.
I saw that it fixed for some just updating the app, didn't work for me.
Any other solutions?
"Any other solutions?"
Not to be facetious but you could go back to factory and enjoy the phone as it was meant to work which is great by the way. YMMV
Tried clearing the data for the camera app?
skaforey said:
Tried clearing the data for the camera app?
Click to expand...
Click to collapse
Yep
jaseman said:
"Any other solutions?"
Not to be facetious but you could go back to factory and enjoy the phone as it was meant to work which is great by the way. YMMV
Click to expand...
Click to collapse
The app still causes problems, it's not a "root" problem.
And I don't live in a place where Google "supports" the country. so rooting is ideal for me and a nice to have.
TheShinyEnd said:
*When I first got the phone I updated it immediately and then rooted it, the GCam app worked fine. but it was soo slow switching between camera modes,
Click to expand...
Click to collapse
Did you happen to have a Magisk mod that disabled the navbar, pill, enabled immersive or similar? If so, these mods will slow down the switching between modes.
If clearing data and cache of the camera app didn't work, a clean flash may be in order.
Lughnasadh said:
"Did you happen to have a Magisk mod that disabled the navbar, pill, enabled immersive.."
Click to expand...
Click to collapse
I do have it.
Lughnasadh said:
If clearing data and cache of the camera app didn't work, a clean flash may be in order.
Click to expand...
Click to collapse
The thing is that wiping the phone won't(probably) fix it.. well it will, until it auto updates the camera app. and I really don't want to go through the struggle of reinstalling and logging into everything again, thanks for the idea but i'd pass..
Thanks either way
TheShinyEnd said:
I do have it.
The thing is that wiping the phone won't(probably) fix it.. well it will, until it auto updates the camera app. and I really don't want to go through the struggle of reinstalling and logging into everything again, thanks for the idea but i'd pass..
Thanks either way
Click to expand...
Click to collapse
Well, at least you now know why it was slow switching between modes and that it was that mods causing it and not the camera itself.
Best of luck getting it all straightened out...