Apple has quietly disabled Dashboard by default in the seventh beta of OS X El Capitan, an unsurprising move given the ten-year-old widget feature on Mac has not been updated in over four years and looks increasingly poised for retirement. Dashboard was similarly disabled by default on OS X Yosemite.
Latest OS X El Capitan beta disables Dashboard by default. Not long now, old friend 😥 pic.twitter.com/Cp2ecE6Fa2
— Jeremy Burge ⌚️ (@jeremyburge) August 20, 2015
While a few websites claim that Apple has removed Dashboard from OS X El Capitan entirely, the feature can be re-enabled by opening System Preferences > Mission Control and choosing “As Space” from the Dashboard drop-down menu. Then, tap on the Dashboard key on your keyboard to bring up the window.
Dashboard was introduced on OS X Tiger in 2005 and acts as a secondary desktop for widgets such as a calculator, calendar, clock, weather, stocks, sticky notes, mini games, dictionary, flight tracker and more. Widgets can be added or removed from Dashboard by clicking on the plus or minus buttons in the bottom-left corner.
Apple today released the seventh beta of OS X 10.11 El Capitan to developers for testing purposes, two weeks after releasing the sixth El Capitan beta and two months after unveiling the new operating system at its 2015 Worldwide Developers Conference. Apple has also re-seeded the fifth public beta of OS X El Capitan to public beta testers.
The update is available through the software update mechanism in the Mac App Store and through the Apple Developer Center.
In recent weeks, Apple has been pushing rapid updates for OS X El Capitan, all of which have focused on under-the-hood performance improvements and bug fixes to optimize the operating system ahead of its public debut. Few design changes have been made in the most recent betas.
OS X El Capitan is designed to improve features introduced with OS X Yosemite, focusing on performance and user experience. A number of apps and processes on the Mac are much faster with El Capitan, and the introduction of Metal for Mac brings system-level graphics rendering that’s 40 percent more efficient.
As for user experience, El Capitan includes a new systemwide San Francisco font, a revamped Mission Control feature, a new Split View feature for using two full-screen apps at once, deeper functionality for Spotlight, and several new features for Safari, including Pinned Sites for housing frequently visited websites and a universal mute button that quiets all tabs.
OS X 10.11 El Capitan is available to both registered developers and public beta testers. Apple plans to release El Capitan to the public in the fall.
If you’re an iPhone user that’s just not happy with the current selection of smartwatches, well, you’re probably on the wrong website, but there’s some good news on the horizon. Developer Mohammad Abu-Garbeyyeh recently released a video showing off how he paired a Moto 360 with an iPhone through some clever workarounds. Most of the functionality was borked, but you could at least check some text messages.
Today, he’s shown off some new progress on pairing the two together. It’s not a ton of improvement, but he’s able to answer a phone call made to the iPhone right from the Moto 360. There’s no jailbreaking, rooting, or anything else done to make this work. Just a simple APK sideloaded onto the Moto 360.
While developers like this are working at making Android Wear compatible with iOS, Google is supposedly working on their own iOS app to enable compatibility. Who do you think will get things working first?
source: Techno Buffalo
Come comment on this article: More progress being made on pairing Android Wear with iPhones
Google has hinted that it could eventually make Android Wear work with iPhones, but as the wearables platform is getting close to its first birthday, we’re yet to see an official integration. The good news is, if you really want to use your Android Wear smartwatch with an iOS device, an unofficial solution may be coming.
Android developer Mohammad Abu-Garbeyyeh, widely known on XDA as MohammadAG, found a way to push notifications from iOS to AW. MohammadAG, who is known for his work developing Xposed Framework modules, used a feature called Apple Notification Center Service (ANSC) that was first introduced on iOS7. This is the same feature that allows Pebble to receive notifications from iPhones via Bluetooth. Because it’s built into the operating system, making use of ANSC doesn’t require a special app – notifications from any app can be pushed automatically to a connected smartwatch.
To enable the feature, MohammadAG created an .apk that needs to run on the smartwatch, and the developer said he’s considering open-sourcing it. You will still need an Android device to set up the smartwatch and get apps on it, but the good news is you can use any iOS7 or higher Apple device, no jailbreak required.
Now, the Android Wear experience is more than just notifications and MohammadAG admits that this ANSC-based implementation is limited. But if you just want simple notifications, this could do. We’ll keep an eye on this little project and let you know when, if ever, becomes available.
Nearly a month ago, we noted that Apple was apparently working on iOS 7.1.2, as revealed in our web logs by the appearance of visits from devices running the operating system version on Apple’s networks.
At the time, we had no information on what the update would include, but suggested it was likely to include fixes for an email attachment encryption issue and problems for users leaving iOS for a different platform trying to disassociate their phone numbers from iMessage. In both cases, Apple acknowledged that it was working on fixes for the issues that would be included in a future software update, and iOS 7.1.2 will be the first public update released since those statements.
MacRumors has now learned that Apple is indeed nearing a public release of iOS 7.1.2 and has begun seeding carrier partners with a version of it, termed build 11D257. Apple has apparently asked carriers to sign off on the update by Friday, June 27, indicating that a public release could occur the following week.
According to sources, the build of iOS 7.1.2 does indeed address the email attachment encryption issue, as well as a bug in downloading emails. Also included in the update is a fix for a lock screen vulnerability that could allow access to “limited apps”. While we can’t say for certain, Apple may be referring to the “missed call” lock screen bug publicized earlier this month.
Finally, iOS 7.1.2 is said to include both improvements to iBeacon connectivity and a bug fix related to data transfer with third-party accessories such as bar code scanners. There is no explicit mention of any fixes for iMessage, but they may still be quietly included in the release.
Visits to MacRumors.com from devices running iOS 7.1.2
Since the first appearance of iOS 7.1.2 in our web logs back in mid-May, traffic from devices running the upcoming operating system has increased fairly gradually with the exception of a spike on the day of Apple’s Worldwide Developers Conference keynote.
Apple today released a new support document, detailing the issue behind the recent problems some iOS 6 users have been experiencing with FaceTime. According to Apple, a bug resulting from an expired device certificate has rendered FaceTime unusable on older versions of iOS and the only solution to the problem is to update to the latest version of the operating system.
Devices capable of running iOS 7 must be upgraded to iOS 7.0.4 or later, while devices unable to run iOS 7, such as the fourth-generation iPod touch, must upgrade to iOS 6.1.6.
If you started to have issues making or receiving FaceTime calls after April 16, 2014, your device or your friend’s device may have encountered a bug resulting from a device certificate that expired on that date. Updating both devices to the latest software will resolve this issue.
If you’re using iOS 7.0.4 or later or iOS 6.1.6, this issue doesn’t affect you.
If you’re using these versions of OS X or FaceTime for Mac, this issue doesn’t affect you:
– OS X Mavericks v10.9.2 or later
– OS X Mountain Lion v10.8 with the latest security updates
– OS X Lion v10.7 with the latest security updates
– FaceTime for Mac version 1.0.5 or later for Mac OS X v10.6
While FaceTime does work with iOS 6.1.6, that particular update is not available to recent devices that are able to run iOS 7, which means iOS 6 users with newer devices who wish to access FaceTime must upgrade to iOS 7.
There’s a sizable contingent of iOS users who opted to stick with iOS 6 over iOS 7 due to the drastic visual changes introduced with the operating system update, so Apple’s upgrade suggestion is likely to be unpopular with those users.
Apple’s FaceTime issues first began on April 16, with many iOS 6 users reporting an inability to use the service. At that time, it was unclear whether Apple would implement a fix, but customer service representatives have been presenting iOS 7 updates as a solution since the problem was first uncovered, and it appears that Apple does not plan to offer another solution. The company did, however, release a FaceTime update for OS X users to fix the issue earlier this week.
Soon you might be able to simply ask your Apple TV to start playing ‘House of Cards’ rather than fumbling through a series menus. Code found in iOS 7.1′s software development kit indicates that Siri is one its way to a new device, likely Apple’s set-top box. In the operating system’s documentation, the iPhone, iPod touch and iPad are represented by “1″ and “2.” The most recent files also include a new device indicated by a “3.” For our non-developer friends following along at home, that means the digital assistant is headed to a different product. While the 3 could potentially represent something entirely new (like the fabled iWatch), Apple has previously used the number to represent its TV product in code. It’s also currently being used in several iOS-based Apple TV apps.
– UNiCORN (@bp_unicorn) April 19, 2014
We first heard about a Siri-enabled television several years ago in Walter Isaacson’s biography of ‘ Steve Jobs. In the book, the Apple cofounder says he’s “finally cracked” the television by creating a voice-controlled remote — a dream that as of yet hasn’t become a reality. Apple’s current TV product (which is rumored to be getting an upgrade soon) doesn’t have a built-in microphone. If Siri is coming, she’ll have to bring a new box with her, or at the very least, a new remote with voice input à la Amazon’s new Fire TV. We suspect all mysteries will be revealed in early June at Apple’s annual developer conference, WWDC. Until then, we’ll keep yelling commands at our TV and hope it gets the idea.
Internet calling and messaging service Viber does a solid job of constantly bringing new features to its apps, regardless of the platform. Now, some seven months after iOS 7 was released, Viber is finally changing the looks of its iPhone app to match that flat, minimalist appearance of Apple’s OS. Aside from overhauling the UI, the Viber application now also lets you create a list of numbers you’d like to block and send longer video messages to people. The company’s CEO, Talmon Marco, tells us this update isn’t just about iOS 7, however. “This is the first time we are introducing a new look and feel for Viber. Our goal was to create a simple and friendly interface but at the same time establish a solid foundation for future updates,” Marco stated. In other words, don’t be surprised when you see some of these design cues make their way to other Viber apps, like those on Windows Phone 8 and Android.
Source: App Store
A security researcher claims changes Apple made to tighten its kernel security system in iOS 7 instead weakened the system, making it less secure than its iOS 6 counterpart. (Via CNET and ThreatPost) Azimuth Security researcher Tarjei Mandt discovered the flaw and presented his findings last week at CanSecWest.
The security flaw involves the random number generator Apple uses to secure its kernel. In iOS 6, the number generator that encrypted the kernel derived its values in part from the CPU clock counter. Because it was based on time, the encryption was only marginally secure as the output values were predictable, especially when examining successive numbers.
Apple was aware of the limitations in iOS 6 and attempted to tighten security in iOS 7 by changing the random number generator to a linear congruential generator, which is more susceptible to brute force attacks.
The problem with the new generator in iOS 7 is that it uses a linear recursion algorithm, Mandt said, which has “more correlation” between the values it generates. That makes them easier to extrapolate and guess, he said.
This flaw potentially allows a malicious hacker to gain kernel-level access to an iOS device via an unpatched vulnerability. The kernel is the base part of the iOS operating system and controls low-level functions such as security and resource allocation.
Apple approached Mandt about his findings and asked for his CanSecWest slide presentation.
Along with several visual tweaks, CarPlay support, and Touch ID enhancements, iOS 7.1 also brought some changes to the way in-app purchases work. When making an in-app purchase for the first time after updating, users are notified via a pop-up window that additional in-app purchases can be made for 15 minutes without reentering a password.
The message also points to an existing option in the Settings menu that allows users to require a password with every in-app purchase.
First uncovered by AppleInsider, the new message is likely the result of an agreement between Apple and the Federal Trade Commission, which required the company to implement measures to obtain express consent from consumers before billing them for an in-app purchase.
According to the consent decree that was initially signed in January, Apple had until March 31 to make the necessary changes, which may or may not be completed with the inclusion of the new message that requires users to acknowledge the possibility of additional in-app purchases.
While the pop-up is new, Apple has always had a 15-minute purchase window allowing additional in-app purchases to be made without reentering a password, a policy that landed the company in hot water in 2011 after parental complaints about children over-spending in apps sparked the FTC’s interest.
Apple made some changes to in-app purchases following the complaints, requiring a separate password entry specifically for in-app purchases, but the company was still forced by the FTC to to provide full refunds to parents whose children purchased unauthorized in-app items.
In addition to implementing the required changes to the App Store, Apple will refund approximately $32 million to parents.