Bionic not working with docks after flashing .246 FXZ

[mattjenn]

Here is 3 more apps that's under the all apps tab smart dock, vehicle mode, and web top. Go in and force stop and if it let's you clear data and cache and scroll down to clear defaults and press that if it let's you. If it says computing let it finish or they'll be greyed out until it finishes. If none of these only other thing I could think of is its a hardware issue.

 

[bionicDock]

Here is 3 more apps that's under the all apps tab smart dock, vehicle mode, and web top. Go in and force stop and if it let's you clear data and cache and scroll down to clear defaults and press that if it let's you. If it says computing let it finish or they'll be greyed out until it finishes. If none of these only other thing I could think of is its a hardware issue.

Nope, still nothing. I guess it must be some sort of hardware issue like you said. I have come up with a work around for anyone who is having a similar problem. I purchased a bluetooth capable stereo for my truck. I'm simply going to use smart actions an create a rule to start bluetooth anytime my phone is charging (when it's connected to the dock) Then I'm going to create another rule to launch a car dock app I downloaded when it connects to a specific device (my stereo). and simply stream the audio through bluetooth. While it doesn't really fix the issue, it certainly is a decent workaround.

Thanks for all your help mattjen!

-NCB

 

[rkismet]

Nope, still nothing. I guess it must be some sort of hardware issue like you said. I have come up with a work around for anyone who is having a similar problem. I purchased a bluetooth capable stereo for my truck. I'm simply going to use smart actions an create a rule to start bluetooth anytime my phone is charging (when it's connected to the dock) Then I'm going to create another rule to launch a car dock app I downloaded when it connects to a specific device (my stereo). and simply stream the audio through bluetooth. While it doesn't really fix the issue, it certainly is a decent workaround.

Thanks for all your help mattjen!

-NCB

i dont think its a hardware issue per-say...unless we are talking at the 50K ft level and says its a bionic
im having the same issue since going to 4.0...home button issues to.

-------------
standard dock
vehicle dock
home button
getting firmware updates when promised :-\
-------------

 

[matthimrod]

I'm having pretty much the same problem as the OP.

I tried flashing a custom ROM (AOKP, if I recall correctly), but I didn't realize until after it was done that it is designed to be run with Safestrap (dumb of me, I know). So, I flashed back to 246 using moto-fastboot, installed Bionic Boostrap and restored my nandroid backup. My docks were mostly not working (more details below). I assumed I had a bad flash, so I reflashed 246 with moto-fastboot again, assuming that would fix the problem. Of course, then I got antsy and installed the JB update that leaked out yesterday without testing the docks first. Now my docks still won't work and I think trying to flash back to 246 using moto-fastboot again is a bad idea.

Both before and after reflashing, I tried force stop/clear data/clear cache on all of the dock-related services.

My Lapdock, HD Dock, Standard Dock, and Navigation Dock all will not fully work. They will all charge the phone, but the phone doesn't go into dock mode nor do I get audio through the dock's audio connectors. I get a little bit more love from the HD Dock and Lapdock. On the HD Dock, the USB ports and remote control function, but the phone won't go into "dock mode". For the most part, the Lapdock works as well, but it won't display the dock's battery status nor does the phone seem to realize it's in the dock and not just connected to the TV with an HDMI cable.

If I am connected with adb, and put the phone into the HD Dock, I see the following from dmesg:

<6>[11003.122406,1] cpcap spi1.0: notify_accy: accy=USB DEVICE
<6>[11003.133880,1] SW:CPCAP_ACCY_USB_DEVICE Connected
<7>[11003.345489,1] musb-hdrc: setup fifo_mode 4
<7>[11003.345642,1] musb-hdrc: 17/31 max ep, 13632/16384 memory
<6>[11003.361236,1] EVENT_NONE: host mode, stop musb
<7>[11003.361358,1] musb-hdrc: setup fifo_mode 4
<7>[11003.361572,1] musb-hdrc: 28/31 max ep, 15424/16384 memory
<6>[11003.361694,1] EVENT_NONE: pull down, disable gadget
<6>[11003.361877,1] EVENT_NONE: pull up, enable gadget anyway
<7>[11003.587646,1] musb-hdrc: setup fifo_mode 4
<7>[11003.587799,1] musb-hdrc: 17/31 max ep, 13632/16384 memory
<6>[11004.017395,1] usb 3-1: new high speed USB device number 4 using musb-hdrc
<3>[11004.166290,0] usb 3-1: device v22b8 p0939 is not supported
<6>[11004.166534,0] usb 3-1: New USB device found, idVendor=22b8, idProduct=0939
<6>[11004.166778,0] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[11004.166900,0] usb 3-1: Product: Motorola HD Dock
<6>[11004.167114,0] usb 3-1: Manufacturer: Motorola Inc.
<6>[11004.167236,0] usb 3-1: SerialNumber: 22E16C22
<6>[11004.169799,0] hub 3-1:1.0: USB hub found
<6>[11004.170257,0] hub 3-1:1.0: 4 ports detected
<6>[11004.454895,0] usb 3-1.1: new full speed USB device number 5 using musb-hdrc
<3>[11004.565826,0] usb 3-1.1: device v22b8 p0938 is not supported
<6>[11004.565917,0] usb 3-1.1: New USB device found, idVendor=22b8, idProduct=0938
<6>[11004.566070,0] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[11004.566223,0] usb 3-1.1: Product: Motorola HD Dock
<6>[11004.566314,0] usb 3-1.1: Manufacturer: Motorola Mobility
<6>[11004.566375,0] usb 3-1.1: SerialNumber: 86C192461C001D00
<6>[11004.571075,0] input: Motorola Mobility Motorola HD Dock as /devices/platform/omap/musb-omap2430/musb-hdrc/usb3/3-1/3-1.1/3-1.1:1.0/input/input7
<6>[11004.572204,0] using input dev Motorola Mobility Motorola HD Dock for key reset
<6>[11004.572357,0] keychord: using input dev Motorola Mobility Motorola HD Dock for fevent
<6>[11004.572998,0] motorola 0003:22B8:0938.0002: input,hidraw0: USB HID v1.01 Keyboard [Motorola Mobility Motorola HD Dock] on usb-musb-hdrc-1.1/input0

It seems that in the case of the HD Dock, the phone detects the dock devices, but I don't see the same thing from the standard or navigation docks. With the navigation dock and only seeing the following:

<6>[21974.348724,0] cpcap spi1.0: notify_accy: accy=NONE
<6>[21992.228668,0] cpcap spi1.0: notify_accy: accy=CHARGER

I'm guessing there's some disconnect with the USB port on the phone. The HDMI port seems okay. I'd also assume that it's some sort of software issue as well since it started after my ROM flashing attempt. I know the docks are all okay because I have an identical work Bionic that I've kept totally stock and unrooted. All of the docks work fine with the work phone, so the docks should be fine. Beyond examining dmesg, I'm not sure what to do next to troubleshoot. When I saw the dmesg output when connecting the HD Dock, I assumed that the kernel was detecting the docks, but my test with the navigation dock refuted that.

Anyone have any ideas of what I can look for next?

 

[taller238]

I have exactly the same problem.
Have you managed somehow to solve it?
Since I'm already on .246, I'm not sure if I can reflash a .246 once again.
I thought you reflashing the .246 indicated you do it again toward a .246 base, correct?

Thank you in advance for your advice.

 

[matthimrod]

I haven't been able to resolve my problem. I've since upgraded to 98.72.22 (Jelly Bean), so I no longer have the ability to reflash 5.9.246. Since others have had issues with the .246 reflash, I doubt reflashing it a third time would help. I also tried doing a partial flash of the 98.72.22 file (all but userdata and emstorage), but that didn't help either. Since I don't really have motivation to wipe and start over, I'm not trying a full flash unless I know it'll work.

 

[taller238]

Thank you for the sharing.

So how did you flash the 98.72.22? Using RSD lite to flash it from .246? Just like RSD flashed .246 from .905?
If so, do you have other choices other than the 98.72.22, which was also allowed to be flashed from a .246 base?
then why choose 98.72.22 among them?

Many thanks

