Related
Hi guys,
I upgraded my phone a while back using c_shekhar's excellent ROM. I've just come back to using the phone again and after charging the phone up from completely dead I now get no buttons on the phone dialler skin. If you use the stylus where the buttons should be you do hear the keypad tones, just there are no visible buttons. I've tried several things, such as changing themes and resetting the phone (although I cant remember how to hard reset the phone) but none of this has worked. Anyone had this, or have any ideas? I did search the forum and found loads of posts on buttons and screens but nothing to help me out.
Cheers
There is a soft button (bottom left) when you are on the dial page that says keypad. Is that still there? I assume you have already checked this and pressed it, but perhaps not. It may have been renamed due to the skin you are using, removed, or perhaps you changed it yourself at some stage accidentally.
Let us know if this helps.
There is no keypad soft button. However, if I just hit random places where the buttons should be, and then press the physical call button, the phone dials the number and then the keypad soft button appears (although just the text appears, not the button itself).
Is there a way to hard reset this phone with the WM2005 ROM? I have tried what used to work on the factory installed O2 ROM (holding the power button and using the stylus to press the reset button), but this doesn't seem to do the trick as all my details and info are still there when it fires up again.
I have also taken the battery out and left it for a couple of days to let the backup battery die too. This hasn't helped.
it appers that the dialer is corrupted..try to hard reset else try other Dialer skins..search the forum's for them
Hey guys, thanks for the help in advance! I have had my tp for 2 weeks now and i love it... i did install a few things like a cab for improving battery life found on ppc geeks website, i also edited the registry to allow me to tether it to my laptop, changed sending text messages so the annoying text sent message doesn't pop up, and finally changed the reply all to just reply when replying to email messages. aside from that i've installed a few apps like google maps, sensorlock, the flip clock (which i removed), fring, tiny twitter, and a weather database editor for the weather thing....
ok now that's all out of the way... somewhere along the way i've lost the ability to change the volume using the hardware buttons. when sitting at the home screen if i press the volume up, the big volume thing opens with the 2 options at the bottom for vibrate and silent, but if i press the volume up or down again, this screen dissapears and does not change the volume. i am still able to change the volume using my finger or the stylus, but this is annoying if i'm on a call or using my bluetooth headset.
i noticed yesterday that if my volume is all the way up and i press down on the volume button, the volume screen goes away like it has been, but highlights the clock, if i press it a few more times it highlights the next thing down (the call log) and again it selects the upcoming calendar events... eventually it minimizes the clock alltogether... this also happens when i press the arrow down.
i'm positive this has something to do with a registry hack or something i've installed, but i have finally got everything setup the way i like it, is there any way this feature can be restored??
bonneyt said:
i'm positive this has something to do with a registry hack or something i've installed, but i have finally got everything setup the way i like it, is there any way this feature can be restored??
Click to expand...
Click to collapse
Well you know the problem. You have two options. Hard reset or find the specific tweak or App that fiddled with the volume buttons.
Did you install anything like AE Buttons plus or anything else?
no, i haven't installed anything that affects buttons. i did do a hard reset, and installed only the things i knew work. everything was fine so i decided i would try a registry trick to allow me to use my tp as a means to access the internet... it worked fine but then i got a call and attempted to turn down the volume and it didn't work again.
i guess my question is, what/where is this controlled? is it something i can re-install? is there an alternative i can install?
bonneyt said:
no, i haven't installed anything that affects buttons. i did do a hard reset, and installed only the things i knew work. everything was fine so i decided i would try a registry trick to allow me to use my tp as a means to access the internet... it worked fine but then i got a call and attempted to turn down the volume and it didn't work again.
i guess my question is, what/where is this controlled? is it something i can re-install? is there an alternative i can install?
Click to expand...
Click to collapse
What happened when you tried to turn down the volume. Please be very specific. The small details will matter on this one.
But one guess... You dsisabled the phone skin.
ok, when pressing volume down one time the volume screen comes on (this is the touch flow 3d volume thing) if i press volume down again to decrease the volume, the screen previously mentioned goes away and highlights the first today screen item, in this case it's the clock.
i have done some troubleshooting of my own... it doesn't seem that it's caused by anything i've installed or tweaked... i did a hard reset, and didn't install anything but went straight to the internet sharing app that comes installed on the tp. i tried to connect with usb, it failed and gave an error message (this is to be expected) but now i can't use the volume buttons... i've narrowed it as far as i can. i can do another hard reset, install all my apps and tweaks again and just avoid the internet sharing piece, but i kindof want that to work too. i would be satisfied to just fix the volume button problem and not try the internet sharing again if it's possible
edit: if the phone skin is disabled, how would i go about re-enabling it?
edit2: i did another hard reset, again didn't install anything this time... i decided i wanted to browse the internet, so i opened opera and it gave me a connection error (i'm in roaming) i dismissed the error and at the same time lost the ability to volume up and down............ any ideas?
Just an update in case anyone was following this
the dialer skin and the volume thing are totally seperate, i know this becuase i went into the registry and disabled the dialer skin to show the winmo default... the volume skin/app stayed the same.
i contacted htc support, the guy i spoke with claimed it to be a hardware issue... i refuse to believe that. this is clearly a software issue/bug
when doing a soft reset i can hit the hardware volume keys up and down before everything finishes loading and the default windows volume sliders appear and they work, but whenever the other volume program loads i can't get back to the windows default.
any help is greatly appreciated, i really don't want to replace my phone for something i know isn't a hardware issue
thanks for all the help but... i have figured out the problem... .net framework 3.5 is what's causing the volume "skin" to stop working... this is installed by default (at least on my phone) and is required to run certain apps (also previously installed)... i've notified htc... they said woops and that's about it
i was able to remove it or at least disable it with the tech's help, some apps wont work and i've noticed the weather app works sometimes and other times not at all. so if anyone else in the world is having this issue... get rid of .net framework v3.5
edit:thank you scrosler, for being the only one that even attempted to help me, you pointed me in the right direction!
i am having the same problem. i'll have to try removing the .net framework and see if that fixes my problem.
i should probably first figure out what apps are going to break if the framework is removed....
I am experiencing problems on both mine and my wife's Fuze with any ROM that has the Slide 2 Answer. If the phone is on sleep, I can't answer an incoming call after the first ring either using the S2A slider or the hard key. I can slide the slider, but the phone doesn't answer. If I answer the phone on the first ring, or when the phone is not in sleep, I can always answer the phone.
I can always reproduce this with any Slide 2 Answer dialers.
1. Put your phone in sleep.
2. Call your phone
3. Wait until after the first ring, i.e. answer on the 3rd ring.
4. Use either the S2A slider or the hard answer key.
5. Phone won't answer, and the phone goes to voicemail.
This is on both of my Fuzes, different ROMS with S2A dialers, and yes, I have reflashed and hard reset numerous times, without installing any new software after a flash. The regular dialer works fine.
Anyone else have this problem?
ragpaoa said:
I am experiencing problems on both mine and my wife's Fuze with any ROM that has the Slide 2 Answer. If the phone is on sleep, I can't answer an incoming call after the first ring either using the S2A slider or the hard key. I can slide the slider, but the phone doesn't answer. If I answer the phone on the first ring, or when the phone is not in sleep, I can always answer the phone.
I can always reproduce this with any Slide 2 Answer dialers.
1. Put your phone in sleep.
2. Call your phone
3. Wait until after the first ring, i.e. answer on the 3rd ring.
4. Use either the S2A slider or the hard answer key.
5. Phone won't answer, and the phone goes to voicemail.
This is on both of my Fuzes, different ROMS with S2A dialers, and yes, I have reflashed and hard reset numerous times, without installing any new software after a flash. The regular dialer works fine.
Anyone else have this problem?
Click to expand...
Click to collapse
I have the slide dialer in my rom. I have never seen this. The only issue with the dialer I have ever had is the delay between incoming calls and the actual audible ring starting. I can answer on any ring under any circumstance. I rarely answer before the third ring.
FYI it would have been best to post this in the software forum in one of the many dialer threads.
Thanks arup for your quick response.
I'll keep digging and see what I can find out. Weird thing is that this is on both Fuzes.
This issue should be posted in the thread for the roms you are using or the many threads related to the dialers. Also it is posted in the wrong section. This is not a Rom Development topic. Please put more though into what you are going to post in the future, especially if it involves starting a new thread.
InCall Lock will temporarily disable Send (aka Talk, Green) and End (aka Red) hardware buttons when you receive an incoming call in order to prevent accidental call pickups/rejects while you are pulling your device out of your pocket. All other hardware buttons are untouched.
After you answer/reject your call the application will release the buttons, so you will be able to hang up, put calls on hold etc. using hardware buttons normally.
The application, after being launched, will remain resident in memory but will not use any CPU cycles at all as it relies on WM Notification system and doesn't do any polling. As it is using WM internal event system, it should work regardless of OS language, installed dialer etc.
This is a zero config application and has no options (yes, this is a feature). I personally needed an application that would do just this - temporarily block these buttons. If you need a device locker, try PocketShield or other available solutions.
How to use:
Install attached cab
Soft reset or launch "InCall Lock Toggle"
To enable/disable InCall Lock temporarily, use InCall Lock Toggle in your Programs menu.
To disable it permanently, just uninstall via Settings - Remove Programs
Requires .Net CF 3.5
Important note for HD2 users: the application won't lock the Send button on this device for some strange reason. If you want to lock it, you'll need to copy phone.lnk from \Windows\Start Menu\Programs to \Windows and rename it to long_send.lnk.
Known issues: the application will also lock the wired headset's answer button. There's no solution for this problem as of yet.
Important note: Unfortunately I cannot support this project anymore because of time constraints and the fact that I don't use a WM device anymore. I'm uploading the source (see attached zip file) so that somebody can develop the thing further. Thanks for understanding and all the positive feedback I've received!
vangrieg said:
InCall Lock will temporarily disable Send (aka Talk, Green) and End (aka Red) hardware buttons when you receive an incoming call in order to prevent accidental call pickups/rejects while you are pulling your device out of your pocket. All other hardware buttons are untouched.
Click to expand...
Click to collapse
Thanks. I installed this earlier and just had my first call with it. Seemed to work perfectly.
Hmm... It doesn't seem to work on Topix 2.9.3. It has the Rhodium dialer. Can this be the culprit?
PS: I've only tested it on outgoing calls so far.
Dmitry N said:
Hmm... It doesn't seem to work on Topix 2.9.3. It has the Rhodium dialer. Can this be the culprit?
Click to expand...
Click to collapse
No, it works with low-level keyboard hooks and WM Notifications so it should work on any device with WM5.0 and later.
Dmitry N said:
PS: I've only tested it on outgoing calls so far.
Click to expand...
Click to collapse
It only locks keys only when your phone is ringing, so it shouldn't even do anything on outgoing calls. It releases keys immediately when you answer or reject a call.
vangrieg said:
It only locks keys only when your phone is ringing, so it shouldn't even do anything on outgoing calls. It releases keys immediately when you answer or reject a call.
Click to expand...
Click to collapse
Ha, my bad! OK, thanks for the app. It DOES work!
confirm: work great with touch HD, must have!
Congratulations. It works nice¡
Several apps lock the keys during the incomming call. The touch HD needs to lock the virtuial HW keys during an incomming call AND during a call.You can use the power butten to unblank the screen then use the screen controls to end a call.
This will prevent hangups when using a bt head set and the phone is in your pocket.
apeko said:
Several apps lock the keys during the incomming call.
Click to expand...
Click to collapse
Well, maybe, but they usually come with something else I don't need (i.e. Pocket Shield or LML) or have bugs I can't live with (i.e. Pocket Shield continues to vibrate on incoming calls after I pick up the phone).
apeko said:
The touch HD needs to lock the virtuial HW keys during an incomming call AND during a call.You can use the power butten to unblank the screen then use the screen controls to end a call.
This will prevent hangups when using a bt head set and the phone is in your pocket.
Click to expand...
Click to collapse
This has never happened to me, and I don't like the idea of locking buttons permanently (I use Green button to put calls on hold, for example, and using touchscreen for this purpose is much more complicated).
If you want a more complete locking solution, why not use a locker like LockDevice, for example? Or even standard lock? It can go hand in hand with InCall Lock. This way you will have buttons locked during the conversation AND prevent accidental presses when pulling your device out of your pocket.
I really don't want to make this program complicated and add options; when people start following this route neat little programs quickly turn into S2U2s. If there is a strong usecase I could theoretically add this functionality, it's not that difficult. I would advise to look at other solutions first though.
vangrieg said:
I really don't want to make this program complicated and add options; when people start following this route neat little programs quickly turn into S2U2s. If there is a strong usecase I could theoretically add this functionality, it's not that difficult. I would advise to look at other solutions first though.
Click to expand...
Click to collapse
Hi, I second that! Please keep this as small and simple as possible. As you say, there are always other solutions that can be used with or without InCall Lock to achieve more complicated behavior.
Thanks for a great little app!
Regards,
PK
I am sure many will find this useful
vangrieg said:
Well, maybe, but they usually come with something else I don't need (i.e. Pocket Shield or LML) or have bugs I can't live with (i.e. Pocket Shield continues to vibrate on incoming calls after I pick up the phone).
This has never happened to me, and I don't like the idea of locking buttons permanently (I use Green button to put calls on hold, for example, and using touchscreen for this purpose is much more complicated).
If you want a more complete locking solution, why not use a locker like LockDevice, for example? Or even standard lock? It can go hand in hand with InCall Lock. This way you will have buttons locked during the conversation AND prevent accidental presses when pulling your device out of your pocket.
I really don't want to make this program complicated and add options; when people start following this route neat little programs quickly turn into S2U2s. If there is a strong usecase I could theoretically add this functionality, it's not that difficult. I would advise to look at other solutions first though.
Click to expand...
Click to collapse
The problem is on the touch HD phone the vertuial keys are allways active even with theas other programs.
No other program has an option to lock the virtuial HW keys on a touch HD during a call. Yours could be the first! If you are making a program to lock the keys why not make it complete? Then with a touch of the power button everything unlocks.
apeko said:
The problem is on the touch HD phone the vertuial keys are allways active even with theas other programs.
No other program has an option to lock the virtuial HW keys on a touch HD during a call.
Click to expand...
Click to collapse
I have a Touch HD myself, and I still don't understand your problem. Keys on HD may be "virtual" in that they are part of the touchscreen, but they are "hardware" in that they are managed by the system (or programs, for that matter) in the same way as true hardware keys are.
apeko said:
If you are making a program to lock the keys why not make it complete? Then with a touch of the power button everything unlocks.
Click to expand...
Click to collapse
Because it locks keys in situations where they can be pressed accidentally and which aren't handled well by other programs, that's the point. Like I said, I don't understand why you can't use standard locking programs to lock keys in standard situations. Maybe I'm missing something?
When i am on a call i do not want the keys on the bottem active. Just because a program blanks out the screen the keys at the bottem of the phone are still active. This causes acctdental key press when the phone is in my pocket and i am talking on my bt head set.
BTW thanks for your hard work and i apreiciate you time on this topic. your time is valuable. Thank you.
apeko, have you tried LockDevice? If yes, did you try activation on screen off? If not, you should try it. If it doesn't help I'll look into the issue and probably will make a version of InCall Lock that will keep keys locked until the end of call.
Actually, how about an alternative solution - what if a program locked Send and End keys while a headset is connected, without monitoring call state?
vangrieg said:
Actually, how about an alternative solution - what if a program locked Send and End keys while a headset is connected, without monitoring call state?
Click to expand...
Click to collapse
Yes that would work.
Is it the monitoring of the call status that makes the program tricky?
To be specific the problem is the Send and End keys while on the BT head set. Your alternitive solution should work fine. But the actual key locking problem on the touch hd is the Send and End keys only
1. when the phone rings-(solved)
2. during a call when on a BT head set- if it has to lock the Send &End keys allways during a BT connection i think i could live with that!
this is an awesome app!! so simple yet so usefull, thank you for your work!!
apeko said:
Is it the monitoring of the call status that makes the program tricky?
Click to expand...
Click to collapse
Well, maybe you don't need all these details, but since you asked... It brings the number of checks the program has to perform to like a dozen from one trigger and one check.
First, it has to monitor if a headset is present - that's two or three checks (HeadsetPresent, A2DPConected and HeadsetAudio).
Then there are like two dozen Phone states, out of which probably three to five are relevant - PhoneIncomingCall, PhoneCallCalling, PhoneCallTalking, PhoneCallOnHold(?), PhoneConferenceCall. Maybe not - that's a Windows flavor after all. In any case, there's no simple "Phone is actively used" state. Or maybe there is - needs investigation.
All this stuff needs testing in different combinations, and I don't even have a bluetooth headset to test (that is, I have it but for the life of me can't remember where it is).
When you introduce all these things you're asking for bugs because it's difficult to predict what they all mean exactly and how they work with each other. That's why I'm reluctant to add features like this into an application that seems to work fine. I'll look into the issue though, and if I do add this functionality it will be in a separate application.
1. How do I stop the backlight turning off when I am on a call? It is frustrating if I want to end a call and the screen is black so I can't press 'end call' or if I am on voicemail, I can't access the keypad to press the number I need to save, delete or save a message.
2. When I first got the phone, whenever I typed an MMS the vibrate worked as I touched the keypad but its not working now. Any ideas how to put this back on, vibrate works for everything else.
Thanks
I've found out the answer to question 2 of my query but still would like to know the answer to question 1. Thanks
deevineb said:
1. How do I stop the backlight turning off when I am on a call? It is frustrating if I want to end a call and the screen is black so I can't press 'end call' or if I am on voicemail, I can't access the keypad to press the number I need to save, delete or save a message.
2. When I first got the phone, whenever I typed an MMS the vibrate worked as I touched the keypad but its not working now. Any ideas how to put this back on, vibrate works for everything else.
Thanks
Click to expand...
Click to collapse
You can press any key other than end call to get the screen back without hanging up the phone, although, I know what you mean, its frustrating.
Theres a couple of programs on the market, but neither of them work right on the Hero yet. Shake awake I think is one.
1. The home key or menu key wake the screen without having any effect on the call.