101–110 of 370 posts
Earlier quoted context omitted.
That point is so weird: Why offer a "performance update" 1.5 years after the end of security updates?
Given the sudden urgency and pulling the old software, I'm assuming they're trying to avoid aging batteries exploding.
Can I submit a GPL request to Google to get the kernel source?
Hi, (soon to be ex) Pixel 4a user here. Regardless of why this update has happened, the way Google have went about this update is sketchy at best, and deceitful at worst. To be plain: this phone has been EOL for 1½ years now. This update has appeared out of the blue and specifically decimates the battery + charging capabilities. My most charitable view is that Google have found a major fault with the Pixel 4a battery…
Unlock the bootloader, then install LineageOS, MindTheGapps, and Magisk.
Once you have Magisk stabilized, install the Advanced Charging Controller, and configure it to halt charging at 80%.
That should solve your problems, and turn the updates back on. I don't think there is a way to make Google Pay work in this configuration, which is a drawback.
I can put all the URLs here if you ask.
Edit:
[I did not remember that Lineage hosts gapps images]
https://wiki.lineageos.org/gapps/
[IIRC, the APK is renamed to a ZIP and flashed with recovery, then name it back and install the app]
Am I the only one that had the immediate thought of "this seems intentional" when they read that they're offering the credit for a newer pixel?
Most believe that they're trying to prevent safety issues with overheating batteries. This update prevents the battery from being charged too much or too little.
* Send from my now charging 4a
Hi, (soon to be ex) Pixel 4a user here. Regardless of why this update has happened, the way Google have went about this update is sketchy at best, and deceitful at worst. To be plain: this phone has been EOL for 1½ years now. This update has appeared out of the blue and specifically decimates the battery + charging capabilities. My most charitable view is that Google have found a major fault with the Pixel 4a battery…
I am still on a 4a. I really hate how in subsequent generations, they faithfully cloned Apple's design decisions of removing ports and making the device gigantic. "For customers who are dissatisfied with iphones, Our product is a slightly different iphone-like device." I mean come on now, what the hell... About twice a decade google makes a good phone and the others are just iphone knockoffs
Earlier quoted context omitted.
This attitude (and the word "problematic") is so tiring. What is the actual problem with running it as your daily driver? What specific vulnerability are you actually concerned about? Unless there's something like an arbitrary code execution bug in one of the networking/radio stacks, "there aren't updates" is a statement with approximately zero useful information.
OK, let me google it for you: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-43096 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4377... https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4377... https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-49747 https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-49748 These are just the RCE bugs without user interaction that were fixed with the January up…
I know they pull firmware from disparate devices when possible.
Earlier quoted context omitted.
The software industry has known how to do this for a very long time, but some companies refuse to do it. You maintain a "sustaining" branch just for security and other legitimately urgent fixes, and a main branch for everything else. Users are nudged more strongly to apply the sustaining fixes and the main update branch should be optional. We have immensely powerful version control and branching at developers' dispos…
But it isn't this simple, because you wouldn't need a single "maintaining" branch. You would need one for each feature release that the user may stop at. So if you release the feature branch every 3 months after a few years you will have a dozen maintaining branches to backport fixes to, and in which to carefully test that the fix actually works. The problem is linearly worse if you release the feature branch more of…
Hi, (soon to be ex) Pixel 4a user here. Regardless of why this update has happened, the way Google have went about this update is sketchy at best, and deceitful at worst. To be plain: this phone has been EOL for 1½ years now. This update has appeared out of the blue and specifically decimates the battery + charging capabilities. My most charitable view is that Google have found a major fault with the Pixel 4a battery…
Unless your Pixel 4a is from Verizon (locked), keep it. Unlock the bootloader, then install LineageOS, MindTheGapps, and Magisk. Once you have Magisk stabilized, install the Advanced Charging Controller, and configure it to halt charging at 80%. That should solve your problems, and turn the updates back on. I don't think there is a way to make Google Pay work in this configuration, which is a drawback. I can put all…
That will reduce future wear, but won't suddenly make the battery better. If anything it'll make the battery even worse, at least in the short term.
Earlier quoted context omitted.
OK, let me google it for you: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-43096 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4377... https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4377... https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-49747 https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-49748 These are just the RCE bugs without user interaction that were fixed with the January up…
Just curious, does current LineageOS close these CVEs? I know they pull firmware from disparate devices when possible.