Database Info

PocketShield version 2.0

Unfortunately does not work on my device. Always getting error “Failed acquiring of the hook”.
Anyone tested already?
Previous version is great but this one promises some nice features…
Homepage: http://pocketshield.netserver01.com/

I have used PocketShield the past few days without any issue, both eval and retail versions. I have .NetCF 3.5 installed and stock ROM. I have ACT3.3 but haven't changed too much that I think would affect the program.

Solved
…found the issue. New version cannot coexist with PQzII (keyboard helper).

Does anyone have this application working on the Fuze. I was using 1.3 fine and now none of the 2.0 versions work without crashing on the device. Latest version I tried was 2.0.6.2 and it will crash constantly, anyone with a Fuze had any luck with this app.

Gave up on it and had too many issues on my fuze =/ It looked nice and I was going to buy it, but screw that. Until the bugs are fixed, I'll stick to SensorLock or TouchLockPro.

Kraize said:
Gave up on it and had too many issues on my fuze =/ It looked nice and I was going to buy it, but screw that. Until the bugs are fixed, I'll stick to SensorLock or TouchLockPro.
Click to expand...
Click to collapse
I like SensorLock, but it stopped working on my Fuze. Now it installs and runs fine, but doesn't lock anything! I have no idea what changed, I'm still running a stock rom.

hopper13 said:
I like SensorLock, but it stopped working on my Fuze. Now it installs and runs fine, but doesn't lock anything! I have no idea what changed, I'm still running a stock rom.
Click to expand...
Click to collapse
Same here...Now I'm using PocketShield....but not really happy. Wish SensorLock would work right and get an update. Oh well.

SensorLock also died on my fuze. I just reset the locking gesture to default. I now use TouchLockPro and it works much nicer than SensorLock.

I'm using TouchLockPro 1.5 also and really like it. Battery's great since switching from S2U2. Make sure to take a look at the registry tweaks (LockTouchPanelOnly is probably a must).

I tried the new version that was released today? or maybe a couple days ago. It worked fine for a while and I was happy. Until now. My power button has been *magically* mapped to PShield. WTF? whenever i click the power button it opens up Pshield rather than turning the screen off.

rifraf1 said:
Does anyone have this application working on the Fuze. I was using 1.3 fine and now none of the 2.0 versions work without crashing on the device. Latest version I tried was 2.0.6.2 and it will crash constantly, anyone with a Fuze had any luck with this app.
Click to expand...
Click to collapse
I've been using 2.0.6.2 for the past several days with no issues. I only use the finger slide unlock and I use the PocketShield dialer and phone plug-in.

The latest version 2.1 appears to be working well for me on the Fuze now. It has some enhancements over the 2.0.x versions that make up for the wait.

The more stuff they add the less I like it. I just want a simple easy to use screen lock to prevent "auto answering" the phone when taking it out of my pocket or case.The first version did just that. Seems like every new application starts out clean and simple, then turns into bloatware with more bugs and features then a person wants, added in. Taking over the standard dialer, pictures popping up on the screen, 30 option boxes in the menus. Ill pass on it all, I just want to lock my screen, and swipe it to unlock it period

yzf750 said:
I just want to lock my screen, and swipe it to unlock it period
Click to expand...
Click to collapse
altough i like the program, i agree with you.

Fuze Hardware Keyboard Locks Up/Disabled

I occasionally get into a mode where the hardware keyboard is non-responsive. Nothing on it works. I'm not sure if this is a defect on my particular phone, or if I've accidentally enabled some "feature" that causes the keyboard to be locked out. A soft reset will fix the issue, but that can be very annoying...
Has anyone else seen this?

