- 2 Posts
- 5 Comments
5·1 month agoOh yeah. My initial plan was to install termux on it and use it as a server for a simple webpage I wanted to make, but the official rom i had was 32bit and the newer termux releases only support 64bit os.
I was going to give up, but while digging for more info I found out that for some reason the chip on my moto g4 was 64bit but not the OS. So I searched in the depths of the xda forums for a 64bit rom, which resulted in way too many dead links and dubious sources. Ended up using some obscure anime themed custom rom that crashed whenever I wanted to open the camera or use the flashlight BUT, it installed and ran termux nicely.
Overall I got what I wanted, but there wasn’t any good quality rom I could find as they all had some sort of flaw. Hope you get better luck though! Those phones are still perfectly usable if not for lack of software support
For the moto E4, Motorola has a guide in their support site to unlock the bootloader. I used it to be able to flash a 64bit rom for my moto g4 plus and the process was pretty straightfoward, although you do need a pc to use the adb command line tool.
Kinky cazzu 😈
1·2 months agoI know it is an old post, but I have the same cpu in my hackintosh and also encountered this same error, but later on fixed it! Turns out I was following the instructions of coffee lake cpus instead of kaby lake (very intuitive naming scheme, intel) for the config.plist. If you’re still interested I can share you my EFI folder, see if you can fix the error
When an app supports linux, it can do so by either:
or
These last ones are sandboxed environments. That means they have their own dependencies isolated from your system, so they dont have to deal with every distros pecularities at the cost of using more storage space. This is very useful for developers and in your case benefitial for the user because you can have both steam and zoom via flatpak on mint, arch or any obscure distro that has flatpak available, without any major problems.
Edit: Formatting