search

sonyxperiadev / bug_tracker

Empty repository that is used as a bugtracker for Open Devices project
52 stars 13 forks source link

[TAMA] Can't connect to PC by usb #531

Closed gumibea closed 4 years ago

gumibea commented 4 years ago

Platform: TAMA Device: Akari (H8296) Kernel version: 4.14 Android version: 10.0 Software binaries version: 0.0.7.1_R1_V3A_TAMA

Description Can't connect to pc by usb, no charge on mobile, and no device on pc. And it's same in the recovery.

MartinX3 commented 4 years ago

On which build datetime? My h8296 build from 01. Feb 13:29 CET has a working usb.

samduanx commented 4 years ago

Dear MartinX3, I have encountered this bug on a H8296 (Android 10, 4.14). The kernel was built on 14 Feb 20:32 CET. Symptoms: USB does not connect, after reboot when pluging in again there is only less than a second of charging (LED orange) and then disconnect. Further attempts of connecting does not work either. You are free to contact me if you need more information (seems hard to do dmesg since USB connection is normally mandatory).

MartinX3 commented 4 years ago

Dear @samduanx, could you try it with my build on XDA, too, since I never had this problem? Since we have the same model we could locate the issue easier, then :)

samduanx commented 4 years ago

@MartinX3 Yes sir, I have already using your XDA builds (both AOSP and LOS, latest version) and there is no sign of working.

MartinX3 commented 4 years ago

@samduanx Can you confirm that it works on stock with the exact same computer, usb port and cable? It sounds for me that the problem is either in the phone hardware, the usb cable, the usb port or the computer (maybe missing operatig system drivers, I use Linux to connect to my phone)

samduanx commented 4 years ago

@MartinX3 Yes it works with the stock firmware (I actually flashed the stock firmware using newflasher twice to confirm). The stock USB line did have a little contact issues but it worked flawlessly on Windows and Linux. My Windows laptop got all related drivers installed.

MartinX3 commented 4 years ago

@samduanx Now it becomes weird, since I own a H8296,too (But I installed the central european stock firmware before)

Can you us a dmesg after you connect the phone with your computer?

And how did you flash stock and SODP if the connection didn't work? O.o

samduanx commented 4 years ago

@MartinX3 I have used adb via Wi-Fi and used dmesg | grep -i usb to get the following log file: dmesg_log.txt This was after plugging in the phone to the laptop.

The USB worked under fastboot and flash modes.

MartinX3 commented 4 years ago

@samduanx thank you :)

Oh and a last question Does some weird entry appear in your windows device manager after you connected your phone or something like adb?

(In linux adb should work out of the box)

samduanx commented 4 years ago

@MartinX3 No, nothing is shown in the device manager.

MartinX3 commented 4 years ago

@samduanx Hmm, does it work on linux? (Virtual Machine with USB passthrough or booted from a usb stick or installed on your machine)

samduanx commented 4 years ago

@MartinX3 No, I have got a Linux laptop (Arch, updated) and the phone doesn't want to connect still.

MartinX3 commented 4 years ago

Different OS, different cable, different Hardware (and usb port)

Hmmmm

Did you flash and boot stock 10 before ?

Now I can only think about a software bug, since fastboot works and the ADB problem is always the same.

samduanx commented 4 years ago

I did booted stock 10 before, one without going through the first-time settings, and the other time did. Also, the bug affects more than adb, you could not transfer files or even charge the phone. This happed in both two ROMs, so I was firstly thinking of a kernel issue.

samduanx commented 4 years ago

@MartinX3 I am happy to find my solution: Simply flash H8266's stock ROM first instead of H8296's. I think it is because of the probable difference between H8266 and H8296. Still thanks for your help!

MartinX3 commented 4 years ago

@samduanx That's indeed very weird. You're welcome but please leave this ticket open and edit it to mention that it only happens with the H8296 stock firmware flashed before using SODP o.O Or call the sony support immediately with a bug report.

samduanx commented 4 years ago

Okay. I am currently creating a new issue regarding to this.

samduanx commented 4 years ago

@MartinX3 I have seen an issue from 2018 that Sony did not include config of H8296 first in SODP, but added after that (see issue #145). Did you add the config for it when building your ROM?

MartinX3 commented 4 years ago

@samduanx the H8296 device should work with a H8266 SODP ROM out of the box :)

samduanx commented 4 years ago

@MartinX3 Got it.

ix5 commented 4 years ago

This issue should be closed in favour of https://github.com/sonyxperiadev/bug_tracker/issues/546 since the author here does not provide sufficient info. @jerpelea