Use of buttons while closed - A question for Vijay? - JASJAR, XDA Exec, MDA Pro General

I guess this is one for Vijay, but I'm getting confused as to the situtation with regard to buttons when the clam is shut.
I know there is a bit of overlap with the Torch utility here, but I'd really like the VoiceDial button to work while the clam is shut (plus, I think the upcoming Torch utility would be most useful if it worked while the clam was shut).
What's the current state of play with regard to getting these buttons to work while the clam is shut?
Cheers,
Steve.

StevePritchard: this could go in the old thread really, but you're right, there is an overlap with the torch app (I've settled on "VJCandela"). I did a bit of R&D from the viewpoint of enabling keys generally for both the torch app and VC. I will seek to release VJCandela prior to a full fix and update should a solution be found.
I know it can be done. Let's say this: I've had a very successful negative finding that indicates a possible way to go. I'm seeking an opinion from the Oracle (Buzz) and will then continue with this, probably around the weekend.
V

That's interesting news. Do you think there will be any "issues" with the technique you are investigating, i.e. are you fooling it to think that the clam is open so the screen stays on and reduces battery life?
Cheers,
Steve.

I think it's more like fooling the device into it's thinking its in PDA mode, I use my Exec screen out all the time, and pressing the camera button, or phone buttons wakes the device up no problem, no need to use the power button and the battery life seems to last no problem at all.
I have "turn off device" on batteries after 3 mins
I have even thought about opening it up to find the system it uses to detect screen in as opposed to screen out and seeing if I could disble it mechanically
Regards

gooroo: it's not merely a hardware mechanism. I can already disable detection of the clam closing, to a degree (ie I can't enable external keys yet), as Steve knows. He's used VJElectrify which incorporates VJClamHack (Steve - I've made a better version of this, no reboot required, but not for release until I can do something with it).
However, if the next hack can be pulled off, which is all software based, then it open up interesting possiblities... certainly the perfect clam hack (with full external key access with clam closed) would be possible. But, and it's a but bigger then this one, it depends on a fundamental piece of information/technique I've yet to work through with help from the real brains behind this operation...
V

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).

Haptic touchkeyboard for wm6?

