Hi,
One of the reasons I use greenify and buy the donate package is the wakeup path cut operation.
But when I upgrade version 2.9, I found the icon disappeared.
Can anyone give me any instruction?
veinpy said:
Hi,
One of the reasons I use greenify and buy the donate package is the wakeup path cut operation.
But when I upgrade version 2.9, I found the icon disappeared.
Can anyone give me any instruction?
Click to expand...
Click to collapse
Go to Settings in Greenify, tap Troubleshooting and then "Apps are not auto-hibernating". Then you will get the option to enable Wake-up Tracker. By default, it is off. After enabling it, follow the usual procedure to invoke the scissors icon.
For me this option don't appear. Only appearQquick Action Notification toggle
Wake-up Tracker requires READ_LOGS permission to work. Follow the instructions here to activate it:
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
BTW, Wake-up Tracker cannot work with Shallow Hibernation.
tnsmani said:
Go to Settings in Greenify, tap Troubleshooting and then "Apps are not auto-hibernating". Then you will get the option to enable Wake-up Tracker. By default, it is off. After enabling it, follow the usual procedure to invoke the scissors icon.
Click to expand...
Click to collapse
im using rooted a7 sm-a710fd android 6.0.1, i have turned on wake-up tracker but still there is no scissor icon or cut paths icon.. it was working on android 5.1
raza3434 said:
im using rooted a7 sm-a710fd android 6.0.1, i have turned on wake-up tracker but still there is no scissor icon or cut paths icon.. it was working on android 5.1
Click to expand...
Click to collapse
See the Dev's post above. Further, the scissors icon will not appear for all apps. It will appear only when you try to manually hibernate some apps which were woken up by another app/process. In other words, the app should have been already chosen for hibernation by you and if it is still woken up by another app/process, the icon will appear when you try to MANUALLY hibernate it.
tnsmani said:
See the Dev's post above. Further, the scissors icon will not appear for all apps. It will appear only when you try to manually hibernate some apps which were woken up by another app/process. In other words, the app should have been already chosen for hibernation by you and if it is still woken up by another app/process, the icon will appear when you try to MANUALLY hibernate it.
Click to expand...
Click to collapse
thank you, i understand what you said, i have checked everything and already know what u are saying but problem is still there, i have used MM Debloater script not sure if it is the reason..
I am having the same problem on my galaxy s7. With stock based superman rom it worked. Not with a note7 port rom it doesn't. And i followed every steps written in this thread
Sent from my SM-N930F using XDA-Developers mobile app
Black_Focus_X said:
I am having the same problem on my galaxy s7. With stock based superman rom it worked. Not with a note7 port rom it doesn't. And i followed every steps written in this thread
Sent from my SM-N930F using XDA-Developers mobile app
Click to expand...
Click to collapse
This is what the Dev says about the current beta:
"v2.9.5 beta 2
Wake-up cut-off now works on Android 7.0 (root).
Improved the overall stability and smoothness of non-root auto-hibernation."
So try the current beta.
oasisfeng said:
BTW, Wake-up Tracker cannot work with Shallow Hibernation.
Click to expand...
Click to collapse
Oh this is it. A clarification in red in the shallow hibernation is needed.
If I turn off shallow hibernation, cut what I need, then turn on SH again, the cutoff paths works?
tnsmani said:
This is what the Dev says about the current beta:
"v2.9.5 beta 2
Wake-up cut-off now works on Android 7.0 (root).
Improved the overall stability and smoothness of non-root auto-hibernation."
So try the current beta.
Click to expand...
Click to collapse
I already use latest beta...
Sent from my SM-N930F using XDA-Developers mobile app
Found any solution?
Nope
Sent from my SM-N930F using XDA-Developers mobile app
Already not fixed in update
Sent from my SM-N930F using XDA-Developers mobile app
@oasisfeng , The wake-up tracker doesnt work on Note 7 ported roms on the s7 edge for me too. Im all rooted and have the donation pack too. The same works on s7 edge based roms and also on other phones i have like Xperia z5 Premium. Could you please help me out ?
Thanks
Ashray_Vk said:
@oasisfeng , The wake-up tracker doesnt work on Note 7 ported roms on the s7 edge for me too. Im all rooted and have the donation pack too. The same works on s7 edge based roms and also on other phones i have like Xperia z5 Premium. Could you please help me out ?
Thanks
Click to expand...
Click to collapse
Some custom ROM may have some low-level Android features disabled. Could you verify whether logcat is disabled in that ROM, since wake-up tracker depends on event log to analyze the wake-ups?
oasisfeng said:
Some custom ROM may have some low-level Android features disabled. Could you verify whether logcat is disabled in that ROM, since wake-up tracker depends on event log to analyze the wake-ups?
Click to expand...
Click to collapse
As far as I know, it's not disabled. But I'll ask the devs anyway
Ashray_Vk said:
As far as I know, it's not disabled. But I'll ask the devs anyway
Click to expand...
Click to collapse
Could you please execute this command in adb shell:
logcat -v time -b events -d > events.log
and send the output file (events.log) to me. (via DM or email)
oasisfeng said:
Could you please execute this command in adb shell:
logcat -v time -b events -d > events.log
and send the output file (events.log) to me. (via DM or email)
Click to expand...
Click to collapse
Surely. As soon as im home. At work now
@oasisfeng
I have a same problem. I checked with he developer. Logcat is runing 100%
I cannot turn accesibility on for greenify though. I get some error about languahe settings.
Everything else is on that should be on.
Can u please help?
Edit: shallow hibernation is off, donation package running on S5, Thunderblot 4.5 rom
Sent from my SM-G532F using Tapatalk
Related
Now with Nougat Support!
Shout to Rovo89 for the Xposed Framework, and the various people who inspired this.
Sensor Disabler (previously known as Disable Proximity) is an Xposed application that allows you to disable or modify most of the sensors on your device, including the proximity sensor. It supports Tasker for changing the sensor status (via In-App Purchase), a blacklist/whitelist for choosing how certain apps will respond to Sensor Disabler, and a reliable and efficient way of modifying and disabling sensors without causing unnecessary slowdown on the device.
I can't offer support for phones that I don't own, but if your phone runs a close to AOSP ROM (for instance Nexus devices) or a CM-based/Lineage ROM (which I can easily see the sources for), this should work. If you're having issues, try to gather the logs from the Xposed app that relate directly to this app and post them here as well as your issue. I recommend reading over the logs yourself to see if the issue might be with your Xposed installation and not the app itself.
Links:
Source Code
Module
Google Play Link
This has been tested on:
Nexus 5 running 4.4.2.
Nexus 5 running 5.0.1.
Nexus 5 running 5.1.
LG G2 running 4.2.2.
OnePlus One running CM11S.
OnePlus One running COS12.
Nexus 6P running 6.0
OnePlus One running LineageOS 14 (Nougat)
Currently, this mod works on 4.2 - 7.1.
Post any questions/requests/etc in this thread, and I'll attempt to get to them in a timely manner.
- Wardell Bagby.
here's link : http://repo.xposed.info/module/com.mrchandler.disableprox
and there is any ways to disable it totally??
WardellChandler said:
I saw a fairly important need for this app, so I decided to make it.
Click to expand...
Click to collapse
Why could I need this app and want to disable proximity?
defim said:
Why could I need this app and want to disable proximity?
Click to expand...
Click to collapse
Someone like me who does not find much of a use of the proximity sensor which has been eating up battery while im on call, would be interested in this feature
Don't work with Themasek KK 4.4.4 v105. Galaxy S3
HGT - Galaxy S3 S5 blue - any KK ROM
defim said:
Why could I need this app and want to disable proximity?
Click to expand...
Click to collapse
If, like me, your Nexus 4's proximity sensor is dead and you're unable to wake up your phone during calls!
HorstiG said:
Don't work with Themasek KK 4.4.4 v105. Galaxy S3
HGT - Galaxy S3 S5 blue - any KK ROM
Click to expand...
Click to collapse
Alrighty, thanks for that!
ravijani said:
and there is any ways to disable it totally??
Click to expand...
Click to collapse
Thanks. Possibly, using the Hardware Disabler app on the Play Store. I've never gotten that to work for me, though.
There might also be a way to truly truly disable it using Xposed, but I'd need to delve extremely deep into the Android sources. I'll look more into it, but definitely no promises.
Could you make an app that has an interface and that can disable touch?
Basically when I put YouTube on my device and give it to my daughter to watch her cartoons she presses the screen and videos go back and forth and even exit, I've tried searching everywhere for a touch disable option, there's 2 apps on the play store but don't work, are very old and outdated...
If anybody knows where I can find one please let me know....
Sent from my GT-I9195 CarbonKat 4.4.4
kamikaze702k said:
Could you make an app that has an interface and that can disable touch?
Click to expand...
Click to collapse
To get OT for a minute, while this might be possible, there are some inherent difficulties associated with this. You should look into an app like Live Lock: YouTube & Kids Lock for Android. Best of luck!
Update 1.01 don't work. S3 Temasek KK 4.4.4 v1.05, Boeffla Omni Kernel.
HGT - Galaxy S3 S5 blue - any KK ROM
HorstiG said:
Update 1.01 don't work. S3 Temasek KK 4.4.4 v1.05, Boeffla Omni Kernel.
Click to expand...
Click to collapse
Hmm. I'll have to wait until I get get the 4.4.4 source straight. Expect an update in a day or so for that.
EDIT: So I've gotten the 4.4.4 source, and I can't see why it wouldn't work. Did you reboot after installing?
A problem that plagued me for a year, gone in 2 minutes. Thank you very much.
rohail6 said:
A problem that plagued me for a year, gone in 2 minutes. Thank you very much.
Click to expand...
Click to collapse
That's what I made it for! I'm very happy to help!
Instead of disabling the sensor, you could try recalibrating, as described in this post. it worked for my Sprint GN2.
http://forum.xda-developers.com/showthread.php?t=2569141
Since the N4 suffers an annoying bug which causes a crackling noise to the headset signal whenever the proyimity sensor is active, I'd like to request an option to disable the sensor only when headset is plugged.
It would be even better if you would consider to integrate your app with Tasker so we could disable the sensor on different contexts too.
cramu said:
Since the N4 suffers an annoying bug which causes a crackling noise to the headset signal whenever the proyimity sensor is active, I'd like to request an option to disable the sensor only when headset is plugged.
It would be even better if you would consider to integrate your app with Tasker so we could disable the sensor on different contexts too.
Click to expand...
Click to collapse
I actually have been wanting to try out Tasker support, so I'll look into that. I think I can push an update that'll disable during headphone disconnected only in the next few days, then I'll work on Tasker support.
Thanks for responding so quickly and for considering my suggestions.
Working on HTC Sensation XE running Vipers ROM 5.1.2 (Android 4.1.2)
Thank you very much!!! :good: I finally solved a problem due to the proximity sensor (probably broken) whose wakelock plagued my battery after a call or automatic brightness; thank you!
Noob question: can RILJ wakelock also be related to the proximity sensor?
Bino92 said:
Working on HTC Sensation XE running Vipers ROM 5.1.2 (Android 4.1.2)
Thank you very much!!! :good: I finally solved a problem due to the proximity sensor (probably broken) whose wakelock plagued my battery after a call or automatic brightness; thank you!
Noob question: can RILJ wakelock also be related to the proximity sensor?
Click to expand...
Click to collapse
To be honest, I don't know. I've never come across the RILJ wakelock issue (literally had to Google it to figure out what you meant) but it could be a possibility?
Although, according to this article here, it has something to do with accessing your location.
My two cents is, go ahead and give my app a try and if it works, great! But I don't know anything about the RILJ wakelock issue to provide any concrete data on whether this will fix it or not. Doesn't hurt to try!
I'm using greenify on CM11 (android 4.4.4). I have xposed modules installed. I want to know what is the difference between Root mode & Boost mode... And also is there any disadvantages of using experimental features?
If you are using the beta build, maybe, otherwise not.
Boost mode requires xposed to be active, where root mode only needs root permissions.
Boost mode is more powerful
Tapatalked from my D802 - CM12
Wycer said:
If you are using the beta build, maybe, otherwise not.
Boost mode requires xposed to be active, where root mode only needs root permissions.
Boost mode is more powerful
Tapatalked from my D802 - CM12
Click to expand...
Click to collapse
I'm using v2.5.2 downloaded from play store
Yeah that's the normal version, everything will work fine
Tapatalked from my D802 - CM12
Wycer said:
Yeah that's the normal version, everything will work fine
Tapatalked from my D802 - CM12
Click to expand...
Click to collapse
I switched to BOOST mode. Everything was working fine, then I noticed that greenify is unable to hibernate facebook automatically. I manually hibernated facebook. Then opened facebook again & after sometimes noticed that greenify has hibernated facebook. My question is why did it fail?
Sometimes apps uses some ways to stay in Android system memory, greenify can't freeze those
Tapatalked from my D802 - CM12
Wycer said:
Sometimes apps uses some ways to stay in Android system memory, greenify can't freeze those
Tapatalked from my D802 - CM12
Click to expand...
Click to collapse
Any solution?
Freezing them through a Tasker plug-in or a greenify shortcut will help I believe, at least does for my aps
Tapatalked from my D802 - CM12
Sometimes hibernated apps are waking up automatically! Is it a bug of Greenify?
No, some other apps might waking them app. Enable the cut off thing and go over the app that wakes up and a pair of scissors will appear.
Sent from my bacon!!!!!
NickosD said:
No, some other apps might waking them app. Enable the cut off thing and go over the app that wakes up and a pair of scissors will appear.
Sent from my bacon!!!!!
Click to expand...
Click to collapse
The problem is happening in BOOST mode but not happening in ROOT mode. Should I revert back to ROOT mode?
If you don't have xposed installed, yes.
Sent from my bacon!!!!!
NickosD said:
If you don't have xposed installed, yes.
Sent from my bacon!!!!!
Click to expand...
Click to collapse
I have Xposed
arpanbag1996 said:
The problem is happening in BOOST mode but not happening in ROOT mode. Should I revert back to ROOT mode?
Click to expand...
Click to collapse
It is not a problem. Boost mode detects it, Root mode does not.
Since you have Xposed, it is for you to decide whether to use Boost or Root mode.
NickosD said:
No, some other apps might waking them app. Enable the cut off thing and go over the app that wakes up and a pair of scissors will appear.
Sent from my bacon!!!!!
Click to expand...
Click to collapse
I don't see where this "cut off thing" is?
Can you clarify plz?
In using 2.6 beta 4
ek69 said:
I don't see where this "cut off thing" is?
Can you clarify plz?
In using 2.6 beta 4
Click to expand...
Click to collapse
Go to "Experimental Features" and enable "Wake-up Tracker and Cutoff".
Then when you click an app in Greenify which is pending hibernation (which was woken by another app), one of the options you will get is the "Scissors" icon.
tnsmani said:
Go to "Experimental Features" and enable "Wake-up Tracker and Cutoff".
Then when you click an app in Greenify which is pending hibernation (which was woken by another app), one of the options you will get is the "Scissors" icon.
Click to expand...
Click to collapse
I don't have that option ( "Wake-up Tracker and Cutoff") in my list. I am on the beta version though, maybe it's not in that one?
Attaching images of my experimental features list
ek69 said:
I don't have that option ( "Wake-up Tracker and Cutoff") in my list. I am on the beta version though, maybe it's not in that one?
Attaching images of my experimental features list
Click to expand...
Click to collapse
In Greenify beta, 'wake up tracker & cut off' is stated (by the Dev) to be built in, which means when an app is greenified, all its links are cut off automatically. That is why you don't get that option in beta.
However I have no idea whether that is working correctly since I have gone back to the stable version and not using beta since I found this feature not suitable for my needs.
tnsmani said:
In Greenify beta, 'wake up tracker & cut off' is stated (by the Dev) to be built in, which means when an app is greenified, all its links are cut off automatically. That is why you don't get that option in beta.
However I have no idea whether that is working correctly since I have gone back to the stable version and not using beta since I found this feature not suitable for my needs.
Click to expand...
Click to collapse
I found that when you click on some apps that are currently not in hibernation mode, sometimes a scissors icon appears in top left and you have to click that to enable that feature. Not all apps get that icon when clicked on though.
Tapatalk is one example, see attached screenshot
After two pagesin this thread i don't say what is the difference between root and boot mode....
I understand Boost mode with an experimental feature (with donation and xposed) it's capable to block any "push wake up" by other application....
There's other?
Disable restricting Android API to get recent tasks in Lollipop and newer. This restriction causes that some apps (e.g. Greenify) don't work as they should, since Android now returns nothing or useless info when they want to get recent tasks. This module should fix it as it was before.
http://repo.xposed.info/module/com.pyler.unrestrictedgettasks
Thank you! Switchr now working on Lollipop with this!
Double thanks to @pyler to bring back recent task usable again....
Sent from my SM-N910G using Tapatalk
chaimc said:
Thank you! Switchr now working on Lollipop with this!
Click to expand...
Click to collapse
Oh yeah!! You're the man pyler
pyler said:
Disable restricting Android API to get recent tasks in Lollipop and newer. This restriction causes that some apps (e.g. Greenify) don't work as they should, since Android now returns nothing or useless info when they want to get recent tasks. This module should fix it as it was before.
http://repo.xposed.info/module/com.pyler.unrestrictedgettasks
Click to expand...
Click to collapse
Does it work with 5.1.1 superalpha xposed?
Thanks dev.. More wisdom. Work great on lollipop
Sure, it works on any Xposed build for 5.0,5.1.
Thanks a ton dev, working smoothly [emoji106]
Sent from my YU5010 using Tapatalk
Would I need this with a nexus 5 with greenify and amplify?
Xenonhd rom
Imho the app developers should update their apps. There are new permissions like PACKAGE_USAGE_STATS. I checked wiht an M emulator my apps (non-xposed & non-root apps) TaskManager and KeepRunning and they still work without this module
defim said:
Imho the app developers should update their apps. There are new permissions like PACKAGE_USAGE_STATS. I checked wiht an M emulator my apps (non-xposed & non-root apps) TaskManager and KeepRunning and they still work without this module
Click to expand...
Click to collapse
Is that a yes or no?
PackageUsageStats is not same as getRecentTasks. I doubt you can get same info from PUS as in getRecentTasks in pre-LP.
Hi,
May I ask what you mean by giving the example of Greenify? What exactly is the shortcoming with Greenify in L in contrast to pre-L?
I was following their change logs and it seems to me that there is nothing Greenify nowadays couldn't do in L. What am I missing?
I am just asking, because I am not sure why and whether I should install this module as a Greenify (beta) user.
Wouldn't it be easier to introduce your fix in their own code?
Modify module to work for only one app?
I'm wondering how I could modify this module to make it so that it only works for one particular app (Last App Switcher). I like the idea of Android preventing third party apps from getting my recent app details, but I also miss using LAS.
I'm thinking that in the call to XposedBridge.hookAllMethods() I could replace the third argument XC_MethodReplacement.returnConstant(true) with a instance of XC_MethodHook that checks the calling app's package name and if it matches the package I want to target (com.abhi.lastappswitcher) then it would return true, otherwise it would call the standard Android isGetTasksAllowed function normally. I've never done any Xposed development though so I'm not sure I'm going about it the right way.
Hi @pyler,
Is this module still needed in Android M for apps like Greenify?
Thanks
Phil
Droidphilev said:
Hi @pyler,
Is this module still needed in Android M for apps like Greenify?
Thanks
Phil
Click to expand...
Click to collapse
I want to know that too
Anymore info on this? Im on g900i lolipop.
Sent from my Samsung Galaxy S5 using XDA Labs
Needed for Marshmallow? Thx
Sent from my lightning fast SM-G930F (S7)
No, since many devs already use new APIs.. If you have old app, not updated for LP/MM, this maybe needed for full app functionality.
A fantastic module, some apps still require this to work, an app from myself for myself for example: RAMTool https://tiziocaio.store.aptoide.com/app/market/com.thepriest.andrea.ramtool/1422/22796519/RAM+Tool
Since my app analyzes recent and running apps and on a regular interval, I fear that using UsageStatsManager will degrade performance, I am afraid that the cpu will be more stressed.
Rewriting my code to get worse perfornce than before doesn't make me happy ...that's probably the reason i hadn't yet wrote it.
Are my fears unfounded?
I noticed a few days ago that Facebook was no longer hibernating when I shut off my screen. It turns out that the option to ignore app state is no longer available, which I was using to hibernate apps like Facebook that always show up as working. Is there a reason for this? Because this option is not available, Greenify will no longer auto-hibernate Facebook. Currently running on a rooted Nexus 6P.
chalkitychalke said:
I noticed a few days ago that Facebook was no longer hibernating when I shut off my screen. It turns out that the option to ignore app state is no longer available, which I was using to hibernate apps like Facebook that always show up as working. Is there a reason for this? Because this option is not available, Greenify will no longer auto-hibernate Facebook. Currently running on a rooted Nexus 6P.
Click to expand...
Click to collapse
This feature is still available in Greenify and I used it yesterday.
Either Facebook or N6P should be the reason if it is not working for you. Most likely Facebook.
tnsmani said:
This feature is still available in Greenify and I used it yesterday.
Either Facebook or N6P should be the reason if it is not working for you. Most likely Facebook.
Click to expand...
Click to collapse
Are you running 2.8 beta 2? It was available on my phone as of a week ago, and the option isn't available for any apps, so it isn't my phone and it isn't Facebook. I recently switched to systemless root, could that be it?
For me is working fine (rooted+Xposed)
chalkitychalke said:
Are you running 2.8 beta 2? It was available on my phone as of a week ago, and the option isn't available for any apps, so it isn't my phone and it isn't Facebook. I recently switched to systemless root, could that be it?
Click to expand...
Click to collapse
Yes, I am on 2.8 beta 2.
Some Apps are not comfortable with the root built into the ROM.
Try SuperSU.
tnsmani said:
Yes, I am on 2.8 beta 2.
Some Apps are not comfortable with the root built into the ROM.
Try SuperSU.
Click to expand...
Click to collapse
I am using SuperSU, version 2.56 beta with systemless root. I'll try going back to regular root and I'll report on whether or not the ignore running state option comes back.
I'm an idiot. You have to manually hibernate a working app before it gives you the option to ignore running state permanently. Thanks for your help, everybody!
I am on 2.8.1 with root mode. I don't seem to find the manual hibernate option to ignore app state. I got this app that's abusing the state and shows "working" all the time.
chinesecooler said:
I am on 2.8.1 with root mode. I don't seem to find the manual hibernate option to ignore app state. I got this app that's abusing the state and shows "working" all the time.
Click to expand...
Click to collapse
Try the way described in the post above yours.
Any specific reason to stick with an older version? If not, update to the latest and then try.
tnsmani said:
Try the way described in the post above yours.
Any specific reason to stick with an older version? If not, update to the latest and then try.
Click to expand...
Click to collapse
I think that's the latest version. I have tried to select the app and click the hibernate button. It does stop the app immediately but doesn't mention anything about app state.
chinesecooler said:
I think that's the latest version. I have tried to select the app and click the hibernate button. It does stop the app immediately but doesn't mention anything about app state.
Click to expand...
Click to collapse
Are you running 2.9.beta4? It does have this option and I am running it without issues on both my devices.
tnsmani said:
Are you running 2.9.beta4? It does have this option and I am running it without issues on both my devices.
Click to expand...
Click to collapse
I just installed beta 4. Nothing changed other than getting a notification saying that the hibernation is postponed. I don't have xposed framework though. Could you please explain a little bit more about how you did it?
chinesecooler said:
I just installed beta 4. Nothing changed other than getting a notification saying that the hibernation is postponed. I don't have xposed framework though. Could you please explain a little bit more about how you did it?
Click to expand...
Click to collapse
Xposed doesn't have anything to do with this option. I hope you are running it in root or boost mode.
You may not get this option on the App Analyzer screen. When you are on the main screen of Greenify and this app is shown as running, touch it to highlight it. Then click the Zzzz button or the three dot menu, then 'hibernate now'. You should get a dialogue box containing some warnings and also a checkbox within it. Tick the checkbox, then click OK. That is all.
tnsmani said:
Xposed doesn't have anything to do with this option. I hope you are running it in root or boost mode.
You may not get this option on the App Analyzer screen. When you are on the main screen of Greenify and this app is shown as running, touch it to highlight it. Then click the Zzzz button or the three dot menu, then 'hibernate now'. You should get a dialogue box containing some warnings and also a checkbox within it. Tick the checkbox, then click OK. That is all.
Click to expand...
Click to collapse
Thanks, this is definitely something I have done in the past on a Samsung device. However, after I had migrated to Nexus 5x I lost this option. I just try to replicate the steps yet once again I don't get any prompt for app state. Sigh.
FYI, yes I am on root mode.
chinesecooler said:
Thanks, this is definitely something I have done in the past on a Samsung device. However, after I had migrated to Nexus 5x I lost this option. I just try to replicate the steps yet once again I don't get any prompt for app state. Sigh.
FYI, yes I am on root mode.
Click to expand...
Click to collapse
This option is not available for all apps. It is only available for certain apps, may be only those that are persistent.
Why don't you try this on another app and see whether you get the option? By the way, which app is giving you this issue?
tnsmani said:
This option is not available for all apps. It is only available for certain apps, may be only those that are persistent.
Why don't you try this on another app and see whether you get the option? By the way, which app is giving you this issue?
Click to expand...
Click to collapse
It's an app named Alipay which is something like PayPal. What is the app that works for you? I might download it and see if I can trigger the option?
chinesecooler said:
It's an app named Alipay which is something like PayPal. What is the app that works for you? I might download it and see if I can trigger the option?
Click to expand...
Click to collapse
With NFC Service and UC Browser, I am able to use that option. I have not used it on other apps that I use.
tnsmani said:
With NFC Service and UC Browser, I am able to use that option. I have not used it on other apps that I use.
Click to expand...
Click to collapse
Thanks mate, I will install uc browse and give that a go.
l'm getting delayed or messed up push notifications in lnstagram. It shows 'x' person liked your picture white it's 'y' in actual and most of the time get no notifications at all. It started to happen from past 3 days. l'm using NitrogenOS but it's probably not ROM related issue. I even tried full system wipe but the issue still remains. Anyone here knows what's going on?
Well that happened to me today....i got a notification from Instagram app 47 minutes later; seconds after unlocking the device. I think in my case it might have been caused due to doze, not sure about yours though. I am running latest build of RR btw.
Itsrp53 said:
Well that happened to me today....i got a notification from Instagram app 47 minutes later; seconds after unlocking the device. I think in my case it might have been caused due to doze, not sure about yours though. I am running latest build of RR btw.
Click to expand...
Click to collapse
Don't know what's causing it. I haven't enabled doze. I'm on latest LOS.
PPStar said:
l'm getting delayed or messed up push notifications in lnstagram. It shows 'x' person liked your picture white it's 'y' in actual and most of the time get no notifications at all. It started to happen from past 3 days. l'm using NitrogenOS but it's probably not ROM related issue. I even tried full system wipe but the issue still remains. Anyone here knows what's going on?
Click to expand...
Click to collapse
Have u changed any settings for apps in privacy manager.. If yes please reset apps preferences and then check.. I mistakenly had denied background start, start on boot of whatsapp and was in similar situation as in U are.
Regards.
herecomesmaggi said:
Have u changed any settings for apps in privacy manager.. If yes please reset apps preferences and then check.. I mistakenly had denied background start, start on boot of whatsapp and was in similar situation as in U are.
Regards.
Click to expand...
Click to collapse
No, I haven't tampered with any apps preference till now. I'll flash LOS and see if the issue remains.
EDIT:- I just flashed LOS and the issue still remains. I tried another account and it has the same issue... No idea what's going on here ??
PPStar said:
No, I haven't tampered with any apps preference till now. I'll flash LOS and see if the issue remains.
EDIT:- I just flashed LOS and the issue still remains. I tried another account and it has the same issue... No idea what's going on here ??
Click to expand...
Click to collapse
Do you use other platform, pc / Mac for same telegram account. ??
herecomesmaggi said:
Do you use other platform, pc / Mac for same telegram account. ??
Click to expand...
Click to collapse
You mean Instagram. Right? And yes, I've linked my Facebook account with my Instagram. Does it have anything to do with it?
PPStar said:
You mean Instagram. Right? And yes, I've linked my Facebook account with my Instagram. Does it have anything to do with it?
Click to expand...
Click to collapse
For a brief period remove Facebook connection and then check. Also there is app called push notification fixer, run that once hopefully it fixes the problem.
Holy **** I thought u were asking for telegram app.. Sorry bro. Let me recheck that. But steps are worthwhile, try above steps.
Regards..
PPStar said:
Don't know what's causing it. I haven't enabled doze. I'm on latest LOS.
Click to expand...
Click to collapse
You do not manually enable doze, it is already enabled by default.
Here is brief introduction to doze which you should read: https://www.thurrott.com/mobile/android/77553/android-7-0-nougat-tip-manage-battery-life
And try doing what that article says at end:
"Settings" -> "Battery" -> "Battery optimization" -> "All apps" -> "Instagram" -> "Don't optimize" -> "Done".
herecomesmaggi said:
For a brief period remove Facebook connection and then check. Also there is app called push notification fixer, run that once hopefully it fixes the problem.
Holy **** I thought u were asking for telegram app.. Sorry bro. Let me recheck that. But steps are worthwhile, try above steps.
Regards..
Click to expand...
Click to collapse
I unlinked my Instagram account with Facebook but the problem still remains. Thanks for the suggestion though..
uoiea0 said:
You do not manually enable doze, it is already enabled by default.
Here is brief introduction to doze which you should read: https://www.thurrott.com/mobile/android/77553/android-7-0-nougat-tip-manage-battery-life
And try doing what that article says at end:
"Settings" -> "Battery" -> "Battery optimization" -> "All apps" -> "Instagram" -> "Don't optimize" -> "Done".
Click to expand...
Click to collapse
Thanx for the info but I'm afraid my issue still remains the same even after selecting 'don't optimize' for Instagram.
Did you ever solve this? I'm getting the same issue on a Pixel 2 running Android P.
The following maybe the cases resulting tot his issue:
1. You have turned off permissions for the app to run in background
2. You have some kind of battery saver settings enabled
3. You may turned on the data saver of your mobile data
4. You could have limited the number of background process running in Developer Options
5. Maybe something related to lock screen settings?
Still got this issue. I've been using Instagram on cm11 since 2021. suddenly in October/November this delay started. Everything was fine before. Then I clean flashed that rom but this bug was still there. Then I shifted to RR M but it was still there. Now I'm using RR LP and it's still here. Tried messing with the heartbeat intervals. Used Push Notification fixer. Messed with my router. Nothing helps. This problem remains in the instagram lite app too. Push notifications of other apps are working fine. This is killing me