181–190 of 370 posts
Earlier quoted context omitted.
Why go all through that pain when graphene OS gives you a straightforward install?
Because the 4a is on extended support, is not recommended, and cessation can happen any time now? https://grapheneos.org/faq#supported-devices
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
They used to have a really good human factors/ui team. I remember Bruce Tognazzini and reading his blog.
https://en.wikipedia.org/wiki/Bruce_Tognazzini
I think I noticed around ios 7 things were getting bad. buttons didn't look like buttons, on-screen controls started being hidden, and form trumped function. Then like you said, ports disappeared and to me "do the wrong thing correctly" started winning.
but the worst thing is that apple sets an example. The same "simplify for sales, but not usability" technique has happened to countless other products in many industries. all laptops have elegant looking keys that have no curve to fit and center your fingers. Tesla cars have a pleasing-looking design, but when you drive them, you can't lean on the touchscreen to hit targets, you don't have drive selection or turn signal stalks to help you get into a parking space easily, and "elegant simplicity" is "cost cutting for the peons".
sigh.
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…
There is no way Google is making software update plans based on the revenue opportunity for breaking phones that are already 2 years past end of life. The numbers just don't make sense. Users who love 5-year-old phones can easily get a cheap used phone, which are in abundant supply.
Earlier quoted context omitted.
If you're reversing this: I was curious if Google determines if your device is "affected" using the phone's serial, or the battery's serial. I've seen reports that people who replace the battery manually outside of the program still experience diminished performance. But of course that could just be because they replaced their defective battery with another defective battery.
I'm going through the kernel with Ghidra but not very good at it and not having much luck. I do have an idea about what it's checking to determine if a battery is affected, but I don't have enough data yet to know if it's just a coincidence.
Earlier quoted context omitted.
If you own a device, you're entitled to a copy of all GPL software that came with it, including some build tools. However, if the diminished battery performance comes from some kind of firmware update for an embedded microcontroller, you're probably out of luck there, unless that controller also runs GPL software. It's possible the changes you're looking for are already listed on one of these repos: https://android.g…
I looked through all the sunfish repos first, which is how I found this: https://android.googlesource.com/device/google/sunfish-kerne... But apparently sunfish-kernel only contains binaries. Given there's an update to Image.lz4, that seems there's an update to the kernel. I also compared the binary to the previous version and found some new strings possibly related to battery charging profile. Next I checked out the…
Android's source code is a maze of branches and tags, unfortunately. The change can have been made in the generic cross-device kernel tree, or it could've been a separate module, or it could've been a binary.
One thing you could consider is checking out the kernel for a project like LineageOS: https://github.com/LineageOS/android_device_xiaomi_sm6150-co... They usually pull+filter changes from upstream. For instance, these changes may be of interest: https://review.lineageos.org/c/LineageOS/android_device_xiao... https://review.lineageos.org/c/LineageOS/android_device_xiao... These kernels are used for a variety of devices with similar hardware, so not all changes have anything to do with the Pixel 4a, but it could prove useful in your search.
There's a nice video about this from Louis Rossmann [1] that talks about this in detail and tries to find some reasons for it, and he seems to suggest that the update was never about improving the battery life as in getting more usage per charge out of the battery, but improving it as in limiting the battery full charge capacity to minimize potential problems with it, because he (and others) assume that they identifi…
Earlier quoted context omitted.
This works until you start attending events that require you to present your cell phone for entrance
What? For what purpose? I've never heard of or encountered this.
In this case, if you don’t have a phone that can display Ticketmaster’s code, you’re just SOL, since they decided to break being able to just print out your code.
It has worked for 3+ years and held a charge for 2-3 days easily until the other week when they pushed the battery patch. Now it dies in a few hours with light usage.
I asked Google support on what will happen if I get a battery replacement and it's still draining fast. They won't answer.
Google reps at a repair center said a battery replacement is unlikely to fix the drain issue since the drain behavior is attached to an OS update you can't opt out of.
This is really frustrating to be ignored by Google after they essentially bricked a fully working device that I paid for.
This is a type of move where I'm tempted to de-Google myself over this, including deleting my YouTube channel with 20k subs that I've been regularly posting to for almost a decade.
My whole business (selling courses and contract work) depends on SEO from Google and YouTube and I'm close to saying fuck it and destroying all of that out of principle on how poorly they are treating folks over this issue. I haven't made that decision yet but it's close to be honest. Close enough that I'm openly posting this message.
Earlier quoted context omitted.
This comment equates Android with Google phones for some reason. The complaints have nothing to do with Android — side loading is light years ahead of Apple (and third party application stores can finally automatically update applications). Call recording works fine on my friend's Xiaomi 14T (I think) that he bought just a couple of weeks ago, and it works fine on my own device that's on latest Lineage (Android 15).…
I have a very small pool of Androids I consider. Pixels maintain a strong security model (similar to what iPhones have), and they allow you to re-lock the bootloader after installing a non-stock OS. It's between a Pixel, or a FairPhone. I liked Lineage, but an unlocked bootloader is a security non-starter for a device that's so personal and vital. For those using the stock OS, Googles are nice because you "only" have…
