Samsung Galaxy A5 (2016) #269
Comments
mskiptr
added a commit
to mskiptr/android-udev-rules
that referenced
this issue
Aug 23, 2023
No other device was harmed in the making of this commit. Closes: M0Rf30#269
mskiptr
added a commit
to mskiptr/android-udev-rules
that referenced
this issue
Aug 23, 2023
No other device was harmed in the making of this commit. Closes: M0Rf30#269
mskiptr
added a commit
to mskiptr/android-udev-rules
that referenced
this issue
Aug 23, 2023
No other device was harmed in the making of this commit. Closes: M0Rf30#269
JoesCat
pushed a commit
to JoesCat/android-udev-rules
that referenced
this issue
Aug 29, 2023
Details as seen in issue M0Rf30#269 - Samsung Galaxy A5 (2016)
JoesCat
added a commit
to JoesCat/libmtp
that referenced
this issue
Sep 29, 2023
Thanks to Piotr Masłowski (mskiptr) for a detailed capture of all these different modes listed here for the A5 seen in issue 269: M0Rf30/android-udev-rules#269 I also can confirm a subset of the PIDs above for the Core: M0Rf30/android-udev-rules#276
JoesCat
pushed a commit
to JoesCat/android-udev-rules
that referenced
this issue
Sep 29, 2023
Thanks to Piotr Masłowski (mskiptr) for the detailed work done here. See issue M0Rf30#269
M0Rf30
pushed a commit
that referenced
this issue
Sep 29, 2023
Thanks to Piotr Masłowski (mskiptr) for the detailed work done here. See issue #269 Co-authored-by: Piotr Masłowski <piotr@maslowski.xyz>
M0Rf30
pushed a commit
that referenced
this issue
Sep 29, 2023
Details as seen in issue #269 - Samsung Galaxy A5 (2016) Co-authored-by: Piotr Masłowski <piotr@maslowski.xyz>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'll send patches after #266 lands. For now, here are all the IDs I could find. I don't have this phone at hand anymore, but I should be able to test things out in a few weeks. If there's anything I had missed do tell me about it.
One thing to note is, since this is a Samsung device, it uses Odin instead of fastboot.
Hardware info
Codename: samsung-a5xelte
Model #: SM-A510F
16113
GH90-42117T
Name: Galaxy A5 (2016)
(The model number is accompanied by these two other things on a sticker in the box. I'm including these for search engine accessibility I guess.)
Software info
Android version: 7.0
Version number: NRD90M.A510FXXS8CTI7
Summary
Here are the non-Android USB modes:
04e8:685d04e8:686004e8:6860These are available from the notification that appears after connecting the phone to a PC:
04e8:686004e8:686504e8:686c04e8:686004e8:686004e8:686604e8:686c04e8:6860And these are what's available in Settings > Developer options > USB configuration:
04e8:686004e8:686504e8:686c04e8:686318d1:2d0204e8:686004e8:686604e8:686c04e8:686004e8:686418d1:2d03Even though
04e8:6860appears a lot, these cases can be (fully?) differentiated based on other factors, such as the length of the serial number or that ACM stuff (see the kernel logs with debugging on).(And here is something interesting: https://youtu.be/I5MtbF4KsDw?t=150. Tho I found about it too late and can't check it out right now.)
Data gathering
All tested with a USB 2.0 A-to-µB cable.
Nothing below is too important. I include it so that it's easy to tell if I made mistakes anywhere and in case additional details are needed.
Phone off:
Neither
fastboot devices,adb devicesnorheimdall detectgave any output.Just after powering on:
The phone re-connects after unlocking it
(maybe the cable is wonky?).Second try of everything: I was careful not to disturb the cable, yet it reconnected after just waiting a little longer. After unlocking it didn't re-connect, but there was this message about the PC not being able to access data on the device and about installing some Mac OS X software.
After clicking the notification I can select the following options:
(Here's this menu in English: https://deviceguides.vodafone.co.uk/samsung/galaxy-j5-2016-android-6-0/connectivity/transfer-files-between-computer-and-phone/. It's on a J5 and not A5 because the only examples of it that I could find were from an earlier Android version which only had MTP and PTP available.)
After selecting "Prześlij obrazy" (was: "Prześlij pliki multim."):
After selecting "Podłącz urządzenie MIDI":
After selecting "Naładuj ten telefon":
After enabling usb debugging:
After selecting "Prześlij pliki multim.":
adb shellworksAfter selecting "Prześlij obrazy":
adb shellworksAfter selecting "Podłącz urządzenie MIDI":
adb shellworksAfter selecting "Naładuj ten telefon":
adb shellworksadb works consistently when it's enabled in the settings (and doesn't when it's disabled).
After rebooting debugging stays as it was.
Toggling debugging state in the settings doesn't mess with the usb connection mode. The phone simply reconnects in the same mode it was in, just with debugging state changed.
Overall debugging on/off is the only piece of persistent state I can see.
USB connection being in MTP/PTP/MIDI/Charging mode is an ephemeral state. It is maintained until either the phone is rebooted or the usb cable is physically reconnected (the default is MTP after either of the two occurs).
After
adb reboot recovery(or [power]+[home]+[vol-up] with the phone turned off or charging) I got a loading screen "Installing system update…". After a while it arrived at the "No command" screen. After [power]+[vol-up] I got the recovery menu (re-plugging the phone seemed to have done the trick at first, but I couldn't get it to work again):Plugging the phone in or turning it off while it's plugged in, after it was in recovery sometimes boots the phone into recovery again.
After selecting "Apply update from ADB":
adb shellgiveserror: closedAfter selecting "Reboot to bootloader" or issuing
adb reboot bootloaderthe phone just reboots into Android.After holding [power]+[home]+[vol-down] when the phone is off displays a warning about installing custom OSes.
[vol-down] cancels this and reboots the phone.
[vol-up], but also [home] or [power] start the download mode (Odin).
heimdall detectprintsDevice detected.adb devicesdoesn't list anything and neither does fastboot.Later, I've noticed 'Developer options' contain a separate USB mode switcher. It offers more entries than the notification that appears when you plug the phone in and it turns out they behave (to some extent) differently!
Here they are:
(the ones in Polish translate to "Charge this phone" and "Sound source" respectively)
Also, here's the same thing in English: https://youtu.be/joPcGu86UUU?t=60
When I plugged the phone in, MTP had already been selected:
After selecting "Naładuj ten telefon", it has simply disconnected and shown no further USB activity.
After selecting "PTP (Picture Transfer Protocol)":
After selecting "RNDIS (USB Ethernet)":
After selecting "Źródło dżwięku":
After selecting "MIDI":
and after switching debugging on, the phone stayed in MIDI mode:
This time after selecting "Naładuj ten telefon":
After selecting "MTP (Media Transfer Protocol)":
After selecting "PTP (Picture Transfer Protocol)":
After selecting "RNDIS (USB Ethernet)":
After selecting "Źródło dżwięku":
After selecting "MIDI":
The text was updated successfully, but these errors were encountered: