New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
never test it. But I think it's possible.
many guide in google. You can try and post here 🤣🤣
Most mediatek and qualcomm snapdragons will lose their shit if they would be ran at high utilization 24/7. Mobile phones just arent made for the environment. But could you? Sure so long as understand how its built and how to mitigate from the chip from blowing its balls (literally).
But should you? Nah. Find any other ARM64 processor.
Not a single reason you can’t.
Install Ubuntu Touch and you're good to go I guess.
until it's blown up your hands when you "Touch" it
Most middle~high-end phone wasn't support backported kernel was provided by ubuntu touch.
I tested on my Redmi 2 running PostmarketOS with some service with 70% CPU usage which kill my battery with less 1 weeks usage (it charging full-speed 24 hours) and it require me to edit kernel to make charging rate slow to level runnable without draining/charging any battery which too complicated.
And yes mobile not designed to using 24 hours, also not all phones have same durablity. You can save some precious times buying some SBC which mostly have designed for 24 hours usage.
You can, but I wouldn't recommend it.
Variants:
1. Write some server service in Java and install it on the phone (pros: minimal changes, cons: only your service, no nginx, docker, databases etc.)
Sideload "arch arm" (you can do it even without chroot), now you can have more services but running manually, not trough systemd. (pros: more services, default libc, cons: android still uses system resources, the only way to clean up system is reflash)
Modify firmware to skip the start of all android services only system initialization. Add your services to init.rc. May event bring arch arm for binaries and libs (kernel still android). (pros: you have all resources and can bring app trough pacman, cons: you need to manage system yourself as example call wpa_supplicant to connect to wifi)
I tried 3rd variant, but not for server, just test if android can run without java at all. You can and can even draw something trough /dev/fb0.
I still think is not good idea of reusing phones.
Root it and run a Linux distro using Linux Deploy and use as server or whatever.