Unable to download HBO GO app...

Hi,

Just got the Charge yesterday; went to download HBO GO; both from phone and on pc and was given the message:

"This app is incompatible with your Verizon Samsung SCH-I510."

I don't think this is true. There's a youtube video http://www.youtube.com/watch?v=OHntYCJzfbk that shows the HBO GO app being run on the Charge. Also, the VZW rep at the store even mentioned the app to me yesterday when I was buying the phone.

Any suggestions? Should I return to the store? Does the phone need to be replaced?

Thanks.

Accepted answers

unknown

The applications on Android Market are managed by the app developers directly. Sounds like HBO needs to update the application to support the latest s/w update on the Charge. Once they do, you'll be able to downloaded it again. I recommend reaching out to HBO directly.

Have a great day!

All comments

pcnorth22

i.e. has anyone been able to download the HBO GO app to the Charge?

Coronabill

I downloaded it prior to the EE4 update. It still works, but is no longer available from the market as it says it's now incompatible... :smileysad:

vidguy7

It's being reported on a number of forums that something broke with the EE4 update and the Android Marketplace. These reports are 100% correct. Before Verizon exchanged my Charge, I had HBO to Go on that phone and it worked fine. I was going to download HBO to Go on my new Charge and I don't even get taken to that app when I go to the Market. It's as if it doesn't exist even though it shows up in the search. When you hit the 'HBO Go' in the search, it takes you to totally different apps. There is actually no HBO app that shows up.

I was at a Verizon store today and they had a beautfiul example of it with their display Charges. One had received the EE4 update and the other didn't. The one that didn't have EE4 update had clear access to the HBO app and the other with the update behaved just like mine.

So Charge owners are now being shut out of a number of Apps. One thread mentioned TMZ and I checked and found out that too is invisible to the Charge.

Ray999

:smileymad: This really bites. Could it be that someone is trying to boost the usage of Media Hub or the VCr*p? Just had to ask.

pcnorth22

Is it safe to assume then that this will be fixed? I enjoy the phone so far...but definitely want something that will run hbo go. Thanks to everyone for their input. Glad to hear i'm not going crazy.

vidguy7

I think (hope) it will be. VZW does read these boards and if it's not their issue, I'd like to think they'd contact Google and have them get the Marketplace fixed. Afterall if you carry these phones, you do share in the responsibility of having them functional.

unknown

Have a great day!

lonndoggie

It's funny, each side is pointing at the other, and no one will actually go and have a look at their side of the problem.

I have MLB At Bat 11 installed on my Charge. Works great.

However, since some combination of EE4 and Google implementing hardware compatibility filtering, At Bat 11 is now invisible in the market to me (I can see it in http://android.market.com, which shows that it's compatible with my old DROID, but not with the DROID Charge).

I sent a help request to MLB. They said it's a problem with the market.

I sent a help request to the market folks. They said it's a problem with the app.

VZW here now says also it's a problem with the app.

The truth is, it's a problem with the intersection of the app and the device, detected by the market.

The app lists what device features it requires.

The device is registered with Google as to what features it supports.

If an app needs a feature and a device doesn't list it, then the market calls it incompatible.

MLB At Bat 11, most of GameLoft's titles, EA's FIFA 10, XX1090 Sports Radio, Touchdown's license key, HBO GO and no doubt dozens more--all perfectly capable of running on the Charge--ARE UNAVAILABLE TO CHARGE OWNERS.

This makes the Charge a truly craptastic device. My old DROID, right now, is more capabie.

Figuring this out is going to take at least one of these app makers to go into the Android developer console to find out what the Charge is being rejected for. It may be legit--if so, it truly is a crippled device. However, my guess is that there is a capability omission that Samsung or VZW needs to update the market with, to allow these apps to install.

But, again, everyone just points the finger and says "Nope, not our issue".

vidguy7

It makes me see the wisdom in the Iphone and the iron hand that Apple has with its apps. Yeah, I like the Charge more as a device (if it worked properly), but there are many pitfalls to all these parties (VZW, Market, App Developer) pointing fingers at each other.

To be perfectly honest, IMO Verizon should be leading the charge (no pun intended) to solve this issue. They are selling a device that is advertised to be compatible with the apps that show up on the marketplace and this is no longer the case. It's obviously not just Verizon responsible for this, but let's see, who carries more weight with the Marketplace & the Developers, us or Verizon? Hmmm. Whose voice is more likely to be heard? Hmmm.

lonndoggie

[Edited to comply with Terms of Service]

SOMEWHERE in Android-land there is a database of android devices/build revisions.

When the Market app sends a request for apps (search, My Apps, whatever) it sends along what device/build rev is asking.

It filters the result based on the capabilities of that device/rev.

The feature information for the Droid Charge/EE4 is missing something. Or things.

I've gone to the Samsung support site for the Charge, but pretty much nothing works, as far as being able to ask questions.

I've also send an "info" into Droid Life, asking that they post an article about this--nothing yet.

VZW--you've crippled your phone! Trying to light a fire somwhere to get this fixed!

Coronabill

They now seem to be available in the market again.(MLB at Bat, HBO to Go, TMZ, etc...) :smileyvery-happy:

lonndoggie

YES!

I'd REALLY like to know what the fix was!

Thanks--

vidguy7

Yup, confirmed, it is fixed. Whoever was responsible, thank you.

Maybe this is one that can be legitimately marked as 'solved'. :smileywink: