reverse engineering a proprietary UART protocol
This sounds cool and all but then
Turns out it was just standard 8N1 115200-baud UART.
I didn’t see any mention of this proprietary UART protocol in your blog and the GitHub project looks like it was as simple as reflashing the onboard ESP32 once everything is wired correctly?
Did they even resolve the issues with the Rust implementation of coreutils?
It’s still there in there latest Android 16 builds
Isn’t that an off the shelf part?
https://www.seeedstudio.com/XIAO-7-5-ePaper-Panel-p-6416.html
You might have used Heimdall, https://github.com/Benjamin-Dobell/Heimdall, the open source Odin alternative 😉.
Or get it for free by downloading the release APK from the GitHub repository 😉
At least the app option persists between system updates 😉
Probably because it still uses the android camera API to do so rather than directly access /dev/video0.
I’m sure it is possible to add a video capture to the API 😉
I guess you never heard of cPLA 😉
Pretty solid how to by James TDG 😉 Louis shouldn’t be given the credit here
Maybe there want to be a scam baiter like Kit Boga 😉
Do you see anything in logcat that looks sus when you insert the card? The logs might give some extra details.
Maybe things at Meta have changed after their “year of efficiency” but week one would be orientation and the start of boot camp and he wouldn’t normally already be on a team this soon. I’m calling BS and taking this as an amusing work of fiction.
Since I’m into 3D printing, I know of this project: https://github.com/gaifeng8864/klipper-on-android
It allows an android device to run a printer that uses the klipper firmware.
Can you link to that line in the code? I’m not seeing it, nor am I seeing the Internet permission being declared in AndroidManifest.xml
It’s easily pronounceable. It’s similar to saying “lick nuts”
Nigeria Launcher 😲
KDE connect can connect to another android device that is also running it and on the same network.