yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
in developer web site, check first post for url link.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Update about 2.2.4

Everything works 96% perfectly. gestures, light sensor, capacitive area, autolockonpoweron=0 ...

after using it for more than 24 hours and with at least 100 times turning screen on, only four times the device has woken up locked and with some clicks in screen before being locked, enough time to make an outgoing call. I still have to log it or to understand which pattern follows.

only one small issue with a concrete pattern:

if device is connected to power and the mobile receive a call that's is not answered because i'm away, when i return back to my mobile (device is not locked because is being powered) and unplug it from the power, then suddenly it locks. I know this is a very concrete situation that doesn't annoy me at all. Just to say it. BTW i will try to log it.

I have another issue, but i don't know if it is TLP related, i have to investigate it a bit more.

I'm testing Iconsoft Phonex and a couple of times when receiving a call and appearing the Phonex incoming call window, when trying to unlock the device, it has frozen. But maybe it is related to Phonex becasue it seems a bit buggy. i will disable TLP to see if those freezes still continue without TLP. I will try to log it to help you see if it is TLP related.

I haven't been able to log it becasue i had the logging feature disabled. I've just enabled it to catch these bugs when happenning.
[Touch Diamond, MDA Compact IV Themes and Apps] ConteMax:
Sorry, but it's possible to lock the device without press power button, so i can unlock just shaking it ? i think that is unuseful to press the power button to unlock device and then also unlocking it shaking, or not ?

Contemax
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Unlocking mechanisms don't work when screen is turned off just to save battery so i think it is not possible what you want. Think that continuosly polling light, capacitive and gesture sensors when device is turn off would drain your battery for sure.
[Touch Diamond, MDA Compact IV Themes and Apps] DomSim:
UnlockWhenConnected is already 0 so thats not the problem and my unlock sequence was 363 but have since changed it to 6353 and seems to prevent false unlocking but i would like to have it only unlock if it is in a ture portrait position so i can change the unlock sequence to just 3.
[Touch Diamond, MDA Compact IV Themes and Apps] datlang:
I have a probem after install 2.2.4.Everytime after I scroll the TF3D menu, my hardware button cannot function. Thats mean if I scroll my slide menu to the last tab then I try to press the Home button to go back to the today screen there is no respond even I tried all 4 buttons.
[Touch Diamond, MDA Compact IV Themes and Apps] momyc:
Datlang ,

I have same problem with 2.2.4 . Also the Gscroll it doesn't seem to respond either.

Also, with 2.2.4 I still missing calls .

I have setup the following :

Incomming= "TochLockAction.exe" Unlock

UnlockWhenConnected=1

LockTouchPanelOnly=1 .

With same setup the 2.2.1 is seems to work fine for my device.

I downgraded to 2.2.1 for now with which Gscroll seems to coexist well.

I'll keep to try the new versions , but the 2.2.1 is a backup for now.

ZR thank you for your work .
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Just checked this and can confirm that I too have that problem. If you unlock on the home screen all the hardware buttons work fine, if you move over to the programs tab the hardware buttons on the capacitive area stop responding. In fact it’s not just the programs tab, it can happen in any tab, but it is intermittent and only 100% in the programs tab
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
Here comes my next try. I hope this is more useful.

Would't it be easier to create a checkbox that the phohe is "locksuspend" when the stylus is put back in?
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Hi ZR, i'm sorry but i've detected a couple of serious bugs with a common pattern.

it seems it is not iconsoft phonex related becasue the freezes when being locked also happen using defaults WM dialer ( not phonex and not HTC dialer either)

I'm preparing the logs and the explanations to post here in a few minutes.
[Touch Diamond, MDA Compact IV Themes and Apps] johnlara:
Aside: Phonex

I noticed you are using Phonex...are you on a Sprint CDMA device? I purchased Phonex but found that it locked up so much (and did other nasties as well) that I just couldn;t bear it any longer, even though it looks like a solid user interface. What's your experience?
[Touch Diamond, MDA Compact IV Themes and Apps] johnlara:
THANKS! Don;t know how I missed it!

:eek: THANKS! I don't know how I missed taht link!
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
No just orange spain GSM.

Phonex has a few bugs, cpu load by itself (4-6%) and also affecting cprog.exe ( 1-2%) & shell32.exe (1-2%) ( being phonex running make increase cpu time of these processes! if phonex is not running these process are quiet!)

Phonex running in a just hard resetted device works fast without any kind of problem.

Phonex running in a device with a lot of installed apps, then sometimes it doesn't appear when relaunching it.

Phonex doesn't detect the pause (p) in a middle of a phone number.

...

This is why meanhile i'm just testing phonex and have yet not purchased it, i'm waiting until they fix these issues.

