Database Develop

So close...Netflix on Vegan-Tab 5.1.1

Through a lot of searching, trial and error, I finally got Netflix working on my Droid original version. I installed the netflix apk with device checking disabled (you can find it on this forum) and then made just 2 changes to my build.prop file. I set ro.product.model=Droid
and
ro.product.manufacturer=Motorola.
Success!!! So, wondering if I could do the same on my Gtab with Vegan-Tab. Installed the apk, changed the build.prop file and gave it a go.
Almost Success!!! The streaming actually works. I have tried all the other methods and never got the movie to stream. With this one it does.....problem is that it is running way to fast. The audio sounds like it must be 10 times faster than normal.
Another step.....sooner or later I'll find the secret.

If you used the version of the Neflix apk with the device check disabled you shouldn't have had to modify your build prop at all.
I installed it on my Droid X and it ran beautifully without any mods at all.

The device check only gets you as far as allowing the Netflix app to actually load completely. There is further wizardry involved to actually get streaming to occur. I can attest to the fact that I have tried at least 8 modifications of the build.prop file, with the only one allowing streaming to occur being the one that matches my Droid. Honest to goodness and cross my heart.

With disregard for the Netflix apk entirely, does Netflix allow streaming of their media directly from their website? Another words can you simply login to your web based account & access the media there?
I've never used Netflix & have no plans to join, but I figured if I could get the web version of Crackle to work when the Crackle.apk didn't then the same might hold true for Netflix. Of course it doesn't resolve the current problem but at the very least allows one to enjoy streaming until the issue is fixed.

droid x
Took the information posted earlier and, what do you know netflix on the droid x combinded with real hdmi lets make it a movie night.
BIG THANKS

EL TEJANO said:
With disregard for the Netflix apk entirely, does Netflix allow streaming of their media directly from their website? Another words can you simply login to your web based account & access the media there?
I've never used Netflix & have no plans to join, but I figured if I could get the web version of Crackle to work when the Crackle.apk didn't then the same might hold true for Netflix. Of course it doesn't resolve the current problem but at the very least allows one to enjoy streaming until the issue is fixed.
Click to expand...
Click to collapse
When I try to use it through the web browser, it wants me to install the Microsoft Silverlight plugin. No go.

Joeb2751 said:
When I try to use it through the web browser, it wants me to install the Microsoft Silverlight plugin. No go.
Click to expand...
Click to collapse
Hmmm..well that may change in the future then & hopefully it does:
http://thedroidguy.com/2011/04/microsoft-silverlight-coming-to-android-via-moonlight-dev-crew/

chipmunks
Finally got a movie to stream using your settings. Thanks! Same result though, sound is way too fast. After reading this thread http://forum.xda-developers.com/archive/index.php/t-954843.html
Thought about changing ro.board.platform= from tegra to whatever it is for the Droid. Do you know what is listed in the build.prop? Anyway thought it might be worth a try.

Im seeing the sped up video and sound as well here. Using the pre-packaged netflix apk on CM7 nightly 85.

maybe it's just me but when I went into the market today it said that there were updates available for netflix. I downloaded them and now when I run netflix it takes me to the "login" page instead of saying this device is not compatible.

fosser2 said:
maybe it's just me but when I went into the market today it said that there were updates available for netflix. I downloaded them and now when I run netflix it takes me to the "login" page instead of saying this device is not compatible.
Click to expand...
Click to collapse
They released an official update in the Market that doesn't do the device check. I don't know if that means it's wide open now for all android devices or not though for folks that have a Netflix account.

sjmoreno said:
They released an official update in the Market that doesn't do the device check. I don't know if that means it's wide open now for all android devices or not though for folks that have a Netflix account.
Click to expand...
Click to collapse
I saw that too and I got all excited. I do have an acct and could get to it. I can see my que but I can not still stream from there. It goes to the red loading screen but then dumps back out to the que. I have tried it several times. Still no. Close.. it seems.

glinraen said:
I saw that too and I got all excited. I do have an acct and could get to it. I can see my que but I can not still stream from there. It goes to the red loading screen but then dumps back out to the que. I have tried it several times. Still no. Close.. it seems.
Click to expand...
Click to collapse
Not working on Vegan 5.1.1
gTablet Vegan 5.1.1 with Pershoot's 2632.41 kernel

achernez said:
Not working on Vegan 5.1.1
gTablet Vegan 5.1.1 with Pershoot's 2632.41 kernel
Click to expand...
Click to collapse
Yea, I run Vegan v1 b511

sjmoreno said:
They released an official update in the Market that doesn't do the device check. I don't know if that means it's wide open now for all android devices or not though for folks that have a Netflix account.
Click to expand...
Click to collapse
It only added about 3 more phones to the list of approved devices. Install CM7 and all will be good.

