Does not work on Samsung w/ OneUI 3.0 / Android 11

[depau]

Forwarding here from EtchDroid/EtchDroid#117

Problem

The affected users seem to be running Samsung's downstream ROM "OneUI" version 3.0 or later. I was able to borrow a devices with OneUI 1.0 and it doesn't seem to be affected.

I'm currently testing on a device with OneUI 2.1, though I'm having issues with wireless ADB and I will have to return it soon.

EDIT: I didn't manage to connect to ADB over Wi-Fi but EtchDroid is working fine on it.

Expected behavior

Actual behavior

No user provided a logcat but the behavior seems the same as when the app is closed, then re-started with the same USB drive selected without unplugging and re-plugging the USB drive (ANR then timeout).

EtchDroid hangs after the USB drive selection, which is when - after devices are discovered by libaums - EtchDroid tries to open it and fetch the block device driver - it usually hangs on the first SCSI command.

Stacktrace of Excpetion

Affected users: please provide.

Code where problem occurs

[magnusja]

Interesting, I read the thread in EtchDroid/EtchDroid#117 but I am as confused as you probably are.

I am not sure if we are missing something to make this fully compatible with Android 11?

I am assuming you are using the libusb communication? Maybe you want to package an app for the guys in EtchDroid/EtchDroid#117 using the vanilla Android USB API and see if that makes any difference?

[depau]

I am assuming you are using the libusb communication? Maybe you want to package an app for the guys in EtchDroid/EtchDroid#117 using the vanilla Android USB API and see if that makes any difference?

That's not a bad idea actually, I didn't think about it. No one provided logs though, it's hard to tell what's breaking exactly.

I just posted this here hoping you have or know someone who has a recent Samsung, it's hard to borrow devices around these times :)

[shirt-dev]

I am assuming you are using the libusb communication? Maybe you want to package an app for the guys in EtchDroid/EtchDroid#117 using the vanilla Android USB API and see if that makes any difference?

That's not a bad idea actually, I didn't think about it. No one provided logs though, it's hard to tell what's breaking exactly.

I just posted this here hoping you have or know someone who has a recent Samsung, it's hard to borrow devices around these times :)

It recently worked for me on my Samsung Galaxy S20 FE running OneUI 3.0 with no issues. If you need any testing let me know.

[Torris-Yin]

I am using MIUI12 (Android 11) in Redmi Note 10 Pro. This software cannot function well, too. It always reports an error and then screen will turn to black. I cannot even exit the software.

[Moohee-yll]

I was very troubled with the same problem. I found this is caused by function: claimInterface (UsbInterface intf, boolean force).

• If I let force == true (just like in libaums), then the crash appeared.
• If I let force == false, this problem disappeared but the return value of "claimInterface" is false, so I was unable to continue the next step.

So I this the key point is claimInterface( ).But I don't know how to do.

[steroidraging]

Are you trying this with or without OTG storage enabled in settings?

Something I noticed, using my OnePlus Nord N10 5G is that for some reason with that enabled as you would typically need for the phone to notice the drive right, it actually throws off EtchDroid on my device.

One day I tried EtchDroid and actually had forgotten to enable that option in System Settings and even tho most apps won't even recognize the drive without that enabled, it was the ONE thing that actually helped EtchDroid to fully complete the writing of the img successfully.

So my suggestion is to play with option, if you haven't enabled OTG Storage in your device settings I know most other apps don't even recognize my drive, so try to do so and if you have been enabling that option then it's probably the same issue I had, turn that option off and see if EtchDroid works then as it did for me.

One last thing, I have a drive with two connection types, USB C and on the other side USB A. Now for some reason when I use that drive and plug it in directly using the USB C side of my drive it simply doesn't work at all.

Yet if I use an adapter to plug into my phone and convert the USB C port to USB A and I use the USB A side of my drive it seems to work fine, which is super weird and I can't wrap my head around but yea....