I may use this blog to post mainly iPhone or software related articles, but I am an electrical engineering student, and as an EE, I love me some good, clean hardware. Therefore, when my favorite pair of earbuds kicked the bucket the other day, my first thought went to the in-box iPhone headset and, more importantly, how much those earbuds suck. My favorite bang-for-the-buck earbuds EVER are Skullcandy Full Metal Jackets, primarily because I got them at TJ Maxx for $25. In general though, they have silicone pads that seal out sound, instead of the hyper uncomfortable iPod earbuds that fall out and sound like crap. I was super bummed when my FMJs broke, but luckily, the part that broke was on the plug end of the earphones. That is, both earbuds themselves still work fine, only the plug is dead. My thought was to cut the crappy iPhone buds off their cable (which includes a microphone and remote button) and graft on my beloved FMJs.
Category: Technical Articles
Ok, lame title, I admit it. That doesn’t change the annoyingness of the error though. Here’s the story: I sit down last night to watch the Oscars and get my feet wet developing for the first time in maybe a month or two. I go to debug an app on the device, you know, to see if I’ve still got it, and lo and behold a big hairy error pops up:
6 days ago: “So Ustream just released their viewer application in time to live stream the innauguration tomorrow at 10AM. The problem is that it only works on a WIFI connection, I’ll assume for now because of ATT no-streaming-video-over-3g restrictions. If that’s possible, never fear, VoIPover3G to the rescue! The only hurdle is figuring out Ustream Player’s bundle identifier to feed to the hack. The whole process, including the less-than-trivial bundle identifier location, is detailed here.”