In case you’re a klutz…

Just in case you’re a klutz like me lately and have a Raspberry Pi this link is for you.

I essentially followed the steps listed on the page this morning and will confirm that the solution indeed works tonight. One side of the SD Card holder on the Pi is a rather thin rail which obviously is quite easy to damage based upon results I get when searching on Google. The end result may not look nice but if it functions that is all I’m concerned about.

I should make a case or perhaps just buy one for the Pi. Of course this is exactly what I was thinking as I watched my Pi fall to the floor. If all else fails there is always using a clothes pin to keep the SD card in place.

Hopefully the next version of the Pi has a more enclosed SD card holder, suppose I could get creative and replace the one with a better one though I don’t feel like dealing with soldering these days.

Update: The solution didn’t quite work for me as it doesn’t create enough pressure on the SD card. I’m going to tweak this approach by sanding down the edges so that the piece of plastic sits lower in the socket.

Update to the update: Dremel to the rescue. Sanding down the thickness of the plastic that you’re adhering to the SD card holder to roughly 50% the original thickness appears to be the right amount of pressure needed for the SD card to seat properly. Looks like a hack but it works and that is all I care about.

Android #Fail

It appears that going to a test URL with a certain iframe using the stock Android browser can perform a factory reset on the phone.

There was a URL posted in the XDA forums pointing to to test whether or not the browser would invoke the dialer and present the IMEI. It worked on my Samsung Infuse 4G running stock Gingerbread so I’m guessing that a real exploit may factory reset my phone. Ugh…

Note: The link above could change at anytime to the real exploit, use at your own risk. Here is the content of the test page.

<!DOCTYPE html>
<frame src=”tel:*%2306%23″>

The exploit code uses:
<frame src=”tel:*2767*3855%23″ />

Nice huh?

Reports have said it affects mainly Samsung devices but other reports have indicated an old Android bug affecting multiple devices. Should be interesting to see how this turns out…

Update: Confirmed that my Samsung Infuse 4G running Android 2.3.6 (Gingerbread) is vulnerable.

Link for exploit as well as other pertinent information:

Samsung Infuse 4G Vulnerable to Exploit (YouTube)


1:12 – Phone Model / Version
3:56 – link clicked, dialer launched, performs format/reset
4:20 – reset
6:35 – files/folders gone

NoTelURL app to install to prompt user on action to take.

Another app ESET USSD – will protect you from this exploit.

AWS Glacier

Someone keeps reminding me of this service. Perhaps something to add to the ultimate backup solution?

I’m all about the CLI so this looks interesting as far as clients go.

38 Days

Vg’f orra 38 qnlf fvapr zl ynfg phor zbir. Jr’er ba gur sbhegu phor fvapr Wnahnel 2011. Gur ovt obbx bs znantrzrag zhfg unir puncgref sbe guvatf yvxr guvf. Qb V arrq gb fvg pybfr gb gur erfg bs gur grnz? Qb jr whfg zbir nebhaq gb vaqhpr hapregnvagl? Gur yvtugvat va guvf arj phor gbgnyyl fhpxf (gbb oevtug).

Jul qvq lbh yrnir lbhe ynfg cbfvgvba? V qvfyvxrq zl phor – jvyy gung ubyq hc?


A Post a Day?

Coincidence or what? It’s been a month since leaving Facebook so perhaps I need to post things somewhere? I dunno. I would post more but a lot of what I want to post probably isn’t too appropriate. Nothing new otherwise, glorified file editor as of recent. (harsh?).

US-CERT Alert TA12-262A – Microsoft Security Advisory for Internet Explorer Exploit

Short summary: Quit using IE? Great job Microsoft.

What is totally sad is companies forcing users to continue to use IE since that is the only “supported” browser for sites/apps. You know who you are companies.


Intriguing but not sure yet..

more later

Update: proved to be more of a pain to get working on OEL/RH 6.2 than worth. As commented just use screen.

1390226400 – sometime it can’t come soon enough.

Days like today and most of last week.

CM10: The good, the bad, and the ugly.

And while back I noticed that there were some nightly CM10 builds out for my cappy (Samsung Captivate) and I’ve given them a try a couple times to see what Jelly Bean (Android 4.1.x) was like, more specifically to experience Google Now. Well given the title of this post I might as well say the good is that the ROM actually flashes fairly painlessly. You do have to reinstall apps and setup accounts which is to be expected given using another release of Android. So far the bad is that something is broken in the media scanner services as after the setup none of my media such as pictures, music, and videos show up in apps such as gallery, Google Music, etc… There are several posts indicating this was some sort of ROM Manager issue with .nomedia files but the solutions to resolve those issues were not applicable to my scenario. What it appears to be the issue is that media scanner is somehow dying and not scanning the SD card correctly. I’ve formatted the SD card and copied some files back to the SD, cleared data in the Media Storage app and rebooted. Yet no luck so I’ve reverted back to CM9.1 for sanity. For the ugly, I suppose the bad is partially the ugly since it’s annoying. Thankfully restoring from the nandroid backup makes it fairly easy to get back to stable, well until you start formatting the SD card of course ;).

It’s only been a couple of weeks since nightlies started so hopefully in the next month or so the issue is resolved. It appears that some are not experiencing the issue so perhaps certain device specific type of issue. I’m just amazed the CM team is still supporting this two year old device and surprised how well CM9 runs on it considering the older hardware.

Update: The issue has been resolved by deleting files created by Camera 360 (C360*.*). Once those files were removed all the media on my device is showing up. I posted this to the following forum and it has helped others as well.



So… Finally got around to trying out Plex Media Server. First impressions, it’s pretty cool and probably the most complete media server I’ve experimented with so far. I had been using a simple DLNA server (minidlna) on Linux to make files available to devices on the home network but after a recent upgrade on the tablet I noticed that AllShare no longer could play files due to a generic error “Unsupported file format” the app returned. I know previously AllShare worked but on the ICS build it would report the file format of */* and no file size. The AllShare app on my phone worked for the most part (it’s also a bit buggy but at least works after a couple of tries). Regardless I have always thought I needed to find an alternative to AllShare since I don’t like to depend upon manufacture specific apps on mobile devices.

So while looking for alternatives I recall seeing something about Plex Media Server being available for Linux (more specifically Ubuntu) and starting looking for a possible version that would work on Debian. I found at and was able to get installed and running. Surprisingly adding my media locations to the web based console was easy and it’s pretty cool how it pulls all the meta data in from the internet. I’d say nearly 90% of the files were identified correctly. A few I just need to rename in a specific way to help the scanner and finally a few I just used the web UI and selected the correct information.

One huge advantage of using Plex is that we can stream media to the iPad regardless of the source file format since transcoding automagically takes place. The price of the app is surely worth the $5 as it looks wonderful and is by far the best media app I’ve seen as far as usability and  experience.

The only negative I see at the time is dealing with the Plex Media Server files on the Linux side due to many paths / files having spaces within the name. Not really a big deal since I hope not to spend much time on the backend other than the occasional apt-get update. In hind-sight it probably would have been better to throw this on a VM rather than the bare metal hardware but we’ll take care of that after Wheezy is released and I rebuild things in a more streamline fashion. Corrected (2012-08-25). Plex is now running in a standalone DomU. For anyone interested the migration was as easy as copying the contents of /var/lib/plexmediaserver to the new server.