Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google activated battery saving mode on multiple phones, then rolled it back

reddit.com

Post reply on HN
Print view View original

181–190 of 202 posts

Re: Google activated battery saving mode on multiple phones, then rolled it back

#181

Post by okonomiyaki3000 »

icebraining wrote: post #83
okonomiyaki3000 wrote: post #53

I think Apple remotely activated battery killing mode on mine. The battery was already in bad shape but since this morning it's been ticking down like a clock. It's much worse than yesterday. Anyone else? Am I just paranoid? Seems like an odd coincidence.

How can it not be a coincidence? Even if Apple did add a battery-killing mode, why would they purposefully wait until this Android bug to launch it?

I was thinking it was more like they just announced new iPhones and now they're giving people a reason to upgrade.

Re: Google activated battery saving mode on multiple phones, then rolled it back

#182

Post by tmaly »

hellosputnik wrote: post #118
lalos wrote: post #65

We need more transparency from companies, this time it was a 'bug' that was visible to the end user (hey! who turned on power saving?). Would Google go public if they also develop a 'bug' that is not visible easily by the user or if it was not discovered by anybody but them? Like a 'bug' that changes certs temporarily to intercept your encrypted traffic or uploads random data elsewhere, etc?

You can avoid all of this by using an iPhone. Apple's business model does not involve ad revenue or data collection. Your data is collected but is used purely to improve the iPhone. Your data is intentionally obfuscated for privacy. For an example of Apple's strict policy, check out this article on Apple Maps: https://techcrunch.com/2018/06/29/apple-is-rebuilding-maps-f...

I like that I can put my IPhone in low power mode even if it is at 100 percent. I also like that I can turn off all notifications in one central place. This has helped me lower distractions from the phone. Previously I was on a Nexus 5. Upgrading to newer versions of Android always came with the possibility that my wifi would not work or my cell signal degraded etc.

Re: Google activated battery saving mode on multiple phones, then rolled it back

#183

Post by kalleboo »

jayd16 wrote: post #85

I'm taken aback by how many, even in this tech forum, seem surprised to learn that automatic os updates means settings can be updated automatically. Bugs are bad and all but I don't understand the "how could Google do this?!" questions. Am I missing something?

There's the difference between the possibility of a software update changing settings and "Google has a whole configuration management infrastructure deployed and active and phones polling for new settings so that one slip of a finger can change the settings on millions of phone by mistake"

Re: Google activated battery saving mode on multiple phones, then rolled it back

#184

Post by gcb0 »

craftyguy wrote: post #35
gcb0 wrote: post #21

Earlier quoted context omitted.

the irony that a product which top feature is literally "Does not run Google Android" serves their javascript from google cdn :) ...also the fact that they have boot up sound means that they are not focusing on user experience and needs, but on copying any and all features from the current phones :(

> they have boot up sound Where did you learn that? I 1) didn't think they did and 2) even if they did the bootloader should be user replaceable. I could be wrong though..

it was a category in their ring tones contest. they have three boot up sounds, which has absolutely no real use.

fun fact, it was originally included in older phones as a marketing gimmick, a way to generate more revenue. someone at nokia or siemens had the idea to sell it to operators the same way as an Ad spot is sold. telco operators paid manufacturers to have their jingle there instead. and in markets without buyers, they put in the manufacturer jingle as a placeholder.

Re: Google activated battery saving mode on multiple phones, then rolled it back

#185

Post by _emacsomancer_ »

muxator wrote: post #52
_emacsomancer_ wrote: post #49

Earlier quoted context omitted.

Without GApps?

Without gapps the phone is faster, and drains less battery. If you mainly use a browser (Firefox, hopefully) and some messaging & mapping apps, works great. If you want to use other apps, you'll have to do more testing.

Right. I know, and I run my device this way. But my point was just installing Lineage by itself doesn't free you from Google's clutches if you install GApps anyway.

Re: Google activated battery saving mode on multiple phones, then rolled it back

#186

Post by _emacsomancer_ »

ForHackernews wrote: post #116
_emacsomancer_ wrote: post #49

Earlier quoted context omitted.

Without GApps?

https://microg.org/

microG is indeed very cool. (though some apps stopped working with it in the past couple of months).

Re: Google activated battery saving mode on multiple phones, then rolled it back

#187

Post by mankash666 »

Dylan16807 wrote: post #142
mankash666 wrote: post #50

Earlier quoted context omitted.

Well beyond reason to assume something pedestrian for you - a developer - to be "reasonable skills" for the average Joe. Do you build your own car? Or bike? Or home? Or even mattress? All of these can be done with reasonable skills, they aren't because you pay for a finished product, in most cases, for the economy to remain productive. No one ever said 'reinvent the wheel' for making progress.

This entire post is a nitpick about a single word, with the intent perfectly clear, and you should be ashamed of that. Just pretend it says "It would take a tech enthusiast to install [...] but the OS once installed can be used by all".

You be ashamed of trying to shame strangers on the interwebs for talking freely!

There's plenty of benefits Google's product offers that lineage doesn't. The surprising thing is, this kind of parameter toggling (turning on battery saver in an OS update) typically happens in non-Google OS-es too. What are you even offering, other than rhetoric, by suggesting lineage as an alt? How does lineage prevent an OS update from toggling a feature - something put in source code.

Lies, damn lies

Re: Google activated battery saving mode on multiple phones, then rolled it back

#188

Post by ASalazarMX »

hellosputnik wrote: post #118
lalos wrote: post #65

We need more transparency from companies, this time it was a 'bug' that was visible to the end user (hey! who turned on power saving?). Would Google go public if they also develop a 'bug' that is not visible easily by the user or if it was not discovered by anybody but them? Like a 'bug' that changes certs temporarily to intercept your encrypted traffic or uploads random data elsewhere, etc?

You can avoid all of this by using an iPhone. Apple's business model does not involve ad revenue or data collection. Your data is collected but is used purely to improve the iPhone. Your data is intentionally obfuscated for privacy. For an example of Apple's strict policy, check out this article on Apple Maps: https://techcrunch.com/2018/06/29/apple-is-rebuilding-maps-f...

> Apple's business model does not involve ad revenue or data collection

Seeing how ads and analytics are so pervasive in the Apple app and music stores, they probably profit from ad revenue and data collection.

Re: Google activated battery saving mode on multiple phones, then rolled it back

#189

Post by helthanatos »

013a wrote: post #8
helthanatos wrote: post #3

Earlier quoted context omitted.

They can also delete media from your phone. Had a graphic video of that carnival ride breaking and killing someone and it was deleted...

Is this for real? Was it deleted specifically on Google Photos, with a local copy still available or possibly available if it hadn't already been cleared locally? Or was it a legitimate "reach into local storage and clear it"?

It was only local.

Re: Google activated battery saving mode on multiple phones, then rolled it back

#190

Post by icebraining »

okonomiyaki3000 wrote: post #181
icebraining wrote: post #83

Earlier quoted context omitted.

How can it not be a coincidence? Even if Apple did add a battery-killing mode, why would they purposefully wait until this Android bug to launch it?

I was thinking it was more like they just announced new iPhones and now they're giving people a reason to upgrade.

Oh, sorry, I didn't realize there were new iPhones just coming out.
Post reply on HN