Mod Version Of ClockWorkMod Recovery for Racer

[Guest Racerboy]

Hi guys, how does the possibility of having touch screen options aswell as normal vol- vol+ make call end call buttons to control CWM sound? The guys in the Blade section have created a Gen2 version for the Blade which is great, i`ve asked them if they could create a Racer gen1 version and if enough people are interested from the Racer forum this could happen......

The thread for the discussion is HERE so please if you can vote up my request which i`ve posted already on the thread or post your own show of support for our device that would be great.......Thx

[Guest t0mm13b]

Hi guys, how does the possibility of having touch screen options aswell as normal vol- vol+ make call end call buttons to control CWM sound? The guys in the Blade section have created a Gen2 version for the Blade which is great, i`ve asked them if they could create a Racer gen1 version and if enough people are interested from the Racer forum this could happen......

The thread for the discussion is HERE so please if you can vote up my request which i`ve posted already on the thread or post your own show of support for our device that would be great.......Thx

Hi Racerboy,

I am the guy responsible for the CWM mod code, so...

Couple of questions:

1. where is the kernel source used for your recovery kernel?
   
2. where is the kernel source used for your main ROM kernel? (Those two are to enable me diff the configs to find any differences and preferably - include the linky to the github if there is one)
   
3. What base address do you use for loading the kernel?
   
4. What is Gen1 address? (Do you have Gen2?)
   
5. What screen resolution is it? 800x480, 320x240 or what?
   

It would be appreciated if you can let me know. :)

As I do not have a Racer, I have no idea if this would work or not...bear with me on this ;)

Cheers,

B)

Edited September 1, 2011 by t0mm13b

[Guest equiliym]

1. i think sebastian404 know this

2. my guess is this is the kernel tigtex and deadlink compiled since deadlink gave this git on 4pda

https://github.com/TomGiordano/kernel_zte_blade

3. someone should fill me on this since i dunno

4. also this, Gen1 by default, Gen2 on russian 2.2 update, tpt files available somewhere

5 320x240

not much of a help. huh :(

[Guest Racerboy]

hey thanks for replying, like equiliym said:

1. Sebastian404 is the best person to ask

2. Main Rom kernal used at the moment is Deadlink 2.6.32.9#64 for the 4pda roms, which are considered the best as yet but i cant get you source code for it....Tigtex Kernal is 2.6.32.9-perf tigtex#1 again i cant get source code for it.

3. I dont know myself, i dont create ROMS but Sebastian404,Tigtex i think they should know...

4. same as no.3

5. 320x240

sorry cant give you more info about it

[Guest Phoenix Silver]

Humm we need kernel source code if we want to compile a version for the racer.

There is an app you have to try later too to look which event the screen use

In blade the screen is on event0

The hard keys are on event1

What our app do to simplify is read event0 and write event1

But each phone have different events

Should be found too

[Guest t0mm13b]

Humm we need kernel source code if we want to compile a version for the racer.

There is an app you have to try later too to look which event the screen use

In blade the screen is on event0

The hard keys are on event1

What our app do to simplify is read event0 and write event1

But each phone have different events

Should be found too

We are in the process of uploading a helper program to help diagnose the events shortly... :)

[Guest Racerboy]

We are in the process of uploading a helper program to help diagnose the events shortly... :)

you 2 work fast, thx hopefully it will help with some of the info needed

[Guest Phoenix Silver]

Someone in the racer forum can go here :

Evtest prog

Download the file port_cwm_gui.zip

And follow the instructions of the readme.txt

We'll need these infos to port the mod for the racer

Edited September 1, 2011 by Phoenix Silver

[Guest equiliym]

Humm we need kernel source code if we want to compile a version for the racer.

i already provided git of the kernel we use on racer, tigtex and deadlink worked both on it and we have two same kernels with just different names (tigtex/deadlink) that are more or less the same

edit: not sure if im doing it right but here are the results nevertheless:

ls /dev/input

event0  event1  event2  event3

# evtest /dev/input/event0

evtest /dev/input/event0

evtest: not found

# evtest /dev/input/event1

evtest /dev/input/event1

evtest: not found

# evtest /dev/input/event2

evtest /dev/input/event2

evtest: not found

# evtest /dev/input/event3

evtest /dev/input/event3

evtest: not found

# uname -a

uname -a

