I'm mad!
bloody buttons don't work if you close the lid. anyone knows a hack?
You probably have to go to buttonsettings in you settings
Go to Locktab and select "Do not lock buttons"
good luck
Locked buttons
Try Start / Settings / Buttons 'Lock'-tab and select 'Do not lock buttons'
I've already done this. it works if you leave the LCD screen open, or if you close the lid flipped (lcd out) but if you close the lid with lcd screen inwards, the buttons stop working.
shafa said:
I've already done this. it works if you leave the LCD screen open, or if you close the lid flipped (lcd out) but if you close the lid with lcd screen inwards, the buttons stop working.
Click to expand...
Click to collapse
Same here and it makes useless the Voice Speed Dial feature
really stupid...
is it every one's problem or just some of the devices have this "feature"?
shafa said:
is it every one's problem or just some of the devices have this "feature"?
Click to expand...
Click to collapse
I have a MDA Pro from T-Mobile Germany and I have the same Problem. Voice Dial not available, if the MDA is closed! :evil:
Yeh, I have a T-Mobile MDA Pro with the same problem.
It's rather silly because it's not just voice dial I want to use - PocketMusic which is my preferred music player doesn't get the button presses if I close up the device...
Could it be a firmaware issue? Is that a WM5.0 Problem? Like the missing A2DP Support on BT Stack? The last point is very awkward for Microsoft.
There is a program, PQzII, what enables you to bind programs to buttons, and it does the magic trick: you can use buttons when the device is closed. BUT there is a problem with that it only works after a soft reset, until you switch off and switch on your device.
I think there is a service what loads when the device boots up, and when you switch it on, like the service, what checks if the device is opened, and rotates the screen.
The screen rotating-service can be stopped, so you can prevent it from rotating, so I think we could do it with the device-closed-button-locker-service
-working on it.
Only want to control my media player with the volume slider, in my pocket, when the device is closed. (I have been using my Universal without any case in my pocket for 2 months, and it is in perfect condition)
Related
Is there really nothing can be done to prevent my JJ from blocking all the keys while closed? I just want it to switch the screen off and that's it.
I'm using the buttons to skip and pause the tracks in TCMP but I have to keep it with the screen out, otherwise it doesn't work. And it's a huge advantage for me to be able to close it.
Help! Please :wink:
Guys, don't put me in with Buzz, the more I read Mamaich, Buzz, Toenailed and other guys' posts, the more I'm embarrassed into thinking I'm just going to stop developing. Those guys are geniuses, I'm just a monkey with a typewriter, almost literally... (I'm quite hairy!)
I didn't know this was a problem. I'll try to investigate. If this is a hardware switch we'll have difficult overriding it, but isn't it possible to answer the phone with the red and green key on the hinge? If so, we should have no problem keeping the system alive but closed.
V
The green and red button are not working until there is an incoming call.
Fixing that would also help to start the voice dialing while the JJ is closed, which is impossible atm.
I keep my fingers crossed!
That's easy then. Have a background program to provide a notification to "wake" the system up while the lid is down. Use code to override the timeout so the system stays on until you open the screen and close the app. Anyone else want to program this? :wink:
V
vijay555 said:
That's easy then. Have a background program to provide a notification to "wake" the system up while the lid is down. Use code to override the timeout so the system stays on until you open the screen and close the app. Anyone else want to program this? :wink:
V
Click to expand...
Click to collapse
Yupp, sounds like a piece of cake to me ! LOL
Man, I'd love to know how to prepare stuff like that, but unfortunately I have to rely on others... 8)
I just had a one more thought - don't you think that keeping the system "alive" and only switching the screen off while the lid is down would fix the problem of this huge delay between receiving a call and being able to hear it after pressing the button? Maybe it takes so long exactly because the system needs to wake up and activate the buttons? (sorry for my lame computer language :wink: )
I imagine it would. Just test: how long does it take to answer the phone with the lid open and screen on, and likewise but with lid down and off?
I'm sure others have tested already, but you could quite easily keep the system powered on but screen off, with the lid down, and battery usage should be relatively minimal (most battery saving techniques would be available to the OS, other than actually suspending the OS. Again, check battery life by running TCMP etc, enable screen blanking and leave the sytem on for some hours).
This should enable you to do anything you can do with the lid open, so I imagine voice dialling would work.
But you're sure the phone responds when someone calls and you press the hinge buttons? I'd imagine it would. So this sounds feasible in theory :shock:
V
Yeah, the green and red button work with the lid closed, but only when there is an incoming phonecall.
I don't really mind a bit shorter battery life, I just don't want use a screen protector, It spoils all the beauty of that screen. I use TomTom while riding a motorbike, just listening to the instructions, and that automatic "sleep" is a problem in that case as well because it disconnects everything when I close the lid to put the JJ in my pocket.
So, who'll write the program?
If no one else jumps up, I'll do it, but I'm quite busy right now...
V
PS. it'd solve your tomtom problem as well.
That's bad news about the automatic sleep. With my XDA2 I used to switch it off and TomTom would continue to make announcements until I actually exited the program. Unfortunately I haven't the time to write the program right now... sorry (I'm not claiming to be a genius by responding in here, by the way). :lol:
Why not buy a Martin Fields screen protector? You can still see the screen with one of those (if you can get all of the effing bubbles out of the blasted thing).
OK, I'm waiting impatiently then!
Thanks a lot!
I wonder whether this application would also allow you to use MS Voice Command when the lid is shut Also, such an application would perhaps stop my Bluetooth radio from switching off when the lid is closed?
As discussed above, the program would keep the device awake in the normal sense, so anything you can do with the lid open you can do with the lid closed. Hence, voice dialling, tomtom, music player etc.
An idea would be to map the external red/green button for mp3 playing, so eg press green = play/pause, press red = next track, double press = previous track etc. So mp3 playback with lid closed but under control...
I was working very very late yesterday so I didn't do any coding, but I need to investigate if there is a hardware switch for powering off when the lid is closed and if it can be overridden... otherwise it will power off the device briefly before powering on again, which would be inconvenient for gps and bluetooth. However, all theoretical for now...
V
The ability to run MS Voice Command with the lid closed would make the JJ almost perfect Currently (with all auto off featured disabled) when I use my BT headset to make a call with the lid closed I do get the acknowledgement 'bleep' from VC but it does not actually action the request
If you could solve this one I know it would make a lot of people very happy. Good luck!
Hi Vijay!
You don't have to worry about the button mapping coz the TCMP is already doing that, you can assign the buttons for almost any functin desired. The only problem is that it doesn't work coz all the buttons are locked :wink:
rottie: I wasn't proposing to do the button mapping, merely the suggestion of how the system could be used if it works as envisaged.
So it looks like no one else is writing this then? I'll see what i can do, but if anyone else is, please shout out so I don't duplicate efforts!
V
Just to remind my humble request... :wink:
Another thought here.. WIth the device closed and the screen off the green and red buttons would not be lit up, this is a major pain in the ass as in the dark you can't tell quickly which is which.... could this be solved.
rottie: I'm very very busy on VJOKButt for now. Fighting with TAPI.
As I said I won't be able to look into this for a while, so if anyone else can code it, please do. I've left my thoughts above on how it should be feasible.
steverae: with the hack proposed, all lights will light in the normal manner, so if the buttons are backlit with lid up, they'd be backlit with this hack as well, lid closed.
V
Hey VIJAY555, This "Hack" sounds like it could be the holy grail to end all our universal woes.... now just have to get one of you guys to fix PocketVCS for me..... it doesn't wanna play on my universal.
Keep us all informed V
Guys, I'm working on this (slowly). It's called VJElectrify.
Can anyone confirm if the Exec hinge red and green buttons work with the lid closed? Either for the phone or otherwise. I think, as rottie says, that for now they only work when a call comes in.
My findings are unfortunately that closing the lid activates a special mode switching off the screen and all hardware keys. The hardware key override needs to be overridden.
I've fixed steverae's problem so far. This might already be enough to activate bluetooth MS Voice Command, I have to test it. I think it should also fix XDAII's issue of bluetooth switching off. Will test tonight.
Does anyone know which driver or device is responsible for the keyboard/hardware keys?
V
When playing a file using TCPMP, close the Jasjar (Universal), the screen and the keyboard will go off. But the external 2 keys (red and green ones) stay on.
Anyway to keep them on?
Come on guys !
I think they are lit up by the backlight no?
It has already been confirmed that there are seperate led's for the answer and hang up buttons, although they do seem to go off at the same time as the back light this is only because they are programmed to do so, not because they share the same led's.
How come they stayed on and the backlight off then?
Guys, the external keys are lit by the same juice that powers the screen and the keyboard. I wrote a hack to provide this functionality already in one of the other threads on this issue. However, keeping the keys functional will the clam closed is a harder problem.
V
vijay555 said:
Guys, the external keys are lit by the same juice that powers the screen and the keyboard. I wrote a hack to provide this functionality already in one of the other threads on this issue. However, keeping the keys functional will the clam closed is a harder problem.
V
Click to expand...
Click to collapse
But the lid was CLOSED and the screen was off, and the external keys stayed ON
How? It never happens to me.
The external key lights can be forced to stay on with the same code used to keep the backlight on. However, forcing the backlight on, but then turning the screen off (ie by closing the clam while TCPMP or VJElectrify etc is running) then the screen is off, but the external keys stay lit up.
SooSpecial: when the lights on, are they responsive to clicking? eg, pressing the external green key - will you go into phone mode with the clam down? Try using AEButtonPlus and assign an app to the red and green keys. Put the clam down. Do the red/green keys respond?
V
How does TCPMP get to leave them on?
It's technically possible then
SooSpecial. Can you use the keys for anything with the clam down? Do they do anything? Are you assigning functions to them in AEButtonPlus and/or TCPMP and they're responding to presses with the clam down?
As I've said, keeping the lights on with the clam down is easy. Getting the device to respond to them with the clam down is harder AFAIK.
V
Vijay, they don't respond with the lid down. Doesn't matter assigned or not.
That's what I'm crying about all the time... :wink:
rottie :roll: exactly. SooSpecial seems to suggest that the keys do something with the clam down. I've not managed to get anything out of them so far. I know it's possible (because the phone app does it), but I need to discover what kind of notification the phone generates in order to re-enable the keys. I need some new tools that I'm trying to chat with Buzz about, before I can make much more progress...
But as I said, keeping the buttons lit up is easy. Enabling them to do something is harder...
V
vijay555 said:
rottie :roll: exactly. SooSpecial seems to suggest that the keys do something with the clam down. I've not managed to get anything out of them so far. I know it's possible (because the phone app does it), but I need to discover what kind of notification the phone generates in order to re-enable the keys. I need some new tools that I'm trying to chat with Buzz about, before I can make much more progress...
But as I said, keeping the buttons lit up is easy. Enabling them to do something is harder...
V
Click to expand...
Click to collapse
Hello vijay555, All!
Neither AEButtonPlus nor TCPMP cant cath these buttons, and all other (like sound volume) with the calm down.
Also, regarding the TCPMP, it would be very usefull to assign the wired head set "Answer\Hang" button to the, let say, "Next track" function of the TCPMP. Is that some how possible?
As far as I have investigated:
- this "Answer\Hang" button is not treated as a hardware keyboard button, and it should use it's own driver? (physically, this button works by a short cut of Ground and Mic, and the device treats this as the "Answer\Hang" button click);
- the Answer and Hang external buttons works with the calm closed to answer\reject the incoming call. So, the Phone app can access them with the calm closed;
BR, Dima_the_chief
dima_the_chief: progress has been made on the external key hack... it's being tested. But it will hopefully be everything we need it to do. I don't know why HTC ever made the decision to disable this.
V
vijay555 said:
dima_the_chief: progress has been made on the external key hack... it's being tested. But it will hopefully be everything we need it to do. I don't know why HTC ever made the decision to disable this.
V
Click to expand...
Click to collapse
I'm guessing it's to prevent unwanted button presses when the Exec is in your pocket, or as you pull it out of your pocket...
Cheers,
Steve.
But why not make it optional? :roll:
The Wizard has enough fun waking itself up as you pull it out of its holster, so why not permit a useful feature? Sigh.
V
vijay555 said:
But why not make it optional? :roll:
The Wizard has enough fun waking itself up as you pull it out of its holster, so why not permit a useful feature? Sigh.
V
Click to expand...
Click to collapse
Agreed.
Cheers,
Steve.
This is a wonderful idea. Here is what I notice about those green and red phone buttons on the hinge:
It has a separate light than the screen backlight and the keyboard backlight. Why? I noticed everytime I perform a soft reset while charging, the 1st thing that will come on is the screen backlight. After a few seconds, you will notice the screen backlight becomes brighter and with it the green & red phone buttons on the hinge also lits up. So maybe the key lies in a similar application that Vijay developed before, I believe VJLumos? You guys can try and soft reset while the Universal is charging and watch closely the screen backlight and the green-red phone buttons.
cktlcmd: guys, we've managed to isolate the "issue" with controlling the external keys with the clam closed (much of this was not my work, it's the work of a genius), so eg I'm using VJCandela with the clam closed. I presume this should extend the whole distance, full control of TCPMP etc with clam closed. No reason why not.
However, the solution is still being tested and tweaked. No further discussions on it for now, don't want to get anyone excited before time. Parts of VJElectrify are part of the solution.
V
vijay555 said:
cktlcmd: guys, we've managed to isolate the "issue" with controlling the external keys with the clam closed (much of this was not my work, it's the work of a genius), so eg I'm using VJCandela with the clam closed. I presume this should extend the whole distance, full control of TCPMP etc with clam closed. No reason why not.
However, the solution is still being tested and tweaked. No further discussions on it for now, don't want to get anyone excited before time. Parts of VJElectrify are part of the solution.
V
Click to expand...
Click to collapse
WOW!!! This IS a great news!!!
Our great thanks and donations to all you, genious!!
Is there a way to disable the answer/hangup buttons when the screen is turned off during a call? i keep accidentally hanging up on people
lol...okay
if you install a program called MortSaver it can turn off the screen and lock all buttons, except the button which de-activates it. you can activate mortscript by either assigning it to a hardware button or by simply launching the programs. if you wanna use it for your phone calls, i think you'd be more comfortable by assigning it to a hardware button. to me, i wouldn't give up one hardware button to mortsaver.
hopefully this will solve my automatic answer when taking the phone out of the holster to check whose calling...
thanks
thanks for the tip. ive read about this app in several threads, never thought to use it for this purpose.
thanks again
My phone is always waking up for odd reasons (AVRCP commands, switching in and out of roaming, etc...), and I can't seem to get the darned thing to stay OFF.
Music A2DP streaming is the biggest deal to me, because not only will the device wake up when I press a remote command (on my AVRCP headset), it will also keep the device backlight on indefinitely. This is clearly shortening my battery.
I tried Slide2Unlock, and have it set to shut off the display if no activity for 5 sec., but the problem is that Slide2Unlock appears to not notice when it is woken up, and just sits there without turning the screen back off again! (a simple screen press brings Slide2U back to life, and then it will toggle the screen... but this defeats the purpose!)
There must be SOMETHING I'm missing here... doesn't anyone else have this problem???
I have 2 things for you. The first, is if you're using WM6 that's a known issue and unchecking the today timeout in start-->settings-->today-->items tab should solve most of your problems. The second is a little program that I found (not sure where at , but it might have been on here) called screen off. Install it and then set it to a hardware button and it will allow you to turn just your screen off whenever you don't need it on.
Maybe it depends on the player you're using? With Coreplayer, my phone's screen just flashes on and off quickly when it receives an AVRCP command.
Still doesn't explain the roaming thing though.
xeno1 said:
I have 2 things for you. The first, is if you're using WM6 that's a known issue and unchecking the today timeout in start-->settings-->today-->items tab should solve most of your problems. The second is a little program that I found (not sure where at , but it might have been on here) called screen off. Install it and then set it to a hardware button and it will allow you to turn just your screen off whenever you don't need it on.
Click to expand...
Click to collapse
Yes, I'm using WM6 on a HTC Titan (Sprint Mogul).
I don't currently timeout to the today screen, but I don't see how that would cause my problem really- I've heard people mention that before, so can anyone explain what difference that would make?
I already have a shortcut to screen toggle (wrote my own MortScript to do it). That's not a problem anyway since every media player can assign a button to toggle the screen- The problem is that it keeps turning the screen back on when a button is pressed no matter how many times I toggle!!
Plastriq, I've heard that coreplayer does that... that's how they deal with this problem. They're the only ones that have addressed it as far as I know, and I'm not about to pay for their app when I already have TCPMP and WMP for free.
I just can't believe that there haven't been more practical ways around this yet!
I love my Piel-Frama case. I got the cowskin in blue.
http://www.pielframa.com/menu_htc_tytn.htm
However, the cover activates the touch screen. I was talking to my boss while walking down the street, and it made a note the call history that looked like a hand giving him the finger.
How do you guys deal with covers that touch the touchscreen? If I have a bluetooth headset, I want to walk and talk but the screen goes crazy!
this can't be an unusual problem. i must be missing something easy and simple. If your case covers the screen of your phone, and you are walking and talkng on your bluetooth wireless headset, doesn't the touchscreen get activated by your case!??!
Lock the device before putting it in the case..
Locking the device involves a password. I toggle the device off with the off button (not completely off -screen off) but it must be that the off button gets activated by the case as well, cuz often when I open it back up I have flipped screens and drawn notes by walking...am I the only one with this problem?
twinpeaks said:
Locking the device involves a password. I toggle the device off with the off button (not completely off -screen off) but it must be that the off button gets activated by the case as well, cuz often when I open it back up I have flipped screens and drawn notes by walking...am I the only one with this problem?
Click to expand...
Click to collapse
Doesnt involve a password on my Hermes...
I got a lock button then i press the unlock softkey and tap the screen where it says unlock
twinpeaks said:
Locking the device involves a password. I toggle the device off with the off button (not completely off -screen off) but it must be that the off button gets activated by the case as well, cuz often when I open it back up I have flipped screens and drawn notes by walking...am I the only one with this problem?
Click to expand...
Click to collapse
Buddy, read your Tytn's manual. Nobody advises you to lock your device with a password/number combination. That would be time-based. Many people here including me don't just press the off button to switch the display off but use the default (or third party app) devicelock functionality. You can even use this as a today screen plugin. Press it and once off your device will only accept input via on-button and an unlock-button afterwards on the todayscreen.
Of course people prevent their phones from making accindental phonecalls etc. You should have noticed that function from beginning on however, because this is a default today plugin when you're using your device for the very first time.
Good luck
OK, i had a hard case for the last 8 months and switched to a soft one. At some point I had taken out that lock button thing. It's kind of small to activate, but, I'll live with it