Ken98045 said:
I occasionally get into a mode where the hardware keyboard is non-responsive. Nothing on it works. I'm not sure if this is a defect on my particular phone, or if I've accidentally enabled some "feature" that causes the keyboard to be locked out. A soft reset will fix the issue, but that can be very annoying...
Has anyone else seen this?
Click to expand...
Click to collapse
I have experienced this before, where the backlight wont even activate from pressing a button, and the keyboard certainly isnt typing anything on the screen either. Although usually i can fix this by sliding the keyboard back in, and then out again.... annoying yes, but its only happened twice in the month i have had my ATT Fuze, and i havent had to reboot like you mentioned.

When running my stock AT&T rom, I had this happen almost daily. Now that I flashed a new rom, I have yet to experience it again. I had to turn off/on my device in order for it to go away before.

Same problem here.
Sliding in and out does not work any more.
Resetting doesn't work anymore either...
Time to flash to original Roms?

Keyboard lock up
This happens to me too. I noticed that it happens more frequently when I set my wifi to best performance, and then try to type something. Keyboard becomes completely unresponsive. I usually have to soft reset.
I had the problem with stock ATT rom, NATF rom, and now with RRE 4.5SE Rom. I have tried the T9 dissabler, but it also did not work. My Fuze is only a few days old...
I notice this seems to be a common problem... No one seems to have answered this in any of the posts I've read. Is there a cab or patch or reg tweak that some one has come up with to deal with this? Can some one look into this???
Thanks so much in advance!
Mitch
*Edit*
Forgot to mention that this my second Fuze, sent the other one back because it was doing the same thing...

same unsolved issue here (wants me to crack my fuze)

Ive noticed this too... but what I do to correct the problem is hit the window key. It then activates the start menu. Then press it again to exit the start menu and the keyboard magiclly works again. At least for me anyway.

I have this problem occasionally, maybe twice with the ATT stock ROM, an once with the RRE 4.5SE ROM, mine rights itself after the application is closed and re-opened after a minute or so, so Im not that bothered, it is annoying though.

Nice, I'll try that..

Try the NATF ROM
Since I've switched over to the NATF ROM I haven't had a single problem with the keyboard.

tried NAFT v4 already with the same hq keyboard lock/die/shut down issue
Ken98045 said:
Since I've switched over to the NATF ROM I haven't had a single problem with the keyboard.
Click to expand...
Click to collapse

Same issue here, happened with both stock rom and NATF 4.1
It goes away after doing some random things like others have mentioned, but still annoying.

Spacebar problem on keyboard

My keyboard was working fine all this while until about 2 weeks ago it starts to act up. When I press the spacebar, sometimes it will create double spaces (instead of the usual one), and sometimes, it wouldn't work at all (meaning no space is created).
Does anyone else have this problem?
And just wondering, I have flashed my TP to ROMeOS, so if I were to claim warranty, does that mean I'll have to re-flash my TP back to the original firmware?

Bump - I really need some help.

Bump again! Mine is doing this at the moment. Stock ROM. UK Vodafone.

As far as going back to get it fixed by someone, yes, you would have to go back to stock SPL and stock ROM. It sounds like a pretty strange problem. The only thing I could think of is that you have some particles stuck underneath the space key since it's acting s erratically.

same problem here. I don't think that it is particles under the keyboard as that would not explain the double spacing issue.
I only noticed it on the R2A rom, don't remember it being there on the R1 so prob a rom issue.

I have this problem too

Figured I'd give this a good Ole Bump, because it seems that, although not widespread, it's still an issue. I'm running the Latest 6.5 ROMeOS on my Fuze and am having the SAME problems mentioned in the first post. I remember reading in Da_G's thread that there was something corrected in his ROM by using a custom xT9 dictionary? Anyone have any input? I'm (almost) positive this is not hardware related. It seems to be tied to the OS. Thanks in advance.

me too having the problem as well, i've it for more than 1.5 months i think, and no one having this in the earlier day which no one can help me out with it, but this few days i think i manage to solve this problem already, which i think it actually is a hardware issue, i used to use my right thumb to press spacebar and the problem occur, but since few days ago i try changing it to use my left thumb to press spacebar, who knows, the problem did not come to me since then... maybe you can try this, if not, i think you might gonna sent it back for warranty... hopes this helps...

