Clockworkmod gui

September 30, 2011

Okie,

Here's the latest CWM in updateable clockwork script.

Can you let me know your feedback on this please?

Cheers,

B)

September 30, 2011

all icons now showing up looking nice but the touch movement from the bottom four icons is very erratic arrow down icon and the one to the right of it hardly work but this cwm works fine in manual mode

September 30, 2011

all icons now showing up looking nice but the touch movement from the bottom four icons is very erratic arrow down icon and the one to the right of it hardly work but this cwm works fine in manual mode

Might try adjusting the sensitivity, by decreasing the sensitivity (if that's what you're describing as erratic), tap say 3 times on the icon with the fingerprint (right-most icon above the four arrows indicating plus, up, down and left arrow respectively) on it and see if that slows it down? :)

October 1, 2011

any chance another skate user try the cwm in post 51 and see what you make of the touch controls

Edited October 1, 2011 by philmein

October 1, 2011

Uhhh... think you mean post#51 :P :D

So anyone else want to give this a spin?

Cheers, B)

October 1, 2011

Uhhh... think you mean post#51 :P :D

So anyone else want to give this a spin?
Cheers, B)

the 2 right hand bottom touch icons dont work nearly as good as the two left ones blade version works great i have tried both and the touch controls don't feel right on the skate

October 1, 2011

the 2 right hand bottom touch icons dont work nearly as good as the two left ones blade version works great i have tried both and the touch controls don't feel right on the skate

Ho okie...

Well, the main principle is this - it builds and works.

That's a good thing, have tried to get it to build initially and failed as you can see from the earlier postings going back a while ago. :)

So... what is it that it does not feel right about it? Remember the Blade is smaller than the Skate, so it could be the size of the handset with the icons etc...

Are the icons wrong or what?

Think we need further input from others on this to get a second opinion... :)

October 1, 2011

it the arrow up button and the one to the right of it the menu options dont scroll yet the two buttons to the left arrow down and the one to the left work fine

dunno if the sensitivity buttons work cannot tell they don't flash or anything

October 1, 2011

it the arrow up button and the one to the right of it the menu options dont scroll yet the two buttons to the left arrow down and the one to the left work fine

dunno if the sensitivity buttons work cannot tell they don't flash or anything

You will know if the sensitivity works, tap on either + or - fingerprint icon a few times, the menu bar will fly off or slow down depending on the sensitivity - if you tap the middle, it resets to 22 (which is what is on the Blade), the - fingerprint icon, that will make it fly off... It retains the setting and remembers it next time you go into cwm mod :)

Bear in mind, about one thing, the touchscreen driver is slightly different to the Blade... :)

October 1, 2011

maybe this bit is not working + or - fingerprint icon

wish somebody else would try it to see if its me

Edited October 1, 2011 by philmein

October 1, 2011

maybe this bit is not working + or - fingerprint icon

wish somebody else would try it to see if its me

You can easily find out using the adb while in recovery.

Plug in the usb cable to handset and issue the commands below


adb shell

Once you're inside the shell within recovery do this.


tail -f /tmp/recovery.log

Now tap on the +/- with fingerprint icon and you should see in the output from the previous command, not necessarily in the order as shown in the quote below

minui: ev_get(...) - Decreased sensitivity to nn WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (nn) minui: ev_get(...) - Resetted sensitivity to nn WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (nn) minui: ev_get(...) - Increased sensitivity to nn WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (nn)

nn is a 2 digit number that indicates the sensitivity. To end the adb command, hit Ctrl+C then


exit

Finally pull the usb cable :)

That is logged in recovery.log found in the /tmp directory.

I am relying on your judgement if 22 (the default sensitivity found on the Blade) is the appropriate default number used for the Skate's specific touchscreen driver...

Cheers, B)

October 2, 2011

Bump :D

October 2, 2011

this looks beyond me i wish somebody else could help

i have to try no pain no gain

Edited October 2, 2011 by philmein

October 2, 2011

minus works see below but plus sensitivity has no effect it does not work

Microsoft Windows [Version 6.1.7601]

C:\Users\philmein>adb shell

* daemon not running. starting it now *

* daemon started successfully *

~ # tail -f /tmp/recovery.log

tail -f /tmp/recovery.log

ro.hardware=skate

ro.revision=0

init.svc.recovery=running

init.svc.adbd=running

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand, file not found...

W:ReadTouchSensitivityData: Could not open /cache/recovery/touchsens.dat - WTF!

mtd: successfully wrote block at c4bb400000000

I:Set boot command ""

W:minui: ev_get(...) - Decreased sensitivity to 21