Found 10082 bookmarks
Newest
Apple releases iOS 7.0.2 with fix for Lock screen passcode bypass flaw - 9to5Mac
Apple releases iOS 7.0.2 with fix for Lock screen passcode bypass flaw - 9to5Mac
Apple has released iOS 7.0.2 over-the-air for iPhone, iPad, and iPod touch. This is a bug fix release that focuses on rectifying an issue that could allow users to bypass the passcode unlock on the Lock screen. Another fix in this release is to re-add the Greek keyboard options for pass codes. iOS 7.0.2 brings […]
·web.archive.org·
Apple releases iOS 7.0.2 with fix for Lock screen passcode bypass flaw - 9to5Mac
Apple pulls iOS 9.3.2 for 9.7 inch iPad Pro following reports of bricked devices with ‘Error 56’ issue
Apple pulls iOS 9.3.2 for 9.7 inch iPad Pro following reports of bricked devices with ‘Error 56’ issue
Update: Here’s Apple’s comment on the matter: We’re working on a fix for an issue impacting a small number of iPad units that are receiving an error when trying to update the software. We’ll issue an update as quickly as possible” Apple has today pulled iOS 9.3.2 for the 9.7 inch iPad Pro, following reports that users […]
·web.archive.org·
Apple pulls iOS 9.3.2 for 9.7 inch iPad Pro following reports of bricked devices with ‘Error 56’ issue
Some users experiencing bricked HomePod after updating to iOS 13.2 [Update: pulled]
Some users experiencing bricked HomePod after updating to iOS 13.2 [Update: pulled]
Update: Apple has pulled the HomePod update temporarily whilst it works on resolving the bricking issue. Users are being advised not to factory reset their HomePods if they were already updated to 13.2. Apple today released iOS 13.2 alongside a new version of HomePod Software with features, including multi-user support and Handoff. Now some users are reporting […]
·web.archive.org·
Some users experiencing bricked HomePod after updating to iOS 13.2 [Update: pulled]
PSA: iPhone alarms not working come New Year's Day 2011
PSA: iPhone alarms not working come New Year's Day 2011
We're not exactly sure of the cause of this fancy new issue affecting Apple's super cool iPhone line of cellphones, but apparently you've got trouble come 1/1/2011. According to an explosive stream of frustration-filled tweets on the Twitter microblogging service, when the clock strikes midnight, one off alarms will cease to sing out. The issue sounds eerily similar to recent Daylight Savings Time trouble we witnessed back in November, although we saw both repeating alarm and single alarm failures. So how can you fix this potentially life-ruining problem? Well until Apple patches its OS -- and it's currently unclear if this is just iOS 4.2.1 or earlier versions as well -- you can simply create a recurring alarm at the time you need to be woken up, and then disable it once your dreams are completely ruined. We're taking a deeper look into the issue and have contacted Apple -- if we get more news, you guys will be the first to know. In the meantime, feel free to commiserate in comments, and... happy new year? Update: 9to5 Mac says that the bug will get fixed all by itself once the calendar hits January 3rd. We haven't confirmed this, but if it turns out to be the case, that's pretty good news. In less good news, the issue seems to be affecting iOS 4.1 and 4.0.2 as well. Update 2: Apple responded to us on the issue, though they didn't offer any surprises: We're aware of an issue related to non repeating alarms set for January 1 or 2. Customers can set recurring alarms for those dates and all alarms will work properly beginning January 3. [Thanks to everyone who sent this in]
·engadget.com·
PSA: iPhone alarms not working come New Year's Day 2011
iPhone DST bug causing alarms to fail across Europe (updated)
iPhone DST bug causing alarms to fail across Europe (updated)
An iPhone bug already seen when Australia switched between Daylight Savings Time and Standard Time a few weeks ago has now hit Europe. Twitter just lit up with reports of recurring iPhone alarms going off an hour later than usual. So even though the iOS clock changed correctly over the weekend, the alarm did not. Thing is, according to a ZDNet Australia report from more than three weeks ago, Apple acknowledged the bug with a promise to fix it with a software update. So why wasn't it rolled out in time to avoid this mess in Europe? Let's see if Apple fixes it before North America makes the switch on November 7th, otherwise, you've been warned. Update: Deleting and re-adding the alarms will NOT fix the issue. We've now tested a number of scenarios under iOS 4.1 on European iPhone 4 and 3GS devices for ourselves. The bug (demoed on video after the break by Roman) appears when using a repeating alarm for anything other than "every day." So for example, your alarm will go off an hour late if it's set for "weekdays," or "weekends," or every "Monday." The following alarms are not affected by the bug: An alarm that doesn't repeat (repeat set to "never") An alarm set to repeat "every day" You can test yourself by creating a repeating alarm (but not every day) to go off one minute in the future and 59 minutes in the past. Update 2: Some US readers are now waking up to alarms reportedly going off an hour early. [Thanks, David O. and Matthieu Di B.]
·engadget.com·
iPhone DST bug causing alarms to fail across Europe (updated)