I'm almost positive it has something to do with xT9. I just used a cab from my tilt days to disable xT9, and its happening FAR less than it was. But its still happening lol. Even with the regular stock non-finger-friendly keyboard set as the SIP. Back to the drawing board.

Well, I'm not sure if everyone else has read and figured out the problem, but it is now known what causes the spacing issue.
Apparently the newest builds have changes to the compime.dll file. These changes are what is causing the spacing problems, and (so far) can only be resolved by using the compime.dll from build 21731 or earlier. So how do we fix this
I know that Da_G has a package in his kitchen to change the dll back to an earlier one, but for the people that are using already cooked roms, what do we do?

djcaston said:
Well, I'm not sure if everyone else has read and figured out the problem, but it is now known what causes the spacing issue.
Apparently the newest builds have changes to the compime.dll file. These changes are what is causing the spacing problems, and (so far) can only be resolved by using the compime.dll from build 21731 or earlier. So how do we fix this
I know that Da_G has a package in his kitchen to change the dll back to an earlier one, but for the people that are using already cooked roms, what do we do?
Click to expand...
Click to collapse
If that's the problem, then this post might help you.
EDIT: But someone noted this problem with their stock ROM, which suggests a hardware issue, not a ROM problem.

I thought I'd post this since clearly I'm not the only one who suffers from this problem. After 6 months of living with this problem, I've decided to flash back to stock SPL and stock ROM and sent it to SiS for repair. They replaced the keyboard, and in just 2 days, I got my phone back (talk about a speedy repair!).
I don't know about you guys, but I'm almost positive mine is a hardware problem. I'm now using a WM6.5 TF3D2 ROM by shep211 and the keyboard seems to be working perfectly.

-accidentally double posted-

i got the same problem.
spacebar sometime can press sometime cant.
i think is hardware problem
anyone can guild me how to open n repair it?
my touch pro is not under sis. too bad.

Mine's been doing the same thing recently. I'm *hoping* this is an os issue, but I'm using stock original bloat free rom.
My has also been acting up tho (goofiness with Opera, rare and seemingly random shut offs and freezing) so I was hoping that a flash to a cooked rom would fix it.
I'm planning on doing it this weekend, if I get around to it I'll post here on my results.

I had the same problem. Went to the AT&T store and got a new phone

I too have been having this problem. I have been using NRG's roms for the past month (no blame on them) and the problem started to occur. Whenever I texted i would hardly ever get any spaces and it would double space when i did get it to work. I found that if i went slower and pressed harder it would work fine, however this is not a good solution. So i figured it was a hardware problem so i put everything back to default for ATT warranty purposes.
This is where it gets weird, the dumb thing starts to work again. I thought it was pure hardware failure because i had to press harder, but now that problem was gone.
So now I am running stock ATT rom but it is starting to double space ALOT. However this only occurs in the text message box. If i open word and type it is flawless. So is there a glitch in the text messaging program?

same problem here... happens when texting in my browser, in forums, in sms msging, all over...

I have a Samsung Omnia with a WM 6.5 build, and I noticed a similar problem, regardless of which onscreen keyboard I use. Basically whenever I type a dot (.) or press the spacebar, the previous letter would get selected (underlined) for a second, before the caret returns to the intended position. Typing the spacebar in a browser would indeed produce 2 spaces.
I assume it's related to the input/dictionary suggest feature, yet dis-/enabling this feature in the settings doesn't fix the problem. My guess is that the dictionary somehow thinks that a single spacebar press is a correct word, which is automatically expanded to the full word (1 space), followed by another space to put the following word.
This issue surfaced at some point (the rom initially worked fine after a hardreset).

same issue on my phone

phenomena.. spacebar works in android, not WM

So now with the dual boot options posted and available for such a wide range of devices, i've decided to try android out and check on its progress.
I have had issues with my keyboard ever since WM6.5 had been leaked.. so its been for a while now. i would have to press very hard on my backspace key, and my spacebar would be hit or miss. I would hit it, and sometimes get multiple spaces, other times nothing at all.
I even flashed the default ATT stock rom to see if it was a rom problem.. there have been many threads about this saying that this was a hardware problem, and i hate to open a new one, but i think this deserves a new thread.
I installed android this morning, and ALL my keys work as they are supposed to. So i would like to get confirmations from other people with this issue on Windows Mobile, by having them try android and see.
I return to windows mobile and the problem still exists. I go back to android and the problem is gone! so i can confirm this is NOT A HARDWARE ISSUE
I will upload videos later.

Contact AT&T warranty about this, and try to convince them to give you a Tilt 2, tell them you don't want to have the same phone and keep having problems and then having to replace it again and want to stay a happy customer.

im guessing its a conflict between the two, but thats just my guess, not totally sure why, try taking out ur memory card and soft reset or if ure phone is fresh from flashing, try a hard reset and dont put the card in yet, do a quick test on office mobile and see if the problem still exist

Nothing makes the spacebar problem go away on WinMo. It works in some ROM's (very few) but most of the ROM's the spacebar problem is back. I can confirm it is not a hardware issue. I just need to hunt for the ROM's on which the space bar used to work. I will try Andriod and report back if the spacebar issue is gone. Downloading now

I can now confirm. The spacebar has issueon EnergyROM but has no issues while using android. TurboX2 good job on noticing this.
Next question how do we go about fixing this?

tael and energy gave me issues, my current one is captains and have no spacebar issue here

so does this mean that the keyboard issue is something that could potentially be solved with some modification to the keyboard driver?

i have a feeling that this will never be solved :/
the whole scenario just doesn't make sense.. like i said... you would think reverting back to stock should have made the keyboard work again.. but nope not for me at least

If I had to guess, I would think that the results you are seeing is a result of either a more sensitive driver or a driver with a more effective signal parser that can distinguish the button press despite the hardware being worn. I'm not sure how that could be used to our advantage but at least its something to go on.

[Q] 4.0 Keypad not responding/loading

Hello all,
I apologize in advance if this problem was solved before, I could not find it.
I have a Galaxy Note (GT-N7000) with Android 4.0.3. For a few weeks now I've been having problems with the onscreen keypad. Everything is working normal when suddenly the keypad stops responding. I can still touch other things on the screen and scroll through menus as normal, it's just the keypad that stops working. When I reboot the device, the problem is usually solved. As of yesterday, I have (occassionaly) had the same problem but the keypad doesnt even load. The page is sized down to accomodate the pad but there's just a black rectangle. To solve this, I needed to reboot twice.
I'm pretty sure this has to be software-related seeing as the rest of the apps/screen keeps working.
Thanks in advance for any help.

Anyone had this same problem? It's happening more frequent now, about twice a day.

Same problem here
I have the same problem and its driving me nuts! If i drag down the notification bar and click the "Select Input Method" button, nothing happens.
Tried going through settings menu and changing to stock/swype and still cannot enter anything. Swype even shows the word i entered in the suggestions bar but nothing appears in the text entry box!
Im so glad it's not just me. Do you use a custom keyboard? I use Swiftkey 3 but as i said, i tried switching to another keyboard and still got nothing. I have even had the problem persist after reboots sometimes!!
Is there another ROM I can flash? I have stayed stock until now, but between this and the bluetooth drop out bug and speakerphone issues, I'm about ready to give up on Samsung's Official ROM :/

When the problems started I didn't have a custom keyboard but now I'm using SwiftKey. Since that change I haven't had as much problems. Only thing that happens now sometimes is when you type for example tree and every keystroke after that then copies ree so you get treereereereereereeree.
There are certainly other ROMs but I'm not really into that so you should search the forum. I'm still (relucantly) using the official ROM.