BTW this is not a phonex related threed so if you have more questions about it ask them to me privately and let's leave this threed for TLP related things.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
because you didn't read this first post entirely maybe? ;)
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
I have a similar problem with 2.2.4. It only happens intermittently, usually after the phone has been sleeping for a while. If I reset my device and slide Manilla from screen to screen and then press the Home key it works great, I go to the Home screen. Then on the Home screen if I press the "up" phone key, it will launch the dial pad. But after a long sleep, sometimes the Home key will not return me to the Home screen. Also, when on the Home screen, the "up" phone key will NOT launch the dial pad. Interestingly, if I go into another program or game and then press the "up" phone key, it will open the dial pad. Thus I have to assume that it has to do with how TLP interacts with Manilla over a long period. It seems that TLP degrades over time.

Usually, the back button works, but I can't tell if the "down" phone key is working on Manilla since it normally doesn't do anything while on Manilla.

I hope this helps in some small way to catch this bug. THANKS! :D
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
I've found that this same problem has cropped up for me after 2.2.4. One time, my phone got stuck vibrating on an incoming call -- had to soft reset. That's never happened on this phone before.

I'm wondering if maybe the fix for the vibrate hook on incoming calls has caused another issue with GScroll. I may try going back to 2.2.3 to see if the issue goes away.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Very strange, because LockTouchPanelOnly=1 means I do not do anything with the hardware buttons. I more think that it has to do with the TLP and GScroll combo and Gscroll is making sure the hardware buttons are not responding. But that is just a guess.

I cannot reproduce. Does the problem also exist without GScroll installed?

Everytime the battclock is recreated/locked I subclass my own wndproc and put back the original at destroy/unlock.

If also GScroll does the same, then maybe not the original wndproc is put back, coming into an inconsistent wndproc sequence?

Is this situation only occuring with GScroll combo?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You should make sure that in the sequence it will not unlock when taking out of the pocket. So only going to portrait seems not a good idea. Therefore I changed it into 343. You start normally with portrait, so 1 sequence is already ok, you then only need to upsidedown-portrait to unlock, 1 extra move with your wrist. But of course other gestures may suit you better.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It should just work, and I cannot reproduce and scratching my head for the cause :confused:

I double checked my code several times, apparently there is going something wrong with the number to int conversion and writing to the registry. I have dutch settings. Maybe I should experiment with other language settings.

I come back on this one, for sure.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for this detailed response. The strange thing I do not get this problem. Maybe I need to change the language setting from dutch to something else. I am scratching my head :confused:

Making a checkbox is a workaround, the real must be found.

I come back on this one, for sure.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I tried this too, no problem :confused:

Are you also using GScroll?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe TLP is too fast at poweron, causing this problem and TF3D is not so fast. Maybe I should subclass not immediately, but after a second or so?

Is this problem away without TF3D (standard Today screen)?

Do you also use GScroll?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately I have no time to look into it today. I expect indeed interferences with GScroll and TLP combo, both subclassing. So stay tuned :D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did not hook the vibrate, only do not vibrate myself anymore when there is an incoming call. So I think it is more a problem of the new subclassing :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Don't worry, take your time ZR, it must not be solved inmediately, meanwhile i've disabled gscroll during all the day and i haven't got a freeze at all and i will continue in such a manner until a fix comes up.

you will see i've tried to be enough clear & detailed in my log comments to make this task easier for you when you spend some time trying to figure out what's happenning.

btw, i feel you are really close to make TLP perfect.

thanks as always :)
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Nope, no other sensor apps are used...

Edit...

Try this sequence:

Press power button to wake up device.

Unlock via capacitive touch

Make sure your on TF3D home screen

Press the call button to bring up the dialler

Press the end button to close the dialler

Slide over to the programs tab

Press the home button (it should work but it doesn’t)

Edit 2

It is definitely something you do in TLP

Here is another example:

With TLP uninstalled (not disabled)

Go to people tab

Press the call button

TF3D automatically starts calling the person shown on the people tab

With TLP enabled

Go to people tab

Press the call button

TF3D just brings up the standard dialling pad
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
With 2.2.4 I still missing calls; I cannot answer, it does not respond when I press the button, even if it's unlock.

The home button does not bring me back to the clock, when pressed.

Thanks,

Eric
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
Only happens with TF3D, not on regular Today screen.

I do not use GScroll.
[Touch Diamond, MDA Compact IV Themes and Apps] jamesford:
TouchLockPro working on Imate 9502 with power button

TouchLockPro working on Imate 9502 with power button and it works fine so far. No stylus, and light senser. I will send settings later
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hello !

If I lock the phone with the "official" lock option I can still use the power button to turn on/off the screen.

