How to tame weather widget applications with many wakelocks? - Greenify

In order to prevent leaks during screen sleep want to run Amplify together with Greenify
What about such alarm (reported by Amplify):
Full Name:
com.Elecont.WeatherClock/.WakeUpReceiver
Elecont eWeather is an application which has many alarms count after every night despite setting it to update just when screen on (and the alarm checks very frequently when screen already comes ON so its crazy). It has time indication on its widgets in very graphical fashion so it takes care to show it accurately and that's why it constantly checks if screen is awaken.
It seems just Xposed module like Greenify can take care of such cases: hibernate when screen OFF and unhibernate when screen comes ON, however it doesn't hibernate the eWeather - why?
Probably because eWeather has two major components: widgets associated background service
and
GUI main interface,
and Greenify can see just GUI part and just this keeps hibernated.
How to make Greenify hibernate both components of eWeather, especially its service? Add list of Greenify shows just one entry eWeather and after choosing it the service component still runs unrestricted during phone sleep.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel

ivy.lally said:
In order to prevent leaks during screen sleep want to run Amplify together with Greenify
What about such alarm (reported by Amplify):
Full Name:
com.Elecont.WeatherClock/.WakeUpReceiver
Elecont eWeather is an application which has many alarms count after every night despite setting it to update just when screen on (and the alarm checks very frequently when screen already comes ON so its crazy). It has time indication on its widgets in very graphical fashion so it takes care to show it accurately and that's why it constantly checks if screen is awaken.
It seems just Xposed module like Greenify can take care of such cases: hibernate when screen OFF and unhibernate when screen comes ON, however it doesn't hibernate the eWeather - why?
Probably because eWeather has two major components: widgets associated background service
and
GUI main interface,
and Greenify can see just GUI part and just this keeps hibernated.
How to make Greenify hibernate both components of eWeather, especially its service? Add list of Greenify shows just one entry eWeather and after choosing it the service component still runs unrestricted during phone sleep.
Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
Click to expand...
Click to collapse
FYI - related conversation here. While a single post is linked best to roll back a few pages to see the full context.

However as you can see other means seem to fail I'd like to return to Greenify. And at once have the big question. Please, see this screen:
and tell me how to enforce of hibernating these applications when the screen sets OFF (and to unhibernate just after screen comes ON): 3CToolBox, Ampere and CoolTool?
Important much to put these applications into hibernation with screen OFF as they have many wakelocks and are reported as power intensive!
Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel

Related

[APP] App Timer Pro [Updated: 7/12/12]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
This app is a also available on the Play store. but I've decided to release it here for free.
YOU MUST BE ROOTED TO USE THIS APP
This application uses root permission to kill an app and its associated processes. You can easily set a time for an app to be killed with the option of audio fade out (ex. listening to music while falling asleep: you can set the time from now or a specific time for the music app to be killed. Optional feature to fade the volume out before the app gets killed). App also contains a threshold killing option (set the lowest amount of RAM in megabytes before process are killed), recurring killing (kill processes at set intervals), customized kill level (by importance), option to kill all but excluded or simply kill the ones you've selected, all completely customizable and much more.
Features:
Kill any app at a time you choose with optional volume fade out.
Easily view which apps are active.
Monitors available memory.
Kill individual app process.
Uninstall app (send to the package manager).
Launch app.
Threshold monitoring and process killing.
Recurring processes killing.
Selected list (apps and processes to exclude).
Innovative help screens.
Backup and restore options.
Main list shows package name and other info.
Change category to show specific processes/apps.
Kill all option.
Widget that monitors available RAM and button to kill all.
Easy start and stop from the main menu.
Highly customizable settings.
Move to SD card enabled.
Hardware acceleration enabled for Android 3.0+.
Permissions:
Storage (modify/delete SD card contents) : this is used to backup and restore saved settings and lists to your SD card.
System tools (kill background processes) : the app doesn't just kill the app processes, it also kills the background ones (to be on the safe side).
*Note: this application will kill an app and its associated processes however, some apps will restart themselves.
If you feel like donating, please consider buying the paid version available on the play store here: here.
Downloads:
App Timer Pro v1.4 [7/12/12] [Size: 526.02 KB (538647 bytes)]
MD5 Sum: 7330c53892171ddc02113ca0eebb00f2​
Screenshots
*Screenshots were taken from my previous, lower resolution phone (Evo Shift).
That's man going to give this a try
Sent from my EVO using xda premium
Very nice :good:
Great app idea!
Sent from my EVO using Tapatalk 2
Excellent idea, thank you.
Sent from my lair.

Some apps always stay "pending" without any further info

Hello!
Used Greenify version 2.4, donation, with Xposed.
I have 3 apps configured to be greenified: Viber, WhatsApp and PushBullet.
Apps have no permanent status icons.
All of them use GCM. GCM pushes passing is activated in Greenify .
Whole phone sleeps ok. I don't see much wakups in statistics during the time screen is off.
PushBullet is normally hybernating, getting pushes, waking up. Just like it should by Greenify design.
But Viber and WhatsApp are always staying "Pending" even when screen is off for hours. There is no any notifications or warning on it in Greenify interface. Just "Pending"...
How can I further diagnose my problem? Or maybe I am doing something wrong?
Thanks!
UPD:
The only difference between my apps is that in non grinified state Viber and WhatsApp are stated as "Running in background" when PushBullet is usually stated as "May slow the device when... app is updated". Thus PushBullet behaves more gently in general. Ok. But what the heck is that everlasting "Pending"?
And what dark magic is hiding behind statement "will hibernate in a short time after the screen goes off"?
Hmm... No thoughts at all?
I'm just curious: if there is a Hybernate action shortcut and application can catch the screen lock event WHY subj can't activate this Hybernate action just after screen off???
I also have a somewhat similar issue. Though I have not greenified Google Play Services, when it is shown as Pending and when the Greenify+lock shortcut is used, Google Play Services remains pending even after hours. Should it not be greenified when the shortcut is used?
tnsmani said:
I also have a somewhat similar issue. Though I have not greenified Google Play Services, when it is shown as Pending and when the Greenify+lock shortcut is used, Google Play Services remains pending even after hours. Should it not be greenified when the shortcut is used?
Click to expand...
Click to collapse
Mine too. I think google backup transport and android system that keeps google play service running all the time. Even if i manually push It doesnt.
Sent from my GT-S7500 using XDA Free mobile app
You are right. But in my case manual hibernation works for Google Backup Transport. However, once I unlock the screen, it is again running and keeps running for hours till it is manually hibernated. It also eats a lot of battery.
I seem to have found a way out for Google Play Services. When I hibernated it manually yesterday and when it said that the app, if greenified in the present state, might have issues, I ticked the checkbox for ignoring its state and then manually greenified it. Till now though it runs on screen unlock, it gets automatically hibernated after the screen is off. I have not so far faced any other issues because of my action.
Maybe @Kirrrr can try the same on Viber if this option is available.
 @naik2902 can definitely try it on GPS.
However, I am not responsible for any consequences.:fingers-crossed:
It looks quite wrong and strange. Isn't it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, it is strange. May be the apps like Whatsap, Facebook and Viber use other methods for staying awake!

Weird case of Google Services battery drain (only on mobile data, among other things)