I haven't been able to resolve my problem. I've since upgraded to 98.72.22 (Jelly Bean), so I no longer have the ability to reflash 5.9.246. Since others have had issues with the .246 reflash, I doubt reflashing it a third time would help. I also tried doing a partial flash of the 98.72.22 file (all but userdata and emstorage), but that didn't help either. Since I don't really have motivation to wipe and start over, I'm not trying a full flash unless I know it'll work.

 

[matthimrod]

98.72.22 was the the OTA JB update. You can't flash backwards back to .246 or .905 because the secure versions of the partition images are incremented for the important partitions. If you try to flash backwards, you'll soft brick your phone.

I did the partial flash using moto-fastboot. I don't use RSD Lite for a few reasons, the biggest of which is that it's overkill for the task. Fastboot also gives you greater control over what's going on instead of having this "magic black box" that just does things for you.

Thank you for the sharing.

So how did you flash the 98.72.22? Using RSD lite to flash it from .246? Just like RSD flashed .246 from .905?
If so, do you have other choices other than the 98.72.22, which was also allowed to be flashed from a .246 base?
then why choose 98.72.22 among them?

Many thanks

 

[taller238]

Thank you for your informative writing.

You mentioned 98.72.22 was from the OTA JB update. So the way to get the 98.72.22 is from Setting->About phone->System updates?
I did find an update there from the stock 6.7.246 and have downloaded. But after automatic powerdown, it always failed to install. Is it the 98.72.22 you mentioned?

And also about the moto-fastboot. What's object your "partial flash" is about? I believe it's not a whole version like .246 or .905 since it may brick the Bionic. Then what is it and where to get it, specially for the hdmi issue?

Thanks again.

98.72.22 was the the OTA JB update. You can't flash backwards back to .246 or .905 because the secure versions of the partition images are incremented for the important partitions. If you try to flash backwards, you'll soft brick your phone.

I did the partial flash using moto-fastboot. I don't use RSD Lite for a few reasons, the biggest of which is that it's overkill for the task. Fastboot also gives you greater control over what's going on instead of having this "magic black box" that just does things for you.

 

[matthimrod]

Yes. 98.72.22 is the latest OTA update. If it's failing to install, you must have modified one of your partitions in some way that is causing the update checks to fail.

The "partial flash" that I referred to was taking the 98.72.22 system images and flashing the partitions manually. This allowed me to skip the commands that would have reformatted the userdata (/data) and emstorage (/mnt/sdcard) partitions. It's the whole version, just without clearing all data from the phone. If you're still on .246, you'll need to do this with the .246 files before completing your upgrade. You shouldn't try to flash 98.72.22 with moto-fastboot (or RSD Lite for that matter) without clearing your userdata and emstorage partitions because the scripts that upgrade your system databases will not run.

I was not having any issues with the HDMI port, so I can't speak to whether or not reflashing using the 98.72.22 files will resolve your issue. My issue is specifically with docks that use the USB port.

Thank you for your informative writing.

You mentioned 98.72.22 was from the OTA JB update. So the way to get the 98.72.22 is from Setting->About phone->System updates?
I did find an update there from the stock 6.7.246 and have downloaded. But after automatic powerdown, it always failed to install. Is it the 98.72.22 you mentioned?

And also about the moto-fastboot. What's object your "partial flash" is about? I believe it's not a whole version like .246 or .905 since it may brick the Bionic. Then what is it and where to get it, specially for the hdmi issue?

Thanks again.

 

[taller238]

Just report here an update: I just reflashed 6.7.246 from a 6,7,246 by RSD lite. So ppl who still wondering if that will brick you Bionic should go ahead to do that. No prblem at all, at least to me.

After the reflashing, I found the HDMI PARTIALLY works - though it's only a TWO SECOND showing-up on one of my three LCD tv (but none of LCD monitors) when I switch the input source to that HDMI input.
Even that proves that the Bionic HDMI may work, but still has a long way to go to make the HDMI useful.

I'm curious at the point what means "not having any issues with the HDMI port", assumingly on your native 6.7.246 stock rom? Are you saying just connect your Bionic with your TV directly with a MicroHDMI-HDMI cable then the phone's screen was "mirrored" to the TV? Without any Mod/hack thing? Without any specific App to launch? And without involving any docks?