This is not working with TLP locking and suspending the phone as reported in one of my previous mail.

Could be nice to have this possible with TLP

Thanks for this great app :)
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
but with the "official" lock option, you can't lock the HW buttons.

Currently TLP doesn't support to partially unlock certain HW bttons, ZR is looking for the way to do it so stay tunned for upcoming TLP releases.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Very interesting. Would loved to know what is working and what not.
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
the same... or not :)

I also don't use any other sensor application and I have seen the Home key failing with 2.2.4. However this sequence doesn't trigger it for me.

I also saw that once it is happening (home key failing in TF3D) it still works if I have any other program displayed beside TF3D. :confused:

This is the same for me.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There must be something wrong with TLP for some people.

Unfortunately, I cannot reproduce. I have a possible guess for a solution, which I will post in a next post.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.2.5 test version

I tried to solve some of the issues reported. I could not reproduce, so it is a long guess if this is an improvement.

Changes:

* tried to solve the stylus toggle time 99999999 and added extra logging in case it is not solved

* solved a small problem, when a call was connected, it was locked when ended (side effect of solving autolockonpoweron=0)

* tried to solve the reported problem because of subclassing the foreground window

Although I do not have the reported problem, I changed the approach I used.

In previous version I subclassed the foreground window when locked and undid that when unlocked. Now I only subclass when not already done and only undo this at destroy or exiting TLP. So I have introduced a linked list for remembering the foreground windows.

This aproach is also a step into the right direction of locking the hardware keys in another way (I hope). Because in the subclass I can catch the hardware buttons. But if the bugs are solved, only then I can go on in introducing new features.

So let me know, for the people having the reported problems, if this solves maybe the problems :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
Hi ZuinigeRijder,

nothing has changed. I have the logfiles attached. Hope it helps. Good luck.
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Great work, just tried version 2.2.5 and it does solve the problems with the hardware buttons not being recognised.

Thanks for that...

Just to let others know this is what I did: -

Uninstall Version 2.2.4

Soft Reset

Delete key HKCR>Software>ZuinigeRijder from Registry

Soft Reset

Install Version 2.2.5 to Device (Not Internal Memory)

Soft Reset

Configure TLP as Required

Now I know that is probably over the top but as ZuinigeRijder was not able to replicate the isses on his phone I decided not to take any chances with registry corruption...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the log files. I can clearly see now in TouchLockAction that on your phone the conversion gives a negative value, e.g.:

17:02:08 NumericUpDown2Int: [99999999]

17:02:08 Result: [-7937]

On my phone, it converts correctly.

I use Decimal(numericUpdown.Value).ToInt32() to convert it. Apparently this goes wrong on your phone. I use .NET 3.5, so maybe it is an implementation problem of .NET 2.0. But I also remember that someone had the problem too and had .NET 3.5 installed.

So definitely a bug in .NET!

The same problem is described here..

And a solution to this (.NET 2.0?) bug is described here..

So the workaround is something like:

x = Decimal.Parse(numericUpDown.Text);

Bad that I need to workaround bugs of .NET :mad:

I will try to solve this one in a next version.

Thanks for the input.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear that this bug is probably solved :)

So sometimes you can solve bugs with good thinking and looking again at the design, although I could not reproduce.

I took me some headaches :rolleyes: to think of a possible cause. I also had another option, to get the capacitive touches in RAW mode, but that would not give me the opportunity for the next step, of another way of locking the hardware buttons.

Hope that others also report that the problem disappeared (and no new ones introduced). :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
How can I get the version of .NET which is installed on my diamond?
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
In the windows directory there should be an app "cgacutil.exe", which shows the .NET version(s).
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
If you put version 2.2.5 as an official release and update the title of this thread then you will probably get more people trying it out and in the process debugging it for you.

I will keep you updated if I find anything else.

PS: one problem I do have is that it is very easy to enter a value in the settings that is not valid hence causing the possibility of corrupting the registry keys. One example is the “TouchLockAction.exe” Unlock setting. Not this time but last time I accidently entered “TouchLockPro.exe” Unlock and corrupted the registry as a result!

Drop down lists or a more user friendly settings app might resolve some of the issues people are having. Not a priority but just a thought...
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
could anyone introduce me how to unlock via g-sensor and the oriantation change-sequence 343?? since now i was not able to unlock the phone via g-sensor. battclock only shows me the first orientation change.
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
I have .NET 2.0 installed. Are there any known difficulties in installing .NET 3.5? How do I do that?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The grey area is because you overruled LockIndicator = 0. Due to my bug the background is not drawn, giving this effect. I will fix this in a next version, so you can specify any color you want. But I will then not draw the BattClock, only the rectangle.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That means that the capacitive NavSensor dll cannot be loaded. So either it is not implemented in Touch HD or that the dll is maybe named differently. I think it will be the first.

