1. lonndoggie's Avatar
    So, once again, a "custom" ROM renders MLB At Bat incompatible with a device that wasn't using a stock ROM. If you have the latest leak, and try to find "At Bat 12" in the Play store, you'll only find the lite version, not the full version.

    The short-term fix in the past was to edit /system/build.prop to have it mimic, to the play store, a build that does work. I've looked around for advice on what to change, but so far the things I've found aren't working.

    Fortunately, I'd backed the app up along with everything else before I installed the leak, and the restore is working fine. but I'm going to miss any app updates.

    If anyone else figures out the magic combination of build.prop settings to allow At Bat 12 (and other apps--it's not the only one so affected, but the only one I'm looking for right now), let us know.
    05-14-2012 08:43 PM
  2. piizzadude's Avatar
    I cannot really help you with the build.prop but I wanted to say you have your terms mixed up.

    A Custom ROM is one that is based off of the official or unofficial builds put forth by the manufacturer or google which ever the case may be.

    A leak is generally and unofficial build that was "found" by someone (or given to someone). This is a preliminary build working up to the fully functional "official" release.

    If you are working off a leak, or even a custom rom BASED on a leak, you are guaranteed to have some issues here and there. That is why it is a leak and not an official build and released OTA.

    I know they may seem similar, but they really are two different animals of the same species.

    Custom ROMs do not need a bad name, the developers work hard on them, hence me throwing this out there.
    05-14-2012 10:23 PM
  3. piizzadude's Avatar
    05-14-2012 10:25 PM
  4. piizzadude's Avatar
    The app says that the ReZound is supported, so your actual beef needs to be with google play.

    MLB.com At Bat 12 | MLB.com: Mobile

    If you scroll down to where the android app is, you will see the rezound listed. This isnt a ROM issue at all
    05-14-2012 10:42 PM
  5. lonndoggie's Avatar
    Hey piizzadude, thanks for chiming in, but let me try to clarify things for you, and fill you in on something I hope you never have to deal with...

    First, I didn't mean to denigrate the fine work of all the custom ROM builders, sorry you misread it that way. Note how I put the custom in custom ROM in quotes? Because it's NOT literally a custom ROM, nor is it stock. It's a leak, and I said as much. In the future, I'll refrain from using custom in this manner, as I realize many may not comprehend such subtlety.

    It's splitting hairs to define this as an app issue or a ROM issue, because the fix can be implemented on either side. The problem is that MLB At Bat is very particular about what devices it works with at all, and of those, which support live video (a different problem). They put restrictions in the market as to what devices and OS versions they work with, so if your phone doesn't meet their criteria, the Play store will show it as not compatible. So, the two ways of fixing it are (a) have MLB change their criteria, or (b) edit your build.prop so that it matches their requirements.

    When I had a DROID Charge, I installed some of the leaks that Team Black Hat procured. This would typically render MLB At Bat 11 (last year's version) unavailable, due to this mismatch. As I do now, I then had TiBu backups that I was able to restore, which worked, but I couldn't get updates on my Charge, even though I could keep getting them on my old OG DROID! There were several places you could find the necessary changes for build.prop, which others, who didn't have backups, would use. Fortunately, over time, MLB would change their app requirements to allow the Charge to get the updates, and all was well.

    Note that this wasn't the only app that was rendered unavailable by those leaks; there were several game apps that were affected the same way by the Charge leaks. I don't doubt there are also other apps so affected by the Rezound leak as well.

    For MLB At Bat 12, this problem has been hitting non-VZW gnex users, too, when they got updated to 4.0.3 and 4.0.4. Hrm, maybe that's the mismatch, the OS rev...

    In any case, I'm happy to report that, as of today, apparently MLB made an update, as now I can see it in the market! If it was the acceptance of 4.0.3 (which is what the leak is) and 4.0.4, then maybe that's it, and as such the gnex users are in luck again (it worked for them with the earlier release of ICS, just as it did for my Rezound prior to installing the leak).

    One more thing--when I first bought this year's version of the app, live video wasn't supported, and the Rezound wasn't listed as "supported" (which literally means live video support). I complained to them, and after a short while, it started working--yay! At that time, they still didn't list the Rezound as supported, but eventually they fixed that.

    And now it's all 100% good. Until the next release, maybe.




    Yes, that xda thread is one I was referencing; I'd tried some of the things mentioned there and elsewhere, too. I've posted in that thread today that the Rezound is now good with the leak (and possibly any other ICS ROMs that were having issues).
    05-15-2012 05:12 PM
  6. MustangDan74's Avatar
    Nevermind. I saw you got it now.
    05-18-2012 01:27 AM
  7. piizzadude's Avatar
    I stand corrected and just a bit flabbergasted/educated.

    If I read everything that you are saying correctly, then it really isn't the phones issue, but, as you stated, a ROM issue. THe issues isn't 4.0.3 on the rezound but 4.0.3 its self.

    Kinda messed up. Most apps from what I know are supported or not due to hardware, software didnt matter that much. THis one is apparently very concerned about the software once it says the hardware is good.

    Very interesting and thanks for the enlightenment.

    Can I blame bud selig for this one too? He messes up a ton about baseball...lol
    05-18-2012 09:17 AM