Lightening Problems - Mogul, XV6800 General

Hi there,
I am looking for solutions (probably registry hacks) for two problems regarding the light of the titan.
1. Does anyone know a solution to extend the lightening time for the front keys? I have always the problem that I cannot clearly find the red phone key when finishing a phone call.
2. A more general problem: When I use my titan in an active car holder, the keyboard stops to lighten after 30 seconds. Is there a possibility to keep the light of the keyboard, when the titan is connected to an active car holder?
Unfortunately HTC is not very helpful, stating that these are desired actions in order to save battery energy (also using it in an active car holder!)
Thanks for your help, me_phi

me_phisto said:
Hi there,
I am looking for solutions (probably registry hacks) for two problems regarding the light of the titan.
1. Does anyone know a solution to extend the lightening time for the front keys? I have always the problem that I cannot clearly find the red phone key when finishing a phone call.
2. A more general problem: When I use my titan in an active car holder, the keyboard stops to lighten after 30 seconds. Is there a possibility to keep the light of the keyboard, when the titan is connected to an active car holder?
Unfortunately HTC is not very helpful, stating that these are desired actions in order to save battery energy (also using it in an active car holder!)
Thanks for your help, me_phi
Click to expand...
Click to collapse
settings > backlight > set the respective timeout higher. it will keep the keys on too.

Related

No LED on answer/hangup buttons on hinge

Hi,
When i first setup my Exec using personal mode, the answer and hangup buttons on the hinge woudl illuminate when a call came in (when the unit is closed like a laptop). Now i am using it in corporate mode, the LED's don't illuminate. They only illuminate when the screen is rotated into PDA mode.
I am assuming this is a reg hack. Does anybody know what it is? or has anybody else got this problem?
Cheers
Paul
They don't illuminate when the device is closed, only when you have the screen open or facing outwards.
hollinshead said:
They don't illuminate when the device is closed, only when you have the screen open or facing outwards.
Click to expand...
Click to collapse
And very annoying it is too - especially when both buttons look so similar when not illuminated. This must be hackable?
This has got to be one of the most annoying features of the exec.
Also i have found that if the device is closed, MSVC does not recognise anything you say when activated via BT.
I have never really played with the device in personal mode as the GUI is bollox so cannot comment on if the buttons light up or not when the device is closed. But what i do know is that when it is closed the screen is switched off as if the device is in standby mode, maybe this has something to do with it.
I try to memorize the position of the green button in relation to how I always hold the phone and feel for it like a Braille board. So far I get it 75% of the time.
is anybody using the 'Personal' install on their exec? can they confirm if the LED's are illuminated or not when the phone rings when it is closed?
Cheers
Paul
Someone who's actually opened the Universal may be able to confirm this, but I suspect that the answer/hang up buttons on the hinge don't actually have LED's. I believe that they simply use the light from the screen's backlight to illuminate. As near as I can tell, they're only on when the screen backlight is on.
If that is the case, then there probably won't be a way to get them to illuminate when the case is closed, unless someone can figure out how to get the backlight to stay on when the case is closed (which would also be a big battery waster)
Brett
Yup, i can confirm this. I've just removed the cover on the top of the hinge. There is one wrapped cable coming out of the base at the right hand side. This then splits off, the main part goes up into the pivot hole, and a thinner wrapped wire brakes away from this and attaches to a small pcb which has the buttons and the LED's mounted on it.
Yes, the buttons are only illuminated when the backlight is on, but the brightness of the buttons remains constant even when the backlight brightness is turned down.
Cheers
Paul
As far as I see it, even if the backlight has to come on that wouldn't be a problem - after all, the phone is waking up in order to ring. I also often open up the screen slightly to see who's calling, then close it and press the answer button - therefore switching on the backlight initially would actually save time!
Maybe somebody knows of a "wake-on-ring" hack :lol:
I've just noticed it with my new Qtek 9000 and I was very worried, because I thought my device is broken.
But now I know this is "normal", but it's very annoying :?
I wish I had this problem! .. since yesterday my JJ seems to have those lights permanently on even when I switch the device off
Guys, I've made a program that will keep the hinge leds on all the time.
Actually this is an accidental discovery for a program I'm working on for this thread:
http://forum.xda-developers.com/viewtopic.php?t=37201&highlight=
Those guys want to be able to use the keys and phone functions with the lid closed.
I'll post more in that thread, but basically closing the lid puts the hardware keys in a special state such that they are not responsive at all until the device is woken internally (eg by an incoming phone call). Actually, can someone confirm that the hinge keys work when a call comes in but the lid is closed. I presume they must, since they don't do anything else!
So, the hinge lights are on when the screen is on. But the screen is switched off when the lid reaches about 10 degrees to closing. But the hinge lights can be kept on nevertheless
Grem: are you using TCPMP or a similar program to play music etc in the background? Anything that tries to keep the phone "on" when the lid is closed will keep the hinge lights on.
V
Hi vijay555
I've actually just done a complete cold re-boot and reflashed to the original i-mate factory ROM to see if that would help, then came here in search of anyone having a similar issue.
It started yesterday, i suspect I've had an internal meltdown somewhere, plugged it into sync, noticed a few minutes later it had randomly done a warm reset and appeared stuck on the blue i-mate screen, picked it up and the sucker was hotter than an AMD without a heatsink! I suspect it's warranty time for this unit
Grem, that's worrying. What were you doing at the time? What brand/operator etc is the phone? It might be worth posting batch numbers or whatever for people that have this kind of problem so we can identify if some are worse then others.
V
It's an i-mate straight from the wholesaler no particular operator. Had it a couple of months, have seen other reports on the forum here which sound perhaps similar in that they've overheated.

