[kwlug-disc] Testing Android app on real phone

[William Park]

On 2025-10-21 21:44, Khalid Baheyeldin wrote:
> On Tue, Oct 21, 2025 at 12:47 AM William Park via kwlug-disc 
> <kwlug-disc at kwlug.org> wrote:
>
>     Finally, a closure.  I wrote up some notes on testing Android
>     phone using *ADB* and *scrcpy*.
>     https://opengeometry.github.io/NOTES/android/
>     Feedbacks are welcomed.
>
>
> Thank you.
>
> Did you test scrcpy as well?
> It looks like it has so many command options, per this page 
> <https://github.com/Genymobile/scrcpy?tab=readme-ov-file#user-documentation>.
Yes, scrcpy works as well.  All those options are about how scrcpy behaves.

> My use case is to control my phone from a larger screen and a proper 
> keyboard.
> I loath small screens and touch typing.
> But it seems to be overkill for such a limited use case.
You can increase the screen size on the desktop.  But, phone screen is 
already so tall, that there isn't much room to increase.

At least, on my Samsung A16 (cheapest in their lineup), I can use real 
keyboard/mouse.  Familiar "mouse pointer" shows up on phone screen, and 
you can click any button using mouse.

In the beginning, my focus was more on "automation", eg. sending key 
press (mostly) and mouse click.  So, I looked into making "programmable 
keyboard".  Just ssh into the board, and run command to send out key 
press out to the phone.  To the phone, it's just another keyboard.  But, 
I think, using ADB over network is better for Android phone.  It's 
1-step solution, whereas programmable keyboard is 2-step.

That said, this programmable keyboard is interesting and useful in many 
ways... :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20251022/562b5396/attachment-0001.htm>