I have a question about using Llama on Marshmallow. I wrote a basic script that enables airplane mode every 10 minutes and queues another task called disable airplane mode that has a delayed start of 9 minutes. So basically every 10 minutes my device turns off airplane mode for a minute then turns it back on. I left the script running over night, with my phone plugged in and it worked perfect. When I run the script without the phone plugged in, it only works for about 60 to 90 minutes. Sometimes it says conditions no longer true so repeating event canceled and sometimes I see nothing indicating why the repeating event stopped. My initial thought is that when plugged in, Marshmallow does not use Doze. Could Doze be causing a problem and preventing the task from running? I have whitelisted Llama along with 30 or 40 other apps and I am continuing testing. If you have any thoughts, I would greatly appreciate it!
Llama on Marshmallow
Not sure if anyone else is still trying to use llama on Marshmallow, but I found a work around. Polling wouldn't work at all for me so I started using WiFi connections and deleting out the entering / exiting location conditions. Wifi is everywhere now a days. This seems to work well unless you were trying to turn your WiFi off and on based on location. I'd tried e-robot for the same thing and it worked sometimes but not others. Couldn't figure what was going wrong there. Llama is still way easier to set up and more reliable than the alternatives I've tried.
Related
I've been using the app BetterBatteryStats as recommended by XDA to determine why my RAZR is awake much of the time, even when the screen is off and data is turned off. It turns out the problem is the internal process IMS_Data_Retry. This process apparently keeps attempting to establish a data connection over cellular data, at least 4G LTE. It aquires a wake lock while doing its work. This one process can keep the phone awake 95% of the time. The only way I have found to semi-stop it is to turn on 4G LTE. Even then, while it stops consuming CPU time (supposedly), the count of retry attempts keeps going up. (Putting the phone in Airplane mode also stops it, but then calls are stopped as well.)
There is a setting in /system/build.prop that I thought controlled this process:
ro.cdma.data_retry_config=default_randomization=2000,max_retries=infinite, 0, 0, 120000, 180000, 540000, 960000
I looked at some code references I found ( http://hi-android.info/src/com/android/internal/telephony/cdma/CdmaDataConnectionTracker.java.html ) and learned that the above values are in milliseconds. It seems that the default_randomization value is added to the other values in the list to create a schedule of retry attempts, but I wasn't able to figure out all the parameters to the method, if I even have the right one. I tried changing "infinite" to a small number under 10, but it had no effect - the process just keeps retrying forever.
Is there a dev out there who knows more about this? I want to limit this process because I seldom use cellular data right now and am usually on WiFi. It hinders any attempt to extend battery life. Is it a bug? Is it fixed in a later release (I'm on .748 stock) ? Do any of the custom ROMs have this problem? Can the build.prop setting I found be given values that limit the amount of time this process holds wake locks?
Thanks.
Did you ever get any resolution on this? For me, I think the problem started with the ICS update this summer. I constantly have gsm_data_tracker, RILJ, and IMS_Data_Retry using up the battery (in that order from highest to lowest). I tried wiping cache which helped the 1st time it cropped up and then it came back. I also tried a tip I saw somewhere for turning on airplane mode, rebooting, and turning off airplane mode (though mine as soon as it reboots, it already turns off airplane mode which it shouldn't). That worked for several weeks, but I had to do it EVERY DAY when I got to work. I think it's something with the 3g repeaters in the building. I did have it so it was wifi only (mobile radio off) on my work profile in profile scheduler, but then I needed cell for some mms stuff, so I ended up enabling it again. Basically when I come in the building and forget about my phone for an hour or 2, I go to get it out of my backpack and it will be hot from processing and 20% or more of the battery gone when I've done nothing in 2 hours of being at work. I saw somewhere that someone though either gsm_data_tracker or RILJ was related to something with the alarm, which I do use my phone as my alarm, but I use a 3rd party app. With the time change, there were a few days I woke up before it ever went off, so I turned it off before it did alarm. There were no differences with the partial wakelocks or battery drain in those cases. Unfortunately, I don't have another alarm readily available to get up for work right now and on the weekends when I don't need an alarm, I can't replicate the cell repeater at work issues, since I wouldn't be around the cell repeaters. As fart as in the building at work, until I reboot with airplane mode and all of that, the cell signal will bounce between like 0 bars/3g and lots of bars (no indication of network) and some bars with 1x network. It's all over the place. The airplane mode/reboot used to stabilize that, but it doesn't seem to be doing the trick anymore the last few days that I've tried that. I have to leave my phone on the charger as much as possible at work so that I don't leave for the day with a dead phone.
Hey guys,
On my second samsung device and my fifth rom (including eclipse TW, eclipse AOSP, aokp, CM10, now hyperdrive). Have to say thay I'm satisfied with pretty much everything Hyperdrive has to offer, its freaking amazing! One issue doesn't seem to be resolving despite many attempts. My phone stays awake nearly 100% of the time with a wlan_wake wakelock. This isnt the well documented wlan_rx_wake wakelock, which I've also had in the past but managed to squash. I'll recount my findings in some order below.
I installed Hyperdrive, restored some some vital apps. Waited a couple days and found the battery wasn't what I'd hoped it'd be. I usually run with auto sync enabled for total 8 mins per hour (via Tasker) and wifi and mobile data on. I've also used a script that disables IPv6 whenever it connects to a wifi network -- work network has tons of IPv6 broadcasts that were triggering massive wlan_rx_wake wakelocks which were vastly reduced with this fix. Even with these throttles, I noticed that some time after boot (10-15 minutes) on my work as well as home network (10 mixed devices on a belkin router), a wlan_wake wakelock would start triggering and my phone would then stay awake 90-100% of the time, screen on or off.
I went ahead factory reset the phone, loaded just my google account, and found the same problem with autosync on, autosync off, GPS was off, Wifi "always allow scanning" option was disabled in the advanced menu, Google's Wifi network location was disabled, and no 3rd party apps except for BBS installed. Of course, with Wifi disabled, the issue abated but 3g/4g doesn't offer much better battery life than the phone staying awake the whole time. During this time, I used Network Logger and Shark for Root to attempt to identify Wifi traffic and found that a few apps were transmitting frequently, but not enough to keep the phone awake for the amount of time the wakelock indicated. Total battery drain is up to 8-10%/hour with absolutely minimal use. I've never had this particular issue with any other OS i've installed, any ideas what could be going on? Really looking forward to being able to rip through days without charging on Hyperdrive!
I have a Samsung Note 3 and I too have this same problem (except that a factory reset solves it). Can't seem to find a fix. People on internet suggest that it's because of some rogue app but my phone starts behaving like this randomly until I do a factory reset.
Hi all,
I have an AT&T Samsung Note 3 SM-N900A running Android 4.3 (baseband version N900AUCUBMJ5, kernel v3.4.0-1625098). I rooted it using Kingo, installed Tasker (with Secure Settings plugin), and created 2 profiles: one with a 'Home' location context, and one with a 'Work' location context. In the 'Location Edit' map screen for each, I set a pinned location w/ a radius of 200m. I also de-select 'GPS' (leaving only 'NET'), since I don't want GPS enabled all the time (to extend battery life). I confirm that these work when I'm actively using the phone.. the profile becomes active when I'm at the specified location (as expected). I know it's active because it's displayed in the Notification Panel (and it's also shown in green in the Tasker profiles list).
The issue I'm having is that after ~10 minutes of idle time (i.e. when the display is off and I'm not using the phone), I find that the profile is no longer active when I turn the display back on and start using the phone again. I confirmed that this *doesn't* happen after 1 minute, 2 minutes, nor 5 minutes… only > 10. I also confirmed that it happens for both profiles consistently. However, as soon as I start Tasker again from the Apps Drawer (or from Recent Apps screen), the profile is immediately activated again, and my Enter task is re-run.
I enabled the run log in Tasker prefs, but it basically shows a clean activation of the profile (with no warnings or anything that looks weird to me).
I know there's a 10-minute timeout in the Display Off Monitoring prefs, but that doesn't seem to be related to my issue. I tried reducing the All Checks Seconds from 600 to 90, rebooted the phone, and it still took ~10 minutes before the profile would become inactive after the phone being idle.
Any thoughts as to what the culprit might be? Are there any system logs I can look at that might shed some light here? I'm new to Android, and this seemed like the place to ask..
Thanks.
Ok, not solved..
Alright, bumping this, as the problem is back again after some time.
Has anyone ever seen Tasker exhibit the behavior I described? Again, I start the phone and Tasker profile is active, let the phone go idle for >10 minutes, the profile is no longer active and I need to restart Tasker manually to make it active again.
Still trying to figure out what logs are best to look at..
Is it possible to set up Tasker (maybe with this plugin: https://play.google.com/store/apps/details?id=com.intangibleobject.securesettings.plugin ) or another automation app (eg Macrodroid) so that it wakes up the phone every x minutes, say, every hour, in order to cause the phone from exiting Marshmallow's Doze mode?
Doze is causing lots of problems with lots of apps because it breaks most push notifications; unless you're rooted, you cannot disable it, and disabling battery optimisation for a given app doesn't do much. I cannot root my phone otherwise the app to connect to my work email won't work.
I was wondering if it is possible to set some automated task that indirectly causes to phone to exit the doze mode, e.g. turning the screen on for 10 seconds every 60 minutes, or launching a specific app, or else.
Has anyone tried it?
Also, I haven't found a way to monitor when the phone is in Doze, nor have I found any official documentation on what triggers Doze (phone stationary, but for how long?).
Thanks
No one knows?
Anyway, this partial solution works for me: http://androidforums.com/threads/ma...x-is-preventing-doze-with-macrodroid.1058445/
It's about using MacroDroid to wake up the phone every 45 minutes, thus prveenting Doze mode from kicking in at all. Battery usage is acceptable (1% /hour with two push emails on).
I don't know if MacroDroid or Tasker can be set up to cause the phone to exit Doze mode, but this solution, however partial or indirect, is better for me as having push email on is a priority to me.
For some reason my watch constantly disconnects from my phone (a One plus 2)
The Android wear app says trying to connect, but the only way is to reboot the phone. It connects again, but then will disconnect later, I'm assuming when the phone goes into deep sleep?
The android wear app has been set to "not optimised" in the phone settings.
Is there anything else to check?
I've removed Greenify and Power Nap to see if that helps, but it's the same.
Phone is running latest Marshmallow from and watch is all up to date
Sent from my oneplus2 using Tapatalk
Are you using OxygenOS? I'm on CM13 and having same disconnects with my Oneplus2 - watch get disconnected 1-2 times per day.
Thought toggling Bluetooth Off/On resolves the issue for me, but temporary.
Is there a way to have constant connection between phone and watch?
Since changing my OS to paranoid android on my phone and removing things like, Power Nap and Amplify, I have had no more disconnect from the watch.
Not sure what services were being stopped to extend battery life
Sent from my ONE A2003 using Tapatalk
Still the same for me, I search and search, but don't find anything
Sometime a sync works for 1day, next day it's disconnected,
If I try to sync it again it takes ~1 to pair, and I dont see my apps, just default apps.
After press multiple times in WearApp to sync all apps I see it again.
Next hour or next day it's again disconnected.
I see the PlayService version on my watch is a older like my version on my phone (Note4)
Any ideas ?