Keyboard backlight time

I know some people wanted to increase the keyboard backlight time. In case this hasnt been posted already, mad monkey has a cab for it:
http://www.dweiniger.com/tips/k-jam.shtml
No i have not seen this posted. tried on my qtek did not work - does it work on your device. i have seen a hack for the universal not wizard
cheers
nope this don't work on the T-Mobile MDA (US model)
Is it supposed to be a DWORD value? Anyone has gotten this to work?
ch4kk said:
Is it supposed to be a DWORD value? Anyone has gotten this to work?
Click to expand...
Click to collapse
No joy here
didnt work either on 2.8
nope - doesn't work
http://forum.xda-developers.com/viewtopic.php?t=38314
You would think someone at HTC would know how to do it. Do any of those guys/girls post on this forum?
not that I've ever seen - not on any of the official retailer sites either. good luck
p.s. the question might not be 'how to do it' but 'can it be done'
yeah, I'm beginning to believe that the whole thing is completely implemented with hardware: a keypress starts a LED "On" timer. This is also why the kbd doesn't illuminate when it gets extended. Even though WM senses this and flips to landscape, it has no control over the backlight: It takes a keypress to start the timer circuit that illuminates the backlight you see.
bummer.
Sleuth255 said:
This is also why the kbd doesn't illuminate when it gets extended. Even though WM senses this and flips to landscape, it has no control over the backlight: It takes a keypress to start the timer circuit that illuminates the backlight you see.
Click to expand...
Click to collapse
Working under the assumption that it is indeed in-hardware, there would've been nothing to prevent the engineers from making the magnetic switch enable the backlight, too
Working under the assumption that it's purely software, there should be nothing to prevent WM5 from doing this... other than that nobody has coded it to do so
Working under the assumption that it's hardcoded in the driver, somebody would have to hack the driver to extend the backlight; adding functionality to turn the backlight on would be a bit more difficult.
ZeBoxx said:
Working under the assumption that it is indeed in-hardware, there would've been nothing to prevent the engineers from making the magnetic switch enable the backlight, too
Click to expand...
Click to collapse
I'll give you "glass half full" on that one :wink:.
However.... the magnetic switch would be more difficult to implement than a simple key press which also resets a timer circuit. You'd have to tie that additional input into a circuit that could be hard-wired with the keyboard itself.
there's my "glass half empty" viewpoint.... I've just got a bad feeling on this one..... sorry.
I guess I'm going to have to take a closer look at some of the disassembled wizard pictures to make up my mind on this.
I sure hope a way is found to fix this as well as control those other blinking leds.....
well the point was, basically, there already -is- a magnetic switch. It's used to signal the OS that the keyboard has extended, and allow it to react on that; the chosen reaction being that the screen orientation is changed.
There would be nothing whatsoever stopping the engineers who actually put the thing together (not talking about somebody taking it apart and tinkering in there and whatnot) to have hooked that up to the backlight control /if/ that is in hardware %)
And if it's in software, then nothing would have technically stopped the software developers from making the keyboard slide-out trigger the backlight that way; assuming they already do as much on keypresses.
exactly. But the kbd does't light up when you extend it you see.... This behavior shoud be obvious
ok weird doesnt even put this into perspective ... i edited that value and softreset my phone. backlight timeout is still 5 seconds and now my bottom ( previously skinned) bar has gone back to default colours ... tried removing the value and resetting again had no effect either ... lovely hack this is now i can try and figure out why the hell this just happened ... running newest official qtek rom only for info
I think this is one of the largest downsides to this device. When I pull the keyboard out the lights should come on AND it should be longer then 5 seconds. It would also be nice if it had a light sensor (like on the SMT5600) to know if the light SHOULD come on or not.
If someone (or HTC) would fix this it would be awesome.
oh, they'll fix it - for their next device models The Universal already works that way, and you can tweak the backlight time. I'm sure by now they've gotten all the feedback they need to decide that that is better than the fixed behavior of the Wizard (not sure who at HTC ever figured that would be a good idea to begin with).

