Database Info

Quicker charging with asus ai charger?

So asus has this little utility that changes the usb settings and sends upto 1.2A to your iphone/ipad though a regular usb slot(works on non-asus mobo's too), problem is it doesn't work on any other device except apples.
Does anyone have an idea what exactly this utility changes in the usb settings?
http://event.asus.com/mb/2010/ai_charger/

Me too using this ai charger to charge my iPod touch. If it work with android too this will be cool.

I think its implemented in the hardware.

As far as I know apple dock connector have 30pin. Will asus ai charger use the pins for firewire to provide additional power?

It says.enabled when I use with my phone?
Sent from my GT-I9100 using Tapatalk

It uses the standard USB port so I'm hoping there is hack that will let me boost the amps to 1.0 amp in order to charge my HTC Amaze phone. I use the utility today with my iPad and it works great.

I have an ASRock motherboard and they rebranded this feature as "App charger".
This enables windows to send over 1A through the USB port and I also would like to find a trick to enable it for non apple devices.
The only way I know to charge the non apple devices faster is using a double headed USB cable that comes with some external hard drives boxes. We get 1Ah as it is getting power from two ports.
http://www.amazon.co.uk/StarTech-com-Cable-External-Hard-Drive/dp/B003HHK58U
Regarding the use of this feature on other motherboards, I'm not sure if it is healthy since forcing extra power to USB ports might damage something. My vintage PII laptop sometimes complained about power surges on USB bus when I connected high powered USB devices so probably wont be happy with this.

I have the AI Charger installed.
When I connect my Xperia Arc to the computer, the phone sets the current to 1050mA at first but immediately changes to 500mA.
D/kernel ( 130): [102752.317169] msm_hsusb msm_hsusb: reset
D/kernel ( 130): [102752.317352] diag_function_disable
V/kernel ( 130): [102752.317352] diag: USB disconnected
D/kernel ( 130): [102752.317901] adb_release
D/kernel ( 130): [102752.321411] adb_open
D/kernel ( 130): [102752.329925] bq24185 0-006b: Disabling charger
D/kernel ( 130): [102752.344360] msm_hsusb msm_hsusb: msm72k_udc: ONLINE -> OFFLINE
D/kernel ( 130): [102752.355224] bq24185 0-006b: Turning off charger
D/kernel ( 130): [102752.574523] msm_otg_suspend: usb in low power mode
D/kernel ( 130): [102761.481933] msm_otg_resume: usb exited from low power mode
D/kernel ( 130): [102761.504638] msm_hsusb msm_hsusb: msm72k_udc: OFFLINE -> ONLINE
D/kernel ( 130): [102761.737518] msm_hsusb msm_hsusb: suspend
D/kernel ( 130): [102761.843658] msm_hsusb msm_hsusb: reset
D/kernel ( 130): [102761.845947]
D/kernel ( 130): [102761.845977] *********** Charger Type: HOST PC
D/kernel ( 130): [102761.845977]
D/kernel ( 130): [102762.003723] msm_hsusb msm_hsusb: reset
D/kernel ( 130): [102762.003753]
D/kernel ( 130): [102762.003753] Charger Type: STD DOWNSTREAM PORT
D/kernel ( 130): [102762.008270] bq24185 0-006b: Turning on charger. USB-Host mode
D/kernel ( 130): [102762.008300] bq24185 0-006b: Set init values
D/kernel ( 130): [102762.009704] bq24185 0-006b: Disabling charger
D/kernel ( 130): [102762.012603] bq24185 0-006b: Setting charger voltage to 4200 mV
D/kernel ( 130): [102762.013427] bq24185 0-006b: Setting charger current to 1050 mA
D/kernel ( 130): [102762.013854] bq24185 0-006b: Enabling charger
D/kernel ( 130): [102762.202941] android_usb gadget: high speed config #1: android
D/Vold ( 117): USB connected
D/Vold ( 117): Share method ums now available
I/StorageNotification( 334): UMS connection changed to true (media state mounted)
D/kernel ( 130): [102762.212371] bq24185 0-006b: Setting input charger current to 500 mA

is there a way to use AI Charger on Asus motherboards but on Galaxy Nexus?

Any updates on this?
Would be really nice to be able to charge my Xperia S faster

this is a fast charge mod for the cable to charge your smartphones/tablets with microusb much faster
http://forum.xda-developers.com/showthread.php?p=22829766

MSI have one called "SuperCharger" which is for iPhones and iDevices, works perfectly fine with ALL my other devices though since all it does it switch the USB power form 3v to 5v.

I'm using Asus Ai charger on my kindle fire , rooted and running rom "gedeROM-KFire-CM9-26-6-2012"
but the icon on the taskbar still has a red x on it but it is charging faster, make sure you inable it in bios and install ai charger drivers and use one of the two usb 3.0 ports on ur mobo. Charging pretty fast for me

Is it working with Galaxy Tabs?

compfast said:
I'm using Asus Ai charger on my kindle fire , rooted and running rom "gedeROM-KFire-CM9-26-6-2012"
but the icon on the taskbar still has a red x on it but it is charging faster, make sure you inable it in bios and install ai charger drivers and use one of the two usb 3.0 ports on ur mobo. Charging pretty fast for me
Click to expand...
Click to collapse
ai charger works only with apple devices so it charges but it charges at half speed of what your device can charge.

I have the Asus Crosshair Formula V motherboard and AI Charger+ does work with my Galaxy S3. I downloaded a charge current monitoring app for my S3 and (using the USB3 port) it detects 0.466A with AI Charger+ disabled and 1.2A with AI Charger+ enabled.

bartekxx12 said:
I have the Asus Crosshair Formula V motherboard and AI Charger+ does work with my Galaxy S3. I downloaded a charge current monitoring app for my S3 and (using the USB3 port) it detects 0.466A with AI Charger+ disabled and 1.2A with AI Charger+ enabled.
Click to expand...
Click to collapse
Get Asus USB Charger+ instead. Supports all devices. My P8Z77-V Pro motherboard delivers a 1790mA current to my Note 2.

AI charge work for me on Asus sabertooth 990fx rev1.0 and SGS-i9500 (usb 3 only support 1000mA power)
Logcat says: current avg:1000
And samsung realy charges fast!!!

yes!!!!!!!!!!!!
i found way to charge android device with 1.2A
---------- Post added at 03:21 AM ---------- Previous post was at 03:16 AM ----------
use power bank cable and connect to
*usb3 port upto 1200mA outpot
*usb2 port up to1000mA outpot
saeid from iran

Here are a few more details about the MSI Super Charger just to give you an idea about some of it's specs and overall speed.
http://vkrepair.com/msi-super-charger/

[Q] Official ICS - support for USB OTG?

Hi there,
I know that some of you were able to connect peripheral devices to their phones.
Has anyone of you tested this with the ICS stock kernel? When looking at /proc/config.gz it seems to me that all things neccessary for USB OTG are contained in the kernel.
Did you always use a special "OTG cable" or were you able to force the controller into host mode?
I'm playing with several USB hubs at the moment but I'm stuck.
Have a nice day,
Markus

You need Y-cable for getting the VBUS to both phone and hub.

Well, I removed a diode from my hub and put a label on it saying "do not connect to computer" .
Now, as soon as I connect my phone to the hub's upstream port, it starts charging. But still dmesg doesn't say anything about a switch to host mode .

Check ID pin value on the cable you're using. You're most likely using the standard A-to-microB cable, meant for device. You need A-to-microA, or just hack your cable and tie ID pin low in the microB plug, turning it into microA.

Now I made sure I'm using the right cable, but still it doesn't work.
This has to do with the stock kernel. If you look at "arch/arm/mach-msm/board-saga.c", line 3168, it says "USB_PERIPHERAL". If you change this to "USB_OTG" and compile it using the default config file, the kernel still won't recognize a OTG cable. But you can mount debugfs: "mount -t debugfs none /sys/kernel/debug" and look at "/sys/kernel/debug/msm_otg/mode". This file contains "none", if no cable is plugged in, or "peripheral" else. If you try to overwrite it with "echo host > mode", something happens according to dmesg:
[USB] msm_otg_mode_write: host
[USBH] msm_otg_sm_work: state:b_peripheral bit:0x00000002
[USB] OTG_STATE_B_PERIPHERAL state
[USBH] gadget off
[USB] OTG runtime idle
[USB] OTG runtime suspend
[USBH] msm_otg_suspend
[USBH] USB in low power mode
[USBH] msm_otg_sm_work: state:b_idle bit:0x00000002
[USB] OTG runtime resume
[USBH] msm_otg_resume
[USBH] USB exited from low power mode
[USB] OTG_STATE_B_IDLE state
[USBH] b_sess_vld
[USBH] gadget on
[USB] CI13XXX_CONTROLLER_RESET_EVENT received
[USBH] send connect type 0
[TP]cable change to 0
[TP]ts->status change to 0
[USB] suspend
[CABLE] usb_status_notifier_func: cable_type = 0
[CABLE] send_cable_connect_notify: cable_type = 0
Click to expand...
Click to collapse
It seems like something is immediately switching back to "peripheral", probably it's got to do with the "carkit driver":
[CABLE] phy_id_detect: usb ID pin = 0
config_saga_usb_id_gpios 145 output high
[USBH] carkit_phy_reset
[USBH] phy_reset: success
[USBH] ulpi: write 0x06 to 0x36
[USBH] ulpi: write 0x0c to 0x31
[USBH] ulpi: write 0x31 to 0x32
[USBH] ulpi: write 0x01 to 0x0d
[USBH] ulpi: write 0x01 to 0x10
[USBH] =============htc_get_accessory_state otgsc = 0x202e20
config_saga_usb_id_gpios 145 input none pull
[CABLE] phy_id_detect: type = 1
[CABLE] cradle inserted
[CABLE] cable_detect_handler ID pin 0, type 1
Click to expand...
Click to collapse
The file "drivers/usb/otg/msm_otg.c" has been adjusted by HTC and I'm afraid you'd have to revert these changes to make host mode work. Unfortunately, I don't think I have enough knowledge about this to do it myself. But probably this is interesting to some of you who are working on custom ICS kernels .

Hello,
Did you manage to make it work with ICS?
Thank you.

Well, no. And currently I've got neither the time nor the knowledge to I'm afraid. But it was possible in Android 2.3.5 by using a kernel hack. As far as I know amidabuddha is playing around with this, too, but wasn't successful yet as we were not able to get the source code of the modified kernel.

Finally, I did it! :victory: ... At least partially.
Code:
<6>[ 1117.578247] [USB] msm_otg_mode_write: host
<6>[ 1117.578735] [USBH] msm_otg_sm_work: state:b_peripheral bit:0x00000002
<6>[ 1117.579437] [USB] OTG_STATE_B_PERIPHERAL state
<6>[ 1117.579833] [USBH] send connect type 0
<6>[ 1117.580169] [TP]cable change to 0
<6>[ 1117.582244] [TP]ts->status change to 0
<7>[ 1117.582702] [USBH] gadget off
<6>[ 1117.583679] [USBH] msm_otg_sm_work: state:b_idle bit:0x00000002
<6>[ 1117.584350] [USB] OTG_STATE_B_IDLE state
<6>[ 1117.584716] [USBH] !id || id_a
<7>[ 1117.585083] [USBH] host on
<6>[ 1117.585754] msm_hsusb_host msm_hsusb_host.0: Qualcomm On-Chip EHCI Host Controller
<6>[ 1117.586242] msm_hsusb_host msm_hsusb_host.0: new USB bus registered, assigned bus number 1
<6>[ 1117.591003] [CABLE] usb_status_notifier_func: cable_type = 0
<7>[ 1117.591400] [CABLE] send_cable_connect_notify: cable_type = 0
<6>[ 1117.592071] [BATT] peripheral_cable_update(0) from_owe=0
<6>[ 1117.592468] [BATT] Update SMEM: cable type 0 at 1111762850068 (2013-01-13 14:46:15.556571647 UTC)
<6>[ 1117.606140] [BATT] ID=2, level=86, vol=4063, temp=256, batt_current=84, chg_src=0, chg_en=1, full_bat=1600000, over_vchg=0, smem_vbus=1 at 1111776216768 (2013-01-13 14:46:15.570213004 UTC)
<6>[ 1117.611083] msm_hsusb_host msm_hsusb_host.0: irq 60, io mem 0xa3600000
<6>[ 1117.630737] msm_hsusb_host msm_hsusb_host.0: USB 2.0 started, EHCI 1.00
<6>[ 1117.632110] hub 1-0:1.0: USB hub found
<6>[ 1117.632324] hub 1-0:1.0: 1 port detected
<6>[ 1117.950714] usb 1-1: new high speed USB device number 2 using msm_hsusb_host
<6>[ 1118.120849] hub 1-1:1.0: USB hub found
<6>[ 1118.121124] hub 1-1:1.0: 4 ports detected
<6>[ 1136.541107] usb 1-1.2: new low speed USB device number 3 using msm_hsusb_host
<6>[ 1136.701995] input: BTC USB Multimedia Keyboard as /devices/platform/msm_hsusb_host.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input7
<6>[ 1136.705749] using input dev BTC USB Multimedia Keyboard for key reset
<6>[ 1136.706481] keychord: using input dev BTC USB Multimedia Keyboard for fevent
<6>[ 1136.707763] generic-usb 0003:046E:52CF.0001: input: USB HID v1.10 Keyboard [BTC USB Multimedia Keyboard] on usb-msm_hsusb_host.0-1.2/input0
<6>[ 1136.817230] input: BTC USB Multimedia Keyboard as /devices/platform/msm_hsusb_host.0/usb1/1-1/1-1.2/1-1.2:1.1/input/input8
<6>[ 1136.825622] using input dev BTC USB Multimedia Keyboard for key reset
<6>[ 1136.825836] keychord: using input dev BTC USB Multimedia Keyboard for fevent
<6>[ 1136.835693] generic-usb 0003:046E:52CF.0002: input: USB HID v1.10 Device [BTC USB Multimedia Keyboard] on usb-msm_hsusb_host.0-1.2/input1
<6>[ 1161.881195] usb 1-1.3: new low speed USB device number 4 using msm_hsusb_host
<6>[ 1162.014099] input: Logitech USB-PS/2 Optical Mouse as /devices/platform/msm_hsusb_host.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input9
<6>[ 1162.020507] generic-usb 0003:046D:C01E.0003: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-msm_hsusb_host.0-1.3/input0
At the moment, you have to switch between peripheral mode and host mode manually, as I explained in my post above. When switching to host mode, the phone stops charging, so this isn't really OTG now.
Patching is much easier than we thought, as all necessary code already exists in the stock source code. HTC just seems to have "forgotten" one line...
I'll append a patch for HTC's ICS stock source code and the .config file I used.

Using the patch and the kernel config I appended OTG mode finally works as it should. The phone switches between peripheral mode and host mode automatically depending on the cable's ID pin and starts charging even when in host mode. It is possible now to connect usb hid devices as well as usb sticks, card readers and so on, I even tried remote triggering a Canon DSLR using "Remote Release".
The appended kernel config file is based on saga_defconfig, the only changes I made are those necessary for OTG. It should still be possible to connect the phone to a car kit or a desktop dock, although I can't test that.

Wow. I worked on this thing for three days and got it working a couple hours ago. And now I find out that you made the the same thing. I patched exactly the same lines. What a coincidence

So your phone starts charging in host mode, too? A few seconds after you plugged in the otg cable?
There's still something wrong I'm afraid:
Code:
<6>[ 1061.087646] [USBH] !id
<6>[ 1061.087738] [USBH] Avail curr from USB = 0
<6>[ 1061.284545] [BATT][tps65200] Set VDPM back to original V: regh 0x03=83
<7>[ 1063.090393] [K] __msm_rpc_read: prog = 0x30100000, procedure = 1, type = 0, xid = 18
<6>[ 1063.090698] [BATT] M2A_RPC: set_charging: 0 at 1057797432594 (2013-01-18 22:12:40.474011248 UTC)
<6>[ 1063.091400] [BATT][tps65200] Switch charger OFF
Although the LED lights up the charger is switched off. You can see that either in the kernel log or in Settings -> Power. There it says "discharging" for me.
There is not even ACA support for the "CI_45NM_INTEGRATED_PHY" as I expected in the first place, so I think we must find a way to force it into ac charging mode when the id pin is grounded. "drivers/usb/otg/msm_otg.c" should be the right place to start...

Hi guys.
I have pulled the request by astro757 and combined it with some more entries from the defconfig by engelmarkus that *could* eventually make the storage host operational. See here. There are some differences in your patches.
Has anyone of you tried that? I do not have a cable to test it and before release I would like to be sure that it is working. Credits will be given to you both of course.
Btw engelmarkus, I see you defconfig is from CM. Am I right?

amidabuddha said:
Has anyone of you tried that?
Click to expand...
Click to collapse
Well, I downloaded your repository and compiled it. HID devices do not work:
...
<3>[ 479.265350] generic-usb 0003:046E:52CF.0002: can't reset device, msm_hsusb_host.0-1.3/input1, status -71
<3>[ 479.272186] generic-usb 0003:046E:52CF.0001: can't reset device, msm_hsusb_host.0-1.3/input0, status -71
...
Click to expand...
Click to collapse
This sounds almost like https://bugzilla.novell.com/show_bug.cgi?id=734754 .
EDIT:
HID devices do work, but you have to plug them in before you power the hub. HID devices plugged in afterwards are not recognized at all. I think there was some change in the patches between 3.0.16 and 3.0.59 that is responsible for this weird behaviour.
amidabuddha said:
Btw engelmarkus, I see you defconfig is from CM. Am I right?
Click to expand...
Click to collapse
I got my saga_defconfig from "saga-ics-crc-3.0.16-62a67df" and made a few changes. I never looked into the CM sources.

Hey, I was wondering what you changed in msm_otg.c. I'm trying to do similar with a Nexus 4 right now, and have modified msm_otg.c for crude support with /sys/kernel/debug/msm_otg/mode (thanks CaptainMuon), but on unplug of the otg cable, mode gets locked to "none" until the device is rebooted. There's also no auto-switching between host and peripheral when an otg cable/device is inserted (externally powered y-cable).
Thanks for any help

Hi,
ziddey said:
Hey, I was wondering what you changed in msm_otg.c.
Click to expand...
Click to collapse
We didn't change this file at all.
Here you can see all the changes that were necessary: https://github.com/amidabuddha/saga-ics-crc-3.0.16/commit/8f04057be6eda67b40eb1bf3354294138f9c2d24
Markus

Problem with charging my phone

My phone doesnt charge when connected to a wall charger, but will charge when connected to anything else through USB. I have tried several different wall adapters and USB cables. Im currently charging my phone via my computer or Xbox 360. Can someone please help me solve this problem.

Did you try another wall charger?
Sent from my SGH-T959V using xda app-developers app

Yes I tried several

Which ROM and kernel? Will your wall charger successfully charge other devices?
Posted from my SGS4G, thanks to Team Acid development

Yes it does charge other devices

It would help to have some kernel messages when you are plugging and unplugging a "good" charger, as well as the one that fails. When you ahve a chance, would you:
Plug your phone into a known good charger
Wait half a minute
Unplug your phone from the charger
Run in a terminal window (*not* adb over USB) # dmesg > /sdcard/good-charger.dmesg
Plug your phone into the bad wall charger
Wait half a minute
Unplug your phone from the charger
Run in a terminal window # dmesg > /sdcard/bad-charger.dmesg
There shouldn't be any personal information in those files, but I'd check them first to make sure.
Once you have those two files, if you would upload them to pastebin or the like, then post the URLs here.
If you don't already have a terminal emulator, I like https://play.google.com/store/apps/details?id=jackpal.androidterm

Good charger - http://pastebin.com/wnJ6b7j3

Bad charger - http://pastebin.com/x7RiKEeX

What I am looking for:
The first battery-status line at boot. Everything up to here is "normal" booting, where you system is trying to figure out what kind of hardware you have, how to "hook it up" and starting up the basic things. This line gets emitted when the charger circuit gets connected to the kernel and starts running. The magic incantation is from drivers/power/s5pc110_battery.c
<4>[ 122.453341] [BAT] CHR(1) CAS(1) CHS(1) DCR(0) ACP(2) BAT(99,0,0) TE(36) HE(1) VO(4168) ED(40) RC(0) CC(869) VF(603) LO(0)
* CHR -- Charger state
* CAS -- Cable status; CABLE_TYPE_NONE - 0, CABLE_TYPE_USB - 1, CABLE_TYPE_AC - 2
* CHS -- Charging status
* DCR -- Discharge reason
* ACP -- "esafe" (haven't looked into this one)
* BAT -- Battery level
* TE -- Temp, in deg. C
* HE -- Health
* VO -- Voltage, mV
* ED -- "event dev state" /* Battery charging in using a Event which consume lots of current */
* RC -- is recharging
* CC -- charge current (really current into the phone/chip, not the battery charging current, from what I can tell)
* VF -- /* Battery VF ADC value */ (no guess yet without a better datasheet on the chip)
The signature of you plugging in a USB cable:
Code:
<6>[ 595.059133] android_usb gadget: USB udc 0,1 lock
<7>[ 595.059150] s5pv210_lock_dvfs_high_level : lock with token(7) level(9) current(0)
<4>[ 595.063011] [otg_clock_enable] clk_enable(otg_clock) OK.
<4>[ 595.326017] [BAT] cable maxim_USB_connect~~~
<6>[ 595.326070] [TSP] (set_tsp_for_ta_detect) state = [1]
<6>[ 595.326082] [TSP] (set_tsp_for_ta_detect_exec) state = [1]
<4>[ 595.330665] [BAT] cable maxim_USB_connect~~~
<4>[ 595.332227] [BAT] CHR(1) CAS(1) CHS(1) DCR(0) ACP(2) BAT(99,0,0) TE(36) HE(1) VO(4062) ED(0) RC(0) CC(767) VF(590) LO(0)
<6>[ 595.428568] android_usb gadget: high speed config #1: android
<4>[ 595.828263] [BAT] cable maxim_USB_connect~~~
This looks good -- CHR=1, charging; CAS=1, USB; CC=767, 767 mA going into your phone
The signature of you plugging in a charger:
Code:
<4>[ 2081.071285] [BAT] cable maxim_not USB,TA _connect~~~ value =[0x40]
<6>[ 2081.071306] [TSP] (set_tsp_for_ta_detect) state = [1]
<6>[ 2081.071318] [TSP] (set_tsp_for_ta_detect_exec) state = [1]
<4>[ 2081.075739] [BAT] cable maxim_TA_connect~~~
<4>[ 2081.077302] [BAT] CHR(1) CAS(2) CHS(1) DCR(0) ACP(2) BAT(95,0,0) TE(35) HE(1) VO(4021) ED(0) RC(0) CC(869) VF(589) LO(0)
<4>[ 2081.573131] [BAT] cable maxim_TA_connect~~~
<6>[ 2081.573156] [TSP] (set_tsp_for_ta_detect) state = [1]
<6>[ 2081.573168] [TSP] (set_tsp_for_ta_detect_exec) state = [1]
<6>[ 2088.027317] [TSP] (set_tsp_for_ta_detect) state = [0]
<6>[ 2088.027334] [TSP] (set_tsp_for_ta_detect_exec) state = [0]
<4>[ 2088.039044] [BAT] CHR(0) CAS(0) CHS(3) DCR(0) ACP(2) BAT(95,0,0) TE(35) HE(1) VO(4101) ED(0) RC(0) CC(869) VF(590) LO(0)
<6>[ 2088.528641] [TSP] (set_tsp_for_ta_detect) state = [0]
<6>[ 2088.528656] [TSP] (set_tsp_for_ta_detect_exec) state = [0]
<6>[ 2091.622419] fsa9480 7-0025: dev1: 0x40, dev2: 0x0
<4>[ 2091.928089] [BAT] cable maxim_TA_connect~~~
<6>[ 2091.928111] [TSP] (set_tsp_for_ta_detect) state = [1]
<6>[ 2091.928121] [TSP] (set_tsp_for_ta_detect_exec) state = [1]
<4>[ 2091.932629] [BAT] cable maxim_TA_connect~~~
<4>[ 2091.961592] [BAT] CHR(1) CAS(2) CHS(1) DCR(0) ACP(2) BAT(95,0,0) TE(35) HE(1) VO(3983) ED(0) RC(0) CC(869) VF(591) LO(0)
<4>[ 2092.432471] [BAT] cable maxim_TA_connect~~~
<6>[ 2092.432493] [TSP] (set_tsp_for_ta_detect) state = [1]
<6>[ 2092.432503] [TSP] (set_tsp_for_ta_detect_exec) state = [1]
<6>[ 2096.440595] fsa9480 7-0025: dev1: 0x0, dev2: 0x0
<6>[ 2096.955019] [TSP] (set_tsp_for_ta_detect) state = [0]
<6>[ 2096.955041] [TSP] (set_tsp_for_ta_detect_exec) state = [0]
<4>[ 2096.976554] [BAT] CHR(0) CAS(0) CHS(3) DCR(0) ACP(2) BAT(95,0,0) TE(35) HE(1) VO(3997) ED(0) RC(0) CC(869) VF(592) LO(0)
It looks like it starts to successfully charge, then is disconnected. It tries again, then disconnects again.
The phone is trying to draw up to 1000 mA from an AC charger. 869 mA is close, but I am thinking that the wall charger may not be able to supply enough current for the smart phone. On the charger's side, probably in nearly illegible writing, you should see something like "Output: 5V, 500 mA" or "Output: 5V, 1000 mA" or "Output: 5V, 1.0 A" -- the first is probably going to cause problems, the last two should be "strong enough."

[Q] External Wi-Fi USB adapter

Hello, guys!
I got Nexus 5 running vanilla AOSP Android 4.4.3 compiled by myself. It works like a charm. I would like to use external Wi-Fi USB adapter with my Nexus 5. I've tried to use AWUS036NHA (with Atheros AR92721 chip) and two other models from different vendors. Every time I get the same error.
So, what have I done? I've rebuilt kernel to add support for my devices (in usual Linux way) and added firmwares they need to /vendor/firmware. When I plug AWUS036NHA into my phone I get the following (dmesg):
Code:
<6>[ 1587.856305] usb 1-1: new high-speed USB device number 2 using xhci-hcd
<6>[ 1587.887070] usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
<6>[ 1587.887129] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
<6>[ 1587.887221] usb 1-1: Product: UB91C
<6>[ 1587.887273] usb 1-1: Manufacturer: ATHEROS
<6>[ 1587.887365] usb 1-1: SerialNumber: 12345
<4>[ 1587.887857] usb 1-1: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.888693] usb 1-1: ep 0x82 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.888968] usb 1-1: ep 0x5 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.889115] usb 1-1: ep 0x6 - rounding interval to 32768 microframes, ep desc says 0 microframes
<6>[ 1587.890044] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
<6>[ 1588.180755] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
<6>[ 1588.416902] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
<6>[ 1588.644279] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
<7>[ 1588.644345] ath: EEPROM regdomain: 0x833a
<7>[ 1588.644351] ath: EEPROM indicates we should expect a country code
<7>[ 1588.644360] ath: doing EEPROM country->regdmn map search
<7>[ 1588.644367] ath: country maps to regdmn code: 0x37
<7>[ 1588.644374] ath: Country alpha2 being used: GB
<7>[ 1588.644379] ath: Regpair used: 0x37
<6>[ 1588.648677] ieee80211 phy3: Atheros AR9271 Rev:1
<7>[ 1588.650804] Registered led device: ath9k_htc-phy3
It seems to me that everything here is ok. But when I try to switch on the adapter (ifconfig wlan1 up) I get an error (dmesg):
Code:
ADDRCONF(NETDEV_UP): wlan1: link is not ready
By the way, "ifconfig" command shows no error, but certainly it doesn't swith my device on.
So, I got the same error with 3 different adapters. I got no idea about possible ways of solving this problem.
Please, share your ideas, I'm really stuck Looking forward for your help. And thanks in advance!

