Related
Hi all
Does anyone know if there is a way to control the length of time that the phone vibrates for? I rarely use my phone with the sound on (meetings etc.) and I realise that it is easy to recognise the difference between an incoming phone call and a notification by the length (and repeat) of the vibration going on in the phone's holster....
The notification vibrate seems to go on for about 5 seconds, whereas the fone ringing vibrate is much shorter and repeats at reasonable intervals.
Is it possible to modify this so that it does short pulses instead of zzzzzzzzzzzzzzzzzzzzzzzzz!! I don't know what the battery consumption is like if one would receive say 30 notifications per day as opposed to just a few. It feels like a reasonably serious motor that is turning for this vibration.
I had the same thoughts, but little research as I am struggling with more serious issues of my TyTN...
Registry does not seem to have anything concerning vibration length.
It would be surely nice to control vibrations... some much less complex devices have such a feature from ages
Vibrate
Hi Rich,
This has been my number one bugbear since I first got this device. I've posted a couple of times here and on Modaco, but not a lot of feedback apart from the following:
http://forum.xda-developers.com/showthread.php?t=281543&highlight=vibrate
I've not tried it yet but let me know how you get on.
PaulB
An idea i just had:
Its unpractical to accidently accept calls or do stuff on the touchscreen after a SMS while the phone is in the pocket.
But its nice to see who is calling or reading the SMS with out having to turn the screen on before.
So why not use the light sensor, pockets are usually dark. So the software would run in background on an incoming SMS or CALL event it would first check the light sensor, if its dark, dont turn on the screen just start the ringtone sounds. If the environment is bright, just display the caller or SMS right away.
Additional features would be:
- beeing able define the values when to turn on or not
- optional auto screen turn on if it gets brighter (taking the phone out of the pocket), this should only work if there is still someone calling, or a SMS was received in the last 20 (or so) seconds
- program should only read the light sensor on an incoming event to save energy
- optional it could read the light sensor all the time and auto turn on the display everytime it comes out of the pocket, some people might want that
Only problem is, has anyone been able to access the X1 light sensor before? There are programs for the lightsensors of other HTC devices, but the X1 sensors seems diffrent.
A more simple version of this program could simply check the light values every 5 min (or self difineable interval) and set the registry settings for wakeuponcall or wakeuponsms.
Hi all,
On a number of occasions, I've used Market apps to control the screen brightness, either manually (like a brightness widget) or scheduled (using Timeriffic - a great tool for automatic profile changes throughout the day).
Apparently, these apps are not aware of the correct minimum brightness supported by the Leo, making it too easy to go too low, which essentially disables the display completely.
Touch still works, so if I'm lucky enough to remember the location of the widget/slider/controls, I may be able to turn brightness back up to a "sane" level.
For example, Timeriffic turns the screen off with a brightness level of 10% - 15% is the lowest working setting.
If I'm unable to fix it this way, I'm basically forced to reset. The problem is that Android *remembers* this setting after a reboot, and reapplies it just when the device is vibrated slightly at the "Android" logo animation. Thus, with a black screen, it is impossible for me to unlock the SIM, hard to unlock the screen lock, and virtually impossible to correct the brightness setting. I need to remove my data.img ("hard resetting" Android) and restore what I can from backups.
The problem also seems to occur with the standard screen dimming which occurs at about half time before the "screen off" setting. I can see the display start to dim, then it suddeny turns off. In this case, however, Android of course reverts to normal brightness at the touch of the screen or press of a button.
On a related note, I have experienced (like right now) that brightness range used by Android is much dimmer then normal. That is, using the regular brightness slider in Settings, I can only vary between almost invisible (min) and quite dim (max). Curiously, in this situation, the display can get *much* dimmer than normal, without becoming disabled.
Any ideas on these issues would be most welcome!
Workarounds found later in this thread:
- Shine a bright light on the screen - the graphics are still there if you look really hard. It's not a joke!
- Use Screencast in Droid Explorer to "remote control" your Android
- adb shell "echo 255 >/sys/class/leds/lcd-backlight/brightness"
ugumba said:
Hi all,
On a number of occasions, I've used Market apps to control the screen brightness, either manually (like a brightness widget) or scheduled (using Timeriffic - a great tool for automatic profile changes throughout the day).
Apparently, these apps are not aware of the correct minimum brightness supported by the Leo, making it too easy to go too low, which essentially disables the display completely.
Touch still works, so if I'm lucky enough to remember the location of the widget/slider/controls, I may be able to turn brightness back up to a "sane" level.
For example, Timeriffic turns the screen off with a brightness level of 10% - 15% is the lowest working setting.
If I'm unable to fix it this way, I'm basically forced to reset. The problem is that Android *remembers* this setting after a reboot, and reapplies it just when the device is vibrated slightly at the "Android" logo animation. Thus, with a black screen, it is impossible for me to unlock the SIM, hard to unlock the screen lock, and virtually impossible to correct the brightness setting. I need to remove my data.img ("hard resetting" Android) and restore what I can from backups.
The problem also seems to occur with the standard screen dimming which occurs at about half time before the "screen off" setting. I can see the display start to dim, then it suddeny turns off. In this case, however, Android of course reverts to normal brightness at the touch of the screen or press of a button.
On a related note, I have experienced (like right now) that brightness range used by Android is much dimmer then normal. That is, using the regular brightness slider in Settings, I can only vary between almost invisible (min) and quite dim (max). Curiously, in this situation, the display can get *much* dimmer than normal, without becoming disabled.
Any ideas on these issues would be most welcome!
Click to expand...
Click to collapse
I don't know these app(s) but if they are writing their settings and configured values into a ini or settings file, than you might be able to connect via adb and change the setting by this way.
With tools like Droidexplorer or ADB magic, browsing through the files should be very comfortable and you might find the correct file.
this happens on regular android devices ...i have a couple of them
thatruth132 said:
this happens on regular android devices ...i have a couple of them
Click to expand...
Click to collapse
What happens? That brightness is set too low, essentially disabling the screen, so you're forced to hard reset or perform some root magic? How do you cope with it? Or does it happen that the permitted brightness range is just dimmer than usual?
Btw, until there is no light-sensor support in kernel, you can't use such apps for the brightness
Stills a good advice
I have had the same issue with the brightness range being too low. The max brightness is really dim and the colors don't seem right. That may just be the dimming effect though. If I restart the phone it seems to take care of this. I have not had the screen go below the minimum level and turn off though.
is there a fix for this. i just experienced this problem
I experienced the same with Multicon widgets.. had to delete Android and start over
somebully said:
I experienced the same with Multicon widgets.. had to delete Android and start over
Click to expand...
Click to collapse
Oh wow, not good at all, crap...
so that means if i do that i'll lose everything huh?
Theres no way to restore the factory brightness or factory settings for the android?
aznsHD2 said:
Oh wow, not good at all, crap...
so that means if i do that i'll lose everything huh?
Theres no way to restore the factory brightness or factory settings for the android?
Click to expand...
Click to collapse
As long as you have a working WinMo it should be possible to edit the values of brightness, but I have no idea where this information is stored.
Deleting Android folder and unzipping again is esentially restoring to factory settings.
yea this happens to me all the time, its a *****. it cuts off at exactly 12% for me. what i do is have aldiko(a book reader) on the home screen. if i click on it and open a book i can just swipe on the left side of the screen to adjust brightness. since i know that its on the home screeen on the right side middle, i can usually find my way back to it.
somebully said:
As long as you have a working WinMo it should be possible to edit the values of brightness, but I have no idea where this information is stored.
Deleting Android folder and unzipping again is esentially restoring to factory settings.
Click to expand...
Click to collapse
which means that i'll lose everything such as data correct? new contacts etc. msgs...
any thing on this... isnt their a file in the android folder that i could maybe replace to restore to factory settings.
and could someone post a screen shot of their phone so i know where the numbers for the pin code lockscreen. tryin to get past that, then i can adjust my brightness
LOL I experienced it one time. And I must delete data.img to restore the phone. After this, I don't use any brightness tools (except ones already in the Android build).
If anyone have solution, please point us
Well i was able to get my screen back to normal. lol.
I didnt delete the data.img, i simply copied it and then removed it, started a fresh install, and then just marked on my screen where the numbers were, turned it off, put the old data.img back. Followed my marks, and was able to unlock it and then found the power control widget. And bam! screen back to bright...
This might work for you!
Erm... In similar circumstances I found this worked...
I was trying out different Android builds and I found a screen brightness widget. It had various available levels of brightness, one being 0%. As soon as I selected it I felt pretty stupid as true to it's word it gave me 0% brightness placing me in a similar position to the OP.
My Solution. I used my (very bright) led torch to light the screen. By playing around with the angle and beam width I found I could just make out the on screen graphics enough to re-adjust the brightness level.
Simples!
Just as " Justblair " said .. you can place your device under a very bright light thus you'll be able to see the screen and what it's showing .. idk what build you guys are using but in cyanogen you can adjust the lowest dim level so that any app or widget tries to set the brightness to 0% it's automatically set to your preset, 15% for instance.
I've only faced this problem once
Is it absolutely necessary to flood the main thread with all these useless noob posts?
It really has nothing to do with Android development on HD2 and should be posted in the General section IMO.
kawazaki said:
Just as " Justblair " said .. you can place your device under a very bright light thus you'll be able to see the screen and what it's showing .. idk what build you guys are using but in cyanogen you can adjust the lowest dim level so that any app or widget tries to set the brightness to 0% it's automatically set to your preset, 15% for instance.
I've only faced this problem once
Click to expand...
Click to collapse
Cyanogen allows you a max dim level of 26 - which is too little on the HD2.
In Tasker, 30 is the lowest setting that still provides light. Maybe Cyanogen can be patched for the HD2 in coming builds?
Thanks for the tip on shining a bright light on the screen.
Another tip is to use Droid Explorer's "Screencast" feature, to view and control your Android's screen on your PC desktop. Of course, the brightness setting has no effect here.
I use a one minute screen timeout, which is a bit long for the screen to stay on every time you put it back in your pocket. It also gets a little annoying hitting the power button every time after I'm done using it, for example if I'm frequently taking it out and putting it away during a text conversation. So, I used Tasker to tell it to lock the screen every time the proximity sensor fires, combined with WidgetLocker set to its own 10 sec screen timeout. I also told it to NOT do this while on a phone call so the proximity sensor would just turn the screen off but not lock it like normal in that case. So this way, you can keep a longer normal screen timeout, put the phone back in your pocket, and the proximity sensor will fire, lock the screen, and the screen will turn off in 10 seconds. The only issue here is the occasional accidental proximity sensor activation, but it's not too frequent. I'd be curious if anyone else finds this useful.
The Tasker profile:
Context: Proximity Sensor
Task:
1. If %WIN !~ Phone (if not in the phone app)
2. WidgetLocker Cmd Activate (lock screen)
Detecting if the Phone app is open does require enabling the Tasker accessibility service in Settings -> Accessibility -> Accessibility services (check Tasker).
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
mrono said:
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
Click to expand...
Click to collapse
You shouldn't have this issue really unless you frequently overshoot the top of the screen when going for the notification bar.
mrono said:
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
Click to expand...
Click to collapse
God i wish XDA had a "like" button
mrono said:
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
Click to expand...
Click to collapse
Yep, I had a profile like this set up before, but abandoned in very quickly due to this issue. Every time I went near the sensor my screen shut off, no bueno.
Hey... This thing makes phone calls too!
JTNiggle said:
Yep, I had a profile like this set up before, but abandoned in very quickly due to this issue. Every time I went near the sensor my screen shut off, no bueno.
Hey... This thing makes phone calls too!
Click to expand...
Click to collapse
Make a timeout so the proximity sensor has to be activated for at least 3 seconds
initial said:
Make a timeout so the proximity sensor has to be activated for at least 3 seconds
Click to expand...
Click to collapse
Good idea, works pretty nice, Thanks! Seems that 7 seconds is the minimum timeout allowed though, not that that's a problem, running it now. Unless there's is another way to do it that
I must recommend this setup for everyone now.
Context: Proximity Sensor
Task: Display Timeout = 7 Seconds
Handy for work/school too, I just lay my phone face down on my desk and the display takes care of itself.
JTNiggle said:
Good idea, works pretty nice, Thanks! Seems that 7 seconds is the minimum timeout allowed though, not that that's a problem, running it now. Unless there's is another way to do it that
I must recommend this setup for everyone now.
Context: Proximity Sensor
Task: Display Timeout = 7 Seconds
Handy for work/school too, I just lay my phone face down on my desk and the display takes care of itself.
Click to expand...
Click to collapse
Actually, wouldn't that profile change the display timeout to 7 seconds, effective immediately when the proximity sensor activates? So you could accidentally activate it, not be aware, and then have the display suddenly go off on you 7 seconds later. I think what initial was saying was to make it so the proximity sensor itself must be active for at least 3 seconds before anything happens, THEN do what you wish - in my case, I don't actually change the display timeout at all, I just lock the screen with WidgetLocker, at which point a 10 second timeout is in effect from that app.
xdp said:
Actually, wouldn't that profile change the display timeout to 7 seconds, effective immediately when the proximity sensor activates? So you could accidentally activate it, not be aware, and then have the display suddenly go off on you 7 seconds later. I think what initial was saying was to make it so the proximity sensor itself must be active for at least 3 seconds before anything happens, THEN do what you wish - in my case, I don't actually change the display timeout at all, I just lock the screen with WidgetLocker, at which point a 10 second timeout is in effect from that app.
Click to expand...
Click to collapse
That's true. The display timeout does change to 7 seconds. How would you set it so that the proximity sensor must be activated for a certain amount of time?
initial said:
Make a timeout so the proximity sensor has to be activated for at least 3 seconds
Click to expand...
Click to collapse
How do you do this in Tasker?
WillJitsu said:
How do you do this in Tasker?
Click to expand...
Click to collapse
I haven't been able to figure it out, anyone?
WillJitsu said:
That's true. The display timeout does change to 7 seconds. How would you set it so that the proximity sensor must be activated for a certain amount of time?
Click to expand...
Click to collapse
It does just change the display timeout, but only while the proximity sensor is covered. So if you uncover it before 7 seconds, the display stays on like normal, works well for now until I learn some more about Tasker.
Hey guys, I think I figured out how to do this. It requires using variables. Basically, you set a "proximity sensor active" variable that you create to true when it's activated (the context enter task), and set it to false when it's deactivated (the context exit task). Then in the enter task, after setting that variable, you wait 3 seconds, and then test if the variable is still true. If it is that means the exit task has not executed which means the sensor is still active and your task can proceed. If it isn't that means the exit task did execute which means you uncovered the sensor before the 3 second wait time elapsed and so you don't want to proceed. It looks like this:
Context: Proximity Sensor
Enter Task:
1. Variable Set, Name %PROXACTIVE to 1
2. Wait 3 seconds
3. If %PROXACTIVE ~ 1
4. If %WIN !~ Phone
5. If %WIN !~ Voicemail
6. WidgetLocker Cmd Activate
Exit Task:
1. Variable Set, Name %PROXACTIVE to 0
This works fine for me using WidgetLocker, since I only need the task to continue executing after the 3 second wait time, but if you are trying to actually change the display timeout, you'll still have the issue of the value reverting once you uncover the sensor. To get around this, create a separate task that changes the value (Tasks button at the bottom, then New Task), and call this task from the enter task (Tasker -> Perform Task). This puts the action behind a sort of wall that makes your main task oblivious to the fact that it's setting a revertible value, and the value will stick even after you uncover the sensor. Of course, this also means your display timeout will now remain at 7 seconds, so you'll have to create another task to restore that value on screen unlock or something like that.
Let me know if you have any questions, this seems to work okay for me!
I am having a few difficulties with my s4 which I picked up at a Telus store last week. First, my mms app (stock) used to show reply/read buttons in notifications, and now it doesn't show up anymore. Next, and the most annoying is the auto dim. I do not have auto brightness set, and the screen is set to 2min before it shuts off, however, it will dim in less than 10 seconds of no touch activity, then shut off a few seconds later. This is such a frustrating thing to deal with, but I am unable to prevent it from doing so.
The only things I have changed is installing nova launcher (touch wiz is horrible) and using swiftkey due to the lack of autocorrect in the stock keyboard.
Any help is appreciated. Thank you.