« Netflix Quietly Adds Subtitles in Latest iOS Update | Main | Are You Having Queue Troubles with TV Shows? »



Wow! Actual "hacking" on Hacking Netflix.

How odd that NF is only checking what the phone reports itself as. It be interesting to see what it works and doesn't work on. Probably a processor limitation.

Brett Cochran

Doesn't work on my Droid OG running CM 6.1.2. Guess I will have to update to GB or CM7.

Jeremy Sheehan

@Brett Cochran - I'm surprised you're still on CM 6.1.2. CM 7.0.3 for OG Droid has been out for several weeks now. It's solid.

Honestly, this hack doesn't seem very safe. I wouldn't feel very comfortable with changing this setting.

Check out this link. I don't think you have to edit the build.prop file to install this. This is an XDA tweaked app. Go team Android!



Really promoting a crime now?

Jeremy Sheehan

@BP108 - What crime are you referring to?

Just installed and didn't play movies on my OG Droid. Disappointing. I'll have to try at home to see if it works from a wifi connection.

Roy Rapoport

Well, that was about ten minutes of fun.

On my new (Netflix-funded, amusingly enough) HTC Thunderbolt, followed the directions (the Thunderbolt's not one of the supported platforms). Installed the app, tried to play. Everthing I tried to play played for about 1/2 second, then would crash out and bring me back to the main screen.

Oh well. So I figured hey, let's change the phone's build.prop file back to what it was, to avoid unforeseen problems. Launched ES File Explorer again and ... it reported it couldn't mount my SD card over and over again, and didn't let me do anything. Crap.

So I uninstalled ES File Explorer, reinstalled it, and attempted to enable root ... only to be told that my phone (remember, it was no longer identifying itself as an HTC Thunderbolt) was not supported for root operations. D'OH!

In the end, I resorted to using adb to download the build.prop file from /system/, modifying it (thankfully, I had no problem accessing the SD card via adb), and uploading it again. All looks well now (and ES File Explorer works as expected).

Which basically suggests that, yes, this is probably one of those hacks one may want to think twice about.



For anyone who has tried this on a rooted Nook Color, did you have any issues doing this with CM7 on an sd card?


How did everyone else log in for comments? I used my twitter account. Only my pic is showing. lol


@ BP:

"Really promoting a crime now?"

What crime is Jeremy Sheehan promoting? He asked and now I'm asking. Don't throw accusations around unless you can back them up.

Jeremy Sheehan

@tester - if you look at BP's profile (http://profile.typepad.com/bp108) he apparently hates Netflix. He trolls on this website as if he has nothing else to do. God Bless the anonymousness of the internet. It allows you say things without fear of retribution.


This is the problem; you shouldn't HAVE to do this trickery to begin with. That's the problem with fragmentation and Netflix not being consistent as well.


I would like to point out that BP108 and I aren't the same person. Wouldn't put it past Jolly to sign up to try and imitate my username, but it could just merely be a coincidence.

Mike can confirm if he wants to.

To address the bulk of (whoever) BP108's (is) arguments, jailbreaking phones and modifying their code has long been deemed legal. There exist exemptions for it within the DMCA and recently the Library of Congress reaffirmed those exemptions. Nothing illegal going on here. Don't be a pillock.


Anyway, I've gotta agree with Roy on this. Hacking an Android phone is kind of a gigantic pain in the ass. The dev tools are fucking stupid (the hoops you have to jump through to get adb to work properly is just dumb) and there exists a high likelihood of breaking something that will be a massive exercise in what will equate to cheesegrating your own balls just to fix it.



@ Jeremy Sheehan:

I did have a look and you are correct in what you've said. Unfortunately there is no accurate way to determine who s/he is. It could be BP, Jolly, or someone else. I have my suspicions but for now I'll keep them to myself


@Jeremy: There is nothing un-safe about making this change to your phone.

@Wilson: It doesn't have anything to do with "fragmentation" (of Android?) so much as it being a hardware issue. It's no different than Flash on Android. Adobe has decided that the performance of Flash on 'older' phones is insufficient. At least in their case, they put in checks that can't be worked around by simply changing a text file !


108 hasn't posted a wall-of-text yet. None of jolly's posts were so concise. The guy had a serious case of oral diarrhea. [I love the picture that invokes. Ewww.]


I am so glad this app finally supports the evo. I just love how people in the market place are giving it one star for it failing to work on an unsupported phone. I think it's great we can hack the android but if I am having problems with an unsupported phone I am not going to blame the developer.


@joe: Sounds like you know how to ignore or weed out the "stupid-user" reviews in the Market ! :)


@ BP:

Hacking your Android phone is no more difficult than hacking most anything else. As long as you are careful and precise in what you do you should not have any problems. You also need to look at the complete instructions very carefully before you start your project. Make sure you have everything you need and if you have any questions or concerns about any of the steps do not do start your hacking until you have, by searching the 'net, alleviated your concerns.

I have been hacking since 1978. I have modded software programs, computers, disc drives, game consoles, discs (yes actual discs) three Evo 4G phones that I own and some other things. About half the time I did my own hacking and the rest of the time I followed someone elses' instructions. Never once did I had any problems.

As far as I am concerned you take the same risk by hacking as you do when you update the firmware on any of your devices.


@ Tester

Reading is obviously not your strong suit. So is not coming across like a condescending prick. Hey, that's something I'm an expert in being, so it appears I'm qualified to comment here!

My entire point in that post was to point out that the tools needed to perform said hacking are extremely obtuse. The Android SDK is universally recognized as being a gigantic piece of dog shit. Hacking an Android phone is easy so long as you are not trying to bake your own rom, which is why easy bake websites have popped up that do the hard work for you. Even so, many of the guides written on how to do this or that are incoherent messes. When you inevitably do fuck something up, and if you claim you've never had any problems ever then you're either full of it or your idea of hacking was running an AoLZ ProGGiE, it will be a massive pain in the ass to fix using the SDK. Most of the time your best bet is to perform a nandroid restore and start over from scratch.

Would you care to explain how, exactly, you physically hacked an optical disc? Because unless you think taking a felt tip sharpie and blocking out the copy protection on certain consoles' discs, which would be a laugh to consider hacking, then I know of no way to hack a physical disc.

Warmest regards!



BP, I don't disagree with what you have said about the current state of Android hacking. But, I stand by what I've said about how someone should go about doing said hacking.

I am sorry to say this but you are wrong when you said "if you claim you've never had any problems ever then you're either full of it or your idea of hacking was running an AoLZ ProGGiE". First, I never was one of those "script-kiddie" type hackers. Between learning disassembly and knowing about electronics/electrical it was a simple matter to do what I did. FYI I was a monthly contributor, for a number of years to a magazine that did mostly software hacking but a little hardware hacking.

I never said I hacked an optical disc, I said a disc. I actually wrote a article on how to add more that the maximum allowed files to a 3.5" Apple disc and I also wrote, but never had published, an article on how to modify a 5.25 disc so it could not be read on a different drive.


Btw, BP, I forgot to mention; I guess reading isn't your strong suit either since you said "Would you care to explain how, exactly, you physically hacked an optical disc?" when I never said that.


Works great on my Nook Color with CM7! So stoked!!!


I've been using the Netflix app quite a bit this past weekend and I am very impressed with it.


Or you could just download the hacked version of the app that has the device check disabled. I'm on a rooted Froyo Droid X and it works fine for me. http://forum.xda-developers.com/showthread.php?t=1076150

The comments to this entry are closed.


Third-Party Netflix Sites