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.

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.

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.

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.

So far mine has been stable on the 0515 build - no lockscreen freezes, no SODs, no reboots.

Thank you!

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:

<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?

I believe xpad uses it for white listing.

I believe XPAD is not dependent on SEC USB host target list(CONFIG_USB_SEC_WHITELIST) look:

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.

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.

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