tech4bot
Joined 5 months ago
Joined 5 months ago
I usually prefer cheap devices for travel, because you never know when something gets lost, broken, or stolen. This tablet fits that well, Android for the kids or for testing an app, and Linux when I need something more specific.
I did mention this in the license section, last line of the README.
Performance is usable, especially compared to stock Android, because there is less background bloat. It’s fine for terminal work, light browsing, VS Code, and small experiments.
If you want you can check my video: https://youtu.be/DbX13_mahKc
I completely agree, this is not the place to let AI blindly edit kernel code. The useful approach is to use it conservatively: understand the error, compare against downstream sources, propose a small patch, review it, test it, and then move one step further.
I’d be happy to work together on an article or guidance document, where to start, how to approach debugging, what to never let AI touch blindly, and how to build confidence step by step. That could help others avoid a lot of mistakes and maybe give a second chance to other devices.
On the units I tested, the board says: RK3562-v1.0 2024.06.28.
This is the listing I used, but it is currently out of stock:
The tablet is from around 2023, with later revisions around 2024. My point was that this kind of older cheap hardware is already out there in people’s drawers.
If a device can boot from SD and the hardware can be documented enough, it becomes a good candidate for reuse instead of becoming e-waste.
In the DTB, I also added eMMC support, so you have full access to it from Linux. This means you can dd everything to the eMMC if you want.