[Pipo-Project] M7Pro kernel

[d33]

[Pipo-Project] M7Pro kernel

Regarding screen I fixed my error and will post new kernels later


Sent from my iPhone using Tapatalk

[d33]

Right - got the screen back on again!

v1.20 - this has a switch to stop VTL CT363 bootloader flashing the firmware so needs to be flashed after a working kernel

[stevejc]

Right - got the screen back on again!

v1.20 - this has a switch to stop VTL CT363 bootloader flashing the firmware so needs to be flashed after a working kernel

ok screen on but same problem with touchscreen

[raxy]

vtl ts

ok screen on but same problem with touchscreen

Let's survey if vtl TS is a significant part of the touchscreens on the m7p owned by freaktabers,
I am afraid that working goodix ts could be messed up by tentatives to make the same kernel tree work also on a weird vtl ts

[Slowry]

ok screen on but same problem with touchscreen

Very strange if the firmware is the stock one...

I use the driver in the ct36x dir not the ct36x_ts (it doesn't exist in my JB source !)

This driver works on M6 max, with xmax=1024 and ymax=768 and ct363 model.

To find the ymax and xmax you can read the ts events; proceed like this :

with stock kernel,

adb shell
su
getevent /dev/input/event1

now in landscape mode, touch the screen and you should see events values (quit noisy, press and release events)
if i remenber good, something like :
035 followed by x value in hex
036 followed by y value in hex

Upper left should be 0,0 and lower right should be xmax, ymax.

For example : 0x400 and 0x300 for max m6.

getevent -lp /dev/input/event1 (should be better !)

[stevejc]

Very strange if the firmware is the stock one...

I use the driver in the ct36x dir not the ct36x_ts (it doesn't exist in my JB source !)

This driver works on M6 max, with xmax=1024 and ymax=768 and ct363 model.

To find the ymax and xmax you can read the ts events; proceed like this :

with stock kernel,

adb shell
su
getevent /dev/input/event1

now in landscape mode, touch the screen and you should see events values (quit noisy, press and release events)
if i remenber good, something like :
035 followed by x value in hex
036 followed by y value in hex

Upper left should be 0,0 and lower right should be xmax, ymax.

For example : 0x400 and 0x300 for max m6.

getevent -lp /dev/input/event1 (should be better !)

Thanks for you tip :

I got 0x77F for X (1919) and 0x4af for Y (1199)

So it confirms it's 1920 x 1200

With stock firmware : I got event 0000 / 0039 / 0035 / 0036 / 0000 / 0039
With new kernel : I got event 0002 / 0000 / 0035 / 0036 / 0002 / 0000

[raxy]

Sounds like a plan.

Let me know if I can help.

Hi, I suggest you try to mix the 1.17 kernel from Dee for M7P with an android from latest maackie's M6pro firmware into a freakatab ROM and we'll try that frankenstein on our goodix TS equiped M7P,

what do you think ?

[stevejc]

Hi, I suggest you try to mix the 1.17 kernel from Dee for M7P with an android from latest maackie's M6pro firmware into a freakatab ROM and we'll try that frankenstein on our goodix TS equiped M7P,

what do you think ?

The screen resolution will not be good , need M8Hd Rom with GPS enabled in code

[stevejc]

After editing in hex the stock firmware I found that the kernel has the goodix driver and ct36x ct363 driver not VTL.

the dat file use is CT363LR2030D_1920x1200_V25130327FN.dat (I found the hex data in code)

[d33]

[Pipo-Project] M7Pro kernel

After editing in hex the stock firmware I found that the kernel has the goodix driver and ct36x ct363 driver not VTL.

the dat file use is CT363LR2030D_1920x1200_V25130327FN.dat (I found the hex data in code)

That's what I used in 1.17


Sent from my iPhone using Tapatalk

[d33]

After editing in hex the stock firmware I found that the kernel has the goodix driver and ct36x ct363 driver not VTL.

the dat file use is CT363LR2030D_1920x1200_V25130327FN.dat (I found the hex data in code)

1.21 - uses ct36x ct363 driver and dat file CT363LR2030D_1920x1200_V25130327FN

[stevejc]

1.21 - uses ct36x ct363 driver and dat file CT363LR2030D_1920x1200_V25130327FN

Hi, I've tested myself too, but get same result the touch zone is not the entire screen (don't know why).

And the X / Y axes are swapped and X axis must be reversed.

It must be the same that VTL driver config used, so need to change code to change it.

But the problem is not really here is the fact that the touch zone is only :

40% - 100 % for X axis
0 - 100 for Y axis (good)

I don't see why the left part of the screen has no touch input !

don't bother with that I will try to do by myself, as normal M7pro has goodix touchscreen and your 1.17 is working good

thanks, will report if I get success

[rrileypm]

Sounds like we are making kernel progress. Tomorrow, I'm planning to flash the M8HD ROM with the new M7 Pro kernel and see where we are at with regard to a whole new ROM. If anyone has time to test this in the meantime, feel free to do so and report.

I'm gathering that we are still trying to get Steve's tablet going...but we already have a working ROM for those tablets that haven't had changes in the touch screen hardware?

[d33]

v1.22 for stevejc

[edit] fixed link typo

[stevejc]

v1.22 for stevejc

You have an error in your link it's freak-tab, but I get It

The axes are good now but I have always the problem of the touch zone

No touch input on the left part (40%) and 5% of the bottom part.


I look again at the stock firmware and there is another dat file just after the first one

I have extract it , in hexadecimal (don't found it in other dat file)

need to convert it to dat format, will try tomorrow

here is : second_CT363.zip

nb : in last JB code for ct36x, there are two dat included


Here is extracted dat file : second_CT363.dat.zip