Related
Hello,
I recently recieved a Dash from T-Mobile with WM6 Standard. 1 annoying thing I've noticed is that although the phone's keypad is locked, while reaching for the phone in the pouch, I've accidentally answered calls that I didn't want to . I wish there was a way that required a combination of at least 2 keys be pressed in a certain order before the call would be answered. This would be similar to unlocking the keypad. I could also prevent unknowingly answering a call if the ringer was on silent.
Wow, many views, no solution??
Im not sure about your phone, but you might want to disable any key answer
For my phone ( tornado ), its under settings, phone, call options
Hello karhoe,
Thanks for the suggestion, however that option is already disabled. The problem is that when the phone is in the case or in my pocket, the Answer Key can easily be activiated by the slightest touch which is not good. I'm suprised that more people haven't responded with the same issue.
Yes it happened to me a couple of days ago, quite annoying. The phone was just in my pocket and it rang. Reached in to pull the phone out, and apparently I had inadvertantly touched the softkey that answers the phone, before I could check the caller ID
Well there is no app that I know of that makes you have to press 2 or more keys to answer the phone. And that is what you would need, a 3rd party app.
It would be kind of dangerous or even more annoying under certain circumstances like driving. But if you had 2 different lock options, one normal the other for the 2 button answer, that would be cool. Very cool indeed.
But it does'nt always happen, I think it's happened only twice. Usually the phone is not in my pocket or on me in a holster, because I want to keep the radiation away from my body, so it's usually on my desk or sitting in the car if I am driving. In-between those times it is on me.
I'm afraid this applies to any phone of the Candy Bar type. Happened to me quite often to answer a call while reaching for the phone (S620 and S710 ans some other Nokias). Flip phones are much better for that. You got to open the phone to answer a call and you can still check the caller on the outside display before opening it.
You're right, a third party app setting a two level answer mode would be great, although don't know if this can be done, where the core of the phone handles the answering alone preventing any developer to set up an "answering sequence". Good idea anyway, curious to check on this one.
Ka.
Thanks for the replies. I'm still optimiistic that SOMEone out there may have a solution!
Sorry can't resist - If its someone you don't want to talk to, pretend you're on ATT and drop the call
I haven't had a problem. I use this case
http://www.krusell.se/product.php?productID=576&category=5
@jamssx: lol
@timothyjok: thx for the suggestion, I've looked at that case before, but was trying to remain positive that someon may have software solution. sigh...
From http://www.shipiboconibo.com/dash/#callreject :
Disable Accidental Call Rejection
Have you ever recieved a call and as you pull your Dash out of your pocket it says 'Call rejected'? I have, and it annoys the hell out of me! I derived this hack from a hack telling how to enable this feature, but mine was enabled by default so I am going to assume the original hack was intended for the Excalibur and T-Mobile decided to enable the feature on their phones. By default (can anyone else verify this is default on the Dash?) simply touching the JOGGR strip on the Dash during an incomming call will reject the call. I hate this and here is how you can disable it!
\HKEY_CURRENT_USER\ControlPanel\JogBar\Settings\EnableRejectCallFunc = 0
As you probably guessed, this is a binary value, setting it to 0 disables it, 1 enables it.
More than half the time I take my phone out of it's case in my pocket to check texts or call somebody, it's always on and eating battery. Alot of the time I have the phone in vibrate or silent because I can't have it going off most of the day, and whenever I get any kind of notification the screen comes on (text, alarm, call, ect.), and then the screen ends up staying on because it's constantly being bumped and never has the time to shut itself down.
Is there any way I can make the screen stay off at ALL times (except on an incoming call), and ONLY come on when I press the unlock/power button on the top of the phone?
I have a TMobile TP2 and I'm running the Nov. 19th, Photon Energy ROM. Upgrading to the Nov. 27th version when it's done downloading but I don't think that will fix the problem as I've changed ROMs before. Thanks to any help.
you will find that when in the case it should be off, on taking the phone out of the case (i assume the HTC one that came with the phone?)
the magnet in the case triggers the keyboard sensor which turns the screen on.
otherwise, you can change the display time out in power options under settings.
Cheers
Steve
That's interesting, I've heard about the case doing that but never thought about it. Would you recommend any cheap cases, or is there a specific magnet location I should be careful of? And do you know if there is a way to keep the screen off when I get a text message for example?
There is a way to fix this... it is to disable "Wake on Slide." I have done this and no more problems.
Here is a link to what to do:
http://forum.xda-developers.com/showpost.php?p=2945249&postcount=3
Hope it helps you, as it did me.
Thanks for the reply and I appreciate the help, but I don't really have a problem with the wake on keyboard slide, it seems that if the phone is in my pocket locked, and I get a text message, the screen comes on to notify me that I have a text message. Then, it's usually being bumped around in my pocket and since the touch screen is usable with any object, it will stay on because something will tap it in my pocket. The phone then heats up over time and drains battery. I want to find a way to keep the screen off at all times unless, I either receive a call, or push the power button. Thanks.
illusion of progress said:
Thanks for the reply and I appreciate the help, but I don't really have a problem with the wake on keyboard slide, it seems that if the phone is in my pocket locked, and I get a text message, the screen comes on to notify me that I have a text message. Then, it's usually being bumped around in my pocket and since the touch screen is usable with any object, it will stay on because something will tap it in my pocket. The phone then heats up over time and drains battery. I want to find a way to keep the screen off at all times unless, I either receive a call, or push the power button. Thanks.
Click to expand...
Click to collapse
Try:
go to HKLM\Drivers\BuiltIn\RIL
change DisableSMSWakeUpEvent to 1 (0 will wake up the device)
On my Rhodium, it does not wake up by default. I hear the notification, but my screen remains dark
Or try this cab file ... soft reset after install
Thanks for the .cab, I'm restarting now to see if it fixes the problem. Kind of random, but I might as well ask here before starting a new thread. I started using Mobile Shell instead of TF3D and so far I love it, but when setting a wallpaper, the wallpapers that I would normally use in TF3D, (480x800), it makes me select or crop out part of the photo to use as a background in Mobile Shell. I can't tell if it actually gets blurry (I would think so, because it's stretching the picture), but does anyone know why it wants me to only use a certain portion of the background instead of just setting the entire picture? Thanks,
More than likely, the version of Mobile Shell you have is either not designed for WVGA or there is a setting somewhere in there that allows you to change it and you haven't found it yet.
Am not a expert on mobile Shell, but according to their website, the latest version (3.5) does support WVGA.
Another option is to, if you have Adobe Photo shop or something similar, scale down the entire picture to the size it reccomends.
Otherwise, if you have a version earlier then 3.5, maybe you could upgrade and see if it makes any difference.
Okay I think I found another bug in the HTC sms program which I discovered today and wanted to see if its just me or anyone else. The other is hoping someone has a fix for a signal problem, and a solution for the third. I have the HTC EU Official ROM WinMo 6.5 with sense 2.1, and the phone is HardSPL.
1) I noticed today a bug in the HTC SMS program (I know who hasnt), but this doesnt seem to fall under anything I've read so far. Here the problem, When you click the contact icon on the slider bar it brings you to the flip contacts, when you click the contacts picture you go into their "profile" when you click the second sms icon here you can txt back and forth, now what I noticed is if you txt thru there when someone responds to a txt, the tone set (be it the default, or custom) doesnt ring completely. It rings for like a 1/4 of a second. I noticed this as I was txting a friend. Has anyone else have this or encountered this? This is completely different then not being notified of an incoming txt, but runs along the same possible reason why we dont get one.
2) I use a bluetooth 85% of the time, I have one major issue. I saw a possible fix, but I dont remember where or what site, but I dont know if its for this issue either. I normally keep my phone on my belt clip on the right side and the bluetooth on the right ear, but if I decide to move the earpiece to my left ear, the signal seems to get weak, and I start hearing crackling until; I move the earpiece back, or move the phone to the same side. Is there a cab or registry edit that improves the signal strength for this? I have two bluetooths, sony erricson and a Jabra V250, both have the same symptom.
3) Everytime I get a call or make a call, when I am talking the proximity sensor kicks in, which is fine, but everytime I move the phone away from my ear, thescreen isnt at the dialpad but at the black notification screen. I understand that if there was a txt, missed call event then thats fine, but when none of these exist its annoying. Is this by design or is this just something thats going to annoy me to hell and back?
Bumpy Bumpy...
Anyone?
Also I found I think another bug, I dont know if its been mentioned, if it has sorry, but has anyone realized that when the phone is on and at standby and the screen goes black that the volume keys still adjust the volume? I normally keep my phone in a leather case on my belt, and notice that when I bend down the buttons if hit will adjust the volume up or down, I ran into this by accident while bending down all of a sudden my phone vibrated briefly checked the phone and saw the volume was all the way down, thought maybe the screen was up and thats why it happened after the second time I tested it and sure enough you can adjust the volume. I know for a fact the Fuze never did that. Anyone else have this issue?
AngelDeath said:
Bumpy Bumpy...
Anyone?
Also I found I think another bug, I dont know if its been mentioned, if it has sorry, but has anyone realized that when the phone is on and at standby and the screen goes black that the volume keys still adjust the volume? I normally keep my phone in a leather case on my belt, and notice that when I bend down the buttons if hit will adjust the volume up or down, I ran into this by accident while bending down all of a sudden my phone vibrated briefly checked the phone and saw the volume was all the way down, thought maybe the screen was up and thats why it happened after the second time I tested it and sure enough you can adjust the volume. I know for a fact the Fuze never did that. Anyone else have this issue?
Click to expand...
Click to collapse
I don't know that this is related to your symptoms above, but several TP2 owners (myself included) have experienced the fact that this model seems to be particularly sensitive to cases with stronger magnets in the clasp...the magnets are just strong enough to trigger the magnetic switches in the phone that register when you slide open the keyboard, or remove the stylus. It drove me nuts for a while trying to figure out why my phone seemed to keep randomly turning itself on in the case, especially right when I was first sliding it in/out. I had thought it was because there were hardware buttons still active even when the screen was dark, but some thorough experimenting/testing proved the issue was due to the magnets....a conclusion that was confirmed by several other users once I actually bothered to go looking online for a solution (....after I'd spent hours figuring it out for myself lol). So, it might be the cause of your screen coming on and then the volume buttons are just the first ones that get pressed by your particular case and/or posture.
Unforutuately, I doubt there's any possible connection between that and your other issues...
I know there isnt any connection with the other issues, I just didnt want to make another post and have XDA shoot me for it.
Also I know about the magnet interference I read up on that long ago, but thats not my issue. I thought that was it, but I can do the same thing while holding the phone in my hands. So the magnet in the holder does not apply. I can have the home screen up, hit the power button to blackout the screen and then hold the volume down key and it will lower the volume cause by holding it down the phone will vibrate, when I turn the screen on, the volume is all the way down.
AngelDeath said:
1) I noticed today a bug in the HTC SMS program (I know who hasnt), but this doesnt seem to fall under anything I've read so far. Here the problem, When you click the contact icon on the slider bar it brings you to the flip contacts, when you click the contacts picture you go into their "profile" when you click the second sms icon here you can txt back and forth, now what I noticed is if you txt thru there when someone responds to a txt, the tone set (be it the default, or custom) doesnt ring completely. It rings for like a 1/4 of a second. I noticed this as I was txting a friend. Has anyone else have this or encountered this? This is completely different then not being notified of an incoming txt, but runs along the same possible reason why we dont get one.
Click to expand...
Click to collapse
You get a shortened notification if the phone thinks you are looking at the screen when the message comes in. It would be nice if this could be turned off, but that is why.
The Pro2 isn't necessary 100% at fault with the Bluetooth problem. It can be a combination with your handsfree earpiece too.
Every Jabra unit I own has always exhibited this problem with every HTC phone I have. The first time I bought a Jabra I remember reading in the manual about their recommendation to keep the phone and earpiece on the same side of the body to avoid "interference" (referring to the body??). And if I'm listening to music through A2DP, and I move the phone to the other side of the body, the music cuts out too.
I also have an old Sony Ericsson HBH-660 and it doesn't have this problem if I wear it on the other side of the body, so it's appears both HTC phones and Jabras emit a weaker bluetooth signal.
Mesquire said:
The Pro2 isn't necessary 100% at fault with the Bluetooth problem. It can be a combination with your handsfree earpiece too.
Every Jabra unit I own has always exhibited this problem with every HTC phone I have. The first time I bought a Jabra I remember reading in the manual about their recommendation to keep the phone and earpiece on the same side of the body to avoid "interference" (referring to the body??). And if I'm listening to music through A2DP, and I move the phone to the other side of the body, the music cuts out too.
I also have an old Sony Ericsson HBH-660 and it doesn't have this problem if I wear it on the other side of the body, so it's appears both HTC phones and Jabras emit a weaker bluetooth signal.
Click to expand...
Click to collapse
My Sony Erricson is a HBH-GV435 And both the Jabra and the Erricson exhibit this behavior. I dont know where I read it, but I think there is a registry edit about improving the signal, unless it was something else and I read wrong, was hoping someone knew what I was talking about.
Zylograth,
I wouldnt want it turned off, if anything it should ring normally. And I think that maybe in connection to the possibility of the SMS alerts not coming in when the screen is off. I think its related somehow. But do you know where this shortened tone noticification is located?
But now what about the other behaviors? Anyone else have them?
The noticification screen is really starting to bug me with I move the phone away from my ear.
After a few months of use...
Notifications - opens every (ear listening) call, apparently my ear shape hits the top bar and the machine thinks I want to see notifications. Since the machine knows it's orientation - it there a way to prevent an ear-activated notification request when phone is vertical, or during a call?
Screen overlays - I bought some and added one, it got scratched and I peeled it off, and now I see at least 2 more! I think I see a glass that fills the frame, a smaller overlay, and another, smaller overlay. My basic thought is to keep peeling as they scratch. I want to make sure that if I get to 'glass' that I have not messed anything up - a decorative overlay (maybe with the browser size slider markings?) or a functional part of the touchscreen assembly. Is there anything I can mess up if I just keep peeling?
Thanks any and all!
Eep, I know know if I'd "keep peeling". If you feel like the screen itself is pulling back, I wouldn't do it. Resistive touchscreens do have 'layers' if you will...
Weird, in WinMo the prox sensor should work just fine - make sure it's enabled, the screen should turn off when your face gets close to the screen.
See this video for a demo.
Thanks for reply.
I'll look for cabs that may have affected the sensor (basically OEM update + a few goodies) as I can find no HTC/WinMo setting.
Were you saying you don't know if you'd... or now know?
Should there be a factory layer, exposed the user, that I should NOT peel off? ( I knew factory touchscreen at one time, they were soft overlays over CRT's.)
THX
tshephard said:
Thanks for reply.
I'll look for cabs that may have affected the sensor (basically OEM update + a few goodies) as I can find no HTC/WinMo setting.
Were you saying you don't know if you'd... or now know?
Should there be a factory layer, exposed the user, that I should NOT peel off? ( I knew factory touchscreen at one time, they were soft overlays over CRT's.)
THX
Click to expand...
Click to collapse
I have no idea, since I can't see what you're peeling. I've never completely disassembled one of these, but I've seen pics/videos. I also know a little bit about how touchscreens work (a little!) and I know there are layers that you should not be peeling back - without seeing a detailed pic or the device in person, I don't feel comfortable saying "yea, peel away" when you could be potentially damaging your phone.
OK - I removed all cabs, still not working, did reflash, same, did task 29 and reflashed, still not working.
Found something called 'Advanced Configuration', played with Light sensor settings, and now that works great, never knew it didn't before (auto did nothing).
Is there something similar for proximity settings? ( I would have thought a connector inside was loose - that's why I messed with light sensor - but that 'healed' and now I want to 'heal' Prox too!)
I peeled down to a full chrome-filling ?glass? layer that looks thick and just a bit wavy - still no Prox activity - and put a new screen saver on that - so that's not it.
Anyone know settings/cab/registry for Prox activity?
Still don't have proximity function... I'm thinking in call, object (ear) near HTC symbol should blank screen and also deny touch response.
I downloaded registry editor, and found some settings. Tried, well many combinations but no results.
I do find that some don't stay set - I change them, and reboot, and they go back to say "0". They are ProximityDetectStatus and ProximitySensorOn . I'm thinking (supposition) resistry settings are static - that they do not reflect machine activity, only editor or user's other software actually changing values to store - rather than indicators of current machine activty (button is now pressed, button is now un-pressed). Is my regedit process (change, close, boot) correct?
I'm left wondering - are registry settings reflective of current activity while regedit is open or even the moment it opened? IE, can I use regedit to show me if a switch is pressed?
Anyone else, help?
I'm on OE ROM, CHT and CHT editor
I noticed a strange behavior of my wildfire, for quite some time and not always certain applications are activated by themselves (like when you click) or the type of home you show when you want to delete, or if you scroll through the call log apart from the call you made to last, in short, seems to be "possessed," what can it be?
the continuous change of rom? (I like to change often)
having put the cap thicker in the display?
is deteriorating the cell?
it sounds like a touch screen issue. how often does this happen? try installing this app. if the screen starts showing pixels without you touching it then its a digitizer issue.
infernale said:
I noticed a strange behavior of my wildfire, for quite some time and not always certain applications are activated by themselves (like when you click) or the type of home you show when you want to delete, or if you scroll through the call log apart from the call you made to last, in short, seems to be "possessed," what can it be?
the continuous change of rom? (I like to change often)
having put the cap thicker in the display?
is deteriorating the cell?
Click to expand...
Click to collapse
I guess what you're trying to say is that the touchscreen seem to be over sensitive.
if that's the case, it also happenes to me while I use the phone rested on a table. this mostly happened to me while on froyo roms.
Or it could also because your screen protector.
try using the phone angled up a bit while on a table. It should somewhat solve it in my experience.
or it could be a touchscreen issue as heavy metal man said.
Cheers
I noticed that happens when it is half or less of battery ....
I attach picture Touch Screen Test
the top line does not work?
but does not work alone!