On Monday, Elgato Systems released version 3.6 of its EyeTV software application, which finds and tracks all television programming you want to see and allows users to pause live television and save content to file.
The update, a 150 megabyte download, offers the following fixes and changes:
- More than 100 new, crisp retina images.
- Support for Gracenote EPG data (Europe).
- Miscellaneous bug fixes.
EyeTV 3.6 requires an Intel-based Mac running Mac OS X 10.5.8 or later to install and run. If you’ve tried the new version and have any feedback to offer, please let us know in the comments.
Per The Mac Observer, the jailbreak community has beat Apple to the punch with its own solution to an iOS 6.1 bug that could give someone access to your iPhone without knowing your passcode. The app, dubbed “disableEmergency”, removes the Emergency Call button from the lock screen, which effectively removes one of the steps needed to break into your iPhone.
The security flaw requires several steps involving swipes, taps and button presses in the right order, afterwhich your contacts, schedule, and email are acessible.
Removing the Emergency Call button from the lock screen means calling for police or fire assistance will require dialing the emergency number yourself, so hacking your iPhone just to avoid a difficult to perform process may be a little extreme, especially since Apple has promised that a fix is on the way.
disableEmergency is free and available through the Cedia installer.
If you’ve tried the disableEmergency app and have any feedback to offer, please let us know in the comments.
Per German web blog iFun and AppleInsider, Apple is already working on an update to iOS 6 to address a dangerous passcode vulnerability discovered earlier in the week, with one report claiming that the company anticipated issuing the update as early as next week.
The article presently states that iOS 6.1.2 will arrive early next week, and likely before February 20. iFun accurately predicted the launch of iOS 6.1.1, relying on the same sources that tell them 6.1.2 is on the way.
News of the lockscreen exploit hit the Internet last Wednesday. Using the bypass method, one can view and modify an iPhone owner’s contacts, listen to voicemail, and browse through their photos. The exploit does not, though, appear to grant access to email or the web.
Apple on Thursday acknowledged the vulnerability. The company, representatives said to the media, is hard at work on a patch, though they provided no hard details on when users could expect one.
Stay tuned for additional details as they become available.
They’re gotta be getting close to release at some point…
Per MacNN, Apple on Thursday released the latest beta build of OS X 10.8.3, dubbed 12D68, to developers as the forthcoming update moves closer to public release.
The most recent seed comes one week after the previous build 12D65 was rolled out with a fix for the “F:///” detection bug that would crash a number of OS X apps.
With no known issues, the latest seed is the eleventh such beta pushed out to developers, though Apple has yet to issue a Golden Master that would signal an imminent public release.
As with the past few builds, the latest 12D68 focuses on testing AirPlay, AirPort, Game Center, Graphics Drivers, and Safari.
Since a seed in December, developers have been able to receive update notifications through Software Update and download beta builds directly from the Mac App Store by using the new “OS X Software Update Seed Configuration Utility.”
Stay tuned for additional details as they become available.
Late Thursday, shareware developer Maintain released version 6.3.1 of CocktailCocktail (Mountain Lion Edition), the popular shareware utility program that allows for additional Mac OS X system tests. The new version, a 5.5 megabyte download, adds the following fixes and features:
- Fixed a problem where Cocktail could not change Time Machine backup interval.
- Addresses an issue in which Cocktail failed to restart or shutdown the computer.
Cocktail 6.3.1 retails for a US$19.00 shareware registration fee and requires an Intel-based Mac running Mac OS X 10.8 or later to install and run.
Per The Verge, a security flaw in Apple’s iOS 6.1 lets anyone bypass your iPhone password lock and access your phone app, view or modify contacts, check your voicemail, and look through your photos (by attempting to add a photo to a contact).
The method, as detailed by YouTube user videosdebarraquito, involves making (and immediately canceling) an emergency call and holding down the power button twice. Tests confirmed that the hack worked on two UK iPhone 5s running iOS 6.1 and can be seen below:
Similar instances had occurred – and were patched – in iOS 4.1, and was fixed in iOS 4.2.
Apple has yet to reply to requests for comment regarding this situation.
Per MacRumors, just a day after Microsoft offered workarounds for an iOS 6.1 Exchange syncing bug and said that it was working with Apple on a solution, Apple has announced on its support page that it has identified the problem and is working on a fix:
“Apple has identified a fix and will make it available in an upcoming software update. In the meantime, you can avoid this bug by not responding to an exception to a recurring event on your iOS device. If you do experience the symptoms described above, disable then reenable the Exchange calendar on your iOS device using the steps below.
Apple details its own workaround until that update is available, advising users to go to ‘Mail, Contacts, Calendars’ under ‘Settings,’ selecting the Exchange account from the accounts list, turning the switch for ‘Calendars’ off, waiting 10 seconds and then turning it back on.”
The bug, which caused iOS 6.1 devices to continuously loop when syncing a recurring calendar meeting invitation to Microsoft Exchange, isn’t the first bug to stem from the two-week old iOS 6.1. iPhone 4S users were affected by a bug that hampered 3G performance, although that was fixed with Apple’s release of iOS 6.1.1 a couple days ago. There is no timeframe for when the fix for the Exchange bug will be released.
If you’ve seen this bug on your end, please let us know in the comments.