If you’re one of the recent ones who has upgraded to iOS 9 and also happens to listen to podcasts using the native Podcasts app, you are now out of luck. Podcasts now crashes on most devices while booting.
Upon opening Podcasts, most users see the notification “Updating Library…” which is subsequently followed by the app crashing.
Deleting all podcasts and restarting the device does not seem to work.
Apparently Podcasts and iOS 9 do not get along. This has been a known issue since iOS 9 Beta 1, but apparently Apple decided to proceed with development and release of iOS 9. Podcasts app crashing is apparently an issue on the following devices:
- iPhone 4S
- iPhone 5
- iPhone 5S (personally tested)
- iPhone 6
- iPhone 6 Plus
For a solution to the Podcasts app crashing, let’s all make sure that we let Apple know about the problem with Podcasts in iOS 9. Report podcast crash bug to Apple.
The evasi0n team claims to have finally made a working jailbreak for iOS 6/6.1. This comes months after the release of iOS 6.
The team has outlined many of the requirements that will be attached to the tool once its released. First and foremost, the jailbreak will be compatible “with all iPhone, iPod touch, iPad and iPad mini models running iOS 6.0 through 6.1.” Yes, this means the first iPhone 5 jailbreak tool is on the way after more than three months of waiting.
It appears that the jailbreak tool will only take five minutes to install and get running on a device and that it will indeed be available to those running OS X, Windows and Linux. Windows XP will be the minimum for Windows users, Mac users will need at least OS X 10.5 and Linux users will need to be running or x86 / x86_64 or higher.
They also make it clear that a USB cable will be needed for the process as well.
Check the evad3rs site frequently for the release:
Are you a home brewer? Do you like beer? Would you rather pour beer from a tap than from a can or bottle? If you answered yes to any or all of those questions then you need to visit Keg Outlet. They’ve got a great selection of corny kegs and other kegging equipment that will help you get up and running to serve draft beer at home.
With the release of Google Product Listing Ads, many e-commerce companies have been left scrambling to figure out how to not lose all the traffic that they currently get from Google Products (previously Google Shopping). However, the problem is that many people and companies have had problems getting their Product Listing Ads to even show on Google, and it has been even more difficult for Multi-Client Accounts within Google Merchant center to get their product listing ads to show.
I’ve been trying to setup PLAs for a client, but have had no luck thus far. I’ve successfully linked my Adwords account to my Merchant Center account (successfully is a relative term), but upon trying to create PLAs from within Adwords, I am constantly given the following error message:
This target does not match any products in your Google Merchant Center feed.
I’m having a hard time trying to figure out if it the multi-client account within Google Merchant Center that is causing the problem, or if I have another problem with the configuration somewhere. I feel like this is going to be an ongoing battle.
Product Listing Ads are a great idea in theory, however it is really going to hinder small companies who don’t have the time and/or resources to put toward creating, managing and spending money for product ads.
Ira Rubin, a man accused of helping online poker companies move and cover billions of dollars in illegal gambling proceeds overseas from U.S. customers was sentenced to three years in prison Thursday by a New York judge. The judge called him an “unreformed con man” who has a long criminal history.
U.S. District Judge Lewis Kaplan handed 54-year-old Rubin one of the longest prison sentences yet in a prosecution that resulted in charges against nearly a dozen people and shut down the U.S. operations of the three largest Internet poker companies. Online gambling in the U.S. was thwarted in 2006 when the house and senate passed the Unlawful Internet Gambling Enforcement Act of 2006.
The authorities said that Rubin fooled U.S. banks into processing gambling proceedings by making it appear that money moving through the poker companies was actually the proceeds of transactions on websites for golf stores and other legitimate businesses, which it was not. If you miss playing online poker, but are still looking for some online gaming, try playing bingo and other online role playing games at www.partybingo.com.
Spotify uses too much hard drive storage space. They cache most of your songs, and use upwards of 1gb of drive space. They do this only to reduce bandwidth to their servers. If you have an enormous hard drive, this isn’t as big of a deal (though I still don’t like when programs use more resources than they need to).
But if you have an ultrafast SSD (such as the 60gb one I have), then hard drive space is once again at a premium. The following simple steps will allow you to limit the space Spotify uses, freeing back up your disk space, while still allowing Spotify to work just fine.
STEP 1: Eliminate the current cache
Open windows explorer and navigate to:
… replacing [computer username] with the name you are logged into Windows with. Note: you may have to first set explorer to display hidden files to see all the files.
Delete all the folders / files in this directory.
STEP 2: Manually edit the settings file
Since Spotify’s preferences only allow you to set the minimum storage space at 1 gb (i.e. 1024 mb), you’ll have to manually edit the settings file to set it lower. I’d recommend no lower than 20 mb, in order that at least the current song you’re listening to and a couple more can be cached. I’m using a value of 50.
Once again in windows explorer, go to:
Open the file “settings” in Notepad. Find the phrase “cache_size”, and change the value following it to your desired size. Example: “cache_size”:1024 ** changed to ** “cache_size”:50
These instructions are for windows 7. Another OS should only differ in where these files are located.
As with anytime you are editing files, backup the original files first (e.g. copy and rename to “settings.old”).
Upon doing a little research, I realized that this was a fairly common problem that quite a few people had run into, however, my solution was not the same as all the solutions that I found. One solution that I found online was to not use the minified version of s3slider. The minified version of s3slider apparently contains some errors, so using the default version will oftentimes solve whatever error you’re receiving. If this solution doesn’t work for you, you may have the same problem I was having. My problem stemmed from where s3slider was being loaded on the page. It was being loaded before the jQuery library was being loaded. By updating my HTML to load jQuery first, I was able to resolve the issue.
s3slider is not a function in my case was the error being caused by the jQuery library not being initialized first. Easy fix, by just moving the s3slider.js file above the jquery declaration.
I recently started encountering a problem with OS X Lion. I’m running a pretty sick Hackintosh setup that has always operated without problem. Then recently, out of nowhere, Google Chrome has suddenly started to cause my computer to crash. I get the gray screen prompting me to reboot my computer. Upon rebooting, if I open Google Chrome, my computer will crash again. If I leave Chrome closed and use Safari instead, everything runs fine. I know the simple solution is to stop using Google Chrome, but that’s not really a solution for me. I like Google Chrome. It is the 1 browser that is most similar between Mac and PC, so it is the browser that I choose to use on my work and personal computers.
Has anyone out there encountered a problem when running Google Chrome on Mac OS X Lion? If so, have you found a way around the crashing issue?
The odd thing in all of this is that the crashes do not even generate error/crash dump reports. So I guess I really don’t know that it is Chrome that is causing the crash, but I’ve been using my computer for 3 hours without incident. I’m writing this post in Safari. I’m fairly certain that opening Chrome will cause my computer to crash.
Yes, opening Chrome did, in fact, cause my computer to crash.
So I’m not sure why this is, but I had previously updated my iTunes libraries to “match” so that I could sync my iPhone to 3 of my computers – my laptop, my home office and my office computer. It worked fine, but with the release of iTunes 10, Apple has apparently nixed this and I haven’t wanted to test (waiting for some other poor sap to try), so I’ve just been plugging my phone into each computer seperately as always, there are some things that puzzle me though.
My home desktop computer is now new, doesn’t have a matching iTunes library ID #, however when I plug my iPhone in to it, I am still able to manage pictures, music, movies, etc. I can copy anything that I want to/from the phone. When I click the “Sync” button on the bottom right from the iPhone Summary page in iTunes, the phone runs through its normal syncing process. No problems at all. Same thing when I plug it into my laptop of office computer. Weird, right?
Update on Syncing to multiple computers
So I found out what is happening. You ARE able to sync/copy content form multiple computers (it seems), however you cannot change settings on your phone on a computer other than the main computer that your phone is synced to. When I try to change the setting “Manually manage music and videos” from unchecked to checked, I get the following message:
Does this make any sense? I don’t know why Apple doesn’t just remove their restrictions.
This is one of my favorite new features of iOS 5 (I’m easily amused). But all joking aside, this feature is very handy, especially when you leave your phone for a couple hours and it gets bombarded with texts, twitter updates, calendar notifications, etc. Regardless of what is on the lock screen, you can simply swipe the icon of the notification that you want to see and iOS 5 will take you directly into the proper app, and if necessary, the proper page. Try it out next time you get a notification!