Expert mode setup assistant doesn't see pairing code on Samsung

[jambl3r]

Have you checked if an issue already exists for this bug?

• Nobody else has reported this bug before

Have you tried restarting your device?

• I have tried restarting my device and that did not help

What happened that you did not expect?

Looks like Samsung has some slightly different wireless debugging screen so the accessibility service isn't matching the pairing code field to auto grab it, see this log

key_mapper_log_20251222-074159.txt

What did you expect to happen?

It would be nice if it worked on Samsung devices

What would the developer need to do to reproduce the bug?

No response

App version

4 beta 3 foss

Android version

android 12

Device model and manufacturer

Samsung M31

Extra info

• My device is rooted

[sds100]

This is an Android 12 samsung device so its probably different on newer versions as well. I won't be able to fix it unless I have that specific ROM with me. I've also noticed that on Android 16.1 on my Pixel it doesn't work anymore. This might be too hit or miss to get it working automagically

[jambl3r]

I don't know if we have to give up yet. It's a very powerful feature when it works and it's good secret sauce. We can have a look next week at what we can glean from the screen. I'll see if we can set up some emulators for different ROMs too

[jambl3r]

I don't think my laptop is strong enough to handle the emulator lol
In theory one could try to run the various settings APKs but I'm not convinced I'll be able to do it.
It's something we can do on a MediaMarkt trip

[sds100]

I guess whatever solution we come up with it will last for 6 months or so until phones or updated. We already disabled the auto navigating to Wireless Debugging on Xiaomi et.al because of a bug in their Settings app so that wipes out a significant percentage of the phones out there. There are just so many combinations of Android versions and ROMs that its a tonne of maintenance work or impossible to have a unified experience.

It might be better to refine the flow where it doesn't auto-click. Also if we ever make a tutorial for gaming mode it should be the same for (almost) everyone.

I didn't think this problem would be that bad, but now im having doubts considering Pixel Android 16.1 visually looks the same I wasn't expecting it to not work. Who knows what other quirks there will be

[jambl3r]

I have some hope that the detection just needs to be a bit smarter. I don't know how it works right now but for the pairing code its 6 numbers, somewhere on that screen, accessible with some number of intermediate interactions.

In the worst case if it does get defeated every 6 months hopefully we can get good at patching it up quick so its not too much of a chore

[sds100]

Just thought of a smarter/dumber solution... find the on screen coordinates of the 6 digits (which is possible), and tap there. Instead of interacting like with the "interact with screen element" action - using that is a losing battle.

[jambl3r]

Maybe it could be a fallback? It is certainly slower. Would you need to essentially screen record and run computer vision every frame or is it smarter than that?

[sds100]

the API gives me the on screen coordinates of a UI element. im going to test it now

[sds100]

Okay, that method won't work for what I was trying to do. The issue i was having on Android 16.1 is that the "pair device with pairing code" button was not being detected. The only reliable way to find the ui element would be to search for the text and then click it. But people have different languages, and the wording is probably different on various ROMs.

[jambl3r]

59% of devices have their device set to English, in fact 86% of users have their device set to one of 5 languages.
I'm not sure how different that string can really be. It wouldn't need to be a perfect match, just need to not have 'QR' in it etc

Getting the string pretty decently is easy if we set our own device language to that and then look at this screen

In Indonesian it's pretty easy to see, 'kode enam digit' or just 'digit' is pretty detectable.
'kode penyambungan' = pairing code

[sds100]

Okay, of all the options, this is the easiest to maintain and patch so lets go with that.