account arrowhead-down arrowhead-up mobile-menu search sm-bold-x x-skinny-rounded x-skinny arrowhead-right social-facebook social-googleplus social-instagram social-linkedin social-pinterest social-qzone social-renren social-tencent social-twitter social-vkontakt social-weibo social-youku social-youtube

Please help us improve our website

Take our customer survey to evaluate your visit.

It should only take a few minutes to answer five quick questions. Just click the Launch survey button at the end of your visit to begin.

cancel
Showing results for 
Search instead for 
Did you mean: 
Welcome to the Open Devices community!

This is where we discuss open source and development related questions on our Open Devices initiative.

Xperia Z4 AOSP (karin) does not boot to charger mode [NEW]

Highlighted
Apprentice
Message 1 of 2
1,750 Views
Message 1 of 2

Xperia Z4 AOSP (karin) does not boot to charger mode [NEW]

Hello,

 

Karin does not boot to charger mode when connect to Linux PC via USB port.

 

[Software]

AOSP android-6.0.1_r66

Sony prebuilt: Xperia_AOSP_M_MR1_v06

 

[How to reproduce]

1. Power off device

2. Connect device to Linux PC using USB cabble

3. -> NG: charger mode is not shown, device seems to reset and boot to android.

 

[Expected behavior]

Device should boot to charger mode (Battery animation should show up)

 

[Note]

If device connects to charger (TA), it can boot to charger mode as normal (OK)

If device connects to Windows PC, reset seems not occurs but battery animation still not show up (NG)

 

It might be problem of dwc3 driver in aosp/LA.BR.1.3.3_rb2.14, so AOSP 6.0.1/7.0/7.0.1 may have same issue.

Because device seems to reset in charger mode, kernel messages are all lost => Uart-enabled device may be need to get log for this issue.

 

Thanks. 

1 REPLY 1
Developer World
Message 2 of 2
1,728 Views
Message 2 of 2

Re: Xperia Z4 AOSP (karin) does not boot to charger mode [NEW]

Hi,

 

please flash the latest sony SW to get the bootloader update,then build and flash the AOSP following the build guide .

 

I tested the reported bug and the device has the expected behaviour

 

Regards

Alin