Thread Deleted

[Q] Kernel USB detection fixing?

OP Darkergothic

Prev Previous Post   Next Post Next
18th April 2014, 07:08 AM   |  #1  
Darkergothic's Avatar
OP Junior Member
Flag Gothenburg
Thanks Meter: 7
29 posts
Join Date:Joined: Jan 2011
The other day my GT-P3110 stopped recharging while in use and after digging around most people seem to think its the charger.
But no, it is NOT!
It's the kernel, and all custom kernels has this apparent problem by default!
Might even be inherited from Samsung Stock kernels!

I really need help sorting this out because I don't have time to dedicate 8-9 hours a day to charge my tab!
Neither do I have much time to sort this out on my own so I am asking for help here!

This log is for when I am connecting my cable:
Android Tuner (logcat)
V/  156.536193  c1     17 usb ta_nconnected_irq : VBUS ON
V/  156.536926  c1     17 [BAT_MANAGER] Charger Connected
V/  156.536926  c0     78 musb-hdrc musb-hdrc: USB/TA Connect
V/  157.161834  c1   1662 check_charger_type : Charger type is [USB], adc=611
V/  157.161865  c1   1662 charger_detect_work: cable flag : 1, cable_type : 1
V/  157.161865  c1   1662 smb136-charger 5-004d: smb136_set_charging_state: set charger current USB & Default
V/  157.167907  c1   1662 cable detect:USB attach, current device = 0x0080
V/  157.167907  c1   1662 espresso_con_usb_charger_attached, USB_EVENT_VBUS
V/  157.167938  c1   1662 otg: otgwl_hold
V/  157.167938  c0     78 musb-hdrc musb-hdrc: VBUS Connect
V/  157.167999  c0     78 musb-omap2430 musb-omap2430: runtime resume
V/  157.168029  c0     78 omap4430_phy_set_clk: clock (0 --> 1)
V/  157.385894  c0     78 omap4430_phy_power : clock 1, power ON
And as you can see it set's the charger to:
V/ 157.161834 c1 1662 check_charger_type : Charger type is [USB], adc=611

And that don't matter if it's connected to AC or my PC, same result!
Hence it trickle charges from both sources, which is a PAIN!
And I'm willing to bet that it's doing the exact same detection cock-up when turned off, hence the MASSIVE recharge times!

For reference I will add the log for disconnecting the charger, and again its identical whether the source is in fact an USB or if its the AC adapter!
Android Tuner (logcat)
W/  191.032257  c0     15 smb136-charger 5-004d: smb136_i2c_read: err -6
W/  191.032318  c0     15 smb136-charger 5-004d: smb136_read_status : I2C read fail addr: 0x35
V/  191.090332  c0     15 smb136-charger 5-004d: addr : 0x35, data : 0x40, addr : 0x36, data : 0x31
V/  191.353881  c1     17 usb ta_nconnected_irq : VBUS OFF
V/  191.354400  c1     17 otg: otgwl_temporary_hold
V/  191.354431  c1     17 [BAT_MANAGER] Charger Disconnect
V/  191.354431  c0   2738 musb-hdrc musb-hdrc: VBUS Disconnect
V/  191.354461  c0   2738 omap4430_phy is : ON
V/  191.354461  c0   2738 omap4430_phy_power : clock 1, power OFF
V/  191.354461  c1   1662 charger_detect_work: cable flag : 0, cable_type : 0
V/  191.354492  c1   1662 smb136-charger 5-004d: smb136_set_charging_state: Set discharging default
V/  191.354492  c0   2738 musb-hdrc musb-hdrc: ID float
V/  191.354522  c0    658 android_work: did not send uevent (0 0   (null))
V/  191.354522  c0    658 otg espresso_otg_work(920)
current device 0080
V/  191.354522  c0    658 otg current device is not USB Host.
V/  191.360412  c1   1662 cable detect:USB detach, current device = 0x0000
V/  191.557556  c0    658 musb-omap2430 musb-omap2430: runtime suspend
V/  191.557586  c0    658 omap4430_phy_set_clk: clock (1 --> 0)
Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes