Database Info

Looking for a simple brightness managment app

All I want is an application that can switch between Auto Brightness to Minimum setting (OS specified or lower) at specific time, time when it gets dark. or maybe it can choose the time automatically based on dusk and dawn.
I noticed that Auto setting NEVER drops to minimal setting for some reason......

kolyan said:
All I want is an application that can switch between Auto Brightness to Minimum setting (OS specified or lower) at specific time, time when it gets dark. or maybe it can choose the time automatically based on dusk and dawn.
I noticed that Auto setting NEVER drops to minimal setting for some reason......
Click to expand...
Click to collapse
There is an app called Timeriffic (I think that's how it's spelled). You just input the settings into the app and at that predetermined time, it will adjust settings (including brightness, not sure about auto brightness).
I have it set so that at a certain time (when I leave the house) it will turn off the wifi, turn on vibrate, etc...
But if you fall out of your routine, you kind of go bonkers because you forget that you have timeriffic set and can't figure out why the wifi turned off, etc... LoL!

How about just using Power Widget when to switch between auto/minimal when you realize the screen is too bright?

Thanks. Timeriffic gets the job done, but i wish it would support auto brightness. using power widget doesnt work for me because if i forget to switch back to auto setting, in sunny day i cant even see the screen at all and have to find shaded area just to switch back

kolyan said:
Thanks. Timeriffic gets the job done, but i wish it would support auto brightness. using power widget doesnt work for me because if i forget to switch back to auto setting, in sunny day i cant even see the screen at all and have to find shaded area just to switch back
Click to expand...
Click to collapse
Yeah I've had to learn where certain objects are on my home screen.
*Unlock* *Swipe right* *press top right of phone*
Haptic feedback is my friend
It's a shame, OLEDs are so much better than TFT screens for battery conservation but they suck in the light, you know, outside, the one place you are most likely to use your MOBILE phone. Ah well, it performs almost as well as the iPhone when the N1's on full brightness. I held it next to my friend's 3GS, but thinking about it forgot to check what brightness hers was on... DOH.
I think they've corrected it now though, with newer designs.

There is also an app that is called auto bright and it can be made into a homescreen shortcut and is basically a macro that turns on autobright. I put it next to my power control widget so in the case where I need to switch brightness manually I can easily switch back. FYI Froyo's power widget has added the autobright setting so soon as a stable version of Froyo comes out this will be a mute point.
-------------------------------------
Sent via the XDA Tapatalk App

Setting Profiles does the same as well, and a whole lot more.

App I use is called, dimmer. It has to manually be switch.

jimtc said:
There is also an app that is called auto bright and it can be made into a homescreen shortcut and is basically a macro that turns on autobright. I put it next to my power control widget so in the case where I need to switch brightness manually I can easily switch back. FYI Froyo's power widget has added the autobright setting so soon as a stable version of Froyo comes out this will be a mute point.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
OP pointed out (correctly) the Automatic Brightness setting will never automatically set the brightness to the minimum point (that is, as low as you could set it manually). I can confirm that, though Froyo does include the Automatic option on the power control widget, it still won't go all the way dim. It seems rather silly that the Automatic range doesn't go all the way down.
Also, the word you're after is "moot", not mute.

codesplice said:
OP pointed out (correctly) the Automatic Brightness setting will never automatically set the brightness to the minimum point (that is, as low as you could set it manually). I can confirm that, though Froyo does include the Automatic option on the power control widget, it still won't go all the way dim. It seems rather silly that the Automatic range doesn't go all the way down.
Also, the word you're after is "moot", not mute.
Click to expand...
Click to collapse
yes. thats correct. if auto setting would go all the way down, then i would not need any 3rd party software to begin with. i really wish we could adjust the range and sensitivity of the sensor
ps. developer of Timeriffic said that its not possible to add Auto Brightness setting to his app because there is no API for that and the only way around is to hack it.

[Q] Xoom as Alarm Clock

My antique alarm clock just died. I was thinking it might be possible to use my Xoom as a replacement but I cannot find a way to dim the screen while on it's docking station. The screen simply sleeps. Is there a way to use the Xoom in the cradle and have a setting to keep the screen active so one can see the time?
Thanks.

OracleBlue said:
My antique alarm clock just died. I was thinking it might be possible to use my Xoom as a replacement but I cannot find a way to dim the screen while on it's docking station. The screen simply sleeps. Is there a way to use the Xoom in the cradle and have a setting to keep the screen active so one can see the time?
Thanks.
Click to expand...
Click to collapse
Are you rooted? If so, there are apps to really dim the screen. If not, you could use Screen Filter.

Try 'alarm clock plus' in the market. Works great.

Tried three of the "Alarm Clock Plus" and they all did a force close. I didn't want to try all of them so I thought I would ask for specifics.
On the screen filter option, all it did was dim the screen and not show the clock screen. It also did a force close when trying to get to the settings.
Thanks though.

I have been using gentle alarm for months. It has a night display mode that I use and is not to bright.

I use superdim and it works well for me.

I go into the development section and turned on Keep Backlight On When Connected to USB then I use the standard clock, works perfect for me

Try one of the Nightstand clock apps by Digital Guesswork, Nightstand Bold has a dimmer control on the side.

while on the docking station you should be able to go to "clock" or if not choose it from your app drawer, it has a alarm option on the screen and by touching anywhere on the screen it will dimm. I am now on ics nightly but I think honeycomb was the same way, correct me if im wrong.
edit* - i also just realized that if you hold on the screen anywhere it will dimm to a different format of clock, so if this doesnt work on honeycomb i know it works on ics so if you can live without bluetooth and a camera (if your on honeycomb) which are the only thing currently not working that this will work as you described you wanted

scsa20 said:
I go into the development section and turned on Keep Backlight On When Connected to USB then I use the standard clock, works perfect for me
Click to expand...
Click to collapse
Just do this.
Development settings on Android to prevent screen from sleeping while plugged in.
Screen dims when it hits your auto sleep time limit instead of cutting the screen off.

Any way to disable soft key lights on One S?

