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
Related
Hi everyone,
I recently tried using a few [5.1.x] ROMs, and as habit I always install xposed with them. The xposed(experimental [5.1] version) and its modules worked flawlessly,no problems at all. But every time, after a few minutes (or hours) of boot, the phone misbehaves with the following consistent symptoms:-
1) The back and the menu buttons stop working. However the Home button still continues to work. Software keys also work.
2) The keyboard stops popping up (Default Google keyboard, Anysoft Keyboard, Google voice keyboard). Task manager shows none of these processes being created after that point. This happens sometimes even during typing when the keyboard disappears and wont show up until I restart my phone.
3) Clicking on any of the icons doesnt create the process, i.e. the app wont launch after the misbehaving symptoms have started.
The only way to solve this is to restart, but the problem returns after a few minutes again.
I have taken all precautions of checking the version compatibilities of the software and modules while installing them. They work perfectly for some time before going bad.
I have this problem only on 5.1 ROMs,that too in combination with the xposed. When I revert back to 4.4 or 5.0 ROMs with their respective xposed versions, the problem goes away.
Does anyone else experience this problem as well? Does anyone know a permanent solution to this?
Hey, I've been using the automatic rules for priority/do not disturb mode in Marshmallow, but I've noticed that lately the phone doesn't automatically turn off this mode after the specified time. For example, I have my class schedule in Google Calendar, and it doesn't exit priority mode after class. Same with nighttime; come morning, its still in 'alarm only' mode.
My phone is rooted, stock rom, w/ xposed framework. I've tried disabling Gravitybox, but that didn't help. I'm thinking it might be a bug with N-ify, because I think it started after I used that, but even if I disable that module, it doesn't fix itself. Otherwise the phone works fine.
viggy96 said:
Hey, I've been using the automatic rules for priority/do not disturb mode in Marshmallow, but I've noticed that lately the phone doesn't automatically turn off this mode after the specified time. For example, I have my class schedule in Google Calendar, and it doesn't exit priority mode after class. Same with nighttime; come morning, its still in 'alarm only' mode.
My phone is rooted, stock rom, w/ xposed framework. I've tried disabling Gravitybox, but that didn't help. I'm thinking it might be a bug with N-ify, because I think it started after I used that, but even if I disable that module, it doesn't fix itself. Otherwise the phone works fine.
Click to expand...
Click to collapse
Are you rebooting after disabling N-ify?
Yeah, I am.
Tel864 said:
Are you rebooting after disabling N-ify?
Click to expand...
Click to collapse
Yeah, I am rebooting after disabling N-ify. In fact, I just restored a backup from before N-ify, and I still have the same problem. I just did the system, cache and boot partitions though, didn't restore data, to save on space.
Solved. Just figured out that SoundAbout's notification listener is interfering with that mode.
Thanks guys.
Today I've got september security update and phone has been working fine for most of the day and then suddenly it started freezing on rotation. Either when it goes fullscreen or I rotate it, the screen freezes, can't turn off screen and either I hard restart or it does it itself after a minute.
I haven't updated or installed anything new besides the security update recently.
I wiped cache and when in safe mode it doesn't freeze, so I assume it's an app problem but is there any way to narrow down to which one it can be? In safe mode most are disabled and when I turn phone on all should be off and it still happens so I'm not sure how to diagnose this besides randomly uninstalling app by app.
Sm g955f, everything stock, android 9
N_L said:
Today I've got september security update and phone has been working fine for most of the day and then suddenly it started freezing on rotation. Either when it goes fullscreen or I rotate it, the screen freezes, can't turn off screen and either I hard restart or it does it itself after a minute.
I haven't updated or installed anything new besides the security update recently.
I wiped cache and when in safe mode it doesn't freeze, so I assume it's an app problem but is there any way to narrow down to which one it can be? In safe mode most are disabled and when I turn phone on all should be off and it still happens so I'm not sure how to diagnose this besides randomly uninstalling app by app.
Sm g955f, everything stock, android 9
Click to expand...
Click to collapse
I have the same problem. I have locked rotation to prevent freeze. hope someone can explain it
Did anyone find a fix for this? Just started happening to my Galaxy s8+ today also after an "1 January 2020" security update.
SMG955F
Temporary fix: when you need full screen, toggle on 'disable HW overlays' in developer options.
This will be resetted each reboot, so you need to enable it when you need manually.
My Pixel 2 XL on Android 10 and Magisk 20.3 keeps getting its Sensitive Notifications setting reset to on when I reboot my phone. Anyone else experiencing this and found a fix? For now, I've set up a Tasker profile to run on boot which is definitely less than ideal.
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.