Hi!
Has anyone had success with turning on the screen on an Archos Titanium (I have 80) using motion sensor?
I tried different apps - "Auto Screen On", "Motion Action", "SleepTweak" and Tasker together with Secure Settings. It's possible to turn off the screen with motion but not on, even if you tell the app to keep wakelock on. Also, Tasker says that Display Action: Turn On "is not available on this device".
I hope there's a way round this problem.
Cheers!
Veikko
Related
Ok, I have a voice changer app that I want to use with the screen off. Ideally I'd start the app, turn on real-time processing, then turn the screen off. Currently, it only runs when the screen is on, as soon as I turn the screen off the app stops all voice processing. Screen needs to be off so the battery will last longer, and so the settings can't be changed accidentally (so touch has to be disabled as well).
I either need the app to keep running in the background, or have the screen turn off but not actually locked (I dunno the right term, but if the screen was off and didn't accept touch input, but the phone thought the screen was on...that'd be fine).
Closest I've found is to edit the AndroidManifest.xml file to set it persistent, then make it a system app. This will take me a while to figure out, and not even sure it'll work.
Is there some simple solution I'm overlooking? I've seen an app that turns off the screen with help from the proximity sensor...but I want the screen off whether it's in my pocket or lying on top of a table.
Edit: I tried some apps that use the proximity sensor to turn off the screen; as soon as the screen goes off, the voice changer app just stops. I have no idea what's triggering it (if the phone is actually entering a sleep state, or if the app is specifically watching for the screen to go off and suspends itself). Thought that might be a workaround, but nope.
Hey Guys,
I'm having a weird issue where the screen brightness keeps changing itself every time I turn the screen off. I tried disabling Smart Actions & Automate It (tasker-like app), changing the brightness in the display setting, unchecking the display power saver option. In all cases if I set the brightness to 100% after turning the screen off and then on again the brightness will be down to like 10% or so, although the indicators I have will still tell me the screen is at 100%. Any ideas?
Thanks.
[email protected] said:
Hey Guys,
I'm having a weird issue where the screen brightness keeps changing itself every time I turn the screen off. I tried disabling Smart Actions & Automate It (tasker-like app), changing the brightness in the display setting, unchecking the display power saver option. In all cases if I set the brightness to 100% after turning the screen off and then on again the brightness will be down to like 10% or so, although the indicators I have will still tell me the screen is at 100%. Any ideas?
Thanks.
Click to expand...
Click to collapse
Me too, it only happens randomly though, i thought it had something to do with the"Lux" app i use to control brightness.
Do u use any screen protectors? It could b interfering with the light sensor
Sent from my ICS Moto Razr XT910
There is a screen protector but this is happening when brightness is not set to Auto. It's set to 80% and every time I hit the power button and then turn the screen back on it dims to like 0-10%. I've tried closing all running processes and it still happens. I also tried resetting the phone and it initially wasn't doing this but once I setup all the programs it does, so it must be somehow related to a non-running process program configuration. Any ideas?
Thanks
Edit: Found out it was the Lightflow app, uninstalled it and no more brightness dimming issue.
[email protected] said:
There is a screen protector but this is happening when brightness is not set to Auto. It's set to 80% and every time I hit the power button and then turn the screen back on it dims to like 0-10%. I've tried closing all running processes and it still happens. I also tried resetting the phone and it initially wasn't doing this but once I setup all the programs it does, so it must be somehow related to a non-running process program configuration. Any ideas?
Thanks
Edit: Found out it was the Lightflow app, uninstalled it and no more brightness dimming issue.
Click to expand...
Click to collapse
interesting. I had that app installed for a while, maybe it messed something up that uninstalling didn't fix. I guess a hard reset is in my future. sigh.
I like my screen to always be on when I am charging the phone, mostly becuase I drive a lot and it sucks to have the screen go off when you are using google maps. I seem that I have to keep changing the "screen always on" in the developer mode section in settings. Has anyone else been able to make this change stick?
I definitely had that option checked when I set up my phone after flashing beans v3 but when I went to check just now it was not selected. I guess I have the issue too, apparently.
Update: I just restated my phone and the option is unchecked again. Definitely not sticking after reboot for some reason.
Sent from my SCH-I605
I use the app *My Settings Pro* to set the screen to never time out whenever I have the phone docked in my truck.
It stays on until I set the screen timeout to 30 seconds & put it in my pocket.
There is a free app in the market called "Screen On"
It allows you to set the screen to stay "Always On" by a per app basis
So for example you can only select Google Maps and the only time the screen will stay on is when you are in Google Maps, etc..
My phone has been doing this since day one after reboot stay awake is unchecked I just use tasker now.
Sent from my SCH-I605 using xda premium
It mildly annoying. I like the screen on when its charging so I can just glance for notifications without touching it, or in the car mount. I guess I can just use my NFC tags for now.
Just a suggestion, but you guys may want to be careful how long you keep your screen lit while charging.
I had my old G3 set to never go out while charging (it was on all night at times) and now it shows some nasty screen burn-in on any white screen (like the gmail background).
Any time it is on a white BG, you can clearly see a gost image of the home screen and the clock widget/icons etc.etc.
I have a similar issue. I set the checkbox to always on when connected via USB directly after setting up the phone for the first time and now it's always on is re-on when deselect it and go to the settings again afterwards.
Could it be some side effect / conflict caused by some powerful apps like "NFC task launcher" or something like that who can change settings as well as the settings dialogues?
Hi
Tasker begginer here.
I'm having some minor issues with Tasker that I was hoping you could help me sort out:
I use Greenify and I was having a little problem with autohibernation feature in my unrooted Nexus 5: The screen has to turn on in order to automatically greenify something. This is a problem when the phone is in my pocket or facing down on the table because it conflicts with Gravity Screen (this app turns the screen off -and keeps it off- when the proximity sensor is active and the device is in a particular orientation), so when the phone is in my pocket or laying face down on a surface, Greenify can't finish its job because Gravity Screen will quickly turn the screen off.
In light of this, I disabled the autohibernation feature in Greenify and made a rather simple group of profiles to control it from Tasker. The main profile, the one that calls the "Hibernate now" shortcut from Greenify, is triggered when the screen turns off and has and If condition. This is the logic of that if:
- If
Proximity sensor: Not active
AND
Screen off
- Then
Run task
I do this to make sure that the hibernate action is not triggered while the screen is on or while the proximity sensor is active. Since Tasker doesn't have a variable for monitoring the proximity sensor, I made a profile that sets a variable (%PROX) to 1 when it's covered and 0 when its uncovered. So the if conditional uses the value of %PROX.
The problem is that if I turn the screen on WHILE the proximity sensor is active, Tasker skips the if statement (as it should), but if I turn the screen off with the proximity sensor uncovered and then cover it, it'll run the task. It's as if the profile that sets the variable %PROX to 1 does not work while the screen is off. Is this normal behaviour? How can I make this work better?
I managed to sort this out by deactivating Gravity Screen at the beggining of the task and reactivating it at the end (with a little waiting to give Greeenify time to finish), but I still want to keep my screen off while the phone is in my pocket.
My other doubt is regarding a group of profiles (that I got from here) that turn Wi-Fi on whenever I'm near two locations using the cell tower and Wifi near state in Tasker. I made some minor adjustments to these profiles, but they're still basically the same. The problem I'm having is that, most of the times, these profiles won't do anything if the screen is off. For example, I have it set to recognize cell towers near my house (and of course my Wifi connects automatically). Let's say I get home and I haven't used my phone in a while (screen off), I'd expect to see my Wi-Fi on and connected some time after I arrived, but this is not the case. It is not until I turn the screen on AND unlock the phone that I see the profiles doing their thing. I see wifi connecting, flash alerts and so on. This probably have something to do with the fact that, for some reason, my phone will not connect to a network while the screen is off. Same example, I get home with wifi on and the screen off, and I'll only see the wifi connecting after I turn the screen on (this happens with or without Tasker and with any wifi) regardless of how long I've been home.
Could it be that the near wifi profile cannot toggle wifi or can't recognize any network while the screen is off due to this bug I have with Wifi connections in my phone (Which I haven't been able to sort out)?
Thanks in advance and sorry for the long post!
Help with wifi profile
Hi, i saw your post in here and i think i can help, do you still have that problem or you managed to fix it? I think I might be able to help you
Hi,
I have this issue with my watch: sometimes I can light-up the watch by touching the display and most of the times this doesn't work. Is this a feature (when it works) or a bug (when doesn't work)?
Thank you!
Just few seconds after your screen goes off, it would get back on by tapping on screen. In other cases you couldn’t make it on by tapping.
I just hop on this thread about screen light.
I trying to find the setting to turn off the screen while on running activity. I notice the screen is light on entire running activity until complete. I had already enable wrist lift option to turn on the screen when i need checking the running stats.
Anyway find the setting to turn it off or perhaps sleep mode. Thank you in advance.
There is no such option in Zepp yet. Hopefully they will add it, since screen-on is very battery-consuming.
casper709394 said:
I just hop on this thread about screen light.
I trying to find the setting to turn off the screen while on running activity. I notice the screen is light on entire running activity until complete. I had already enable wrist lift option to turn on the screen when i need checking the running stats.
Anyway find the setting to turn it off or perhaps sleep mode. Thank you in advance.
Click to expand...
Click to collapse
You can turn it off by going into workout settings.
If you disable light on lift, touch to light up display will be also disabled. At least it happens on mine.