Related
SecureAccessibility - Accessibility services or password-on-boot encryption? Pick both!
SecureAccessibility allows you to use accessibility services while still keeping the password-on-boot screen enabled!
If your password-on-boot screen is currently disabled, you will have to reactivate it for SecureAccessibility to work.
Compatible with everything from Kitkat (4.0) all the way to Oreo (8.1)!
If you find a bug, post here or create an issue in the Github issue tracker with your logcat + Xposed logs.
NOT TESTED on heavily modified ROMS (Touchwiz, LG, EMUI, etc...)
Xposed repository link: http://repo.xposed.info/module/xyz.nulldev.secureaccess
Source code: https://github.com/null-dev/SecureAccessibility
I managed to name the thread wrong while copy and pasting. Huge derp. It's fixed now.
Wow I was waiting a module like this a while ago.
Hy, may I ask why would I compromise phone's security if I would have accessibility enabled at the same time as pattern on boot? I'm just trying to understand the problem, I hope you can explain it
Also i want to know the problem.
It looks like I was actually wrong. This module may actually improve the security of your phone!
The reason accessibility services disable the password on boot screen is so users that rely on accessibility services to input data don't get locked out. This is because accessibility services are not available early on boot until the user decrypts their phone (they are not usable while entering the boot password).
I got this explanation from here where users are petitioning Google to keep the password on boot screen while having accessibility services enabled (which is what this module does): https://code.google.com/p/android/issues/detail?id=79309
By keeping the accessibility services enabled with the password on boot screen, you get the best of both worlds, with no compromise on security.
I have removed the warning from the module descriptions.
To add to comment #6 above:
Yes, this module has zero security impact.
All it does is prevent Android from disabling the boot encryption password when you enable an accessibility service. Period.
Before I used this module, whenever I turned on an accessibility service, I had to reenable password on boot by resetting my pin, which was a chore.
Fif_ said:
To add to comment #6 above:
Yes, this module has zero security impact.
All it does is prevent Android from disabling the boot encryption password when you enable an accessibility service. Period.
Click to expand...
Click to collapse
So I won't have any issues if I have to disable xposed after making use of this module for some reason? Just worried I might lock myself out of my phone.
Silkeyway said:
So I won't have any issues if I have to disable xposed after making use of this module for some reason? Just worried I might lock myself out of my phone.
Click to expand...
Click to collapse
Yep, nothing will happen.
Great work! Thank u very much!
greetz, brockn
Now that we have a janky Xposed on Nougat, has anyone tried it?
I've looked at the code, it should work, but doesn't on Nougat, Oxygen OS 4.5.10 on OnePlus 5.
No errors in the logs related to this module.
Fif_ said:
Now that we have a janky Xposed on Nougat, has anyone tried it?
I've looked at the code, it should work, but doesn't on Nougat, Oxygen OS 4.5.10 on OnePlus 5.
No errors in the logs related to this module.
Click to expand...
Click to collapse
I've just checked it again as well and it *should* work but I can't test it. Do you get the warning that password-on-boot will be disabled when you try to enable an accessibility service?
null-dev said:
I've just checked it again as well and it *should* work but I can't test it. Do you get the warning that password-on-boot will be disabled when you try to enable an accessibility service?
Click to expand...
Click to collapse
Yes I did.
I also checked the nougat source code and I agree with you that it should work [emoji3]
Yet it doesn't. It could be OOS patching the settings manager. I'll need to decompile it one day.
Fif_ said:
Yes I did.
I also checked the nougat source code and I agree with you that it should work [emoji3]
Yet it doesn't. It could be OOS patching the settings manager. I'll need to decompile it one day.
Click to expand...
Click to collapse
The official version of Xposed for Nougat was just released and I can confirm it works on there.
null-dev said:
The official version of Xposed for Nougat was just released and I can confirm it works on there.
Click to expand...
Click to collapse
I'll try it as soon as a systemless version comes out.
Edit: It works fine with the official Rovo89 Xposed 88.1 systemless and Magisk 14.2.
:angel:
I'm using Android 9 Magisk 20 and riru sandhook, just installed apk/activated xposed and seems to work so far. My intent was to prevent accessibility from turning my tasker off. This seems to the only real solution. Thank you.
Oukitel K9
[Solved] [Magisk Module] [Oreo Update] Spoofing "Daydream ready device" on a Nexus 6P
TL;DR Skip to the last paragraph!
Daydream runs pretty nice on my n6p. sucks to sideload all apps also not all apps can be found on google. so i wanted play store to recognize my device as "daydream ready" and let me download all daydream apps. a little googleing later i found 2 reddits explaining what to do and saying "it works" in the comments.
https://www.reddit.com/r/oneplus/co...got_daydream_working_on_a_oneplus33t/dbmy2it/ creating 2 new files in /system/etc/permissions/
https://www.reddit.com/r/Android/comments/5hno6u/got_daydream_to_work_on_my_5x_might_work_on_other/ put the 2 feature tags in handheld_core_hardware.xml
none of those worked. i could start sideloaded daydream apps before this. updating/downloading from play store is my issue.
things i didnt try yet:
- a clean flash of the rom then change the permission files in twrp adb then reboot.
- putting the feature tags in 2 seperate files AND in handheld_core_hardware.xml
- https://android.googlesource.com/pl.../etc/android.hardware.vr.high_performance.xml has the <feature name="android.software.vr.mode" /> and the high performance mode tag in it. didnt try that 2 tags in one file way yet.
anybody got this to work yet? if so pls share
EDIT: i made a magisk v10 module changing the build.prop. if anyone wants to do it this way feel free to dl the attached module.zip. just downloaded some previously "incompatible" apps. idk what happens if u install it on a device that is not daydream-compatible. n6p is the dev device so it is compat but not daydream-ready. as every dev i take no responsibility for anything. u flash this at ur own risk. that it requires magisk to be installed and working is self-explainatory. just ignore the "wrong vendor.img" warning that pops up on booting.
UPDATE: magisk module disabling bug fixed since some versions ago.
V1.1 : quick and dirty commented out out manufacuturer line and zipped it again. still v10/11 magisk template but it works. just tested. template didnt change much anyway to v12 i think.
DaydreamBypass.zip : version for oreo by @tazzkiller
Here you go::
1) Get a build.prop editor out of the play store once you have acquired root access.
2) Locate the following strings of texts and change what is written there to "marlin", without the quotes.
ro.build.product
ro.product.device
ro.product.board
ro.product.name
3) Locate the following strings of texts and change what is written there to "Google", without the quotes.
ro.product.manufacturer
4) Locate the following string of text to "Pixel XL", without the quotes.
ro.product.model
5) Locate the following string of text and change what is written there to "google/marlin/marlin:7.1/NDE63L/3273814:user/release-keys" without the quotes.
ro.build.fingerprint
The last part might not be the proper string of text but I am doing this off of memory. Just look for the text that looks like the above and swap it out. After you do this, reboot your device. You will get an error message or two upon booting up and the first boot may take longer than normal but it works. I've personally done it with my 6P to get proper Daydream store games because I wanted to play Gunjack and ArcSlinger. Your build.prop editor should save the original build.prop as a build.prop.bak. When you are done installing your new games, simply change the new build.prop to build.prop.bak1, and the original back to a build.prop
The only bugs I have noticed with this are that during the first 24 hours after doing this I continually got an overheating message while in daydream even when the device wasn't hot. I don't know if time played a factor or multiple reboots but eventually the message stopped popping up. Let me know if it works for you.
Varking said:
Here you go::
1) Get a build.prop editor out of the play store once you have acquired root access.
2) Locate the following strings of texts and change what is written there to "marlin", without the quotes.
ro.build.product
ro.product.device
ro.product.board
ro.product.name
3) Locate the following strings of texts and change what is written there to "Google", without the quotes.
ro.product.manufacturer
4) Locate the following string of text to "Pixel XL", without the quotes.
ro.product.model
5) Locate the following string of text and change what is written there to "google/marlin/marlin:7.1/NDE63L/3273814:user/release-keys" without the quotes.
ro.build.fingerprint
The last part might not be the proper string of text but I am doing this off of memory. Just look for the text that looks like the above and swap it out. After you do this, reboot your device. You will get an error message or two upon booting up and the first boot may take longer than normal but it works. I've personally done it with my 6P to get proper Daydream store games because I wanted to play Gunjack and ArcSlinger. Your build.prop editor should save the original build.prop as a build.prop.bak. When you are done installing your new games, simply change the new build.prop to build.prop.bak1, and the original back to a build.prop
The only bugs I have noticed with this are that during the first 24 hours after doing this I continually got an overheating message while in daydream even when the device wasn't hot. I don't know if time played a factor or multiple reboots but eventually the message stopped popping up. Let me know if it works for you.
Click to expand...
Click to collapse
oh so its build.prop not permissions. or do i need those too?
will make me a magisk module for the build.prop mods tomorrow or so. and tell u how it worked out. u dont recommend keeping the changed build.prop?
Sent from my Nexus 6P using XDA Labs
All I did is unlock my bootloader, root my phone, and edit the build.prop. I would keep both build.props. It makes it so you can easily switch to the Pixel XL settings to download and install new games, and then load the original 6P ones again after you are done. Editing the build.prop like above had Google email me a welcome to the Pixel family email, too lol.
But I have 100% working daydream and store access just by doing what I listed above.
4RK4N said:
oh so its build.prop not permissions. or do i need those too?
will make me a magisk module for the build.prop mods tomorrow or so. and tell u how it worked out. u dont recommend keeping the changed build.prop?
Click to expand...
Click to collapse
I'm on a Nexus 5X and I'm on Pixel ROM, but I've heard keeping that build.prop change is fine. It doesn't affect Nexus as our OTAs and Stock apps don't need it. It'll just give you access to the Pixel specific apps
My experience on Sony Xperia Z1 says that you need to clear data of Google Play Service and Google Play Store after you modify the XMLs in system. I guess that by doing this, your device will be updated as a "Daydream ready phone" in Google's database.
By the way, Xperia Z1's Daydream doesn't work on AOSP 7.1.1. It crashes. Anyway, after I cleaned the data of those two apps, I can download apps like Daydream, Google VR Service, Daydream Keyboard, etc. from Google Play.
UPDATE:
apparently the build.prop modifications crash google camera (latest purenexus). fc upon opening the app.
also various daydream apps (twilight pioneers, vr karts sprint, etc) report "phone overheating" quite fast and force you to "cool the phone" with a "take it out of the headset and close the app" vr screen.
interstingly disabling the magisk module in magisk manager wasnt enough. build.prop was still set to the pixel xl values. uninstalling my module restored original build.prop.
no "wrong vendor.img" warning, google camera works, i still get "performance reduced. phone overheating." overlay warnings while playing daydream games but no force cool off time.
so i just install the module again once a week to check for updates on daydream apps and then uninstall it again.
anybody figured out how to disable the kinda annoying "overheating" warning while playing? ^^
Sent from my Nexus 6P using XDA Labs
4RK4N said:
UPDATE:
apparently the build.prop modifications crash google camera (latest purenexus). fc upon opening the app.
also various daydream apps (twilight pioneers, vr karts sprint, etc) report "phone overheating" quite fast and force you to "cool the phone" with a "take it out of the headset and close the app" vr screen.
interstingly disabling the magisk module in magisk manager wasnt enough. build.prop was still set to the pixel xl values. uninstalling my module restored original build.prop.
no "wrong vendor.img" warning, google camera works, i still get "performance reduced. phone overheating." overlay warnings while playing daydream games but no force cool off time.
so i just install the module again once a week to check for updates on daydream apps and then uninstall it again.
anybody figured out how to disable the kinda annoying "overheating" warning while playing? ^^
Click to expand...
Click to collapse
About the build.prop, don't change manufacturer. That messes up the camera. Allot.
I'm really interested in making my Samsung Galaxy S7 Edge "Daydream-compatible". I don't even have a Daydream headset, just the regular Gear VR. I really wish that Google would just make a Youtube VR app for Gear VR--it's the only reason why I'd like to give Daydream a try. If you want me to test anything, please let me know!
itinkerstuff said:
I'm really interested in making my Samsung Galaxy S7 Edge "Daydream-compatible". I don't even have a Daydream headset, just the regular Gear VR. I really wish that Google would just make a Youtube VR app for Gear VR--it's the only reason why I'd like to give Daydream a try. If you want me to test anything, please let me know!
Click to expand...
Click to collapse
since it requires the actual daydream headset to activate daydream mode im afraid i cant help you. besides the youtube vr app is optimized for the daydream controller. making it work with the gear vr headset buttons or the gear vr controller would require some rewriting of the yt vr app.
Sent from my Nexus 6P using XDA Labs
i tested this magisk modul on my s7 edge. seems to work. but then my NFC doesnt work anymore ?!?! so daydream doesnt work.
are really all prop need to be changed?
what build.prop item can make NFC unfunctional?
btw. this is the error i got in Need for Speed VR (logcat) ->
"failed to initialize async reprojection, unsupported device"
inteks said:
i tested this magisk modul on my s7 edge. seems to work. but then my NFC doesnt work anymore ?!?! so daydream doesnt work.
are really all prop need to be changed?
what build.prop item can make NFC unfunctional?
btw. this is the error i got in Need for Speed VR (logcat) ->
"failed to initialize async reprojection, unsupported device"
Click to expand...
Click to collapse
try removing the manufacturer line. maybe nfc still works and u can daydream.
just recived my n6p back from rma (ranfom hardware failure) dunno if module still works with latest magisk.
about nfs vr idk. maybe samsung messed up some graphics function. wait no they call it "optimized" xD find a aosp rom and try it again.
Sent from my Nexus 6P using XDA Labs
use magisk prompt incompatible
use magisk daydream prompt： ‘’ incompatible phone ‘’
how to deal with .......
my telephone model is Nexus 6
xiaoluwan said:
use magisk daydream prompt： ‘’ incompatible phone ‘’
how to deal with .......
my telephone model is Nexus 6
Click to expand...
Click to collapse
What? give us a little more than a few random words pls. ur post makes like no sense sry to day that.
ALSO: changed the module to NOT alter manufacturer. i still wouldnt recommend having the module always running. just tested it. still can dl all daydream apps while module is active. module disabling works now with magisk yay. new version in first post.
Sent from my Nexus 6P using XDA Labs
How to get past this screen?
Not able to proceed even if I enter my credentials.
Will this work for leeco lemax2?
Guys don't bother. I got Daydream running on my Moto X Style and virtually all of the 3rd party apps don't work. They either crash on launch or are in full screen 2d mode and not split screen 3d mode. Only the Google made Daydream apps seem to work.
tboy2000 said:
Guys don't bother. I got Daydream running on my Moto X Style and virtually all of the 3rd party apps don't work. They either crash on launch or are in full screen 2d mode and not split screen 3d mode. Only the Google made Daydream apps seem to work.
Click to expand...
Click to collapse
How did u skip add payment option?
baratheon16 said:
How to get past this screen?
Not able to proceed even if I enter my credentials.
Click to expand...
Click to collapse
i never had that screen lol. cant help you sorry. i have a paypal linked with my playstore since ages ago maybe thats why it never asked me.
Sent from my Nexus 6P using XDA Labs
baratheon16 said:
How did u skip add payment option?
Click to expand...
Click to collapse
I never got that option. maybe because I have paypal linked to playstore as previous guy said.
Seriously, don't waste your time.
Greenify can't auto hibernate apps in Xiaomi Redmi Note 4 running the latest Miui version 9.2.1.0 (details attached in screenshot below).Even after granting all the permissions, Greenify fails to click the force stop button & no apps are hibernated.
This is a major bug and leaves Greenify completely non functional in non rooted phones.
This issue must be fixed ASAP!
Video which shows that Greenify doesn't hibernate apps (CHECK VIDEO FOR COMPLETE INFO) :- https://drive.google.com/file/d/1H3h1118X4WXwmeBDNLL0nHiVEkGyWsjH/view?usp=drivesdk
Screenshot of device details attached below.
Please check and revert.
Thanks
Screenshot Of Device details attached below
KauG said:
Greenify can't auto hibernate apps in Xiaomi Redmi Note 4 running the latest Miui version 9.2.1.0 (details attached in screenshot below).Even after granting all the permissions, Greenify fails to click the force stop button & no apps are hibernated.
This is a major bug and leaves Greenify completely non functional in non rooted phones.
This issue must be fixed ASAP!
Video which shows that Greenify doesn't hibernate apps (CHECK VIDEO FOR COMPLETE INFO) :- https://drive.google.com/file/d/1H3h1118X4WXwmeBDNLL0nHiVEkGyWsjH/view?usp=drivesdk
Screenshot of device details attached below.
Please check and revert.
Thanks
Click to expand...
Click to collapse
Not sure of your expectations or what you are trying to show with the video. Greenify does not remove apps from storage nor immediately reduce their memory footprint (although they may happen over time due to normal LMK behavior). It's singular purpose is to block unwanted background behavior without crushing functionality.
While you may have indeed identified a new 'bug' a single data point (your device) does not necessarily extend to all devices and configs - rooted or otherwise.
Davey126 said:
Not sure of your expectations or what you are trying to show with the video. Greenify does not remove apps from storage nor immediately reduce their memory footprint (although they may happen over time due to normal LMK behavior). It's singular purpose is to block unwanted background behavior without crushing functionality.
While you may have indeed identified a new 'bug' a single data point (your device) does not necessarily extend to all devices and configs - rooted or otherwise.
Click to expand...
Click to collapse
Yes brother.I know that Greenify doesn't remove apps from storage but what I'm trying to show here is that when you click on Hibernate Now, Greenify force closes the apps but in this case it fails to do the same.I am not the sole user facing this issue.
This problem has popped up after the latest miui update.
Thanks again
Kaushik
KauG said:
Yes brother.I know that Greenify doesn't remove apps from storage but what I'm trying to show here is that when you click on Hibernate Now, Greenify force closes the apps but in this case it fails to do the same.I am not the sole user facing this issue.
This problem has popped up after the latest miui update.
Thanks again
Kaushik
Click to expand...
Click to collapse
Appreciate the clarification (might want to shorten and/or annotate the video). So you claim the "problem" is related to the latest miui update but then extend the claim to all unrooted phones and demand Greenify "revert" ... to what?
I do see others raising issues with accessibility based functionality and there may indeed be a link. So far none have stated Greenify flat out does not work, only that automatic hibernation doesn't take place the screen is turned off.
Let's see how this plays out as more reports filter in.
Davey126 said:
Appreciate the clarification (might want to shorten and/or annotate the video). So you claim the "problem" is related to the latest miui update but then extend the claim to all unrooted phones and demand Greenify "revert" ... to what?
I do see others raising issues with accessibility based functionality and there may indeed be a link. So far none have stated Greenify flat out does not work, only that automatic hibernation doesn't take place the screen is turned off.
Let's see how this plays out as more reports filter in.
Click to expand...
Click to collapse
Yes!You are correct.In a nutshell with the latest Miui Update (9.2) , Greenify doesn't hibernate the apps after screen lock even after being granted all the required permissions.
This happens in non-rooted devices
Hope that we will find a fix soon
Thanks a lot!
Kaushik
Turn Off MIUI Optimisation
I had same problem on my Mi Max 2 after MIUI update. To solve it just disable MIUI optimization under developer settings and reboot, Greenify will work again as it used to work before MIUI update.
KauG said:
Yes!You are correct.In a nutshell with the latest Miui Update (9.2) , Greenify doesn't hibernate the apps after screen lock even after being granted all the required permissions.
This happens in non-rooted devices
Hope that we will find a fix soon
Thanks a lot!
Kaushik
Click to expand...
Click to collapse
Check v3.9.5 on Play Store. It seems to have the solution for your issue.
jai220 said:
I had same problem on my Mi Max 2 after MIUI update. To solve it just disable MIUI optimization under developer settings and reboot, Greenify will work again as it used to work before MIUI update.
Click to expand...
Click to collapse
Thanks!
This solved the problem!
tnsmani said:
Check v3.9.5 on Play Store. It seems to have the solution for your issue.
Click to expand...
Click to collapse
Thanks!
This solved the problem!
jai220 said:
I had same problem on my Mi Max 2 after MIUI update. To solve it just disable MIUI optimization under developer settings and reboot, Greenify will work again as it used to work before MIUI update.
Click to expand...
Click to collapse
Are you able to grant special ADB Permissions via Pc brother in non rooted Mi device?
In my case,with usb debugging enabled and all permissions granted,I get an error saying "Neither user 2000 nor......."
Kindly help
Thanks
V 3.9.5 does not work on redmi note 3 (miui9)
I noticed this the hibernate now does not works because Xiaomi change force stop button layout.
Yes Sir correct it doesn't work in note 3
KauG said:
Are you able to grant special ADB Permissions via Pc brother in non rooted Mi device?
In my case,with usb debugging enabled and all permissions granted,I get an error saying "Neither user 2000 nor......."
Kindly help
Thanks
Click to expand...
Click to collapse
Me and others in MIUI forums had the same problem with only USB debugging turned on, this is what solved it:
Turn on the following option:
USB debugging -Debug mode when USB is connected
Install via USB -Allow installing apps via USB
USB debugging (Security Settings)- Allow granting permissions and simulating input via USB debugging
It's very simple
1 . Turn off miui optimisation under developer settings
2 . Turn on " FORCE ALLOW apps on external "under
developer settings.
bit.ly/2JXpR7s
Watch this ,
I think this will surely fix your problem.
I'm on xiaomi redmi note 5 pro (india) with miui 10.0.1
0. I'm having the same issue that greenify is not at all able to click the force stop option in the app page in the settings. This renders greenify completely useless in my device, since hibernation isn't working at all. I've been using greenify from last 5 years, and never faced an issue until now.
akhu5 said:
I'm on xiaomi redmi note 5 pro (india) with miui 10.0.1
0. I'm having the same issue that greenify is not at all able to click the force stop option in the app page in the settings. This renders greenify completely useless in my device, since hibernation isn't working at all. I've been using greenify from last 5 years, and never faced an issue until now.
Click to expand...
Click to collapse
I really don't understand why you are using Greenify to go to an app and click force stop ... Why not just go directly to the MIUI settings and force stop it there ?
Anyway, on all my 4 Xiaomis, with the latest and greatest MIUI 10 8.9.2 Developer ROM as at this date, Greenify works perfectly.
Apps under Hibernation are as expected when viewed from the MIUI Settings, they are already Force Closed (Force Close button greyed out), with the Uninstall button available (not greyed out).
Under MIUI Settings, apps under Shallow Hibernation are not Force Closed, and clicking on the button Force Close will force close it and the button becomes greyed out, and after that, the Uninstall button will be ungreyed and available. When you go back to Greenify, the previously shallow hibernated app that was force closed is now under the section of the normal hibernation, no longer under shallow hibernation.
All fine on my side, MM and Nougat Xiaomis, I don't know about Oreo. I think Greenify is still needed for Xiaomi with Oreo, since Xiaomi seems to walk a different path than the others.
hyborian said:
I really don't understand why you are using Greenify to go to an app and click force stop ... Why not just go directly to the MIUI settings and force stop it there ?
Anyway, on all my 4 Xiaomis, with the latest and greatest MIUI 10 8.9.2 Developer ROM as at this date, Greenify works perfectly.
Apps under Hibernation are as expected when viewed from the MIUI Settings, they are already Force Closed (Force Close button greyed out), with the Uninstall button available (not greyed out).
Under MIUI Settings, apps under Shallow Hibernation are not Force Closed, and clicking on the button Force Close will force close it and the button becomes greyed out, and after that, the Uninstall button will be ungreyed and available. When you go back to Greenify, the previously shallow hibernated app that was force closed is now under the section of the normal hibernation, no longer under shallow hibernation.
All fine on my side, MM and Nougat Xiaomis, I don't know about Oreo. I think Greenify is still needed for Xiaomi with Oreo, since Xiaomi seems to walk a different path than the others.
Click to expand...
Click to collapse
I have over 200 apps in my phone. So there are a lot of apps that need to be 'greenified'. And I've noticed that if you go into developer settings and disable 'miui optimisations', then greenify works perfectly. But for the rest, even if the app is open in the background and you select the option to hibernate it, the force close button is greyed out and nothing happens
akhu5 said:
I have over 200 apps in my phone. So there are a lot of apps that need to be 'greenified'. And I've noticed that if you go into developer settings and disable 'miui optimisations', then greenify works perfectly. But for the rest, even if the app is open in the background and you select the option to hibernate it, the force close button is greyed out and nothing happens
Click to expand...
Click to collapse
Oh, yes, I forgot, of course I have MIUI OPtimizations disabled, always, less problems for me. All rooted too, with Greenify4Magisk, and some module to allow Play Services to be dozed.
Well, if an app cannot be force closed in the MIUI settings, then it is something else preventing it from being closed, and Greenify cannot override it. Gboard (Google Keyboard if used) I think is an example, if I remember. Only a few, and system apps which I would not touch anyway. I don't greenify important user message apps like Messenger or Whatsapp, though, I also Whitelist them from deep doze, just playing safe.
Excluding system apps, I have only a few user apps, less than 40 for sure. All greenified except a few I don't want greenified. As for system apps,
I froze many of them that I will never use and safe to freeze of course, surely stronger than doze or hibernate.
akhu5 said:
I have over 200 apps in my phone. So there are a lot of apps that need to be 'greenified'. And I've noticed that if you go into developer settings and disable 'miui optimisations', then greenify works perfectly. But for the rest, even if the app is open in the background and you select the option to hibernate it, the force close button is greyed out and nothing happens
Click to expand...
Click to collapse
hyborian said:
Excluding system apps, I have only a few user apps, less than 40 for sure. All greenified except a few I don't want greenified. As for system apps, I froze many of them that I will never use and safe to freeze of course, surely stronger than doze or hibernate.
Click to expand...
Click to collapse
Ridiculous and counterproductive greenifying a huge app suite. Focus on those that demonstrate bad behaviors; ignore the rest.
hi,
After lock screen for more than few minutes, the screen wake up stop working.
Anyone has any suggestion to fix the problem? I have so far tried "ignore battery optimization" and "launch manually".
THe app tells me to use protected apps but I do not see anywhere in EMUI settings.
It did not work. ''Special access>Ignore optimisations''
It did not work. '' Launch manually''
It did not work. ''I changed my google and instagram accounts.''
especially I am having trouble with instagram and facebook notifications.
Whatsapp notifications are working normally. The phone in the service changed but not resolved. This huawei problem.
Please help me.
EMUI is likely killing off background apps for you, in the name of battery optimization. If rooted, disable the Power Genius app using either Titanium Backup or Service Disabler, and reboot. If not rooted, you can try disabling Power Genius via adb, but I'm not sure it will work.
thref23 said:
EMUI is likely killing off background apps for you, in the name of battery optimization. If rooted, disable the Power Genius app using either Titanium Backup or Service Disabler, and reboot. If not rooted, you can try disabling Power Genius via adb, but I'm not sure it will work.
Click to expand...
Click to collapse
what is your phone model? Anyone using mate 10 pro is having this problem?
ladysuin said:
what is your phone model? Anyone using mate 10 pro is having this problem?
Click to expand...
Click to collapse
Mediapad M5 but issues like this are specific to all EMUI models. For me, disabling Power Genius prevented Google Maps from getting killed off in the background, and also got rid of bugs related to bluetooth music playback..
thref23 said:
Mediapad M5 but issues like this are specific to all EMUI models. For me, disabling Power Genius prevented Google Maps from getting killed off in the background, and also got rid of bugs related to bluetooth music playback..
Click to expand...
Click to collapse
This problem name ''Power Genius'' and Emui has this problem on all devices, is this true?
any fix?
the same as my problem: https://forum.xda-developers.com/mate-10/help/mate-10-pro-gmail-notifications-delay-t3736793
So I've seen this issue occurring in almost every custom ROMs, is there a custom ROM without this issue? Of course other than MIUI. I need this because I have Bluetooth on all the time to get notifications on mi Mi Band 3
I would like to have a fix for this issue, too. I think it is a problem of all Android Pie roms.
Is there a way to solve the issue now? I'm having troubles with this, the speed is under 5Mbps not even enough to watch a 1080p 60fps video on YouTube...is there a kernel maybe which has not this issue? Is it present on official MIUI ROMs too?
Try this
In Developer Options, go to Running Services.
In Goggle Play Services stop NearbyMessagingService.
It's temporary, it will run again once in a while. I think using an app like DisableService may disable it definitely, but it needs root.
extrem0 said:
Try this
In Developer Options, go to Running Services.
In Goggle Play Services stop NearbyMessagingService.
It's temporary, it will run again once in a while. I think using an app like DisableService may disable it definitely, but it needs root.
Click to expand...
Click to collapse
Wow it worked...what is this service for? Will I get notifications and call alerts on my mi band 3 while stopped or not?
This is just awesome, I'll find a way to disable this service for good.
It worked like a charm, and I'm still getting notifications in my Mi Band 3. I used this app
https://play.google.com/store/apps/details?id=com.kunkunsoft.rootservicedisabler
To disable the service permanently. Thanks a lot.
extrem0 said:
Try this
In Developer Options, go to Running Services.
In Goggle Play Services stop NearbyMessagingService.
It's temporary, it will run again once in a while. I think using an app like DisableService may disable it definitely, but it needs root.
Click to expand...
Click to collapse
i have the same issue when pair my mi band 4 on my new redmi note 8 pro miui 11.0.3 i dont want to root my phone and i this setings dont exist on my device ..:crying: can you help me , cause this is very annoying.
I have the same problem on Huawei M20 Lite and band 4. I have Android 10 and i cant find the service to kill any suggestions?
extrem0 said:
Try this
In Developer Options, go to Running Services.
In Goggle Play Services stop NearbyMessagingService.
It's temporary, it will run again once in a while. I think using an app like DisableService may disable it definitely, but it needs root.
Click to expand...
Click to collapse
How to get there?
Can't see any Runing Services option.
Thanks
no such service running
extrem0 said:
Try this
In Developer Options, go to Running Services.
In Goggle Play Services stop NearbyMessagingService.
It's temporary, it will run again once in a while. I think using an app like DisableService may disable it definitely, but it needs root.
Click to expand...
Click to collapse
I am also facing the same problem. There is no such service running on my phone. Currently i am on Lineage OS 16 android 9.
0