I've been testing https://github.com/Genymobile/gnirehtet when I run the tests at home and maybe you @dpifke have other things we could try?
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Peter | T279572 Evaluate doing Android performance test using a Raspberry Pi | |||
| Resolved | • dpifke | T279584 Evaluate which reverse tethering solution we should use. |
Event Timeline
Comment Actions
Interesting. With my Pixel 3, I don't need any software to reverse tether. I just create a USB ethernet device on the computer to which it's connected (modprobe g_ether on a Raspberry Pi, if not already enabled via boot/cmdline.txt) and start a DHCP server on it, and the phone uses it if there's no wifi available.
From the phone's perspective, this is the same as if I had plugged an ethernet dongle into the USB-C port, which from a cursory Googling seems to be somewhat widely supported. (Android since version 5 supports wired ethernet, but it appears modern versions don't expose the settings screen for non-DHCP configuration.)
Other vendors may lock this down more, which may be why the software to which you linked is needed. I'll do some more research, and possibly pick up a refurbished Galaxy or other non-Pixel device for testing.
Comment Actions
Aha! I can try that, do you have exact instructions? Do you need to have the phones rooted for that?
Today we run Moto G4 and G5. G4 because of the old version of https://infrequently.org/2021/03/the-performance-inequality-gap/, I've been using Moto G5 because Mozilla uses it and contributed how to set performance governor and more tuning on a rooted device. They also use Pixel 2 so we could maybe use them too, but I haven't looked at the CPU performance.