Database Develop

Backlight wont go off ....

i have set the back light to turn off after one minute in external power.
usb sync cable connected to pc and back light will go dimmer in one minute but not complete off.
anyone has this problem?

this seems to be the new behavior of the TyTN II vs. the old TyTN: The back light never goes completely off. You have to push the power button to put the unit in standby. When I listen to music, for instance, I want the backlight to go off to save power: I must push the power button to turn off the backlight. The music still plays, which is nice...
Anyway I'm not sure what to do about it when it's connected to a computer to sync, since pushing the power button would likely interrupt the sync. It doesn't bother me that the backlight doesn't go off.

Hi
I'd go as far to say this is the new behaviour of Windows Mobile 6. The Toshiba G900 was exactly the same. It is possible to get a small app to turn the backlight off completely however when it's connected to your computer via USB it isn't drawing power from the battery but from the computer so it doesn't matter, and it's just show you it is still on.
Regards
Phil

8525 running Black Satin WM6 doesn't do this, I don't think it's WM6

rite i dont mind the power consumption, but i cant go to sleep with the light on next to me, i like it off completely to save screen life too.

Hi
8525 running Black Satin WM6 doesn't do this, I don't think it's WM6
Click to expand...
Click to collapse
With all due respect that is a cooked ROM and will not need to follow WM6 best practice or MS guidelines.
I think this happens with the Kaiser (like it does with the G900) because the LCD isn't transreflective. With a transreflective device, even in normal room light you can usually see what is on the TFT display, so the device can time out the backlight completely turning it off, and you still know it is powered on but just the backlight has gone off. With a non transreflective screen like the Kaiser, if the backlight did go off completely while the device is still on, you can not see anything on the TFT screen, so it looks completely off, but it isn't. So I think the dimmed backlight is so you know it is still on by being able to see something on the display.
You can see this happening on battery power. If the backlight is timed to go off before the device powers down, it doesn't go off completely but dims, then shuts off completely when the device goes into standby.
but i cant go to sleep with the light on next to me, i like it off completely to save screen life too.
Click to expand...
Click to collapse
You have a few options:
1) Power off the device.
2) Press the standby button.
3) Turn it upside down or cover it.
4) Download this application that will let you turn off the backlight completely. http://ppcsoft.narod.ru/english/
i like it off completely to save screen life too.
Click to expand...
Click to collapse
This will be making little different to your screen life. The backlight is made up of white LEDs, these will have a lifetime of around 50,000 to 100,000 hours (more when used at a dimmed setting) so will easily outlast the device even if running non-stop from the day you buy it.
Best Regards
Phil

ic, as long as its ok for the screen life i am cool with it. thanks for the input.

PhilipL said:
Hi
4) Download this application that will let you turn off the backlight completely. http://ppcsoft.narod.ru/english/
Best Regards
Phil
Click to expand...
Click to collapse
This app would be good except that when you set the action to turn the light off in say 15 seconds it only does it the first time and then must exit itself because it won't do anything further until you reload it.
I need a program that stays resident and turns the light off after a set period of time. Pressing the power button isn't good enough because that stops a lot of apps running by putting the Kaiser into standby.
Anyone know of a program or fix?

The 8525 turned the backlight off no matter if you used stock or cooked ROM. The 8125 was the same way. Not until I got my Tilt did this "feature" arrive.

There may be some kind of a flaw in the programming. No, that never happens with a M$ program.
I was having the issue described in the thread, backlight stayed on. I played with my power and backlight settings and while searching for the answer my screen dimmed, even though it is connected via USB. I think if you go back and reset your backlight and power settings, that you will then see the desired effect on the PDA screen.
My settings:
Power= On Battery- 1 minute, On External- 2 minutes
Backlight Brightness= On Battery set to middle (half way), On External set to full
Battery Power Tab and External Power Tab- both set to 1 minute
The end result is that after 1 minute my screen dims to the lowest backlight setting. Screen is dim but I can still read what is there.

This is a very old thread, the backlight is always on because the Kaiser's screen is not transreflective like it's predecessor Hermes. If the light is out you will see nothing where you could with the Hermes. It's just the way it is with this model.

I have another question which it is related with the backlight and power off.
I tried to power off the phone by pressing and holding the power button. It asks me to confirm it. However, after the phone is "powered" off, it seems can be turned on by sliding out the keyboard.
Is it normal? or is it something to be fixed?
I have an ATT Tilt with stock ROM.
(just got it few days ago from ebay).
Thanks.