G-off Display

"Description:
With G-off display you can turn off the screen by rotating and holding the phone upside down and holding it like that for a second.
To save battery while listen to your favorite music, simply point your phone downward, light off. All background processes remain.
Require G-sensor found in the latest HTC devices like Diamond / Pro / HD, etc."
Download
Just what I need! but...
Hi
This is a nice app that i've wanted. I know I could use Changescreen as it has a similar feature, but a standalone like this is more preferable for me...
But I just can't download from Rapidshare...
Is it possible to load the .cab here since its only 345kb? or a mirror to somewhere else...
Anyways, Thanks for pointing this App out...
bulletproof_78 said:
Hi
But I just can't download from Rapidshare...
Click to expand...
Click to collapse
I haven't got any problem downloading
thanks a million bro...
Works like a Charm!!!!
Installed on my TP doesnt seem to work and no progam icon to make any type of changes?
great idea. tried on my Omnia, works fine. but screen powers on only with Power button
installed on my touch pro, but doesnt seem to do anything any ideas, would really like to have it working am on WM6.5 if that makes any difference...
cheers!
Installed on my Diamond
it's ok
After a call is not working so
only works after soft reset.
Anyone same problem? solution?
Thejackal_71 said:
After a call is not working so
only works after soft reset.
Anyone same problem? solution?
Click to expand...
Click to collapse
Same problem here. I have to kill it with task manager and run it again It's faster then softreset...
Hello
how about battery drain pls?
not working on HTC Rhodium (TP2) - also I can't see it in programs, etc. Do I need to do anything else after install?
I got a question are there any options? like on conference call (when using loud speakers - device is upside down), will it ignore the g-off? Because I am not sure what would happend if I would press POWER BUTTON in the middle of the call just to get the screen back ..
Not working in my Touch Pro, too
Using latest WinMobile 6.5.21935.
I also did a softreset after installation!
Mashe said:
not working on HTC Rhodium (TP2) - also I can't see it in programs, etc. Do I need to do anything else after install?
Click to expand...
Click to collapse
You don't see it. But it is there. Go to the Program Files and the directory with the same name. Click once on it, and tune the device upside down. It will switch it off.Not ON again.
You can link to it.
I got a question are there any options? l..
Click to expand...
Click to collapse
No options. no nothing! It does work on my TD 1
origin of g-off display
Beware! I am NOT the programmer. I don't know who is either. I just found it.
btw ChangeScreen has a "display off" option too.
worked on the tilt 2
it needs dot net compact framework 3.5 and then it loads on startup... closing the title bar that comes up doesn't seem to stop it from working. however, having said this, i can't say that perhaps the tilt 2 didn't have the behavior before i installed this... it took me a while to realize that upside down doesn't mean face down, which is what i had wanted. but having said that, turning it upside down works great because you can put it in your pocket upside down (which basically you might do anyway).
also, indeed, to get it back on, one has to push the power button. but that's good in case the device moves out of tolerance for downward position it won't be going on and off unintentionally--except that even after the screen is already off it will keep executing--i know this because it vibrates when the screen goes off as well, and if i take it out of upside down position and then put it back without turning screen on again, it will vibrate again. this said, walking with it in a pocket didn't seem to keep triggering it, so overall this is a really cool hack.
now for figuring out why my t2 doesn't turn its speakerphone on when placed face down during a call (i was thinking face down should always turn the screen off by way of proximity sensor--which does work on my device because during a call holding finger over ear speaker turns off the display--just doesn't turn speaker on). wait... just realized... if it did then it would have to assume that just putting it to the ear should turn on speaker. so, i'd say what we have here is a challenge... integrate the proximity sensing with the g-sensor to always turn off the display when face down on a flat, reasonably level surface-- and during a call turn on the speaker too.
if this can be done, then combined with the g-off existing functionality it'd be really sweet--i wouldn't have to turn it upside down _before_ placing it flat on a table while listening to music. and the proximity could help make it less worrysome to just automatically turn the screen back on when picked up.
worked on the tilt 2
it needs dot net compact framework 3.5 and then it loads on startup... closing the title bar that comes up doesn't seem to stop it from working. however, having said this, i can't say that perhaps the tilt 2 didn't have the behavior before i installed this... it took me a while to realize that upside down doesn't mean face down, which is what i had wanted. but having said that, turning it upside down works great because you can put it in your pocket upside down (which basically you might do anyway).
also, indeed, to get it back on, one has to push the power button. but that's good in case the device moves out of tolerance for downward position it won't be going on and off unintentionally--except that even after the screen is already off it will keep executing--i know this because it vibrates when the screen goes off as well, and if i take it out of upside down position and then put it back without turning screen on again, it will vibrate again. this said, walking with it in a pocket didn't seem to keep triggering it, so overall this is a really cool hack.
now for figuring out why my t2 doesn't turn its speakerphone on when placed face down during a call (i was thinking face down should always turn the screen off by way of proximity sensor--which does work on my device because during a call holding finger over ear speaker turns off the display--just doesn't turn speaker on). wait... just realized... if it did then it would have to assume that just putting it to the ear should turn on speaker. so, i'd say what we have here is a challenge... integrate the proximity sensing with the g-sensor to always turn off the display when face down on a flat, reasonably level surface-- and during a call turn on the speaker too.
if this can be done, then combined with the g-off existing functionality it'd be really sweet--i wouldn't have to turn it upside down _before_ placing it flat on a table while listening to music. and the proximity could help make it less worrysome to just automatically turn the screen back on when picked up.
sorry for the duplicate post above--tried to edit, then hit save by accident
edit... i just tried screenchange and it in theory seems to do exactly what i want, but in practice, with 2.78 and any sensitivity level and appropriate no light option checked, it turns off the display even if there is light (and lots of it to be sure). i hold the device upside down above my head and the display goes off. i'm not covering the proximity sensor. my proximity sensor does work when in a phone call. i tried rebooting. i think the proximity sensor may be off somehow on my device...maybe htc only wants it on in a phone call? i will have to see if screenchange will work right with the device in a phone call... further posts will go over with screenchange.
btw, regarding the forum... its annoying that my edit made a whole new post in the first place.
cool!!!thanks

