Driver update depends on your OEM. Both ARM and Qualcomm send driver updates for their premium and upper highend Socs. The support reaching your phone is on the OEM. Google has started to push direct GPU driver updates starting with Pixel 10. So, hopefully others may follow too.
Usually GPU vendors (Nvidia, Intel, AMD) provide a way to download and install drivers manually (on Windows), including specific versions or older versions. Qualcomm is an outlier in this case.
Note that those drivers usually only work well in desktops, on laptops the GPU might have gone through OEM adaptations on the motherboard integration, and a driver from GPU vendors might have issues.
A common example is overheating, because the way the OEM has done their device isn't a setup that the driver knows about.
Which is why on laptops, the drivers if available have to be from the OEM themselves.
It might be more fair to say that there's simply no standard way to do power management for discrete GPUs in a laptop, or to integrate such power management with Windows and whatever power management it's trying to do. And the lack of a clear "right" way to do things means laptop OEMs use this area for product differentiation with their own shitty special sauce software and firmware hacks.
If installing drivers that come directly from NVIDIA onto a laptop can cause that laptop's GPU to overheat in the sense of getting so hot it fails to function properly or has degraded reliability, that's entirely NVIDIA's fault. If by "overheating" you just mean drawing more power and causing the fans to get louder than they would in an out of the box configuration, the blame for that should be shared between NVIDIA, Microsoft, and the laptop OEM, but you shouldn't blame the user for doing something that should work and would work if those three vendors could cooperate.
I primarily use Hacker's keyboard to use Emacs in Termux. Bluetooth keyboard is also an option. But, for some text editing sessions software keyboard is sufficient.
mozilla builds firefox for android (fennec). a perfectly functional browser.
Then they remove:
- dev tools (understandable, but it's weird because it works perfectly if you dont' remove)
- the ADDED code to create a list of white-listed extensions! And never updated the list in over a decade!
- they prevent you from accessing about:config
- they remove 80% of the settings from the settings screen.
- They disable user.js and user.css
- they add full google suit client library code when they only claim to use the screen cast (which do not require the full client, which is only needed if you also show ads from google network...)
- probably many more things
- the f-droid build just don't do any of that crap. simply builds and packages and distribute. a perfectly functional browser. With a fully verifiable build too! because you didn't add external binaries and undocumented steps.
Mainly block css. But, a better way to block media, CSS, scripts, frames in a fine grained domain basis--more complicated in ublock.
Also, limit cookies by domain. Certain websites(extremely rare ones) need 3rd party cookies to function.
