3 ms·

Still no word on iMessages in the Cloud. I'm curious how the functionality of turning off the battery saving feature will work. Either a.) the phone constantly

by wycy 9y ago

Still no word on iMessages in the Cloud. I'm curious how the functionality of turning off the battery saving feature will work. Either a.) the phone constantly turns off and is unusuable, proving Apple did the right thing in the first place, or b.) the phone continues to work as it did when it was new, proving Apple lied.

taf2 9y ago
Or c.) an engineer spent weeks after news broke looking into issue again and found a better solution...
dusing 9y ago
It is back in 11.3 - when you first launch messages it even asks you to turn it on.
Yetanfou 9y ago
For Apple to do the right thing they'd have to issue a blanket free battery swap on all affected iDevices or maybe even a device swap to a model unaffected by this 'design problem'. I can simulate the problem these devices have rather easily on my own phone, a 2011-vintage Motorola Defy. The thing was first sold as having an '800 MHz' SoC, a later model (Defy+) supposedly sported a '1000 MHz' SoC. In reality the hardware did not change all that much between those releases except for the inclusion of a high-capacity battery. The clock rate is software-defined and can be changed more or less at will. As I was one of the developers to work on porting newer releases of Android (in the guise of Cyanogenmod) to this platform I had access to a number of these devices. All of them ran without problems at the standard clock rates of 800MHz and 1000MHz, most could be overclocked to 1.1GHz. Beyond that clock rate things started to look different with some devices experiencing sudden reboots when called or in other 'active' situations. The higher the clock rate, the more devices would start failing. On the other hand, some of them could run at 1.3GHz without problems, this includes the one I'm still using. It is now almost 7 years old but still works fine on its original battery. While battery runtime has gone down from about 5 to 3 days it still works without sudden reboots. If Motorola had clocked the Defy to 1.2GHz from the outset they'd have been in a similar situation as Apple is now with some users complaining about their devices rebooting spontaneously. They did not do so, instead they marketed the device on other features (being waterproof and rugged and such). Apple on the other hand did and marketed their devices as being 'faster than ever', i.e. they deemed the instability caused by the overly high clock rate a defensible trade-off.

by wycy 9y ago

taf2 9y ago

Or c.) an engineer spent weeks after news broke looking into issue again and found a better solution...

dusing 9y ago

It is back in 11.3 - when you first launch messages it even asks you to turn it on.

Yetanfou 9y ago

For Apple to do the right thing they'd have to issue a blanket free battery swap on all affected iDevices or maybe even a device swap to a model unaffected by this 'design problem'. I can simulate the problem these devices have rather easily on my own phone, a 2011-vintage Motorola Defy. The thing was first sold as having an '800 MHz' SoC, a later model (Defy+) supposedly sported a '1000 MHz' SoC. In reality the hardware did not change all that much between those releases except for the inclusion of a high-capacity battery. The clock rate is software-defined and can be changed more or less at will. As I was one of the developers to work on porting newer releases of Android (in the guise of Cyanogenmod) to this platform I had access to a number of these devices. All of them ran without problems at the standard clock rates of 800MHz and 1000MHz, most could be overclocked to 1.1GHz. Beyond that clock rate things started to look different with some devices experiencing sudden reboots when called or in other 'active' situations. The higher the clock rate, the more devices would start failing. On the other hand, some of them could run at 1.3GHz without problems, this includes the one I'm still using. It is now almost 7 years old but still works fine on its original battery. While battery runtime has gone down from about 5 to 3 days it still works without sudden reboots. If Motorola had clocked the Defy to 1.2GHz from the outset they'd have been in a similar situation as Apple is now with some users complaining about their devices rebooting spontaneously. They did not do so, instead they marketed the device on other features (being waterproof and rugged and such). Apple on the other hand did and marketed their devices as being 'faster than ever', i.e. they deemed the instability caused by the overly high clock rate a defensible trade-off.