HTC NIKI 100 strange screen problem

Hi to all, i'm new to this forum, i have a problem with my niki 100 20 keys.
I search a lot in the forum for a problem like my but i can't find similar problem.
The problem is very strange, i buy it used.
All work perfectly for the first day.
I try htc hero on sd, all perfect.
I unlock the device, upgraded radio and installed insomniac windows mobile 6.5 without problems and all work perfectly.
After the first day i have a problem on the screen.
If i close the slide, the screen freeze, but the touch screen work because i can tap and launch application, but nothing change on the screen.
If i open the slide the screen appear correctly to the application i lauched when was closed.
With slide open all work perfectly again, touch, calls, suspend/resume.
After 2 days more, the problem go bad.
I have to close/open a lot of time the slide, power off an on a lot of time to have the phone running correctly.
If the screen appear correct and the slide stay open all work.
If i close the slide the screen disappear and i have to open/close and power on/off a lot of time to make it usable again.
At this point i try to open the phone for check the cables.
I found 2 screw unscrewed, one was around inside the phone, the other one was on the magnet of speaker.
The right place for the screw was on the plate under the motherboard.
All the cable was connected correctly.
The touch work always slide open or close
The phone work always slide open or close
The camera work always slide open or close
The screen switch on correctly because i see that the light turn on but it work only web slide open and i have a lot of power on/off to have the image visualized correctly.
Can someone suggest me what can i do?
i hope in gurus of this wonderfull forum
sorry for my english.
i have same problem, maybe is the model help us, how to fix.
for your info, i order the flex cable, as soon as it arrive i make a test and told to you if i resolve the problem.
radio problem
marcoandreacchio said:
Hi to all, i'm new to this forum, i have a problem with my niki 100 20 keys.
I search a lot in the forum for a problem like my but i can't find similar problem.
The problem is very strange, i buy it used.
All work perfectly for the first day.
I try htc hero on sd, all perfect.
I unlock the device, upgraded radio and installed insomniac windows mobile 6.5 without problems and all work perfectly.
After the first day i have a problem on the screen.
If i close the slide, the screen freeze, but the touch screen work because i can tap and launch application, but nothing change on the screen.
If i open the slide the screen appear correctly to the application i lauched when was closed.
With slide open all work perfectly again, touch, calls, suspend/resume.
After 2 days more, the problem go bad.
I have to close/open a lot of time the slide, power off an on a lot of time to have the phone running correctly.
If the screen appear correct and the slide stay open all work.
If i close the slide the screen disappear and i have to open/close and power on/off a lot of time to make it usable again.
At this point i try to open the phone for check the cables.
I found 2 screw unscrewed, one was around inside the phone, the other one was on the magnet of speaker.
The right place for the screw was on the plate under the motherboard.
All the cable was connected correctly.
The touch work always slide open or close
The phone work always slide open or close
The camera work always slide open or close
The screen switch on correctly because i see that the light turn on but it work only web slide open and i have a lot of power on/off to have the image visualized correctly.
Can someone suggest me what can i do?
i hope in gurus of this wonderfull forum
sorry for my english.
Click to expand...
Click to collapse
I think it may be radio problem try to downgrade the radio and see what will happen if not try another rom