If yes, then apparantly that didn't happen to me. I did find an App named "Webtop" (abt 3.03M) residing in the Settings->Apps->All, but not sure if that means anything when I tried to directly connect HDMI to the TV.

Please let me know if you have any thoughts.

Thanks.

Yes. 98.72.22 is the latest OTA update. If it's failing to install, you must have modified one of your partitions in some way that is causing the update checks to fail.

The "partial flash" that I referred to was taking the 98.72.22 system images and flashing the partitions manually. This allowed me to skip the commands that would have reformatted the userdata (/data) and emstorage (/mnt/sdcard) partitions. It's the whole version, just without clearing all data from the phone. If you're still on .246, you'll need to do this with the .246 files before completing your upgrade. You shouldn't try to flash 98.72.22 with moto-fastboot (or RSD Lite for that matter) without clearing your userdata and emstorage partitions because the scripts that upgrade your system databases will not run.

I was not having any issues with the HDMI port, so I can't speak to whether or not reflashing using the 98.72.22 files will resolve your issue. My issue is specifically with docks that use the USB port.

 

[matthimrod]

DO NOT DO THIS IF YOU HAVE TAKEN THE OTA UPDATE. YOU WILL SOFT BRICK YOUR PHONE.

taller238 successfully flashed 6.7.246 because his update failed and he was not running 98.72.22.

Just report here an update: I just reflashed 6.7.246 from a 6,7,246 by RSD lite. So ppl who still wondering if that will brick you Bionic should go ahead to do that. No prblem at all, at least to me.

Sent from my Nexus 7 using Tapatalk HD

 

[taller238]

Good reminding. If I made the ota update 98.72.22 then I may not be able to go through the reflashing of 6.7.246 on its own.

Also matthimrod, can you please take a look at my post #26 about the HDMI issue? All I did is just for that sake

Thanks again.

DO NOT DO THIS IF YOU HAVE TAKEN THE OTA UPDATE. YOU WILL SOFT BRICK YOUR PHONE.

taller238 successfully flashed 6.7.246 because his update failed and he was not running 98.72.22.





Sent from my Nexus 7 using Tapatalk HD

 

[matthimrod]

My HDMI works with my devices in both mirror and web top modes without any additional tweaking or third party apps. It seems that you are having an unrelated issue. You may find it helpful to look at dmesg or logcat but I'm not sure what to tell you to look for.

Good reminding. If I made the ota update 98.72.22 then I may not be able to go through the reflashing of 6.7.246 on its own.

Also matthimrod, can you please take a look at my post #26 about the HDMI issue? All I did is just for that sake

Thanks again.

Sent from my Nexus 7 using Tapatalk HD

 

[taller238]

This is a section about HDMI I got from logcat.txt:

05-01 15:38:41.134 D/HWC_HDMI_MOT( 158): Display Inactive
05-01 15:38:41.134 D/HWC_HDMI_MOT( 158): handle_hdmi_pwrctrl (0/0/0/0)
05-01 15:38:41.134 D/HDMI ( 158): HDMI_SetDisplay (0)
05-01 15:38:41.134 D/HDMI ( 158): HDMI_SetDisplay: Already Off
05-01 15:38:41.134 D/HDMI ( 158): HDMI_SetDetection (0)
05-01 15:38:41.134 D/HDMI_OMAP( 158): hdmiOmap_SetPwrState: On -> Off
05-01 15:38:41.134 D/HDMI_OMAP( 158): hdmiOmap_disableEvents
05-01 15:38:41.134 D/HDMI_OMAP( 158): hdmiOmap_eventLoop: Exiting
05-01 15:38:41.134 D/HDMI_HW ( 158): hdmiHw_setHpdEnable (0)
05-01 15:38:41.134 D/HDMI_HW ( 158): Setting HDMI PwrCtrl State (1)

there's no word "hdmi" found in dmesg.txt
if you don't mind, can you please provide the hdmi section of yours (which has a working hdmi), so I can make a compare?

Thank you so much.

My HDMI works with my devices in both mirror and web top modes without any additional tweaking or third party apps. It seems that you are having an unrelated issue. You may find it helpful to look at dmesg or logcat but I'm not sure what to tell you to look for.





Sent from my Nexus 7 using Tapatalk HD