glinraen said:
I saw that too and I got all excited. I do have an acct and could get to it. I can see my que but I can not still stream from there. It goes to the red loading screen but then dumps back out to the que. I have tried it several times. Still no. Close.. it seems.
Click to expand...
Click to collapse
Yep, same behavior for me after editing the build prop, running on Vegan 7 RC1, including after the market posted update to the apk.

drbomb said:
Finally got a movie to stream using your settings. Thanks! Same result though, sound is way too fast. After reading this thread http://forum.xda-developers.com/archive/index.php/t-954843.html
Thought about changing ro.board.platform= from tegra to whatever it is for the Droid. Do you know what is listed in the build.prop? Anyway thought it might be worth a try.
Click to expand...
Click to collapse
Sorry for the delay, have been on vacation. I will try that this evening and let you know the results.
Joe

tgruendler said:
It only added about 3 more phones to the list of approved devices. Install CM7 and all will be good.
Click to expand...
Click to collapse
My netflix running on CM7 about 2 days ago was working and now its not apparently because there is a new Netflix Update on the market.
Is there a reason why I can't search the Official Netflix App on the market using my GTAB? My build.prop is already modified to Nexus S. Maybe someone can post the Netflix APK since it is probably detecting my device as not supported.

Same here, using the new app, starts loading, flashes briefly, then back to the queue. Just installed flash 10.3 ,still no go.
On the gtab, ocd
Sent from my UPC300-2.2 using XDA Premium App

samlot said:
My netflix running on CM7 about 2 days ago was working and now its not apparently because there is a new Netflix Update on the market.
Is there a reason why I can't search the Official Netflix App on the market using my GTAB? My build.prop is already modified to Nexus S. Maybe someone can post the Netflix APK since it is probably detecting my device as not supported.
Click to expand...
Click to collapse
Droid-life had a link to the app. I grabbed the one off my phone I grabbed from the market. It didn't work on CM7.02 but I updated to CM7.03 and it works fine. No build.prop edits or anything needed.
Sent from my Viewsonic 10" GTab...CM7 style...

[Q] ICS Stunner apps incompatible?

I've just installed the latest ics stunner rom on galaxy note everything is working great very happy but a lot of apps (most of the good ones) don't show I'n the play store and when on the play google site it says these apps are incompatible with my phone, but there not I know they work and they do if I download the apk. Google tech support say its because I'm using a custom rom :s anyone else have this problem? Any fixes? Thanks in advance for any help.

mikeyy109 said:
I've just installed the latest ics stunner rom on galaxy note everything is working great very happy but a lot of apps (most of the good ones) don't show I'n the play store and when on the play google site it says these apps are incompatible with my phone, but there not I know they work and they do if I download the apk. Google tech support say its because I'm using a custom rom :s anyone else have this problem? Any fixes? Thanks in advance for any help.
Click to expand...
Click to collapse
You running on stock DPI ? 320 or 240 or 160(tablet)mode?

Thanks for quick reply. Im currently running on 200 as seems to work best but I have tryed all settings with full reboot/market data clear etc with no change.
Edit: it seems no one else has this problem, maybe its the chain fire ics repack that's causing the problem? I can't think of any other reasons, is there a newer version of this firmware?

Basically, the market (I refuse to call it "play store") is crap. In Euphoria Control set both dpi settings to 240, reboot, clear market data, reboot, and then you should be able to use the market. I never managed to make it work with DPI other that 240 for more than a day before it craps out again.
There are also hacked vending.apk versions that work with any DPI setting, but they tend to have problems, like not allowing to buy apps.

mikeyy109 said:
Thanks for quick reply. Im currently running on 200 as seems to work best but I have tryed all settings with full reboot/market data clear etc with no change.
Edit: it seems no one else has this problem, maybe its the chain fire ics repack that's causing the problem? I can't think of any other reasons, is there a newer version of this firmware?
Click to expand...
Click to collapse
Market recognizes the apps and device based on the DPI. Use the stock dpi values like 320, 240 or 160 to get apps. After every dpi change and reboot remember to clear the market data. After installing the apps you can switch to the dpi u choose to!! This is the limitation of market and not the rom!
Cheers!

Thank you for this useful information, Abhi.
(Well, it's good manners for someone to say thanks, isn't it?)

Thank you very much I have sorted the problem sticking to 160 dpi with the phone fc fix is working great, I now have all apps accessible thanks everyone

[Q] Two devices appearing in Google Play Store?

For some reason my Nexus 6 is showing up as two separate devices when I view devices connected to my Google account (Google Play Store > Settings > Devices).
This happened after I was running Pure Nexus ROM, then tried the new Carbon beta (which encrypted my phone), then moved back to Pure Nexus. I don't see any way to remove devices from the Google Play Store.
Any idea how to get rid of this?

