Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

mk808b and Crackle. Is it possible?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    mk808b and Crackle. Is it possible?

    I've had an mk808b for a few weeks (v4.2.2). It's my first android device except my phone (which I only use to talk and text on). I have Netflix installed and working. I have Crackle on my PS3 and would like it on the tvstick. I found it in the Play Store, but it "doesn't support my device". I downloaded and installed an apk and everything works with the exception of actually playing the content. I can search and select movies, but when they should start playing the screen just goes blank. I've Googled around and not found anything helpful regarding Crackle and TVSticks. Am I missing something simple? Is there a better forum for this kind of question/problem? TIA

    #2
    I'm almost positive I saw Crackle as an XBMC addon in Flumpster's XBMC. Someone else had trouble with the Hulu app and they said that accessing it through the XBMC addon did the trick. Use the regular version, not the launcher: http://www.freaktab.com/showthread.p...BMC-(Beta-3-3)

    Also, you can spoof your Device Manufacturer/Model information using build.prop editor on Google play store ( https://play.google.com/store/apps/d...ld.prop.editor ) so that the Play Store will see your device as a Samsung Galaxy S3 which has more apps listed as "compatible". Here is a quote by mo123:

    4. Change build.prop to ro.product.model=GT-I9300 and ro.product.manufacturer=Samsung
    from ro.product.model=mk808b and ro.product.manufacturer=Rockchip
    Finless' ROM's have the build.prop set up like this by default.

    Comment


      #3
      Gracias

      Thanks for the quick response Bueno! I think I'll try the build.prop spoof first and let you know how it works out.

      Comment


        #4
        I didn't have any good luck with the build prop spoofing. I installed build prop editor and made the changes suggested. Deleted cache and data from App Store and rebooted. It still said my device was unsupported. I did find a newer apk, downloaded and installed that. Crackle now works, but it constantly stops to buffer. This seems to be a common problem with the android crackle app when I googled it. The PS3 app doesn't have that problem though.

        Comment


          #5
          Originally posted by Sourwood View Post
          It still said my device was unsupported.
          Are you sure that you changed both model as well as manufacturer information?
          Maybe you mixed it up and put Samsung in the ro.product.model and GT-I9300 in the manufacturer?

          Currently I am using Prahjister's ROM and it spoofs Galaxy S2, which comes up as incompatible. I gave you instruction for the S3 which you can see is showing up as compatible:



          All of those are the MK808B using different roms... Even "Rockchip / MK808B" looks like it works as long as the capitalization is correct. Make sure you did the caps and that the "I" in I9300 is in fact an upper case I and not a lower case "L".

          Comment


            #6
            Have you tried the latest crackle apk (i think version 4.04)?

            Comment


              #7
              Originally posted by phinc View Post
              Have you tried the latest crackle apk (i think version 4.04)?
              Yes, that's the version downloaded most recently. It suffers from a buffering problem that makes it impossible to watch.

              Comment


                #8
                Originally posted by Sourwood View Post
                Yes, that's the version downloaded most recently. It suffers from a buffering problem that makes it impossible to watch.
                But that really isn't the fault of the app... its an indication that there is a bottleneck elsewhere... either the server is overloaded and slow or the internet connection itself is restricted. People often think ( incorrectly ) that buffering issues can be overcome by overclocking... again that doesn't help either because the cause is in the network ( ie server and/or internet ) and not the device trying to display the video.

                Comment


                  #9
                  Originally posted by rdsok View Post
                  But that really isn't the fault of the app... its an indication that there is a bottleneck elsewhere... either the server is overloaded and slow or the internet connection itself is restricted. People often think ( incorrectly ) that buffering issues can be overcome by overclocking... again that doesn't help either because the cause is in the network ( ie server and/or internet ) and not the device trying to display the video.
                  Maybe not, but there are tons of people complaining about Crackle buffering on android if you google it. Do you use Crackle on android? I have it on a PS3 using the same network as my android machine and it works fine on the PS3. That same android machine works great with Netflix.

                  Comment


                    #10
                    Use the xbmc addon. I tried this one and it works very well: http://www23.zippyshare.com/v/53953421/file.html

                    Sent from my GT-I9100 using Tapatalk

                    Comment


                      #11
                      Originally posted by Sourwood View Post
                      Maybe not, but there are tons of people complaining about Crackle buffering on android if you google it. Do you use Crackle on android? I have it on a PS3 using the same network as my android machine and it works fine on the PS3. That same android machine works great with Netflix.
                      I usually use the XBMC add-on instead of the Crackle app itself... but the app doesn't have buffer issues on my device either... I only see a buffer on occasion when coming back from a commercial

                      The issues you may read from a search ( Google or otherwise ) are only relevant if they are also posting about how quick their internet connection is... which I doubt since most aren't technicians and don't think about the requirement needed.

                      Test your internet download speed... if it's less than 6mbps ( 10+ is better of course ) then you have probably found part of the cause. I say "part of" because it still also relies on the server to serve up the media.

                      Comment

                      Working...
                      X