RYk that right?
RCoots phone had a 64 bit cpu
RAnd ran a 32 bit os because it didn't have enough ram to run 64 bit apps
RWhich leads to really bad performance
CDebian fully supports three ports to different flavours of little-endian ARM hardware:
The ARM EABI (armel) port targets a range of older 32-bit ARM devices, particularly those used in NAS hardware and a variety of *plug computers.
The newer ARM hard-float (armhf) port supports newer, more powerful 32-bit devices using version 7 of the ARM architecture specification.
The 64-bit ARM (arm64) port supports the latest 64-bit ARM-powered devices.
The ARM EABI (armel) port targets a range of older 32-bit ARM devices, particularly those used in NAS hardware and a variety of *plug computers.
The newer ARM hard-float (armhf) port supports newer, more powerful 32-bit devices using version 7 of the ARM architecture specification.
The 64-bit ARM (arm64) port supports the latest 64-bit ARM-powered devices.
LDoesn't pi zero run 32bit soc...?
C32 is useful for less demanding tasks
RIt uses an ancient cpu
RAlso only has half a gb of ram
RIt couldn't run a 64 bit os if the cpu supported it
Lfor the image https://www.debian.org/distrib/netinst
LPress on armel or armhf for 32bit..
RThe issue is, it ends up being MORE INTENSIVE because running 32 bit apps and os's on a 64 bit cpu means everything is emulated, which makes the experience slower and use more power.
RAll because you don't have enough ram
Cstill can handle the load
RIt's not faster
RIt's actually slower
RBecause it's emulation
Ci was able to listen to music on firefox while using geany (a ide), webcord and filezila at the same time
RWhich is exactly why arm32 is phased out
Cfaster than what?
RWow you were able to run 4 apps‽
Cat the same time without any lags lmao
RIts not faster than a 64 bit app or a 64 bit os
RShiver me timbers
Cwell ofc since theyre using more updated technologies
RNo, that's not why
Cmy new phone crashes x11 and freezes when i try to run vscode armcord and firefox at the same time
RIt's because all arm and x86 cpus from the past decade or 2 have been 64 bit. Running 32 bit shit on them makes them slower because they are emulated
RDon't act like your old phone was better in any way
RI literally own your old phone
RIt blows ass
RIt struggles to run spotify
Cit wasnt better but it didnt had as many issues at my new one tbh
Cmy new one cant even handle a anr
RYour just trying to justify why Google should continue to support a slower, outdated, and dead architecture for android apps and os's
Carm32 is still used widely
RNo, it's not
Cold raspberry pis use it
RYeah, old rpi
RWith even older cpus
RThe new rpi uses old cpus
RThat's how they are so cheap
RUse old chips
REven the pi 3 was 64 bit iirc
RThe pi os wasn't 64 bit, but you could install other os's that were.
RThey are old cheap and slow chips, so they source them for cheap.
RBut it works out, because they aren't made for using as a computer. Web browsing on a pi can be a pain.
Ccheap? theyre like 40$ for base model lmao
RThat's mega cheap