Down with new, weird "features"!
Lidberg said:
The 8525 turned the backlight off no matter if you used stock or cooked ROM. The 8125 was the same way. Not until I got my Tilt did this "feature" arrive.
Click to expand...
Click to collapse
If I read your sarcasm correctly, I am in agreement that this is a dubious feature. I think there are a number of changes from 8125&8525 to "8925" that are questionable. I wish HTC would spend more time getting the hardware and basic features working perfectly, and less time adding new programs just to change the look.

Transflective . . .
RemE said:
This is a very old thread, the backlight is always on because the Kaiser's screen is not transreflective like it's predecessor Hermes. If the light is out you will see nothing where you could with the Hermes. It's just the way it is with this model.
Click to expand...
Click to collapse
Everything I can find in searching says both the Hermes and the Kaiser have transflective screens, (as well as the 8125); e.g., from elite-electronics.com RE: the Tytn II: "color transflective TFT". [However, neither the 8125 or Tytn II have the technology that allows good viewing in daylight, like a Garmin Nuvi 350 or similar]
But if you can actually see something on screen on the Hermes when backlight is turned off, then that is truly different from the 8125 and the Tilt.

plchan said:
I have another question which it is related with the backlight and power off.
I tried to power off the phone by pressing and holding the power button. It asks me to confirm it. However, after the phone is "powered" off, it seems can be turned on by sliding out the keyboard.
Is it normal? or is it something to be fixed?
I have an ATT Tilt with stock ROM.
(just got it few days ago from ebay).
Thanks.
Click to expand...
Click to collapse
This is normal behavior. If you don't like it...download KaiserTweak.
Under the Keyboard->Slide Wake option you can disable it.

cushcalc said:
If I read your sarcasm correctly, I am in agreement that this is a dubious feature. I think there are a number of changes from 8125&8525 to "8925" that are questionable. I wish HTC would spend more time getting the hardware and basic features working perfectly, and less time adding new programs just to change the look.
Click to expand...
Click to collapse
Agreed. HTC - stop fixing what isn't broken in the first place.

cushcalc said:
Everything I can find in searching says both the Hermes and the Kaiser have transflective screens, (as well as the 8125); e.g., from elite-electronics.com RE: the Tytn II: "color transflective TFT". [However, neither the 8125 or Tytn II have the technology that allows good viewing in daylight, like a Garmin Nuvi 350 or similar]
But if you can actually see something on screen on the Hermes when backlight is turned off, then that is truly different from the 8125 and the Tilt.
Click to expand...
Click to collapse
Transreflective is NOT in the HTC TyTN II spec but is in the TyTN I spec. You can't believe a reseller.
If you turn off the backlight on a Hermes and then grab a big flashlight and shine it on the screen, you can then easily see the screen, the brighter the light the better you will be able to see it.
If you try this with Kaiser you will quickly see that the bright light will make it impossible to see the kaiser screen, no mater what backlight setting you choose, and certainly not on low.
It's a simple test and I'm convinced on what I say.
That said, the Kaiser's transmissive screen is super bright in most mid to low light areas since transreflective screens are normally not quite as bright as transmissives.

[SOLVED] Backlight doesn't turn off when using TomTom...?

TomTom v7.450
Diamond ROM v1.37.405.1 WWE
Can anyone else confirm that their backlight never turns off whilst using TomTom, regardless of what setting/timeout they've got on the device's Power config page? Whether I'm using it on battery or mains the result is the same - backlight remains on continuously. If I shut TomTom down I then see normal behaviour and the light turns off after the set time.
Interestingly, if I install the very same TomTom CAB on my M600/Prophet it behaves correctly i.e. the backlight turns off after a time. The device remains continuously on, regardless of setting, but then that's what I'd hope for anyway as TomTom is no use if the device is not active.
Given the above, has anyone got any ideas as to why this might be the case, and what I might be able to do to solve it? I really want the backlight to dim as it will save a considerable amount of battery should I be using TomTom on battery... and it would automatically turn it back on when it comes to advised turns etc.
Incidentally, the backlight does dim/brighten in response to changes in the ambient light level so that's at least something - however I tried removing this setting in case that was the problem but it wasn't.
Mathew

I also use TOM TOM on my Diamond..and I think that is normal that the backlight is on when using the navigato..also if you use the Stand Alone navigator the back ligt stays on!
I can't see the use of the navigator with the device in standby..you should buy a car charger so your battery recharge during the utilization of navigator

Backlight doesn't turn off when using TomTom...?
Click to expand...
Click to collapse
I have a question, can this problem co-exist with the problem of backlight turning off too fast when making a call, or do these two problems cancel each other ?

MJNewton said:
TomTom v7.450
Diamond ROM v1.37.405.1 WWE
Can anyone else confirm that their backlight never turns off whilst using TomTom, regardless of what setting/timeout they've got on the device's Power config page? Whether I'm using it on battery or mains the result is the same - backlight remains on continuously. If I shut TomTom down I then see normal behaviour and the light turns off after the set time.
Interestingly, if I install the very same TomTom CAB on my M600/Prophet it behaves correctly i.e. the backlight turns off after a time. The device remains continuously on, regardless of setting, but then that's what I'd hope for anyway as TomTom is no use if the device is not active.
Given the above, has anyone got any ideas as to why this might be the case, and what I might be able to do to solve it? I really want the backlight to dim as it will save a considerable amount of battery should I be using TomTom on battery... and it would automatically turn it back on when it comes to advised turns etc.
Incidentally, the backlight does dim/brighten in response to changes in the ambient light level so that's at least something - however I tried removing this setting in case that was the problem but it wasn't.
Mathew
Click to expand...
Click to collapse
this is a feature (and a good one) and not a bug. i bet you don't want that when driving, right before a big intersection yr screen go off....
for example,the igo (that's what i am using) give you the option to go by the device or all time on.

KukurikU said:
this is a feature (and a good one) and not a bug.
Click to expand...
Click to collapse
If it was a feature I would expect it to manifest itself when installed on both the Diamond and the Prophet (given the common application) - the fact it doesn't suggests to me it is a 'quirk' (not necessarilly a bug) with the way it works on the Diamond. As mentioned, the backlight used to come back on when being advised of any directions etc and would remain until well clear of a junction so if it is a feature it's an unnecessary one!
Sometimes it is not convenient for me to use external power - when riding on my bike for example. And in such circumstances the high ambient light level used to be plenty sufficient for me to see the screen on the Prophet without the backlight being on - this is obviously great for conserving battery power as the light ranks as one of the highest power consumers.
I might see if the TomTom menu is still customisable and, if so, include the 'Backlight Preferences' icon that was present in versions of Navigator prior to v6.
Mathew

As mentioned, the backlight used to come back on when being advised of any directions etc and would remain until well clear of a junction so if it is a feature it's an unnecessary one!
Click to expand...
Click to collapse
interesting! didn't know that...doesn't bother the on\off of the screen while navigating in town (lots of instructions)? not sure i'll want all this flickering

Solved it!
In fairness, it seems that it is a TomTom quirk.
Specifically, the application has always (since I've been using it from v5) had a built-in setting for when to turn the backlight the backlight off (or, more accurately, when to allow the device to turn it off in accordance with your time setting) - the options being: 'Always', 'When on a walking route', 'When not charging' or 'Never'. The default being 'Never'.
However, since v6 the button to change this setting disappeared from the menus however given it is possible to customise the TomTom menus and, even better, to include icons from previous versions of TomTom (assuming the feature is still supported internally) I did the following to turn my backlight setting to 'When not charging'...
- Create a file \TomTom\SDKRegistry\TomTom.mnu in the root of the device
- Inside this file put the following:
Code:
MENUBLOCK|BLOCK_MAIN|BTM_DONE|
MENUPAGE|TASK_PAGE1|Main Menu|
MENUITEM|TASK_EXIT_APP|
MENUITEM|TASK_SET_BACKLIGHT|
MENUITEM|TASK_PAGE1|
- Now run TomTom and click the main screen - up will come a menu with two items in it - Exit and Backlight Preferences, the latter will allow you to configure exactly how you want the backlight to behave.
- Quit TomTom and delete the TomTom.mnu file - this will revert you back to the stock menus, but with the backlight setting (permanently) set.
Of course, this process can be used to configure your menus exactly how you want them however I don't know the keys for all the icons - only for those when I last dabbled in v5 - maybe if I can find some time I'll find the others (I haven't Google for them so perhaps these are now common knowledge) such as the MapShare functions that only came in v7.
The reason it the backlight worked as I wanted when installing the cab on my Prophet was because it still had my menu configs from v5 installed on it... d'oh!
I could be alone in wanting to be able to choose how the backlight is managed, but just in case there's someone with the same desire hopefully this'll be some use to you. It does of course beg the obvious question - why did TomTom remove this customisable feature?!
Cheers,
Mathew

youupy! drinks on you!
congrats and yes, i knew from the beginning that i can help you. dhaaaahh. lol!

Interesting, previous versions of tomtom allowed you to adjust the backlight settings within the application.
cant find it in TT7 though

KukurikU said:
doesn't bother the on\off of the screen while navigating in town (lots of instructions)? not sure i'll want all this flickering
Click to expand...
Click to collapse
On the contrary; they've handled it handle it very well.
Say you've got your backlight timeout set to 30 seconds then after this amount of time with no activity (direction instructions etc) it will turn the backlight off - you can still see the map outline in ambient light and, most importantly, can easily see the distance indicator to the next direction.
A few seconds prior to the next instruction the light will reilluminate, a few seconds later it will give the direction advice/distance etc and then once you're through the junction it will turn the light off again after 30 seconds.
Of course, when following a rapid series of instructions in, say, a built-up area then the backlight will stay on continuously - each instruction essentially resets the timer. It's only when out on the 'open road' with no isntructions for miles that you'd see the effect.
All said and done, when I've got access to external power I keep the backlight on constantly (that's where the 'Extinguish only when not charging' option comes in) but when I'm running on batteries I need all the power-saving I can get, not least given the limit battery capacity in the Diamond!
Rumpleforeskin said:
Interesting, previous versions of tomtom allowed you to adjust the backlight settings within the application.
cant find it in TT7 though
Click to expand...
Click to collapse
As mentioned they dropped the icon in v6 yet still supported the functionality internally - it's just that with no icon you can't change the setting hence the temporary icon-insertion method discussed above.
Mathew

TouchLockPro poll

Hi,
currently some people are reporting problems with TouchLockPro 2.2.7, which uses the GSENSOR and capacitive sensor for unlocking.
Via this poll I want to achieve the following:
* get insight which percentage experiences problems with TouchLockPro
Hope this is going to work.
Rick.

ZR,
...USING THE STANDARD WINDOWS MOBILE DIALER (NOT HTC) PREVENTS UNLOCKING...
Something else I noticed. Because of ring delays (caller is on the 2nd or 3rd rings when my phone rings the first time), I switched to the default dialer skin. That's the standard WM6.1 phone interface. When I'm on the dialer screen when the phone wakes up (either through a call or me hitting the power button), the touchscreen stays locked (red strip will not go away) and the capacitive unlock does not work (though the buttons do).
There must be some compatibility issue with the standard dialer vs. the HTC dialer. In fact, there are several other compatibility issues with the standard dialer (bluetooth icon is gone, volume control during a call does not work, etc.), so I bet some of these problems are a result of some of us not using default HTC dialer skin.
The only way I can unlock the phone when it is on the dialer screen is by sliding the keyboard or removing the stylus.
Also, now at the end of the day, if I am on the today screen and wake up the phone, it takes about 5 seconds before the capacitive unlock works. Any ideas what could be causing that delay?

I don't remember if I had problems with v2.1 so I did not check the box. I am having problems with 2.2.7 so I posted my problems in the other thread.

well I have had problems with version 2.2.6 - sometimes it didnt lock; when I connected to EDGE display turned off etc. but now version 2.2.7 looks that its working right again

v2.2.4 so far is the one with most responsive capacitive sensor on my Dutty ROM for HTC Diamond.

ZR,
I'm still using TLP 2.1 on my touchpro.
After a few attempts to upgrade to TLP2.2 and higher, which always giving unstable feedbacks, i turn back to the more stable TLP2.1. Afterall, i don't use the features in TLP2.2 with Gsensor support and i don't use light sensor either.

TouchLockPro 2.3
Because of too may problems with TouchLockPro 2.2.7, I posted TouchLockPro 2.3, which should solve the reported problems.
See TouchLockPro XDA thread and zuinigerijder.com
Hope this version is better, as bonus I included some new cool features

Diamond keeps "waking"

My phone is constantly waking up when not in use. There is no obvious activity that i see, such as email,SMS etc. I was told possibly when the signal or towers change it wakes up?
All i know is im at work and the darn phone keeps lighting up. Im driving at night and it's lighting up. it's in my pocket and im dialing my last call! This is also killing my batteries!
Is anyone having this problem?? Can this be fixed?? registry tweak?? Im so angry with this phone because of this. otherwise i really like this phone.
Thanks.

I had the problem of dialing when in my pocket... and a slightly different error with the lights.. the ones around the dial just won't switch off even when all the messages and alerts are cleared.
I've found that if you lock the screen so that you can only use the power button, it solves this as it's easy to unlock the phone from ur pocket (I've had it in a jacket pocket and it's done it!)
Should solve it!...
As for the lighting up... have you tried adjusting the power options for optimum battery as this solved the same issue on my Touch Cruise.

you can use TouchLockPro for preventing bogus calls. Are you sure it does not awake on buton presses, a windows mobile setting.

wake up woes
Same issue here. It seems the CDMA Sprint Diamond wakes up on new SMS or when switching cell towers and there is no way to disable that regardless of what ROM you're using. It's ridiculous... and it is my only major problem with the phone. Hopefully someone will find a better solution. Until then Locking the phone will have to suffice.

ive been using the lock feature. the only thing is it often gets "stuck" in lock mode. i will turn on the phone the backlight would be dim - like in lock mode. i can use the phone but it wont come out of the "dim" mode until i take out the battery and put it back in.
separately,
I wonder if i was using the diamond phone from another provider if i would have the same "waking" problems?

xm81bpm said:
ive been using the lock feature. the only thing is it often gets "stuck" in lock mode. i will turn on the phone the backlight would be dim - like in lock mode. i can use the phone but it wont come out of the "dim" mode until i take out the battery and put it back in.
separately,
I wonder if i was using the diamond phone from another provider if i would have the same "waking" problems?
Click to expand...
Click to collapse
I have the same problem. The phone wakes up all the time by itself. It is a problem with the defective power buttons that come on the Diamonds. No fix for that so far that I know of. It is a hardware problem, I think.

Mine wakes up when switching between home and roaming towers. Not sure about switching home to home towers or roaming to roaming. I also had my power button being bumped on from time to time; I'd take out my phone to find it had tried to dial someone, adjust the clock, etc. Very annoying.
Pocket Shield is amazing; it's the only lock app I can find that does what my Treo's always did: unlock on center button.
Works wonderfully well!

Before I upgrade my 1.93 CSL ROM to the 2.0x CSL ROM, it also always woke up itself...
After I upgarded my ROM (i.e. a hard reset) problem gone... So I think that's not a hardware problem...
Yet at this moment I'm still unclear which program caused that problem...

I've been using the locking program S2U2 which is free and it works beautifully.

Tomtom screen disabeling

I already made a thread about the backlight, but it seems that I only have that problem while using Tomtom.
If I use tomtom without external power, the screen blanks after 30 seconds, or whatever setting is used in the energy settings of the TD2.
When driving on external power, the screen goes blank after 30 minutes (the maximum of the settings if the TD2 isn't used.
On my diamond 1, the diamond recognized tomtom as an active application, hence the screen would stay on, until the battery was empty.
Weird thing is: if I use Coreplayer, the screen does stay on, so the TD2 recognizes Coreplayer as an active application.
More people with this problem? I have the latest official HTC rom (Dutch). Did multiple hard-resets and multiple installations of TT7 (7.910 and 7.915 versions). With or without audio-fix; no matter what: screen blanks....

Touch Incall Tweak ?
maybe is the Touch Incall tweak the solution for you? You can then manually enable backlight settings:
http://forum.xda-developers.com/showthread.php?t=488991!:
Hope this works for you, did it for me.

Unfortunately, it did not. I installed the app, did a soft reset and saw that TomTom was one of the applications on the list.
However, after the same period the screen went blank again. As far as I understand it, the applications on that list are the apps that should prevent the screen blanking out, when a call is coming in. But using tomtom, not always a call comes in..
So, how did you manage to get it working then..??

Honoustly I don't know. I remember I had the same problem but after a while the screen doesn't switch off anymore.
I always have the TD2 power connected when navigating and in the settings tab-more-system-energy-advanced tab you can control the lighting settings and time outs.
Must say that I downgraded to Tomtom 7.910.9185 caus' it should work a little better... I still have the big lag and slow screen refreshing problem though.
For navigating I use Nav'n go Igo (8.3.2.80621) now. Has a lag also but works better and more stable. And uses maps of 10-3-2009!
What version are you using?

TT 7.915.9196, but tried the .9185 also, but seemed to me that that version gave a little more lag than the newest. Newest is stable; the point of the arrow is the point that my car is, so thats ok with me.
Last thing seems that on car power the tt stays on now, but on battery power still disables the screen. Both versions, with or without the audio-fix, with or without the tweak.
O and I upgraded to the latest rom; no result either.