Has anyone made a haptic touch plugin for wm6 devices?
Would love the phone to slightly vibrate when I use the touch keyboard.
I'm on a htc diamond btw.
I think it would be cool too, but I think one of the biggest problems is the time delay between hitting the key and feeling the vibration. I also wonder about the effect on battery life... anyways I would still like to try it!
You might want to do a search because I remember reading about something like this but think it was for the dialer.
I will post here if I find the thread.
-bridic-
Yea I am pretty certain one of the Iphone dialers is haptic or something...perhaps it's a dailer you have to pay for.
I have a couple kinda sorta solutions..
I'm at work so I don't have them here.. But I have one .cab that will vibrate when you press the number buttons on your dial screen, and it work's perfectly. And then I have an .exe that make's every screen tap vibrate, and it kinda sorta work's. I've looked for feedback programs for months, and have found nothing. The best thing i've determined which took me forever, is enabling screen tap sounds, and going into the registry and changing the default sound to vibrate instead.. I can also look up how to do this for you when I get home.. But really there's no good solution out there. On another note this would be almost considered tactile feedback.. Haptic feedback is crazy technology that deals with detecting the electrical current from your touch. That's why current PPC's are awful with this stuff, cause it doesn't have that technology, and most phones that say they do, don't, they just mimic it.
- Walter
Raven1467 said:
I'm at work so I don't have them here.. But I have one .cab that will vibrate when you press the number buttons on your dial screen, and it work's perfectly. And then I have an .exe that make's every screen tap vibrate, and it kinda sorta work's. I've looked for feedback programs for months, and have found nothing. The best thing i've determined which took me forever, is enabling screen tap sounds, and going into the registry and changing the default sound to vibrate instead.. I can also look up how to do this for you when I get home.. But really there's no good solution out there. On another note this would be almost considered tactile feedback.. Haptic feedback is crazy technology that deals with detecting the electrical current from your touch. That's why current PPC's are awful with this stuff, cause it doesn't have that technology, and most phones that say they do, don't, they just mimic it.
- Walter
Click to expand...
Click to collapse
Tnx a lot walter, and thanks for explaining the difference between haptic and tactile
Posting a guide on changing the registry or giving me a link to the two programs mentioned over would be great.
Raven1467 said:
On another note this would be almost considered tactile feedback.. Haptic feedback is crazy technology that deals with detecting the electrical current from your touch. That's why current PPC's are awful with this stuff, cause it doesn't have that technology, and most phones that say they do, don't, they just mimic it.
- Walter
Click to expand...
Click to collapse
uh, not quite sure what "haptic" technology you're talking about, but any feedback of mechanical vibration would definitely be considered "haptic feedback". From wikipeida: "Haptic technology refers to technology which interfaces the user via the sense of touch by applying forces, vibrations and/or motions to the user."
Also, to address concerns a little further up the thread: If implemented correctly, there is no perceptible delay between screen contact and vibration feedback. Me and a couple friends whipped up a little test application based on the WM6 SDK's application template, wherein if you tap anywhere in the application window, the vibration motor is toggled for ~50ms (this can be adjusted based on preference, but 50ms was a nice barely perceptible 'thud' with each tap). The feedback is, for all intents and purposes, instantaneous. Also, since the vibrator is only active for 50ms, you'd need to tap 20 times before you've drained the same battery as a 1 second text message alert, or 40 times for 2 seconds, and so on... really, I think the battery drain would be negligible. Anyway, proof of principle for using the vibration motor for haptic feedback is there, and the affect is quite nice, but we never got much further because of a lack of time and programming knowledge. By the way, if anyone has any information on how to hook into touch.dll (which would be the proper way of implementing a system-wide haptic response), I'd be very interested in hearing about it.
This sounds a very interesting idea! Not every program visually responds to touch when operated with finger, so sometimes I was just left wondering did I make the touch? Did the touch go through? Then one or two seconds later (yes my phone is that slow) something happens. This should help if not eliminate that problem.
Here is the cab for the haptic-esque dialpad if anyone was interested
i've noticed that when haptics is on, it tends to vibrate only every other press
such intensive vibration is probably bad for your phone
a_lazy_dude said:
Also, to address concerns a little further up the thread: If implemented correctly, there is no perceptible delay between screen contact and vibration feedback. Me and a couple friends whipped up a little test application based on the WM6 SDK's application template, wherein if you tap anywhere in the application window, the vibration motor is toggled for ~50ms (this can be adjusted based on preference, but 50ms was a nice barely perceptible 'thud' with each tap). The feedback is, for all intents and purposes, instantaneous. Also, since the vibrator is only active for 50ms, you'd need to tap 20 times before you've drained the same battery as a 1 second text message alert, or 40 times for 2 seconds, and so on... really, I think the battery drain would be negligible. Anyway, proof of principle for using the vibration motor for haptic feedback is there, and the affect is quite nice, but we never got much further because of a lack of time and programming knowledge. By the way, if anyone has any information on how to hook into touch.dll (which would be the proper way of implementing a system-wide haptic response), I'd be very interested in hearing about it.
Click to expand...
Click to collapse
That sounds pretty perfect. Would be nice if someone finished your project.
DiemetriX said:
That sounds pretty perfect. Would be nice if someone finished your project.
Click to expand...
Click to collapse
I've installed this but can't find it anywhere. Looked in programs, personal and settings. I've even looked in the windows folder. I have an HTC Raphael.
Any pointers please...?

Impressions after 3 days with the HD

