Database Develop

Screen Lock and Backlight

Is there a hack to not have the backlight automatically dim out when screen locking the phone? Any help appreciated on this. Thanks.

Yeah, use search. There's a quick & dirty fix that helps until HTC wakes up. It's in this thread somewhere.

Thanks,
I did search quite a bit. The fix I found was to diable the screen shutting off during a phone call. I haven't been able to find the fix for the backlight dimming out when screen locking the device.

Search
Hmmmm... Sorry you missed it. I went back a couple of pages and found ur answer; there are two:
1) Easiest remains to switch off-on your TyTN II after call. Ur back to normal then.
2) Option is a small app, written by Magxs that wakes the baby up after disconnect. See more here: link.
Hope this is of use.
edit: by the way, this only seems to happen to password protected systems. That is an option - switch off the PW. Lot of us can't due to corporate (exchange or goodlink) security pollicy.

Thanks Nukenine, however, this is not the issue I am questioning. Regarding the issue that you are speaking about, the following is the fix:
Modifying the DWORD stored in:
Code:
\HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall
from "1" to "0" will leave the screen on and will fall back to the backlight/power settings
My question is when I key lock my device (the action that we can have on our today screen which says "Device Locked" or "Device Unlocked"), the screen automatically dims out. And when I tap on the screen, it stays dim, it does NOT become bright again. So, I am asking if anyone knows the registry hack on this issue. I hope I clarified what I am trying to find. Thanks again.

Sorry for misunderstanding.

It is a very easy fix.
HKCU\ControlPanel\BackLight\LockLevel\
Change LockLevel to something other than 0. I use 4. The number indicates now many notches you have the slider moved up in the back light control panel.

Jason Lee said:
It is a very easy fix.
HKCU\ControlPanel\BackLight\LockLevel\
Change LockLevel to something other than 0. I use 4. The number indicates now many notches you have the slider moved up in the back light control panel.
Click to expand...
Click to collapse
Hey Jason,
Thanks for the info. However, when I change the number to 4 (I even tried 9), and then I screen lock my device, my original Backlight setting (set to turn off in 30 Seconds) changes to 10 seconds. When I unlock it, go to the backlight settings, change it back to 30 seconds and then lock it, it changes automatically back to 10 seconds. So the hack works, but it gets rid of the backlight settings and changes them to the ones mentioned above.
The more serious issue is when I soft reset the device. It seems that the number I entered into the registry path goes back to the default "0" automatically. I tried this three times and it always goes back to the "0" default, rendering the hack useless.
Any advice?
Thanks again.

Jason, any advice on the above? Is it possible it is because of the registry editor I am using (Resco Registry)?

Sorry it took so ling, been busy.
That is odd.. I guess i hadn't rebooted in some time.. Mine goes back to 0 as well. It doesn't have anything to do with your registry editor. Something is changing it back on boot. Probably one of the HTC services or something. So there may be no good fix for this.. Other than someone writing a program that will change it back after start up.
I don't have my back light ever set to go off after a time.. It seems pointless to me.. Just have the device power off after a time. Saves more power than just dimming the back light.
anyway.. i have not seen the issues you describe with that but i don't have it set that way.

Jason Lee said:
Sorry it took so ling, been busy.
That is odd.. I guess i hadn't rebooted in some time.. Mine goes back to 0 as well. It doesn't have anything to do with your registry editor. Something is changing it back on boot. Probably one of the HTC services or something. So there may be no good fix for this.. Other than someone writing a program that will change it back after start up.
I don't have my back light ever set to go off after a time.. It seems pointless to me.. Just have the device power off after a time. Saves more power than just dimming the back light.
anyway.. i have not seen the issues you describe with that but i don't have it set that way.
Click to expand...
Click to collapse
Thanks Jason, I appreciate the reply and feedback.

This is bugging me too. I hope we find a solution for it soon. Is there a place in registry where startup programs can be defined? If yes, is there a silent tool we can use to import a reg file in the background at startup?

Dim Backlight until unlock - why? - fix?

When my Tilt is locked and I hit the unlock key, the screen turns on, but very dim until I tap the unlock button onscreen.
Is this normal behavior for Tilt and Tytn II?
And what would be the purpose of this?
It is annoying and inconvenient, IMNSHO - especially when outdoors and the screen is difficult to see even on brightest setting - it can be hard to tap the right spot to unlock!
If this is normal, is there a disable available?

I was under the impression that this was a battery saving feature of the device. Dont want your device going flat from accidental taps of the screen whilst its locked.
Probably fixed through a reg hack.
Will have a look and let you know.
BTW this happened on the original TyTN too.

silent_killa said:
I was under the impression that this was a battery saving feature of the device. Dont want your device going flat from accidental taps of the screen whilst its locked.
Probably fixed through a reg hack.
Will have a look and let you know.
BTW this happened on the original TyTN too.
Click to expand...
Click to collapse
I had a Wizard before this and it didn't do that, so I wasn't sure.
The Wizard screen would never light up from screen taps, just when button pressed for unloc.

\HKCU\ControlPanel\BackLight\LockLevel\ Change LockLevel to what ever value you want the back light set to when your device is locked.
From here:
http://wiki.modaco.com/index.php/HTC_Kaiser

Axman said:
\HKCU\ControlPanel\BackLight\LockLevel\ Change LockLevel to what ever value you want the back light set to when your device is locked.
From here:
http://wiki.modaco.com/index.php/HTC_Kaiser
Click to expand...
Click to collapse
Link isn't working for me.
EDIT: Nevermind, works now.

Change LockLevel
Axman said:
\HKCU\ControlPanel\BackLight\LockLevel\ Change LockLevel to what ever value you want the back light set to when your device is locked.
From here:
http://wiki.modaco.com/index.php/HTC_Kaiser
Click to expand...
Click to collapse
Thanks, man! That worked perfect!
That site has a lot of useful tweaks, such as "Stop screen going off during call"
EDIT: This registry setting will not stick for me after a soft reset. And I know the drill, I've done dozens and dozens of registry tweaks. Somebody else try it just to confirm please?

cushcalc said:
EDIT: This registry setting will not stick for me after a soft reset. And I know the drill, I've done dozens and dozens of registry tweaks. Somebody else try it just to confirm please?
Click to expand...
Click to collapse
Did u find a fix for this issue?

cushcalc said:
EDIT: This registry setting will not stick for me after a soft reset. And I know the drill, I've done dozens and dozens of registry tweaks. Somebody else try it just to confirm please?
Click to expand...
Click to collapse
Did u find a fix for this issue?

Screen sensativity.

So my only complaint so far is the screen sensativity.
I know this doesnt use a capacitive screen, so it needs physical pressure, but it seems to me the glass on the top of the screen makes it need alot more pressure than i'm used to. The middle of the screen seems to be more sensative, and the outside less sensative.
You can test this by putting your finger down on HOME in touchflo, then scrolling to programs and back again. If you pres hard, it will go back and forth. If you use less pressure at home and programs it will load the programs or home screen, as if you released your finger.
So i know there's two reg keys for this:
HKEY_LOCAL_MACHINE\Drivers\TouchPanel
By doing a screen slignment and pressing hard with the stylus i get a lower value here, and by pressing lightly i get a higher value here.
So high value = detects lighter press, low value - needs harder press
HKLM\Software\OEM\TFLOSettings\fingurepressure
This i'm confused about. I tried setting it to 0, 2, 14, 200, 255, 600, and there's not noticable difference as far as i can see.
Is there some sort of program that can read the the pressure from the screen and display it? This would help make the tests alot more scientific!

