Related
I went to my local AT&T corporate retail store to try the Tilt 2 again because the first device I tried at another store seemed slow and not responsive. I had a similar experience this time around too. But I have to believe that most of that can be chalked up to the fact that it has the stock ROM on it and also every noob in the world has messed with it inside the store. But it did leave me with a few questions.
I could not get the screen to go landscape unless I flipped out the keyboard. And when I pushed the keyboard back in it would go back to portrait even though I was still holding it landscape. Is this a setting somewhere? I thought the Tilt 2 had a true accelorometer.
When in the browser I would touch in the URL line and start typing out a www address. But every time i would get a few letters into it and another text field would open at the bottom and start intercepting my typing. Anyone know what that is?
While the Tilt2 is equipped with an accelerometer, TouchFLO itself is not designed to re-orient itself in landscape using just the accelerometer.
That being said, some applications do go into landscape mode when you turn it with the keyboard closed. The Windows Mobile SMS application, some versions of Opera, and other various apps. Otherwise, to "force" landscape the keyboard needs to be open (or use some 3rd-party app/tweak).
Also, out-of-the-box, the stock ROM is actually pretty responsive and fast. Its one of AT&T/HTC's better built stock ROMs out there. Of course there is always room for improvement. I suspect the slow/unresponsiveness is due to the fact that its a demo unit thats already been messed with.
As for the additional text field in the browser, I have no idea what that is. Only thing that pops up normally during normal browser usage is auto-complete that makes URL suggestions.
ChasDun said:
I could not get the screen to go landscape unless I flipped out the keyboard. And when I pushed the keyboard back in it would go back to portrait even though I was still holding it landscape. Is this a setting somewhere? I thought the Tilt 2 had a true accelorometer.
Click to expand...
Click to collapse
You can use G-Config (available here on xda) to add programs (including TF3D and the Start menu) to the sensor database. Works great!
I have mapped one of the hardware buttons (long press on the answer key) to rotate the screen. Find it better than auto rotate depending on the orientation.
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
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?
I'm going mad here trying to find a screen Lock suitable to my needs. Can anyone please help? I want a simple screen lock, nothing fancy, no bells'n'whistles, but with the following two essential features.
1) Screen Lock is quickly unlocked with a simple screen swipe as soon as I either power on or slide open the device (ideally slide-opening would automatically unlock without requiring a swipe).
2) When running on external power the screen should unlock automatically and remain unlocked.
I've now auditioned PocketShield, Sunscape, TouchLockPro and S2U2 all of which may have one or other of those features, but none have both.
Can anyone please recommend anything else? Thank you.
1) In Pocketshield you can auto unlock by sliding QWERTY out if you create the following reg key: HKEY_LOCAL_MACHINE\Software\Pocketshield\ROTATE=1 (DWORD)
2) There is an option for it in settings.
Thanks for that. I've decided to give PocketShield another go and am auditioning it at the moment. Also I've changed my UI from Winterface to Spb Mobile Shell 3.5 because I wondered whether Winterface wasn't working well with PocketShield.
But here's my issue with PocketShield, perhaps somebody can please help?
If I open the slide keyboard I am able for a second or two to use the device as if it were not locked, before PocketShield "remembers" that is supposed to be on and then suddenly the device gets upset, slow, stuck, until I can find and unlock pocketShield. If I first power on and then slide open the keyboard, everything is fine, but everything stays in portrait, even though the keyboard is open. I can unlock PocketShield properly (though sideways) but then everything else is displayed in portrait, even though the keyboard is open.
I tried the reg tweak suggested, but found that that just caused even more confusion; portrait trying to change the landscape at the same time as the UI was trying to appear, at the same time as PocketShield was trying to put up its lock screen, basically chaos!
Any thoughts anyone, please?
My S2U2 v 2.42, has both of those options. Just go to Settings>Others
1. Action when connect to power>Unlock
2. Unlock when Keyboard is opened>On
Thanks. I've been trying out PocketShield all day and it seems that in its simplest terms there is a delay between switching on the unit and PocketShield realising it should be locking the screen, during which time it is possible to start an action which is then instantly stopped when PocketShield kicks in. Ridiculous.
I'll give S2U2 another shot now, cheers.
Smart unlock, its in the software worth installing section, does exactly what you want
I'm getting very frustrated here and beginning to think that my problem is nothing to do with one screen lock program or another, but with my unit.
Whichever screen lock I install, roughly 60% of the time the lock works as it should, but about 40% of the time there is a short period between powering on and the screen lock preventing me from doing anything. During this time it's possible to use the unit normally for a second or two until the screen lock kicks in, at which point often the unit gets confused, actions jam, and I often end up having to soft reset.
With all of the locks I've tried, if I open the keyboard and THEN power on, this also causes confusion.
Can anybody possibly shed any light on all this, please?
Could be that one of your installed applications is subscribed to the power on event and performs a very intensive processing each time device is turned on, delaying other subscriber apps such as lock screens. You might want to try uninstalling one by one to see if any culprit. Last resource is hard reset.
Thanks Pckshd. To be honest I've just had a rough day with the phone: it froze last night and on soft reset wouldn't boot up. This morning was the same story so eventually I was forced to do a hard reset. Then my most recent backup wouldn't restore, claiming there wasn't enough memory in the phone (how can that be? It was backed up from the phone!). Eventually I had to rebuild everything and right now haven't dared install any of the screen lock programs!
Is there not a registry entry anywhere that would show me which programs are taking priority over power on? My UI of choice, Winterface, as its own screen Lock, which is almost 100% reliable but regrettably continues to run went on mains power (I want one that unlocks on mains power, the desired feature that started all this off in the first place).
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