Linux localhost 2.6.32.9-perf #64 PREEMPT Thu Jun 23 01:00:24 SAMST 2011 armv6l

GNU/Linux

Edited September 1, 2011 by equiliym

[Guest Racerboy]

# cp /sdcard/evtest /data/local/tmp

# cd /data/local/tmp

# ls /dev/input

event0 event1 event2 event3

# evtest /dev/input/event0

evtest /dev/input/event0

evtest: permission denied

# evtest /dev/input/event1

evtest /dev/input/event1

evtest: permission denied

# evtest /dev/input/event2

evtest /dev/input/event2

evtest: permission denied

# evtest /dev/input/event3

evtest /dev/input/event3

evtest: permission denied

# uname -a

Linux localhost 2.6.32.9-perf #64 PREEMPT Thu Jun 23 01:00:24 SAMST 2011 armv6l

GNU/Linux

i get permission denied :blink: i must be doing something wrong, 3UK ZTE Racer, ROM 4pda #179 (racer kernal version 2.6.32.9#64 by deadlink)

Edited September 1, 2011 by Racerboy

[Guest t0mm13b]

Thanks guys for your rapid replies... :)

Just looked at it - it seems your handsets are not rooted!

This explains the permission denied....

:(

Edited September 1, 2011 by t0mm13b

[Guest Racerboy]

:blink: mine is definately rooted as all cm7 custom/ported roms for the racer come with ChainDD root app and i have apps installed that need root permissions :)

Edited September 1, 2011 by Racerboy

[Guest t0mm13b]

:blink: mine is definately rooted as all cm7 custom/ported roms for the racer come with ChainDD root app and i have apps installed that need root permissions :)

Oki - can you try this way?

go into /data/local/tmp (this is where you copied the binary evtest into)

cd /data/local/tmp

Make the binary executable

chmod +x evtest

Then invoke this

./evtest /dev/input/eventN

Let me know how that goes for you? :)

Cheers, B)

Edited September 1, 2011 by t0mm13b

[Guest Racerboy]

installed new rom yesterday and didnt set su permissions, but now i get same results as equiliym above "not found"

[Guest t0mm13b]

i already provided git of the kernel we use on racer, tigtex and deadlink worked both on it and we have two same kernels with just different names (tigtex/deadlink) that are more or less the same

edit: not sure if im doing it right but here are the results nevertheless:

ls /dev/input

event0  event1  event2  event3

# evtest /dev/input/event0

evtest /dev/input/event0

evtest: not found

# evtest /dev/input/event1

evtest /dev/input/event1

evtest: not found

# evtest /dev/input/event2

evtest /dev/input/event2

evtest: not found

# evtest /dev/input/event3

evtest /dev/input/event3

evtest: not found

# uname -a

uname -a

Linux localhost 2.6.32.9-perf #64 PREEMPT Thu Jun 23 01:00:24 SAMST 2011 armv6l

GNU/Linux

Thanks! :) Okie! Having a look here - it seems you did not copy the binary 'evtest' to /data/local/tmp and run it from there, for instance:

cd /data/local/tmp

cp /sdcard/evtest .

Also, to make it executable do this,

chmod +x evtest

Then run it from there on:

./evtest /dev/input/eventN 

If you get permission denied when running the program - you may have to do this before the last line above

su

Let me know how that goes for you?

Edited September 1, 2011 by t0mm13b

[Guest t0mm13b]

I have updated posts 13 and 15 above to reflect on my part where the permissions needs to be added...

Sorry for the inconvenience caused :)

[Guest Phoenix Silver]

Thanks! :)

Okie! Having a look here - it seems you did not copy the binary 'evtest' to /data/local/tmp and run it from there, for instance:

cd /data/local/tmp

cp /sdcard/evtest .

Also, to make it executable do this,

chmod +x evtest

Then run it from there on:

./evtest /dev/input/eventN 

If you get permission denied when running the program - you may have to do this before the last line above

su

Let me know how that goes for you?

A lot better honey :)

Readme.txt has been updated in the Web page.

[Guest Sebastian404]

someone mention my name?

Its been a LOOOOONNNNNNGGGG TIME.. how have you been, you monster......

erm,, try again...

Its been a LONG time since I messed with the racer, but I seem to recall I had quite a fight to get the 2.6.32 kernel to work on the racer, and I might of given up and stuck with an older source to make a custom kernal for CWMR.. I will check my dev box at the weekend when I'm back home...

