[Pipo-Project] M7Pro kernel

[d33]

I see lots of glgps errors in logcat

.17 with VTL CT363 support removed

v1.32.17b

[cedbor]

Touchscreen is back, but still no file transfer and internet via bluetooth. And no GPS.

.17b and RileyRom-3.4.2

[tgray]

Hi D33,

I installed your .17b kernel with Rileyrom 3.4.2 and everything I have tested on my M7Pro is working (GPS, Bluetooth file transfer, Internet via Bluetooth, Camera). The only issue I have is that the HDMI does not work. I have attached the syslog and DMESG.

[cedbor]

Hmmm. And for me, hdmi is fine...

[tgray]

My HDMI works the first time after the new install with the .17b kernel but if I shutdown and restart it stops working. Also I just found that the USB OTG does not work.

[d33]

My HDMI works the first time after the new install with the .17b kernel but if I shutdown and restart it stops working. Also I just found that the USB OTG does not work.

Things that work and then don't are extremely difficult to 'fix' since they do work! I'll step through the HDMI code to see what may be the issue.

What is not working with OTG? Everything or just some devices? Is it a power issue?

[d33]

The OTG port appears to be initialising ok in "Both Device & Host" mode. I can provide variants for that do host only or device only as a test.

<6>[    2.888004] DWC_OTG: ^^^^^^^^^^^^^^^^^Device Mode
<6>[    2.888044] usb20_otg usb20_otg: DWC OTG Controller
<6>[    2.888141] usb20_otg usb20_otg: new USB bus registered, assigned bus number 1
<6>[    2.888200] usb20_otg usb20_otg: irq 48, io mem 0x00000000
<6>[    2.888233] DWC_OTG: dwc_otg_hcd_start controller in device mode,everest
<6>[    2.888301] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[    2.888341] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[    2.888384] usb usb1: Product: DWC OTG Controller
<6>[    2.888412] usb usb1: Manufacturer: Linux 3.0.36+ dwc_otg_hcd
<6>[    2.888444] usb usb1: SerialNumber: usb20_otg
<6>[    2.888735] hub 1-0:1.0: USB hub found
<6>[    2.888765] hub 1-0:1.0: 1 port detected
<6>[    2.893615] DWC_OTG: host20_driver_probe host2.0 reg addr: 0x101c0000 remap:0xdf200000
<6>[    3.104046] DWC_OTG: ^^^^^^^^^^^^^^^^^^Host Mode
<6>[    3.104073] usb20_host usb20_host: DWC OTG Controller
<6>[    3.104115] usb20_host usb20_host: new USB bus registered, assigned bus number 2
<6>[    3.104154] usb20_host usb20_host: irq 49, io mem 0x00000000
<6>[    3.104203] DWC_OTG: Init: Port Power? op_state=1
<6>[    3.104216] DWC_OTG: Init: Power Port (0)

HDMI appears ok

<4>[    3.253877] func rk_hdmi_power_init, line 1259:
<4>[    3.536339] CAT66121: Reg[0-3] = 0x[54].[49].[12].[16]
<4>[    3.536377] [CAT66121] Device found!
<6>[    3.635731] cat66121_hdmi 2-004c: cat66121 hdmi i2c probe ok

ooooh - here's something, maybe?

<6>[   11.133738] DWC_OTG: dwc_otg_hcd_enable, disable host controller
<6>[  287.943610] DWC_OTG: ********vbus detect*********************************************
<6>[  288.128808] DWC_OTG: ********soft connect!!!*****************************************
<6>[  288.134817] DWC_OTG: USB SUSPEND
<6>[  288.268332] DWC_OTG: USB RESET
<6>[  288.455743] android_work: sent uevent USB_STATE=CONNECTED
<6>[  288.459118] DWC_OTG: USB RESET
<6>[  288.711568] android_usb gadget: high speed config #1: android
<6>[  288.711801] android_work: sent uevent USB_STATE=CONFIGURED
<4>[  290.486882] DWC_OTG: req 80.06 v0303 i0000 l0200 protocol STALL; err -22
<4>[  290.598756] DWC_OTG: req 80.06 v0304 i0000 l0200 protocol STALL; err -22
<4>[  290.669109] DWC_OTG: req 80.06 v0303 i0000 l0200 protocol STALL; err -22
<4>[  290.775030] DWC_OTG: req 80.06 v0304 i0000 l0200 protocol STALL; err -22

