FORUMS

OnePlus Addresses Reservation List Cheating

Jake Cooper figured out how to bump his place up on OnePlus’ reservation list and … more

OnePlus 2 Benchmark Scores Show Its Muscle

This video by FoneArena contains all the popular benchmarks being tested on the OnePlus 2, … more

Sony’s Emergence in The Middle: Is The Price Right?

Sony’s Electronics Division is not in its best days, and its smartphone … more

HTC Delivering Ads Straight to Sense Home

HTC’s 2015 has been a year marked by a desperate search for revenue.The HTC One M9 … more

[ROM][Nightlies][03-02-2012]CyanogenMod 9 Nightlies Galaxy Tab 10.1 WIFI

825 posts
Thanks Meter: 2,074
 
Post Reply Subscribe to Thread Email Thread
16th May 2012, 04:26 PM |#201  
Recognized Developer
Thanks Meter: 4,195
 
More
Quote:
Originally Posted by mcgoo99

Hmm just had a long lockscreen freeze, followed by a reboot. Log attached once again.

that log wont help me (if it reboots, and there was a panic, youll see /proc/last_kmsg ; thats the log i need). i think you have another issue (which is isolated).

i want you to odin back to 3.2 (the whole tablet will be wiped), flash cwm 5.5.0.4 (from snapshot 0515 folder), boot it, wipe, flash 0515 rom, reboot (do not flash gapps). then once you get in, dont restore apps, dont oc. observe for 24 hours.

then report back.
Last edited by pershoot; 16th May 2012 at 04:29 PM.
 
 
16th May 2012, 04:30 PM |#202  
Recognized Developer
Thanks Meter: 4,195
 
More
Quote:
Originally Posted by pershoot

that log wont help me (if it reboots, and there was a panic, youll see /proc/last_kmsg ; thats the log i need). i think you have another issue (which is isolated).

i want you to odin back to 3.2 (the whole tablet will be wiped), flash cwm 5.5.0.4 (from snapshot 0515 folder), boot it, wipe, flash 0515 rom, reboot (do not flash gapps). then once you get in, dont restore apps, dont oc. observe for 24 hours.

then report back.

if it does happen, then i want you to re-odin back to 3.2, and observe for another 24 hours. this is to rule out any potential HW issue at play.

thx.
Last edited by pershoot; 16th May 2012 at 04:35 PM.
16th May 2012, 04:47 PM |#203  
Recognized Developer
Thanks Meter: 4,195
 
More
Quote:
Originally Posted by pershoot

if it does happen, then i want you to re-odin back to 3.2, and observe for another 24 hours. this is to rule out any potential HW issue at play.

thx.

the issue im speaking of here is not the once in a blue lockscreen dim issue (that could still happen and is an old issue from HC; this event could freeze up wifi). im speaking of your new issue where the lockscreen is completly locked up and the tablet bouncing itself.

to get out of the dim issue:
1. press power, it will dim, wait for screen off, press power, screen will come on and youll be able to unlock. wifi will reenable and come alive

or

2. plug in usb.
Last edited by pershoot; 16th May 2012 at 04:55 PM.
17th May 2012, 01:41 PM |#204  
mcgoo99's Avatar
Senior Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by pershoot

the issue im speaking of here is not the once in a blue lockscreen dim issue (that could still happen and is an old issue from HC; this event could freeze up wifi). im speaking of your new issue where the lockscreen is completly locked up and the tablet bouncing itself.

to get out of the dim issue:
1. press power, it will dim, wait for screen off, press power, screen will come on and youll be able to unlock. wifi will reenable and come alive

or

2. plug in usb.

OK give me a couple days. Traveling at the moment and need a functional tablet in the meantime.
17th May 2012, 02:13 PM |#205  
URPREY's Avatar
Senior Member
Flag Louisville, KY
Thanks Meter: 99
 
More
So far mine has been stable on the 0515 build - no lockscreen freezes, no SODs, no reboots.

Thank you!
17th May 2012, 05:56 PM |#206  
Senior Member
Flag Enschede
Thanks Meter: 62
 
Donate to Me
More
Hey Pershoot,

I'm trying to use an FTDI232 usb serial adapter but it is blocked by the kernel, because this symbol is set to yes: SEC USB host target list[=y]

ftdi_sio.ko is loaded

dmesg:
Code:
<6>[  244.527101] usb 1-1: new full speed USB device using tegra-ehci and address 2
<3>[  244.790705] usb 1-1: device v0403 p6001 is not supported
<6>[  244.817622] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[  244.817701] hub 1-0:1.0: unable to enumerate USB device on port 1
Could you disable that config symbol in your kernel build?
17th May 2012, 05:59 PM |#207  
Recognized Developer
Thanks Meter: 4,195
 
More
I believe xpad uses it for white listing.
17th May 2012, 06:10 PM |#208  
Senior Member
Flag Enschede
Thanks Meter: 62
 
Donate to Me
More
I believe XPAD is not dependent on SEC USB host target list(CONFIG_USB_SEC_WHITELIST) look:

Code:
Symbol: JOYSTICK_XPAD [=m]
Type  : tristate
Prompt: X-Box gamepad support
Defined at drivers/input/joystick/Kconfig:269
Depends on: !S390 && INPUT [=y] && INPUT_JOYSTICK [=y] && USB_ARCH_HAS_HCD [=y]
So you could safely disable CONFIG_USB_SEC_WHITELIST.
17th May 2012, 06:41 PM |#209  
Recognized Developer
Thanks Meter: 4,195
 
More
Pls rebuild the kernel and test. I vaguely remember a reason for this. Would have to grep git logs for it.

If no issues (with USB, xpad or otherwise), then I can make the change moving forward at some point.
17th May 2012, 06:56 PM |#210  
Senior Member
Flag Enschede
Thanks Meter: 62
 
Donate to Me
More
Ok, I will build and test using arch/arm/configs/pershoot_samsung_p4wifi_ics_defconfig without CONFIG_USB_SEC_WHITELIST

edit:

Tried building your kernel but it doesn't boot. Dont know why, just hangs at galaxy tab bootlogo, adb logcat is not connected so unfortunately no info.

Replaced your boot.img-kernel with my zImage and kept ramdisk the same. Used mkbootimg for boot.img creation. Any idea's?

Did some further reading and came across this: http://blog.teadriven.me.uk/2011/09/...oid-phone.html maybe you could add the fix to sec_whitelist.h
Last edited by peeter123; 17th May 2012 at 11:32 PM.
19th May 2012, 01:29 PM |#211  
Senior Member
Flag Enschede
Thanks Meter: 62
 
Donate to Me
More
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:

Code:
<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:

Code:
<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

Read More
Post Reply Subscribe to Thread

Tags
android 4.0, cyanogenmod, ics, rom
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes