• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

Clockworkmod gui

85 posts in this topic

Posted

Okie,

Here's the latest CWM in updateable clockwork script.

Can you let me know your feedback on this please?

Cheers,

B)

photom_cwm_update_skate.zip

0

Share this post


Link to post
Share on other sites

Posted

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

0

Share this post


Link to post
Share on other sites

Posted

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? :)

0

Share this post


Link to post
Share on other sites

Posted (edited)

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

Edited by philmein
0

Share this post


Link to post
Share on other sites

Posted

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

So anyone else want to give this a spin?

Cheers, B)

0

Share this post


Link to post
Share on other sites

Posted

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

0

Share this post


Link to post
Share on other sites

Posted

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... :)

0

Share this post


Link to post
Share on other sites

Posted

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 anythingdry.gif

0

Share this post


Link to post
Share on other sites

Posted

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 anythingdry.gif

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... :)

0

Share this post


Link to post
Share on other sites

Posted (edited)

maybe this bit is not working + or - fingerprint icon

wish somebody else would try it to see if its me

Edited by philmein
0

Share this post


Link to post
Share on other sites

Posted

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)

0

Share this post


Link to post
Share on other sites

Posted

Bump :D

0

Share this post


Link to post
Share on other sites

Posted (edited)

this looks beyond me i wish somebody else could helpsad.gif

i have to try no pain no gainrolleyes.gif

Edited by philmein
0

Share this post


Link to post
Share on other sites

Posted

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

Microsoft Windows [Version 6.1.7601]

Copyright © 2009 Microsoft Corporation. All rights reserved.

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

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.d

at (21)

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

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.d

at (20)

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

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.d

at (19)

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

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.d

at (18)

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

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.d

at (17)

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

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.d

at (16)

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

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.d

at (15)

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

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.d

at (14)

0

Share this post


Link to post
Share on other sites

Posted (edited)

the + and middle sensitivity buttons have no effect seems to be stuck at 0 coz i cannot use + or middle reset button

hope this helps tom

more text

tail -f /tmp/recovery.log Microsoft Windows [Version 6.1.7601]Copyright © 2009 Microsoft Corporation. All rights reserved.C:\Users\philmein>adb shell~ # tail -f /tmp/recovery.logtail -f /tmp/recovery.logW:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)W:minui: ev_get(...) - Decreased sensitivity to 0W:WriteTouchSensitivityData: bytesWritten = 1W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (0)

Edited by philmein
0

Share this post


Link to post
Share on other sites

Posted (edited)

do you have enough info from the posts above tom??

once the nn went to zero i could not increase to make it go upwards

Edited by philmein
0

Share this post


Link to post
Share on other sites

Posted

do you have enough info from the posts above tom??

Thanks for that, will investigate this ... :)

Cheers,

B)

0

Share this post


Link to post
Share on other sites

Posted

does it make sense tho and have i done the adb thing right

0

Share this post


Link to post
Share on other sites

Posted

does it make sense tho and have i done the adb thing right

Ho yes it makes sense.

And yes you've done the adb correctly :)

0

Share this post


Link to post
Share on other sites

Posted (edited)

good my pulse will start getting back to normal now lolrolleyes.gif

after all the effort you have put into this i will not give up in this threaddry.gif

Edited by philmein
0

Share this post


Link to post
Share on other sites

Posted (edited)

Hiya :)

I have updated the recovery image, here for you to try out, this is flashable via clockwork.

Now, I have added extra debugging and runtime checking on the touch input, so please, do the following to get the output I am looking for or expecting. :)

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, as for an example this is what I get when tapping on the icon with the fingerprint and plus combined, looking at it you can tell from the below output, that I tapped it a few times until it reached 30 and then resetted back to 22. Then I tapped on the icon with the fingerprint and minus, to increase the sensitivity....
W:minui: ev_get(...) - Increased sensitivity to 23 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (23) W:minui: ev_get(...) - Increased sensitivity to 24 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (24) W:minui: ev_get(...) - Increased sensitivity to 25 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (25) W:minui: ev_get(...) - Increased sensitivity to 26 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (26) W:minui: ev_get(...) - Increased sensitivity to 27 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (27) W:minui: ev_get(...) - Increased sensitivity to 28 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (28) W:minui: ev_get(...) - Increased sensitivity to 29 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (29) W:minui: ev_get(...) - Increased sensitivity to 30 W:minui: ev_get(...) - Sensitivity increase threshold reached. Resetted to 22 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (22) W:minui: ev_get(...) - Increased sensitivity to 23 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (23) W:minui: ev_get(...) - Decreased sensitivity to 22 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (22) W:minui: ev_get(...) - Decreased sensitivity to 21 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (21) W:minui: ev_get(...) - Decreased sensitivity to 20 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (20) W:minui: ev_get(...) - Decreased sensitivity to 19 W:WriteTouchSensitivityData: bytesWritten = 1 W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (19)
To end the adb command, hit Ctrl+C then
exit

Finally pull the usb cable

Let me know how that goes for you.

Cheers B)

photom_cwm_update_skate.zip

Edited by t0mm13b
0

Share this post


Link to post
Share on other sites

Posted

hey i know your busy with this but you seem to know allot about clockworkmod & such, so could you please have a quick look at this http://android.modaco.com/topic/346580-rom-bluemonte-custom-rom-zte-skate-omc-new-v16-available/page__st__220 POST #224

& tell us wot we are doing wrong

we are trying to get a rom domp from the users factory unlocked skate using sebastions404 method for a clean dump,

of course if you have not got time its cool, just we cant send Sebastian404 a message for some reason huh.gif

hope you dont mind me asking this sad.gif

thanks smile.gif

0

Share this post


Link to post
Share on other sites

Posted (edited)

hey i know your busy with this but you seem to know allot about clockworkmod & such, so could you please have a quick look at this http://android.modaco.com/topic/346580-rom-bluemonte-custom-rom-zte-skate-omc-new-v16-available/page__st__220 POST #224

& tell us wot we are doing wrong

we are trying to get a rom domp from the users factory unlocked skate using sebastions404 method for a clean dump,

of course if you have not got time its cool, just we cant send Sebastian404 a message for some reason huh.gif

hope you dont mind me asking this sad.gif

thanks smile.gif

No problem :)

Sebastian404 has his pm messaging switched off hence you cannot send him a message directly via modaco forums.

Well, looking at post #224, I can see there's something amiss here....

The fastboot.... well... it looks incorrect to me ... you're attempting to boot a recovery image....

The best and reliable method to use is this, flash it into the recovery partition, not the boot partition... as in:


fastboot-windows flash recovery recovery.img

As a side note: for flashing the boot.img, which is different to the recovery.img do this:

fastboot-windows flash boot boot.img

then to reboot:

fastboot-windows reboot

It seems that from looking at the screenshot as per on post #224 that you included, fastboot-windows, seems to have written recovery.img into the boot partition.... :) Edit: Mind you - I have not tried that method
fastboot boot recovery.img

either!

Hope this is of help, B)

Edited by t0mm13b
0

Share this post


Link to post
Share on other sites

Posted

cool, thanks for having a look smile.gif

0

Share this post


Link to post
Share on other sites

Posted

Bump :D

For Philmein, please refer to post #71 above :D

0

Share this post


Link to post
Share on other sites
This topic is now closed to further replies.

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.