I like to leave my HTC One cradles with blinkfeed running. Using Viper on 4.1, one could choose a setting to disable sleep when connected to power. This was never perfect, since, no matter what, it got dimmed after 10 minutes, but it was better than nothing. Is there any way with the 4.3 firmware to make this work (preferably with no screen dimming!)?
scottegos2 said:
I like to leave my HTC One cradles with blinkfeed running. Using Viper on 4.1, one could choose a setting to disable sleep when connected to power. This was never perfect, since, no matter what, it got dimmed after 10 minutes, but it was better than nothing. Is there any way with the 4.3 firmware to make this work (preferably with no screen dimming!)?
Click to expand...
Click to collapse
I'm new to the phone and still learning the ins and outs (and still on 4.1), but you could build a tasker profile to do what you're looking for pretty easily.
fachadick said:
I'm new to the phone and still learning the ins and outs (and still on 4.1), but you could build a tasker profile to do what you're looking for pretty easily.
Click to expand...
Click to collapse
Thanks for the idea. Every once in a while I think of using tasker and never can get it to do what I want. In this case, I get the idea that I set a "plugged in" state condition, but the 'screen on ' action tells me to try the secure settings plugin, which seems even more impenetrable.
scottegos2 said:
Thanks for the idea. Every once in a while I think of using tasker and never can get it to do what I want. In this case, I get the idea that I set a "plugged in" state condition, but the 'screen on ' action tells me to try the secure settings plugin, which seems even more impenetrable.
Click to expand...
Click to collapse
yeah - I could never get screen on to do what I wanted either. As a workaround, I set up a task that changed the display timeout to 23 hours - which is effectively the same thing.
Related
Wifi keeps turning off during sleep...?
.. and yes, I've turned 'Keep Wi-Fi on during sleep' to always. Tried a couple of 'keep wifi on' type apps, no help. Any thoughts? thanks, jf
friedsonjm said:
Wifi keeps turning off during sleep...?
.. and yes, I've turned 'Keep Wi-Fi on during sleep' to always. Tried a couple of 'keep wifi on' type apps, no help. Any thoughts? thanks, jf
Click to expand...
Click to collapse
Mine does to, but I don't have it set to "always", since I kind of prefer it that way. I'll give it a shot to see what the results are. Do you notice any difference between the two settings, as far as how long it stays active and on?
phonic said:
Mine does to, but I don't have it set to "always", since I kind of prefer it that way. I'll give it a shot to see what the results are. Do you notice any difference between the two settings, as far as how long it stays active and on?
Click to expand...
Click to collapse
Have not tried the 'when plugged in only,' will try it now..
EDIT: Nope, that was no better.. <sigh>
friedsonjm said:
Have not tried the 'when plugged in only,' will try it now..
EDIT: Nope, that was no better.. <sigh>
Click to expand...
Click to collapse
31 Minutes on hold - so far - with Google device support...<sigh>
friedsonjm said:
31 Minutes on hold - so far - with Google device support...<sigh>
Click to expand...
Click to collapse
FYI - "Always on" seems to be working fine for me. I turned my screen off about an hour ago, and just connected into the system via Cerberus. In the past, wifi would have shut off within a few minutes and I would get a connection timeout warning. So maybe your unit is having issues with it. I've also only lost MAYBE 1% in battery power, so I think I will leave mine in this state as opposed to disabling wifi on sleep.
I have this problem on some of my devices on 1 of my wife access points but not the other. I believe I could possibly tweak some settings on the access point as I don't believe it is the android device. I use an app called WIFI Fixer and that keeps things working.
friedsonjm said:
Wifi keeps turning off during sleep...?
.. and yes, I've turned 'Keep Wi-Fi on during sleep' to always. Tried a couple of 'keep wifi on' type apps, no help. Any thoughts? thanks, jf
Click to expand...
Click to collapse
Happening on multiple devices. Try advanced WiFi lock on the market. Its one of the first apk's I install and always works.
Sent from My Ball of Fire™
SirWill said:
I have this problem on some of my devices on 1 of my wife access points but not the other. I believe I could possibly tweak some settings on the access point as I don't believe it is the android device. I use an app called WIFI Fixer and that keeps things working.
Click to expand...
Click to collapse
Seemed to work for a while last night... but woke up this morning and it was off again <sigh>.
Does keeping wifi "always on" adversely affect your battery?
clankfu said:
Does keeping wifi "always on" adversely affect your battery?
Click to expand...
Click to collapse
Yes. How much depends on how many apps you have set for auto-updates, I suppose. If you're running several games and social networking apps and they're set for auto-updates, you'll experience a battery drain from them checking for updates every 5 minutes. How much, I can't say. I still don't have my Nexus 7. But if your device drops off the WiFi signal, those apps will know that there is no data connection and not try to update until there is one.
Not to change the subject of the thread, but if I see one more <sigh> I'm going to snap.
Also, OP, why do you need WiFi to be always on? If you can't live without it try: http://bit.ly/MdurdU
As I mentioned, "always on" is working fine for me. Tested it over a period of a few hours. Even moved from one AP to another (ie: work to home), and it auto joined the new wlan.
Battery drain is very minimal in my case. Maybe 0.5-1% an hour, if that.
Yeah but then the apps can't update. IMHO, if you don't want constantly-updating apps, don't enable them to.. If they are checking as often as you think, I would find a different app which gives you what you want but doesn't do that sillyness..
I keep Wi-Fi on 24/7 on all my devices. GPS and BlueTooth too.
I *REFUSE* to let my device "run my life". I find a way to make my battery life happy, and still enjoy my devices. I disable all of the other senseless crap like Facebook or FriendStream, or bloatware-apps.. I don't EVER use an app like ATK or JuiceDefender, or if I do, I only use it instantly to kill an app and then I make it kill itself too. In my 3+ years experience with Android and 30+ devices, I've found that a LOT of apps will TRY to restart even if you kill them. Imagine ATK killing an app, it restarting, ATK auto-killing it again, it restarting again, ATK re-killing it AGAIN, loop()... get my point? Uninstall the problem app and/or find a similar one which doesn't treat your device like it's own playground..
miketoasty said:
Not to change the subject of the thread, but if I see one more <sigh> I'm going to snap.
Also, OP, why do you need WiFi to be always on? If you can't live without it try: http://bit.ly/MdurdU
Click to expand...
Click to collapse
,,
I want to use my table as a phone via VOIP when I travel, need to get incoming 'phone' calls.
That app is coming across in play as not compatible with the N7 ? <darn> <grin?>
I use my Nexus 7 as a speaker phone so had to set "Keep Wi-Fi on during sleep" to "Always". Easy fix.
mi7chy said:
I use my Nexus 7 as a speaker phone so had to set "Keep Wi-Fi on during sleep" to "Always". Easy fix.
Click to expand...
Click to collapse
Yes... and as I said in the post that started this thread, on my N7, it still turns off.... easy, but no fix.
friedsonjm said:
Yes... and as I said in the post that started this thread, on my N7, it still turns off.... easy, but no fix.
Click to expand...
Click to collapse
Now rooted and still trying... still keeps auto-turning-off !
This might be a defect in your units. I have gone many, many hours (12+) with my unit in standby mode without it losing wifi connection. It will also continue to sync with email, etc. during this time (and provide audio notifications).
I only lose .5-1%/hour, so I've left it "always on".
I'm having the same issue. On overnight sleep, the wifi is off when I turn it on. It won't reconnect until I toggle wifi on and off. Nothing I've tried so far has worked. Little worried its not as widespread of an issue as I thought it would be.
ssahnan said:
I'm having the same issue. On overnight sleep, the wifi is off when I turn it on. It won't reconnect until I toggle wifi on and off. Nothing I've tried so far has worked. Little worried its not as widespread of an issue as I thought it would be.
Click to expand...
Click to collapse
Since mine has worked flawlessly (stock rom) for very long periods of sleep with an active wi-fi connection, I would have to believe you have a defect in yours. Either that, or a problematic AP.
I like to keep the battery in my Note as charged up possible which means I plug it into the charger most times I come home and so I have to unplug it whenever I leave ... and so both coming and going the phone display turns on when I plug/unplug it and 99.9% of the time I don't want this. If the display is off it should just stay that way! For some reason I find this unwanted behavior so obnoxious I was going to get rid of the phone ... until I realized that getting a new phone might likely have the same problem since it seems to be quite common. I'm not so sensitive to other things not quite working the way I would like, but that one is so obviously crazy and happens so many times per day that it bugs me more and more each day. I've never seen this discussed, so my main confusion on this issue is why this doesn't seem to bother anybody else.
Anyway I noticed in the Revolt Rom there is a feature in the list called "Wake up on charging".
Does having this feature imply that one can disable it ... i.e. not have it wake up when the charger is plugged in?
Also does this mean that you can also disable Wake up when charging is terminated by unplugging the charger?
Please say yes and I will just die now and go to heaven.
If my interpretation of this feature is correct ... can most modern roms do this or is this unique to the Revolt rom?
Thanks
~Paul
~Paul
wrong section to post q
I have found option in developer menu but that states to keep device awake.
Usually screen dims and sleeps after a while.
I press powerbutton to put screen into sleep.
Another workaround could be to use tasker and program it to set screen off upon adding charger.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Usually screen dims and sleeps after a while.
I press powerbutton to put screen into sleep.
Click to expand...
Click to collapse
Yes it dims after 10 minutes (in my case since that is my sleep delay setting), but why should I waste 10 minutes of power or why should I have to press the power button to avoid this? My point is that this makes no sense. It would make way more sense for the screen to turn off when I tell it to and not otherwise.
> Another workaround could be to use tasker and program it to set screen off upon adding charger.
Now you're talking. A suggestion that actually worked. I had never heard of tasker. I paid the 3 bucks, then spent an hour learning how it works and figuring out the right combination of profile contexts and tasks ... and then it didn't work. I was using button number 26 which was supposed to be the power button but I never figured out why this didn't turn off the screen on the N7000. (Surprisingly tasker does not have a task identified as turning off the display!). Eventually however I stumbled across the fact that the task item called "system lock" turned off the display, and that did the trick for me. It was a minor expense and a lot of work to get my phone to behave the way I believe it should have to begin with ... but I'm happy that I prevailed in the end. Thanks very much for your suggestion.
~Paul
Haven't seen that option in stock-based ROMs but CM ROMs can do this.
I'm currently using CM10.2 and the screen stays off while connecting/disconnecting the charger
good one
jakuburban said:
Haven't seen that option in stock-based ROMs but CM ROMs can do this.
I'm currently using CM10.2 and the screen stays off while connecting/disconnecting the charger
Click to expand...
Click to collapse
Do you know if that is true with CM10.1 based roms as well?
I don't flash often, and I don't want to flash a CM10.2 based rom since it looked to me that this was still too much of a work in progress.
~Paul
pmennen said:
Do you know if that is true with CM10.1 based roms as well?
I don't flash often, and I don't want to flash a CM10.2 based rom since it looked to me that this was still too much of a work in progress.
~Paul
Click to expand...
Click to collapse
I think jellybam had this option and surely some other ROMs have it too, but I can't help You with 10.1 ROMs as I don't use them myself.
However You might wanna give a chance to 10.2. I think it's pretty good for daily usage as I'm using it like 3 weeks now. All the major bugs have been fixed. The only unsupported apps are the navigation ones like tom tom and automapa. However forevermaps still works.
That's what worked for me in Tasker
Profile: State/Power/Power any
Entry --> Power - On
Exit <-- Power - Off
Task: Power - On
Variable/Variable set/%PWR =1
Task: Power - Off
Variable/Variable set/%PWR =0
Profile: State/Display/Display State Off
Entry --> Power - Old
Exit <-- Screen - Off
Task: Power - Old
Variable/Variable set/%PWR_OLD = %PWR
Task: Screen - Off
Display/System Lock
If %PWR_OLD =/= (not =) %PWR
Variable/Variable set/%PWR_OLD = %PWR
Ok so I'm on 6.0.1 and for the life of me I can't figure out this spastic notification behavior. When I'm using my phone, notifications come in just fine. However let's say I've left my phone on my desk and come back in an hour and pick up the phone... as soon as I turn the screen on, all the notifications start flying in from the past hour, including all the notification sounds 1 by 1 in quick succession. I've checked all the options I can to see if there is anything related to this behavior but I can't find it.
I've gotten used to iOS where my notifications are always on the screen waiting for me so I can pick up the phone and glance and put back down, without the hoopla of watching them fly in after turn the screen on and listening to all the annoying notification sounds jumbled together. I'm by no means new to Android however. I've owned many but my last was my N5 which got long in the tooth so I switched to a iPhone 6S as my daily driver and have been using my N5 just to play around and keep up with development of my favorite ROMS and apps. I saw the 6 on a really good deal so I decided to pick up it and see what it would be like to have Android as my daily driver again.
Anyhow, all that being said, how do I get the desired outcome of notifications actually coming in when the phone is idle and waiting for me without having to load after I turn the screen on? I'm guessing notifications in 6.0+ are tied to wakelock events but not sure. Any thoughts?
itpromike said:
Ok so I'm on 6.0.1 and for the life of me I can't figure out this spastic notification behavior. When I'm using my phone, notifications come in just fine. However let's say I've left my phone on my desk and come back in an hour and pick up the phone... as soon as I turn the screen on, all the notifications start flying in from the past hour, including all the notification sounds 1 by 1 in quick succession. I've checked all the options I can to see if there is anything related to this behavior but I can't find it.
I've gotten used to iOS where my notifications are always on the screen waiting for me so I can pick up the phone and glance and put back down, without the hoopla of watching them fly in after turn the screen on and listening to all the annoying notification sounds jumbled together. I'm by no means new to Android however. I've owned many but my last was my N5 which got long in the tooth so I switched to a iPhone 6S as my daily driver and have been using my N5 just to play around and keep up with development of my favorite ROMS and apps. I saw the 6 on a really good deal so I decided to pick up it and see what it would be like to have Android as my daily driver again.
Anyhow, all that being said, how do I get the desired outcome of notifications actually coming in when the phone is idle and waiting for me without having to load after I turn the screen on? I'm guessing notifications in 6.0+ are tied to wakelock events but not sure. Any thoughts?
Click to expand...
Click to collapse
What you are seeing is androids new doze feature. It puts apps to sleep when the device has been on a flat surface for a long time unmoved. Go into settings/apps/What ever app you want and change the battery priority settings.
zelendel said:
What you are seeing is androids new doze feature. It puts apps to sleep when the device has been on a flat surface for a long time unmoved. Go into settings/apps/What ever app you want and change the battery priority settings.
Click to expand...
Click to collapse
Ah OK. I totally forgot about doze... Want aware it was implemented in this manner. All the setting to change this would be in the app/notification section and Rick the "treat add priority" option? The description associates this option with so not disturb mode but it also affects doze too?
Sent from my Nexus 6 using Tapatalk
itpromike said:
Ah OK. I totally forgot about doze... Want aware it was implemented in this manner. All the setting to change this would be in the app/notification section and Rick the "treat add priority" option? The description associates this option with so not disturb mode but it also affects doze too?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Ahh sorry had to find it again. It is under settings/battery then hit the 3dot menu for battery optimization. Then select the app. And change the settings. An easy work around is to plug it in when you will be leaving it for awhile. This disables doze.
itpromike said:
... as soon as I turn the screen on, all the notifications start flying in from the past hour, including all the notification sounds.
Click to expand...
Click to collapse
settings - sounds ¬ifications - nofications ringtone --> none
What I would like to have happen is have the clock go into night mode when: wirelessly charging, connected to a specific wifi network, and to start and end at specific times.
I've been messing around with this and can't figure it out for the life of me. Any help is greatly appreciated.
Thanks
Larzzzz82 said:
What I would like to have happen is have the clock go into night mode when: wirelessly charging, connected to a specific wifi network, and to start and end at specific times.
I've been messing around with this and can't figure it out for the life of me. Any help is greatly appreciated.
Thanks
Click to expand...
Click to collapse
where exactly are you stuck at?
Basically the whole thing... I created a profile called night mode to turn on and off at certain hours.
In the tasks tab, I've tried to set up the wifi network, but don't see a variable for specifying being connected to it, nor do I see anything for the battery charging wirelessly.
A couple you tube videos later and I'm scratching my head harder.
Larzzzz82 said:
Basically the whole thing... I created a profile called night mode to turn on and off at certain hours.
In the tasks tab, I've tried to set up the wifi network, but don't see a variable for specifying being connected to it, nor do I see anything for the battery charging wirelessly.
A couple you tube videos later and I'm scratching my head harder.
Click to expand...
Click to collapse
so for the Wi-Fi part:
- there is the state 'Wi-Fi connected' to activate when you are connected
- you can use 'test net' to store ssid to a variable, then check it for a match with certain ssid, with which you want the profile to react to - only do when connected to certain Wi-Fi.
I don't have wireless charge so I cannot say anything here, but if I remember correctly, recent update of Tasker has included detection of this, so too should bff able to sound something useful in those states or events.
Then finally, in the clock app, you can either try to use intent or simulate taps to switch it to night clock.
After that, hopefully you will be happy with the result
Thank you sir. I will give those a shot
Light dawns on marble head! I got it to work, 98% of what I envisioned.
Is there a way to make this work without having to wake the phone up first? A lot of times, I just place it on the charger.
Larzzzz82 said:
Light dawns on marble head! I got it to work, 98% of what I envisioned.
Is there a way to make this work without having to wake the phone up first? A lot of times, I just place it on the charger.
Click to expand...
Click to collapse
what is your solution so far?
for connecting to Wi-Fi, sometimes it does not connect without screen on though, and I still have not figured that out.
Rather than try to explain it, these are my set ups.
Didn't seem to work as I wanted until I added the the, If lines to tasks 2and 3.
Still gotta unlock the phone to start the process though.
Larzzzz82 said:
Rather than try to explain it, these are my set ups.
Didn't seem to work as I wanted until I added the the, If lines to tasks 2and 3.
Still gotta unlock the phone to start the process though.
Click to expand...
Click to collapse
did you check to use root in the run shell commands?
Sadly I don't have a solution for the unlocking part.
I did use root. Had to add the if statement at the bottom for. Both tasks are the same aside from the input tap x y numbers
PS.. If I remove the pattern lock, it will work the way I want(ed) it to. Not worth it to do that IMO.
Sent from my Nexus 6 using Tapatalk
Larzzzz82 said:
I did use root. Had to add the if statement at the bottom for. Both tasks are the same aside from the input tap x y numbers
PS.. If I remove the pattern lock, it will work the way I want(ed) it to. Not worth it to do that IMO.
Click to expand...
Click to collapse
ah the pattern lock! now I see the pattern
do you have Xposed? maybe try to allow clock app over lock screen?
No exposed. Is it out for 7.1.1?
Sent from my Nexus 6 using Tapatalk
Larzzzz82 said:
No exposed. Is it out for 7.1.1?
Click to expand...
Click to collapse
oh naah....
Seems to stop after the battery is charged... Gotta figure out how to latch the power till the end of the task.
So I just got a GS8. Fantastic phone. The only issue I am noticing is that when the phone enters "Do not Disturb" mode, it does not exit as scheduled. Typically it is set to turn on at 10 PM each night and turn off at 6 AM the next day. (save for the alarm that goes off at 5 AM). The alarm goes off fine. The phone, however, stays in "Do not Disturb" mode well past 6 AM and until I turn it off. Anyone else notice similar behavior? Could this result from the phone being connected to the A/C charger? I ask because when I set "Do not Disturb" to turn on and off at work it does so just fine. At work the phone is not connected to a charger.
I'm blanking on what it was, but I was running an app that was causing this issue. I've looked through my Google play library and just can't recall what it was. Might have had something to do with volume control. Start by removing anything you aren't using. If the problem persists, try removing anything that sounds like it could interact with audio or notifications until you find it. Worst case, factory reset, confirm issue is gone, then add things back until issue recurrs. I'll try again to jog my memory.
rcobourn said:
I'm blanking on what it was, but I was running an app that was causing this issue. I've looked through my Google play library and just can't recall what it was. Might have had something to do with volume control. Start by removing anything you aren't using. If the problem persists, try removing anything that sounds like it could interact with audio or notifications until you find it. Worst case, factory reset, confirm issue is gone, then add things back until issue recurrs. I'll try again to jog my memory.
Click to expand...
Click to collapse
This gets weirder and weirder. So, I am coming from a Mate 9. on that phone I could set multiple Do Not disturb profiles. So I had one set for overnight (10 PM to 6 AM and one set for work hours (7 AM to 3:30 PM). Although the GS8 only allows one profile, it seems to have "remembered" the second profile. I say this because the phone went into "do not disturb" at 7 AM. I am not even sure how that's possible. I did restore apps via the google, but I cannot think of anything else besides what you are recommending. I may have to do a factory data reset as you recommend and set everything up.
anl2304 said:
This gets weirder and weirder. So, I am coming from a Mate 9. on that phone I could set multiple Do Not disturb profiles. So I had one set for overnight (10 PM to 6 AM and one set for work hours (7 AM to 3:30 PM). Although the GS8 only allows one profile, it seems to have "remembered" the second profile. I say this because the phone went into "do not disturb" at 7 AM. I am not even sure how that's possible. I did restore apps via the google, but I cannot think of anything else besides what you are recommending. I may have to do a factory data reset as you recommend and set everything up.
Click to expand...
Click to collapse
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
rcobourn said:
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
Click to expand...
Click to collapse
You know, as long as I have had an android phone and I didn't think to do that. I should have. One issue I need to deal with is whether turning off the built-in Do Not Disturb disables that suspected hidden profile. If so, then I am good to go, if not, then I need to do the factory reset before using an app from the playstore (probably gives me more options than what Samsung allows).
Thanks.
rcobourn said:
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
Click to expand...
Click to collapse
Resetting the device did the trick. rather than restoring apps from the Huawei Mate 9, I started fresh and downloaded apps from the app store. A pain, but it worked. Thanks again.