[Pipo-Project] M9Pro kernel

[d33]

Test v1.08 - assume lcd will still not work?

[Edit] Re-uploaded with a version containing 4 new govenors to possibly align with SteveJC. I added InteractiveX, HotPlug, SavagedZen & SmartAss2

[edit2] Re-uploaded @16:28 UK time with fixed MIPI settings for LCD

Changelog (from d33 v1.07)

1. Fixed MIPI GPIOs - probably reason no working LCD
2. Fixed touchscreen orientations
3. Fixed accelerometer
4. Made code change for GPS - await feedback on whether working!
5. Added 4 additional Governors as mentioned above

[d33]

I added InteractiveX, HotPlug, SavagedZen & SmartAss2

Reference for those that don't know which govenor is best for them: http://androidforums.com/threads/and...lained.513426/

[BliND123]

Tested! Screen is working and everything looks normal so far with stock digitizer: https://drive.google.com/file/d/0B9O...ew?usp=sharing
With the replacement digitizer only saw 1-3 touches and then no more touches seemed to do anything (Edit: I couldn't tell where they were touching so can't really say if rotation is right): https://drive.google.com/file/d/0B9O...ew?usp=sharing

[bucefal82]

Test v1.08 - assume lcd will still not work?

[Edit] Re-uploaded with a version containing 4 new govenors to possibly align with SteveJC. I added InteractiveX, HotPlug, SavagedZen & SmartAss2

[edit2] Re-uploaded @16:28 UK time with fixed MIPI settings for LCD

Changelog (from d33 v1.07)

1. Fixed MIPI GPIOs - probably reason no working LCD
2. Fixed touchscreen orientations
3. Fixed accelerometer
4. Made code change for GPS - await feedback on whether working!
5. Added 4 additional Governors as mentioned above

overclockomatic3188.pl
found 2 tables DDR 8 and 9

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\bucefal82>overclockomatic3188.pl kernel.img
Integer overflow in hexadecimal number at C:\Users\bucefal82\overclockomatic3188
.pl line 225.
=============================
Rockchip Patchomatic Suite
Overclockomatic RK3188 v1.2
by phjanderson
=============================

Reading kernel image
Done!

Searching GPU frequency limit cap
Found: 133000000, 600000000
Patching...

Searching volt/frequency tables
Done!

Volt/frequency tables found in the image:
== Table 1 at offset 11544760 ==
MHz     mV
816     1000

== Table 2 at offset 11548424 ==
MHz     mV
500     1100

== Table 3 at offset 11548448 ==
MHz     mV
180     1150
300     1100
400     1150
500     1200

== Table 4 at offset 11548488 ==
MHz     mV
200     1000
300     1050
400     1100
500     1150
600     1200

== Table 5 at offset 11548536 ==
MHz     mV
816     1050

== Table 6 at offset 11559512 ==
MHz     mV
312     900
504     925
816     1000
1008    1075
1200    1200
1416    1250
1608    1350

== Table 7 at offset 11559576 ==
MHz     mV
133     975
200     1000
266     1025
300     1050
400     1100
600     1250

== Table 8 at offset 11559632 ==
MHz     mV
200     950     1 DDR_FREQ_SUSPEND
528     1250    256 DDR_FREQ_NORMAL

== Table 9 at offset 11559656 ==
MHz     mV
200     950     1 DDR_FREQ_SUSPEND
460     1150    256 DDR_FREQ_NORMAL

== End of tables ==

Please identify the CPU, GPU and DDR table. Press ctrl-c to cancel.

Which table is the CPU table?
(The CPU table is mostly the largest table ranging from 312 to 1608 MHz)

And worries

Integer overflow in hexadecimal number at C:\Users\bucefal82\overclockomatic3188
.pl line 225.

How to fix the script for overclocking?
Thanks in advance!

In the remaining core of the working
Thank you for a job

[d33]

overclockomatic3188.pl
found 2 tables DDR 8 and 9


And worries

Integer overflow in hexadecimal number at C:\Users\bucefal82\overclockomatic3188
.pl line 225.

How to fix the script for overclocking?
Thanks in advance!

