Can someone please post the APK for Netflix that was released today. Would like to try on the Atrix.
I want this too
Wow....the advertisements on this page are about Netflix...google is taunting me..
no worky
I tried downloading the apk and it basically says Netflix does not support this device. Nice. No Atrix support.
I'm hoping that can be rectified. Doubt it will be by Motorola.
even if you get it, it wont work.
Netflix app
frankic said:
Can someone please post the APK for Netflix that was released today. Would like to try on the Atrix.
Click to expand...
Click to collapse
roharia said:
I want this too
Click to expand...
Click to collapse
Here you go.
com.netflix.mediaclient.apk
nope won't work....
Sent from my MB860 using XDA Premium App
What if someone spoofs the build.prop line that identifies the device? I hear people with custom roms can't run the app because it shows something other than default, so it sounds like the app is based off of that... but I have no clue if that can be changed on the Atrix at this point. If it's possible though, it would just take a minute to change it to read Nexus S or something.
EDIT: I just tried http://www.reddit.com/r/Android/comments/ha5oh/root_how_to_edit_your_buildprop_to_make_netflix/ but still got the device unsupported message error. I probably did something wrong, so someone else is free to try.
Netflix Fix for Atrix
Sorry for the mispost...
I played with the apk all day and build.prop settings. I couldn't get it to work at all.
I could get it to load, error message, but still could sign in and manage my queue and whatnot, but when I hit play, the error came back up again.
messing with the build.prop, the app just flat out wouldn't load.
Oh, and swype stopped working at one point because of the edits, so I just put it back to stock and carry both my Evo and Atrix
agentscreech said:
I played with the apk all day and build.prop settings. I couldn't get it to work at all.
I could get it to load, error message, but still could sign in and manage my queue and whatnot, but when I hit play, the error came back up again.
messing with the build.prop, the app just flat out wouldn't load.
Oh, and swype stopped working at one point because of the edits, so I just put it back to stock and carry both my Evo and Atrix
Click to expand...
Click to collapse
Something I thought of afterwards was that it may look for other lines in the build.prop. There's a line in the Atrix's build.prop saying that the processor is a Tegra, did you try changing that line? If I remember right all (or nearly all) the Netflix supported phones run off a Qualcomm chip after all.
They got it working on the g2x (Tegra 2) by editing the build.prop also. Dang what is it about the atrix that is causing it not to load?
Are you on a custom rom?
Sent from my HTC Vision using XDA App
I guess they said they are working on it still because of the drm they use and that android doesn't have a unified method to decrypt it for play back, so I guss they have to make it work in each device one at a time that sucks.
Sound right?
ya but this build prop edit has allowed it to work on phones that were not on the 'officially supported' list
I tried to copy any relavant info from my evo's build.prop (it's cyanogen7) that I could think of. I saw the processor type field on the atrix, but there wasn't one on the evo. There were quite a few fields that are extra on the atrix.
But again, swype stopped working because it thought my phone was some other phone...not worth it. I'll look into more detail of why the evo works
Sent from my MB860 using XDA App
Related
I don't know may it's stupid request, but may could change somehow apk for Thunderbolt that it works on our XOOM devices? I tried to install apk of Skype with Video on my XOOM WiFi, but without success.
http://forum.xda-developers.com/showpost.php?p=12822787&postcount=7
Hope that somebody will find a way how to install above-mention Skype on our XOOM
Kozdoba said:
I don't know may it's stupid request, but may could change somehow apk for Thunderbolt that it works on our XOOM devices? I tried to install apk of Skype with Video on my XOOM WiFi, but without success.
http://forum.xda-developers.com/showpost.php?p=12822787&postcount=7
Hope that somebody will find a way how to install above-mention Skype on our XOOM
Click to expand...
Click to collapse
I would LOVE to have this working on our Xooms!
Yeah! That will be pretty neat. I'm not a dev, but truly believe that this apk isn't just sighned for xoom, and that results in "app not installed" message
I tried to install it too, didnt work ;-(
There has to be something within the files that only allow it to work on the Thunderbolt. I opened the apk and searched through the files, but did not see any type of device ID or anything that read "thunderbolt" or HTC. I remember when I used to make BlackBerry hybrids, there were "device IDs" that could be modified. I am uncertain about Android.
I am going to try and install it on other model phones running Froyo and see what I can figure out.
The only other thing I could think is that it is just not written to be compatable with honeycomb as most apps arent.
It won't install on my Evo either
Sent from my PC36100 using Tapatalk
Did you guys go into setting>applications>and check "unknown sources" first.
supremecream06 said:
Did you guys go into setting>applications>and check "unknown sources" first.
Click to expand...
Click to collapse
Yes, at least I'm check it, but it doesn't help
Tried installing that APK on Nexus 1, Galaxy S and Xoom, none of them work. There seems to be a lot of buzz about this but not too much info beyond that.
Skype really needs to release a Honeycomb video chat client. With so many HC tablets in the works, it would really be a killer app.
However, I think I can understand Skype's hesitation. Can you fellas imagine the massive amounts of traffic that would hit Skype's datacenters?
I just tried G-Chat Video chat, and it works amazingly well if you guys haven't tried it. At least as a temporary alternative.
Why don't google hurry up and update talk with video like when using gmail you can video chat?
Sent from my GT-I9000 using XDA App
Google's video-chat already works on the Xoom.
Is that a tablet only thing as it's missing from galaxy s?
Sent from my GT-I9000 using XDA App
Google talk video was released only for Honeycomb.
It cross platform Google solution because it works with PC and mac running Google talk.
Unfortunately, there is no such thing for Froyo.
Is there a way to use Google Talk for calls with Skype users?
FYI this program works on XOOM and available for Android and iOs system.
https://market.android.com/details?id=com.sgiggle.production&feature=search_result
Kozdoba said:
FYI this program works on XOOM and available for Android and iOs system.
https://market.android.com/details?id=com.sgiggle.production&feature=search_result
Click to expand...
Click to collapse
Not with video
Sent from my Xoom using Tapatalk
jvs60 said:
Not with video
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Did you tried it, they claim that his program works with XOOM, unfortunately I couldn't check it right now. Just found it in the market
Kozdoba said:
Did you tried it, they claim that his program works with XOOM, unfortunately I couldn't check it right now. Just found it in the market
Click to expand...
Click to collapse
Works for outgoing not incoming
According to the announcement, the Nexus S (which is a Galaxy S with a curved screen, NFC, and GB) is supported for streaming, even though it's supposed to only be available for Snapdragons, and not yet for Hummingbird.
Anyone manage to snag the APK yet? It won't let me install from the Market, even though even Google thinks I'm running a Nexus S (when in reality, it's just a Fascinate with CM7).
http://www.businessinsider.com/how-to-get-netflix-on-your-android-phone-2011-3
Sent from my SCH-I500 using XDA App
Using that version of the app just gives you a message saying the phone is unsupported for streaming. Would changing the ID of the device in the build.prop or something similar be enough to fool Netflix?
Sent from my SCH-I500 using XDA App
caesus said:
Using that version of the app just gives you a message saying the phone is unsupported for streaming. Would changing the ID of the device in the build.prop or something similar be enough to fool Netflix?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
That's the question I have. Trying to find out where I could edit it to see what it does.
I downloaded it on my Nexus and transfered the apk to my i500 but when I installed it it gave me the "unsupported device" error.
AlexDeGruven said:
That's the question I have. Trying to find out where I could edit it to see what it does.
Click to expand...
Click to collapse
Please share if you get this working.
http://forum.xda-developers.com/showthread.php?t=1076260
If I can get my hands on the build.prop from either the Nexus S on AT&T or the Nexus S 4G, then I might be able to figure out the pertinent tweaks to make the Fascinate appear as either of those to the app when it tries to stream.
If it runs and streams on the NS, then the purported hardware limitation that was supposed to be there doesn't exist, and they're implementing the device lockout entirely in software. This means it will be easy to hack around, and probably be able to do so cleanly without hammering any important settings for the phone.
Edit: The Incredible (and presumably, by extension, the Thunderbolt) is supported, so it's not a carrier lockout, either. This tells me that it's only software, which is heartening.
http://t.co/n7QDwJ4
Courtesy of koush
Sent from my SCH-I500 using XDA App
Awesome. I'll check this out tonight and see what I can come up with.
Sent by touching a featureless glass panel with mysterious lights behind it.
"HELL YEAH!!!!.... aww man...."
it pretty much happened just like that.
Hmm no luck so far. Not really sure what to change without breaking the whole show.
Hopefully, someone with more expertise than I can chime in with the right changes.
Sent by touching a featureless glass panel with mysterious lights behind it.
Tech buzz widget has an androidpolice article about what lines in the build prop to edit. Haven't tried it yet...
OTB Comm.Rominate
Found this in the evo forums...maybe it'll help you guys
mikel719 said:
Ok, so I was in the virus kingdom rom thread and seen this asked a couple of times.
I found this info on another site, I'll past the link in a few but here are the instructions...
So how’s it done? Well, the instructions are actually fairly straightforward, and come courtesy of tipster/redditor natemckn:
Root is required. Make a Nandroid backup! (I accidentally deleted by build.prop file and bootlooped my phone)
Download ES File Explorer (Or any other root file editor)
In ES File Explorer, go into Setting > Root Settings and enable both check boxes
Navigate to /system/ and copy/paste build.prop to /sdcard/ (just in case)
Open & edit /system/build.prop
Change the following lines to make your phone think it is a HTC G2:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
ro.product.manufacturer=HTC
Reboot the phone
Install the netflix apk (if you haven’t already)
Enjoy
Update: Apparently you don’t need to do the lines that are crossed out in Step 6 – only the product model and manufacturer need to be changed.Also, it appears that this is hit-or-miss at the moment. Works for some, partially (but not really) for others.
Heres the link,, if its not clickable its because I'm doing this from my phone, so copy and paste.
http://www.androidpolice.com/2011/0...to-thinking-your-rooted-device-is-supported/#
Sent from the hidden underground command bunker
Click to expand...
Click to collapse
Tried it on my Fascinate with CM 7 (5/11/11). Changed build.prop to the HTC Vision. Installed netflix app without any errors, but when I play a movie, it only plays the audio, the video is just a black screen. Anyone else have this problem and found a solution??
emortio said:
Tried it on my Fascinate with CM 7 (5/11/11). Changed build.prop to the HTC Vision. Installed netflix app without any errors, but when I play a movie, it only plays the audio, the video is just a black screen. Anyone else have this problem and found a solution??
Click to expand...
Click to collapse
Afaik, our cm7 builds are missing a lot of codecs... this could be part of your video problems.
Sent from my HTC Vision using Tapatalk (heh... well, I guess we know where Tapatalk gets its model info. )
* The Netflix app runs on these phones:
1. HTC Incredible with Android 2.2
2. HTC Nexus One with Android 2.2, 2.3
3. HTC Evo 4G with Android 2.2
4. HTC G2 with Android 2.2
5. Samsung Nexus S with Android 2.3.
Thank you for repeating the information that we already know.
We're aware of the devices it works on, we're trying to make our devices masquerade as one of those in an attempt to get streaming working.
Not much luck so far. Time to work now. Might hack on it some more tonight.
The apk running around here doesn't work, either. At least not on 2.2.
Ok, so I said I was going to quit, but it's just too juicy.
Here's what I've found:
Work on Nexus S with GB. The NS is identical to the rest of the Galaxy S line from a hardware standpoint (with the exception of the NFC and curved screen, which have nothing to do with things). The only difference between them is the software.
Some more digging revealed that the key difference in a device working or not working is the Stagefright media framework, which is supposed to be the stock setup in 2.2, but OEMs mostly felt like they needed to hack it out in favor of their own stuff.
So... To get this working on the Fascinate, we need one of the following:
1. A CM7/AOSP GB build with working video codecs (we're almost there on that point)
2. A CM6/AOSP FroYo build with Stagefright media framework in place.
3. A custom ROM with the Stagefright framework hacked in.
AlexDeGruven said:
So... To get this working on the Fascinate, we need one of the following:
1. A CM7/AOSP GB build with working video codecs (we're almost there on that point)
2. A CM6/AOSP FroYo build with Stagefright media framework in place.
3. A custom ROM with the Stagefright framework hacked in.
Click to expand...
Click to collapse
4. A Samsung GB leak. Don't laugh -- now that i9000 GB is final, it's already official for the GSM Tab, and the Epic has a leak (now two) as well. US Galaxy S models running Touchwiz GB have run Netflix with no problem.
I've been up late tonight, and just so happened to stumble across this article over at AndroidPolice. Figured it might interest some people here since it includes our phone.
http://www.androidpolice.com/2011/1...e-numbers-gps-sms-emails-addresses-much-more/
Here's the thing, though. They recommend uninstalling the offending apk immediately, which I tried.....Unfortunately that gives me repeated force closes over and over and over while the system tries to run it, to the point where I had to restore to a backup. So what do we do about this?
UPDATE: You can remove HTCloggers.apk...all you have to do is restart afterwards.
Evo4gLI said:
I've been up late tonight, and just so happened to stumble across this article over at AndroidPolice. Figured it might interest some people here since it includes our phone.
http://www.androidpolice.com/2011/1...e-numbers-gps-sms-emails-addresses-much-more/
Here's the thing, though. They recommend uninstalling the offending apk immediately, which I tried.....Unfortunately that gives me repeated force closes over and over and over while the system tries to run it, to the point where I had to restore to a backup. So what do we do about this?
Click to expand...
Click to collapse
Yes and no.
Yes because so many users run Sense.
No because I run AOSP.
Frankly, I wonder how many other serious flaws there are.
I can name several apps that want their hands on permissions they have no business in [Facebook for one]
Its like 1984 for sure. There's an article in the new section here at xda that talks about some of the other vulnerabilities as well.
Sent from my PC36100 using xda premium
Thanks for sharing. Another reason why we root our phones
Sent from my PC36100 using XDA Premium App
Many devs remove these programs and such to remove ciq. I can't find the thread right now, but it reads just about everything. It's so deeply imbedded into the framework.
It reads every button you press on your keyboard.
Every text you send and receive.
Every app you use and download.
The pages you browse on using the internet browser.
It even goes as far to read any spot on your screen that you touch.
This is spyware to the extreme. Sprint and HTC will say its not "spyware" and say its used only for marketing to determine how phones are being used to further develop for the current trends in smartphones. It's very possible they could steal personal info with this. Is it currently happening? Uhh...probably not, but there will still be a lot of paranoia about it.
Sent from my PC36100 using XDA App
Sounds like a really good reason to stay with AOSP to me...
very True Haha
Sent from my GT-I5800 using XDA App
Some of us haven't forgotten the XCP rootkit that was on some Sony BMG titles in 2005... hope HTC doesnt suffer a similar demise like Sony eventually has of late.
This has been removed from MikG.
This is exactly why I'm AOSP. (that and sub-100MB ROM files)
I read the article too- (I have an Androidpolice/Android Central) feed in my Pulse reader....
I already knew CIQ and such were slimy embedded spyware...but the Treve app- spotted stuff I hadnt deleted already... Sprint sent me a "letter" about bandwidth usage and We-KNOW-what-Your-Doing" ----
I'm not amused by HTC/Sprint's collusion... leaving our bottoms out there in the cold for anyone to do whatever with.....
I bet even money my phones been cloned... sometimes I can't use it for calls .. recently -and I'd not had a single missed call or problem in a year.
I'm not a happy camper.. worried about my credit card #'s and really really am annoyed by HTC sliming us this way...
to the tune- that it'll be an icey cold day in hell before I'd consider buying another HTC phone for anyone in my family- (my family has 3 Evo 4g)...
We are not amused.....
HipKat said:
Sounds like a really good reason to stay with AOSP to me...
Click to expand...
Click to collapse
AMEN
it appears to me that this file has already been removed from MikFroyo. At least, I can't find it...
BTW, you can just remove it using TIbackup, but you'll have to restart to get rid of the repeated force closes. Simple fix, and I've done the same for CarrierIQ as well.
It was removed from sprint lovers rom as well... I couldnt find it at least
I removed HtcLoggers.apk from mine and after rebooting (force close loop) it seems to be working fine. However, is there an old log file still on the phone that can be read by some Spyware app that needs to be removed or does all this data need to come from the logger app itself? If there still is a log, I'm sure it has enough info to still steal my ESN and other stuff.
Wow! Glad I run custom ROMS
To start this off, I want to say that this is an awesome community full of great people willing to help others. It takes this sort of open source sharing to come together for the greater good. That is why I want to make a thread to document my experiences so that it may help others and myself.
As of yesterday, I started using froyo 2.2.2 by joshkoss. This update is probably the best of all of them and I like it much better than 2.2.1, which is what I previously had installed. Having said that, there are still some problems, which I almost find enjoyable to discover how to fix.
Throughout most of my updates, my GPS has been slow to connect. Finally on 2.2.2 it is impossible to establish a connection and everytime I turn on GPS it always asks me to 'Accept' or 'Cancel' the agreement. I've never had this happen before. Anyone know what to do about that?
Beyond this issue, I wanted to try this fix by ciscogee. I have gotten all the way to the point on ADB tools that in my cmd prompt I can type 'adb devices' to show me my devices serial number. For me, it ends there. As soon as I can figure out how to do this fix step by step for a beginner I will type it out in this thread. I am using Android SDK.
Another problem with this 2.2.2 update is that my banking app no longer works and it force closes right after start up. Then when I try to send a report, that also force closes. It worked on 2.2.1 so Im sure it has something to do with it.
So as of right now this is where I'm at. I hope I can help some people out with their Continuum. I just dont have the detailed knowledge of the inner workings to really bring something to the table, but I hope to at least help someone else out and learn something in the process.
My Wells Fargo app quit working when I switched over to EC07 and I haven't been able to pinpoint what the problem is. I posted my problems in another thread, but basically I had several apps that were FCing when I tried to use them. I did logcat on them, and based on the errors I got from there, I think is has something to do with the apps trying to access data either over 3G or wifi.
Never got any further than that though.
That's weird. Did you have problems reporting the failure? Ill have to try out that log app and see what I can find out. Hopefully ill have something later today.
Anyone else have problems with a banking app? Mine is comerica bank.
Sent from my SCH-I400 using XDA App
Trailblazer101 has a fixed browser app. Try that.
Sent from my SCH-I400 using xda premium
I don't think that'll help. My browser has never forced closed.
Sent from my SCH-I400 using XDA App
Thinking is a lil dif than trying it and knowing for sure.
Sent from my SCH-I400 using xda premium
I tried the hacked browser and it didn't change anything on my phone. Both the stock browser and TB's hacked one FC as soon I tried load a page.
One thing I did notice though, was that the browser would let me surf the web just fine. It was when I tried to log into any account; Wells Fargo, Google, etc.,that it would FC. Don't know if that means anything or not. Wonder if it is the same reason some banking apps aren't working. Could it have something to do with using secure connections?
Just a thought.
ciscogee said:
Thinking is a lil dif than trying it and knowing for sure.
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
You're absolutely right! You really can't mess up this phone either.
rowdyw said:
I tried the hacked browser and it didn't change anything on my phone. Both the stock browser and TB's hacked one FC as soon I tried load a page.
One thing I did notice though, was that the browser would let me surf the web just fine. It was when I tried to log into any account; Wells Fargo, Google, etc.,that it would FC. Don't know if that means anything or not. Wonder if it is the same reason some banking apps aren't working. Could it have something to do with using secure connections?
Just a thought.
Click to expand...
Click to collapse
I get what you're saying about the force close on secure connections. Ive only had a force close on one bank app. Never online through the web browser such as dolphin.
Was the hacked browser an internet browser?
Yep, my Wells Fargo app doesn't work either.
Same fc issue... as with the Flixter and imapmyrun apps.
(Small vibrate... pause... blackscreen & 3 pulse vibrate fc.)
I'm running Miunia Beta 3 on ec07 radio with the Ciscogee .85 blue theme.
Sent from my SCH-I400 using XDA App
Yes exactly. My comerica does the same vibrating act.
Sent from my SCH-I400 using XDA App
Ahh just found another one with the buzzing act. The app called zillow. Makes me wonder if I should go back to my old rom...nahh ill stick out for an update...come on joshkoss!
Sent from my SCH-I400 using XDA App
Ok, after reading some old posts, I think I may have found a connection with the FC issues and certain apps. It seems that there were alot less FC problems when using the EC03 baseband vs. the EC06 baseband.
Does anyone know what the differences are between the two?
I've said it before, but; I don't know much about programming, language, kernals, etc. but I can see patterns. And what I have seen is that most of the apps with FC problems are trying to access network data, and alot of those seem to be secure connections (such as banking apps). Someone said before that it is hard to know what the real problem is because everyone uses different apps, but I have seen the same apps listed as causing problems with several different users here over and over again. So that makes me think that there is an underlying problem causing these issues.
Like I said, I don't know much, but this seems like the problem to me, and if these clues make something, somewhere, inside someone's brain click that actually does know something about this, then maybe I helped a little bit.
rowdyw said:
Ok, after reading some old posts, I think I may have found a connection with the FC issues and certain apps. It seems that there were alot less FC problems when using the EC03 baseband vs. the EC06 baseband.
Does anyone know what the differences are between the two?
I've said it before, but; I don't know much about programming, language, kernals, etc. but I can see patterns. And what I have seen is that most of the apps with FC problems are trying to access network data, and alot of those seem to be secure connections (such as banking apps). Someone said before that it is hard to know what the real problem is because everyone uses different apps, but I have seen the same apps listed as causing problems with several different users here over and over again. So that makes me think that there is an underlying problem causing these issues.
Like I said, I don't know much, but this seems like the problem to me, and if these clues make something, somewhere, inside someone's brain click that actually does know something about this, then maybe I helped a little bit.
Click to expand...
Click to collapse
If that's the case, it sounds like a problem with ssl. I wonder if a fascinate baseband would fix it. Trailblazer proved that a fascinate baseband would work on our phones a few months ago
Release your inhibitions, feel the rain on your skin, no one else can feel it for you. only you can let it in - Natasha Bedingfield
It would be worth a shot for sure.
Sent from my SCH-I400 using Tapatalk
http://forums.androidcentral.com/co...unknown-baseband-radio-modem-replacement.html
Try that link... let's find out if it works.
Thanks, I will have to try it out when I get home.
Will cwm save my existing radio if I wanted to back up what I've got?
Sent from my SCH-I400 using XDA App
minirome said:
Will cwm save my existing radio if I wanted to back up what I've got?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
I believe so. But, if not, reflash with odin.
Either let me fly or give me death. Let my soul rest, or take my breath. - DMX
Cwm will NOT back up your radio!
Sent from my SCH-I400 using xda premium
I installed ECO3 from imnuts and it works great, but if i install the updated 2.2.2 ECO7 Netflix will not work, am i doing something wrong. Everything else works
I've noticed that as well. I think it has something to do with the api, but I'm not sure. It worked on EC07 for a while, and the app update broke it. If you can get one that is a couple of versions older, it will work fine. I just haven't bothered to find one, since watching streaming media on a phone is kind of silly for me, when I have my computer on hand at all times.
There are a few apps on my 2.2.2 that dont work. Such as banking app, home buying app Zillow. They force close. Are you saying your netflix force closes?
minirome said:
There are a few apps on my 2.2.2 that dont work. Such as banking app, home buying app Zillow. They force close. Are you saying your netflix force closes?
Click to expand...
Click to collapse
No. You get an android toast message that says "we are unable to start netdlix.Please restart" and error code 136006. I haven't bilothered to call netdlix, or logcat it, since I don't watch netdlix on this thing. Since its not just me with this issue, ill play with it this week. Colby, what Ron are you on? I'm on t1231's ec07 deodexed. Personally, since it used to work on this Rom, I think an app update it broke it.
I am not a fly, i am levitation. I represent an entire generation. - Niki Minaj
I'm pretty sure an app update did break it. It worked fine for me on EC07 and then Netflix added support for Cyanogenmod in a recent update and that's when it stopped for working for me
circa881 said:
I'm pretty sure an app update did break it. It worked fine for me on EC07 and then Netflix added support for Cyanogenmod in a recent update and that's when it stopped for working for me
Click to expand...
Click to collapse
You don't happen to remember the last version that worked, do you? I never paid attention.
I am not a fly, i am levitation. I represent an entire generation. - Niki Minaj
current release is 1.5.2
here's 1.4.1 from when i still had netflix and was using it.
ciscogee said:
current release is 1.5.2
here's 1.4.1 from when i still had netflix and was using it.
Click to expand...
Click to collapse
I love ya man... and no, I don't want your bud light (flashback, anyone?)
EDIT: i don't love you anymore. The app worked fine, for about 3 seconds. After that, Netflix forced me to update before it would even let me sign in... and back to square one. Oh well. I didn't wanna watch anything on that tiny screen anyway. But, I'll call netflix tomorrow with the error code and see what they say. Maybe their dev team can fix it.
Ok, called netflix. That wasn't exercise in futility. She suggested I call samsung to get an update to 2.3.... Yeah.
Muddling through logcat, now. If I can decipher it, I'll see what I find. I'll also post it so that others can muddle through and see if they catch something. Anyone else having issues, I'd suggest posting one as well. Maybe we can find a common thread. It would make knowing where to hack the app a lot easier.
---------- Post added at 10:29 AM ---------- Previous post was at 10:16 AM ----------
http://dl.dropbox.com/u/30171389/Netflix logcat.txt
2 things I noticed.
1. on line 134 (if you are using notepad++) it says
I/WindowManager( 2466): Device ID doesn't match window display, ignored!
2. Both times I tried to start the app, with logcat going, it seemed to trigger the ticker and weatherbug to spool up and go through their paces (location update, set wallpaper, etc.) it also seemed to cycle the bat stats.... The battery stats may be a normal process, since it's starting a high usage app. I'm not sure.
Txwolf1980 said:
I love ya man... and no, I don't want your bud light (flashback, anyone?)
EDIT: i don't love you anymore. The app worked fine, for about 3 seconds. After that, Netflix forced me to update before it would even let me sign in... and back to square one. Oh well. I didn't wanna watch anything on that tiny screen anyway. But, I'll call netflix tomorrow with the error code and see what they say. Maybe their dev team can fix it.
Click to expand...
Click to collapse
That sucks.
Sent from my SCH-I400 using xda premium
It's still working on EC03...