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

91–100 of 202 posts

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

#91

Post by pjmlp »

rapnie wrote: post #67
Tharkun wrote: post #62

Earlier quoted context omitted.

We've had several FOSS based phones. The problem is that no one buys them, their finances dry up and the whole thing goes down the drain.

Isn't that a bit of a marketing issue as well? I am tracking development of Fairphone, puri.sm Librem5 and e.foundation (just released beta version, based on LineageOS). Do you have pointers to the FOSS OS'es you refer to?

- Maemo (2005)

- OpenMoko (2006)

- Symbian (2009)

- MeeGo (2010)

- Mer (2011)

- Jolla (2011)

- Tizen (2012)

- Ubuntu Touch (2013)

- Firefox OS (2013)

- Web OS (2013)

So it is a bit more than just lack of marketing.

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

#92

Post by Yetanfou »

muks wrote: post #16

After my Samsung Galaxy S7 phone started having hardware issues, I looked to see if a phone running open source software was available, one that also could run the Android apps I currently use. I've had sucess with LineageOS 15.1 on a Xiaomi Redmi Note 5 Pro (codename "whyred"). Unfortunately the phone's LTE bands don't support every country, but it works fine here in India. The phone hardware costs USD 210 and buys…

I'm also using a 'Whyred' (silly name but since Xiaomi used the model name 'Redmi Note 5 (sometimes followed by 'Pro' or 'AI', terms which have different meanings in different countries)' for several different devices it is better to be accurate and use the code name), it offers great hardware for its price (around $180 for the 4GB/64GB model on Aliexpress) and - just as important - runs for 7 days/15 hours of screen-on time on a single charge. I'd just add that once you unlock the bootloader (which can be done in Linux using the java-based MiUnlocktool [1]) you can also de-fang MIUI by disabling all the intrusive bits, installing a different launcher and configuring iptables. Turn on the firewall log to see what tries to get through, you'll notice the thing trying to establish XMPP connections to some Xiaomi-owned domains. After disabling most of Xiaomi's 'services' the log stays empty without anything of value having been lost. This is a good compromise for those who'd rather use stock firmware, albeit de-bloated.

[1] http://xiaomitool.com/MiUnlockTool - make sure to run it on a 64bit machine as the included fastboot binary doesn't work on 32bit installations

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

#93

Post by A2017U1 »

krn wrote: post #43
9935c101ab17a66 wrote: post #20

Earlier quoted context omitted.

Fully aware this might be a silly question, but why do they make you wait, and why does the time period vary so greatly?

Xiaomi temporarily locks the bootloader to prevent third-party Chinese retailers from bundling malware and adware with its phones sold on the international market[1]. [1] https://www.xda-developers.com/xiaomi-anti-rollback-protecti...

Which is hilariously dumb because now 3rd party retailers are the go to source if you want to buy a Xiaomi with unlocked bootloader rather than waiting a month . It's creating more business for the people they are supposedly trying to stop.

Also none of the stock Android phones they sell have a wait time for bootloader unlocking, it's only the ones with their own os MIUI

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

#94

Post by 9HZZRfNlpR »

saagarjha wrote: post #86
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?

OS updates should not update your settings. They can update system frameworks, but they shouldn't just randomly change the preferences you have set.

OP meant why tech savvy people are surprised the Google has the possibility to do such things even though it's obvious they have full control over your operating system.

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

#95

Post by pjmlp »

hardwaresofton wrote: post #79
Tharkun wrote: post #62

Earlier quoted context omitted.

We've had several FOSS based phones. The problem is that no one buys them, their finances dry up and the whole thing goes down the drain.

I'm a broken record at this point, but I'll say it again until I'm convinced I'm wrong -- FirefoxOS did great but was tragically mishandled. I'm 100% a FFOS stan ( https://en.wikipedia.org/wiki/Fan_(person)#%22Stan%22_fans ) but it absolutely could have (and did) work -- they just fumbled the execution and 0 executives took responsibility (as per usual). While I appreciate Mozilla's recent exploits like the IoT Gatew…

The fact that Google has brought Android to ChromeOS and not the other way around, that Fuchsia is based on Flutter and not ChromeOS UI, and all the corpses of Web based OSes all the way back to Web Widgets Runtime on Symbian is quite telling about the performance of web UIs on phone hardware.

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

#96

Post by TorKlingberg »

saagarjha wrote: post #86
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?

OS updates should not update your settings. They can update system frameworks, but they shouldn't just randomly change the preferences you have set.

It is a bug that can easily happen by mistake, especially if the update changes how preferences are stored in any way.

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

#97

Post by Freak_NL »

austhrow743 wrote: post #57
some_account wrote: post #41

Earlier quoted context omitted.

I think people with a Google phone should just implant a chip in their arm, reporting to Google. It's basically the same thing, and you can view your body information on a Google dashboard and get Google advice on health care, along with a Google map to get there.

Many would and will when it's available.

Except for the 20% of users who feel that Google is not to be trusted and implant an Apple iChip for the premium experience.

In all seriousness, the percentage of people willing to forego using an Apple or Google smartphone (or any smartphone) to uphold at least some semblance of (digital) control over their life sometimes feels so low that it should be called a permillage.

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

#99

Post by SmellyGeekBoy »

ggm wrote: post #36

I don't see WHS the the big issue is. Yes my phone went to red battery low power mode. So what? What aspects of this alter contract between me and Google over automatically applied updstes? I gave can implicitly ages ago. If they involuntarily disabled battery saving and caused me to loose service or drain and reduce battery life i could see an issue. Truly, bemused at the hate. What did you think the t&c said when y…

I think the hate is directed more at the general concept here rather than the specifics. What if they'd pushed out an update that silently broke SSL, made all your Google Photos public or started calling people at random, for example? This particular bug is pretty innocuous but the fact that it's possible to push out very obviously broken updates like this (and only admit to it when they're publicly called out on it) could lead to all sorts of issues. It's not like these users were opted in to some kind of "insider" or "testing" builds, after all.

This should be the point where I point out that I installed LineageOS for this very reason but even they do stupid stuff, their "April Fools" update this year, for example: https://www.androidpolice.com/2018/04/05/dont-freak-lineageo...

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

#100

Post by enriquto »

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?

This happens in ubuntu linux actually. Every now and then, an update changes my configuration of systemd without asking.
Post reply on HN