[d33]

Logcat on HDMI:

05-17 08:38:32.749 D/HdmiControllerActivity(  985): onPreferenceThreeClick() ==>> isConnected=false
05-17 08:38:32.749 D/HdmiControllerActivity(  985): setHdmiConfig
05-17 08:38:32.749 D/AudioHardware(  131): AudioHardware pcm playback is exiting standby.
05-17 08:38:32.749 D/AudioHardware(  131): openPcmOut_l() mPcmOpenCnt: 0
05-17 08:38:32.749 D/alsa_route(  131): route_info->sound_card 0, route_info->devices 0  
05-17 08:38:32.749 D/alsa_pcm(  131): pcm_open(0x0001f000)
05-17 08:38:32.749 D/alsa_pcm(  131): pcm_open() card 0, device 0, Playback
05-17 08:38:32.749 D/alsa_route(  131): route_set_controls() set route 0
05-17 08:38:33.549 D/HdmiControllerActivity(  985): onPreferenceThreeClick() ==>> isConnected=false
05-17 08:38:33.549 D/HdmiControllerActivity(  985): setHdmiConfig
05-17 08:38:34.619 D/HdmiControllerActivity(  985): onPreferenceThreeClick() ==>> isConnected=false
05-17 08:38:36.449 D/HdmiControllerActivity(  985): onPreferenceThreeClick() ==>> isConnected=false
05-17 08:38:37.849 D/HdmiControllerActivity(  985): setHdmiOutputStyle
05-17 08:38:37.849 D/HdmiControllerActivity(  985): strbuf=1920x1080p-60
05-17 08:38:41.849 D/AudioHardware(  131): AudioHardware pcm playback is going to standby.
05-17 08:38:41.849 D/AudioHardware(  131): closePcmOut_l() mPcmOpenCnt: 1
05-17 08:38:41.849 D/alsa_route(  131): route_set_controls() set route 24
05-17 08:38:41.849 D/alsa_pcm(  131): pcm_close() card 0, device 0, Playback

[tgray]

Hi D33,

I have just tested the .17b kernel on a second M7 Pro and it does exactly the same thing as mine (bought by a friend about 3 month after I got mine). The HDMI & OTG work after flashing and if you just reboot they continue to work but as soon as you power off and then restart the tablets the HDMI and OTG no longer work. I check the OTG and it is not a power issue. Everything else works okay as far as I can tell (WIFI, Camera, GPS, Bluetooth file transfer & internet, etc).

[raxy]

tgray
maybe you should redo a complete nand flash of all partitions (from RROM 3.4.2) and not only the kernel's one so that no interference from previous ROM can occur.
If this confirms that all features are working, .17b would become a big milestone in freaktab's history !

[d33]

1.33.01

Removed VTL CT363 support for now
USB OTG set to Host/Slave but now defaults to HOST (was USB_ID dependant)

Download

Notes

[d33]

1.33.02

Removed VTL CT363 support for now
USB OTG set to Slave only

Download

Notes

[tgray]

tgray
maybe you should redo a complete nand flash of all partitions (from RROM 3.4.2) and not only the kernel's one so that no interference from previous ROM can occur.
If this confirms that all features are working, .17b would become a big milestone in freaktab's history !

Hi Raxy,

I always do a complete nand flash of all the partitions when trying these kernels.

D33, I will try the new kernels tonight and let you know if there is any improvement.

[TriA]

I've tested the 1.33.02 kernel under 3 conditions:
- just after flashing the kernel;
- after power cycle;
- after reboot

Touch screen, brightness control, rotation sensor, Wi-Fi and HDMI are OK in all 3 cases.
BT isn't working just after flashing the kernel, but is OK after power cycle, and isn't working again after reboot.
GPS behavior is the same as BT (with screen off; it isn't working at all when screen is on).
OTG was OK (USB mouse for example) only after flashing the kernel, but isn't working (no power on OTG) after power cycle and/or reboot.

[d33]

I've tested the 1.33.02 kernel under 3 conditions:
- just after flashing the kernel;
- after power cycle;
- after reboot

Power cycle == pressing the power button to turn the screen off?

... and what about 1.33.01?