I know this is probably the most addressed issue in any Android forum, but I swear I've tried it all and nothing seems to work.
First of all, the drain only happens when on mobile data, I never see it when on WIFI, even on extremely crappy connections like the one I have at work (no exageration here, it's almost dial-up), where you'd think that the device is being kept awake because it takes longer to sync. I've been having this issue for over a week now. Here are some of the things I've tried and noticed.
- I have disabled syncronization from every Google Service (contacts, Gmail, Apps, Fit... everything) and autosync in general is disabled.
- Through Privacy Guard in CM12.1, I denied EVERY permission to Google Services
- Inspite of having denied these permissions, including location, and location being disabled completely, Google Services is still asking constantly for location, as you can see in the screenshots. It has requested location 775 times and woken up the device 669 times (this happened in 24 hours, the stats reset yesterday night when I made factory reset). That can't be normal, right? If i set the permissions to awlays ask, I see not one, but 4 or 5 requests in a row at virtually every screen on or every couple of minutes if the screen is kept on, regardless of if I denied or grant them. Why is it even asking for location when location is off!?
- I've denied permissions to Contacts Sync only because the icon in the battery stats frequently changed to the contacts icon
- The drain may not be massive but it's definitely considerable, it varies between 1.5% and 8% per hour when idle. At least the first hour idle.
- I occasionally see some wakelocks when on mobile data (RILJ is the most noticeable, but sometimes sync related and *alarm* wakelocks are there too) but the drain is there regardless of if the phones sleeps +90% of the time, as it usually does (according to wakelock detector and Better Battery stats anyway), which is very strange to me
- If I leave the phone untouched for several hours, the drain can go down to less than 1%, but it takes at least an hour for the device to get to that point, waking up in the middle to use 5% per hour for several minutes (no considerable wakelocks). Very inconsistent.
These screenshots show the device on wifi using 0.58%. After turning it off it started using 1.47% and then almost 4%/H (it's usually much higher with sync enabled and permissions granted).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These show the request count of Google Services (note location (ubicación) and wake up (despertar)). EVERY SINGLE permission is denied (ignorado) but it still drains the battery!
Has anyone seen anything like this? This started happening when I got the 5.1 OTA. I changed carriers around the same time and the mobile data signal at home isn't very good, but it happens everywhere, even on areas with great LTE or 3G coverage. I'm not completely sure of this, but I think forcing 2G helps.
I'd be immensely aprreciated if someone can give me hint on what the hell is going on here, buecause I just don't get it. Non of the usual approaches work.
Thanks
______
Nexus 5 running CM 12.1 (happened on stock 5.1 and after downgrading to 5.0.1 as well)
Google Services version 7.3.29

[Workaround] Bring S-View back (xposed, dashclock)

First of all, video:
https://www.youtube.com/watch?v=9axQHQ8ZXLU
Solution is not from android programmer, rather geek
Hi there... so, i was pretty dissapointed with lack of S-View functionality on CM13, S4 Mini. It was great feature, that was doing really good job with magnetic cover.
If you tried to do something with it, you probably experienced some problems with magnetic sensor (or you were smarter than me). It prevented to turn on screen with power button on any custom lockscreen from market, that was better than cm's stock one. In terms of 'better' i have in mind a lockscreen... that has f*** clock in right spot for case's window I was trying to bring it back with various results, but finally i achieved (i think) the best possible solution, turning lockscreen into S-View screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What it does right: showing time and basic info about battery, calls, msgs, next alarm, notifications (from gmail, fb messeger - that part is actually very customizable).
What it doesn't do at all: doesn't let you pick up calls, turn off your alarm via window and do any stuff that requiers touching via window. Magnetic sensor basicaly turns off that feature when case is closed. Showing info about playing track is not worth activating (because of space).
So, we need xposed installed and then download module: http://repo.xposed.info/module/com.ssrdroide.lockscreenwidgets
And the widget we are gonna use is dashclock: https://play.google.com/store/apps/details?id=net.nurik.roman.dashclock (or you can use more advanced alternative: https://play.google.com/store/apps/details?id=com.kk.widget)
Step 1. First thing you wanna do is to configure widget the way you want - download some extensions for it (like battery info). I highly recommend to use DashNotifer to get notifications from custom apps like fb messenger (https://play.google.com/store/apps/details?id=com.umang.dashnotifier It's already there in KK Widgets). Test it on your homescreen for now and find configuration that suits you.
Step 2. will be add widget to lockscreen via xposed module. This configuration (http://i.imgur.com/iiJMK7w.png) will keep your widget in case's window, when owner info will be out of it on same time. There is also something to mention - if you will not turn off notifications on lockscreen they will move your widget little higher (depending on number of notifications).
So... 1. If you wanna keep your notifications on lockscreen, set container 'y' translation to something around -150. Widget will stay in window regardless number of notifications.
2. If you wanna remove notifications for that cause, set container 'y' translation to -175. Widget will be in perfect spot for the whole time.
That works for standard DPI.
And that's it. It works perfectly with magnetic sensor.
For better effect you can change your wallpaper to black (worth it). That's however will change when you will listen to music, you can turn this option off or use this xposed module to paint it black for good: http://repo.xposed.info/module/com.generalbrus.brightlockscreen
Another thing is alarm. It happens that Timely has clock in perfect spot when activated and can be controlled with physical buttons
I'm super happy with result. It's not exactly what you could achieve with real S-View, but it does good job
If you have better solutions share it in thread!

Question Apps being aggressively closed following June update!

Hi folks,
I'm wondering if anyone has a solution to this: Immediately following applying the June update, I noticed certain apps (crucially, Angry Birds2) were being closed in the background as soon as I switch to other apps. Previously, I could have AB2 open, go do other things on the phone, come back half an hour, and AB2 would still be open. Now, even brief switches to other apps results in it being closed.
Figuring it had been switched to a higher level of battery optimization, I checked the AB2 app and made sure it was still Unrestricted (it is).
Battery Saver is off.
Adaptive Battery is on, but it was before the update too.
What other settings do I need to monkey with to fix this?
Thanks in advance!
Developer options>standby apps, check bucket state of app. It should be active.
If that's the case disable all global power management. If disabled all buckets show as active and their state can't be altered.
Google global power management never worked right. Turn all that junk off.
Deal with power hogs on a case by case basis instead. In settings individual apps can be set to not run in background without invoking global power management.
blackhawk said:
Developer options>standby apps, check bucket state of app. It should be active.
If that's the case disable all global power management. If disabled all buckets show as active and their state can't be altered.
Google global power management never worked right. Turn all that junk off.
Deal with power hogs on a case by case basis instead. In settings individual apps can be set to not run in background without invoking global power management.
Click to expand...
Click to collapse
For AB2 it shows "exempted" and is grayed out. What does that mean? Meanwhile I'm turning off Adaptive power. Anything else I need to turn off, while I'm at it?
Frankenscript said:
For AB2 it shows "exempted" and is grayed out. What does that mean? Meanwhile I'm turning off Adaptive power. Anything else I need to turn off, while I'm at it?
Click to expand...
Click to collapse
Exempted? More like KIA Erratic behavior is typically what it causes on my Samsung's.
In power management the only thing I enable would be fast charging if you want that.
Not familiar with Pixel settings but they are similar as it's a Google Android based subsystem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sadly all similar settings are now turned off and the phone has been rebooted. AB2 still closes nearly instantly when I switch to another app. Sigh.
Frankenscript said:
Sadly all similar settings are now turned off and the phone has been rebooted. AB2 still closes nearly instantly when I switch to another app. Sigh.
Click to expand...
Click to collapse
Try clearing app cache.
More drastically delete data or reinstall it.
It may be the app itself is no longer compatible now and needs an update.
On a Samsung my first choice would be to clear the system cache found on the boot menu. I've been told Pixel's don't have this option.
Personally I avoid all OTA updates as they can and do break things. Pie and above are fairly secure if you don't do stupid things.

Categories

Resources