Related
I have my EVo on MetroPCS, and i have been trying to get MMS and other things working for a while.
For the most part i have had everything working 100% at one time or the other, but most things not at the same time, due to kernel and apks.
I wrote a guide to getting the MMS working, but it relies on Ava' v2RC3 ROM, witch is a port from the incredible.
http://forum.xda-developers.com/showthread.php?t=739409
I was messing around with a stock Fresh 3.1 ROM, i rebooted to recovery and pushed the Mms.apk from the incrediable to the /ssytem/app folder, then rebooted the phone.
I started the messaging app.... it now looked like the MMS app from the Ava_v2RC3! So i tired to send a MMS to my email address....it sent!! SO to recap, OEM EVO ROM working 100% + the Mms.apk from the incredible + Token419's metrov3 flash = working MMS!!
BUT, now here in lies the problems:
When you send a message on the OEM EVO MMS, it takes you to the thread page so you can view the conversations of that person and you.
With the MMS app from the incredible it goes to "loading"....and hangs, it does nothing...BUT the MMS is still sent. Now if you open the MMS app and click on a person to view their conversation thread, it says "loading"....and hangs....
SO i think we need a custom Mms.apk from the incredible for the EVO for metropcs/cricket users!!!!!
I want to know if anyone out their can modify the Mms.apk to work on the EVO.
Or point me in some direction...
It just needs to finish loading the threads...thats alll...
If you compare the Mms.apk from sprint and the Mms.apk from incredible, the sprint is bigger. I have decompiled both files, but now i have no idea what i am looking at.
Now before we get in to posts about "did you try..."
-I tried Fresh and OMJ Froyo ROMs, both had same results from above.
-I tried pushing the com.htc.recources.apk .... framework-res.apk ... Rosie.apk from the incrediable to the phone (with working MMS), rebooted, still same results from above.
-I tried building a ROM from the Fresh and OMJ ROMs, and packing the framework files into it. Still same results from above.
-Downloaded handcent form market... was NOT able to send MMS at all with handcent. so i uninstalled it, then was able to send again.
i had the same results, this seems to plague not only the Evo but also the Hero Sprint stock MMS.apk's, i loaded a sprint port on my eris and had the same issue, swapped in an Mms.apk from a verizon rom and had the same results.
I too have been decompiling both Mms.apk's with the apktool and am going to run a dif later on the files to check for differences.
one thing i saw was some references to some sprint frameworks, im going to dig and ssee if i can find them as well.
A resolution seems to be simply swapping the mms.apk file, BUT i think the issue is actually in a framework file, and that swapping the mms.apk simply does not point to that framework that is not working properly on alternate carriers.
we will have to see
@token:
But i took the com.htc.resources.apk and the framework-res.apk from the incredible, pushed them to the EVO, still with same results. Did i miss a framework file??
All you need is Mms.apk from any aosp Rom. Bugless beast, or cyanogenmod for example.
chavonbravo said:
All you need is Mms.apk from any aosp Rom. Bugless beast, or cyanogenmod for example.
Click to expand...
Click to collapse
Tried it....did not work. I tried one from CM and one from AVa.
When you goto send a MMS, it seems to do nothing... and the send button gets grayed out.
i saw somewhere about a code change that needed to be done from hero rom to port to g1, but i cant find the thread with the code change in it anymore.
but pushing the raw frameworks from another rom will surely break the rom im guessing. i would stay away from that if at all possible but its definately worth testing out, to find where our issue is.
unfortunately my time will be very limited for the next month or so, have quite alot of stuff to attend to.
As suggested by chavonbravo, i tired the Mms.apk from the supersonic AOSP ROMs (for my EVO) With NO luck
So i thought, how about a Mms.apk from cyanogenmod for a Verizon phone...
It worked well, send and receive MMS, but sometimes it would fail on both.
Now the strange part, when you send a MMS with the cyanogenmod Mms.apk for the incredible, it will attach a XML file before the image. i think it was a SMIL.xml. So if you send a MMS to another mobile user, they cant see the image, because of the XML file. If you send the MMS to a email address, its ok, because you get the image and the XML, and you can open just the image.
Why is it sending the XML file too?
Now even stranger, after useing this method, i downloaded the handcent app. It also would send the XML file first. SO i then deleted the Mms.apk (adb shell rm /system/app/Mms.apk), rebooted, and the handcent STILL sent the xml......
getting closer...
xboxhacker said:
As suggested by chavonbravo, i tired the Mms.apk from the supersonic AOSP ROMs (for my EVO) With NO luck
So i thought, how about a Mms.apk from cyanogenmod for a Verizon phone...
It worked well, send and receive MMS, but sometimes it would fail on both.
Now the strange part, when you send a MMS with the cyanogenmod Mms.apk for the incredible, it will attach a XML file before the image. i think it was a samil.xml ?? So if you send a MMS to another mobile user, they cant see the image, because of the XML file. If you send the MMS to a email address, its ok, because you get the image and the XML, and you can open just the image.
Why is it sending the XML file too?
Now even stranger, after useing this method, i downloaded the handcent app. It also would send the XML file first. SO i then deleted the Mms.apk (adb shell rm /system/app/Mms.apk), rebooted, and the handcent STILL sent the xml......
getting closer...
Click to expand...
Click to collapse
I am not an expert on the MMS protocol(s?) but i believe the XML file IS THE MMS, and the picture is the attachment from the XML if that makes sense.
I believe the XML file contains the recipient/sender/subject/text/ and what attachments there are to the message, the picture is then the attachment and called upon by the XML file.
Definitely a good find and im still working on this as well, my time is just limited but i have a few things i want to try.
one thing i noticed when i unpacked a sprint based mms.apk file was that it was calling on the specific hardware (hero) in this case, and since the app i dropped in was desirec (eris) it didnt match up, im going to go through and edit that to point to the proper frameworks to see if i can at least get it working on my phone, but that could explain why the incredible didnt work on the evo.
Im also toying with getting a AOSP or Cyanogen one together, since that would be legal to distribute i belive, even if i do find a solution, it will be instructions, as i dont want to edit/repackage/redistrubute proprietary files without consent, which i dbout we would get since we are taking their hardware/development to use on an alternate carrier.
i found this:
http://www.w3.org/AudioVideo/
which points to SMIL, which is the spec for MMS messages i belive, i belive it gets put into an XML, then wrapped with SMIL, which links to all the stuff in the message.
I could be way off, but im pretty certian the XML file its sending is actually the MMS message itself.
I think our problem is still within the sprint mms.apk or an associated framework, because i think its still trying to interact with sprint's servers and not our alternate carrier.
I believe the XML file contains the recipient/sender/subject/text/
Click to expand...
Click to collapse
Nope...just images info.
here is a sample of the SMIL.xml file....
Code:
<smil>
<head>
<layout>
<root-layout width="320px" height="480px"/><region id="Image" left="0" top="0" width="320px" height="320px" fit="meet"/>
</layout>
</head>
<body>
<par dur="5000ms"><img src="screenshot_3.png" region="Image"/></par>
</body>
</smil>
one thing i noticed when i unpacked a sprint based mms.apk file was that it was calling on the specific hardware (hero) in this case, and since the app i dropped in was desirec (eris) it didnt match up, im going to go through and edit that to point to the proper frameworks to see if i can at least get it working on my phone, but that could explain why the incredible didnt work on the evo.
Click to expand...
Click to collapse
I saw that too, when i unpacked the sprint one.
Now this is funny... Incredible users putting the EVO Mms.apk on the incredible and it works fine!!!! LOLOLOL
For anyone having a problem with pictures showing up from contacts in the stock MMS application on Froyo ROMs, the EVO Mms.apk works fine.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=754832
Also, you can't put an Mms.apk from 2.2 aosp on a 2.1 rom, and vice versa. The bugless beast Mms.apk works great for the stock 2.1 rom.
FYI...
Bug report:
Using the stock Mms.apk from a Incredible, you can not send a MMS with Wifi is on. It might be ROM specific, i am using Fresh 3.0.
xboxhacker said:
FYI...
Bug report:
Using the stock Mms.apk from a Incredible, you can not send a MMS with Wifi is on. It might be ROM specific, i am using Fresh 3.0.
Click to expand...
Click to collapse
Just curious, in your APN, do you have the type set to MMS?
If so that should tell it to send MMS via your mobile network even if you are connected to wifi.
token419 said:
Just curious, in your APN, do you have the type set to MMS?
If so that should tell it to send MMS via your mobile network even if you are connected to wifi.
Click to expand...
Click to collapse
Yes it is... i am using your V3.5 (also tired v3.0) Now when i used a ROM based on incredible ported to the EVO, it sent fine with your v3 and sent fine with WIFI on.
im almost certain its a framework issue, and the reason the incredible mms is working is that its not calling in the framework that sprint has, its a bandaid so to say, not a resolution. Im assuming if you went through the Mms.apk from incredible and aligned all the framework calls that it may work, with wifi, but that may break the Mms again.
I just havent had the time to do a dif on the sources to compare where there are differences yet. but i think that will provide us some good information as to where the issue is.
Also im hearing reports of the paid Mms.apk not sending some pictures correctly, he can send anything that has been sent to him previously (i.e. resized properly) and also can send pics resized from his pc, so even the paid solution Mms.apk needs work. Hopefully we can nail this down and potentially even get the settings 100% for our carriers so that it will resize anything and work well
Alright, movie time, then bed, then work, then vacation!! Ill check back in a few weeks when im back
token419 said:
im almost certain its a framework issue, and the reason the incredible mms is working is that its not calling in the framework that sprint has, its a bandaid so to say, not a resolution.
Click to expand...
Click to collapse
Then why are the Incredible guys putting the EVO Mms.apk on the incredible and it works fine?
That would tell me that that, both Mms.apk are calling the same thing....
xboxhacker said:
Then why are the Incredible guys putting the EVO Mms.apk on the incredible and it works fine?
That would tell me that that, both Mms.apk are calling the same thing....
Click to expand...
Click to collapse
The Mms.apk is what sets up what com.android.xxx libraries it pulls up. for example if the sprint one pulled up com.android.sprint.mms.settings.blah, and you use the verizon one that points to com.android.verizon.mms.settings.blah, then it isnt calling the broken framework to run the instruction on.
Thats just an example, not based on any findings.
Whats interesting though is that the Cyanogen and AOSP roms are failing, which as far as i know only reuse a few things from a base rom (libs and whatnot), so what im thinking is to find out a vendor tree for cyanogen and see which frameworks/libs etc that they pull from an original rom that don't get built from cyanogen sources, and that will help us narrow down what could be not working correctly.
Just a thought, ill have to experiment when i get back from vacation.
Eager to see if anything arises
Phew, I've finally got a 99% working MMS solution on my EVO on Cricket. I can send and receive everything however you have to jump through a tiny hoop for sending, pretty livable though until a real solution comes out.
I am using the latest APNs posted around the forums for Cricket/Android:
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="2">
<apn name="CDMA-MMS" numeric="46605" mcc="466" mnc="05" apn="mms" user="my#[email protected]" server="NA" password="cricket" proxy="wap.mycricket.com" port="8080" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="http://mms.mycricket.com/mycricket/mms.php" type="mms" />
<apn name="8960-MMS" numeric="46605" mcc="466" mnc="05" apn="mms" user="" server="" password="" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="http://10.113.63.8:8080/12345=abc" type="mms" />
</apns>
I haven't gone back and tested with previous APN settings, but I know this is working for me for sure.
You still cannot use the MMS.apk from a Sprint or AOSP based rom. You need to have one from a Verizon based rom. I am using the MMS.apk from the Incredible as was posted in another thread I believe. I think this is the one ripped out of AVA Froyo V2RC3.
I did finally get MMS working under V2RC3 one I realized my real problem after the APN settings. The MMS app by default has the MMS size set too high for cricket. It was up over 1mb. Once I dropped the size of MMS down to 500k everything started sending.
I have installed this MMS.apk on to the Fresh 3.2 rom for EVO. As it has was stated earlier in this thread I think it is allowing me to send just fine, however it cannot load a conversation. I can see multiple conversation but if I try to open one up it just goes to "loading".
As a work around I am now using Handcent as my primary messaging app. It will allow me to send/receive all regular texts, receive MMS, and view conversations. It won't send an MMS for some reason, so for that I just go to the picture I want to send, select share, and then use the "stock" MMS app to send the picture, then back to Handcent. Not pretty but highly functional for now and certainly not a major pain in the ass.
The REAL trick which may have allowed MMS to work a while back if I had known was to get that MMS size down to like 500k or something. I bet I could have been sending MMS long ago if I had done that.
As far as getting the Incredible MMS apk to work, it's definitely a missing library/framework problem. I had to open the APK and resign it in order to attempt to install it on the CM6 rom (installed without a hitch on Fresh) and after resigning the next error I get is that there are some missing shared libraries. If someone who knows more about what they're doing can determine what libraries the APK requires maybe those can easily be loaded into whatever ROM someone wishes to use?
I also get no MMS in or out when Wifi is on.
I would just stick on the Ava Froyo V2RC3 rom since MMS works so fantastically on it, but Youtube can't play anything worth a damn over 3G.
Can you explain what apn settings you changed? Im following the guide that's here that works for everyone else except me and I'm willing to try anything right now!
Swyped from an HTC Evo on MetroPCS...
Dunno how many other people share my feelings, but I love the AOSP/CM6 browser more than HTC's browser. If one of you kind developers wouldn't mind, I'd love to see the AOSP or CM6 browser ported to Sense or installable on Sense.
So far what I've tried is simply renaming HTC's browser to Browser.apk.bak, and then moving CM6's Browser.apk to my phone. I then rebooted and tried to run it, but it force closed instantly. I've attached the logcat for anyone that is interested.
I'm gonna see if I can install the apk.
edit: no bueno; even after installing it, it force closes when opening.
I've been trying to do the exact opposite but haven't gotten any replies from my posts. I love cm6 but would rather have the htc browser. Good luck
i'm searching for the same thing found a possible that show's u how to do it but it just F/C on me too will be searching too
What I liked about the HTC browser was that you could pinch it. I'm surprised that Google includes this functionality in Android/Froyo but not in their own browser.
So like the 2nd poster, I'd like to see a pinchable (e.g. HTC) browser in CM6.
I posted this in one of the Ninjamorph tutorial threads but it is basically dead so posting it here.
Trying to mod all the notifications icons using Ninjamorph. This is what I did:
Replaced all of the notification pngs with different ones of the same name. This worked however the radio, 3G, & GPS are still the same as before. It did change the Wifi, battery, & bluetooth. I've also looked in the framework/drawable-res.apk for the original ones still showing up and can't find them. All of the drawable-hdpi\stat_sys_xxx.png have been replaced with the new. Why in the world do the old on some still show up?
Does anyone know where these might be located? Also, do I have to modify an xml somewhere to get all of them changed?
Thanks.
Ok...thought I had found the answer to this but not quite. Figured out the 3G and radio are in htcresources.apk but still can't find the GPS pngs. I may just be overlooking something but can someone point me to their location so they can be themed?
Thanks.
Got screen shots ?
Sound sweet I want to learn how to theme with ninjamorph as well
I tried to theme the calculator icon but that didn't work & messed up the app .
Had to delete the app & re-install it :-(
Sent From One BadAss Rooted Evo 4G On Myn's Warm 2.2 Rls 5 Steroids Via XDA App. ;-)
are you running a rom or something cause then ones ur trying to change might be in a different spot from the ones your changing
How I did it
There can be two reasons why your changes are not reflecting:
1.
While navigating through the /system/framework folder I realized that there was another .apk file in the folder. Just check if there are any other .apk in the same folder as framework-res.apk that might contain the images.
2.
Are the images that you are trying to replace ending with .9.png? The 9.png format is different from the normal png and needs to be compiled before it can be used. I will post the link to thread as soon as i find it.
The url is on developer.android.com /guide/developing/tools/draw9patch.html
I posted this on the CM Slide forum but I haven't gotten any actual help yet, I'm hoping someone here on XDA will be a bit more helpful
CM6/7 comes with the Gallery3D apk, which looks nice. However, it's slow. I hate opening it and sitting there waiting for the pictures to load, especially in folders with a lot of pictures.
It's even more annoying when I am trying to send an email/picture message and I have to sit there for a couple minutes waiting for them to load.
Does anyone have the stock gallery apk, or a good alternative? Or ANYTHING which will help whatsoever?
Thanks
So I don't know what this is, but the thread looked similar.
http://forum.xda-developers.com/showthread.php?t=775897&highlight=gallery
You could try that out, the file on mediafire there is Gallery.apk, but I haven't tried it out.
Thanks for the quick response
I actually did try doing that, it worked but it was very..unorganized, I guess. And no way to change it around to make it better
I'm currently using JustPictures...hoping to pull the stock gallery from my girlfriends Slide when I see her..but I was hoping maybe someone had a nandroid backup or something.
I looked in the stock Eclair ROM and it' says HTCAlbum.apk. I'll upload the .apk for ya, I hope it helps you out somewhat.
EDIT: AlbumStuffs.zip has 3 files, the .odex and 2 lib files. Lemme know if that helps out Now I'm interested in if this works.
Thank you!
I'm going to try it now, I'll edit this when I find out what happens.
*edit*
No good. I get Application Not Installed.
I'm currently trying to push to /system/app via ADB, hoping that helps.
Any ideas on what might work if this doesn't?
Thanks!
**edit 2**
ADB install gives me Install Failed Missing Shared Library, I'm guessing there's another file that goes with the HTCAlbum.apk, maybe an odex or whatever?
Would you mind maybe doing a quick search for anything associated with it, and upload if you find it? I'd appreciate it
Thanks again.
i would like the samething. i hate that the 3d gallery lags!!
well, I've tried pushing those files, fresh installs, and a few other unorthodox methods... can't seem to get the 2D gallery working from the HTC based Album. I'm not a dev at all, so I really can't do much else to help out here. Maybe a dev will glance over here while they are bored and looking for a project or something? Good Luck though, hope you are able to get this working.
You can't pull the stock gallery for several reasons. One, it's odexed, and our rom isn't, which might be why you get app not installed. Frameworks aren't compatible. Even if it was deodexed, it wouldn't work, since stock htc apps are tightly tied into com.htc.resources.apk and other htc and tmobile framework apk files which cm roms don't have. It is probably impossible to run htc system apps as standalone apps on other roms. Personally I don't have gallery issues running cm7, but if you do you will have to find a market alternative.
You can also select a tool like astro when attaching images when it asks you what you want to use to select an image, if you are having issues with the stock gallery from google.
Sent from my T-Mobile myTouch 3G Slide
Hi, rather new here so I can't post in the thread on the developers board. Thought I'd try here. I recently flashed Tiny's latest CM 10.1 nightly rom and I really like it so far. There are a couple of issues but after messing with it for a while, it's mostly smooth and works well. My biggest beef, aside from those couple issues is Netflix. The app loads and I can select a show, but when I try to load a video, I just get the red loading screen that goes on forever until I hit the back button. I tried an older apk, and it wouldn't load, period (1.5.2), which I guess is to be expected when running Android 4.2. I tried 2.1 and I got the same issue with the red loading screen. Tried loading it in the browser and I got the usual page that tells me I need a certain browser for it to work. The app worked just fine in the official CM 7.2. Is there an option in settings I'm missing or something or does it not work on this rom (which I don't see why it wouldn't)?
Other naggy issue is epsxe. It works alright but if I press a volume button, it either increases or decreases all the way and all buttons freeze. Nothing works. Home, menu, power button, touch, etc (yet the emu keeps going and the music keeps playing). Sometimes when I press an on-screen button to move, it's like the button gets stuck and the character keeps moving in that direction. I have to remove the battery to reboot. Did not have this issue in cm 7.2.
Other than that, awesome rom and thanks, Tiny, for working on it.
EDIT: Well, I just tried using epsxe again and it even worked when using the volume button. Not sure why it worked except that I let the game load for a bit before pressing anything. After that, it worked just fine. So, I guess it may be even an app issue on 4.2, rather than the rom. Hope Netflix is as easy to get working.
Netflix hasn't worked on JB or ICS. Known issue since day one. Probably won't be fixed as it's not a high priority in the overall picture.
...sorry...I was on the phone...
omniatic said:
Netflix hasn't worked on JB or ICS. Known issue since day one. Probably won't be fixed as it's not a high priority in the overall picture.
...sorry...I was on the phone...
Click to expand...
Click to collapse
Well, that's disappointing. I really like this this rom but Netflix was one of the biggest reasons to keep using this device. It's mainly used as a tablet now and I don't want to buy anything else right now. Funny thing, Netflix was the only reason I didn't switch from Windows 7 to Linux. I figure, if I'm paying them every month, I should be able to play their vids on any device I please and it irks me that I can't even get it working in the android browser. Oh well. Thanks for the quick response.
EDIT: Well, I did some research and found that Netflix 1.81 seems to work to an extent. I get sound and subtitles but no video. Going to look into it some more.
Kaepernick said:
Well, that's disappointing. I really like this this rom but Netflix was one of the biggest reasons to keep using this device. It's mainly used as a tablet now and I don't want to buy anything else right now. Funny thing, Netflix was the only reason I didn't switch from Windows 7 to Linux. I figure, if I'm paying them every month, I should be able to play their vids on any device I please and it irks me that I can't even get it working in the android browser. Oh well. Thanks for the quick response.
EDIT: Well, I did some research and found that Netflix 1.81 seems to work to an extent. I get sound and subtitles but no video. Going to look into it some more.
Click to expand...
Click to collapse
It works on better supported devices on ICS and JB. The issue here is the codecs and hardware support / drivers which will not be fixed for now. Just confirming its not androids fault or Netflix's.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
It works on better supported devices on ICS and JB. The issue here is the codecs and hardware support / drivers which will not be fixed for now. Just confirming its not androids fault or Netflix's.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So no amount of tinkering with older apks and workarounds (to make it so the app uses older netflix video players) will work because the rom/hardware simply doesn't support playback? I was looking at some other threads and google and a lot of people seem to be having trouble getting Netflix to work on 10.1 and Android 4.2 in general. Seems when the app detects Jelly Bean, it uses its newest video player, which has some problems on some devices. Forcing it to use an older player seems to work for some people. Adding a line to the code to make it use player "6" instead of "10" or something. Haven't actually applied anything to the app to try it because I'm a complete novice at this.
You're the expert and I assume if there was an easy method that wouldn't screw anything up in the CM 10.1 build, you'd apply it. I do appreciate the work you and others are putting into these roms and other than this Netflix issue, it rocks. I may go back to CM 7.2 after a bit but I'll definitely keep an eye on your updates and try them out.
Kaepernick said:
So no amount of tinkering with older apks and workarounds (to make it so the app uses older netflix video players) will work because the rom/hardware simply doesn't support playback? I was looking at some other threads and google and a lot of people seem to be having trouble getting Netflix to work on 10.1 and Android 4.2 in general. Seems when the app detects Jelly Bean, it uses its newest video player, which has some problems on some devices. Forcing it to use an older player seems to work for some people. Adding a line to the code to make it use player "6" instead of "10" or something. Haven't actually applied anything to the app to try it because I'm a complete novice at this.
You're the expert and I assume if there was an easy method that wouldn't screw anything up in the CM 10.1 build, you'd apply it. I do appreciate the work you and others are putting into these roms and other than this Netflix issue, it rocks. I may go back to CM 7.2 after a bit but I'll definitely keep an eye on your updates and try them out.
Click to expand...
Click to collapse
That may just work. I'm kind of a newb at smali but it may be worth a shot. I haven't heard of this workaround before. In theory it should work under software.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
That may just work. I'm kind of a newb at smali but it may be worth a shot. I haven't heard of this workaround before. In theory it should work under software.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, that gives me some hope, at least. Here's one of the threads I was looking at.
http://forum.xda-developers.com/showthread.php?t=2101525
On the last page, someone posted the code that enabled it to work on theirs.
EDIT: I tried the Xposed app workaround, by the way, which did not work for me, using 1.8.0 (thought it was 1.8.1 but wasn't. Plan on trying that next) or the newest version. I realize that these are different devices, but I'm hoping there's a way to get it to work on ours. I wonder if there's a way to trick it into thinking it's Gingerbread instead of ICS (in the thread) and using the player that works on CM 7, if it would work?
Kaepernick said:
Well, that gives me some hope, at least. Here's one of the threads I was looking at.
http://forum.xda-developers.com/showthread.php?t=2101525
On the last page, someone posted the code that enabled it to work on theirs.
EDIT: I tried the Xposed app workaround, by the way, which did not work for me, using 1.8.0 (thought it was 1.8.1 but wasn't. Plan on trying that next) or the newest version. I realize that these are different devices, but I'm hoping there's a way to get it to work on ours. I wonder if there's a way to trick it into thinking it's Gingerbread instead of ICS (in the thread) and using the player that works on CM 7, if it would work?
Click to expand...
Click to collapse
I don't have a netflix account currently (had it and didn't use it), so I can't do much testing but based on the link you showed me, the app should work fine. Try the init.d script linked in the github in the thread you posted. Are you familiar with pushing files to your device? You just need to copy it to /system/etc/init.d and add execute permissions. Usuaully I use read-write-execute for user and read-execute for group and other.
tiny4579 said:
I don't have a netflix account currently (had it and didn't use it), so I can't do much testing but based on the link you showed me, the app should work fine. Try the init.d script linked in the github in the thread you posted. Are you familiar with pushing files to your device? You just need to copy it to /system/etc/init.d and add execute permissions. Usuaully I use read-write-execute for user and read-execute for group and other.
Click to expand...
Click to collapse
The xposed_init file under assets? Can't say I've ever tried this before. I know how to add files to that folder, but no idea how to copy it to a file or whatever that would work. Don't know how to execute permissions either.
Looking things up, I can't just add a file to my sdcard and use ES File explorer to add it to the init.d folder? I copied one of the files on my desktop and opened it up with notepad. It sadly didn't help me. Like I said, total novice with android here or this stuff in general. Would like to give this a shot though. Do I add the text to notepad and then delete the .txt or do I need to make a .js file? As for permissions, do I just add r rw and x to the file?
Kaepernick said:
The xposed_init file under assets? Can't say I've ever tried this before. I know how to add files to that folder, but no idea how to copy it to a file or whatever that would work. Don't know how to execute permissions either.
Looking things up, I can't just add a file to my sdcard and use ES File explorer to add it to the init.d folder? I copied one of the files on my desktop and opened it up with notepad. It sadly didn't help me. Like I said, total novice with android here or this stuff in general. Would like to give this a shot though. Do I add the text to notepad and then delete the .txt or do I need to make a .js file? As for permissions, do I just add r rw and x to the file?
Click to expand...
Click to collapse
Yeah, you can add it to notepad and remove the .txt at the end but it uses different line breaks in Windows than what Linux uses so the script may not work right. I'm not sure though. The worse thing that can happen is nothing. Android doesn't use .js which is Javascript. For permissions, yes that will work.
ealassi content
tiny4579 said:
Yeah, you can add it to notepad and remove the .txt at the end but it uses different line breaks in Windows than what Linux uses so the script may not work right. I'm not sure though. The worse thing that can happen is nothing. Android doesn't use .js which is Javascript. For permissions, yes that will work.
Click to expand...
Click to collapse
Tried it. Not sure if I did it right. Most likely not. lol But in any case, it doesn't work. Getting a bit tired, so I may just relent. I'm sure many who are more experienced have tried already.
Just curious: If your primary use for your old Dinc is as a portable Netflix viewer, then why not just flash back to a stable GB-based ROM and enjoy?
Seems that would be a lot simpler than trying to get Netflix to work on JB, especially if you're not doing anything with the phone that requires JB.
MysticCobra said:
Just curious: If your primary use for your old Dinc is as a portable Netflix viewer, then why not just flash back to a stable GB-based ROM and enjoy?
Seems that would be a lot simpler than trying to get Netflix to work on JB, especially if you're not doing anything with the phone that requires JB.
Click to expand...
Click to collapse
I like Jelly Bean. I like how it looks and feels. It's a more mature Android. Plus, I like keeping up to date with software. It's kind of nice to have 4.2 running on the aging, yet good o'l Dinc, when some newer devices don't even have 4.1 yet officially.
Also, I got it working, by the way! Before, when I downloaded the newest one onto 10.1, it would just continuously load when picking a video and not work. After tinkering, I got it to play sound but no video. I could tell that the video player was different than the one I used on 7.2 (also, the newest app). I switched back to 7.2 for a bit and downloaded my apps. I backed everything up using Clockwork mod so I could go back to it whenever. Then I backed up all the Apps with Titanium Backup. I switched back to Tiny's 10.1 and restored the apps. I tried out Netflix and it worked. It was using the same player it used on 7.2. I don't know if it detects Jelly Bean when you download it from Google Play or if it does it when you sign in to your account. When I restored it, I was already signed in, so maybe that's it. At any rate, it works.
Well, I spoke too soon. It did work for the first few videos but then stopped. I tried uninstalling and reinstalling with the Titanium Backup, but when I try to choose a video, it says I've been signed out. I sign back in and I'm back to the forever loading red screen. So yeah, I think it detects which OS I'm on as I sign in. Just a guess though. Just shows that it has nothing to do with your ROM aside from their newest player not working properly on it. It can indeed be fixed via the software with some tinkering.
Can you check the value for int name="nflx_player_type" in /data/data/com.netflix.mediaclient/shared_prefs/nfxpref.xml from a working Netflix in Gingerbread? Easier yet, pull that file from your Netflix backup from Gingerbread for me. Check for passwords in the file and clear them out before giving it to me for security.
tiny4579 said:
Can you check the value for int name="nflx_player_type" in /data/data/com.netflix.mediaclient/shared_prefs/nfxpref.xml from a working Netflix in Gingerbread? Easier yet, pull that file from your Netflix backup from Gingerbread for me. Check for passwords in the file and clear them out before giving it to me for security.
Click to expand...
Click to collapse
Here you go. Says It's using Player 9. I have read that 10 is the newest player. At least I believe so.
Edit: just checked that file on 10.1. It says player 10. That means it switched when I signed back in.
Kaepernick said:
Here you go. Says It's using Player 9. I have read that 10 is the newest player. At least I believe so.
Edit: just checked that file on 10.1. It says player 10. That means it switched when I signed back in.
Click to expand...
Click to collapse
Hmm, if you edit that file back to 9 and open Netflix does it work?
tiny4579 said:
Hmm, if you edit that file back to 9 and open Netflix does it work?
Click to expand...
Click to collapse
Yes and it didn't work. Then I tried "6". Didn't load. I tried 9 again and for whatever reason, it loaded. It works just fine now, using the same player it did in 7.2. The kicker is that I check the XML file again and it changed somewhat. It now says "6" and it looks different. I believe the Player line used to be before the Logged in line. Now the logged in line is last. If there was some way to force it to use 6 every time, even when logging in, we'd have a working netflix app on your rom.
Maybe "old app version=17" is the key, I don't know.
EDIT: Exited the app. Still works. Rebooted the phone. Still works. There's no log out button, so I assume to log out, I need to clear data, which I assume would just put me back at square one. Seems to be working fine now, as long as I stay signed in. If I somehow have to sign in again, I'll check the xml file.
Attached the file. Just edited the user id part.
Well, it was working. Then it quit. I checked the xml file and it had switched to 10. Didn't sign in or out or anything. Tried the 6 file and it immediately switched back to 10. So, I uninstalled and then installed 1.8.1. Replaced the nfxpref file with the one I backed up and it worked. Funny thing, it's actually using an older version of the player. I believe that may actually be "6". In cm7.2, it said "9" and was using a newer version of the player (newer than the one I'm using now). It seems to work well so far. Haven't tried updating from this yet, to see if the newest one works by updating, but I doubt it would work anyway. I did notice that in the shared prefs folder, there's only one other file with the nfxpref file. In the newest version, there looked to be about six or seven other files.
Watching this with interest, if you guys figure it out please post a guide and link to it because you're not alone. My Netflix stopped working when I upgraded to 10.1 as well (interestingly it worked fine on my ICS One-Click ODIN Rom that I got last June, not CM) and this was the first thread to pop on my google search as I've started looking for answers.
*UPDATE* Got mine working using the directions in this thread: http://forum.xda-developers.com/showthread.php?t=2101525
Hope this helps!
Kaepernick said:
Well, it was working. Then it quit. I checked the xml file and it had switched to 10. Didn't sign in or out or anything. Tried the 6 file and it immediately switched back to 10. So, I uninstalled and then installed 1.8.1. Replaced the nfxpref file with the one I backed up and it worked. Funny thing, it's actually using an older version of the player. I believe that may actually be "6". In cm7.2, it said "9" and was using a newer version of the player (newer than the one I'm using now). It seems to work well so far. Haven't tried updating from this yet, to see if the newest one works by updating, but I doubt it would work anyway. I did notice that in the shared prefs folder, there's only one other file with the nfxpref file. In the newest version, there looked to be about six or seven other files.
Click to expand...
Click to collapse