Someone posted this tip in the tips and tweaks thread above...maybe useful to you??
One tip for changing the sensitivity if you don't want to mess around in the registry:
- run the Align Screen setting (under Settings/System/ Screen)
- when you press on the 'targets' with the stylus, use VERY light pressure...just enough that the tap is accepted
- I usually tap a few times on each target, starting too lightly, and then gradually increasing the pressure until the tap is taken
- do this for each of the 5 targets
I found this seems to make the Diamond calibrate a higher sensitivity for its touch-screen, so finger touches can be much lighter.
This is probably a safer way to change the sensitivity, as you don't risk putting an invalid number into the registry.

Thanks, i already tried that.
Can someone tell me their value for this key?
HKLM\Software\OEM\TFLOSettings\fingurepressure

Screen sensitivty
Spawn12 said:
Someone posted this tip in the tips and tweaks thread above...maybe useful to you??
One tip for changing the sensitivity if you don't want to mess around in the registry:
- run the Align Screen setting (under Settings/System/ Screen)
- when you press on the 'targets' with the stylus, use VERY light pressure...just enough that the tap is accepted
- I usually tap a few times on each target, starting too lightly, and then gradually increasing the pressure until the tap is taken
- do this for each of the 5 targets
I found this seems to make the Diamond calibrate a higher sensitivity for its touch-screen, so finger touches can be much lighter.
This is probably a safer way to change the sensitivity, as you don't risk putting an invalid number into the registry.
Click to expand...
Click to collapse
Tried that, and its really works. Thank a lots.

someone1234 said:
Thanks, i already tried that.
Can someone tell me their value for this key?
HKLM\Software\OEM\TFLOSettings\fingurepressure
Click to expand...
Click to collapse
the value is 19 in uk device rom.

vijayvasa said:
the value is 19 in uk device rom.
Click to expand...
Click to collapse
19 decimal?
I've just about had enough of this touchflo.. pretty but soooo anoying to use
Today on about 3 ocasions i was navigating through it and got a call.. the lights on the touch wheel were flashing and it was playing the ringtone, but the whole phone was frozen for about 4 seconds. Eventually the call popped up and i was able to answer!
I think i'm going to diable it and do my best to make the rest pretty.

You just have to be patient...the roms are not mature yet...
In 3 months you'll see that Diamond will be the best phone out there
I also am trying to find out the best way to configure the finger sensitivity.
HastaSSSS

s1rl4ncel0t said:
In 3 months you'll see that Diamond will be the best phone out there
Click to expand...
Click to collapse
yeah but 3 months is a long time... i have to do something to stop myself smashing the phone on the floor on frustration!
for now i'm going to disable touch flow, and i'll come back to it when a new rom comes out.

Have you tried the new rom 1.37.XXX ?
Bye

I have a UK diamond.. so it came with 1.37.405.1

I've just done the "light tap" trick, and now it's perfect...
Could it be that you have a defective device?
Bye

Its better with that 'trick' but still anoying. I have a feeling i'm just too used to a capacitive screen.
The wierd thing is with the light tap the key HKEY_LOCAL_MACHINE\Drivers\TouchPanel ends up back to 30 to 50 decimal.

i only bought it today yet im seriously thinking of taking it back. The iPhone is just the better product, and always will be, unless Microsoft and the software developers get as passionate as those at apple.
Its Laggy
Its un-intuative
The touch screen isnt as sensitive as it should be. (why are they still using resistive touchscreens)
And the opera browser isnt all that either, it doesnt redraw quick enough for the full page display thing to really be all that impressive on zoom in/out and leaves chessboard squared at it struggles and chuggs to redraw.. . .not great, not when the comptetition is as good as it is. . . . .im thinking 3G Iphone, ****ty camera or not.
Loose the 6.1 and stop trying to polish that turd with TouchFlo's. Yeah good effort, but it just aint good enough
J

WM is just a huge resource hog. The touchflo is slow because its a plugin for the today screen, which then calls on windows API's to draw onto the screen.
Its such a long long way round to get to the hardware that its just slow no matter how well u code.
I just hope someone ports android to the diamond, because the hardware is amazing, the OS is a pile of ****!
BTW they use resistive touchscreens to have increased touch resolution. Also a stylus wouldnt work with a capacitive screen.

