Related
If any of you other users out there feel that the whites on this thing are too awesome for super late at night like I do, I found a app when searching for a f.lux type alternative for android. I have been using this app to help ease the stress on my eye late at night. I dont know about the techical side of what it does, or any of the jargon involved, but it applies a filter of sorts to dim the screen further than what the phone allows. I been using it a lot lately and figure I would share with you guys. If anyone has any recommendations for other similar apps, please share.
Tl:dr
Screen Filter
https://play.google.com/store/apps/details?id=com.haxor
Sent from my SCH-I535 using Tapatalk 2
enomele said:
If any of you other users out there feel that the whites on this thing are too awesome for super late at night like I do, I found a app when searching for a f.lux type alternative for android. I have been using this app to help ease the stress on my eye late at night. I dont know about the techical side of what it does, or any of the jargon involved, but it applies a filter of sorts to dim the screen further than what the phone allows. I been using it a lot lately and figure I would share with you guys. If anyone has any recommendations for other similar apps, please share.
Tl:dr
Screen Filter
https://play.google.com/store/apps/details?id=com.haxor
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Or just turn on "Background Color" in Power Saving Settings.
Or if you want the screen brightness itself to be lower than what most ROMs allow, you can use this app called RootDim. It worked amazing on my xoom, not sure if it works on the SGSIII yet..
It requires root though..
yosterwp said:
Or if you want the screen brightness itself to be lower than what most ROMs allow, you can use this app called RootDim. It worked amazing on my xoom, not sure if it works on the SGSIII yet..
It requires root though..
Click to expand...
Click to collapse
Screen filter does the same and doesn't require root. On our AMOLED screens this can save battery.
Also you can turn off those damn capacitive key lights by going to Settings>display>"touch Key light duration"> Always off.
I can confirm that Root dim does work for the SGS3 I use it on my phone.
Current~Samsung Galaxy S3 SynergyRom 1.3 & Imo's Lean Kernel v12 Oc'd @ 1.9ghz
~Acer Iconia A500 Stock
Past~Droid X Gummy ICS 1.2
Lux is an amazing auto brightness app and setting it up for your tastes is incredibly simple.
Go out in the sun and turn brightness up all the way using the app then "link" that setting, go in complete darkness and set it to your taste and link it, then indoor lighting, set it, link it. It then uses just those 3 settings to create a smooth graph of brightness values that are all perfect. You can have as many links as you want but i find the less settings you put in that app the better.
I tried all the suggested ones in here btw.
Sent from my SCH-I535 using xda app-developers app
I've tried and really like Lux (in fact I'm considering purchasing it soon) but I've noticed two issues. First is that sometimes it will not refresh itself and I have to open up the lux dash to get the brightness to change. It doesn't happen often, but it happens often enough to be annoying, and I have it set to automatically.
Also, (and this may simply be an issue with the S3 and not lux itself) but sometimes I will be in a decently lit room and be at 1 lux, while lights out is 0. Not a lot of variance unless it's really bright outside. Have you found anyway to increase the light sensors sensitivity?
noingwhat said:
I've tried and really like Lux (in fact I'm considering purchasing it soon) but I've noticed two issues. First is that sometimes it will not refresh itself and I have to open up the lux dash to get the brightness to change. It doesn't happen often, but it happens often enough to be annoying, and I have it set to automatically.
Also, (and this may simply be an issue with the S3 and not lux itself) but sometimes I will be in a decently lit room and be at 1 lux, while lights out is 0. Not a lot of variance unless it's really bright outside. Have you found anyway to increase the light sensors sensitivity?
Click to expand...
Click to collapse
Try setting it to be always active in the task bar, that prevents it from being killed. Also try setting it to not use raw values for light sensor readings, this gives you a simple scale of 0-10 for readings and total darkness always reads as 0.
Edit: oops reread your post. That's weird that it is reading indoor light at 1. I usually get around 2 or 3. I used to have a screen protector on that covered the light sensor and that put it all over the place. Maybe that is what's causing it?
noingwhat said:
I've tried and really like Lux (in fact I'm considering purchasing it soon) but I've noticed two issues. First is that sometimes it will not refresh itself and I have to open up the lux dash to get the brightness to change. It doesn't happen often, but it happens often enough to be annoying, and I have it set to automatically.
Click to expand...
Click to collapse
I noticed the same behavior with the free version. In my case, the lowest value the HTC Desire S can reach with its default Android auto brightness is in fact about 15%.
In LUX settings you can configure the "0" value to be lower and "bypass" the freeware limitation (you can't configure sub-zero levels in the free version). This will work when you test it in the dashboard, but during regular use the light level never goes below the 15% limit already set by the OS.
What I did was purchase the full version (to get astronomer mode along with all the settings unlocked) so I was able to leave the 0 level at its default 15% but link some light intensity values to sub-zero percentages. Guess what? It works great! Once you go into a very dark room, the display dims as far as you set it to.
Another problem with the free version was that a few times I unlocked the phone outside in full sunlight and LUX did not increase the brightness. It appeared almost completely black because the light level was at about 15-25% (the same level it would be inside a low lit room).
Again, with the full version I did not notice this problem (I've used the free version for 1 day and the paid version for 1 day but running tests in different light levels inside and outside).
It's like the free version is a bit buggy on purpose, and I remember uninstalling LUX free about 2 months because of this; I was thinking that if the free version does not work OK, I shouldn't buy the full version. Apparently this is not the case (touch wood).
Just for the record, it's on "dynamically adjust".
noingwhat said:
Also, (and this may simply be an issue with the S3 and not lux itself) but sometimes I will be in a decently lit room and be at 1 lux, while lights out is 0. Not a lot of variance unless it's really bright outside. Have you found anyway to increase the light sensors sensitivity?
Click to expand...
Click to collapse
If the display is a bit dirty (oily, dusty, etc) around the light sensor, you can try to clean it. If this is not the case, open the dashboard, let it determine the light level or hit "auto" a few times and make sure the reading is correct. Then just slide your finger along the yellow line to find the appropriate brightness level and long press the chain to link. Go to a brighter lit room then go back to the first room and see how LUX behaves. Also lock/unlock the phone a few times and see how it goes.
If you still have problems running LUX, disable it and check the default Android auto brightness to make sure it's not a sensor issue.
LUX also has the possibility to set the response delay under Settings -> Advanced -> Developer Settings (the last to just on the bottom, but for this you would need to buy the full version.
Inginerul said:
If the display is a bit dirty (oily, dusty, etc) around the light sensor, you can try to clean it. If this is not the case, open the dashboard, let it determine the light level or hit "auto" a few times and make sure the reading is correct. Then just slide your finger along the yellow line to find the appropriate brightness level and long press the chain to link. Go to a brighter lit room then go back to the first room and see how LUX behaves. Also lock/unlock the phone a few times and see how it goes.
If you still have problems running LUX, disable it and check the default Android auto brightness to make sure it's not a sensor issue.
LUX also has the possibility to set the response delay under Settings -> Advanced -> Developer Settings (the last to just on the bottom, but for this you would need to buy the full version.
Click to expand...
Click to collapse
Thanks, but I think it is more of an issue of the sensor not being sensitive enough. I'm not sure if this is anything you can change in lux or if it would have to be edited in the kernel (or if it is fault of the hardware) but I just feel like the sensor doesn't go down low enough. As I said, I can get down to 1 or 0 in a decently lit room, and yes I have tried cleaning the screen. It's not like it jumps around or anything so it's not like I would notice anything in default auto brightness, it's just that it doesn't seem to be sensitive enough.
Screen filter is great!! I use as well!!!
Sent from my SCH-I535 using Tapatalk 2
Well for my Desire S, the lowest light level that the sensor can read is 160 lux (raw value). You can try and set LUX to use raw values because this is more accurate in my oppinion.
Another +1 for Screen filter here
Does anyone know how to use "luma" values for automatic adjustment in Lux instead of "lux" values?
noingwhat said:
Does anyone know how to use "luma" values for automatic adjustment in Lux instead of "lux" values?
Click to expand...
Click to collapse
What I have noticed on my phone is that "luma" readings are taken from the front facing camera, while "lux" readings are taken from the ambient light sensor (you can chose which one to use in the settings).
I suppose the front facing camera uses more battery than the light sensor; it also appears to be more sensitive because it can read more light levels.
Inginerul said:
What I have noticed on my phone is that "luma" readings are taken from the front facing camera, while "lux" readings are taken from the ambient light sensor (you can chose which one to use in the settings).
I suppose the front facing camera uses more battery than the light sensor; it also appears to be more sensitive because it can read more light levels.
Click to expand...
Click to collapse
I guess so. Thanks! But doesn't that kinda defeat the whole purpose of Lux? Because you can't use automatic mode with the camera(s).... so then what's it good for?
Well even if you don't have an ambient light sensor, you can still use the camera to check the light level when you unlock the phone and let LUX adjust the brightness level. Of course it's not dynamic but it's still better than having the brightness at 50% the whole time or changing brightness levels through a widget..
Sony xperia Z3 Dual D6633 Android 5.0.2 Build 23.1.1.E.0.1
Hi there,
Upgraded my Z3 to lollipop last week and, despite the fact that the upgrade itself was flawless, I think I went from a device that used to work like a charm to one full of annoyances.
On day #1, noticed the batt drain skyrocket. 3h after disconnecting it, it was at 68%, half way through the morning. WTF? was my first thought. On a typical day on kitkat, I was able to end the day at 40% at least.
The second thing I´ve noticed was the phone app. It starts giving me errors, saying that the "network could not be reached" when I try to dial a number. If I insist for 4, 5 more times, it crashes. Dialing is only possible again if I reset the phone.
The third thing is the lock screen. It seems that lollipop has a drop down menu that makes it possible to enable/disable lots of things, like communications and even setting the phone in airplane mode. Imho that´s a huge liability / security risk and it appears that there is no way around that.
Still about the lock screen, it seems to have a bug: if you have any activesync account setup, not notifications will show up, no matter how you configure it (to show all or hide sensitive content).
So, I had only one thing to do, after reading forums etc... factory reseting it.
Surprise! All problems are still there.
Does any1 have any tips on those?
Thanks in advance.
There will be a widget on one of the screens which keeps refreshing itself and I found that to be the battery killer on my 6603.
Did you use any specific app to pinpoint the culprit?
1. It is possible that the battery levels are calibrating and will be imprecise for a while after the update, using the device normally for a couple of days will fix it, or at least this is what I observed in many phones I owned.
2. This is very weird and I can't help you with. If not even factory reset did help you may have some corrupted data on one of your contacts maybe? Try to make a thread about this issue on the Sony forum.
3. I noticed that as well, but even on pervious versions you could turn off the phone so I don't think it changes anything. Make sure to disable the multi user options that would allowanyone to add a new user from the lock screen.
4. Another weird thing, I use exchange accounts on my phone and I don't have any problem on mine. See point 2.
Under
settings>sound and notifications>when device is locked
Set to hide sensitive notification content or don't show notification content at all.
This should fix lock screen displaying email notifications from your exchange account.
Also, unlock phone, pull down notifications, pull down again to reveal quick settings, hit the edit button (pencil) and remove icons but clicking and holding and drawing them to the top. Unfortunately this removes them even when phone is unlocked but of your worried about unauthorised toggling of things on off its the best you can do I think.
As for battery drain, check the battery usage in
Settings>power management
Make sure stamina mode is on, toggle it off then on to make sure.
Select battery usage and check to see if any apps are using more than they should. Make sure brightness is set low but enable adaptive brightness under display settings.
ozzy lion said:
Under
settings>sound and notifications>when device is locked
Set to hide sensitive notification content or don't show notification content at all.
This should fix lock screen displaying email notifications from your exchange account.
Also, unlock phone, pull down notifications, pull down again to reveal quick settings, hit the edit button (pencil) and remove icons but clicking and holding and drawing them to the top. Unfortunately this removes them even when phone is unlocked but of your worried about unauthorised toggling of things on off its the best you can do I think.
As for battery drain, check the battery usage in
Settings>power management
Make sure stamina mode is on, toggle it off then on to make sure.
Select battery usage and check to see if any apps are using more than they should. Make sure brightness is set low but enable adaptive brightness under display settings.
Click to expand...
Click to collapse
That's not a smartphone anymore, with all functions shut down and brightness low.
This phone has the best screen, use it at least 50% brightness.
I have no issues with the brightness down. It bumps up nicely in brighter conditions and will even max out in daylight. If I ever need it brighter then it's easy to boost temporarily. It's a small price to pay for nearly 24 hours of battery with 5 hours screen on time.
I never mentioned shutting down functions. The only thing I mentioned removing was the toggles that concerned the op on the quick settings. Removing mobile data and aeroplane mode from quick settings hardly cripples the device, I never use these anyway.
I don't think it very useful that there's not more customisation available here such as a complete set of separate lockscreen settings. But if all you can do is comprise then what else can you suggest?
I don't think unlocking the bootloader and installing a custom ROM is something the op wants to do.
ozzy lion said:
I have no issues with the brightness down. It bumps up nicely in brighter conditions and will even max out in daylight. If I ever need it brighter then it's easy to boost temporarily. It's a small price to pay for nearly 24 hours of battery with 5 hours screen on time.
I never mentioned shutting down functions. The only thing I mentioned removing was the toggles that concerned the op on the quick settings. Removing mobile data and aeroplane mode from quick settings hardly cripples the device, I never use these anyway.
I don't think it very useful that there's not more customisation available here such as a complete set of separate lockscreen settings. But if all you can do is comprise then what else can you suggest?
I don't think unlocking the bootloader and installing a custom ROM is something the op wants to do.
Click to expand...
Click to collapse
You said stamina.
Stamina means already some functions off.
Update:
1. Batt drain
Remains without an explanation. My daily use profile is basically the same as before the update. 3PM and I am at 28%, with stamina on. I can´t recall a day, running kitkat, that I would hit the charger at night with 28% of batt remaining (and I still have 4h to go). It was always on 40% ish. GSAM is reporting that 47% of the batt drain is caused by apps and, from that, 30% is represented by android core apps + android system + kernel. I might be wrong, but I think it is related to reindexing, contact + agenda sync etc and it will probably get lower eventually (I hope!)
2. Phone App giving errors
I think I have isolated the problem. It seems to be caused by TrueCaller.
3. Lock screen
Regarding the drop down menu, It is clear now that what I think is a problem is, in fact, by design and there is no way around it without rooting. But regarding the notifications, I just removed both activesync accounts and I started getting notifications in the lock screen again. So, my guess is that there is a policy of some sort that is being interpreted by the phone as it should hide all notifications from the lock screen.
In fact, there are lots of things that got blocked / disabled because of those policies. Here is a list of things that were disabled and now appear to be working again, after the removal of the activesync accounts:
. notifications are showing again in the lock screen;
. smart lock;
. screen lock options (none, swipe, pattern);
note: I thought that I would be able to enable services in Accessibility, like LastPass or App Advisor by Norton, but it still does not work (I try to enable any of them, but pressing "ok" on the warning dialog does nothing and the only option working is "cancel").
Thinking about resetting it again...
Hi, if problems are persistant you can always downgrad software at KitKat by using FlashTool and wait Lollipop 5.1 (5.1 will probably solve many problems).
StealthNet said:
Update:
1. Batt drain
Remains without an explanation. My daily use profile is basically the same as before the update. 3PM and I am at 28%, with stamina on. I can´t recall a day, running kitkat, that I would hit the charger at night with 28% of batt remaining (and I still have 4h to go). It was always on 40% ish. GSAM is reporting that 47% of the batt drain is caused by apps and, from that, 30% is represented by android core apps + android system + kernel. I might be wrong, but I think it is related to reindexing, contact + agenda sync etc and it will probably get lower eventually (I hope!)
2. Phone App giving errors
I think I have isolated the problem. It seems to be caused by TrueCaller.
3. Lock screen
Regarding the drop down menu, It is clear now that what I think is a problem is, in fact, by design and there is no way around it without rooting. But regarding the notifications, I just removed both activesync accounts and I started getting notifications in the lock screen again. So, my guess is that there is a policy of some sort that is being interpreted by the phone as it should hide all notifications from the lock screen.
In fact, there are lots of things that got blocked / disabled because of those policies. Here is a list of things that were disabled and now appear to be working again, after the removal of the activesync accounts:
. notifications are showing again in the lock screen;
. smart lock;
. screen lock options (none, swipe, pattern);
note: I thought that I would be able to enable services in Accessibility, like LastPass or App Advisor by Norton, but it still does not work (I try to enable any of them, but pressing "ok" on the warning dialog does nothing and the only option working is "cancel").
Thinking about resetting it again...
Click to expand...
Click to collapse
A new firmware version has dropped for the Z3 which I think fixes your issues with notifications.
I received it OTA yesterday, I'm running the Balkans customisation.
Thank you for the tip! I hope it does! Will keep it posted here just for the reference. I am starting to feel other "symptoms" as well, like bluetooth instability (you pair a device and it stops working, have to pair again).
.
Just hit another weird thing.
I am not being able to create a new vpn connection. I am trying to use the PureVPN and IPVanish client software, but when I try to setup the conection, I receive a disclaimer, saying that my traffic might be monitored, with a "CANCEL" and "OK" options. The OK doesn´t work, only "CANCEL".
My device is encrypted and I have also noticed that I am not able to decrypt it.
Also, If I go to Accessibility and try to enable a service, the same thing happens: a disclaimer appears, saying that the service might observe my actions, with a "CANCEL" and "OK" options. The OK doesn´t work, only "CANCEL".
Any ideas?
Ok, just a quick fup: the ability to create VPNs from apps is disabled if you encrypt the phone. It seems that if you create if before encrypting, it won´t be disabled; but you wont be able to create a new vpn from an app downloaded, after encryption.
Regarding the Accessibility > Services, after a *lot* of research, I have found that Twilight was the culprit. For the reference:
https://code.google.com/p/android/issues/detail?id=79637
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
Face unlock currently requires a double tap, which is annoying because it doesn't work half the time
Even though they are trying to fix this in the next update, a better implementation would be when you raise the phone, it shows the lock screen (not ambient display screen), and simultaneously turns on the front camera to face unlock your phone
Gravity screen can do this, but requires a heavy wakelock to do so. Using the same 'raise to wake' method as ambient display [which seems to work without a heavy wakelock], but then showing the lock screen instead of ambient display, should achieve this
I would LOVE this feature, it would be a complete game changer!!
I use gravity screen and don't lose much battery
Use the power button since it's more reliable anyways ?
Bradl79 said:
I use gravity screen and don't lose much battery
Click to expand...
Click to collapse
There's still a fair amount of battery loss. Oneplus raise to wake seems to be able to do the same action without any battery loss
This was so fine on Op5 and 5T. Open Beta, of course!
Update: I've installed the wave up app. It basically wakes the phone when proximity sensor is uncovered
So when I take the phone out of my pocket, it authenticates my face automatically and unlocks, in a split second. I don't need to touch anything
Similarly if I keep my phone face down on a desk (not ideal), when I flip it over to look at it, it unlocks.
No messing around with d2tw which is more like quadruple tap to wake since this functionality is broken
3473 said:
Update: I've installed the wave up app. It basically wakes the phone when proximity sensor is uncovered
So when I take the phone out of my pocket, it authenticates my face automatically and unlocks, in a split second. I don't need to touch anything
Similarly if I keep my phone face down on a desk (not ideal), when I flip it over to look at it, it unlocks.
No messing around with d2tw which is more like quadruple tap to wake since this functionality is broken
Click to expand...
Click to collapse
Hi i use the original flip case from OP and as soon as i open my case door it unlocks witch is very easy and convenient.
Shall check with tasker.
Update: could not succeed.
I face no trouble in dt2w it wakes as it's intended to and unlocks with face within a split second, face unlock has become slower since the 5.1.9 and in dp3 but still fast enough
If my hand is dirty i just say Hey or Ok google.
Agree. it would be a great thing
Hi!
I would like something like this https://forum.xda-developers.com/t/...ness-fix-torch-light-not-photo-flash.3872858/ for my Xperia 5 II.
Or if there is a setting for it. I have read on some webpages that maybe you could boost it in settings. This site https://smartandroid.fr/en/comment-allumer-la-lampe-torche-de-son-sony-xperia-5-2/ is about "Xperia 5" (not "Xperia 5 II") and say:
Slide the notification bar down
Go to the settings shortcut page on which your » Lamp »
Rather than clicking on the logo to light it, click on the text: » Lamp ", In this way you will access the torch settings of your Sony Xperia 5
You can now move the slider to manage the intensity of your flash. Namely that the device will save the setting and that it will have this intensity during the next ignition
I cant find that setting on my Xperia 5 II.
I have also tried this:
I go to Settings
There, at the top, I search for "Flash"
Now I see the setting "Flashlight", but nothing happens what I try to choose it.
Is there any magic out there to turn up the light?
Hi raffe,
I'm glad you posted this as I was looking to ask this question myself. The flashlight is really dim compared to my old phone so it would be great to turn up the brightness (lumens).
I also have no response when I look at settings and search torch. And no way to find other options for this feature. I even looked on Developer Tools.
Hopefully someone can help....?
Maybe the problem is, there is only one led diode..
Agree the "torch" is incredibly woeful, worst I've seen to be honest.
if you make a photo then you see that the led can be pretty bright even brighter than everyother phone I've had. Problem is that sony sets it low to allow it to go on for couple of hours winthout overheating.
I'm looking into it myself, if I find anything then I'll let you guys know
So it's me again. I have a solution but it requires root
Release v1.4.6 · BRoy98/GodlyTorch
Merge pull request #2 from TheDorkKnightRises/patch Fix LED file path for OnePlus One (bacon), proper device names for OP Merge pull request #3 from TheDorkKnightRises/patch Fix default double-...
github.com
Download this app and select device google pixel 2 it allows you to control the torch brightness
But be careful and don't burn your finger by setting it to 100% max bright like me hah. The 10% is normal brightness 20% is brighter than every other device and 30% is enough for myself
Qbus2002 said:
So it's me again. I have a solution but it requires root
Release v1.4.6 · BRoy98/GodlyTorch
Merge pull request #2 from TheDorkKnightRises/patch Fix LED file path for OnePlus One (bacon), proper device names for OP Merge pull request #3 from TheDorkKnightRises/patch Fix default double-...
github.com
Download this app and select device google pixel 2 it allows you to control the torch brightness
But be careful and don't burn your finger by setting it to 100% max bright like me hah. The 10% is normal brightness 20% is brighter than every other device and 30% is enough for myself
Click to expand...
Click to collapse
Thanks! That worked well
Wish there was a solution without root.
Qbus2002 said:
So it's me again. I have a solution but it requires root
Release v1.4.6 · BRoy98/GodlyTorch
Merge pull request #2 from TheDorkKnightRises/patch Fix LED file path for OnePlus One (bacon), proper device names for OP Merge pull request #3 from TheDorkKnightRises/patch Fix default double-...
github.com
Download this app and select device google pixel 2 it allows you to control the torch brightness
But be careful and don't burn your finger by setting it to 100% max bright like me hah. The 10% is normal brightness 20% is brighter than every other device and 30% is enough for myself
Click to expand...
Click to collapse
Good find! I only wish there were an easier way to toggle flashlight on/off to a preset intensity. The app doesn't provide a shortcut.
CazeW said:
Wish there was a solution without root.
Click to expand...
Click to collapse
The brightness setting may be hidden. On my Samsung simply long pressing the flashlight icon toggle takes you to the brightness control.
It was purely by accident that I discovered it as that's the only way to access it.
I agree that root shouldn't be required for such a simple thing.
Crap it
homerlovesbeer said:
I agree that root shouldn't be required for such a simple thing.
Crap it
Click to expand...
Click to collapse
It's probably buried in the settings or a 3rd party flashlight app can be used to access the brightness controls.
I would use the former rather than the latter...
blackhawk said:
It's probably buried in the settings or a 3rd party flashlight app can be used to access the brightness controls.
I would use the former rather than the latter...
Click to expand...
Click to collapse
If it's buried then it's buried so deep that it doesn't exist.
CazeW said:
If it's buried then it's buried so deep that it doesn't exist.
Click to expand...
Click to collapse
With Samsung there's no rythm or reason; double tapping or long pressing to access unindicted drop down menus. They are far and few in between so finding one tends to be a shock.
Another reason I seldom upgrade the firmware.
Maybe Sony is more sane but don't count on it.
Play with it...
I had to un-root the phone. When I rooted, the one app that could change the light intensity worked, but three other apps (financial and banking) said they would not start on a rooted phone and I never could get past that. Back to square 1 ;-(
Does anyone know the current version of an app like this? The application works well enough. But the problem is that two flash leds don't work at the same time. It lights up white or yellow alone, but both do not work at the same time. I have a Xiaomi Mi 9 device and I find the flash led running in the developer test interface of the device and the flash led running from the normal interface does not find a difference in lighting twice or three times.
raffe said:
Hi!
I would like something like this https://forum.xda-developers.com/t/...ness-fix-torch-light-not-photo-flash.3872858/ for my Xperia 5 II.
Or if there is a setting for it. I have read on some webpages that maybe you could boost it in settings. This site https://smartandroid.fr/en/comment-allumer-la-lampe-torche-de-son-sony-xperia-5-2/ is about "Xperia 5" (not "Xperia 5 II") and say:
Slide the notification bar down
Go to the settings shortcut page on which your » Lamp »
Rather than clicking on the logo to light it, click on the text: » Lamp ", In this way you will access the torch settings of your Sony Xperia 5
You can now move the slider to manage the intensity of your flash. Namely that the device will save the setting and that it will have this intensity during the next ignition
I cant find that setting on my Xperia 5 II.
I have also tried this:
I go to Settings
There, at the top, I search for "Flash"
Now I see the setting "Flashlight", but nothing happens what I try to choose it.
Is there any magic out there to turn up the light?
Click to expand...
Click to collapse
any help for galaxy a8 2018 ?? i have a problem Torchlight Intensity Control