I have moved to the HTC One S from the Galaxy S2. One of the most annoying things of the S2 was the soft key lights when using the phone in the dark. I solved this by using the "Screen Filter" app from the Market. I have also seen that Samsung has put the option to disable the light on those buttons in the Settings menu.
Now, on the HTC One S, the problem is back. Screen Filter does not kill the light on the buttons (it says that this won't work on all phones...) and I can not find a setting to do this.
Is there a way to kill the lights on those buttons?

Am I the only one that finds this annoying? I find the phone impossible to use while in bed or in a dark lit environment...

jadajada said:
Am I the only one that finds this annoying? I find the phone impossible to use while in bed or in a dark lit environment...
Click to expand...
Click to collapse
yes

I'll be getting the ONE S tomorrow, but on my SGSII you can go into settings > display > touch key light duration. I'm not sure if the one s has it but hopefully that helps.

I know about the S2, I have one myself. I am not sure if this is a "samsung feature" or a stock ICS feature. If it is an ICS feature, then it should be possible to dim or turn off those lights on the ONE S also in one way or another? The best solution would be to switch them off permanently.
I have no use for those lights since I know where the three buttons are.
And the fact that they light up, full blast, and stay lit, when I watch movies via Mirage (Air Video client) in bed is just annoying at best.

jadajada said:
I know about the S2, I have one myself. I am not sure if this is a "samsung feature" or a stock ICS feature. If it is an ICS feature, then it should be possible to dim or turn off those lights on the ONE S also in one way or another? The best solution would be to switch them off permanently.
I have no use for those lights since I know where the three buttons are.
And the fact that they light up, full blast, and stay lit, when I watch movies via Mirage (Air Video client) in bed is just annoying at best.
Click to expand...
Click to collapse
Did anyone ever find a solution to this problem. I use my phone as an alarm clock, and now leave the display turned off as those pesky little lights on the buttons blaze away all night

What alarm clock do you use that the lights stay on? That doesnt make any sense. I use my phone as an alarm. Screen shuts off as normal and when the alert comes in it turns on like normal.
Sent from my HTC one sex

elracing21 said:
What alarm clock do you use that the lights stay on? That doesnt make any sense. I use my phone as an alarm. Screen shuts off as normal and when the alert comes in it turns on like normal.
Sent from my HTC one sex
Click to expand...
Click to collapse
Sorry, I'm maybe not explained it clearly. I use Gentle Alarm that has a night time display of the time. My old phone the button back lights (4) used to turn off. With the HOS they stay on and there seems to be no option to turn them off. There is only 3 of them of now on the HOS but they are quite bright. If the light is bright enough they turn off during the day but at night they blaze away regardless. I currently just turn the screen off and Gentle Alarm still works of course but with no time display. Not a big issue as only useful if you happen to wake in the night and wonder what time it was. I only ask because I wonder if I've missed an option somewhere. Screen Filter has the option to turn them off but does not work with the HOS.

I understand now. I didn't know people leave their displays on for alarm clock use. As far as I know there is no way to completely disable the capacitive buttons. Sorry bud.
Sent from my HTC one sex

You can turn off the button lights in LeeDroid's ROM. It's in the tweaks settings.

You could also manually set the brightness of the display just bright enough that the phone disables the softkey lights.
Edit: nvm. It only works while using auto brightness.
Sent from my HTC VLE_U using XDA

i would also like to know if anyone finds a fix i was watching a movie on my phone last night to keep it quiet and them lights satyed on all the time i also looked for the settings like they had on the sgs2 but no dice

I wrote a tasker task that will disable the lights on the capacitative buttons. You can use it to automatically disable the lights when in whichever app your want or set it up to have a toggle. I use both.
The task does require root. And Tasker, obviously.
If anyone else is interested I can export it and post it.

jayelbird said:
I wrote a tasker task that will disable the lights on the capacitative buttons. You can use it to automatically disable the lights when in whichever app your want or set it up to have a toggle. I use both.
The task does require root. And Tasker, obviously.
If anyone else is interested I can export it and post it.
Click to expand...
Click to collapse
I'm in
Sent from my Ville using xda premium

Main Task
Example Toggle Task
To use: ensure that you have root. If you have not already granted Tasker root access before, you will have to when using this task. Import at least the main task (called button light) into Tasker. To use it, either create your own task to reference it, or import the toggle task.
Using the toggle task: Just run the task (for example, create a shortcut to the task on your homepage), and select if you want the task on, off or on system default.
Using your own task: In your task, use the Perform Task action. Var1 should be either On, Off, or System. (For example, create a profile for MX Player, Enter action is Perform Task with var1 Off, and Exit Task is Perform Task with var2 system. This task can be downloaded here for you to edit from.)
All files are also attached.
Click Thanks if it works for you.

You can go to sys/class/leds/button-backlight/ then open the "brightness" file in a text editor and change "255" to "0" then save.

In essence, that is what the Tasker task does, but if you just change the value of that file, then Sense will just restore it as soon as it detects that the light values have changed. I couldn't get it to stick without root. The Tasker task also changes the permissions for that file, thus preventing Sense from changing it until you unlock the file again.

Perfect
Thanks jayelbird, your brilliant. The Tasker do the job very nice.
OT: can you make a task wake up volume?

The most that Tasker can do right now is detect if there was a volume change and wake the phone, although I can et you a profile for that if you want it.
Button remapping might be a better avenue to take. Try changing the codes for the button remapping.

Try changing the codes for the button remapping
Thanks.How can i change the code for the button remapping?

Touchkey backlight behavior

I've been digging into the "touchkey backlight issue" and would appreciate some help understanding how it worked (or didn't) on GB-based ROMs. If you are running GB (rather than "I remember..."), understanding how the proprietary Samsung code handled the backlight, both in auto- and manual-brightness mode, under a variety of screen timeouts, USB plugged, AC plugged, etc., would be great. Information like this can also help me guess where Samsung has their proprietary code, rather than wading through 150 MB of ROM.
Reports like,
The backlights go out after a couple seconds
Click to expand...
Click to collapse
aren't terribly helpful.
The backlights turn on when I tap the screen anywhere, then turn off after a second or two (it seems to vary from time to time), when I'm running on batttery, with auto-brightness on, and in normal indoor home lighting. They don't turn on with the same settings if I am outside.
Click to expand...
Click to collapse
or the like is much more helpful.
(I made that stuff up. I don't remember how they worked under GB.)
Oh, let me know which ROM you are running as well.
No promises, but knowing where we came from can help determine where we might go.
Thanks!
P.S. This is a common problem with Samsung phones -- You'd be amazed at the number of inquiries about the touchkey backlight.

I can check these later again a stock S4G I have still on GB, but on my flashed one with FB's AOKP using your brightness for the screen fixes, this is what I just tested.
-Turn Autobrightness off, screen sleep to 5 mins, brightness about 30%, backlights stay on for the whole 5 mins.
-Turn Autobrightness off, screen sleep to 5 mins, brightness about 100%, backlights stay on for the whole 5 mins.
Turn Autobrightness On, screen sleep to 5 mins, filtered/raw 34/34, backlights stay on for the whole 5 mins.
Turn Autobrightness On, screen sleep to 5 mins, filtered/raw 2000/2000, backlights go out as soon as the raw value hits past 150, your default to turn them off.
When I remove it from a bright light and the raw goes back down to below 50 though, the autobrightness does not dim the screen, I have to put it to sleep and wake it up to get it to actually drop the brightness..
Moving the phone between bright light and dim light, the buttons do go on and off corresponding to the 150, but the screen doesn't dim or go brighter.
If the buttons are off from being in bright light, and I press one, they go on and stay on and moving out and back into bright light, they seem to stay on most of the time.
So it seems your code for the autobrightness can turn the buttons on and off, by the 0 value for the correct RAW value. It's spotty though and the autobrightness doesn't adjust itself to the correct level until I sleep/wakeup again. I can have autobrightness on and move my phone from dark to light and the buttons go on and off by the brightness of the light but the screen doesn't.
I will check this same test against a stock GB and see what happens.

This is for gingerbread:
Sometimes the key lights don't turn on at all while using the keyboard, and even when you are pressing keys in the keyboard. It might not even be caused by the keyboard being out, maybe it's the way I hold my phone while I'm typing that causes the auto brightness to go down.
This doesn't occur all the time though. Also, sometimes it doesn't turn on at all even when touching the screen (maybe for a minute) then they turn back on.
It seems that the key lights have some situations where they decide to ignore touches and stay off, I'm still trying to figure out when this is. Again, it mostly happens when the keyboard is out. Maybe it has something to do with auto brightness. When toggling auto brightness on and off, the key lights immediately turn off and stay off for about 30 seconds. This makes me think that the soft key lights even on stock are buggy

Thanks getochkn; great report for ICS!
That pretty much agrees with what I am seeing on ICS and what I would expect from the code.
The buttons "don't play nice" with the Android world as it seems they turn themselves on when you touch them (probably hardware control), and the present TeamAcid ICS driver turns them on when it (re-)initializes. The Android world won't change the brightness of any of the "lights" if it thinks that the level is already set. For example, if it thinks the buttons are off, it won't try to turn them off again. I believe this is why with auto-brightness on the buttons sometimes won't turn off. I'm still wading through PowerManager service to understand how the code is trying to handle them when in "manual" brightness mode.
Definitely looking forward to your results for GB, though pisherthefisher's report that they seem "buggy" on "stock" for him suggests that Samsung might not have gotten it right even there.

Seems to be no way to fully disable them eh? Then we could just use the JB style nav bar like already in FB's AOKP which lets us set color, brightness, custom icon, etc but with the other buttons still working physically, lights on or not, it seems not worth it as you will still hit the sammy buttons, especially if the light is off but the buttons still physically work.

I can "hack" them off, but I'm trying to solve the problem more generally and in a way that keeps the TeamAcid framework able to easily track the CyanogenMod upstream. I might build a "Hefe Kernel Of Darkness" if I can't find something this week.
Posted from my SGS4G, thanks to Team Acid development

Ah. Might be an option, go all softkeys via the ROM instead.
I know OT, but any idea why the autobrightness doesn't seem to fully kick in sometimes either? I can be in the custom screen to view the raw values and see the numbers drop but not the screen brightness until i sleep/wakeup. The backlights will go on/off according to the raw value but not the screen brightness. lol.
Going to go see how my stock one works and I'll report back.

On the auto-brightness not seeming to work, you might want to check the auto-brightness thread in the dev section. I am guessing it might be related to the "Allow light decrease" and "Decrease hysteresis" settings.

jeffsf said:
On the auto-brightness not seeming to work, you might want to check the auto-brightness thread in the dev section. I am guessing it might be related to the "Allow light decrease" and "Decrease hysteresis" settings.
Click to expand...
Click to collapse
Thanks. I forgot the settings after reinstall.
On GB, the lights seem to go out at some value (no custom, can't tell) but do come back on when you press them and then seem to stay on randomly. lol.
FB's AOKP comes with BLN control which does seem to use the lights as an indicator light for lockscreen notifications, so they seem to be able to be controlled from that SW. Not sure if that helps or not?

Hefe kernel of darkness sounds awesome, it would be cool to use the sgs4g like a galaxy nexus

Setting the backlights to 0 on all light settings, the backlights go out, but as soon as you go to sleep, and wake up, the lights come back on and don't go out even though the custom panel shows the state of them at 0. Turning auto-brightness off/on then turns the lights off, so the state is not being restored at wake. Of course touching one of them turns them on and they stay on again unless i toggle off/on again.

Yes, right now driver resume turns on the backlights, but Android thinks they are already off, so it doesn't turn them off based on the auto-brightness settings. Touching the keys is similar, but it seems to be hardware that is turning them on.
Posted from my SGS4G, thanks to Team Acid development

Well I'll test a darkness kernel if you get one going. lol. Use the softkey feature in AOKP. I've already been playing with and have it setup, I just don't want to hit the sammy buttons which I brush sometimes by accident, nor have the lights come back on after wake up, so if can disable them fully in the kernel, that would be cool.

Hefe Kernel Of Darkness in Post #2 of the Hefe Kernel thread

jeffsf said:
Hefe Kernel Of Darkness in Post #2 of the Hefe Kernel thread
Click to expand...
Click to collapse
no wifi. lol. Doesn't even turn on.

Yeah, something is flaky. I'll look at it again tonight.
Posted from my SGS4G, thanks to Team Acid development

jeffsf said:
Yeah, something is flaky. I'll look at it again tonight.
Posted from my SGS4G, thanks to Team Acid development
Click to expand...
Click to collapse
Works good other than that.

Can the lights be disabled with the keys functional?
Sent from my SGH-T959V using xda app-developers app

m4127440 said:
Can the lights be disabled with the keys functional?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
The best we can do right is only have them turned on while pressed with the hefe kernel of darkness. Check out the hefe kernel thread in the development section, second post
Sent from my SGH-T959V using xda app-developers app

We?

[APP][Android 6+] Ambi-Turner - wake up ambient display

I've created an app that wakes ambient display when you take the phone out of your pocket or if you have the phone face down and turn it over. The app is in addition to Google's ambient display and does not change your lock screen in anyway. It can also set "pulses" of ambient display. The free version allows you to have it always pulse while charging.
I added a few other paid features for tilt or lift to unlock, wave to unlock, pulsing at an interval, and battery percentage display on the ambient display.
Please let me know if you have any suggestions or run into any problems. Thank you!
Check it out: https://play.google.com/store/apps/details?id=com.compass.ambiturner

Pulse means, as long as i have for exampel a unread whatsapp message, ambi is showing at the set pulse time?
Maybe ill test it on OP3 with CM14.1 running ... will report back!

MultiCulti said:
Pulse means, as long as i have for exampel a unread whatsapp message, ambi is showing at the set pulse time?
Maybe ill test it on OP3 with CM14.1 running ... will report back!
Click to expand...
Click to collapse
Correct. There is a filter for you to choose which apps can trigger a pulse. The pulse timeout is how long do you want the pulses to continue before it stops (to save battery). Pulse will temporarily pause when your phone goes into deep sleep. I could wake it up, but that's a much larger battery hit.
The other features seems to have little to now battery impact. Pulse is fine as long as the interval isn't set crazy low.
So far I've only personally tested it on stock Pixel XL.

ok, so far its working fine here!
Just the pulse isnt working (tried whatsapp and google messenger)
Love the idea off showing the battery, but its not that looking good :silly:
but i think, you just can manage this as "notification", or am i wrong?
anyways, good idea so far, will follow (bought it anyway) :laugh:

MultiCulti said:
ok, so far its working fine here!
Just the pulse isnt working (tried whatsapp and google messenger)
Love the idea off showing the battery, but its not that looking good :silly:
but i think, you just can manage this as "notification", or am i wrong?
anyways, good idea so far, will follow (bought it anyway) :laugh:
Click to expand...
Click to collapse
The battery level is a notification. I'll create a custom layout to improve the look in a future update.
The pulse is the least reliable feature. I'm still working out the kinks, but doze and deep sleep definitely are one problem. I'm testing various ways and will try to get it as consistent as possible.
Alarm Manager would work but it would drain battery.

Looks great! Just to confirm - you need to have a lock screen set up for it to work?

poczynek said:
Looks great! Just to confirm - you need to have a lock screen set up for it to work?
Click to expand...
Click to collapse
Yes, it works with androids Ambient Display. So if you have that and it's turned on it should work.

So I've done some limited testing with the app white listed from doze and so far it improves the responsiveness significantly. I don't know the battery impacts yet, but if it's not noticeable I'll add code to prompt users to white list it.
Other upcoming changes:
Advanced settings to adjust wait times for how long the phone has to be in your pocket or laying flat before a wake can occur.
A pulse option that initially pulses faster when a notification comes in, and progressively shows down until the timeout.
Possibly change in lock screen battery indicator appearance.
Filter on laying flat thresholds. I suspect the accelerometer incorrectly reports the phone tilted while it is laying flat on occasion.

New update posted.
I may have discovered what is causing the intermittent nature of wave to wake. I made some changes in how I'm using the proximity sensor so that should help. I'll have to wait and see after a day or so of use to see how consistent it is.
I also added an option to turn off the wake from pocket.
There's now a help screen with an email developer button and some troubleshooting hints. I've been getting a large number of 1 star reviews, and many of them are people who don't realize you need to have ambient display turned on and a lock screen set, so I included more info on that.
Oh, and the notification is now hidden unless you have the Battery Indicator selected!
If anyone is still having problems with tilt to wake please let me know. On my Pixel XL that has been working every time all day. There is sometimes a delay, but I think that's due to the aggressiveness of Android 7.1 putting the device into sleep.

Awesome app. I bought it mainly because of Wave To Wake, but for some reason it works two times on my Nexus 6 and then stops working until I turn my screen on and off again. Oh, and I've already whitelisted Ambi-Turner from the battery optimisation.
Also I would love if you could make Ambient Display work as soon as I turn the screen off, without having to wait for 10 or 3 seconds.
Thank you a lot for your hard work, I hope this can be fixed. Please contact me if I can help with anything!

Ygor Cortes said:
Awesome app. I bought it mainly because of Wave To Wake, but for some reason it works two times on my Nexus 6 and then stops working until I turn my screen on and off again. Oh, and I've already whitelisted Ambi-Turner from the battery optimisation.
Also I would love if you could make Ambient Display work as soon as I turn the screen off, without having to wait for 10 or 3 seconds.
Thank you a lot for your hard work, I hope this can be fixed. Please contact me if I can help with anything!
Click to expand...
Click to collapse
I'm trying to get wave to wake as consistent as possible. Did you update last night? Let me know if that helps it.
I'm actually working on some advanced settings to let you control those timeouts.

grokus said:
I'm trying to get wave to wake as consistent as possible. Did you update last night? Let me know if that helps it.
I'm actually working on some advanced settings to let you control those timeouts.
Click to expand...
Click to collapse
I'm testing it right now and it's still quite inconsistent. Though I never know if I'm waving too fast or too slow, you know? Maybe if there was a way to make it more sensitive? Thanks for the attention! ;D
Edit: just to be clear, Wave To Wake does only work two times, but I discovered that I don't actually need to turn the screen on for it to work, I can just move the device (then Ambient Display will turn on) and after that the Wave To Wake will work again (though still only two times). I believe it has something to do with the time after it's been awake or something like that.

Android Wear Issue
Ok...I love the app when its working and even bought the Pro. So worth it to me.
This morning I forgot my Android Wear watch (LG Urbane) at home and Ambi Turner was working perfectly. I had to run home at lunch, grabbed my watch, turned it on and now Ambi Turner isn't working.
Any thoughts how to get around this?

mschumacker said:
Ok...I love the app when its working and even bought the Pro. So worth it to me.
This morning I forgot my Android Wear watch (LG Urbane) at home and Ambi Turner was working perfectly. I had to run home at lunch, grabbed my watch, turned it on and now Ambi Turner isn't working.
Any thoughts how to get around this?
Click to expand...
Click to collapse
UPDATE: I turned off the 'Mute' for my watch and Ambi Turner started working again. Hmm...gotta thing this one through. Turning on Mute alerts my watch, but I also see them on Amber Display.

Ygor Cortes said:
I'm testing it right now and it's still quite inconsistent. Though I never know if I'm waving too fast or too slow, you know? Maybe if there was a way to make it more sensitive? Thanks for the attention! ;D
Edit: just to be clear, Wave To Wake does only work two times, but I discovered that I don't actually need to turn the screen on for it to work, I can just move the device (then Ambient Display will turn on) and after that the Wave To Wake will work again (though still only two times). I believe it has something to do with the time after it's been awake or something like that.
Click to expand...
Click to collapse
I'm adding some customization for the wave timeouts. I wish I could measure hand distance from phone but the pixel and nexus sensors don't have that granularity the way moto phones do.

mschumacker said:
UPDATE: I turned off the 'Mute' for my watch and Ambi Turner started working again. Hmm...gotta thing this one through. Turning on Mute alerts my watch, but I also see them on Amber Display.
Click to expand...
Click to collapse
Hmm that's strange. I'm using a garmin fitness watch that has notifications and haven't seen anything like that. Does your watch somehow mute notifications on your phone so that only the watch displays them?

grokus said:
Hmm that's strange. I'm using a garmin fitness watch that has notifications and haven't seen anything like that. Does your watch somehow mute notifications on your phone so that only the watch displays them?
Click to expand...
Click to collapse
Yes...there is a setting in Android Watch (Silence phone while wearing watch ) in the new version. It used to be 'Mute calls and notifications'. Its actually very handy so that when I'm in a meeting, I just get a vibration on my watch instead of my phone making any noise. Add the 'Feel the Wear' app where you can customize the vibration pattern per app...just a great combo.
EDIT: Since I just got a new version of Android Watch, it seems I can turn on the Silence option and the AmbiTurner, wake on wave, is working! Woo HOO!

Made tons of improvements. Tilt to wake should be extremely reliable now. There is also a lift to wake option. I reduced the speed you need to wave, so it should be much easier to trigger now. I also added an option to always pulse while charging.
Let me know how it works!
I had taken a break from updating it because I became a father but I have a little spare time now.

grokus said:
Made tons of improvements. Tilt to wake should be extremely reliable now. There is also a lift to wake option. I reduced the speed you need to wave, so it should be much easier to trigger now. I also added an option to always pulse while charging.
Let me know how it works!
I had taken a break from updating it because I became a father but I have a little spare time now.
Click to expand...
Click to collapse
@grokus is this app still being developed?
Sent from my LG-H990 using XDA Labs