Related
Hi,
I'm just letting everyone know that I have just pushed an update to my automation app MacroDroid http://forum.xda-developers.com/showthread.php?t=1694335 to add Android Wear support.
You can read about the functionality on my blog post here: http://macro-droid.blogspot.co.uk/2014/08/introducing-macrodroid-wear.html
This is a first release, so I strongly welcome all feedback and comments!
Cheers,
Jamie
Very impressive app ?, seriously quality app.
I need more time to test out all the different stuff in your app but so far everything works great whit my lg watch .
This is using 60mb of memory for the macrodroid process alone. Seems very high.
This is on a Moto G. Compared to Tasker which is running at the same time and only uses 12mb.
I have deleted all macrodroid profiles so it shouldn't have had anything running, but the memory use was still high.
Cossack101 said:
This is using 60mb of memory for the macrodroid process alone. Seems very high.
This is on a Moto G. Compared to Tasker which is running at the same time and only uses 12mb.
I have deleted all macrodroid profiles so it shouldn't have had anything running, but the memory use was still high.
Click to expand...
Click to collapse
You're right that does sound very high, I've got a bunch of macros configured and I'm at 19MB. Most likely you've hit a memory leak in the UI and the UI pages are still hanging around in memory. It can be hard to catch all cases as there are many many UI paths, but I'll certainly do some more memory profiling to see if I can spot anything naughty hanging around. If you kill the MacroDroid process and restart does the memory return to something sane for you?
Cheers,
Jamie
I killed the app and wiped the macros. Started again with only 1 simple low battery warning macro. It stayed at 15mb all day.
I just created a new location macro and it jumped to 38mb and stayed there.
I switched macrodroid off and restarted and it is now back to 17mb.
Cossack101 said:
I killed the app and wiped the macros. Started again with only 1 simple low battery warning macro. It stayed at 15mb all day.
I just created a new location macro and it jumped to 38mb and stayed there.
I switched macrodroid off and restarted and it is now back to 17mb.
Click to expand...
Click to collapse
Great thanks for the info. I've just had to move to Google Maps V2 and changed a load of UI, so I'm guessing I've got a little bug in there where I'm not releasing something. Hopefully I can get this squashed for the next update.
Cheers,
Jamie
I am trying to automate the screen intensity.
The worst thing about my Gear Live is battery live, if I am inside love to find a way to always have the screen minimum and the best I could do is have a manual macro to change the screen intensity.
I wonder if I can design a macro that every time the watch gets a notification the screen goes to 5, when it dims it goes back to 1.
Why not set the brightness to low when connected to WiFi and high when disconnected.
It should mean you always have a dim watch when indoors
AstroDigital said:
I am trying to automate the screen intensity.
The worst thing about my Gear Live is battery live, if I am inside love to find a way to always have the screen minimum and the best I could do is have a manual macro to change the screen intensity.
I wonder if I can design a macro that every time the watch gets a notification the screen goes to 5, when it dims it goes back to 1.
Click to expand...
Click to collapse
You could do something like on every incoming notification (using the incoming notification trigger), you set the brightness high and have a sleep before next (e.g 30 seconds) and set the brightness low again. Not perfect but might be of some use.
What I really wanted to do was find a way so that I could configure the Always on screen setting via the action, but after digging down into the code I'm pretty certain this would only be possible on a rooted Android Wear device and I don't really want to go adding 'root only' features for Wear just yet. Hopefully Google will open up this API at some point because as you point out battery life is critical on these devices.
Cossack101 said:
Why not set the brightness to low when connected to WiFi and high when disconnected.
It should mean you always have a dim watch when indoors
Click to expand...
Click to collapse
I do not use WiFi on my cell phone, just LTE data at least 95% of the time.
---------- Post added at 05:02 PM ---------- Previous post was at 04:39 PM ----------
UndeadCretin said:
You could do something like on every incoming notification (using the incoming notification trigger), you set the brightness high and have a sleep before next (e.g 30 seconds) and set the brightness low again. Not perfect but might be of some use.
What I really wanted to do was find a way so that I could configure the Always on screen setting via the action, but after digging down into the code I'm pretty certain this would only be possible on a rooted Android Wear device and I don't really want to go adding 'root only' features for Wear just yet. Hopefully Google will open up this API at some point because as you point out battery life is critical on these devices.
Click to expand...
Click to collapse
If I set the app to listen for notifications it looks like it will disable much more than I would like to be disabled.
Manage Accessibliity, MacroDroid
-air gesture, air view interaction control, assistant menu, multi window, direct pen input, palm motion, one-handed operation will all be turned off....
I always lost "Jess" my customer voice synthesizer
Some of these I will miss on my Note 3 but I am trying it,
Toggle on Notification
Android Wear set the brightness to 6
Sleep before next action 20 seconds
Android Wear set the brightness to 1
If it works right notifications will crank the display for 20 seconds and then dim the display (may cut it back to 10 or 5 seconds)
You know I like your app, tried the other macro app .... (can not remember its name)
Found it too complicated..... Thanks for the tip.
AstroDigital said:
I do not use WiFi on my cell phone, just LTE data at least 95% of the time.
---------- Post added at 05:02 PM ---------- Previous post was at 04:39 PM ----------
If I set the app to listen for notifications it looks like it will disable much more than I would like to be disabled.
Manage Accessibliity, MacroDroid
-air gesture, air view interaction control, assistant menu, multi window, direct pen input, palm motion, one-handed operation will all be turned off....
I always lost "Jess" my customer voice synthesizer
Some of these I will miss on my Note 3 but I am trying it,
Toggle on Notification
Android Wear set the brightness to 6
Sleep before next action 20 seconds
Android Wear set the brightness to 1
If it works right notifications will crank the display for 20 seconds and then dim the display (may cut it back to 10 or 5 seconds)
You know I like your app, tried the other macro app .... (can not remember its name)
Found it too complicated..... Thanks for the tip.
Click to expand...
Click to collapse
I've no idea why these should be turned off by enabling MacroDroids accessibility options, but I don't have any Samsung devices so I'm afraid I can't really look into it at the moment.
UndeadCretin said:
I've no idea why these should be turned off by enabling MacroDroids accessibility options, but I don't have any Samsung devices so I'm afraid I can't really look into it at the moment.
Click to expand...
Click to collapse
If the macro works may not care much about the disabled stuff.
May want to put constraint in, 5am do not need the watch display cranked.
Hi guys!
I would like to start a small project. The whole point is to find out in which circumstances battery is running down faster/slower. It's more less about consumption and I hope we all will benefit from that simply by knowing what to avoid and if some features of Gear S are really draining battery or if it's just a myth.
I'm really looking forward to update this project in time.
Because of the nature of this project. I would love to get some help. Even if one person wants to participate I'll be thrilled.
Each test takes quite a lot of time so we can get more results if we will work together. I choose to run tests for 10 hours as it will give us more accurate results than anything shorter. 10 hours seems to be right as smartwatch still can be used during the day and whats more important, battery can be run down before recharging and testing.
Watch always on (6th watchface) Wifi/Network/BT(unpaired) off - 10h: 22%
Watch always on (6th watchface) Wifi/Network/ off - 10h: 23%
Watch always on (1st watchface) Wifi/Network/ off - 10h: 23%
Watch always on (Watcher) Wifi/Network/ off - 10h: 25%
Watch off (6th watchface) Wifi/Network/BT off -10h: 9% Comment: I was expecting less usage. BT in GearS was still ON as it can't be turned off (but not connected)
Connected via Bluetooth (Watch/Motion/WiFi off): 10h 11% Comment: Apparently when it's paired with phone (sync) does not make much of the different
Connected via GSM without data (Watch/Motion/WiFi off): 10h 18%
Connected via GSM with data (Watch/Motion/WiFi off): 10h 20%
Connected via UMTS with data (Watch/Motion/WiFi off) - 10h: 20%
Talk time on UMTS with data (Watch ON, Motion off, WiFi off) - 2h21m Screen was lighted up few times just to have a look what's going on
[By saying BT off means that do not keep it connected to your phone]
[While connected to Bluetooth or via cellular network make sure to deactivate all notifications in GearManager App - test will be useless if any notification will be delivered to the smartwatch]
To do a test just after a day of use charge your Gear S fully. After reaching 100% still wait approx 20-30min, choose what test you want to participate, disconnect from a charging cradle, switch the screen off and set an alarm to check it back after 10h
Observations:
Having a "Clock Always On" is not that bad idea. During 10h test it consumed 13% more than without it (6th watchface). So we can assume that during all day (approx 16h) we're loosing only 19-20% of juice. Is it bad? I don't think so... especially because you don't need to light up the whole screen just to check what the time is - which will consume some energy too... In the end of the day it still depends of that how often you need to check the time. If you are doing that very often, than "Clock Always On" is... lets say... more energy efficient solution (and looks much better than dark screen).
The only problem with "Clock Always On" is that, almost every touch, raindrop, wet sleeve triggers screen to turn on and it's very inconvenient for the battery life and it can messing around in the interface - it happened to me when i was walking in the rain.
In my opinion touchscreen should be inactive during that mode or even to give such an option to tick in the settings menu.
Thread to that issue http://forum.xda-developers.com/gear-s/help/how-to-stop-accidental-cuff-calling-t2991565#post58596115
What is your brightness setting when your clock is on? If it's set to "auto," then is this being done in a dark room or a bright room?
Seems like losing 20% of battery life after 10 hrs of clock mode on is reasonable at average to high brightness. I wouldn't mind a "clock always on" mode where the brightness is set to min and then the display brightens up when I either touch the display or wake button.
I currently use my Gear S with the "wake motion on" and I'm ending a day of 12-14 hrs of moderate use with 35-50% of battery.
My settings:
Gear S only connected to phone via BT
Wifi off, mobile network off
Set vibration intensity to low (don't see many people talking about this option)
minimal notifications
minimal apps
S voice to wake is off (have to turn off via S Voice settings on Gear S)
Minimal black clock face (batteryclock app)
Screen brightness to auto
I periodically go in to close all recent apps.
I'm always setting brightness to auto but in this case it doesn't really matter.
If you set to max or min ClockAlwaysOn is on with the same level of brightness.
On auto brightness there is no reaction too. Regardless if it is outside in a sunny day or in pitch black basement.
Also during a test just after disconnecting from a charger I'm switching off the screen with a button and after 10h wake it up with a button and straight check battery level. So brightness level won't change much for these 3-5secs
OK so I got my Z4 tablet three days ago. Fantastic construction, fantastic specs on paper.
I had a Z tablet up until last weekend that I sold for a good price and got this as a much needed replacement.
Both are LTE versions.
Anyway, here are some things I've noticed and I would like to have your comments on.
1) The "antitheft" system for the first two days seemed to be a PITA. As my device is set for three users (me, my wife, my son), it kept popping for the others that it locked and needed MY credentials to unlock. I did unlock it at least five times for each, which means I can't really be... far from the device and let them use it. That I use two step authentication, makes things even harder. Once my "authenticator" phone was out of power and I had to wait several minutes to unlock the tablet. Yesterday I updated to latest firmware and I haven't noticed the issue since. But it's just one day, it may come back. Once (before updating firmware) I tried to disable My Xperia (although I love the find my device feature) so they could work, but it kept me "waiting". In the end I pressed back and it didn't get disabled. Any similar experiences with the theft protection?
2) Backlight (set in auto) seems to be too dark some times. I clicked on the intensity bar, set it brighter while STILL in auto (like it is now set to have a brighter "base value"?). Does this sound normal?
3) This is not a Z4 issue, I also had this in Z. It's probably a lollipop thing or I don't understand something properly. Clicking the volume buttons I can set it to "no" sound from home screen. Or so I think. Because even if I set it to "off", apps STILL have sound and I have to RE-adjust the volume to off from within the app (without the "priority buttons" under the volume bar)... Am I the only one to find this stupid?
4) Anybody notices some lag or ESPECIALLY stuck web browser, when other profiles (users) have run apps? If I reset the device and not visit the other profiles, the device is more snappy. If some other user goes in, even quiting every app they run, the device seems to get slower when back in "owner" user. Still fast but not as "snappy". Anybody noticed the same?
5) Any idea when we get Android M? Will we get 5.1 before that? I mean official firmware. Anybody?
6) Is there a way to go to test menu? The tablet Z method doesn't seem to work.
7) Serious. No restricted profiles. Why? Sony support replied that lollipop has this disabled only on 3G/LTE devices (that makes no sense), yet my Z was also LTE and both are on lollipop 5.0.2 and it DID have restricted profiles. What's up with that?
Thank you for your time people, have fun.
...wow
2) Yes.. brightness is usually set a little low at first for battery purposes.
3) There are different volumes for different things. Using the volume rocker on the home screen and putting it all the way down will only adjust ringer/notification volume. In-app sounds will use the media volume which you will need to adjust while media sounds are playing or you can adjust it in your sound settings. Not stupid imo, just gives more flexibility.
5) It'll come when it comes.. nobody knows except google and sony. I'd like to hope we'd get 5.1 before 6.
(pending something on the other questions above)
2) So the set value, when brightness is in "auto" is like a base value?
3) Well I find it stupid. Why: Because when I am in home screen I used to be able to manage the universal audio settings of the device. Turning device to mute, would turn it to mute. As simple as that. Also clicking a simple icon next to volume bar, you could separately adjust notification and ringer and stuff like that. Now? You THINK you set your device to mute, but you have only set the notifications. You sleep in a silent house (next to the wife or something), start a game, it YELLS with the last volume settings, ignoring that you set the device to mute in home screen and you have to "run" and re-adjust the volume to zero, usually with some delay (in the meantime waking everybody) since the device won't let you adjust anything while loading the game. No, I call this stupid.
5) Well if it won't delay 6, I don't mind for 5.1. But I want 6 the soonest possible.
With my Note 4, it would wake up from Android Doze, or simply not enter that state if there was movement of the phone. I felt stupid needing to pick up my phone every 10 min to give it a small shake, but at least it seemed to work. I keep my phone in my pocket when I'm working outside and that always kept the Note 4 from falling into Doze mode. Not so with the S9+. It drops into Doze even in my pocket. Anyway to stop that from happening? Like others here, I feel frustrated needing to activate my screen to find out if there are notifications.
Brokk said:
With my Note 4, it would wake up from Android Doze, or simply not enter that state if there was movement of the phone. I felt stupid needing to pick up my phone every 10 min to give it a small shake, but at least it seemed to work. I keep my phone in my pocket when I'm working outside and that always kept the Note 4 from falling into Doze mode. Not so with the S9+. It drops into Doze even in my pocket. Anyway to stop that from happening? Like others here, I feel frustrated needing to activate my screen to find out if there are notifications.
Click to expand...
Click to collapse
That's not Doze mode. Doze is when Android puts apps to sleep that are in memory not being used. This is done to save battery (and processing time?).
So what is happening here, if I understand, is that your phone display is going blank when you pull it from your pocket?
Scott said:
That's not Doze mode. Doze is when Android puts apps to sleep that are in memory not being used. This is done to save battery (and processing time?).
Click to expand...
Click to collapse
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
Scott said:
So what is happening here, if I understand, is that your phone display is going blank when you pull it from your pocket?
Click to expand...
Click to collapse
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Brokk said:
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Click to expand...
Click to collapse
I concur. Same happens to me.
I don't have this issue at all. I have my phone in my pocket most of the day and don't need to "wake" the phone up for notifications. I can leave my phone unattended for hour or 3 and it still receives the notifications without issues. I don't know if I have turned on a setting that mine works different, but I must say that my battery life isn't that great....as if the phone never sleeps/doze at all
termdj said:
I don't have this issue at all. I have my phone in my pocket most of the day and don't need to "wake" the phone up for notifications. I can leave my phone unattended for hour or 3 and it still receives the notifications without issues. I don't know if I have turned on a setting that mine works different, but I must say that my battery life isn't that great....as if the phone never sleeps/doze at all
Click to expand...
Click to collapse
I'm curious. Do you have any of the power saving modes turned on? Do you use "always on display"?
I never use the power save modes. Aod is on from 5 in the morning till 8 at night
termdj said:
I never use the power save modes. Aod is on from 5 in the morning till 8 at night
Click to expand...
Click to collapse
AoD could be keeping your phone awake, preventing Doze. The power saving features talks about putting apps to sleep, so unless you use them, that could also be disabling Doze. I could try changing the power saving settings, though it seems like a shame. I have zero interesting in AoD for multiple reasons, so it's not worth it for me to use that to solve my problems.
Thanks for the information!
Doze changed in Nougat, I believe, so that motion no longer prevented Doze from working. Since most men, at least, carry their phone in their pocket Doze hardly ever kicked in, greatly limiting its power saving capability.
You can exempt specific apps from Doze if you want to get notifications from them even when dozing.
Settings / Apps / 3 dot menu / special access / Optimize battery usage. Select All Apps from the drop down. Turn off the toggle for any apps you don't want to Doze.
Brokk said:
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Click to expand...
Click to collapse
Yes, I am confusing Doze with the Samsung power saving options. Blah!
I know the battery life will decrease with aod, but I have noticed that even without aod on my battery drop 2% per hour, so I leave it on...There are days that I can go 1 day and 8 hours before charging, but then my sot is only 2 hours....In general I'm happy with the battery life
meyerweb said:
You can exempt specific apps from Doze if you want to get notifications from them even when dozing.
Settings / Apps / 3 dot menu / special access / Optimize battery usage. Select All Apps from the drop down. Turn off the toggle for any apps you don't want to Doze.
Click to expand...
Click to collapse
Thanks!
It seems oddly redundant needing to do essentially the same thing in two places. One well advertised under the battery settings, and the other one hidden under settings/apps/special access.
Hopefully this will fix my problems. Glad to know there is a work around.
Brokk said:
Thanks!
It seems oddly redundant needing to do essentially the same thing in two places. One well advertised under the battery settings, and the other one hidden under settings/apps/special access.
Hopefully this will fix my problems. Glad to know there is a work around.
Click to expand...
Click to collapse
The two settings really are doing different things. Samsung's (in the battery settings), puts apps to sleep after 3 to 7 days (depending on your settings). The won't wake up again until you use them. Doze (the pretty much hidden option in Apps), lets the apps wake up on their own, when you start using the phone, even if you don't access those particular apps.
I'm not sure why the Doze setup is buried so deep in settings, though. I guess Google (or Samsung?) really doesn't want you interfering with it.
meyerweb said:
The two settings really are doing different things. Samsung's (in the battery settings), puts apps to sleep after 3 to 7 days (depending on your settings). The won't wake up again until you use them.
Click to expand...
Click to collapse
I made a mistake of putting an app to sleep that I use to keep my screen awake. It uses a widget to toggle it on/off, but will shut off along with the screen if you intentionally shut your screen off. After putting that app to sleep, the widget stopped working. I had to go find the actual app, start it, then quickly flip back to my home screen and click on the widget. I couldn't undo my "sleep" action on that app. I changed it to "unmonitored", so that the S9+ would never put it to sleep. I rebooted. I shut off the power saving options. Nothing worked. Everytime I would go to the widget (unless I just started the actual app), it wouldn't react to clicking on the widget.
I finally gave up and uninstalled the app from my phone. Rebooted. Reinstalled it and now it works fine. So I'm not sure I agree with "puts the app to sleep in 3 to 7 days". Maybe 3-7 minutes...
Well, 3 to 7 days is what Samsung says, and the optional range you can set in the app. Don't know what specifically happened with that widget, though.
meyerweb said:
Well, 3 to 7 days is what Samsung says, and the optional range you can set in the app. Don't know what specifically happened with that widget, though.
Click to expand...
Click to collapse
Where is the setting(s) for optimal range? I don't remember specifying that. I thought it was more of an on/off thing. White listed (unmonitored resource consumption) or black listed (never let it run in the background). Then apps in neither list it reports to you and you can force them to sleep or not.
Brokk said:
Where is the setting(s) for optimal range? I don't remember specifying that. I thought it was more of an on/off thing. White listed (unmonitored resource consumption) or black listed (never let it run in the background). Then apps in neither list it reports to you and you can force them to sleep or not.
Click to expand...
Click to collapse
Samsung does bury things....
Settings / Device maintenance, click Battery at the bottom.
Then click the 3 dot menu at the top, and Advanced Settings.
Tap App power monitor (the text, not the toggle).
Tap Put unused apps to sleep (again, the text).
You can set the slider anywhere between 3 days and 7.
I spent several days just wandering through every settings option I could find after I setup the phone. Discovered all kinds of hidden things. Sometimes I can even remember where I saw them.
I'm close to having the phone perfect but these two still persist. There is a myriad of old options for Xposed and I was wondering if anyone has had success with any of them? I use the phone for a GPS unit on a cycle with a dynamo hub, so the waking up is annoying.
I've sorted the sound already, so there are two wake up conditions:-
1. power is enabled
2. battery reaches 100%.
Cheers, Andrew
snoopy20 said:
I use the phone for a GPS unit on a cycle with a dynamo hub, so the waking up is annoying.
Click to expand...
Click to collapse
Hi Andrew,
I can't help with Xposed, but I have a suggestion and a side question.
My suggestion : try IpBike (with IpBikeKey to unlock it).
The author of IpBike reads and answers e-mails. He is opened to new features if the idea is good.
If IpBike can't force the screen off (I never tested, as I don't charge my device as I cycle !), he may add the feature.
My question : is the PVG100 ANT+ capable ?
I use a Sony-Ericsson Xperia Active as a cycle computer (powered by IpBike), with ANT+ Speed, Cadence and Heart-rate sensors.
I would like to replace it with a PVG100E/EU, but the ANT directory does not list any Palm device.
Have a nice day !
Cobus.
Probably not, ANT is an extra cost for a manufacturer.
I found an open-source app which works. It's a bit old but still it does the job.
Basically it registers itself as an admin app so it can control the screen, then when a wakeup comes in it turns the screen back off. It's quick enough that the screen doesn't get a chance to come on. No root required.
snoopy20 said:
I'm close to having the phone perfect but these two still persist. There is a myriad of old options for Xposed and I was wondering if anyone has had success with any of them? I use the phone for a GPS unit on a cycle with a dynamo hub, so the waking up is annoying.
I've sorted the sound already, so there are two wake up conditions:-
1. power is enabled
2. battery reaches 100%.
Cheers, Andrew
Click to expand...
Click to collapse
Have you tried enabling "zen mode?" Zen mode keeps everything on the phone from waking I believe. I have tried it, but got annoyed when the wifi would cut out once I turned my screen off, because it would stop what I was listening to. Not sure exactly what you're looking for, but zen mode might be something to play around with.
To activate zen mode, the easiest way is probably through the app "setedit." Under "system" options, scroll to the bottom and change zen mode from 0 to 1.