revive Pixel 3a

Hi there
my wife told me today that after the lunch her 3a was dead.
The screen is black, no led is lighting, nothing. She also told me the phone was charged over night - it should be no battery issue.
So I, as a good husband, attached it to my laptop and - everything is dark.
dmesg is saying
[ +8,360574] usb 1-11: new high-speed USB device number 12 using xhci_hcd
[ +0,127284] usb 1-11: New USB device found, idVendor=05c6, idProduct=9008, bcdDevice= 0.00
[ +0,000019] usb 1-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ +0,000010] usb 1-11: Product: QUSB_BULK_CID:0402_SN:37FACF8C
[ +0,000007] usb 1-11: Manufacturer: Qualcomm CDMA Technologies MSM
[ +0,003456] qcserial 1-11:1.0: Qualcomm USB modem converter detected
[ +0,000283] usb 1-11: Qualcomm USB modem converter now attached to ttyUSB0
Click to expand...
Click to collapse
adb devices and fastboot devices doesn´t see anything.
At least lsusb -v is showing something
Bus 001 Device 013: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9008 Gobi Wireless Modem (QDL mode)
bcdDevice 0.00
iManufacturer 1 Qualcomm CDMA Technologies MSM
iProduct 2 QUSB_BULK_CID:0402_SN:37FACF8C
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 16
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Click to expand...
Click to collapse
What is this QDL mode?
Is there a possibility to revive the device?
*edit*
OK, I found https://github.com/andersson/qdl
Lets try this