I prefer to work with resistive LCD than capacitive...
The capacitive have better sensibility, but are less precise...
Although the Diamond LCD is not as sensitive as a capacitive, it's sensitive enough to work well with the fingers...
It's just a matter of tweaking.
HastaSSSS

Resistive screens use a grid of conductive material, sandwitched between the glass and a conductive layer. They alternatly pass an electrical current on each line of the grid along the x and y axis. When you press the screen you touch this grid onto the conductive layer and the current passes through it, which is detected. You can make resistive screen that have a very high resolution of detection, and the resolution is always what you design it to be.
Resistive screens are pressure sensative, and by design can't handle multi-touch.
Capacitive screens use glass coated with a conductive coating. The edges of the screen are connected to conducters. Each conducter has a different frequency oscilator connected.
The capacitance of a human finger changes the impedance of the screen, and so changes the frequency of the oscillator circuit. This gets converted to distance from each oscillator and so a co-ordinate.
The resolution is limited by how acuratly you can detect changes.
Typically in electronics very small changes are hard to measure because they are indistiguishable from noise.
Capacitive screens can handle multi-touch, but the resolution of each touch is decreased in that case.
Capacitive screen resolution is not absolute and can change with increased noise in the system, or by multiple capapcitive effects on the screen - like multiple touches.

Screen sensitivity

Is there a setting in Andorid to make the touch pressure more sensitive. I recall do registry edits in WinMo that accomplished this. The screen in Android just seem to require more pressure then what I remember having WinMo set to.
It also could be that I'm just use to capacitive screens.
Thanks

gedster314 said:
Is there a setting in Andorid to make the touch pressure more sensitive. I recall do registry edits in WinMo that accomplished this. The screen in Android just seem to require more pressure then what I remember having WinMo set to.
It also could be that I'm just use to capacitive screens.
Thanks
Click to expand...
Click to collapse
ADB/Terminal:
echo "3072" > /sys/module/tsc2003/parameters/sensitivity
I've tried it and I could mess it up enough for it to noticeably lower sensitivity but I could never tell if it actually increased it (but it probably did).
Edit: One thing I noticed is that I could never get the settings to stick beyond a reboot.

lightly touching during screen calibration seems to work.
I was having a similar issue with "touching like you mean it" to get things to work. I tried re-running the calibration tool and pressing with the stylus as light as i could and still get a reading. its not like my incredible, but it is silky smooth.

LiveDisplay's RGB Color Calibration on the fly

Recently I've had my phone display repaired and the very first thing I noticed was that the brightness on the replacement display was not working. I tried wiping data/changing ROMs and confirmed that it really is hardware related.
My solution is to use LiveDisplay Color Calibration from LOS. What is does is basically reduce the screen "brightness" by reducing the RGB values. It does a relatively good job at preventing my eyes from drying out at night.
Now, the problem is that everytime I need to increase/decrease the brightness, I need to manually go deep into Settings to adjust it. Is there any Tasker profile to let me adjust those values on the fly? Or at least to profile a low-brightness value on one tap?
I found a thread on r/tasker that is close to my problem, but isn't really doing anything. Any help would be greatly appreciated.

axljohn said:
Recently I've had my phone display repaired and the very first thing I noticed was that the brightness on the replacement display was not working. I tried wiping data/changing ROMs and confirmed that it really is hardware related.
My solution is to use LiveDisplay Color Calibration from LOS. What is does is basically reduce the screen "brightness" by reducing the RGB values. It does a relatively good job at preventing my eyes from drying out at night.
Now, the problem is that everytime I need to increase/decrease the brightness, I need to manually go deep into Settings to adjust it. Is there any Tasker profile to let me adjust those values on the fly? Or at least to profile a low-brightness value on one tap?
I found a thread on r/tasker that is close to my problem, but isn't really doing anything. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Test the sensor light under the screen

qitecko said:
Test the sensor light under the screen
Click to expand...
Click to collapse
I'm not sure what you meant by that but my phone doesn't have a light sensor.