Related
Here's the scenario.
I have my blueangel in my pocket.
It's off and the button lock is engaged so that it wont turn itself on accidentally. There's nothing I hate more than when it switches itself on in my pocket and goes berserk with random screen input.
My bluetooth headset is connected.
(I'm not even gonna start on how appaling the blue tooth on the blue angel is !!!!!, but that aside.....)
The phone rings and I press the answer buton on my headset to answer it.
The damn phone is now on in my pocket and the screen is active and receiving input during the call. Quite apart from anything else, there is a great big red END CALL button on the screen just waiting to be touched.
Assuming the call survives any problems, at the end of the call I have to get the phone out of my pocket to turn it off again because it wont turn itself off unless the activity timeout occurs which is not going to happen if the screen is being brused by anything in my pocket.
Is there some configuration or tool or utility or something that can detect when the phone is in handfree mode and disable screen input unless a certain button is pressed (like the green phone buton) and then switch the phone off again when the call is terminated ?
http://www.trancreative.com/nicestart.aspx
Have a look at this.
Im using it, and its the one that does the job best of them all out there, well in my opinion anyway
What about a case?
I had an alu one... no problem!
OK. I got NiceStart and had a play with it.
I think I have got it configured to work OK now.
Seems to solve most of the issues I raised.
I can't believe I had to get extra software to do that though.
I mean, it's not as if any of those probelms are either unforseeable or hard to solve.
It makes you wonder if the people who design these devices ever actually use them for real for any length of time.
The worst thing about it, is that i can buy a 1$ phone with a locking thats even better than this.
People have been screaming about this since the birth of WM, but M$ dont seem to be hearing this.
I have set Start->Settings->System->Button Lock-> Lock all ........power Button
Set a 4 digit password in NiceStart and mapped it to the 4 action buttons right under the screen.
Works great, but the screen will from time to time light up (M$ thing that it must do) to check the battery status. This cant be stopped in any way.
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.
Have had my new Sprint TP2 for a couple of weeks now, really enjoying it. First "smartphone" for me, figured it's time to join the 21st century.
Biggest issue so far:
When putting the phone into a holster, it comes out of sleep mode (display comes on) - no, I'm not hitting the Power key when I do this. Something here doesnt seem right, but that's what happens...
At that point, on occasion the Dial key may get hit while in the holster (I can understand this, it's a hardware key) - which if the key kets tagged 2x while out of sleep-mode does a pocket dial to the last number called/received.
My original fix to this was to enable the password lock. While a PITA to unlock the phone every time, I'd rather do that than pocket dial. HOWEVER, when running an output only app (such as Google Maps or Navigation) the phone keeps going into lock mode and asking for the password - NOT a good situation while driving down the road...
So my question(s) are:
1. Is there a way to keep the phone from exiting sleep mode while entering a holster?
2. Is there a way to keep the phone from locking up and requesting a password during apps such as Navigation?
(I found this thread while searching, but still un-answered... [Thread 614599; vBulletin wont let me post the URL...)
Thanks in advance for any help!
Jim
This is a completely stock phone, no mods (so far...) other than a couple of applications added (Google Mobile apps, WSOP Poker).
The first question I have for you. Is the case/holder specific to HTC TP2 or is it generic and originally designed for a blackberry?
I ask this because no matter what blackberry case i've ever tried, they always bring my phone out of sleep mode. The reason is the magnet in the case that is designed to put the BB INTO sleep mode.
The case is specific for the Sprint TP2, from ThinkTouchPro2.com. It's the [HTC Touch Pro 2 Naztech Kaskade Vertical Pouch Case - Black], since I still cant post a url... well, I guess I can fake one:
thinktouchpro2.com/htc-touch-pro-2-cases-7462.html
It's definitely the magnet that's doing the trick. The phone comes out of sleep mode just as it starts to go into the case, so it's not a function of hitting any buttons.
Somehow I got into the habit of hitting the power button to put it to sleep before going into the holster, SOOOO thinking maybe it's a 2-way deal I tried leaving the phone awake and putting into the holster - no dice, still awake.
Test 2 was to put the phone into the holster, and then force to sleep. Removing it wakes the phone up, that I'm cool with. But I'm still left with the issue of pocket dialing whenever I use the holster...
Maybe the best solution would be to go to a non-magnetic holster?
Jim
that would be it.
The device uses a magnetic switch to tell it when you slide the keyboard out. So by pulling the device in/out of the case the magnet is triggering the switch leading the device to think you've slid out the keyboard and it should wake up.
I think Advanced config has an option to disable the device from waking up when the keyboard is slid open.
Actually I believe it's the magnet on the stylus, it doesn't have anything to do with the sliding function.
There was a solution for this somewhere around the forums.
If I'm not mistaken, removing the "wake up when keyboard is out" setting, solved the problem with cases that have a magnet.
j0shtalgia said:
Actually I believe it's the magnet on the stylus, it doesn't have anything to do with the sliding function.
Click to expand...
Click to collapse
my laptop uses a magnet to secure the screen when i close it and if i slide my tilt2 across where the magnet is with the stylus in or out, the device wakes up and goes into landscape for a second then switches back to portrait.
dont think the stylus magnet would cause it because the stylus is still in the device and the magnet is securing it in. I think it has another sensor in the stylus slot and just uses the magnet to suck it in because on older devices (wizard) the stylus would go loose, but then again those devices didn't wake when the stylus was removed.
fone_fanatic said:
my laptop uses a magnet to secure the screen when i close it and if i slide my tilt2 across where the magnet is with the stylus in or out, the device wakes up and goes into landscape for a second then switches back to portrait.
dont think the stylus magnet would cause it because the stylus is still in the device and the magnet is securing it in. I think it has another sensor in the stylus slot and just uses the magnet to suck it in because on older devices (wizard) the stylus would go loose, but then again those devices didn't wake when the stylus was removed.
Click to expand...
Click to collapse
Ah, I see. Interesting!
fone_fanatic said:
... if i slide my tilt2 across where the magnet is with the stylus in or out, the device wakes up and goes into landscape for a second then switches back to portrait.
Click to expand...
Click to collapse
BINGO, think we're onto it as I've seen this behavior as well.
I've poked around looking for this, but the closest I've found is the "Keyboard Sliding Sound", but there's not an option to kill the wake-up function. Can someone point me in the direction of the "Advanced Config"?
Jim
So why not use pocket sheild? It has a 15 sec timer on it, so if you put it in your holster and it "wakes up", after 15 seconds it will turn the phone off again if there isn't any action done on it. Use it to only turn on with the light sensor when you pull it out of you pocket or a finger swipe from top to bottom. Also, you can tell it what apps that it cannot go into sleep mode on.
aj48198 said:
So why not use pocket sheild?
Click to expand...
Click to collapse
That's actually on my list of apps to take a look at, but for a different reason. I'd still like it to not come on at all, as the pocket dial I made was well w/in the 15s timeout for PS.
Ok, so the search originally didnt work for me because I didnt realize it was the magnet causing the wake-up. Knowing that now, I found the registry change I need to make in another thread.
Now for the total noob quesion:
How do I get into the registry to edit it?
I gather Total Commander is the popular tool of choice, and now have that installed. But my searches keep coming up with various tweaks to MAKE in the registry, but not how to GET TO it. I was unable to find this in the TC docs, either...
Thanks for the patient assistance to a WM noob.
(tho I'm a .Net programmer, so not a complete ijit - unless you want to hold being a .Net programmer against me, which I really couldnt blame you for - but it beats the heck outta COBOL...)
Jim
PHM Registry Editor. I would have posted a link but I don't have enough posts to do so!! Just google it and it should come up I got mine off of freewareppc com
Pocket Sheild will not let anything happen what so ever. Unless you physically make it happen, it will do nothing but sit there at the unlock screen waiting for input. If nothing happens, the screen will go back into sleep mode. Check the website out, that should help you make your decision easier. You can change the timer to be 10 seconds as well but I think that is about as close as you can get beside turning the phone off!!
SailCO26 said:
Have had my new Sprint TP2 for a couple of weeks now, really enjoying it. First "smartphone" for me, figured it's time to join the 21st century.
Biggest issue so far:
When putting the phone into a holster, it comes out of sleep mode (display comes on) - no, I'm not hitting the Power key when I do this. Something here doesnt seem right, but that's what happens...
At that point, on occasion the Dial key may get hit while in the holster (I can understand this, it's a hardware key) - which if the key kets tagged 2x while out of sleep-mode does a pocket dial to the last number called/received.
My original fix to this was to enable the password lock. While a PITA to unlock the phone every time, I'd rather do that than pocket dial. HOWEVER, when running an output only app (such as Google Maps or Navigation) the phone keeps going into lock mode and asking for the password - NOT a good situation while driving down the road...
So my question(s) are:
1. Is there a way to keep the phone from exiting sleep mode while entering a holster?
2. Is there a way to keep the phone from locking up and requesting a password during apps such as Navigation?
(I found this thread while searching, but still un-answered... [Thread 614599; vBulletin wont let me post the URL...)
Thanks in advance for any help!
Jim
This is a completely stock phone, no mods (so far...) other than a couple of applications added (Google Mobile apps, WSOP Poker).
Click to expand...
Click to collapse
I think this is what you need:
1) this is a magnet holster issue -- FIX: from wmexpert touch-pro-2-tip-fix-cases-magnets-issue-registry-fix *attached Cab
2) To stop certain apps from locking automatically I use S2U2 *zip attached (Slide to Unlock) there is a list of applications that you can set not to lock when active. I use this for GPS navigation for example. showthread.php?t=527523
You can set a password with this or not as you wish. You'll like it.
Keep in mind that the one sideeffect of the magnet fix is that the phone will not automatically unlock on opening the keyboard. You have to hit the power button. Personally I don't have any problem with this.
aj48198 said:
Pocket Sheild will not let anything happen what so ever. Unless you physically make it happen, it will do nothing but sit there at the unlock screen waiting for input. If nothing happens, the screen will go back into sleep mode. Check the website out, that should help you make your decision easier. You can change the timer to be 10 seconds as well but I think that is about as close as you can get beside turning the phone off!!
Click to expand...
Click to collapse
well he is making it physically happen, but unintentionally. The magnet in the holster is waking the device up by making it think the keyboard has slid open, then the call button is being pressed against the case causing the device to place a call.
as i stated earlier, its best to disable wake-up when keyboard is slid out which is provided in a cab in the post right before this one.
Thanks aj and fwp, I think I've got it now.
Backed into a copy of the PHM RegEdit, and the slide fix worked great! No worries about the kb not waking the phone up, never used that function anyway.
Re the S2U2 app and preventing lock during some apps, does PocketShield also do this - or would I need to run both to keep GPS apps alive?
Thanks again!
Jim
fone_fanatic said:
well he is making it physically happen, but unintentionally. The magnet in the holster is waking the device up by making it think the keyboard has slid open, then the call button is being pressed against the case causing the device to place a call.
as i stated earlier, its best to disable wake-up when keyboard is slid out which is provided in a cab in the post right before this one.
Click to expand...
Click to collapse
I get that, and if the cab fixes the issue, thats great. What I was saying was that pocket sheild will not unlock at all, be it the keyboard slid open or the stylus came out, unless you program it to do so. I just tried to make it unlock by sliding the keyboard open and the only thing it did was go into landscape, still locked tho.
aj48198 said:
I get that, and if the cab fixes the issue, thats great. What I was saying was that pocket sheild will not unlock at all, be it the keyboard slid open or the stylus came out, unless you program it to do so. I just tried to make it unlock by sliding the keyboard open and the only thing it did was go into landscape, still locked tho.
Click to expand...
Click to collapse
ahh ok, not familiar with that app and thought you were saying that it would wait for an input (i.e. buttons pressed) for a set time, and if nothing happened then it would lock the device after a set time period.
SailCO26 said:
Thanks aj and fwp, I think I've got it now.
Backed into a copy of the PHM RegEdit, and the slide fix worked great! No worries about the kb not waking the phone up, never used that function anyway.
Re the S2U2 app and preventing lock during some apps, does PocketShield also do this - or would I need to run both to keep GPS apps alive?
Thanks again!
Jim
Click to expand...
Click to collapse
PS does do that (preventing lock during some apps) You just have to tell it when you are in the settings.
Thanks for all the great info! Have the phone "safe" now, but will be looking into PocketShield as the next app.
Jim
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.
NOTIFICATION BAR scrolling down without touching it: Static Electr & Capacitive Scrns
I would like to know if anyone else has experienced this at least once. I didn't post here as a thread til I got confirmation from one other DESIRE user that this has happened to him as well.
I don't know the exact triggers or even the exact scenarios, but this has happened several times to me already:
I am using the phone in horizontal mode and tapping menu items or inputting text, and my finger is nowhere even close to the Notification Bar at top of screen -- and yet suddenly the Notification Bar will auto-scroll down, interrupting what I was doing. Repeated times. It would happen again, with no accidental slippage of my finger or anything. My finger would be nowhere near the bar.
I am wondering if there is any kind of static electricity effect with capacitive screens that can set off a menu action.
So I am asking the experts here. Is that possible? Is it anything that was reported with the Nexus One?
RELATED (1): After this happened a few time in ONE SESSION using the phone -- it happened to be while uploading videos to YouTube, I wanted to test to see if I moved my finger close to the Notification Bar would this perhaps trigger this auto-scroll-down. So I moved my finger just slightly above the surface of the glass at the Notification Bar, and it didn't make it scroll down, but on this occasion, it set off a kind of jumpiness whereby the notification bar was rapidly shifting up and down a few pixels, as though it was receiving input. Has anyone seen this happen? I have not yet been able to get this to repeat from that session of using the phone a few days ago. I was lying down on my bed, and I'm pretty sure sheets produce a lot of static electricity, so this is my layman's question. Is there some causal effect here?
RELATED (2): A variation on this problem would be where I am actually trying to select a menu choice, and instead of my finger-press activating the menu item, instead the menu item jumps up slightly, and does not get selected.
This, again, happened when I was in ALBUM MODE, watched a video in horizontal display, then tapped-and-held the video to bring up the context menu that includes various SHARE options. One of those options is YouTube (the last item of the menu). I would try to select "YouTube" but the menu jumped upwards slightly, and wouldn't get selected.
I have been able to reproduce this one (Related 2) today, days later, in totally different environment .
So, a bunch of questions:
1. Is there such a thing as a static electricity effect that confuses the screen?
2. Are there other kinds of known screen-response problems that could be at play here?
3. Is this something that sounds like "it's defective so return it", or is this a somewhat common experience, sporadically?
the only time I've had that happen to me is when I use a cheap charger I've got and yeah the screen just skitses out. I am using a hero tho but this is the first time I've seen anyone else encounter this so I thought il'd churp in.
I had something similar only once.
The notification bar went mad. It was flicking up and down constantly without me touching the phone at all.
I had to pull the battery to fix the problem.
Hasn't happened since.
Fon22
Happened to me also when loading a ROM in Nesoid.
So I'm not sensing any concerns re; any defect... but still wondering, since I don't know the physics of capacitive screens... Is static electricity the culprit? Never happened once on my GSM HERO... so something is at play here.. or is it an intermittent defect that rarely shows up?
quicksite said:
So I'm not sensing any concerns re; any defect... but still wondering, since I don't know the physics of capacitive screens... Is static electricity the culprit? Never happened once on my GSM HERO... so something is at play here.. or is it an intermittent defect that rarely shows up?
Click to expand...
Click to collapse
The capacitive touch screens work by detecting a disturbance in the EM field on the glass surface. There's a few ways to do it, I think the way mobile phones are doing this is to put a field of their own over the glass and detect fingers on the surface based on what levels of the field they'd expect to see at different points around the screen, and doing some comparisons on what levels are actually detected.
Please someone correct me if I'm wrong BTW.
I've noticed this notification bar problem today and yesterday. Lucky I at least saw how I caused it. My finger was to close to the top right of the screen because of the way I was holding the handset. That combined with the lacklustre multi-touch support on this handset made the phone detect it as a finger swipe that rapidly moved downwards.
I've always had similar problems with capacitative and inductive touch technologies. I don't actually need to touch the desires screen to activate a touch. The worsted was the Zen Micro with the touch controls. I could activate that thing from about 10-15mm away. The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Brilliant, Alex... You got right inside my head and answered exactly what i was trying to ask.... the physics of the system.
I'm okay with little glitches here and there, and I am sure I will learn to avoid proximity issues that tend to trigger these mis-fires... just as I learned to adjust my tap-key behavior in typing on the on-screen keyboard on capacitive screen vs all the resistive screens I had used before on Windows Mobile, where fingernails could & would engage the resistive screen -- vs learning that the bottom surface of the finger has to make contact on the keys on capacitive screen... (sorry i am USA and we still resist the world's metric standard, so i don't know the equivalent distance in cm,)... but it's over a 1/4-inch of an upward shift in the position of one's fingers above the capacitive screen from the tip of the fingernail.
But once you train your senses to activate the keys sensors properly, the finger impact behaviors of resistive screens goes away after a while (at least for me)
(oh, btw, I ordered the new HTC capacitive stylus which is a couple of months old now, but is an official DESIRE accessory, so that will be an interesting experience... the thing i miss most about the resistive screen and stylus was being able to scribble notes really fast, way faster than i could ever type -- and draw pretty detailed images or maps and directuions for people. so it will be interesting to see the granularity of control the capacitive stylus will give)
So thanks very much for giving me the exact level of detail I can process as a lay person.. and for assuring me, as the rest of you have as well, that this apparently comes with the territory of this phone -- and therefore should not be seen as a defect. Because i sure as hell didn't want to go shipping this phone back. I can live with an occasional spazzoid misread of intended impact spot on screen...
And, fnally, this was funny -- re the different degree of touch we all consider "normal" --
The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Click to expand...
Click to collapse
thanks!
Alex_w said:
The capacitive touch screens work by detecting a disturbance in the EM field on the glass surface. There's a few ways to do it, I think the way mobile phones are doing this is to put a field of their own over the glass and detect fingers on the surface based on what levels of the field they'd expect to see at different points around the screen, and doing some comparisons on what levels are actually detected.
Please someone correct me if I'm wrong BTW.
I've noticed this notification bar problem today and yesterday. Lucky I at least saw how I caused it. My finger was to close to the top right of the screen because of the way I was holding the handset. That combined with the lacklustre multi-touch support on this handset made the phone detect it as a finger swipe that rapidly moved downwards.
I've always had similar problems with capacitative and inductive touch technologies. I don't actually need to touch the desires screen to activate a touch. The worsted was the Zen Micro with the touch controls. I could activate that thing from about 10-15mm away. The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Click to expand...
Click to collapse
I was thinking it is softwarerelated. The bar remains halfway the screen, is in the layer below the active app, and jumps to front upon touching the screen.
I have the Problem, too. And that since Monday. I went mad since yesterday evening so i tried to go back to stock, unroot and all.
But the problem is still there.
How can i fix it? Or is my Phone damaged?!
The Notification Bar scrolls down without touching the display and then freezes the phone. so i must lock the phone and relock it and then i can use the phone but after a short time the same problem came back!!
So I reckon you're an undertaker for a living?
Sent from my HTC Desire using Tapatalk 2
erklat said:
So I reckon you're an undertaker for a living?
Click to expand...
Click to collapse
Sorry but i don't understand what you mean
The problem makes me crazy because i have now the stock rom because i thougt it was an issue due a custom rom or a kernel or something.
If you can help me please do that, this problem robs me to sleep
But i havent the Desire. I Have the HTC EVO 3D GSM
19Marc89 said:
Sorry but i don't understand what you mean
Click to expand...
Click to collapse
lol digging up the dead
Sent from my HTC Desire
Sorry but I do not understand the background of your information which is in context with my problem of the notification bar.
@19Marc89 He meant that you responded to a an old (dead) post. Listen, I'm trying to recondition an old Motorola Milestone (Droid) with a crazy touchscreen problem, whose cause I believe I've narrowed down to static electricity - can you do me a favor and try stroking the glass side of the phone lengthwise in one direction down your sleeve, preferably if you have a wool sweater on? Call me crazy, but this works for me, at least temporarily. I posted more here:
http://forum.xda-developers.com/showthread.php?t=1041943&page=5
install gravitybox. go to >statusbar tweaks>disable peek. click it. problem solved!
quicksite said:
I would like to know if anyone else has experienced this at least once. I didn't post here as a thread til I got confirmation from one other DESIRE user that this has happened to him as well.
I don't know the exact triggers or even the exact scenarios, but this has happened several times to me already:
I am using the phone in horizontal mode and tapping menu items or inputting text, and my finger is nowhere even close to the Notification Bar at top of screen -- and yet suddenly the Notification Bar will auto-scroll down, interrupting what I was doing. Repeated times. It would happen again, with no accidental slippage of my finger or anything. My finger would be nowhere near the bar.
I am wondering if there is any kind of static electricity effect with capacitive screens that can set off a menu action.
So I am asking the experts here. Is that possible? Is it anything that was reported with the Nexus One?
RELATED (1): After this happened a few time in ONE SESSION using the phone -- it happened to be while uploading videos to YouTube, I wanted to test to see if I moved my finger close to the Notification Bar would this perhaps trigger this auto-scroll-down. So I moved my finger just slightly above the surface of the glass at the Notification Bar, and it didn't make it scroll down, but on this occasion, it set off a kind of jumpiness whereby the notification bar was rapidly shifting up and down a few pixels, as though it was receiving input. Has anyone seen this happen? I have not yet been able to get this to repeat from that session of using the phone a few days ago. I was lying down on my bed, and I'm pretty sure sheets produce a lot of static electricity, so this is my layman's question. Is there some causal effect here?
RELATED (2): A variation on this problem would be where I am actually trying to select a menu choice, and instead of my finger-press activating the menu item, instead the menu item jumps up slightly, and does not get selected.
This, again, happened when I was in ALBUM MODE, watched a video in horizontal display, then tapped-and-held the video to bring up the context menu that includes various SHARE options. One of those options is YouTube (the last item of the menu). I would try to select "YouTube" but the menu jumped upwards slightly, and wouldn't get selected.
I have been able to reproduce this one (Related 2) today, days later, in totally different environment .
So, a bunch of questions:
1. Is there such a thing as a static electricity effect that confuses the screen?
2. Are there other kinds of known screen-response problems that could be at play here?
3. Is this something that sounds like "it's defective so return it", or is this a somewhat common experience, sporadically?
Click to expand...
Click to collapse
REPLY :
install gravitybox. go to >statusbar tweaks>disable peek. click it. problem solved!
I know I am many years late but did you somehow manage to solve this problem?