Hi Pershoot,

I've got my recompiled kernel working, turns out it boots with arm-2010.09 toolchain. I was using the default Ubuntu one before. Xpad, usb and mouse works like a charm.

This is dmesg with xbox controller:

<6>[ 2496.848919] [ CONNECTOR_DRIVER (acc_ID_interrupt,461) ]
<6>[ 2496.848969] [ CONNECTOR_DRIVER (acc_ID_interrupt,464) ] IRQ_DOCK_GPIO is 0
<6>[ 2497.273144] [ CONNECTOR_DRIVER (acc_ID_interrupt,480) ] Accessory attached
<4>[ 2497.314936] stmpe811_adc_get_value: ADC_DATA_CH(7) = 0xaa5, 2725.
<4>[ 2497.383738] stmpe811_adc_get_value: ADC_DATA_CH(7) = 0xaa5, 2725.
<4>[ 2497.454426] stmpe811_adc_get_value: ADC_DATA_CH(7) = 0xaa5, 2725.
<4>[ 2497.524716] stmpe811_adc_get_value: ADC_DATA_CH(7) = 0xaa6, 2726.
<4>[ 2497.594438] stmpe811_adc_get_value: ADC_DATA_CH(7) = 0xaa5, 2725.
<6>[ 2497.623138] [ CONNECTOR_DRIVER (connector_detect_change,112) ] ACCESSORY_ID : ADC value = 2725
<6>[ 2497.623170]
<6>[ 2497.623216] Board P4 : tegra_acc_power token : (0,0) off
<6>[ 2497.623284] Board P4 : tegra_usb_ldo_en=1 instance=0 present regulator=0
<6>[ 2497.653127] Board P4 : tegra_otg_en = 1
<6>[ 2497.663267] tegra-otg tegra-otg: SUSPEND --> HOST
<6>[ 2497.663315] tegra-otg tegra-otg: tegra_start_host+
<4>[ 2497.665628] tegra_usb_phy_open() called instance :0
<6>[ 2497.665755] Board P4 : tegra_usb_ldo_en=1 instance=0 present regulator=1
<4>[ 2497.665807] utmi_phy_power_on() called. instance : 0
<6>[ 2497.666517] tegra-otg tegra-otg: Acc power on detect
<6>[ 2497.693453] [ CONNECTOR_DRIVER (acc_notified,427) ] ACCESSORY=OTG : STATE=online
<6>[ 2497.693820] Board P4 : tegra_acc_power token : (1,1) on
<4>[ 2497.693864] utmi_phy_clk_enable() called. instance : 0
<6>[ 2497.694506] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[ 2497.694867] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 1
<6>[ 2497.723459] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[ 2497.743226] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 2497.743492] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 2497.743545] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 2497.743589] usb usb1: Product: Tegra EHCI Host Controller
<6>[ 2497.743627] usb usb1: Manufacturer: Linux 2.6.36.4-cyanogenmod+ ehci_hcd
<6>[ 2497.743666] usb usb1: SerialNumber: tegra-ehci.0
<6>[ 2497.749003] hub 1-0:1.0: USB hub found
<6>[ 2497.749097] hub 1-0:1.0: 1 port detected
<6>[ 2497.751798] tegra-otg tegra-otg: tegra_start_host-
<6>[ 2497.751847] host_notify: ndev name=usb_otg: from state=2 -> to state=1
<6>[ 2497.963171] usb 1-1: new full speed USB device using tegra-ehci and address 2
<6>[ 2498.518348] usb 1-1: New USB device found, idVendor=045e, idProduct=028e
<6>[ 2498.518405] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 2498.518450] usb 1-1: Product: Controller
<6>[ 2498.518482] usb 1-1: Manufacturer: -®Microsoft Corporation
<6>[ 2498.518518] usb 1-1: SerialNumber: 054C852
<7>[ 2498.526974] Registered led device: xpad1
<6>[ 2498.529628] input: Microsoft X-Box 360 pad as /devices/platform/tegra-ehci.0/usb1/1-1/1-1:1.0/input/input10

Played some racing games and have not encountered any problems.

And my usb<->Serial converter:

