Slashdot Mirror
iOS 6.1 Leads To Battery Life Drain, Overheating For iPhone Users
An anonymous reader writes "We have started seeing an increase in iPhone issues related to battery life and overheating. All of them seem to be related to users upgrading their devices to iOS 6.1. Furthermore, Vodafone UK today began sending out text messages to iPhone 4S owners on its network, warning them not to upgrade to iOS 6.1 due to issues with 3G performance. The text reads, 'If you've not already downloaded iOS 6.1 for your iPhone 4s, please hold off for the next version while Apple fixes 3G performance issues. Thanks.'"
My phone is too full to run the upgrade. I guess I am just good.
It seems background audio from Safari and other browsers is broken as well.
And this is why I refuse to install system updates for at least a month after they are released. Let some other poor sod brick their phone with an obscure bug, and get the fixed update once they finish the croudsourcing beta test.
I've decided to Diversify my Holdings. I've divided my cash between my left and right pockets, instead of all in one.
Maybe those have the same bug since they are (allegedly) such a shameful copy of the iPhone...
lucm, indeed.
iOS 6.1 - iPhone 4S - no issues. Don't know where TFA is getting this from.
The most recent update on my HTC increased my battery life significantly.
"I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
It's a feature to keep user's hands warm during the cold winter months, which will be turned off in a future release when the seasons change.
- Apple PR
Trolling much?
http://www.phonesreview.co.uk/2012/12/17/galaxy-s3-jelly-bean-problems-since-verizon-update/
I've been reading /. since 1998 or something and one thing that would always make me mad were the assholes that would reply to a problem in a particular OS with the suggestion that the solution to that problem would be using another particular OS. Normally it would be a MS Windows issue and always there was an asshole saying that with Linux that particular problem would not happen.
So to get back to point. Next time you have a headache, please remember, that the problem is that you have a faulty head and should be using another, better one. So please have someone chop it off, and replace it with a new one.
Everything I read points to interaction with MS-Exchange as the culprit.
It may be an Apple bug related to interacting with Exchange, but since Exchange is a proprietary and non-standards compliant interface, such things happen from time to time.
I've experienced better battery life since going to 6.1 on my 4S. Of course I don't (and hopefully won't ever) use Exchange.
Suppose you were an idiot. And suppose you were a member of congress. But then I repeat myself. -- Mark Twain
Next time you have a headache, please remember, that the problem is that you have a faulty head and should be using another, better one. So please have someone chop it off, and replace it with a new one.
And we'd really like to hear about your experiences afterwards. Especially if this problem keeps recurring despite your solution...
Those who can make you believe absurdities can make you commit atrocities. - Voltaire
and they have replaceable batterys and extended ones as well.
As far as I know, 32-bit Windows 8 still supports 16-bit apps. 64-bit Windows dropped those quite some time ago.
...to keep from fucking things up all the time.
There may be many worthy reasons to move from an iPhone to a Nexus 4, but battery life isn't one of them, and neither is heat.
However, you may be on to something with the SIII. After all, if holding off on upgrades to the newest OS version is something that's important to you, going with a non-Nexus Android device will provide that functionality far beyond expectations. :D
I remember hearing battery problems for practically every iOS version from 5.0 onwards.
http://osxdaily.com/2011/10/16/ios-5-battery-life-fix-tips/
http://arstechnica.com/apple/2012/12/ios-6-0-2-suspected-of-draining-batteries/
What gives?
One of the strong points of iPhone is the fact that it is very manufacturer supported. It is *THE BEST* menufacturer supported consumer device out there. I don't care what you cheer for or what you bought, I think there's simply no denying Apple's iPhone is at the top in this category. They get updates. They get fixes. The carrier does not and cannot get in the way. (Though in the early days with AT&T demanding Apple disable tethering and all that kinda sucked.) After saying all this, you would think I'm another Appe fanboy. I'm not. I'm not any kind of fan boy, but I choose Android over all others and choose carrier independence by going with unlocked, rooted and custom ROM'd phones. So all that out of the way, what am I talking about cutting both ways?
Well, this: Apple pushes updates to the whole OS -- kernel, apps and all, to all users and all [selected] phones. "The experience" is pretty important to Apple and that it should be consistent is a high priority to them. I think their rate of updates appear to be okay but their all-or-nothing thing is a problem in that problems like these occur and from what I understand, going back to a previous version is not done... not casually anyway and requires jailbreaking maybe?
The power of the various versions of the iPhones vary. Android devices vary a LOT more. And as I look at the potential of the devices, it is easy to observe that the hardware has limits which shouldn't be exceeded. I've been pissed off at T-Mobile and Samsung for not updating my SGS2 soon enough or for long enough, but sometimes the argument that the hardware can't support the software is true. This Apple story rather reminds me of that fact.
So it cuts when the device (iPhone or Android) doesn't get the updates users crave, but it also cuts when the updates kill the phone. I guess it's time for me (and anyone else who hasn't yet) to accept that my expensive phone(s) are to be considered short-term use devices with a life expenctancy of about a year... maybe a year and a half. (And certainly not the duration of the contracts that most people sign in order to get their new shiny.)
Wouldn't it be nice if we could have a more PC like experience with our phones? By that I mean, choose our body/case, display, processor, RAM, storage, radios and all that? I know... too much to hope for. Still, to fight be able osolecence would be nice.
the models are all the same, the 3G networks around the world are all slightly different
probably a bug in how vodaphone does something on their network and some app using location services
Apple provides some of the best legacy support for their devices of all mobile vendors. By a WIDE margin, in many cases given that most other mobile vendors stop supporting a device the instant it's sold...
Also, on the desktop side, they continued supporting OS9 apps for almost a decade after moving on from that OS, as but one example of their legacy support. They not only provide some of the best legacy support in the industry, they also provide a great deal of advance warning of when that legacy support os going to end.
So, aside from just being a troll, I don't have a clue what you're talking about.
I solved my 6.1 battery issues by deleting and recreating my two exchange email profile.
Apparently this a common issue after iOS upgrades.
CC
TaijiQuan (Huang, 5 loosenings)
This is correct.
Apparently if you update a calendar item on your iOS device, it tries to update Exchange and fails.
It then retries continuously, chewing through battery life and log files: http://wmpoweruser.com/exchange-server-acting-up-blame-those-ios-6-1-users-then-ban-them/.
Um, what is this drivel? The 4S isn't "yesterday's customers". Apple sells it today, and will keep selling it tomorrow, and for many tomorrows to come. Nobody's telling you to buy a 5, not even Apple. I have a 4S, and it works better today than it did when I bought it well over a year ago.
You are right about one thing. Apple does drop support when they feel it's worth it. PPC, Classic, 32-bit hardware... But here's the deal with that: 1. the old stuff doesn't magically stop working. 2. by dropping legacy support, the new stuff works much better than it otherwise would.
MS's adherence to legacy has brought about all sorts of annoyances (including security issues) throughout the years. That's one of MS's strengths, though, supporting things for years and years. Apple's quickness to disregard legacy to make things better is one of their strengths. I prefer the latter, because it provides, for me, a much better experience. Perhaps you prefer the former?
Apple provides some of the [least horrible] legacy support for their devices of all mobile vendors. By a WIDE margin
FTFY.
Thanks, you are correct on all counts. My comments were based on the preponderance of new systems sold, which are pretty much all 64 bits as of (vaguely) recently.
Including two iPhone 4S.
Because the manufacturer of my 1 year old phone has decided that it isn't *worth* updating. No problem - I just installed Cyanogen mod and I'm good ... well, except that the camera isn't supported yet, and the battery life is 1/2 what I get on the manufacturer's ROM.
Suddenly, overheating Apple phones don't look so bad - at least iPhone owners can be reasonably certain that Apple will actually release a fix, in a timely fashion.
So to get back to point. Next time you have a headache, please remember, that the problem is that you have a faulty head and should be using another, better one. So please have someone chop it off, and replace it with a new one.
Don't be a pirate. Don't steal heads.
#DeleteChrome
Perhaps you prefer the former?
We've talked about this from several angles, so that's a hard question to answer simplistically. We all like cool new stuff that works. :D
I'd just get back to my example of Apple deliberately breaking autorotate for legacy apps running on iOS 6. I definitely do not prefer that kind of change. I think it was a good example of what I was talking about, and not "drivel" at all. You're welcome to write a refutation of that point.
Did you get paid for that advertisement? Either way, it's still spam.
Not a developer - feel free to ignore as you will.
Your complaint is as a developer. You started the conversation about owning an iPhone, which is about being a consumer.
As a consumer, Apple provides some of the best legacy support in the industry. Yes, some things eventually become EOL but, compared to the other options, Apple products are supported a very long time from release.
As a developer, I would say this - any developer who thinks they can develop once and be done forever, especially in the rapidly changing landscape that is mobile, is delusional. To stay current means periodically being forced to adapt to an evolving OS landscape.
I would imagine that for every example of Apple breaking something in iOS as the system has evolved, someone (with more knowledge about the development environments than I have) can point out similar situations with Android (not singling out Android - it's just a two horse race and the others don't really matter, quite frankly...).
So, either complain as a developer (which isn't really relevant to this entire subject given that it has pretty much nothing at all to do with development) or complain as a consumer in which case you're wrong.
I suggest switching to Linux.
Title fixxored.
I can see the fnords!
Apple really doesn't care much for legacy support; Rosetta is not even installed on Mac OS X by default anymore. They constantly make minor changes to their core OS APIs that require writing separate code paths or using separate languages altogether. The OS X window system interface in my graphics engine is 4x as long as the Microsoft Windows interface. And now, to compile the engine as a 64-bit binary on OS X, I have to write an Objective C wrapper to use parts of the OS that are no longer accessible in their 64-bit C APIs.
It has been this way for most of Apple's history and it is frustrating for software developers and consumers alike.
Oh I get it! M$! Like "MS" for "MicroSoft," but you used a dollar sign instead of the S to show they're greedy! That's so clever! Did you think that up yourself? I bet you're well-liked with tons of friends, being as witty as you are.
We don't have a state-run media we have a media-run state.
Coming from the Microsoft world I have been very surprised at how little attention Apple pays to legacy compatibility. It's only recently become impossible to run 16 bit Windows apps in the latest Microsoft OS. Compare that to the constant forced churn in Apple desktop software.
Huh? Are you talking about the sample Apple that let desktop software developed for 68K CPUs run on Power Macs, software developed for classic Mac OS run on OS X, and software compiled for PowerPC to run on x86?
Are you talking about the same Microsoft that replaced Visual Basic with the incompatible VB.NET, changed the way to develop for smartphones in Visual Studio 2008 and then again in 2010, so that applications developed in VS 2008 will only compile in that version? The same Microsoft that pushed PlaysForSure DRM, and then released the Zune with an incompatible DRM scheme, so that the music its allies had been selling wouldn't play on the Zune? The same Microsoft that got half the world writing code that only worked in Internet Explorer 6, and then broke compatibility in IE7, that pushed Silverlight as the primary way to develop for Windows Phone, and then discontinued Silverlight?
Maybe, coming from the Microsoft world, you really are used to better backward compatibility than what you've seen from Apple. But both companies have cases where they went to great length to preserve backward compatibility and cases where they didn't.
Please correct me if I got my facts wrong.
Every civilized person shouldn't venture more than 4 feet away from an outlet. Swapping batteries is so bohemian. This isn't some hippy love-in we're talking about.
I'm a big apple fan and have "bought in" to their ecosystem, but your statements about legacy support by apple are flat wrong. Apple is both a hardware and software company, so I'll discuss both:
Software:
If I buy some software application developed for the current MacOS version, it will probably run on the newest version of MacOS 5 years down the line, _probably_. 10 years down the line, I might be so lucky, 15 years and almost certainly not.
Given that you can still run DOS and Windows 3.1 applications in the current version of Windows, I've pretty much got a guarantee of at least 20+ years of backwards compatibility with Microsoft.
Hardware:
My modern iMac is being currently forced into obsolescence by Apple with new features (AirPlay) being not supported. Generally speaking, you can expect an Apple computer to have partial ability to keep up with the newest OS upgrades for about 4 years. After 5 years, you will probably not be able to upgrade it at all (not because of issues with processing power, but forced obsolescence).
In short, there are many reasons to buy Apple products: design, user interface, ecosystem, the it-just-works thing. Legacy support is not one of those.
How about the other way around? Every time there is a major OSX release, Adobe programs break, Autodesk products stop working. And of course you don't find out about the software incompatibility until you upgrade.
I have both OSX and Windows machines (although most of them run Linux), and have never run into software incompatibility issues with Windows upgrades. Not even from Windows XP -> Win7. On OSX, need to purchase a new version of Adobe and Autodesk products with every upgrade. New versions not available until several months _after_ the OSX upgrade, which completely blows. That's no "best legacy support", sorry.
You called your parent a troll, not knowing what he's talking about - the pot calling the kettle black.
I am pissed that the Nexus 4 does not support LTE.
I concur.
While I think it is great that Google released a high end phone for $300, I would gladly have paid the normal Nexus retail price of $650 for a Nexus 4 LTE.
Instead I have gone with the Galaxy SIII and a custom ROM to get an AOSP and LTE experience on 2012 hardware.
The inclusion of AWS Band 4 LTE the requires some hacking is interesting.
I was hoping for LTE 700MHz Band 17 personally.
What LTE frequencies would you want supported?
"There's Always Next Year", when the Nexus 5 will have:
4/17/13/7/3/12/25 band LTE and Penta-Band HSPA+
A high quality 16MP CMOS camera sensor with O.I.S and Xenon flash.
A 5" 1080P IPS screen.
A physical QWERTY keyboard as well as physical home, menu, back, accept call, end call, and camera shutter buttons.
Dual EasyPoint Joysticks.
Hey, I can dream!
It will be interesting to see if Google can pull off a multi-band LTE device at the $300-$350 price point later this year.
It seems LTE cannot be ignored given the inclusion on the iPhone 5 and the backlash of complaints (although Nexus 4 sales exceeded supply expectations still).
But if Google "must" include LTE, how will it do it?
Penta-band HSPA+ has been a great feature of the last two Nexus Devices (only took two next years to get that).
In addition to the GSM support, the inclusion of LTE Bands 17/4 would cover AT&T and T-Mobile.
Throw in LTE Band 7 and Canada carriers covered.
The CDMA/LTE Verizon Galaxy Nexus was a headache for Google due to the proprietary CDMA binaries.
But including LTE Band 13 and counting on the 700MHz C Block FCC open rules would allow Verizon LTE coverage.
However, that would be data only on the Red Devil Carrier.
Including LTE Band 25 is tempting, but Sprint does not offer up SIM cards for its LTE device since it has no 700MHz C Block rules to comply with like Verizon.
Looking outside of North America, including LTE Band 3 and Band 20 would complete LTE coverage in handful of Asian, European, African, and the Middle Eastern locations.
I could not find the exact seven bands that the Nexus 4 Qualcomm WTR1605L chip supports.
The WTRL1605L supported bands may reveal what the Nexus 5 would support.
Of course there are rumors that Google is creating an experimental wireless network in Mountain View.
Perhaps like Google Fiber we will see Google's own wireless network rolled out...
The view controller auto rotation on ios sucks. Just plain sucks. It was bad before ios6, and ios6 made it even worse.
And if having to work with a crappy api is not enough, your app will be rejected if the ui doesn't rotate the way apple wants it. What apple wants you won't find out until about a week from the date of submission. Then you can try to hack it, one week at a time.
I thought the M$ thing was cool when I was a kid. Then I realized that Apple (and later Google) were all about making profits, too, so the whole $ thing seemed rather juvenile. No company is perfect, either with their products or their business tactics.
Anyway, to the topic on hand: As far as I know, it's a relatively uncommon issue. I haven't noticed any battery problems with my iPhone 5; I still recharge it every other night, and LTE/3G seem the same speed as usual. I'm not claiming that some people don't see the problem, but that it may not be as big a deal as the article/summary/headline makes it out to be. As is common for modern /., the headline itself makes it seem as if it's a problem with every iPhone running the new update. Also keep in mind that people will post complaints, and be more vocal about them, more often than they will post compliments.
For those who are experiencing this issue, though, I hope Apple fixes it soon.
If you can't convince them, convict them.
How about the other way around? Every time there is a major OSX release, Adobe programs break, Autodesk products stop working. And of course you don't find out about the software incompatibility until you upgrade. I have both OSX and Windows machines (although most of them run Linux), and have never run into software incompatibility issues with Windows upgrades. Not even from Windows XP -> Win7. On OSX, need to purchase a new version of Adobe and Autodesk products with every upgrade. New versions not available until several months _after_ the OSX upgrade, which completely blows. That's no "best legacy support", sorry. You called your parent a troll, not knowing what he's talking about - the pot calling the kettle black.
I haven't had any of those problems and I used Photoshop CS3 for years until I finally upgraded a few months ago. The only headache I ever had with Adobe software were very occasional segfaults in Photoshop and for a while time I had trouble with the Adobe Reader update program refusing to finish the update process.
When I was a kid there was no "google," or rather they didn't matter yet. Apple was the company who's products you laughed at for being awful. Well...google matters now.
Umadbro? Umad? Why u so mad brah?
No, I'm not trolling. Do you have a response to my comment about the deliberate breaking of autorotation in UIViewController in iOS 6? (If you're not an iOS developer, then never mind.)
Apple provides some of the [least horrible] legacy support for their devices of all mobile vendors. By a WIDE margin
FTFY.
Firstly, untwist your panties, everybody breaks APIs. I develop UNIX/Linux software for a living, I could write you several volumes about the joys of broken APIs.
Secondly, you said:
Conclusion: Apple doesn't care about yesterday's customers, they keep their eyes fixed only on future dollars. When Apple goes down (as all behemoth tech companies eventually do) I shall do a little iDance on their grave, perform an Xpectoration on their development tools, and will be sure to Pee Different(r) on anything else I see lying around.
Which is what he was responding to and which is demonstrably false. I used to have an iPhone 3GS, bought in 2009 and I just upgraded it to iOS 6.1 for it's current owner. That'll soon be four years of regular updates; which is what I call support. I know several people with Android phones whose manufacturers orphaned the devices and stopped supporting them around a year (plus minis a few months) from their market debut. I'm not saying all Android device manufacturers are like that, Samsung for example does a reasonable job with updates even though the first version of the Galaxy tab became a neglected stepchild pretty quickly.
My data connection drops, I have to toggle Roaming to get it back. I've never had roaming turned on and prefer it off but turning it on and then back off or simply turning it on brings back the data connection - for awhile. The screen also seems a bit dimmer and softer especially in dark conditions but I'm not seeing any issues with battery life or performance of 3G for phone calls. The data thing, THAT is a killer that needs to be fixed and hopefully without breaking the jailbreak that's out.
I've done the jailbreak on an iPad2 and want to do it to an older iPhone 4 but I'm having issues upgrading the 4 to 6.1 from 5.1.1 that I suspect have to do with the jailbreak. I'm going to take it through recovery mode with fingers crossed as a simple upgrade wouldn't do it nor would it clear correctly when asked. This experience is making me a little less eager to jailbreak my primary device to say the least. However some of the tweaks are pretty nice and I'll admit make Android a little more attractive. They have their own issues too with custom ROMs and whatnot so I know it's no panacea there either and I like my existing hardware. We'll see what Apple does next, if they break the JB I'm going to be peeved...
Build it, Drive it, Improve it! Hybridz.org
... works flawlessly with iOS 6.1 installed.
Apple was the company who's products you laughed at for being awful.
Wow. If I were being charitable, I'd say that you must have been a really late developer if you thought Apple's products were awful.
Apple is no better than MS for backwards compatibility. MS have done a lot in the past, keeping support for 16 bit apps (even in Windows 7 x86 you can run some 16 bit installers) and other ancient APIs around. Your example of Visual Basic is stupid - they continued to sell it for years and VB app still work perfectly well on the latest 64 bit version of the OS. Similarly VS2008 still works and VS2010 includes an importer for older projects that seems to work just fine.
Apple has managed to piss off quite a few customers by dropping backwards compatibility, for example in Final Cut X which is unable to load projects from previous versions and is missing many features that used to be included. Hell, they annoyed a lot of people way back when they stopped including floppy drives in their computers (and I happen to agree that it was the right thing to do).
Both are as good/bad as each other.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
I know a UNIX admin who took the server MSCE exam when it first came out. Didn't touch any books or study materials. Just took the test.
For every question, he looked at the answers, and asked himself - "Which answer would make Microsoft the most money?"
He passed the test.
late developer? An idiot if I was being charitable.
This is exactly why Apple must lock down your device for your own good. If you jailbreak, you might run unapproved software that could affect battery life or ecen overheat.....OH.......Never mind. Nothing to see here. Move along!
Oh I get it! M$! Like "MS" for "MicroSoft," but you used a dollar sign instead of the S to show they're greedy! That's so clever! Did you think that up yourself? I bet you're well-liked with tons of friends, being as witty as you are.
It's okay. Really. Corporations don't have feelings.
It is a miracle that curiosity survives formal education. - Einstein
It all depends on what you use your phone for.
I have an iPhone--no replaceable battery. And I didn't really miss it. Until I also started using it as a bike computer. Because of the reflective screen, I have to turn it to full brightness. I'm also using the GPS, downloading mapping information, etc. I can get a little over 50 miles--about 3.5 hours--before I'm out of juice.
So I'm sure you've never had to replace a battery on a Nexus phone because you don't use your phone in an environment where it's eating lots of power and you're not near an outlet.
Rosetta is not even installed on Mac OS X by default anymore.
It hasn't been available at all since Lion (10.7). Snow Leopard (10.6) didn't have it by default but at least supported it. I wouldn't be surprised to find out that someone has gotten Rosetta from 10.6 to work on {Mountain ,}Lion, but even if it works it's not guaranteed to work after patches or to not just blow up in your face.
From the Wikipedia article http://en.wikipedia.org/wiki/Year_2038_problem
A month ago I was on a trip, when all of a sudden my iphone 4 was shutting off at exactly 20% battery remaining. I would recharge, and same thing would happen again. I looked online and people said to reset your phone.. So I did that, and while that did fix it, ever since then my phone has been draining faster (so maybe the software bumped the new 0 to be 20%. I used to be able to get 2 days out of it, now it is dieing after about 1 and a quarter days.
Then I upgraded to 6.1 three days ago, now my battery isn't even making it through a day. Ill let it charge to full overnight, and by 9 or 10 p.m it is <10%.
Then use of the many battery extenders which double or more the battery life of your phone, or use one of the portable battery rechargers, which isn't much larger than the battery itself.
Like one of these rechargers: http://www.charmofdresden.com/techcandy-batteryextender.html?productid=techcandy-batteryextender&channelid=FROOG
Or one of these extenders: http://www.wirelessground.com/iphone-4-battery-extender-case.html?utm_source=iphone-4-battery-extender-case&utm_medium=shopping%2Bengine&utm_campaign=googleproducts&gclid=CNnrweviqrUCFag7MgodQTkAcQ
The view controller auto rotation on ios sucks. Just plain sucks. It was bad before ios6, and ios6 made it even worse.
I've nothing to add either way to this.
And if having to work with a crappy api is not enough, your app will be rejected if the ui doesn't rotate the way apple wants it. What apple wants you won't find out until about a week from the date of submission. Then you can try to hack it, one week at a time.
However this seems to be contradicted by all the apps on the App Store. I don't mean to say it's something every developer gets right on the first try or anything like that, just that I doubt every developer goes through repeated submissions for something like this.
And maybe they do. Either way, it's not enough of a problem that it supports the OP's claim. Unless it's really horrible. Which, again, would be suspicious given all the apps on the App Store. I just can't buy that every, or even most, apps go through such rigamarole as you seem to imply. That would put such a burden on Apple's resources as to make it a no brainer to just address that part of UIKit itself.
We've talked about this from several angles, so that's a hard question to answer simplistically. We all like cool new stuff that works. :D
Awesome!
I'd just get back to my example of Apple deliberately breaking autorotate for legacy apps running on iOS 6. I definitely do not prefer that kind of change. I think it was a good example of what I was talking about, and not "drivel" at all. You're welcome to write a refutation of that point.
The claim that they just quite simply broke it, deliberately, for no benefit whatsoever is not something that I can believe without some evidence.
With Apple, there are all sorts of things that look like that, but turn out to have some reason that is not so capricious or malevolent at all. I'll give another example. Mountain Lion requires 64-bit Macs, and there are a handful of 64-bit models it can't run on due to graphics cards requirements.
The explanation for the 64-bit requirement should be straightforward: to simplify development. The graphics card requirement though? Some people have concluded that was because Apple just wanted to force people to buy new Macs. But the reason is as a result of the 64-bit requirement. The 64-bit kernel means 64-bit kexts. The older Intel iGPUs don't have 64-bit drivers.
I'd wager your example is more along those lines than that they just want to make things hard for developers.
LTE really sucked on my Galaxy Nexus when the phone was first released. It would drop the signal entirely every 5-20 minutes even though I live in an area with really good coverage. Verizon said they knew about the problem but it took them months to release a fix. Luckily, the update was leaked online very early on so I was able to get the phone in a working state.
I've been fine with my phones for years. Recently I've been playing Ingress on my HTC EVO Design 4g. That can suck up a battery pretty quick. Even on a 2.1A charger it doesn't keep up all that well. After an hour or two, it starts complaining. I found replacement batteries for about $5/ea on Amazon. It's much easier to swap batteries, than to sit at a portal for 1/2 hour waiting for the battery to charged enough to run the game for a while. The car charger isn't all that useful when walking around to resonators, or in a high density area.
Serious? Seriousness is well above my pay grade.
This happened with the 3G and iOS 4, too. There was no downgrade and the only recourse to an operational phone was t buy a new one. I can't believe they're doing it again. Twice shy...
Win64 never supported 16-bit.
not so much
This isn't my video, but it's exactly the experience I had when upgrading my 2-year old iphone 3g to the 'latest and greatest' iOS 4.
That's not a pirate. That's a head hunter.
Life is not for the lazy.
> mobile vendors.
Apple is the best mobile vendor. Well, MS probably does a good job, but they aren't a big player.
We are comparing iOS to Android; not OSX to Windows.
I have NEVER had to replace a battery on a nexus phone. nobody needs a replaceable battery unless you cant afford the phone to begin with.
Lucky you. Lithium batteries do fail. Ask Boeing if you need proof.
The thing is, the absolute worst thing about the Microsoft system is that it *is* so overly backward-compatible. It sticks it with awful crud such as lettered drives, unversioned dlls, and encourages pathetic solutions to architecture changes such as "Program Files (x86)".
Lol the ironic part is that you thought you were being funny with your comment. It just made you look like an ass.
You are entitled to your own opinions, not your own facts.
When did Apples products suck?
Mid 80s- Late 90s. Give or take.
You are entitled to your own opinions, not your own facts.
When did Apples products suck?
Mid 80s- Late 90s. Give or take.
Depends on what you were doing with your computer.
Audio production work: Mac ruled this domain.
Desktop publishing: Mac here as well.
Pretty much anything else, PCs were the order of the day.
"Flame away, I wear asbestos underwear"
Kudos to your upbeat attitude, but in this case Apple did make a conscious decision to break many existing apps in the App Store. Here's a link that describes the changes they made. For what it's worth, I personally could have coded something that would either not break anything (realistically unlikely in an app store of hundreds of thousands of apps relying on obscure side effects), or at least break a lot fewer apps. link to description.
This is not like the 64 bit thing, because Apple could easily have avoided breaking this stuff on iOS 6. The message they sent was that you'd better be prepared to re-release your app for every new iOS version, because Apple's primary interest is forward-looking, not backward looking. They care about their next dollar, not one they earned a year ago. But I already said that.
Except that full OS upgrades are the only way to fix security and privacy issues. Other than buying a new
iPhone, of course.
I don't care about android - I don't own one. Although if apple continues with this crap I may well soon.
The issues with 6.1 are no different from scattered reports of issues for every release of iOS that has ever come out. There are a few phones after each release that eat battery fast or have other problems, and there are easy solutions posted on many sites as well as Apple support fora. No problems with iOS 6.1 on my phone.
... except that there's no fault in the logic, despite your distaste for it.
If in fact [softwareA] is better at something than [softwareB] and this thing matters to you, then you should probably switch.
If I spent all my time complaining about how I don't get iTunes integration on my Android phone, I'd expect a few dozen "then buy an iPhone" responses.
- Michael T. Babcock (Yes, I blog)
Except that these guys http://www.mugen-power-batteries.com/ make a killing selling extended batteries for phones. Even if you never need to replace it after the fact, the ability to buy an extended battery is eliminated with a sealed case.
- Michael T. Babcock (Yes, I blog)
Sounds like a Verizon issue there not a S3 issue.
Jellybean 4.2 runs beautifully on mine, non-Verizon of course.
I updated my iPhone 4 to iOS 6.1 yesterday. I live in Sao Paulo. Today I went to my parent's in Sao Bernardo (just 20 miles away) and tried to access 3G. I found out neither 3G nor my phone service were working. I turned off / restarted my iPhone, the problem continued. I thought it was a problem with the carrier (Vivo), but my brother-in-law laughed at me showing his Android phone working just fine with the same carrier. Back home, my iPhone started working again.This may be evidence that there is really a problem with iOS 6.1. I don't like to jump to conclusions, but it quacks like a duck...
I've tried to recreate the issue, and so far I can't.
iPhone 5 iOS 6.1, Exchange 2010
I created an appointment - no abnormal increase in logs
I invited someone internal - no abnormal increase in logs
I was invited from an internal account, rejected one, accepted another - no abnormal increase in logs
I was invited from an external account, rejected one, accepted another, also declined after accepting - no abnormal increase in logs
For each of these, there was the expected 20 or so packets associated with the changes, and no ongoing network traffic.
On the other hand, we had a client that had the runaway log issue last week - I'll be following up with him to find the iOS versions involved