Related
Well, i have observed it with Facebook Messenger and Viber, should be the same issue with other greenified applications
The GCM push works fine, but the problem is, that the notification won't be visible till i actually open or unlock my screen
That said, i can see that the application has been woken by a push( seconds or minutes before i get the notification) but you can't see it till you actually open the phone so the application opens in foreground.
I am almost definitely sure this used to work at KitKat normally
I have tested this using Greenify beta(the latest) with the xposed-alpha 14-05 on OnePlus One
Reptant said:
Well, i have observed it with Facebook Messenger and Viber, should be the same issue with other greenified applications
The GCM push works fine, but the problem is, that the notification won't be visible till i actually open or unlock my screen
That said, i can see that the application has been woken by a push( seconds or minutes before i get the notification) but you can't see it till you actually open the phone so the application opens in foreground.
I am almost definitely sure this used to work at KitKat normally
I have tested this using Greenify beta(the latest) with the xposed-alpha 14-05 on OnePlus One
Click to expand...
Click to collapse
I can confirm this too! @oasisfeng you should definitely look into this issue.I've tried it on my two devices running 5.0.2 and 5.1.1 respectively.The notification doesn't come through until I wakeup the screen.The app is waken up but the notification doesn't arrive until I turn on the screen.
Removing the app from greenified list fixes the issue.
Tapped from my furious dogo
vaisakh7 said:
I can confirm this too! @oasisfeng you should definitely look into this issue.I've tried it on my two devices running 5.0.2 and 5.1.1 respectively.The notification doesn't come through until I wakeup the screen.The app is waken up but the notification doesn't arrive until I turn on the screen.
Removing the app from greenified list fixes the issue.
Tapped from my furious dogo
Click to expand...
Click to collapse
Well sometimes, after a random amount of time it may appear.. But the randomness is what troubles me as well..
@oasisfeng Can confirm this. Unless I turn on the screen manually, I don't hear the notification chime. And yes, it did work fine in KitKat.
Have same issue, no notification with Facebook and Messenger.
I get the when screen turns on, but not instantly...after a while.
Any fix?
Sent from my Samsung Galaxy S5 SM-G906K using TapaTalk
Same here, but also without greenify. I switched to a new ROM and phone. So perhaps it is ROM related.
bongster said:
Same here, but also without greenify. I switched to a new ROM and phone. So perhaps it is ROM related.
Click to expand...
Click to collapse
Hi again, I have managed to get it work again. I degreenified all apps, deselected everything under experimentally features. After a reboot I ticked off my normal feature set. And voila I'm getting gcm messages again! I guess I messed something up by using titanium...
BTW I'm using cm 12.1 optimized on a S4
bongster said:
Hi again, I have managed to get it work again. I degreenified all apps, deselected everything under experimentally features. After a reboot I ticked off my normal feature set. And voila I'm getting gcm messages again! I guess I messed something up by using titanium...
BTW I'm using cm 12.1 optimized on a S4
Click to expand...
Click to collapse
Can you be more precise in what you've done?
For now I've made an app with Tasker that closes Facebook and Messenger and then Greenify all my app list and then locks system, so to not put Facebook and Messenger on Greenify and have push messages, but don't constantly have them on Active Apps last if used.
If you want I can share it.
Sent from my Samsung Galaxy S5 SM-G906K using TapaTalk
PIRATA! said:
Can you be more precise in what you've done?
For now I've made an app with Tasker that closes Facebook and Messenger and then Greenify all my app list and then locks system, so to not put Facebook and Messenger on Greenify and have push messages, but don't constantly have them on Active Apps last if used.
If you want I can share it.
Sent from my Samsung Galaxy S5 SM-G906K using TapaTalk
Click to expand...
Click to collapse
OK. I'll try to explain a bit more precisely.
My issue was, that e.g. whatsapp does not receive messages while greenified. I had to start it manually to see if I got new messages.
This started a few days ago with my new phone. Before the new phone I had no problems with greenify in combination with cm12.1.
Here my steps:
1. Remove all Apps from greenify
2. Remove all options from experimental features
3. Restart the phone
4. Select all apps that I want to greenify
5. Reselect my normal options under experimental options.
That's it
Regards
Unfortunately this didn't work for me. But I tried something else that might be helpful. I use Amplify and decided to disable it temporarily to see if I received the GCM push and the notifications, and yes, it did work flawlessly. I might have stopped a wakelock or a service being of google that might be helpful in this.
same issues, then went to settings security device administrators checked greenify now i get push notifications when screens off
stesteste said:
same issues, then went to settings security device administrators checked greenify now i get push notifications when screens off
Click to expand...
Click to collapse
You mean you turned on the administrator setting?
ottomanrage said:
You mean you turned on the administrator setting?
Click to expand...
Click to collapse
yes just for greenify
blisspop 6.3 .arter97 kernel xposed
Same here :/ It's enabled in security settings
stesteste said:
yes just for greenify
blisspop 6.3 .arter97 kernel xposed
Click to expand...
Click to collapse
Well, it didn't help much. I tried flashing all the ROMs available for S3 and it works, partially, in the latest BlissPop. The thing is that GCM push gets received instantaneously but the notification doesn't get posted. It does though, like after 30 mins or so. But never soon enough.
any news why GCM doesnt work proberly anymore with some apps like WhatsApp ? It used to work so i wonder if this a ROM, App, Xposed or Greenify problem.
About 6-8 weeks ago i had this working with CM12.1 on a GT-I9505 (Galaxy S4) with at that time actual apps, modules and ROM.
Phone: PLK_L01
Build: PLK-L01C432B121
The EMUI seems to be very quick to kill apps running in background which is mostly a great thing (too many apps are running background service for nothing).
Unfortunately, some times, it's useful.
I'm using Tasker but it's regularly killed by system (sometimes it last 2 days before being killed and some times only few hours)
Normally, the problem can be avoid in parameters with "protected apps" which normally allow you to select some apps that can not be killed. I've added Tasker to it but it still being killed...
I've also tried to put Tasker as a system app, not working too.
Tasker is also configured as "running in foreground" to avoid being killed, it's also not working.
Did some of you have the same problem with Tasker or another app htat need to run constantly in background ?
I've been using tasker for the last couple of weeks since I got my phone with no problems.
It's on the protected list with only one other app.
Sent from my PLK-L01 using XDA Free mobile app
I have been having issues on Tasker although are slightly different to the OPs. I also have Tasker set as protected and running in the foreground and I can see that it is running in the Taskbar. However, I have found that the tasks aren't being triggered at the times when they are supposed too. It seems that they will only trigger if I disable and then reenable Tasker each time.
The tasks that I have setup were imported from my old Nexus 5 where they were working fine, they are also the same tasks that I was using on a Moto G. Therefore I'm sure that the issue is with the phone and not Tasker itself.
Does anyone have any idea what could be causing this issue?
---------- Post added at 02:57 PM ---------- Previous post was at 02:43 PM ----------
dws199xda said:
I have been having issues on Tasker although are slightly different to the OPs. I also have Tasker set as protected and running in the foreground and I can see that it is running in the Taskbar. However, I have found that the tasks aren't being triggered at the times when they are supposed too. It seems that they will only trigger if I disable and then reenable Tasker each time.
The tasks that I have setup were imported from my old Nexus 5 where they were working fine, they are also the same tasks that I was using on a Moto G. Therefore I'm sure that the issue is with the phone and not Tasker itself.
Does anyone have any idea what could be causing this issue?
Click to expand...
Click to collapse
I've just noticed in the Tasker log that the TaskService keeps getting stopped, I presume that this causing the scheduled tasks not to trigger. But I don't know what could be causing the service to stop, I'm not running any app killers and just the stock power manager
I had a problem with protected apps being killed with all versions of the firmware until I installed b170, which solved it.
Try installing b170 and see if it solves your problem too.
Snackiz said:
I had a problem with protected apps being killed with all versions of the firmware until I installed b170, which solved it.
Try installing b170 and see if it solves your problem too.
Click to expand...
Click to collapse
Thanks for your suggestion however I think I now know that the issue is being caused by the Power Saving mode being set to "Smart", I have switched it back to "Performance" and I can now see that the tasks are being triggered as expected. So I guess that there is an issue with the "Smart" setting where it is still killing Protected apps. BTW I'm running B121
dws199xda said:
Thanks for your suggestion however I think I now know that the issue is being caused by the Power Saving mode being set to "Smart", I have switched it back to "Performance" and I can now see that the tasks are being triggered as expected. So I guess that there is an issue with the "Smart" setting where it is still killing Protected apps. BTW I'm running B121
Click to expand...
Click to collapse
That's great
My problem persisted even after I set the power saving mode to performance.
I used tasker with honor 6, nexus 4 and now honor 7. the only mobile that doesn't work is honor 7, even with last version . Last week finally I uninstalled tasker with 4 months triying to work. the substitute is automateit and automate
Still in b140 and the problem seems to have been solved b itself...
Thank you all for your answers
Having the exact problem with my Huawei phone.
Model: SCL-L21
EMUI: SCL-L21C432B130
edit: I was wrong fortunately. It was not about Tasker and/or EMUI. I was using the "Last Cell" location Profile in Tasker and it didn't work properly so I thought it means Tasker is getting killed by EMUI battery manager (it's really aggressive). Fact is, Huawei is just good at switching cell towers rapidly, choosing between 3G, 2G or 4G while accepting a call or in other circumstances. This was the problem, Tasker is still protected from EMUI battery manager (2 days +).
Just add Tasker to the list of protected apps (PhoneManager - Settings - Protected Apps)
SuperSU doesn't seem to be working the way it always has on my other devices in the past. After successfully flashing TWRP 2.8.7.0 [6.0] EN (by Sminki *xda* repack) on my Honor 7 with multi-tool and then installing SuperSU via TWRP and gaining root access, I rebooted my phone and immediately Google Play wanted me to update the SuperSU app. I updated the SuperSU app and also installed SuperSU Pro that I had purchased previously on another device. I then installed terminal emulator so I could confirm that I had root access by running the su command. However after running the terminal emulator and attempting to use the su command nothing happened. I didn't get an error that I would expect if root wasn't present such as su not found, it just seems to sit there waiting. It then occurred to me that I hadn't received the usual popup from SuperSU asking me whether I wanted to grant root permission.
From what I have been able to work out I do have root access but for whatever reason SuperSU is not displaying its message asking me to grant or deny access. I have managed to establish that I do have root by going into the SuperSU settings and setting the default access as grant rather than prompt after which terminal emulator is able to use the su command.
Does anyone know how I can get the prompt to work? I would rather have SuperSU prompt me when an app requests root access for security reasons since giving any app that requests root unfettered access probably isn't the best idea.
If your problem has anything to do with SSU Pro then I dont say nothing cause dont use it.
Anyway going the same procedure as you I had, after GPlay update, the problem when trying to open SSU with message "SSU binary cant be found" or sth like this. However my SSU has been working (at least it did look alike) giving prompts.
The solution was SSU cleanup, copying and installing SSU once again. If you check some threads here you will find some kinds of initial problems with SSU are quite common.
It looks like it is H7 speciality ;p. You need to flash B330 twice for 100% and you need to install SSU twice ;p
ps. Also "Draw over other apps" on but it was automatic - at least for me
adxuser said:
If your problem has anything to do with SSU Pro then I dont say nothing cause dont use it.
Anyway going the same procedure as you I had, after GPlay update, the problem when trying to open SSU with message "SSU binary cant be found" or sth like this. However my SSU has been working (at least it did look alike) giving prompts.
The solution was SSU cleanup, copying and installing SSU once again. If you check some threads here you will find some kinds of initial problems with SSU are quite common.
It looks like it is H7 speciality ;p. You need to flash B330 twice for 100% and you need to install SSU twice ;p
ps. Also "Draw over other apps" on but it was automatic - at least for me
Click to expand...
Click to collapse
Thanks. Seems to be working now. Also disabling doze altogether on marshmallow seems to have solved a lot of other issues I was having since the marshmallow update and subsequent custom recovery and root install.
Squall88uk said:
disabling doze altogether on marshmallow
Click to expand...
Click to collapse
By "Doze" you mean those switches to kill apps after screen lock or not?
adxuser said:
By "Doze" you mean those switches to kill apps after screen lock or not?
Click to expand...
Click to collapse
No I mean Marshmallows built in doze feature. I have the switches you're talking about set to let the app keep running for important apps like SuperSU anyway but they only affect EMUIs own power manager. Doze and EMUIs power manager seem to fight each other anyway and I don't like how doze stops my notifications coming through with some apps and interferes with other apps that I like to leave running all the time like AcDisplay.
I completely disabled doze altogether using "dumpsys deviceidle disable" in terminal emulator or using adb shell. The only problem is that it will be re-enabled after a reboot so I used the universal init.d app to run an init.d script on every boot to disable it again since the honor 7 kernel doesn't natively support init.d. I have all the apps that I had on lollipop (plus some more that I didn't have on lollipop, since I didn't have root when I used lollipop) set up exactly the way they were then and let EMUI handle the power management. I get about the same battery life that I had in lollipop which is fine for me since I charge it fully every night anyway.
I am just in process of developing opinion on that. For sure made one mistake prefering Google Clock over Huawei (and uninstalling the latter) but now even with adequate settings (for example it should have auto-start set by PM Plus add-on for Phone Manager) I am not so sure of my alarms ; ) I have been accustomed to Vanilla Android till now.
Ok. I had to do my lecture on MM Doze & App Standby functions. Also I am newbie on EMUI.
It looks like that many important things (background GPS runnings apps, notifications, alarms) can be double complicated on MM Huawei :/ (not to mention other EMUI problems e.g. with lock screen)
We have clean MM Android with its problems even for Nexus owners, then we have EMUI with its own background / notifications problems.
So 'Ignore optimisations' switch is by Google. You do not use it but maybe know which Google / Huawei apps should have optimizations off? (I have there Android System WebView - why? Google product should have it invisible, Fused Locations - the same, HiSuite ?, HwAps ?)
Anyway people report that it does not help for GPS tracking apps shutdown problems, but it is rather related to EMUI I think.
PS. 1. I do not think Huawei / Google power managers fight in any way. Huawei power manager stricly speaking these are drivers for hardware needed + basic user power handling setup.
What they did on higher level is this "keeps running after screen off" switch but I would not be so sure if this, set one or the other way (and Huawei soft in general), works properly with GCM messages and other wakeups. One should keep in mind that Huawei sells a lot without Google apps at all.
PS.1.b. Some apps need some changes to work properly with Doze. They are not allowed now to do what they like and when they like. And if they have to say sth they must use GCM message , if they have sth important to say they must use GCM high priority message. Android 5.1 API level 22 alarms do not fire now, there are 2 new methods from what I read. And Google could block spamming "high priority messages". So idea & direction is good I think. For not MM updated apps put them in Ignored.
PS2. In my opinion also you should not confuse B330 power handling issues with Doze.
It could be just Huawei optimizing things: taking away fast charging switch because it is on default now, making changes to power handling etc. or not making changes needed so now it could be the problem with Android. People claiming worse battery life for B330 claim mostly best on B320.
adxuser said:
For sure made one mistake prefering Google Clock over Huawei (and uninstalling the latter) but now even with adequate settings (for example it should have auto-start set by PM Plus add-on for Phone Manager) I am not so sure of my alarms ; ) I have been accustomed to Vanilla Android till now.
Click to expand...
Click to collapse
What's wrong with the Google clock? And what problems did you have after uninstalling the Huawei clock? I use the Google clock as my main clock app and have had no issues with it on either lollipop or marshmallow even after uninstalling the Huawei clock.
adxuser said:
Ok. I had to do my lecture on MM Doze & App Standby functions. Also I am newbie on EMUI.
It looks like that many important things (background GPS runnings apps, notifications, alarms) can be double complicated on MM Huawei :/ (not to mention other EMUI problems e.g. with lock screen)
We have clean MM Android with its problems even for Nexus owners, then we have EMUI with its own background / notifications problems.
Click to expand...
Click to collapse
Agreed. While EMUI does have some of its own features that can be useful a lot of things are twice as complicated as they need to be. I have generally found that just allowing all apps that have notifications you want to receive e.g. twitter set to be allowed to autostart and run in the background as much as they like seems to reduce issues with notifications (still not worked out if it completely stopped any issues), and even then if I want notifications to display correctly on the lockscreen, not only do I need to allow them for each particular app on the lockscreen through the notification manager I still have to use a lockscreen replacement which in my case is AcDisplay. To be honest I have every app set to run on autostart and in the background and I still haven't found that it has much impact on battery life and this seems to solves a lot of these kinds of issues for me. My previous phone (Samsung Galaxy A3) used touchwiz and never had any of these options so I've always assumed that touchwiz/android allowed apps to run when they wanted and access what they wanted within the scope of their permissions and everything always worked fine, admittedly battery life was an issue on that phone but it had a much smaller battery capacity than the Honor 7 and it still lasted me most of a day.
adxuser said:
So 'Ignore optimisations' switch is by Google. You do not use it but maybe know which Google / Huawei apps should have optimizations off? (I have there Android System WebView - why? Google product should have it invisible, Fused Locations - the same, HiSuite ?, HwAps ?)
Anyway people report that it does not help for GPS tracking apps shutdown problems, but it is rather related to EMUI I think.
Click to expand...
Click to collapse
I tried messing with the Ignore optimisations switch when I first upgraded to Marshmallow and it didn't seem to make any difference apps were still being afflicted with issues. I asked honor uk exactly what it did and whether it was for doze or not and they didn't know. I'm sure if I spoke Chinese and asked the Chinese customer service they would be able to tell me straight away but I never managed to find out. Even with doze disabled completely on my device I still have it set to ignore optimisations for all apps in case its something to do with EMUI.
adxuser said:
PS. 1. I do not think Huawei / Google power managers fight in any way. Huawei power manager stricly speaking these are drivers for hardware needed + basic user power handling setup.
What they did on higher level is this "keeps running after screen off" switch but I would not be so sure if this, set one or the other way (and Huawei soft in general), works properly with GCM messages and other wakeups. One should keep in mind that Huawei sells a lot without Google apps at all.
Click to expand...
Click to collapse
What I meant by fight is that the 2 have their own settings rather than these being integrated with each other. So for example when specify that I want an app to be able to run in the background while the screen is off in an ideal world this would also tell Google's doze that I do not want it to doze that app. otherwise I have to effectively set the same thing twice even though it may be called different things.
adxuser said:
PS.1.b. Some apps need some changes to work properly with Doze. They are not allowed now to do what they like and when they like. And if they have to say sth they must use GCM message , if they have sth important to say they must use GCM high priority message. Android 5.1 API level 22 alarms do not fire now, there are 2 new methods from what I read. And Google could block spamming "high priority messages". So idea & direction is good I think. For not MM updated apps put them in Ignored.
Click to expand...
Click to collapse
I like the idea of doze in general and I'm generally a fan of most things that google do with android. If i was running a nexus or an AOSP rom I would definitely leave doze activated and only disable its optimization for apps that either coded with doze in mind or apps which I personally consider to be high priority regardless of whether google agrees such as twitter. I lie to get twitter notification that I have enabled as soon as the tweet they link to is tweeted not at the intervals that doze allows apps to update at. But that's a personal thing rather than an issue with the idea. So for YouTube notifications for example I would be quite happy for doze to run the show.
adxuser said:
PS2. In my opinion also you should not confuse B330 power handling issues with Doze.
It could be just Huawei optimizing things: taking away fast charging switch because it is on default now, making changes to power handling etc. or not making changes needed so now it could be the problem with Android. People claiming worse battery life for B330 claim mostly best on B320.
Click to expand...
Click to collapse
My intention has never been to confuse EMUI's power handling with Doze. I have just been trying to simplify the issue for me. as I have already said I generally allow any apps to do what they want both in EMUI's settings and by disabling doze as its simpler that way for me. Battery has never been an issue for me with either lollipop (B180) or marshmallow (B330) for me personally but i'm sure for some people it can be.
Squall88uk said:
What's wrong with the Google clock? And what problems did you have after uninstalling the Huawei clock? I use the Google clock as my main clock app and have had no issues with it on either lollipop or marshmallow even after uninstalling the Huawei clock.
Click to expand...
Click to collapse
nothing wrong, in fact I've chosen it deliberately.
Basically prefer Google apps cause they can be updated and whats more new features are added from time to time, with let's say B330 stock you are left with B330 stock unless and if Huawei pushes sth new.
Just for some producers ROM's there are sometimes apps good enough and also interconnected on some levels with launcher / lock screen / power management that it is better to leave them & even make use of them.
Squall88uk said:
Even with doze disabled completely on my device I still have it set to ignore optimisations for all apps in case its something to do with EMUI.
Click to expand...
Click to collapse
Rather strange for me what you're doing.
Squall88uk said:
What I meant by fight is that the 2 have their own settings rather than these being integrated with each other. So for example when specify that I want an app to be able to run in the background while the screen is off in an ideal world this would also tell Google's doze that I do not want it to doze that app. otherwise I have to effectively set the same thing twice even though it may be called different things.
Click to expand...
Click to collapse
It cant be integrated, it is Google licensed system. Doze & App standby these are powerfull, long-term features.
This EMUI function is just easy switch to kill sth after screen off. Not sure of it
Also not sure of this auto-start PM Plus utility It is not only auto-start on system start but also start on events. Powerfull mess with many apps without granular controls.
However I use both ;p
edit. ok, it looks you're right about Doze. I.e. Huawei Doze problem. Here for Mate 8:
http://forum.xda-developers.com/showpost.php?p=64827731&postcount=15
Not solved as I see (but no time to read everything)
So Paul @paulobrien solution is with his ROM, your solution is to shut down Doze, I would prefer Doze properly working on (rooted) stock solution
adxuser said:
The solution was SSU cleanup, copying and installing SSU once again. If you check some threads here you will find some kinds of initial problems with SSU are quite common.
Click to expand...
Click to collapse
I have the same problem on my tablet Huawei MediaPad T1 8.0 Pro.
Please explain exactly what supposed to mean is "SSU cleanup, copying and installing SSU once again".
If one makes SSU cleanup then root access will flee for good and installing SSU again encounter the stark barrier, right?
If of course by "cleanup" you mean SuperSU's SETTINGS -> CLEANUP -> Reinstall (?)
@ioy
Do you have EMUI 4.0 on your tablet?
Some tips & tricks work between some Huawei models but for sure not each on everyone...
Anyway I made (in SSU) cleanup for full unroot (if I remember correctly :/) and by "copying & installing" I mean H7 procedure to copy and install via TWRP.
So full unroot and full root once again and in my case it solved my problem.
@adxuser, and what is EMUI 4.0 and how to check if it is on the tablet?
Where to learn about these tip & tricks?
I do not have TWRP because I wanted to have warranty still intact so not unlocked bootloader, and that's why I have unrooted with KingRooot and afterwards switched to SuperSU with SuperSume.
Please, respond...
How to use cleanup options in SuperSu, there're several ones intended for switching to another su application - all of them work the way they need TWRP or maybe it is possible to switchin the system (booted)?
@ioy
what is EMUI 4.0 and how to check if it is on the tablet?
Where to learn about these tip & tricks?
I do not have TWRP because I wanted to have warranty still intact so not unlocked bootloader, and that's why I have unrooted with KingRooot and afterwards switched to SuperSU with SuperSume.
Click to expand...
Click to collapse
Emotion^^ User Interfece - Huawei visual & control overlay over Android.
For your http://www.gsmarena.com/huawei_mediapad_t1_8_0-6705.php 4.3 not upgradeble Android it is probably 2.0? (settings > about).
Tips & tricks those are some common to EMUI solutions - working on many Huawei models. They are nowhere together to be found, you have to search in all Huawei models if you are looking for sth. special. Anyway as you probably understand from JellyBean EMUI no.x to MM EMUI no.4.0 (or 4.1) that is a long way (some common things could even work however).
And also I am not a root specialist but if you have a locked bootloader SSU will never work so make a full cleanup and do not try again
Maybe this KingRoot will work but search for info on that.
ps. in most "normal" countries unlocked bootloader hasn't got anything to warranty.
Yes, KingRoot worked normally, prompt popup windows worked neatly.
However, Huawei itself warns if you unlock the bootloader then they will not help you anymore in case of trouble. And as you maybe know already, Huawei official assistance is needed in doing unlocking bootloader, it is done through their site and first this terrible warning is displayed... (presumably they register phone's IMEI, serial number and these data is then spread to warranty service outposts worldwide)
Yes, they can track and they probably track a lot more easily
Regarding warranty it may and it vary from continent/country to continent/country but local (e.g. european) regulations take effect on that matter.
So Huawei China can even track what I did with the phone yesterday at 6pm but when I am able to relock the phone (even with status relocked) and it could be seen that it is malfunctioning because of hardware failure then I am talking to Huawei in Europe and I am totally not interested what Huawei China has to say.
So sometimes there are some commom myths and you should check (in a proper way ) what are the possibilities.
And you have cited wrong model, this one is Huawei MediaPad T1 PRO LTE:
http://www.gsmchoice.com/en/catalogue/huawei/mediapadt18.0lte/Huawei-MediaPad-T1-8.0-LTE.html
It has 4.4.4 Android version, and Emotion UI version 2.3, so what are these tips & tricks for this?
Please try to provide any clue, about those tips& tricks in respect of popup windows, as as I can see usual popups for any application are not present in this Huawei model... Apparently something must block them in a regular manner...
ioy said:
And you have cited wrong model, this one is Huawei MediaPad T1 PRO LTE:
http://www.gsmchoice.com/en/catalogue/huawei/mediapadt18.0lte/Huawei-MediaPad-T1-8.0-LTE.html
Click to expand...
Click to collapse
Quite possibly. Just a quick look.
As you probably understand we are on H7 subforum and I am not interested in other devices with its variants.
ioy said:
It has 4.4.4 Android version, and Emotion UI version 2.3, so what are these tips & tricks for this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66946525&postcount=12
Allright, how is it possible to switch off / disable this EMUI? What to freeze without bricking the phone? Presumably indeed this blocks popup windows itself and at all it seems providing no gain, plain Android is better and there are many apps on PlayStore with genius functions and full user's control, so please which system or internal memory apks are responsible for this EMUI and one normally can freeze them thus freeing the 'core' Android system from this dubious attraction?
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.
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