In the remaining core of the working
Thank you for a job

CPU - 6
GPU -7
DDR -8
DDR for 3188T - 9 (not required)

[d33]

Tested! Screen is working and everything looks normal so far with stock digitizer: https://drive.google.com/file/d/0B9O...ew?usp=sharing
With the replacement digitizer only saw 1-3 touches and then no more touches seemed to do anything (Edit: I couldn't tell where they were touching so can't really say if rotation is right): https://drive.google.com/file/d/0B9O...ew?usp=sharing

So pretty much finished for standard model then? Good! Still need someone to test for GPS please.

Created v1.09 to try to get better fit for replacement digitizer

Changelog:

1. Swapped CT36x driver definition
2. Imported new .DAT file for CT36x

[bucefal82]

Created v1.09 to try to get better fit for replacement digitizer

On my tablet GPS does not work with this kernel
Is it possible to collect the same kernel but without inversion?
in this kernel works fine auto brightness.

[d33]

On my tablet GPS does not work with this kernel
Is it possible to collect the same kernel but without inversion?
in this kernel works fine auto brightness.

OK, so GPS needs more work. Did the stock kernel/SteveJC work for GPS?

I don't understand the question about inversion. What is inverted?

[alex_tv]

Flashed the kernel v1.09. Inversion-axis Y is preserved. In the horizontal position of the tablet "camera on UP" touchscreen mirror.

[d33]

Flashed the kernel v1.09. Inversion-axis Y is preserved. In the horizontal position of the tablet "camera on UP" touchscreen mirror. [ATTACH=CONFIG]temp_9605_1428059249125_456[/ATTACH]

Sorry I don't understand.

I can see your tablet has a CT363 Touchscreen and it initializes ok. What is the problem? What needs to change? Are you saying that Y-Axis is okay but X-axis needs to reverse?

[alex_tv]

I can see your tablet has a CT363 Touchscreen and it initializes ok. What is the problem? What needs to change? Are you saying that Y-Axis is okay but X-axis needs to reverse?

Axis X O.K. Reversed Y. May be change firmware?What firmware do you recommend?

[d33]

v1.09a & 1.09b uploaded

Changelog:

(a) Changed CT36x orientation string from 1,0,0,1 to 1,0,1,0
(b) Changed CT36x orientation string from 1,0,0,1 to 1,0,0,-1

[d33]

[BliND123]

Ok, with stock digitizer I don't get a touchscreen response from either kernel: 1.09a https://drive.google.com/file/d/0B9O...ew?usp=sharing and 1.09b https://drive.google.com/file/d/0B9O...ew?usp=sharing

On the replacement digitizer I get some movement with 1.09a on the first 5 inches of the left side of the screen. I can grab the clock but only dragging at an angle that I can't freely move, from top left to bottom right where the 5 inches that respond seems to stop: 1.09a https://drive.google.com/file/d/0B9O...ew?usp=sharing and 1.09b https://drive.google.com/file/d/0B9O...ew?usp=sharing

Edit: Forgot to say that I didn't see any movement on replacement digitizer with 1.09b and here I drew a little sketch on what I mean on 1.09a with the replacement digitizer. The section in red is the only place I see response and the only thing I can move which is the clock only moves in that angle I have in the arrows, I can't move it anywhere else: http://snag.gy/d9h9Y.jpg (edited screenshot showing all my tabs and bookmarks! LOL)

Also, I didn't get a DMESG for 1.09 but I couldn't get a response with it on the stock digitizer with it either so I went back to 1.08.

[d33]

Also, I didn't get a DMESG for 1.09 but I couldn't get a response with it on the stock digitizer with it either so I went back to 1.08.

How odd. I didn't amend any Goodix code. All I can see is that it fails to get a response from both GPIOs when it tries to communicate in your DMESG logs. I assume you are certain it was properly connected?

On the replacement digitizer I get some movement with 1.09a on the first 5 inches of the left side of the screen. .... I didn't see any movement on replacement digitizer with 1.09b

Okay, so it seems we don't have the right firmware .dat for your replacement in the build with that driver.