[Q] GTP31xx charging issues

Search This thread

Darkergothic

Member
Jan 1, 2011
39
10
Gothenburg
(Samsung GT-P3110 Galaxy Tab 2 7.0")

Recently the tab stopped charging while plugged to AC and in use...
Ok, it's not losing power as fast as when unplugged, but almost!
I have to turn it off and AC charge for hours and hours as the phone seem to think that it's connected to a PC all of a sudden!
Wasn't an issue up until last week then for no apparent reason it says "not charging" in Battery..

After a lot of reading around and confirming that it was not the charger or cable i dug deeper and it seems that USB charging is turned of by default on the Tab 2's except all custom kernels have it turned on and now that's always on!
Since the tab wont change charger state from USB to AC then all I'm getting is a slow trickle charge at the same slow pace, and it don't whether I am plugged in to the AC or into the PC!

So i figured hey, it's just a terminal command to force it to switch and that's when i realized that, no it's not that easy!
As USB charge is not only the default setting in custom kernels, its the ONLY option available!

The ability to have the tab swiftly reach a full charge while in use seems to currently be impossible with custom kernels it seems!
Is there a work around, or have everyone been to busy implementing USB charging to remember that sometimes you don't want to spend 8+ hours with tab turned off to get a full charge?

Below is a logcat from connecting and disconnecting charger cable to my GTP3110 WHILE connected to an AC adapter!
Code:
Android Tuner (logcat)
======================
V/   96.627105  c1     17 usb ta_nconnected_irq : VBUS ON
V/   96.627899  c1     17 [BAT_MANAGER] Charger Connected
V/   96.627960  c1     58 musb-hdrc musb-hdrc: USB/TA Connect
V/   97.256317  c1   1662 check_charger_type : Charger type is [USB], adc=594
V/   97.256317  c1   1662 charger_detect_work: cable flag : 1, cable_type : 1
V/   97.256347  c1   1662 smb136-charger 5-004d: smb136_set_charging_state: set charger current USB & Default
V/   97.262725  c1   1662 cable detect:USB attach, current device = 0x0080
V/   97.262756  c1   1662 espresso_con_usb_charger_attached, USB_EVENT_VBUS
V/   97.262756  c1   1662 otg: otgwl_hold
V/   97.262847  c0     58 musb-hdrc musb-hdrc: VBUS Connect
V/   97.262908  c0     58 musb-omap2430 musb-omap2430: runtime resume
V/   97.263061  c0     58 omap4430_phy_set_clk: clock (0 --> 1)
V/   97.504699  c0     58 omap4430_phy_power : clock 1, power ON
W/  103.476745  c0     15 smb136-charger 5-004d: smb136_i2c_read: err -6
W/  103.476806  c0     15 smb136-charger 5-004d: smb136_read_status : I2C read fail addr: 0x35
V/  103.535827  c0     15 smb136-charger 5-004d: addr : 0x35, data : 0x40, addr : 0x36, data : 0x31
V/  103.806243  c1     17 usb ta_nconnected_irq : VBUS OFF
V/  103.806793  c1     17 otg: otgwl_temporary_hold
V/  103.806793  c0     78 musb-hdrc musb-hdrc: VBUS Disconnect
V/  103.806793  c1     17 [BAT_MANAGER] Charger Disconnect
V/  103.806823  c0     78 omap4430_phy is : ON
V/  103.806854  c0     78 omap4430_phy_power : clock 1, power OFF
V/  103.806854  c1   1662 charger_detect_work: cable flag : 0, cable_type : 0
V/  103.806854  c1   1662 smb136-charger 5-004d: smb136_set_charging_state: Set discharging default
V/  103.806884  c0     78 musb-hdrc musb-hdrc: ID float
V/  103.806884  c0    605 android_work: did not send uevent (0 0   (null))
V/  103.806915  c0    605 otg espresso_otg_work(920)
current device 0080
V/  103.806915  c0    605 otg current device is not USB Host.
V/  103.812805  c1   1662 cable detect:USB detach, current device = 0x0000
V/  104.002899  c0    658 musb-omap2430 musb-omap2430: runtime suspend
V/  104.002899  c0    658 omap4430_phy_set_clk: clock (1 --> 0)
 
Last edited:

MultipleMonomials

Senior Member
May 25, 2012
724
244
San Diego
I use cyanogenmod, and I'm fairly sure that my tablet charges faster on ac than when plugged into my PC. Have you tried a different kernel/rom?

Sent from my Galaxy S4
 

Darkergothic

Member
Jan 1, 2011
39
10
Gothenburg
What kernel are you on, been trying with 5-6 different ones and they all display that bug that they are incapable in detecting if you are really on AC or USB...
It IS a kernel issue I am 100% sure of that since the Tab has USB charging turned off by default exactly to avoid this issue...