MrBrady said:
For some reason my Nexus 6 is showing up as two separate devices when I view devices connected to my Google account (Google Play Store > Settings > Devices).
This happened after I was running Pure Nexus ROM, then tried the new Carbon beta (which encrypted my phone), then moved back to Pure Nexus. I don't see any way to remove devices from the Google Play Store.
Any idea how to get rid of this?
Click to expand...
Click to collapse
Same thing on nearly every device where I've flashed a custom ROM. There does not appear to be any way to get rid of them (at least from what I've found). If you go into Settings, you can at least, uncheck them for "Visibility".

cam30era said:
Same thing on nearly every device where I've flashed a custom ROM. There does not appear to be any way to get rid of them (at least from what I've found). If you go into Settings, you can at least, uncheck them for "Visibility".
Click to expand...
Click to collapse
Thanks for the feedback. The strange thing is I've flashed TONS of ROMs on this device. It wasn't until I flashed the Carbon beta that this happened. It's almost like it gave my phone a new device ID. [emoji15]
Sent from my Nexus 6

MrBrady said:
Thanks for the feedback. The strange thing is I've flashed TONS of ROMs on this device. It wasn't until I flashed the Carbon beta that this happened. It's almost like it gave my phone a new device ID. [emoji15]
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes, I've noticed that it only happens on a few ROMs. Don't know why. But it's not like you're not being singled out for special attention.

Pixel / Daydream / VR Apps

Hey everyone,
So I've been trying to "modernize" my phone, since I'm under the impression that I can get another 2-3 years out of it. So far I have:
-Running 7.1.1 stock rooted w/Franco kernel
-Hacked to include Pixel launcher (works great)
-Hacked to include Assistant (works great)
-Hacked to run Daydream (works great(ish)) -These tutorials are all available online and are pretty simple if you kinda know what you're doing
I bought a Daydream headset and have been playing with the apps. Some seem to work fine, and some won't run, some won't install. This seems like pretty fresh territory, so I haven't found much help online.
I know our phone supposedly doesn't meet the intended hardware specs (thermal characteristics, and GPU speed?), but it sure seems capable enough to me.
-Home screen and remote - works no problem.
-Playstore - works no problem.
-Netflix VR - works no problem.
-Arts & Culture - works no problem.
-Asteroids - This is pretty awesome. It's a demo of an animated episode (not the old game). It has 3D sound, which I wasn't expecting since the Netflix VR app didn't have it.
-Youtube VR - won't install (sideload). A little research, and it sounds like this app won't run on our phone's architecture. As far as I know, I can't force it to run. I'm very interested in getting this to work though.
-NextVR - Launches to blank screen.
-Hello Mars - works no problem. Lacking content it seems.
-JauntVR - works no problem.
-Littlestar - opens to non-side-by-side screen.
-InceptionVR - opens to non-side-by-side screen.
-Etc.. haven't tried very many yet.
For some of these, I wonder... I have my phone "posing" as a Pixel XL. I wonder if it would make a difference if I changed it to Pixel regular instead.
Anyhow, there must be others out there who are interested in exploring Daydream on our Nexus 6. Please share your experiences/expertise or point to relevant threads I may have missed!

Unfortunately I am in the same situation as you are, but I am just as interested in getting it resolved. The Daydream UI and the apps that are working actually work very well. What I found is the apps that are opening single screen are doing so because of our device info. I can go into the build.prop and edit the ro.product.device to marlin instead of shamu the app will open in a side by side screen. The only problem is that my phone reboots after running for a few minutes (even if I am not in daydream). I emailed the app developer of "AFFECTED:The Manor" and he said they will adjust the app requirements in their next update, but we can't expect everyone to be so helpful. We need to come up with a way to edit the build.prop info without causing rebooting. Keep me posted and I will do the same ...

Very cool, glad I'm not alone here.
I did notice that Netflix seemed to have picked out that my device was a Shamu, but luckily at least that app doesn't care.
FYI it looks like a bunch more apps just got added to the in-Daydream app-store. Going to try a few of those, and also trying to get google photos working.

Having trouble with Google Pictures in daydream. I get a message saying there is no daydream content for this app. I tried the same build.prop mod you mentioned, and it did not help with that app. I can confirm it did fix the others which didn't previously work. It threw off my kernel though, so I set it back to Shamu. I didn't experience reboots, but I had it set that way for about 10 minutes only.

Guys remember that there is a reason the nexus 6 didnt make the cut. One of the main reasons being that it wont be getting the vulcan drivers that daydream will need. By forcing it you could damage your device beyond repair. Its a high risk for something that will most likely die out over the next few years.

zelendel said:
Guys remember that there is a reason the nexus 6 didnt make the cut. One of the main reasons being that it wont be getting the vulcan drivers that daydream will need. By forcing it you could damage your device beyond repair. Its a high risk for something that will most likely die out over the next few years.
Click to expand...
Click to collapse
Yes good point. I personally am prepared for the worst, but yeah, disclaimer to others...

I was able to get it to work in safe mode.. But after rebooting I was still logged in but it's like the touch screen is dead and when I move my phone the picture jitters

needleyepoke said:
I was able to get it to work in safe mode.. But after rebooting I was still logged in but it's like the touch screen is dead and when I move my phone the picture jitters
Click to expand...
Click to collapse
Get what to work?

stev067 said:
Get what to work?
Click to expand...
Click to collapse
The daydream app... Isn't that what this forum is about?

needleyepoke said:
The daydream app... Isn't that what this forum is about?
Click to expand...
Click to collapse
We had just been talking about getting specific apps running, so I didn't know if you were referring to a certain app or just Daydream in general. I didn't have any trouble following the guide to get Daydream up and running. You sure you did it right?

stev067 said:
We had just been talking about getting specific apps running, so I didn't know if you were referring to a certain app or just Daydream in general. I didn't have any trouble following the guide to get Daydream up and running. You sure you did it right?
Click to expand...
Click to collapse
I'll go back and check my steps.. Thanks

stev067 said:
Having trouble with Google Pictures in daydream. I get a message saying there is no daydream content for this app. I tried the same build.prop mod you mentioned, and it did not help with that app. I can confirm it did fix the others which didn't previously work. It threw off my kernel though, so I set it back to Shamu. I didn't experience reboots, but I had it set that way for about 10 minutes only.
Click to expand...
Click to collapse
That is going to be the key to getting those apps working, it is pulling info from the build.prop to verify it should run in the dual screen mode. I just can't figure out how to make the edit and have my device run correctly. I noticed when I changed shamu to marlin even some of my apps updated (like camera) to the pixel camera, but it is supposed to run on 64 bit system so it crashed. I think the change will have to take place on the app side, which is unfortunate.

adbFreedom said:
That is going to be the key to getting those apps working, it is pulling info from the build.prop to verify it should run in the dual screen mode. I just can't figure out how to make the edit and have my device run correctly. I noticed when I changed shamu to marlin even some of my apps updated (like camera) to the pixel camera, but it is supposed to run on 64 bit system so it crashed. I think the change will have to take place on the app side, which is unfortunate.
Click to expand...
Click to collapse
Check this article out: http://apcmag.com/how-to-fake-an-android-device.htm/
It's kinda old, but it sounds like there's more lines that may need to be changed besides [ro.product.device].

stev067 said:
Check this article out: http://apcmag.com/how-to-fake-an-android-device.htm/
It's kinda old, but it sounds like there's more lines that may need to be changed besides [ro.product.device].
Click to expand...
Click to collapse
Yea, I had tried all combinations one at a time and all at once and my device would always reboot. I found during the trial and error that only the ro.product.device was what the app was reading, but could not stop the rebooting.

Galaxy Tab A, and Android Auto

I tried to install Android Auto from the play store, it says my tablet is not compatible. i tried side loading AA from mirrorlink, and it downloaded, and installed, when running the program, it says that google cant use the app. is there something i am missing,
Galaxy Tab A 8.0, with Samsung 9.5, and Android 8.1
Thanks

dgrobe2112 said:
I tried to install Android Auto from the play store, it says my tablet is not compatible. i tried side loading AA from mirrorlink, and it downloaded, and installed, when running the program, it says that google cant use the app. is there something i am missing,
Galaxy Tab A 8.0, with Samsung 9.5, and Android 8.1
Thanks
Click to expand...
Click to collapse
BUMP? was curious.... i have the same thoughts

I had similar experience on my Tab S4. My impression is that Google has blocked AA from working on tablets.

Note10.1Dude said:
I had similar experience on my Tab S4. My impression is that Google has blocked AA from working on tablets.
Click to expand...
Click to collapse
You can spoof some other device name (need to be rooted)... my tab2 (p5100) is working as a phone (i think there is also an app to to the same).. use build.prop editor and than reboot... simple :laugh:
Good luck.

drnightshadow said:
You can spoof some other device name (need to be rooted)... my tab2 (p5100) is working as a phone (i think there is also an app to to the same).. use build.prop editor and than reboot... simple :laugh:
Good luck.
Click to expand...
Click to collapse
Could you, please, dm me with what exactly should I change in build.prop file?

Bumping this rather than starting a new thread...
I side-loaded Android Auto onto My Samsung Tab S7, but it will not run. I'd like to use the tablet rather than my small phone as my AA display in the car. I've tried a couple of the other Auto-focused launchers, but prefer AA. Anyone doing this, is there a simple fix/work around?
The earlier posts suggest it is possible, I guess I'm looking for a bit of hand-holding on what I have to do to get it to work.
Thanks in advance.
Dude