[Pipo-Project] M7Pro kernel

[d33]

OK - I've sorted the CT363 for once and all! As stated above - only flash AFTER successfully flashing a stock firmware in you have a CT363 touchscreen for now.

v1.34.10

Notes:
Amended CT36x driver to be configurable and to avoid flashing new firmware.

[TriA]

1.34.09 - no changes to BT...
1.34.10 - no touch screen

[d33]

v1.34.11

Notes:

Released GPIO reservations on CT363 TS
comment out avs_init

[raxy]

v1.34.11

Notes:

Released GPIO reservations on CT363 TS
comment out avs_init

wifi OK
usb audio OK
bt starts OK
gps starts OK (did not go outside to test reception)
touchscreen OK
brightness range and progressivity OK

sofarsogood

here is syslog capture with an USB DAC attached while booting:

[d33]

<6>[    3.906733] [BT_RFKILL]: Enter rfkill_rk_init
<6>[    3.906791] [BT_RFKILL]: Enter rfkill_rk_probe
<6>[    3.906832] [BT_RFKILL]: init gpio
<6>[    3.906847] [BT_RFKILL]: Succesfully gained ap6476_poweron gpio.
<6>[    3.906867] [BT_RFKILL]: Succesfully gained ap6476_wake gpio.
<6>[    3.906883] [BT_RFKILL]: Succesfully gained ap6476_wake_host gpio.
<6>[    3.906900] [BT_RFKILL]: Request irq for bt wakeup host
<6>[    3.906925] [BT_RFKILL]: ** disable irq
<6>[    3.906941] [BT_RFKILL]: Succesfully gained ap6476_rts gpio.
<6>[    3.906957] [BT_RFKILL]: setup rfkill
<6>[    3.907027] [BT_RFKILL]: Enter rfkill_rk_set_power
<6>[    3.907041] [BT_RFKILL]: Set blocked:1
<6>[    3.907051] [BT_RFKILL]: blocked is set to true
<6>[    3.932477] [BT_RFKILL]: bt shut off power
<6>[    3.932495] [BT_RFKILL]: reset GPIO is invalid
<6>[    3.932515] [BT_RFKILL]: ap6476 device registered.
....
<6>[  157.413977] [BT_RFKILL]: Enter rfkill_rk_set_power
<6>[  157.414007] [BT_RFKILL]: Set blocked:0
<6>[  157.414024] [BT_RFKILL]: Blocked is set to false, Wakeup!
<6>[  157.414053] [BT_RFKILL]: Enter rfkill_rk_sleep_bt
<6>[  157.414094] [BT_RFKILL]: *** bt sleep: 0 ***
<6>[  157.442610] [BT_RFKILL]: Reset GPIO is invalid
<6>[  157.442651] [BT_RFKILL]: bt turn on power

All looks healthy

[TriA]

1.34.11
touchscreen ok
but I'm still unlucky with BT
This time, before I took the DMESG, I tried to turn on BT, transfer a file (unsuccessfully) and turn it off

and there are absolutely no problems with BT on stock kernel

[d33]

wifi OK
usb audio OK
bt starts OK
gps starts OK (did not go outside to test reception)
touchscreen OK
brightness range and progressivity OK

sofarsogood

here is syslog capture with an USB DAC attached while booting:

Yepp, I think this is done now.

[TriA]

Here is dmesg with the stock kernel, after similar actions:
cold boot, turn on BT, transfer a file (this time with success) and turn it off

[raxy]

i face something strange:
any request to Internet is slow as hell!
rebooted many times, reinstalled opera, cleared cache and dalvik cache without success,
will revert to another kernel to see if it is kernel related...


edit: flashed kernel 1.32.7 and internet speed became OK,
flashed kernel 1.32.17b and internet speed still OK
reinstall 1.34.11 then slooooowwww wifi
flashed kernel 1.32.17b and internet speed OK again

[JohnThomson]

Hello, I am testing 1.34.11, but encounter something funny. On my tablet all Icons are exchanged
right to left. Volume up becomes back Home becomes volume down etc. With difficulty I got to settings
and the Kernel identifies as 3.0.36+ by darrell on May 20th. Hard to test further. Anyone have any idea.
I start to think that all M7's are different !
Kind regards to the developers, John

[d33]

Hello, I am testing 1.34.11, but encounter something funny. On my tablet all Icons are exchanged
right to left. Volume up becomes back Home becomes volume down etc. With difficulty I got to settings
and the Kernel identifies as 3.0.36+ by darrell on May 20th. Hard to test further. Anyone have any idea.
I start to think that all M7's are different !
Kind regards to the developers, John

Do you mean the function of the icon changes? That probably means the touchscreen is reversed left to right (x-axis). I can build you a 'special one'

[JohnThomson]

Yes, exactly so. I just checked version 1.34.10 and it is the same, earlier than that I think not.
Also not a problem with the Riley rom's. Would appreciate your help.
Kind regards, John

[d33]

v12

Changelog:
Upped the VCC_Jetta voltage to 3V from 2.8. It has been reported to improve wifi chip stability
Reversed x-axis for CT363 Touchscreen

For Raxy & SteveJC - I've pushed the code so that you can get involved too.

[edit]

Just noticed that the original stock DMESG had this at 1.8v! I've made v13 with this

v13

Changelog from 11
LDO6 - 1.8V
Reversed x-axis

[TriA]

by the way, what is LDO8?
3.0V in the stock dmesg
2.8V with 1.34.11

[d33]

by the way, what is LDO8?
3.0V in the stock dmesg
2.8V with 1.34.11

Code tags are "vcc 28 cif" so 2.8v sounds correct??