adb hang issue with i.MX6DQ kk4.4.2-1.0.0-ga.

[satoshishimoda]

Hi community,

I have a about i.MX6DQ Android kk4.4.2_1.0.0-ga.

Actually, adb hangs and don't return a response when execute the following procedure.

[Board]

MCIMX6Q-SDP

[BSP]

Android kk4.4.2_1.0.0-ga

[Procedure]

1. Boot kk4.4.2_1.0.0-ga BSP on MCIMX6Q-SDP, and connect MCIMX6Q-SDP & PC via USB.

2. Tap "Settings" -> "About Tablet" -> "Build number" seven times, then "Developpers option" appears.

3. Enable "Developpers option" -> "USB debugging".

4. Activate adb with the following command on PC.

adb devices

4. Execute following adb command on PC.

adb usb

5. Execute a adb command after that. (e.g. adb shell ls)

Then, adb seems it was hanged and kk4.4.2_1.0.0-ga did not response to adb command.

[Question]

Could you let me know how should we modify kk4.4.2_1.0.0-ga to this adb hang issue resolve?

Best Regards,

Satoshi Shimoda

[SergioSolis]

That's odd.. the steps you mentioned should work.. I just did the procedure and was able to go to USB mode.

I'm also using kk 4.4.2 in the i.mx6Q SDP

Do you get any error or message?

[satoshishimoda]

Hi SerchMX,

I'm sorry, I miswrote what is happen.

Yes, enter to USB mode is no problem.

adb hang issue occurs when execute next adb command.

I updated this post, could you recheck it?

Best Regards,

Satoshi Shimoda

[SergioSolis]

Do you see any hang up if you skip "adb usb"?

By default, adb is running at USB mode. If you restart the adb in TCP mode, you need to use "adb usb" to switch it back. I think the hang up is caused by adb itself.

I think this would need to be reported to Google.

[satoshishimoda]

Hi SerchMX,

Would you give me a comment about this issue again?

Do you think it is android issue? or bsp issue?

Best Regards,

Satoshi Shimoda

[SergioSolis]

Apart from the adb application and device, there is a PC driver which handle the communication between adb application and devices. Are you saying that the same PC driver is used when other KitKat devices is reproducing the problem.

By the way, is there any real problem here to the issue where no response to adb command after "adb usb"?

[satoshishimoda]

Hi SerchMX,

> Are you saying that the same PC driver is used when other KitKat devices is reproducing the problem.

Host PC is Ubuntu, and no new driver was installed.

> By the way, is there any real problem here to the issue where no response to adb command after "adb usb"?

Android CDD (Compatibility Definition Document) defines about adb as following.

=====

Device implementations MUST support all adb functions as documented in the Android SDK

=====

We think this issue violate the above definition, so the android product is not able to be shipped to end customer in worst case.

Best Regards,

Satoshi Shimoda

[SergioSolis]

This issue has been escalated to fix it. I will update you as soon as I get updates too.

[satoshishimoda]

Hi SerchMX,

Would you let me know how log time is needed to fix this issue?

Best Regards,

Satoshi Shimoda

[SergioSolis]

Hello Satoshi,

The last update I have is that our R&D team is working on it. Unfortunately there is no estimated time yet to have it fixed.

[satoshishimoda]

Hi Sergio Solis,

I heard the fix schedule for this issue from Freescale Japan.

Please update ASAP when you get a solution.

Best Regards,

Satoshi Shimoda

[SergioSolis]

I will let you know as soon as I have something. The fix was scheduled to be worked on after the GA release of Jan 23rd, so they should start today or monday I guess

[satoshishimoda]

Hi Sergio Solis,

> The fix was scheduled to be worked on after the GA release of Jan 23rd,

Yes, I heard it from Freescale Japan.

Then, could you let me know when this issue will be fixed also before release a patch?

Best Regards,

Satoshi Shimoda

[SergioSolis]

Hello Satoshi,

The problem is fixed in KK4.4.3_2.0.0 which will be released soon (sanity check is scheduled to end on Jan 31st).

This release will use 3.10 kernel.

Please let me know of any question you may have.

[satoshishimoda]

Hi Sergio Solis,

Is there any method to fixed this issue on kk4.4.2_1.0.0-ga without kernel update from 3.0.35 to 3.10?

Best Regards,

Satoshi Shimoda

[SergioSolis]

Hello Satoshi,

Our SW team found that the kernel is suspended on drivers/usb/gadget/f_adb.c line 309 , but there is no solution available yet.

Satoshi, is your customer able to upgrade to KK4.4.3 or is it necessary to stay at kk4.4.2 ?

[satoshishimoda]

Hi Sergio,

Unfortunately, our customer MUST use kk4.4.2.
It is not enough time to estimate k4.4.3 and kernel 3.10.x because it is close to mass production.

And they have applied to google for certification with kk4.4.2.

Best Regards,

Satoshi Shimoda

[SergioSolis · Accepted solution]

Hello Satoshi,

I was told that the USB reset mechanism has been added to ADB commands and that you have confirmed this is fixed. I will procced to close this thread.

Please let me know of any other question you may have.

[satoshishimoda]

Hello Sergio,

Yes, this issue has been fixed by the patch.

I appreciate your great support!

Best Regards,

Satoshi Shimoda

[damiendejean]

Hello Satoshi,

We're facing an issue similar to the one you had. Is the patch you are talking about available somewhere ?

Best regards,

Damien

[satoshishimoda]

Hello Damien,

I got the patch from a local Freescale FAE, so I don't know whether the patch is available somewhere now.

And I don't know whether it is OK to attached the patch to this post also.

I recommend you create a Service Request to get the patch.

The patch name is "0001-MA-6018-usb-gadget-android-fix-adb-hang-issue-after-.patch.".

I hope this helps.

Best Regards,

Satoshi Shimoda