Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Apple Releases iOS 6.1.3 With Passcode Bug Fix and Japanese Maps Enhancements, Kills Evasi0n Jailbreak

smithrh said:
I'm trying to figure out why any map updates would require new code on the iPhone... Japan, US, wherever. I'd tend to think (and I'm probably wrong!) that way north of 99% of the content would be server-side.
Click to expand...


The actual map data can be updated server side (and was for Japan before this update). But UI bugs, routing issues, etc all have to be fixed by updating the app itself.
 
...2 out of 3 calls I've made without a headset have complained about "muffled" "robotic" or "underwater" audio, so I'd say 6.1.3 does not address the audio quality issue - at least not for me.
 
Apple is failing to innovate. There hasn't been any new features in iOS 6 since release. I remember the days when X.1 or even X.X.1 releases would add useful features. What is being released nowadays seems to be maintenance and obligation.
 
orthorim said:
If you think the US is bad then you haven't been anywhere else. It would be an understatement to say Apple Maps is completely useless in Thailand. Just as an example.
Click to expand...

Useless in the Philippines also. I travel there a lot on business and Apple maps are awful there. I'm based in San Jose, Ca and my local US maps have actually been really good.
 
McPc said:
I think it must be some kind of bug that it reports higher battery life! :p

My phone reported it had a 100% charge after the update when it was at 87% before downloading and installing the update UNPLUGGED. It's a miracle!
Click to expand...

I finished the update at 11:30 AM CST at 98% battery.
It now is 3:55 PM and I am at 84% battery.
 
No thanks. 6.1.2 killed the wifi on my 4S. The wifi button itself is greyed out. I thought it was supposed to FIX that issue. It was fine before. Heading to the Genius Bar tomorrow although I've tried about everything in the book - and some not in the book...
 
Why can't I do this over LTE?! It's only 18.2MB and I have apps that are bigger that I can download over LTE. So dumb.
 
I made the mistake of upgrading from 5.1.1 to 6.0 buying the iPhone 5, only to have to wait 5 months to regain the jailbreak functionality I sorely missed. I won't make the same mistake again.
 
Biscuit411 said:
No thanks. 6.1.2 killed the wifi on my 4S. The wifi button itself is greyed out. I thought it was supposed to FIX that issue. It was fine before. Heading to the Genius Bar tomorrow although I've tried about everything in the book - and some not in the book...
Click to expand...

That stinks. I'm sure you have tried but I'll ask anyway, have you tried to restore and set it up as a new phone, not restoring from a backup, to make sure it isn't a preference that got screwed up in the upgrade process?
 
klamse25 said:
Apple is failing to innovate. There hasn't been any new features in iOS 6 since release. I remember the days when X.1 or even X.X.1 releases would add useful features. What is being released nowadays seems to be maintenance and obligation.
Click to expand...

If by "failing to innovate" you mean they're not throwing in whatever new features you happen to be looking for in their 6.1.X release, yes, that's true. It's the way most mature OSs are on this leg of their release cycles. Android is currently another example of this behavior. If you look at the difference between Android 4.2.1 and 4.2.2, not much going on, and 4.2 wasn't huge on features either, mostly tweaking and expanding existing stuff.
 
a.jfred said:
Oh, and I'd love for Location Services to not ALWAYS be activated when I wake my phone up. There's no reason for it to be on all the time, particularly when I don't have anything running in the background.
Click to expand...

This could be happening if you have anything in your Passbook. It's always looking at your location when you wake up the phone so it can display your tickets, cards, etc. when you arrive at the airport, store, theater, or wherever. It will stop doing that if you remove your things from Passbook.
 
RJCP said:
You people are funny. THe bug is announced, you cry for blood. They release a fix, you say "thank you, but no thank you"...

For crying out loud...
Click to expand...

Are you sure the same people that cried for blood are now saying no thank you? That's the danger of assigning viewpoints to an entire group....
 
iPad (3) stuck on update via iTunes

Edit: Never mind -- update just finished successfully, but it sure took an extraordinary mount of time.


I successfully update my iPhone 4S via iTunes, and then hooked up the iPad (3rd gen) and it is taking forever (Apple with progress bar on screen). I looked at the console log and there are some very bizarre messages:


3/19/13 5:53:35.155 PM iTunes[248]: AMDeviceConnect (thread 0x117161000): Could not connect to lockdown port (62078) on device 664 - 2077dbbea81b34219ac7b85e978fe42191b629e1: 0xe8000065.
3/19/13 5:54:18.529 PM iTunesHelper[278]: AMDeviceConnect (thread 0x7fff742f3180): This is not the droid you're looking for (is actually com.apple.mobile.restored). Move along, move along.
3/19/13 5:54:18.530 PM iTunes[248]: AMDeviceConnect (thread 0x11a573000): This is not the droid you're looking for (is actually com.apple.mobile.restored). Move along, move along.
3/19/13 5:54:18.534 PM iTunesHelper[278]: AMDeviceConnect (thread 0x7fff742f3180): This is not the droid you're looking for (is actually com.apple.mobile.restored). Move along, move along.
3/19/13 5:54:18.535 PM iTunes[248]: AMDeviceConnect (thread 0x11a573000): This is not the droid you're looking for (is actually com.apple.mobile.restored). Move along, move along.
3/19/13 6:03:27.520 PM com.apple.usbmuxd[19]: MuxTCPInputSCE received RST for 0x299-2077dbbea81b34219ac7b85e978fe42191b629e1@0xfd300000:12345->0x10025dc80-iTunes/com.apple.iTunes:56587: handleConnectResult: failure - 61
3/19/13 6:03:27.522 PM com.apple.usbmuxd[19]: MuxTCPInputSCE received RST for 0x299-2077dbbea81b34219ac7b85e978fe42191b629e1@0xfd300000:12345->0x10025de10-iTunes/com.apple.iTunes:56843: handleConnectResult: failure - 61
3/19/13 6:32:19.860 PM com.apple.usbmuxd[19]: MuxTCPInputSCE received RST for 0x299-2077dbbea81b34219ac7b85e978fe42191b629e1@0xfd300000:62078->0x101d0a940-iTunes/com.apple.iTunes:54539: sendMuxSegment connection was closed
3/19/13 6:48:55.335 PM iTunes[248]: lockssl_handshake (thread 0x7fff742f3180): SSL handshake fatal lower level error -1: SSL_ERROR_WANT_READ
3/19/13 6:49:36.274 PM iTunes[248]: lockssl_handshake (thread 0x7fff742f3180): SSL handshake fatal lower level error -1: SSL_ERROR_WANT_READ
3/19/13 6:53:27.863 PM iTunes[248]: _NotificationSocketReadCallbackGCD (thread 0x7fff742f3180): Unexpected connection closure...
3/19/13 6:53:39.528 PM iTunes[248]: AMDeviceConnect (thread 0x117161000): Could not connect to lockdown port (62078) on device 666 - 2077dbbea81b34219ac7b85e978fe42191b629e1: 0xe8000084.
3/19/13 7:03:42.077 PM iTunes[248]: lockssl_handshake (thread 0x1359e1000): SSL handshake controlled failure 0: SSL_ERROR_SYSCALL (Early EOF reached)
3/19/13 7:03:42.078 PM iTunes[248]: AMDeviceStartSession (thread 0x1359e1000): Could not start session: kAMDDeviceDisconnectedError
3/19/13 7:05:30.271 PM iTunes[248]: _select_socket (thread 0x117161000): receive secure message timeout!
3/19/13 7:05:33.355 PM iTunes[248]: lockconn_disable_ssl (thread 0x11a573000): Could not shutdown SSL connection: -1.
3/19/13 7:12:54.694 PM iTunes[248]: _select_socket (thread 0x117161000): receive secure message timeout!
3/19/13 7:12:54.695 PM iTunes[248]: AMDeviceValidatePairing (thread 0x117161000): Could not validate pairing with device 670: kAMDReadError


Any ideas?
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back