[Atrix 4G Android Development] zelipukin:
Atrix Ba2tF No connection via USB in OS mode

Device: Motorola Atrix MB860

Mod V.: CyanogenMod-7.1.0-Ba2tF-Olympus

Kernel V.: 2.6.32.50-MB860-CM7-faux123-v023r

Symptoms: Phone does not connect via USB in OS mode

(actually, as I can understand from logcat(attached) it starts to connect then disconnects

then connects again and so on untill cable is plugged)

- usb connection msg appears for the very short time in notif.bar

- windows begins to recognize connected device (see win_msg.png attached)

but device disconnects same second and windows can't finish process.

- device connects to pc OK in any other modes (fastboot, recovery)

(see USBDevview attached)

-device charges via usb OK

-device does not tether via usb

Search - yes, I did. Lot of people have similar problem - no answers but obvious

(cables, drivers, ports, hub, etc.)

When it first happened: not sure but after Ba2tF installed

FAQ:

-did it work before? yes, all the time (stock and prev.CM7)

-different machines? yes, PC w. WXP and NB w.W7

-cables? they(3, orig.incl.) are oK

-ports? ~10, all are OK incl.device port

-hub? I have one(powered) - same result

-drivers? yes, latest Moto. You don't need any spec.drivers for mass storage mode?

-Enable/disable debugging? Yes, I know what is it

-Notification bar w. usb message - not accessible

-Uninstall all mass storage devices / Moto devices /drivers then plug device in. Yes, I did

-Recognize device/load drivers in a different mode(fastboot, recovery) then reboot to OS. Yes, I did

-Different android devices w. same machines? Had no chance to try

-Different kernel? Yes, Clemsyn's, same result

-Different ROMs after issue found? No, I like this one (thanks to devs !) and have not to much time to experiment.

-Any apps installed right before issue? may be, not sure

-Any sys. changes right before issue? Not sure before or after, I've mounted back internal sd as /mnt/sdcard and external one as /mnt/emmc.

-Undervolting? All -50, but same result w. 0

-Overclocking? No

I post my Q here because this is a developers forum and someone smart enough can read logcat(attached)

and find something suspicious. if I'm wrong, please, correct

Short logcat (long attached):

D/MotUsbService( 1650): handleUsbEvent(), Received event: 0, current state: 0

D/UsbSettings( 1650): USB mode (fallback) : 5

D/UsbListener( 1650): received usb mode change command from UI: usb_mode_charge_adb

D/UsbListener( 1650): Writing command usb_mode_charge_adb� to usbd

I/usbd ( 1456): main(): Read and handle a pending message from the App

I/usbd ( 1456): usbd_socket_event(): recieved usb_mode_charge_adb

I/usbd ( 1456): usbd_socket_event(): Matched new usb mode = 16 , current mode = 0

I/usbd ( 1456): usbd_set_usb_mode(): new_mode: charge_adb

D/UsbListener( 1650): handleEvent: usb_mode_msc:ok

D/MotUsbService( 1650): handleUsbEvent(), Received event: 2, current state: 1

D/UsbSettings( 1650): USB mode (fallback) : 5

D/UsbSettings( 1650): USB mode (fallback) : 5

I/BATTD ( 1455): set_charge_voltage=4200

D/Vold ( 1369): USB connected

I/BATTD ( 1455): set_charge_current=100

I/ftmipcd ( 2637): USBLAN interface not available

D/lights ( 1514): RGB: USER, "battery", color=0xffffff00, onMs=0, offMs=0

D/lights ( 1514): RGB, blink=0, RGB=0 0 0

D/FlexLabs( 1768): Widget count: 1

I/usbd ( 1456): process_usb_uevent_message(): cable type: usb

I/usbd ( 1456): main(): Spurious Cable Event, Ignore

I/ActivityManager( 1514): Start proc com.android.settings for broadcast com.android.settings/.widget.SettingsAppWidgetProvider: pid=2645 uid=1000 gids={3002, 3001, 3003, 1015}

I/BATTD ( 1455): set_charge_current=0

I/BATTD ( 1455): Battd CHARGER/USB Removed = Success

I/usbd ( 1456): process_usb_uevent_message(): cable type: none

I/usbd ( 1456): process_usb_uevent_message(): USB offline

I/usbd ( 1456): main(): Cable Status Changed, need to notify Cable Status to App

I/usbd ( 1456): usbd_notify_current_status(): Notifying App with Current Status : cable_disconnected

D/UsbListener( 1650): handleEvent: cable_disconnected

D/MotUsbService( 1650): handleUsbCableDetachment()

D/MotUsbService( 1650): handleUsbEvent(), Received event: 4, current state: 2

D/UsbSettings( 1650): USB mode (fallback) : 5

D/MotUsbService( 1650): deviceEnumPreAction()

D/UsbSettings( 1650): USB mode (fallback) : 5

D/MotUsbService( 1650): handleUsbEvent(), Received event: 6, current state: 4

D/UsbSettings( 1650): USB mode (fallback) : 5

D/UsbListener( 1650): received usb mode change command from UI: usb_unload_driver

D/UsbListener( 1650): Writing command usb_unload_driver� to usbd

I/usbd ( 1456): main(): Read and handle a pending message from the App

I/usbd ( 1456): usbd_socket_event(): recieved usb_unload_driver

I/usbd ( 1456): usbd_socket_event(): Matched new usb mode = 0 , current mode = 0

D/Vold ( 1369): USB disconnected

D/lights ( 1514): RGB: USER, "battery", color=0x00000000, onMs=0, offMs=0

D/lights ( 1514): RGB, blink=0, RGB=0 0 0

D/szipinf ( 2645): Initializing inflate state

I/BATTD ( 1455): Battd USB INSERT = Success

.................................................................................................

THANK YOU!