[Q] Prevent Accidental Turn-On of HD2

I love my new HD2, except ... when turned off and in my pocket (or wife's handbag) it will nearly always turn itself on. I normally find out too late, after it has made calls or changed settings, etc.
I can't for the life of me understand how anyone would design a device that will turn itself on after a single, gentle, short key press on the power button.
Is there any way (config. setting, registry hack or 3rd party app) that this can be prevented, accepting that a more complex turn on procedure will result?
Hey Steve,
You could take a look at TouchLockPRO from ZuinigeRijder - I use it on my (company issue) Touch PRO which was prone to doing exactly what you're finding with your HD2.
I've got my HD2 cased, so it stays off until I tell it otherwise - there are quite a few HD2 owners who use TouchLockPro although it works differently on the HD2 than it does on the TP due to the lack of touch sensitive button area etc.
I can't remember if, on the HD2, you can disable all the hardware buttons except, say, the volume buttons which you would press in a sequence to unlock it/turn it on.....
Have a look at the thread - all of the documentation is on the developers' site if you some more detailed information - and see what you think. The thread is pretty active still, so if you post a "How do I", you'll likely get a response PDQ
Hope that helps,
Mark.
Mark Crouch said:
Hey Steve,
You could take a look at TouchLockPRO from ZuinigeRijder - I use it on my (company issue) Touch PRO which was prone to doing exactly what you're finding with your HD2.
I've got my HD2 cased, so it stays off until I tell it otherwise - there are quite a few HD2 owners who use TouchLockPro although it works differently on the HD2 than it does on the TP due to the lack of touch sensitive button area etc.
I can't remember if, on the HD2, you can disable all the hardware buttons except, say, the volume buttons which you would press in a sequence to unlock it/turn it on.....
Have a look at the thread - all of the documentation is on the developers' site if you some more detailed information - and see what you think. The thread is pretty active still, so if you post a "How do I", you'll likely get a response PDQ
Hope that helps,
Mark.
Click to expand...
Click to collapse
+1
TouchLockPro is a strong, lite lock! I use it on my Touch Pro2.
Thanks for the prompt assistance, guys, and I have taken a first look at TouchLockPro. Sadly, I'm having issues, though - I have tried the AutoLockOnPowerOn setting but can't get it to work. Not only does it take a good 30 seconds to 1 minute for the BattClock icon to appear after my Spb Mobile Shell has initialised (which gives the phone more than enough time to do its dirty work after accidental switch on) but TouchLockPro doesn't perform the lock as expected - it remains unlocked.
I guess a 'lock after turn on' feature is about the best workaround there is, as the power button turn on probably can't be changed.
I have also now started trialling PocketShield, and its 'lock after turn on' feature does work. I'll continue trialling both products, but if you can suggest how I might make TouchLockPro do what I want I'd appreciate it.
Why not leave it on and lock the screen? That would stop it making calls, although it might not stop the back-light from lighting whenever a button is accidentally pressed.
Personally I keep my phone is a belt pouch. This stops any accidental button presses and, most importantly, protects my phone against damage.
fred_up said:
Why not leave it on and lock the screen? That would stop it making calls, although it might not stop the back-light from lighting whenever a button is accidentally pressed.
Click to expand...
Click to collapse
Because there are many situations when I want it switched off, or am required to have it switched off.
cocospm said:
Because there are many situations when I want it switched off, or am required to have it switched off.
Click to expand...
Click to collapse
Good answer
How about pouching or casing the phone?
fred_up said:
Good answer
How about pouching or casing the phone?
Click to expand...
Click to collapse
OK, OK I guess I'll have to Can't fit a case in my pocket, so I'll work on softening up the leather pouch that came with the 'phone!
cocospm said:
OK, OK I guess I'll have to Can't fit a case in my pocket, so I'll work on softening up the leather pouch that came with the 'phone!
Click to expand...
Click to collapse
I have a PDair pouch (belt-clip type) and there is definately no softening up required.
cocospm said:
I have also now started trialling PocketShield, and its 'lock after turn on' feature does work.
Click to expand...
Click to collapse
I had similar issues especially after handsfree operation while driving...tried pocketshield...liked it and purchased it.
I am fully satisfied with it...

Categories

Resources