Related
http://www.engadget.com/2011/05/12/netflix-releases-android-app-for-select-htc-phones-samsung-nexu/
I hope the Xoom is not far behind.
I hope they start rolling this out on different devices.
The leaked netflix app a while back now has a different error message saying that the device is not supported
I wonder if we can trick the new app into thinking we are on one of those devices to try it out for the time being.
Sent from my Droid using Tapatalk
Why would they not release this on tablets at the same time? That's retarded. I hope someone can port it to the xoom.
Surprising when I hit the Android Market web site and select install.. Not only does my Incredible show as a selection on the list, but so does my Nook Color!! The Thunderbolt, X and Xoom are grayed out.
I wonder if this app is built like the HBO2Go app (which complains about compatibility with the device on start up), or if we can pull the APK and side load it? (I'll have to test when I get home and power on my old Incredible)
ruvort said:
I wonder if we can trick the new app into thinking we are on one of those devices to try it out for the time being.
Sent from my Droid using Tapatalk
Click to expand...
Click to collapse
Yea I was thinking the same thing (and the Thunderbolt too). Hopefully someone can try it out.
none of the device listed are multicore... fortunately the nexus s is not a qualcom chip based device so at least we know its not locked into a single manufacturer... i suspect that we will get it as soon as they roll out tegra support
SQurel23 said:
Yea I was thinking the same thing (and the Thunderbolt too). Hopefully someone can try it out.
Click to expand...
Click to collapse
Unless someone here beats me to it, I'll try it on my Xoom and TB as soon as I get home (probably 3 hrs from now)...
Installed it on my A500 (got it off my Nexus One), "Netflix is not supported on this device.." Can manage my watch now queue, but that is it.
daveid said:
Installed it on my A500 (got it off my Nexus One), "Netflix is not supported on this device.." Can manage my watch now queue, but that is it.
Click to expand...
Click to collapse
that is kind of what I expected.. just like the APK pulled from the LG rom a while ago... and kind of like what the HBO2Go apk does when loaded onto other devices...
D/l and installed Netflix apk. Everything works except streaming. Tells you your device is not supported. I wonder if its a simple fix. I'm going to look into it.
Sent from my Xoom using XDA Premium App
You can get the apk at multiupload. com/ NPZ062QIZB (stupid post limit, sorry)
I sideloaded it on my X and my Xoom. It works on my X, but the Xoom gets an 'unsupported device' error.
Cracked apk open. In the lib/armeabi file it lists 5 supported devices. They are in .so format however, not sure how to edit those. I'll keep everyone updated
Sent from my Xoom using XDA Premium App
ruvort said:
I wonder if we can trick the new app into thinking we are on one of those devices to try it out for the time being.
Sent from my Droid using Tapatalk
Click to expand...
Click to collapse
This is trivial, but pointless. Playback will error out because we do not have the DRM it is looking for
Like so:
05-12 16:50:24.317: ERROR/CNetflixOMXILClient(1576): OMX enumerator found no names matching drm.play
05-12 16:50:24.317: ERROR/CNetflixOMXILClient(1576): Failed to identify and instantiate DRM play
05-12 16:50:24.317: ERROR/PlaybackDeviceNative(1576): Failed initializing Netflix OMX IL client
05-12 16:50:24.387: ERROR/nf_player(1576): MediaControl Listener: error = NFErr_MC_OpenDeviceFailure
05-12 16:50:24.387: ERROR/nf_player(1576): NetflixPlayer::sendEvent: msg: 100, ext1: 2, ext2: 4026597381, msg:
05-12 16:50:24.387: ERROR/nf-player(1576): MP Error PlayError
Code:
Other people claim to have gotten it to work on the Nook Color by changing the build.prop to g2 though, so who knows
Can't edit .so without source. Thought about swapping build.props but sounds risky
Sent from my Xoom using XDA Premium App
idkwhothatis123 said:
Can't edit .so without source. Thought about swapping build.props but sounds risky
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I attempted changing the items in build.prop that got things going for the Nook devices but had no luck. Device is not supported error when opening app. Changing build.prop did allow me to download the app from the market though.
Sent from my HTC Vision using XDA Premium App
idkwhothatis123 said:
Can't edit .so without source. Thought about swapping build.props but sounds risky
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
There is an 'isdevicesupported()' function in the androidutils source file that they use to check compatibility, however my attempts to edit the SMALI code has ended in failure on my part I just get an app that crashes, and I'm too lazy to build the app in debug and find out why.
Genius in progress
I do say, indeed, it was no trouble getting the APK file from my EVO to my Xoom. Should any of you, Dear Sirs, figure out a non-destructive way of getting this to play on a Xoom, I shall ask the Gods to bestow upon you: the Sword of Light.
I installed on my EVO earlier and it works beautifully! Wish it would come to the xoom
Sent from my Xoom using XDA App
iim right with ya buddy, can't wait.I'm surprised netflix already got as far as it did lol it was kinda out of the blue ..
Hulu plus just added official support for the thunderbolt but upon running it I was immediatly hit with a device not supported error
I'm running Cm7 rc 1.2 any suggestions?
Sent from my ThunderBolt using XDA App
I'm in the same boat. Any input would be appreciated.
Sent from my ThunderBolt using XDA App
Ditto
Same as well. Latest CM7 on latest OTA radio.
I can't provide much help here... Running CM7 RC 1.2, latest radio. I'm not having any issue.
Same issue here
I am having the same issue, Hulu plus says the device is not supported. I found a different flash.apk from another forum that said it would get hulu to work, but no dice.
Any help would be greatly appreciated.
it probably doesnt detect CM7 as being a thunderbolt. sorta like we had to trick the netflix app also. it runs on mine running BAMF sense 3.0 RC5 but force closes. I am thinking some hack will be needed to run netflix and hulu+ both.
Wow what BS! I want to try it out to see if I can just ditch Netflix since they are screwing everyone!!!
Idea: What about modifying the build.prop to make the device name match what it says stock?
Mustang302LX said:
Wow what BS! I want to try it out to see if I can just ditch Netflix since they are screwing everyone!!!
Idea: What about modifying the build.prop to make the device name match what it says stock?
Click to expand...
Click to collapse
i think that is what will have to be done. i havent tried it yet though
howarmat said:
i think that is what will have to be done. i havent tried it yet though
Click to expand...
Click to collapse
I will try it and let you guys know I just don't know what the device name is out of the box. Was it Thunderbolt without the capital B or was it the AD600blahblah lol?
now sure lol
It's ADR6400L I'm going to try now.
Nope still says unsupported device.
Anybody know what had to be done to allow the netflix app to work on CM7?
wfagan59 said:
Anybody know what had to be done to allow the netflix app to work on CM7?
Click to expand...
Click to collapse
The Netflix app works on CM7. However this is for the new Hulu Plus app.
Sent from my Thunderbolt running CyanogenMod 7 using the Tapatalk app.
Hopefully someone gets it working!
Mustang302LX said:
The Netflix app works on CM7. However this is for the new Hulu Plus app.
Sent from my Thunderbolt running CyanogenMod 7 using the Tapatalk app.
Click to expand...
Click to collapse
I know this is hulu. Just seemed like its having the same problems running as netflix did at first. Thought it might be the same kind of device check feature that had to be bypassed.
Sent from my ThunderBolt using XDA App
wfagan59 said:
I know this is hulu. Just seemed like its having the same problems running as netflix did at first. Thought it might be the same kind of device check feature that had to be bypassed.
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
I think it does have a device check as people with stock unrooted roms say it works for them
howarmat said:
I think it does have a device check as people with stock unrooted roms say it works for them
Click to expand...
Click to collapse
Which doesn't make sense. I even named my device like it is stock and nada.
Sent from my Thunderbolt running CyanogenMod 7 using the Tapatalk app.
Mustang302LX said:
Which doesn't make sense. I even named my device like it is stock and nada.
Sent from my Thunderbolt running CyanogenMod 7 using the Tapatalk app.
Click to expand...
Click to collapse
im sure there are other ways it can check to see what "phone" you have. liking missing libraries or something.
howarmat said:
im sure there are other ways it can check to see what "phone" you have. liking missing libraries or something.
Click to expand...
Click to collapse
Yeah hopefully someone can figure it out so we can rock some Hulu!
Its because we are blocking ad and modifying the hosts file.
you need to have adfree installed and hit revert to repair the hosts file.
Working now for me!
They worked fine on my old Charge... And this phone has more ram.. what gives? Any way to get them to work...
Sent from my ADR6400L using Tapatalk 2
miguel11691 said:
They worked fine on my old Charge... And this phone has more ram.. what gives? Any way to get them to work...
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
It would be helpful to have some specifics...
1. What games are you trying?
2. What ROM are you running?
Those are the big two...
miguel11691 said:
They worked fine on my old Charge... And this phone has more ram.. what gives? Any way to get them to work...
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
djsnake210 said:
It would be helpful to have some specifics...
1. What games are you trying?
2. What ROM are you running?
Those are the big two...
Click to expand...
Click to collapse
Dude has a good point, more info would be helpful. But you can edit your build.prop to spoof the market that you have a different device.
Sorry I have the infected rom 3.5 and games like NBA Jam and Max Payne for example
Sent from my ADR6400L using Tapatalk 2
How can I spoof the market
Sent from my ADR6400L using Tapatalk 2
One of the fairly popular ROMS on the board was using a build that reported something other than being a t-bolt. It happened to crop up when I was using bootmanager and it was a bit upset at one of the roms.
In checking-it was ODJDub. A lot of EA games run much tighter checks than others. By modifying the build file, you can tell these "checks" what device you have. It's fairly common when you slap the droid OS on a non android device like Nook Colors, HP touchpads, etc.
NapalmDawn said:
One of the fairly popular ROMS on the board was using a build that reported something other than being a t-bolt. It happened to crop up when I was using bootmanager and it was a bit upset at one of the roms.
In checking-it was ODJDub. A lot of EA games run much tighter checks than others. By modifying the build file, you can tell these "checks" what device you have. It's fairly common when you slap the droid OS on a non android device like Nook Colors, HP touchpads, etc.
Click to expand...
Click to collapse
You need to change
ro.product.device
ro.product.board
ro.product.name
Change them to something like the HTC flyer or another tablet should resolve your issue, you'd have to Google it though, as I'm not sure of the proper entries for other devices.
Sent from my Thunderbolt using Xparent ICS Tapatalk 2
Will that effect my phone in anyway with updates
Sent from my ADR6400L using Tapatalk 2
miguel11691 said:
Will that effect my phone in anyway with updates
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
No. However, I would make a back up copy of your build file and name it like build.old and keep it safe. If you wish to restore your checks to broadcasting the tbolt name, simply rename the current build file and rename build.old back to build.prop. It's just a matter of whether or not you think renaming files is quicker than editing them.
The stood charge is a duel core phone so more games for it. Our phone is single core and not as good for gaming as more.cores are needed.
Sent from my ADR6400L using xda premium
Google_Nexus said:
The stood charge is a duel core phone so more games for it. Our phone is single core and not as good for gaming as more.cores are needed.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
WRONG, yet again...
Might wanna start checking facts before you post anymore in these forums.
That applies to both you and your alter ego "Entitled".
The Droid Charge has a single-core 1Ghz Hummingbird processor on VZW.
The issue lies within the build.prop, as already correctly mentioned above.
In fact, I wonder if the OP has applied one of the modified build.props posted over at InfectedRom.
Anyway, editing that should fix you back up.
Otherwise, there are also modded versions of the Play Store out there with device specific restrictions removed, though they tend to be outdated fairly quickly.
No I didn't know once existed... do u have a link bro
Sent from my HTC ThunderBolt using Tapatalk 2
why dont use apk downloader?
if interested i can lend you my username,password and dev UID by PM:good:
but for free game only:victory:
Just seen this on the wire and thought how awesome it looks.
Rockchip is a chinese chip manufacture that powers devices like the popular MK808 and other handheld devices. Looks like they've been busy as today they announced they have a Split screen solution similar to Samsung that runs on Stock Android, except it can run any app.
Oh man does this look yummy.
How likely is it that we will get this on the Nexus 7?
Sent from my Nexus 7 using xda premium
StrangerWeather said:
How likely is it that we will get this on the Nexus 7?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
very very very very likely as Nexus 7 is one the best and popular high end device....IMO
Wow I want this, I don't have an N7 yet, but soon.
Sent from my Nexus 4 using xda premium
Can't wait!
Sent from my Nexus 7 using xda premium
Split screen solution similar to Samsung.
Click to expand...
Click to collapse
Anyone correct me if I'm wrong, But Samsung implementation seems to only be custom apps that work in window form, but this seems to be a framework implementation?
Meaning this should work well with all Play Store apps as long as they followed the Android development guidelines and have a tablet UI. (fragments, panels etc)
Why is this thread has a PORT prefix in the title?
lionsson said:
Anyone correct me if I'm wrong, But Samsung implementation seems to only be custom apps that work in window form, but this seems to be a framework implementation?
Meaning this should work well with all Play Store apps as long as they followed the Android development guidelines and have a tablet UI. (fragments, panels etc)
Click to expand...
Click to collapse
You are correct about how Samsung multi window works.
I don't know what the guidelines are for this multi window feature.
Sent from my Nexus 4 using xda premium
I wrote an article on this yesterday.
I can't wait to see how it properly functions on some of the well known devices.
@StrangerWeather its very likely the N7 will get it as its probably the most popular 7" tab on the market.
Fatal1ty_18_RUS said:
Why is this thread has a PORT prefix in the title?
Click to expand...
Click to collapse
Because it would require a port from Rock chip devices to our N7.
This seems really cool because the Samsung required specific apps where here, he used anything, such as the stock settings app. So it should work with any app.
Plus I like how they all control and flip back and forth. Really nice.
Sent from my Galaxy Nexus using xda premium
Saw this on Android police and the implementation of gestures, Window resizing, management etc was nice and it's better than Samsung's Multi Window feature.
Wish this gets ported to custom ROMS soon.
Sent from my Nexus 7 using Tapatalk 4 Beta
Hopefully in the final release it uses the phablet layouts when in split screen. Ideally it would recalculate screen metrics based on the window size.
Sent from my Nexus 7 using xda premium
blackhand1001 said:
Hopefully in the final release it uses the phablet layouts when in split screen. Ideally it would recalculate screen metrics based on the window size.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
A port would be awesome. Can't wait for it!
player911 said:
Because it would require a port from Rock chip devices to our N7.
This seems really cool because the Samsung required specific apps where here, he used anything, such as the stock settings app. So it should work with any app.
Plus I like how they all control and flip back and forth. Really nice.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So if I wanted someone to make a guide on how to root would I make a thread called "[GIUDE][HOW-TO] How to root Nexus 7"?
Sent from my Nexus 7 using xda app-developers app
The rumor has it that Paranoid Android team is developing something like this. In fact CM team had tried to publish their version of multi window(project Cornersrone) but Google wouldn't let them. Multi window is totally possible to make for N7 and whatever modern android device. In near future!
Sent from my teddy bear
Quite frankly, in the era of 1080p displays, there should be multi-window baked in to the OS. It's a feature that I think would really propel Android forward.
Sent from my HTC One using Tapatalk 2
Useful on a tablet but pointless on a phone. May be Google will bring this in KLP?
Sent from my GT-I9100 using Tapatalk 4
rakeshishere said:
Useful on a tablet but pointless on a phone. May be Google will bring this in KLP?
Sent from my GT-I9100 using Tapatalk 4
Click to expand...
Click to collapse
I sure as hell hope so. Who said Sammy devices can have fun with this all alone?
This is MIUI V6 Based Nexus 7.
It have some problem so it's aphla version.if you like,you can have a try.
MODERATOR EDIT:
Based on this http://en.miui.com/thread-15454-1-1.html page saying....
Please do not leak the ROM file! Or else you'll be removed from the team immediately!
As it's closed beta version, there're still many bugs. It's kind of risky to flash it.
Please think carefully before applying. Thanks!
Click to expand...
Click to collapse
The download links have been removed and the thread closed
Are you Chinese？？？？
i don't wanna sound rude but its 'alpha'
v6 means kitkat, right?
Feel free to ask if you need any help for make this fully working!! may be XDA community can help you.
Jing, did you noticed any major changes to v5?
Can you provide us with more screenshots please ? I wanna see how the v6 looks like
Sent from my Nexus 4 using xda app-developers app
Can´t find any official info about MIUI based on KitKat.
Is this real or fake ? because looks fake for me.
Its probably a port from the beta found here: http://www.miui.com/thread-1634372-1-1.html
It boots but it has a lot of FC`s
Navigation is impossible as we don't have navigation keys but its 4.4 and has a theme that looks like iOS 7.
Well, at last miui v6 is here! Hope that all the bugs will be squashed out!
I will also try to look into the problems like systemui fc tomorrow if I have time.
Looks to me that its because of the size cause the nexus 4 has a smaller screen size in DPI and resolution believe then nexus7.
Do you actually have permission to post your port here cause if you would leak a build then you would be kicked of the beta team.
Sent from my Nexus 4 using Tapatalk
Hey, i am certain that you can not post private builds (like the Nexus 7 II beta), even if it is a port.
Also, i ran into the same SystemUI issue while porting to Nexus 5.
Seems to be related to non-existant/wrong layout defined for phones, i haven't found an fix for this yet. Feel free to share the fix if you find one.
Please continue with this. It looks awesome
Sent from my Nexus 4 using Tapatalk
datagutt said:
Hey, i am certain that you can not post private builds (like the Nexus 7 II beta), even if it is a port.
Also, i ran into the same SystemUI issue while porting to Nexus 5.
Seems to be related to non-existant/wrong layout defined for phones, i haven't found an fix for this yet. Feel free to share the fix if you find one.
Click to expand...
Click to collapse
I think I can because it's public on the internet. You can google miui and a lot of link there
Sent from my iPad using Tapatalk
jing95916 said:
I think I can because it's public on the internet. You can google miui and a lot of link there
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
+1
Sent from my Nexus 4 using Tapatalk
jing95916 said:
I think I can because it's public on the internet. You can google miui and a lot of link there
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I can't find the download link :crying: Could you please give a small hint on where tot download the Nexus 7 version? Thanks :good:
greveldinges said:
I can't find the download link :crying: Could you please give a small hint on where tot download the Nexus 7 version? Thanks :good:
Click to expand...
Click to collapse
Its in OP...
Sent from my Nexus 4 using XDA Premium 4 mobile app
mailyaseen said:
Its in OP...
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's the nexus 4 download, asked for the nexus 7 download but i already have it, nvm
jing95916 said:
I think I can because it's public on the internet. You can google miui and a lot of link there
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Oh, as long as someone else is the leaker it doesn't matter
Good luck with your porting.
datagutt said:
Oh, as long as someone else is the leaker it doesn't matter
Good luck with your porting.
Click to expand...
Click to collapse
u fix it already？
Sent from my iPhone using Tapatalk
jing95916 said:
u fix it already？
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Not yet.
I tried to explore the res/ folder of MiuiSystemUI to try finding the difference between the sw600dp (tablet layout) and the other values folders. I can't find anything wrong so i think the issue must be fixed in smali.
I removed SystemUI to explore the UI and MiuiHome crashed because it could not find an resource. Does MiuiHome crash for you as well? MiuiHome is probably dependant on MiuiSystemUI though.