<6>[ 3081.123355] USB Serial support registered for pl2303
<6>[ 3081.123811] usbcore: registered new interface driver pl2303
<6>[ 3081.123821] pl2303: Prolific PL2303 USB to serial adaptor driver
<6>[ 3086.960489] [ CONNECTOR_DRIVER (acc_ID_interrupt,461) ]
<6>[ 3086.960539] [ CONNECTOR_DRIVER (acc_ID_interrupt,464) ] IRQ_DOCK_GPIO is 0
<6>[ 3087.385717] [ CONNECTOR_DRIVER (acc_ID_interrupt,480) ] Accessory attached
<4>[ 3087.424599] stmpe811_adc_get_value: ADC_DATA_CH(7) = 0xaa6, 2726.
<4>[ 3087.494557] stmpe811_adc_get_value: ADC_DATA_CH(7) = 0xaa6, 2726.
<4>[ 3087.564745] stmpe811_adc_get_value: ADC_DATA_CH(7) = 0xaa6, 2726.
<4>[ 3087.634387] stmpe811_adc_get_value: ADC_DATA_CH(7) = 0xaa6, 2726.
<4>[ 3087.704371] stmpe811_adc_get_value: ADC_DATA_CH(7) = 0xaa7, 2727.
<6>[ 3087.733118] [ CONNECTOR_DRIVER (connector_detect_change,112) ] ACCESSORY_ID : ADC value = 2726
<6>[ 3087.733150]
<6>[ 3087.733195] Board P4 : tegra_acc_power token : (0,0) off
<6>[ 3087.733262] Board P4 : tegra_usb_ldo_en=1 instance=0 present regulator=0
<6>[ 3087.763207] Board P4 : tegra_otg_en = 1
<6>[ 3087.773433] tegra-otg tegra-otg: SUSPEND --> HOST
<6>[ 3087.773481] tegra-otg tegra-otg: tegra_start_host+
<4>[ 3087.774730] tegra_usb_phy_open() called instance :0
<6>[ 3087.774857] Board P4 : tegra_usb_ldo_en=1 instance=0 present regulator=1
<4>[ 3087.774910] utmi_phy_power_on() called. instance : 0
<6>[ 3087.775812] tegra-otg tegra-otg: Acc power on detect
<6>[ 3087.793258] Board P4 : tegra_acc_power token : (1,1) on
<4>[ 3087.793350] utmi_phy_clk_enable() called. instance : 0
<6>[ 3087.794376] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[ 3087.794760] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 1
<6>[ 3087.803520] [ CONNECTOR_DRIVER (acc_notified,427) ] ACCESSORY=OTG : STATE=online
<6>[ 3087.828814] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[ 3087.845093] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 3087.845175] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 3087.845186] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 3087.845196] usb usb1: Product: Tegra EHCI Host Controller
<6>[ 3087.845205] usb usb1: Manufacturer: Linux 2.6.36.4-cyanogenmod+ ehci_hcd
<6>[ 3087.845213] usb usb1: SerialNumber: tegra-ehci.0
<6>[ 3087.846693] hub 1-0:1.0: USB hub found
<6>[ 3087.846722] hub 1-0:1.0: 1 port detected
<6>[ 3087.847349] tegra-otg tegra-otg: tegra_start_host-
<6>[ 3087.847360] host_notify: ndev name=usb_otg: from state=2 -> to state=1
<6>[ 3088.063307] usb 1-1: new full speed USB device using tegra-ehci and address 2
<6>[ 3088.206539] usb 1-1: New USB device found, idVendor=067b, idProduct=2303
<6>[ 3088.206595] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
<6>[ 3088.212789] pl2303 1-1:1.0: pl2303 converter detected
<6>[ 3088.616970] usb 1-1: pl2303 converter now attached to ttyUSB0

Does the controller itself work (buttons/pad, etc.)?

Xbox led is lit and buttons work without a problem. There is a /dev/input/js0 entry and I can play games with the controller

builds via get.cm

http://droidbasement.com/db-blog/?p=2557

Originally Posted by peeter123

Xbox led is lit and buttons work without a problem. There is a /dev/input/js0 entry and I can play games with the controller

can you please post a patch or list the changes you want done?

thanks.

Hey guys,
I'm guessing that the Theme Chooser Engine isn't working yet on our Tablets running cm9, am I correct?

Sent from my SPH-D710 using xda premium

Pershoot: only thing I've changed is:

Drivers->Usb->CONFIG_USB_SEC_WHITELIST = n

I'm not sure which of these threads is appropriate to post, so I apologize in advanced if I'm in the wrong arena here...

On Thursday evening I completely Odin'd back to 3.2, and did a full wipe (inc. my "SD card" which I made a backup of prior to all of this). Booted 3.2 with no setup, then boot into bootloader and proceeded to flash the latest CWM (5.5.0.4) with Odin. Booted to CWM recovery, did a full wipe (data, cache, dalvik) and installed the 5/15 build and latest GAPPS.

Ran through setup and allowed Google Market to re-install all of my apps, but did not restore any data using Titanium.

Tab ran great all weekend, Friday through Sunday, however I woke up this morning (Monday) and on first attempt to access my tab got a "locked" lock screen. Orientation would change from portrait to landscape, but lock icon would not move and screen would not unlock. Then a few seconds later before I could do anything, I got the "Boot Screen Animation SOD", after which I simply did a hard reboot (held down power button), and then shut the tablet down before coming to work for the day.

Unfortunately was not able to collect any logs, and I was really hoping that the 3 full days my tablet had been running smoothly was a good sign...but I guess not. I know this is of little help to the devs with no log, but wanted to report the incident anyway.

Anyone else experiencing this...
Regardless of which ICS I use on my Galaxy Tab 10.1 WiFi..CM9 nightlies or Kang, it will either lock, reboot or power off at least once a day. I often wake to the spinning CM9 boot logo, not know how long it has been doing that.
If I go back to Honeycomb, the problem is gone.

Originally Posted by Barsky

Anyone else experiencing this...
Regardless of which ICS I use on my Galaxy Tab 10.1 WiFi..CM9 nightlies or Kang, it will either lock, reboot or power off at least once a day. I often wake to the spinning CM9 boot logo, not know how long it has been doing that.
If I go back to Honeycomb, the problem is gone.

If you see my post directly above yours, you will see that yes, others are having the same issue. It's been widely reported in the threads.