Laptop Won't Charge BJII When Tethered

[Guest goodguy6]

I'm using a BJII that has just been updated to WM6.1

When using my BJII for an Internet connection while tethered to my previous notebook, a Toshiba Lifebook, one of the nice side benefits was that the notebook would provide power from the USB port to charge the BJII.

Now I'm using an Acer Inspire One. Unfortunately, the USB power doesn't remain on continuously, at least on the right-rear USB port that I want to use. It comes on when the BJII is first plugged in, but then switches off. Looking in the USB section of Device Manager, I see no way to set the port for continuous power.

UPDATE: I find that my AC charger ALSO won't charge the phone. When I plug the charger in, the red charging led on the phone turns on. After about 30 sec, it blinks for about 5 sec, then turns off. The phone's battery is clearly not fully charged. It worked perfectly before the upgrade to WM6.1

FURTHER UPDATE: Turns out it seems to be related to ActiveSync 4.5. I turned off the phone and removed the battery to do a reset. Once i re-started the phone and then plugged it into the AC charger, it charged normally. HOWEVER, when I plug it into the laptop via the tethering cable, the red led on the phone goes OFF once ActiveSyne has finished its synchronization. ActiveSync 3 didn't do that. I see no way to adjust this.

So, what to do? Could I set the BJII to send to the modem, rather than ActiveSync 4.5? Seems like ICS didn't work when I tried that. Is there any way to stop ActiveSync 4.5 from switching off the USB port power once it's finished syncing?

Any ideas?

Edited February 23, 2009 by goodguy6

[Guest Majyk]

Same problem here. I have no problems charging from the AC charger or the car charger but my BJ2 will not charge once Activesync has finished connecting to the phone. My Q9h charges fine all the time. Haven 't had any luck finding a fix for the BlackJack 2 yet. Anyone gets this one figured out, please let me know.

Majyk

[Guest RichWhy]

Is your USB sync cable model # APCBS10BBE? If not, it needs to be.

Same problem here. I have no problems charging from the AC charger or the car charger but my BJ2 will not charge once Activesync has finished connecting to the phone. My Q9h charges fine all the time. Haven 't had any luck finding a fix for the BlackJack 2 yet. Anyone gets this one figured out, please let me know.

Majyk

Edited April 30, 2009 by RichWhy

[Guest mikefazz]

So after 'upgrading' to WM 6.1 I have had the same problem. I figured out a hack that helps... at least partially

1. Open the USB -> BJII cable and cut the white and green (usb signal) cables (maybe the ground[bare] wire too).

2. Look at the end of the connector with the yellow arrow down and bend the third pin from the right (third (-) pin) to the left and down into the connector to get it out of the way. You will need a fine flat head, pin, needle, or something and good lighting.

This makes the connector look the same as the AC adapter to the phone. The AC adapter outputs 700ma and the usb 500ma. I have revived my drained cell phone from a computer and a simple 4-AA NiMh battery block.

That third (-) pins seems to tell the cell phone that it is connected to a USB cable and not to charge... odd.

Of course try at your own rist

I have tried reconnecting the green and white cable but the cell phone doesn't show up with the computer. So this makes this a charging only adapter cable. But to me this is better than carrying a proper AC or car adapter.

Edited September 29, 2009 by mikefazz

[Guest Roger525]

Just thought I'd share -- I have this problem too, sort of.

My BJII had MW6.1 out of the box. I'm running Windows 7 on my laptop now, which downloads the latest ActiveSync when required (when you plug in a Windows Mobile phone for the first time).

Same symptoms when connecting the BJII to USB: It'll say it's charging for about half a minute, then stops charging. Killing Active Sync (or Windows Mobile Device Center) doesn't seem to have any effect. Phone will still charge fine through the AC adapter though. Still, quite annoying.