Apparently the Stylus is operating. You can use my predecessor application, Stylus(BattC)lock 1.6. This uses only the Stylus for locking. But it excludes the capacitive touches.
[Touch Diamond, MDA Compact IV Themes and Apps] johnny--2k:
So I have a question. I downloaded the app, and love it so far.

Is there a way to unlock the phone when the screen is off without pulling out the stylus?

I do a lot of driving, so having to pull the stylus out every time is a bit of a hassle while on the road.

Aside from keeping the backlight on to see the screen and draining extra battery, is there anything that can be done?

I just downloaded the latest version today.

Thanks for all your hard work!
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
read post 3 all the setting are there
[Touch Diamond, MDA Compact IV Themes and Apps] shattering:
I just downloaded the latest version and will try and give feedback soon.

You're really fast with this app, really appreciate it.
[Touch Diamond, MDA Compact IV Themes and Apps] snufkin:
I tried to reset and re-install v1.2 and did some more tests. I've found that the problem I've got was mainly because I pressed the power buttons and the capacitive areas too fast! I need to wait a while (around a minute??) after power off and after the screen comes out, I also need to wait for a while (few sec) before I can touch the capacitive area! Don't know why. I've not started any other application.

Also, I expected if the key and power button will only be locked when power on, I can resume the handset after suspend not only from power button but also other hardware buttons. However, the case is not. I can only use the power button to resume the handset.

Finally, for the batt drainage problem, I suspected the BattClock reading may not be accurate. When the reading was 83% only, I've found full bar in Settings>System>Power. :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] kwill:
thanks for the app, it was cool, but not what i was looking for. anyways i uninstalled but it seems that the app is still active even after soft reset. i put the stylus in and the device locks. take it out and then it unlocks. but, the app should be gone. unless my fuze was like that from the beginning:D ive tried checking the reg for left over files and the startup items with no luck
[Touch Diamond, MDA Compact IV Themes and Apps] raspdeep:
Did you disable the program (by running the program again will get a popup that ask if you want to disable) before installing?
[Touch Diamond, MDA Compact IV Themes and Apps] kwill:
yep, did that too.
[Touch Diamond, MDA Compact IV Themes and Apps] raspdeep:
Just downloaded v1.2 to test and have some interesting findings. With my settings, the software will hide the indicator after it unlocks! While using default settings, it will sit at the battery area even after unlock. I dont know if this is a bug but I like it :)

All I did was moving the indicator from top to bottom bar near the middle left of the keyboard icon. Also changing it to less intrusive color like grey foreground. If you have to fix this, please include a setting like AutoHideWhenUnlock because this feature is pretty cool.

Below is my reg file if you want to run using my settings. Disable the software first by running it. Rename the .txt to .reg and run it if you have associated the reg file with your registry editor to import the setting. If you have not associate .reg file, you can also try importing manually using your registry editor.

The settings are:

[HKEY_CURRENT_USER\Software\ZuinigeRijder\LockSettings]

"ClockForeground"=dword:00545454

"ClockX"=dword:fffffec5

"ClockY"=dword:00000250

"ClockWidth"=dword:00000030

"ClockHeight"=dword:00000030

"CapacitiveToggleTime"=dword:00001f40

"ClockClickable"=dword:00000001

"ClockBackground"=dword:00000000

"LockTouchPanelOnly"=dword:00000001

"SuspendOnBacklightOff"=dword:00000001

"LockIndicator"=dword:00000001

"Beep"=dword:00000000

"Vibrate"=dword:00000001

The software is pretty neat but there are still some bugs to fix :D

Can we have a setting to adjust the sensitivity of the capacitive touch? It is currently very unreliable so perhaps the hardware needs to be tweaked.
[Touch Diamond, MDA Compact IV Themes and Apps] raspdeep:
Is touchlockpro.exe still running in the background? You can check using a taskmanager (not the default HTC taskmanager).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can press the power button to turn the screen on and thereafter tripple touch the hardware area to unlock.

Another way, would be to disable "AutoLockOnPowerOn" so it will not autolock. When you are in your car, you must be sure you toggle the phone to "lock mode" disabled, by taking the Stylus OUT/IN within 1 second, before driving. But then the locking application is not active.

I use in my car a very simple, small telephone holder, which I can click on the ventilation ribbles. This did cost only 6 euro on the market, not special designed for the TD. On top of that I can attach the phone to a 12V loader. When it is powered by that, it is also automatically unlocked. And with the small battery, it is nice I can also charge the TD will driving.

The telephone holder is also fine for navigation. I like IGO8 more than Tom Tom, but that is a personal choice and offtopic.