There are a Gen1 and Gen2 versions of the devices out there, and there is a TPT file set for people to mess with, hard to say which is more common now...

It is a LPDI screen ,so you'll have to make LPDI versions of the graphic assets... tho while your at it, make some HDPI too incase you ever port it to a tablet :)

[Guest Racerboy]

ok i`m getting results with new method but how do i capture results and where would they be saved too? do i do it for each event 0-3? i`m sorry i dont know much on this side of things but i`m learning :)

Edited September 1, 2011 by Racerboy

[Guest Phoenix Silver]

someone mention my name?

Its been a LOOOOONNNNNNGGGG TIME.. how have you been, you monster......

erm,, try again...

Its been a LONG time since I messed with the racer, but I seem to recall I had quite a fight to get the 2.6.32 kernel to work on the racer, and I might of given up and stuck with an older source to make a custom kernal for CWMR.. I will check my dev box at the weekend when I'm back home...

There are a Gen1 and Gen2 versions of the devices out there, and there is a TPT file set for people to mess with, hard to say which is more common now...

It is a LPDI screen ,so you'll have to make LPDI versions of the graphic assets... tho while your at it, make some HDPI too incase you ever port it to a tablet :)

Hey Sebastian long time :)

Kiss

Missed you

[Guest jm888]

Ok, results from Aussie T3020 phone:

# cd /data/local/tmp

# ./evtest /dev/input/event0

Input driver version is 1.0.0

Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0

Input device name: "msm-touchscreen"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 330 (Touch)

Event type 3 (Absolute)

Event code 0 (X)

Value 668

Min 69

Max 959

Event code 1 (Y)

Value 571

Min 0

Max 846

Event code 24 (Pressure)

Value 1

Min 0

Max 255

Testing ... (interrupt to exit)

========================================

# cd /data/local/tmp

# ./evtest /dev/input/event1

Input driver version is 1.0.0

Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0

Input device name: "mooncake_keypad"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 59 (F1)

Event code 102 (Home)

Event code 107 (End)

Event code 114 (VolumeDown)

Event code 115 (VolumeUp)

Event code 158 (Back)

Event code 231 (?)

Testing ... (interrupt to exit)

========================================

# cd /data/local/tmp

# ./evtest /dev/input/event2

Input driver version is 1.0.0

Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0

Input device name: "compass"

Supported events:

Event type 0 (Sync)

Event type 3 (Absolute)

Event code 0 (X)

Value -251

Min -5760

Max 5760

Event code 1 (Y)

Value 462

Min -5760

Max 5760

Event code 2 (Z)

Value -555

Min -5760

Max 5760

Event code 3 (Rx)

Value 0

Min 0

Max 23040

{{cut short - goes on forever?}}

================================\

# cd /data/local/tmp

# ./evtest /dev/input/event3

Input driver version is 1.0.0

Input device ID: bus 0x0 vendor 0x1 product 0x1 version 0x1

Input device name: "7k_handset"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 114 (VolumeDown)

Event code 115 (VolumeUp)

Event code 116 (Power)

Event code 142 (Sleep)

Event code 143 (WakeUp)

Event code 226 (Media)

Testing ... (interrupt to exit)

=================================

# uname -a

Linux localhost 2.6.32.9-perf #64 PREEMPT Thu Jun 23 01:00:24 SAMST 2011 armv6l GNU/Linux

#

===============================

Hope this helps.

[Guest Sebastian404]

Jm888. Did you dump the rom on your device?

[Guest jm888]

Jm888. Did you dump the rom on your device?

Hi, I'm running 2.3.5 #179.

Haven't taken a rom dump, what do I do with it when I get one?

cheers

edit - I have a CWM backup

Edited September 1, 2011 by jm888

[Guest t0mm13b]

Ok, results from Aussie T3020 phone:

# cd /data/local/tmp

# ./evtest /dev/input/event0

Input driver version is 1.0.0

Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0

Input device name: "msm-touchscreen"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 330 (Touch)

Event type 3 (Absolute)

Event code 0 (X)

Value 668

Min 69

Max 959

Event code 1 (Y)

Value 571

Min 0

Max 846

Event code 24 (Pressure)

Value 1

Min 0

Max 255

Testing ... (interrupt to exit)

========================================

# cd /data/local/tmp

# ./evtest /dev/input/event1

Input driver version is 1.0.0

Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0

Input device name: "mooncake_keypad"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 59 (F1)

Event code 102 (Home)

Event code 107 (End)

Event code 114 (VolumeDown)

Event code 115 (VolumeUp)

Event code 158 (Back)

Event code 231 (?)

Testing ... (interrupt to exit)

========================================

# cd /data/local/tmp

# ./evtest /dev/input/event2

Input driver version is 1.0.0

Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0

Input device name: "compass"

Supported events:

Event type 0 (Sync)

Event type 3 (Absolute)

Event code 0 (X)

Value -251

Min -5760

Max 5760

Event code 1 (Y)

Value 462

Min -5760

Max 5760

Event code 2 (Z)

Value -555

Min -5760

Max 5760

Event code 3 (Rx)

Value 0

Min 0

Max 23040

{{cut short - goes on forever?}}

================================\

# cd /data/local/tmp

# ./evtest /dev/input/event3

Input driver version is 1.0.0

Input device ID: bus 0x0 vendor 0x1 product 0x1 version 0x1

Input device name: "7k_handset"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 114 (VolumeDown)

Event code 115 (VolumeUp)

Event code 116 (Power)

Event code 142 (Sleep)

Event code 143 (WakeUp)

Event code 226 (Media)

Testing ... (interrupt to exit)

=================================

# uname -a

Linux localhost 2.6.32.9-perf #64 PREEMPT Thu Jun 23 01:00:24 SAMST 2011 armv6l GNU/Linux

#

===============================

Hope this helps.

Brilliant! :D

That's great - what screen resolution is that handset? 320x240 - its just the naming of the handset is what lead me to ask if there's any differences with the official ZTE Racer handset.... :)

Thanks a million for your feedback ... will look into this :)

Cheers, B)

[Guest Racerboy]

heres mine finally, 3uk ZTE Racer ROM 2.3.5 4pda #179, kernal 2.6.32.9#64 by deadlink

# ./evtest /dev/input/event0

Input driver version is 1.0.0

Input device ID: bus 0x0 product 0x0 version 0x0

Input device name: "msm-touchscreen"

Supported events:

Event type 0 (sync)

Event type 1 (key)

Event code 330 (touch)

Event type 3 (Absolute)

Event code 0 (X)

Value 887

Min 69

Max 959

Event code 1 (Y)

Value 723

Min 0

Max 846

Event code 24 (Pressure)

Value 313

Min 0

Max 255

# ./evtest /dev/input/event1

Input driver version is 1.0.0

Input device ID: bus 0x0 product 0x0 version 0x0

Input device name: "mooncake_keypad"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 59 (F1)

Event code 102 (Home)

Event code 107 (End)

Event code 114 (VolumeDown)

Event code 115 (VolumeUp)

Event code 158 (BAck)

Event code 231 (?)

# ./evtest /dev/input/event2

Input driver version is 1.0.0

Input device ID: bus 0x0 product 0x0 version 0x0

Input device name: "compass"

Supported Events:

Event type 0 (sync)

Event type 3 (Absolute)

Event code 0 (X)

Value -39

Min -5760

Max 5760

Event code 1 (Y)

Value 13

Min -5760

Max 5760

Event code 2 (Z)

Value -727

Min -5760

Max 5760

Event code 3 (Rx)

Value 0

Min 0

Max 23040

Event code 4 (Ry)

Value 0

Min -11520

Max 11520

Event code 5 (Rz)

Value 0

Min -5760

Max 5760

Event code 6 (Throttle)

Value 33

Min -30

Max 85

Event code 7 (Rudder)

Value 0

Min 0

Max 3

Event code 8 (Wheel)

Value 3

Min 0

Max 3

Event code 10 (Brake)

Value 0

Min -2048

Max 2032

Event code 16 (Hat0X)

Value 0

Min -2048

Max 2032

Event code 17 (Hay0Y)

Value 0

Min -2048

Max 2032

# ./evtest /dev/input/event3

Input driver version is 1.0.0

Input driver ID: bus 0x0 vendor 0x1 product 0x1 version 0x1

Input device name: "7k_handset"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 114 (volumeDown)

Event code 115(Volume Up)

Event code 116 (Power)

Event code 142 (Sleep)

Event code 143 (WakeUp)

Event code 226 (Media)