I have the screen set to always on (no time out) when I have it in the car, it stays on fine while listening to music or if it just sitting there doing nothing, but no matter if I get a call or I make a call -- the screen will always turn off after a couple seconds even though the screen is set to always stay on, also as soon as the call ends -- the phone automatically locks and I have to log in / unlock it every time. I know on the old Froyo ROMs it would stay on if I had it set to always on -- didn't matter a call or not, it stayed on like it is supposed to do and it did not automatically lock either. I am on the Weapon 3.0ROM and I am using the same widgetsoid app as the the switching mechanism for the "always on" screen setting in a widget on one of the home screens. I have checked the widgetsoid settings and there is no definition between call settings and normal data for the screen time out. Under settings in the main menu, there is no toggle to enable/disable the proximity sensor either, but since the phone face has nothing close to it when it is mounted in the car (like it would be if you had it up to your ear), I don't think that this is the proper setting to manipulate. I really believe that this is a timing setting, and I am wondering if it is separate setting that can be changed or linked to the normal screen time out settings.
Is there a way to stop the screen from timing out on the Weapon3.0 Rom during phone calls and then automatically locking the phone when the call ends? its getting a bit annoying and any help would be appreciated.
Am I really the only one experienceing this?
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
crockashat said:
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
Click to expand...
Click to collapse
I think that is an unwanted "feature" of the 2.3.3 Gingerbread rom. I am not sure of anyway around it without changing to a rom that is not 2.3.3 based.
Has anyone had any issues using either Sleep as Android or Sleepbot? The screen never fully turns off because the accelerometers don't function with the screen off. I'm concerned that leaving the screen on for hours on end will cause pretty substantial burn-in.
tekhna said:
Has anyone had any issues using either Sleep as Android or Sleepbot? The screen never fully turns off because the accelerometers don't function with the screen off. I'm concerned that leaving the screen on for hours on end will cause pretty substantial burn-in.
Click to expand...
Click to collapse
Hey there, I actually made SleepBot and we have an option called "Screen Off Tracking" in the Settings which is supported for newer devices like the S3 or Nexus. Motion and sound tracking will still work even if you turn the screen off, but I recommend trying it out for 3-4 minutes first to make sure.
We've been testing on an LG Optimus (one of the older models that doesn't support screen-off tracking and nothing like burn happens. We dim the screen to all black within 10 seconds of tracking in any case. Email me at [email protected] if you have other questions.
I was concerned about burn-in as well and I use Sleep As Android. My solution was to install Dock Clock. It has an option to make the clock move around on the screen which will eliminate any burn-in and it is very easy to read at night.
janenyc said:
Hey there, I actually made SleepBot and we have an option called "Screen Off Tracking" in the Settings which is supported for newer devices like the S3 or Nexus. Motion and sound tracking will still work even if you turn the screen off, but I recommend trying it out for 3-4 minutes first to make sure.
We've been testing on an LG Optimus (one of the older models that doesn't support screen-off tracking and nothing like burn happens. We dim the screen to all black within 10 seconds of tracking in any case. Email me at [email protected] if you have other questions.
Click to expand...
Click to collapse
So, how about development of sleepbot cause the soft is great
Not sure if this is a Nexus5 or Android issue ...
Not sure if this is because I'm moving from an AMOLED to a IPS LCD ...
but I find the Auto-Brightness less of a function and more of a roller coaster ride.
- At home, in a well lit environment, the phone defaults to max brightness, which doesn't seem correct.
- In a dark room, upon wake of the phone, it correctly selects a lower brightness, yet will randomly ping up to max brightness, then settle back down.
The screen on the Nexus5 is absolutely gorgeous, but it just can't seem to select and lock onto the proper brightness level with respect to ambient light.
Is anyone else experiencing auto-brightness wonky-ness? Are there any potential fixes?
Everyone AFAIK suffers from it on nexus 5.
I have a horrible feeling it's a hardware fault, as none of the other Google devices on kitkat have this issue.
yeah the auto brightness seems to be too aggressive, but i'm sure custom roms will have the ability to tweak the auto brightness settings. i think even gravity box has some tweaks for the brightness
If you download Android Sensor Box, you can check the Light sensors. I think it may be bugged with Halogen lighting (correct me if I'm wrong). My home is ~ 18 years old, and we have some bulbs that have not been changed yet (yellow). Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings. I'm not sure if it's a rom issue or hardware issue, but my cousin also has a N5 and his worked fine. I tried flashing a new rom and mine still acted up fresh after boot (1st app installed after fresh flash was Android Sensor Box to test).
As a rule I don't use auto brightness. Just get something like lux or install exposed and enable a mod to let you adjust it by sliding your finger across the notification n shade. Easier and faster.
Sent from my Nexus 5 using Tapatalk
I find that autobrightness will auto-turn on, even when i don't want it to.
There is something funky about it, I can either make the phone too dark (using lux) or too bright (using default settings)
I'm still not happy.
Tried Lux, tried adjusting the brightness tables via Gravity Box, used Twilight (to dim at night), no matter what, N5 just wants to be at full brightness all the time!
I had my Nexus 5 in the cinema the other day. The phone was sat in the cup holder by the chair for the most part of an hour when I quickly replied to a text. On turning the screen on it was on full brightness and what's worst is it took around 10 seconds for it to go down. There is definitely something not quite right with it.
Aria807 said:
Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings.
Click to expand...
Click to collapse
Hi, I have been experiencing this as well, so I attempted to fix this at ROM level. The solution requires Xposed framework, so it works only on rooted devices (related discussion).
Hi everyone
I have had my OPO for quite some time and I absolutely love it.
Bootloader is unlocked, TWRP installed, MultiRom installed, CM12.1 newest nightly installed using newest AK kernel. Using Xposed arm22 and a lot of lovely modules, even some that are meant to save power.
Okay, now for the problem:
I have started noticing it turning on the screen in a very dim light, while the phone is "locked" for quite some time. It is unresponsive to touches until I press "power button" at which it actually turns on the screen and it lights up to a "normal" brightness setting. I have no idea why it does this. I've looked around in the settings to see if it is a feature that can be turned on or off but that doesn't seem to be the case. I usually notice it when the phone is charging, but it also happens when it isn't. On a regular day I will notice it happen 2-3 times.
I know there is a feature that dimly turns on the screen when receiving notifications, but I have that turned off. Also it doesn't happen when not receiving notifications. I tried browsing for users with similar problems, but found no posts about this.
Does anyone have a clue why it does that?
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