Pro's:
- screen (size, sensitivity, resolution)
- fast processor + huge storage memory
- Youtube playback (only use WiFi). Very good quality, only few occasional frame rate issues
- very good phone quality (audio)
- can mostly be operated by finger, although sometimes you do need the stylus. To me that's no problem.
- format (seems big, but fits perfectly it in your jeans' pocket)
So/so:
- Opera. At times I like it, other times I don't. Maybe I just need to get used to it...
- HTC keyboard. It works, but could be improved.
- Camera is OK, but not spectacular.
- no D-pad, although I have barely missed it so far
Cons:
- Soft reset button is behind back cover. Haven't had the need to use it yet but I am afraid this may become annoying
- LED in On/off button looks stylish, but now I have to look closely on top of my device, rather than to get a quick glance from a distance to see if I missed any phone calls or messages
- Device isn't entirely 'flat on the back' because of camera, which causes some instability while operating it lying on a table
- Virtual buttons; didn't find a way yet to assign different functions
- Not all software works (eg. HiCalc). But this will only be a matter of time
Haven't tested yet:
- movie playback
- MP3 playback
- GPS
Conclusion: so far I am pretty happy with the HD. Ofcourse it could be improved. But that counts for all devices out there...
Hah... This is EXACTLY how I view the HD... nice sum-up Apart from Opera, I do like it, even when it's a little sluggish at times, but mainly because it's on the HD i like it, the huge screen makes most of the difference.
For the keyboard I use TouchPal. Google it. Love it.
The camera is GOOD in good lighting conditions but VERY VERY bad in poor lighting, so yeah, so-so average.
Oh, I regard Audio playback as so-so, video playback as PRO despite what a lot of other people think (so-so). My movies play like a breeze and it's all super sharp thanks to the screen (use CorePlayer).
GPS is also a PRO... I used to own the Diamond (which also did an OK job at it) and I don't know what they improved but they did, I easily get 8-12 or even more connections in Google Maps almost instantly. No inherent GPS lag anymore either. I confirmed it was there on my diamond and confirmed it wasn't there anymore on the HD. Except in Google Maps, there is a slight delay, but that has been commonly agreed upon as an issue in GM and not in the HD.
For the soft reset.....
You can either just power down the device (press and hold power button) and then power back on. It's the same as a soft reset.
or...
I use PHM power toys (they are free) and once installed you get a soft reset program icon. Stick that in the program section of touchflo and no need to take the back off
donzx6 said:
You can either just power down the device (press and hold power button) and then power back on. It's the same as a soft reset.
or...
I use PHM power toys (they are free) and once installed you get a soft reset program icon. Stick that in the program section of touchflo and no need to take the back off
Click to expand...
Click to collapse
Er... if the phone freezes, then the power button doesn't work - so you need to hit the soft reset button.
I'd like to be able to turn off/change the function of the volume buttons - too easy to accidently press them - and they are very sensitive. When you want to change the volume they seem very nice, tactile and smooth, but they're just too sensitive when you don't...
donzx6 said:
You can either just power down the device (press and hold power button) and then power back on. It's the same as a soft reset.
Click to expand...
Click to collapse
I'm the guy who sand-papered the faceted back of his diamond, so for me - drilling a small hole in the back cover to uncover the soft reset button would also be an option.
Thats a good point monkeyboy....
....I'll get me coat
I have used the GPS with TomTom 7 and works like a dream.
Tip: Use Quick GPS to download data first - last for 6 days.
I migrated from Trinity to this phone and have never looked back apart
from the camera - is there a way to stop the 3 second delay and take instant photos without autofocus on -perhaps a reg hack?
Hawk
I have used the GPS with TomTom 7 and works like a dream.
Tip: Use Quick GPS to download data first - last for 6 days.
I migrated from Trinity to this phone and have never looked back apart
from the camera - is there a way to stop the 3 second delay and take instant photos without autofocus on -perhaps a reg hack?
Hawk
thats the funny lol
losdrivare said:
I'm the guy who sand-papered the faceted back of his diamond, so for me - drilling a small hole in the back cover to uncover the soft reset button would also be an option.
Click to expand...
Click to collapse
i cant believ you would actualy do that mate thats realy funny but if you did that wont that cause dust to go into your device and cause damage and how would you sell it of
Hah I still can't believe you sandpaper the back of the Diamond roflmao
But of course he takes the cover off before drilling a hole into it, makes sense don't it
well I am on day two .. its an up and down relationship. One thing doesn't work .. find a how to sort it .. another thing comes up. I wouldn't say that is a phone for the masses.
Day 2 for me and so far:
Pros:
The screen is amazing for ebook reading. Much bigger, clearer & sharper than my Prophet.
I didn't actually realise there was a radio, but it works really well.
The Teeter game is amusing and fun to show off with.
The GPS is very accurate and, because I walk/get the bus, it doesn't need huge amounts of maps, so data's not too bad.
Cons:
TouchFLO has gone. It was too slow for me (no nice run-finger-along-to-scroll)...
No D-pad meant I had to rebind the volume keys to up/down - they work fine now.
The Opera browser doesn't always register my clicks on the links.
I'm very happy with it so far. It does everything I need (which is simple - phone, ebooks, music player!) and does it well with extras. Husband doesn't like it because he likes physical keyboards, but hey!
Xarra said:
... Husband doesn't like it because he likes physical keyboards, but hey!
Click to expand...
Click to collapse
Take it that goes under the 'Pros' heading then
Day 3 for me too, so I thought I'd share
Pros
blimey - where to start?!
This is my first WM device (see Cons), so pretty much everything is a bonus - but stand out moments have been:
YouTube on the move - I'm not a huge YouTube fan (or at least I wasn't), but I can now while away my time whilst taking a coffee / fag break from work. Beats picking up a book and reading 3 pages before having to put it down.
GoogleMaps. No huge use for me as satnav (got that built into the car), but lots of fun already showing it off to mates LOL
Lots of techy tweaking to be done (yes, I am a Geek at heart...)
Onbviously at lots of this is down to the size and quality of the screen - the main reason that this is my first WM device was being put off by trying to browse etc on a screen the size of a large stamp - the HD size (for me) is about the best compromise - big enough to read, small enough to fit in the pocket.
Cons
becuase it is my first WM device, I'm still trying to desperately get my head around it all!
Getting there though
Congrats on your HD!
Half my friends group has the iPhone, the rest, well, something else. Then I got my HD and lots of them ordered it too, so now it's 4 HD's My father and brother both got the Diamond, and at work many of my colleagues have some version of HTC phone ranging from the TyTNII to the Touch Pro... These things pop up everywhere...

[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