Every once in a while we get an email or a tweet from a reader who claims not being able to play YouTube videos in Mobile Safari, and asking for a fix. The answer I give is always the same: you probably installed a jailbreak tweak (likely ProTube) that conflicts with Safari and prevents you from watching YouTube videos in the browser.
Today, thanks to iDB reader J. Louis, we get to the bottom of this problem and find the real cause and the easy solution to fix it...
Even though Absinthe appears to be a very simple and stable jailbreak tool, a few people are still getting some errors despite the 2.0.1 update.
The main errors that pop up seem to be "Error detecting device (lockdown error -5)" and "Could not connect to lockdown"...
Earlier today, Apple released a new version of its mobile software: iOS 5.1.1. The update includes a number of bug fixes, and also apparently contains a patch for the dangerous URL spoofing vulnerability in mobile Safari.
We told you about the exploit, discovered by the folks at Major Security, back in March of this year. It allows web pages to spoof URLs in Safari's address bar, leading users to believe they're on a different website...
Twitter integration with iOS has led to huge sign-up numbers for the social network. Add those new users to the throngs of iPhone owners that were already big Twitter users, and it's safe to say that there are plenty of Twitter accounts plugged into iPhones.
We're also willing to bet that a fair chunk of those are using the official Twitter app, and it appears that some of those may be experiencing an odd bug, and one that is rather annoying – users are reporting that they are unable to see their own @replies in the Connect tab of the iOS Twitter app. We've seen this first hand, and it is indeed rather odd.
No amount of refreshing, rebooting or force-closing fixes it. Thankfully though, there is one fix that works, and it's really rather simple...
I've been trying to update my iPad over the air to iOS 5.1 ever since it was released this last Wednesday. Unfortunately, it kept throwing an error saying "Unable to Check for Update. An error occurred while checking for a software update."
At first, I assumed that Apple's servers were being slammed, but it's now been two days and I still couldn't update, constantly getting this "unable to check for update" error.
So I decided to plug my iPad in to update it the good old way, you know, using iTunes. But iTunes was not very cooperating either as it kept throwing this error: "There was a problem downloading the software for the iPad. The network connection could not be established."
After a bit of googling, I found the solution to my problem:
Last month we showed you a way to fix your iDevice's white app icons after jailbreaking, but did you know that you can perform a similar fix with Springtomize 2?
Since most jailbreakers probably already have Springtomize 2 running on their device's, this is a very convenient method for cleaning up those annoying white app icons that rear their ugly heads post jailbreak.
Check inside for the full how-to...
Ever since I jailbroke my iPhone 4S using Absinthe, it has been behaving a little weird, sometimes displaying white icons or even transparent icons for certain applications. It seems that this issue only affects Apple's stock applications such as the Phone app, Calendar, etc.
I can't really pinpoint the issue. Is it because of Absinthe? Or is it because of a package I have installed from Cydia? While I'm not really sure what causes this problem, I have found a simple trick to fix the blank or missing icon dilemma...
The Absinthe jailbreak for iPhone 4S and iPad 2 was released a few minutes ago. Of course, we were right on it and we already posted a tutorial on how to jailbreak the iPhone 4S or iPad 2 using Absinthe.
While I haven't had any problem running the jailbreak – well, I had it a few minutes before everybody else – it appears that some users are having a problem when launching the Absinthe app installed on their device, which returns an "error establishing a database connection".
We have a fix for that...
If your iPhone is jailbroken on iOS 5.0.1, and you use iBooks, chances are you've encountered the dreaded "Configuration Error".
No worries though, as both RedSn0w and Corona have been updated to remedy the issue.
Inside, we'll show you how to use the Corona package from the Chronic Dev Team to fix the iBooks issue on jailbroken 5.0.1 devices.
Hot off the heels of the Corona iBooks fix, MuscleNerd tweeted that RedSn0w has been updated to 0.9.10b4 to incorporate the fix for Apple's mobile book app.
The good news for current RedSn0w users is that all you have to do is rerun the new version over your existing jailbreak in order to receive the fix.
The release of the Corona untethered jailbreak for iOS 5.0.1 hasn't come with its fair share of problems, which led the Chronic Dev Team to update the tool a couple weeks ago to fix the Launchctl error.
Unfortunately, this update was not enough to fix all the problems inherent to Corona. The main issue that users have been experiencing is with the iBooks app, which would just display an error message at launch. We shared a few workarounds with you to fix this problem, but we knew an official fix was on the way...
Having trouble with iBooks on the latest Corona untether for iOS 5.0.1? Never fear, pod2g has said that an update is coming to resolve issues with iBooks crashing on iOS devices running the Chronic Dev Team's latest jailbreak.
We've already told you how to fix issues with iBooks on iOS 5.0.1, but those of you that are still having trouble after using Corona can look forward to pod2g's upcoming update.