You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support for Older Android Versions (Android 7 ) #73
I love your idea bro and i want to use it myself but majority of the old phones in normal homes run either Android 8 or below and the new ones ( android 13,14,15,16,17) are currently in use.
How could PhoneBox help?
No response
Data and privacy
No response
Contributing
I'd like to build this myself (please read CONTRIBUTING.md and wait for a go-ahead on larger features)
Thanks! You're not the only one asking: #65 lowers the minimum to Android 7, and with it the app builds and passes Android's API checks. What's still unknown is whether the panel runs well on the WebView those phones have (the panel uses fairly recent browser features, and Android 7 phones can't get the newest WebView).
To find out, it would help a lot if you could tell me which phone(s) you'd use: the model, the Android version, and the Android System WebView (or Chrome) version from Settings › Apps. Once there's a build for Android 7/8 to try, I'll post it here.
Thanks, that's a good test phone: on Android 7 the WebView is provided by the Chrome app, and Chrome 119 supports everything the panel uses.
There's a test build in #81 now: minSdk 24 (Android 7.0), with the two places that needed newer Android APIs fixed.
Download:phonebox-apk. You need to be signed in to GitHub. It is a zip that holds app-debug.apk.
Install the app:adb install app-debug.apk, or copy it to the phone and open it after allowing installs from that app.
Computer: install the agent from the latest release. On Windows the quickest way is irm https://raw.githubusercontent.com/ersinkoc/phonebox/main/setup.ps1 | iex after #80 is merged; until then, unzip the release.
Things to try:
Panel rendering. Does it start and look right? A screenshot would help, and also a note if a yellow "WebView is too old" bar appears.
USB. With USB debugging on, plug the phone in. Does the panel connect, and does the phone wake when plugged in?
Wi-Fi. In the agent's settings, under General › Wi-Fi & Tailscale, use Pair a phone over Wi-Fi and scan the QR code with the phone. Does it pair, and does the panel keep working after you unplug the cable?
Touch. Do swiping between pages and the haptic feedback on taps work?
Before you test:
This is a debug build, signed with a different key than the releases. Over USB the agent will try to update the phone app to the release version; that fails on Android 7 and leaves the test app as it is, so you can ignore that message.
If Android 7 support is released later, uninstall this test app before installing the release.
What works:
Touch
Panel Rendering
adb installation
What doesnt work:
Terminal button ( I am on windows 10 right now but will test on Arch later if you have a pkg for that)
Installation in phone via its own package manager
PS My phone doesn't have any WiFi debugging options and it connected without it ( via QR code option), It could be that the WiFi debugging option were implemented differently in later versions or always active with developer options enabled in older Android versions.
Also can you mention me as a tester or like for the formalities i am trying to build a portfolio on my github. It would be very nice of you
Thank you, this is exactly what was needed, and the screenshots help a lot.
Credit: you're now in a new Thanks section of the README and in the changelog entry for Android 7 support (#81). Both go live when #81 is merged.
Terminal button: on Windows the default Terminal shortcut starts Windows Terminal (wt.exe). Windows 11 includes it, Windows 10 doesn't. #100 makes it fall back to PowerShell when wt.exe is missing. On Linux the default is x-terminal-emulator, which only Debian and Ubuntu have, so the same PR falls back to $TERMINAL or the first installed terminal (GNOME Console, Konsole, Alacritty, kitty, xterm …). For Arch, use the linux-x64 agent zip from the releases (there's no AUR package yet), or curl -fsSL https://raw.githubusercontent.com/ersinkoc/phonebox/main/setup.sh | bash.
You can also change it yourself right now: in the agent's settings, edit the Terminal shortcut and set its command to powershell.exe or cmd.exe.
Installing from the phone's package installer: what exactly happened? For example:
"App not installed";
"There was a problem parsing the package";
the installer didn't open at all.
Also: was the app already installed through adb when you tried? The download from the Actions page is a zip with app-debug.apk inside. Android can't install the zip itself, so it has to be extracted first.
Wi-Fi: right, nothing more is needed. QR pairing doesn't use Android's wireless debugging; the app connects to the agent over your network by itself. Wireless debugging only matters for adb over Wi-Fi.
Both will be in the next release. I'll keep this issue open until that release is out, and until we know what went wrong with installing through the phone's package installer.
The thing is that the package installer goes on forever ( more like 15 minutes), and surprisingly doesn't throw any error, almost like waiting for something. Moreover I think that adb just brute forces it.
About the fallback to powershell even that didn't open could be system specific but I will dig more into it.
0.9.11 is out: the regular release APK now installs on Android 7.0+, and it includes the Terminal fallback.
The release APK is signed with the release key, unlike the test build from #81. So first uninstall the debug build (adb uninstall net.oxog.phonebox.deskpanel), then install PhoneBox-0.9.11.apk. If installing from the phone's own package installer still fails with this APK, please send the exact message.
I tried the new release it works, the installation is only going through adb, while the internal package installer is still stuck at this after 40 minutes.The installation isn't failing and it throws no error, but at the same time it doesn't complete the whole process, I will try to look into it.
Your screenshot didn't finish uploading (the comment shows "Uploading …"). Could you attach it again?
The stuck package installer: an install that hangs without an error usually means Android's installer is waiting on something outside the APK. On the same APK, adb install skips that step. To find out what it waits for:
Connect the phone with adb and run adb logcat -c, then adb logcat | grep -i -E "PackageInstaller|PackageManager|verif".
Start the install from the phone and wait about a minute.
Paste what the log shows.
Two common causes you can check before that:
Google Play Protect scanning the app: turn off Play Store › Play Protect › Scan apps for the install, then turn it back on.
The file manager that opens the APK: try opening it from Chrome's Downloads instead.
The phone's make and model would also help, since some manufacturers ship their own installer.
Changelog: 0.9.11 is out, so I'll leave its entry as it is. Wireless debugging is an Android 11 feature, but PhoneBox doesn't use it. Pairing over Wi-Fi works on Android 7 once the app is installed, however you installed it.
I don't know why but it's now installing correctly with the package manager of my phone, must be some temporary glitch. I tried to reproduce the glitch but was unable to seems that we are fine for now.
Thanks for checking. If the package installer hangs again, the logcat steps above will show what it waits for; please open a new issue then. And thanks again for testing Android 7 support: it shipped in 0.9.11, with your credit in the README.
Activity
ersinkoc commentedon Nov 15, 2026
Thanks! You're not the only one asking: #65 lowers the minimum to Android 7, and with it the app builds and passes Android's API checks. What's still unknown is whether the panel runs well on the WebView those phones have (the panel uses fairly recent browser features, and Android 7 phones can't get the newest WebView).
To find out, it would help a lot if you could tell me which phone(s) you'd use: the model, the Android version, and the Android System WebView (or Chrome) version from Settings › Apps. Once there's a build for Android 7/8 to try, I'll post it here.
anandyakshit commentedon Nov 15, 2026
OPPO A71 , Android 7.1.1 ,and Chrome verion 119, i can be the beta tester i dont mind,
ersinkoc commentedon Nov 15, 2026
Thanks, that's a good test phone: on Android 7 the WebView is provided by the Chrome app, and Chrome 119 supports everything the panel uses.
There's a test build in #81 now:
minSdk24 (Android 7.0), with the two places that needed newer Android APIs fixed.Download:
phonebox-apk. You need to be signed in to GitHub. It is a zip that holdsapp-debug.apk.Install the app:
adb install app-debug.apk, or copy it to the phone and open it after allowing installs from that app.Computer: install the agent from the latest release. On Windows the quickest way is
irm https://raw.githubusercontent.com/ersinkoc/phonebox/main/setup.ps1 | iexafter #80 is merged; until then, unzip the release.Things to try:
Before you test:
Thanks a lot for testing!
anandyakshit commentedon Nov 16, 2026
What works:
Touch
Panel Rendering
adb installation
What doesnt work:
Terminal button ( I am on windows 10 right now but will test on Arch later if you have a pkg for that)
Installation in phone via its own package manager
PS My phone doesn't have any WiFi debugging options and it connected without it ( via QR code option), It could be that the WiFi debugging option were implemented differently in later versions or always active with developer options enabled in older Android versions.
Also can you mention me as a tester or like for the formalities i am trying to build a portfolio on my github. It would be very nice of you
Thanks
I will attach the screenshots after this comment
anandyakshit commentedon Nov 16, 2026
Android 7: docs, setup checks and credits; cut-out theme is values-v28
ersinkoc commentedon Nov 16, 2026
Thank you, this is exactly what was needed, and the screenshots help a lot.
Credit: you're now in a new Thanks section of the README and in the changelog entry for Android 7 support (#81). Both go live when #81 is merged.
Terminal button: on Windows the default Terminal shortcut starts Windows Terminal (
wt.exe). Windows 11 includes it, Windows 10 doesn't. #100 makes it fall back to PowerShell whenwt.exeis missing. On Linux the default isx-terminal-emulator, which only Debian and Ubuntu have, so the same PR falls back to$TERMINALor the first installed terminal (GNOME Console, Konsole, Alacritty, kitty, xterm …). For Arch, use thelinux-x64agent zip from the releases (there's no AUR package yet), orcurl -fsSL https://raw.githubusercontent.com/ersinkoc/phonebox/main/setup.sh | bash.You can also change it yourself right now: in the agent's settings, edit the Terminal shortcut and set its command to
powershell.exeorcmd.exe.Installing from the phone's package installer: what exactly happened? For example:
Also: was the app already installed through
adbwhen you tried? The download from the Actions page is a zip withapp-debug.apkinside. Android can't install the zip itself, so it has to be extracted first.Wi-Fi: right, nothing more is needed. QR pairing doesn't use Android's wireless debugging; the app connects to the agent over your network by itself. Wireless debugging only matters for
adbover Wi-Fi.Terminal shortcut: fall back when wt.exe or x-terminal-emulator is mi…
Android 7.0+ support (minSdk 24) (#81)
ersinkoc commentedon Nov 16, 2026
Merged:
Both will be in the next release. I'll keep this issue open until that release is out, and until we know what went wrong with installing through the phone's package installer.
Release 0.9.11: Android 7+, raw-input shortcut keys, Terminal and set…
anandyakshit commentedon Nov 16, 2026
The thing is that the package installer goes on forever ( more like 15 minutes), and surprisingly doesn't throw any error, almost like waiting for something. Moreover I think that adb just brute forces it.
About the fallback to powershell even that didn't open could be system specific but I will dig more into it.
PS.
Thank you for the credit.
anandyakshit commentedon Nov 16, 2026
Also you forgot to mention in the Change log that Android 7 gets the app installed via adb for now and that WiFi debugging is not available.
ersinkoc commentedon Nov 16, 2026
0.9.11 is out: the regular release APK now installs on Android 7.0+, and it includes the Terminal fallback.
The release APK is signed with the release key, unlike the test build from #81. So first uninstall the debug build (
adb uninstall net.oxog.phonebox.deskpanel), then installPhoneBox-0.9.11.apk. If installing from the phone's own package installer still fails with this APK, please send the exact message.anandyakshit commentedon Nov 16, 2026
I tried the new release it works, the installation is only going through adb, while the internal package installer is still stuck at this after 40 minutes.The installation isn't failing and it throws no error, but at the same time it doesn't complete the whole process, I will try to look into it.
ersinkoc commentedon Nov 16, 2026
Thanks for testing 0.9.11. Good to hear it runs.
Your screenshot didn't finish uploading (the comment shows "Uploading …"). Could you attach it again?
The stuck package installer: an install that hangs without an error usually means Android's installer is waiting on something outside the APK. On the same APK,
adb installskips that step. To find out what it waits for:adband runadb logcat -c, thenadb logcat | grep -i -E "PackageInstaller|PackageManager|verif".Two common causes you can check before that:
The phone's make and model would also help, since some manufacturers ship their own installer.
Changelog: 0.9.11 is out, so I'll leave its entry as it is. Wireless debugging is an Android 11 feature, but PhoneBox doesn't use it. Pairing over Wi-Fi works on Android 7 once the app is installed, however you installed it.
anandyakshit commentedon Nov 16, 2026
I don't know why but it's now installing correctly with the package manager of my phone, must be some temporary glitch. I tried to reproduce the glitch but was unable to seems that we are fine for now.
ersinkoc commentedon Nov 16, 2026
Thanks for checking. If the package installer hangs again, the
logcatsteps above will show what it waits for; please open a new issue then. And thanks again for testing Android 7 support: it shipped in 0.9.11, with your credit in the README.