Related
Well since wifi tether does not work with this build. I was just curious if the one built into cyanogenmod is free just like the wifi tether app in the market?
slebron33 said:
Well since wifi tether does not work with this build. I was just curious if the one built into cyanogenmod is free just like the wifi tether app in the market?
Click to expand...
Click to collapse
OK, first of all....what ROM are you using right now? CM7 or a different one because it sounds like you're talking like we're right there with you dude! The WiFi tethering in CM7 works flawlessly and YES is build in so is FREE! The only thing is that you can't use the one in the market prior to trying to use the build in one because it will break the build in one and that will open up a can of worms!
For future questions or anything, try to explain things a bit in detail and include what rom you're currently on....if you're talking about a kernel include that as well! Don't always assume that we're mind readers or anything.......Oh and NO I'm not catching an attitude, I just like to use exclamation points...lol
Disclaimer--- this is simply a thread to discuss and rant about issues with wifi calling related to MMS sending and retrieval as well as blurry mms. This is also to keep it in one place rather than on other posts where it becomes unrelated to the original topic. I have tested sending MMS through stock, hand cent, and go SMS and am unable to send pictures. This said I am using kl1 deodexed rom by whitehawx. This is just the beginning of my research and observation. Another user (docmjldds) mentioned that it was working on zombie rom but only using hand cent. Please post what roms you have tested and whether or not sending over wifi calling works for you. Also post what SMS app you are using and what file size it was also. Screenshots help but keep them G rated. Also post whether the pics where blurry. If it helps post what types of mms mods you have flashed. I will clean this up more when I get to a computer and update the list... please feel free to rant and rave. Just don't take it personal.
You can help research by posting the following:
1.) Rom you are using and version
2.) Kernel you are using
3.) Any mods, scripts, etc.
4.) Using wificalling only, NOT 4g, attempt to send MMS to yourself or other person using either
1.) Stock Rom
2.) Other sms app (please state which one works)
3.) State whether or not it DID or DID NOT compress the image when sending and if it failed, or when receiving if it ends up blurry.
My rom:
Deodexed KL1 by Whitehawx. Using Fauxkernel 07b5 default with no scripts or mods added.
[stock mms app] = unable to send large pictures but can send decent size. Takes more than 10 minutes for me to send. Compresses the images right away.
[Go Sms and Handcent] able to send regular sized pictures but not large ones >1mb. Still took 10 minutes to send. Compression occurred.
Did not notice any blurriness from the pictures that I did receive.
Updated List for ROMS able to send MMS/Large sized MMS, etc
--ZombieRom 3.0 Thank you Docmjldds for the heads up on this info.
Updated List for tweaks, mods, tricks to get MMS to send.
--Will update as people post.
Thanks for your contribution. I will post better screenshots of pictures sent and received.
I can send through Go SMS ...
I am running a mishmash of ROM's I threw together myself, I know not much help
It is 2.3.6 with KL1 ...
Using the alternate APN but transferred all the MMS settings to the new APN ...
I can send while on Wi-Fi with wifi calling enabled, BUT, it does seem to take a very long time ...
yes it helps. I noticed I sent one large pic about 200 KB and the other was less. After ten mins I got a link to download the smaller of the two. The bigger failed. No blurriness though. I got notifications from all the SMS apps with the smaller pic.
tcboo said:
I can send through Go SMS ...
I am running a mishmash of ROM's I threw together myself, I know not much help
It is 2.3.6 with KL1 ...
Using the alternate APN but transferred all the MMS settings to the new APN ...
I can send while on Wi-Fi with wifi calling enabled, BUT, it does seem to take a very long time ...
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
chib1panda said:
yes it helps. I noticed I sent one large pic about 200 KB and the other was less. After ten mins I got a link to download the smaller of the two. The bigger failed. No blurriness though. I got notifications from all the SMS apps with the smaller pic.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Not going to repeat the same old same old. I will simply watch and learn what others state. Until I see otherwise, I only ask users to try every ROM 2.3.6 based and tell me if they can specifically send and receive with the following parameters
1. Use WiFi calling enabled. I am NOT interested in 4G. That's NOT the issue here.
2. Be able to enable 1.0Mb file sizes to send with MMS and NOT have files shrink to 16-26Kb file sizes.
3. Not have to R+R any mms.apk files from one source to get around blurry mms issues.
Now, based on these parameters, I am simply going to make the following statement regarding what works for me and specifics. For those that have already heard me say this, hold your ears please since many users here may not have had the misery of reading my prior posts.
I have found that consistently only one ROM here for our model works. I have no idea on why. I am only stating to try the following.
The Zombie based ROM, currently 3.0 version here. Install per OP directions. Then install Handcent SMS third party app. It's the only app that works consistently for me where I can send large sized MMS files (350-950Kb sized) using WiFi calling enabled. It should only take a few seconds to send. And yes, these are the sizes received. I am using 2-3Mb pictures I take with our phone, using the 1.0Mb MMS settings for sending in the Handcent preference setup for MMS. You can use the stock message app to read the same file, AFTER it is first received with Handcent, BTW. Oh, like GoSMS Pro, you don't have that arrow showing in the mms file as if it's a video file you are seeing, BTW. I have seen this asked by others. But Handcent does not give that message "Unable to send. Wait till Network is available message". GoSMS Pro does give that message for me.
I have posted enough screen shots on various development threads so I won't clutter up the post here. If users ask, I will post to prove that with the ROM mentioned and Handcent, it works, but I cannot get this to work with any other ROM. Again, NOT 4G and not 16-26KB file sizes that I am interested specifically in.
1) didn't use 4g
2.) File over 1mb did not com press with hand cent nor go SMS but did with stock. I couldn't test what file size it was received as because large file never was sent.
3.) Did zombierom dev state what specific tweaks mods or scripts he used that other 2.3.6 roms. Don't have in them?
4.) I will have more time tomorrow so I can flash zombie and see if I can duplicate the same as you.
Thanks
chib1panda said:
1) didn't use 4g
2.) File over 1mb did not com press with hand cent nor go SMS but did with stock. I couldn't test what file size it was received as because large file never was sent.
3.) Did zombierom dev state what specific tweaks mods or scripts he used that other 2.3.6 roms. Don't have in them?
4.) I will have more time tomorrow so I can flash zombie and see if I can duplicate the same as you.
Thanks
Click to expand...
Click to collapse
Before 3.0 just posted it basically has been a plain Jane ROM much the same as the Original MrX first 2.3.6 or Whitehawk 2.3.6 ROM. No themeing to speak of. In fact, it doesn't even have the 13-14 toggle above the notification area. I would have to look at the original change-logs to see specifically what exact tweaks etc may have been incorporated. AFAIK, nothing at all different from the others. I can only add that I routinely change to the Faux kernels since I want BLN support, and the kernel he uses for stock doesn't offer it. But Kernels never played any role in what made this work or not work. Just an fyi.
Do you think kernel has anything to do with it? I would be very surprised to find out. Plus, I want to know why my wife's Mytouch 4g is able to send any type of picture, text quickly with good results?? whats different about HTC's wifi calling than ours? I know hers is activated by an actual app like other legacy wifi calling phones still do. I wonder if the way it is now implemented messes with sending MMS.
Docmjldds said:
Before 3.0 just posted it basically has been a plain Jane ROM much the same as the Original MrX first 2.3.6 or Whitehawk 2.3.6 ROM. No themeing to speak of. In fact, it doesn't even have the 13-14 toggle above the notification area. I would have to look at the original change-logs to see specifically what exact tweaks etc may have been incorporated. AFAIK, nothing at all different from the others. I can only add that I routinely change to the Faux kernels since I want BLN support, and the kernel he uses for stock doesn't offer it. But Kernels never played any role in what made this work or not work. Just an fyi.
Click to expand...
Click to collapse
chib1panda said:
Do you think kernel has anything to do with it? I would be very surprised to find out. Plus, I want to know why my wife's Mytouch 4g is able to send any type of picture, text quickly with good results?? whats different about HTC's wifi calling than ours? I know hers is activated by an actual app like other legacy wifi calling phones still do. I wonder if the way it is now implemented messes with sending MMS.
Click to expand...
Click to collapse
My wife also has a MyTouch4G and I believe it really has something to do with the newer implementation used by our style WiFi calling. I know that TMobile has already acknowledged to me it's an issue they are looking at. I really have a feeling they know they are intentionally overcompressing on the newer models like our SGS2. The Sensation I used to use also was on the older standard and worked just fine, as long as the model and brand name was correct in the build.prop files. Kernel is NOT an issue. I have basically tested every Kernel there is with all the ROMs. Zombie consistently works with any of them. Anecdotal here, the Revolution ROM that I believe is retired because of some XDA issues with the Developer, also did work, like the Zombie ROM too, but I am going on another close friend here that remembers it worked for him.
When I get the time, I have several programs that can do a file by file comparison. Takes a lot of time, but that's the only way I know of to see what is different from the base that Zombie is using vs the others. My feeling is it's a source files used issue. Just a guess.
EDIT:
PS... I have all the older files for the legacy method here along with the necessary build.prop edits that are required to make that older HTC method work. Not sure it will even be worth it, but I am going to try adding that stuff, lib files and APK and edits to see if it's even possible to use the older wifi calling.
It may also mean also going back to Android 2.3.5 base. I'm pretty ADD about this subject. I just need to find the time
Sounds like that too. I hope they fix it. It looks like you have more time than I do for testing. Ill be getting my new white one tomorrow so that means rerooting and installing everything again.
Edit-.saw your edit. That would be great if you could get that working.
Docmjldds said:
My wife also has a MyTouch4G and I believe it really has something to do with the newer implementation used by our style WiFi calling. I know that TMobile has already acknowledged to me it's an issue they are looking at. I really have a feeling they know they are intentionally overcompressing on the newer models like our SGS2. The Sensation I used to use also was on the older standard and worked just fine, as long as the model and brand name was correct in the build.prop files. Kernel is NOT an issue. I have basically tested every Kernel there is with all the ROMs. Zombie consistently works with any of them. Anecdotal here, the Revolution ROM that I believe is retired because of some XDA issues with the Developer, also did work, like the Zombie ROM too, but I am going on another close friend here that remembers it worked for him.
When I get the time, I have several programs that can do a file by file comparison. Takes a lot of time, but that's the only way I know of to see what is different from the base that Zombie is using vs the others. My feeling is it's a source files used issue. Just a guess.
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
chib1panda said:
Sounds like that too. I hope they fix it. It looks like you have more time than I do for testing. Ill be getting my new white one tomorrow so that means rerooting and installing everything again.
Edit-.saw your edit. That would be great if you could get that working.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Just to show how lame TMobile support is, out on their tech Forums they are basically telling users NOT to even have wifi calling enabled. Below is a stock answer I see this mod. posting to everyone with issues complaining about this subject.
Being a retired bum, I do have some time on my hands. I can think of better ways to spend it, but this is one nut I really would like to crack. But at least there's a method on a particular ROM that does work. So deoending on importance of this feature will dictate what any user wants in a given ROM. BTW, don't know why the Zombie developer is placing his beta stuff outside of XDA, but there are references to links. Latest 3.1.1 includes update for the multiple toggles above notification area. Just an FYI...NOT...again NOT trying to be a Troll, but I can see how I can be accused, by now
IF...other ROMs would work, I would have no reason to state what to use...really...
http://www.androidzombie.com/az/Andr...x0.9KERNv2.zip
***********************************************************************************
TMobile Reply
8. Jan 11, 2012 8:42 AM (in response to sjmrshll)
Correct AnswerRe: MMS will not download while WiFi is enabled...
Hi!
Let me first thank you for being part of our community! We are happy to have you here and love to see you as an active participant. Unfortunately we cannot guarantee any of your services will work over the wi-fi network. Not being able to both send and receive MMS over wi-fi is an issue that can be slightly common.
If you have any further questions, please feel free to reply to this message or contact any member of the staff. Thank you and have a great day!
- Alicia B.
Community Moderator
1.) Juggernaut 4.1
2.) Faux .007
3.) ICS Mod
4.) No matter what the file size no MMS will come through while I am connnected to wifi calling. If I disconnect and switch to 4G it will go through provided it has synced with Google.
1.) Stock SMS App doesn't work. Neither does GOSMS which is my go to texting app.
2.) See above.
3.) Fails completetly on download or upload.
Hope this helps!
Haven't tried zombie but the only rom I have tried that lets me send and receive mms while using wifi is when I'm on complete stock with root of course but its not really too much of a hassle to just switch wifi off if needed while using jugs 4.1 if it ever does get too annoying I always keep a backup of my stock just in case... So I know it has to be something that's been removed from the custom roms that keeps the phone from auto switching to data from wifi when using mms
Sent from my SGH-T989 using Tapatalk
rickm8384 said:
1.) Juggernaut 4.1
2.) Faux .007
3.) ICS Mod
4.) No matter what the file size no MMS will come through while I am connnected to wifi calling. If I disconnect and switch to 4G it will go through provided it has synced with Google.
1.) Stock SMS App doesn't work. Neither does GOSMS which is my go to texting app.
2.) See above.
3.) Fails completetly on download or upload.
Hope this helps!
Click to expand...
Click to collapse
IT basically verifies what my claims have been. Something about the Zombie Rom is different to allow MMS to work correctly as long as Handcent is being used. I used Tmoble_SGH-T989UVKL1_Stock_Rooted.zip as a base 2.3.6 to compare with the latest Zombie ROM although versions of this ROM have always worked. Using a program that actually does a great job of side by side taking files withing a given folder to compare with another source of given files. All of the folders basically used the same exact files. The few times lets say that one ROM used a slightly different version lets say of wificalling.apk as an example could not break either the working Zombie functionality, nor could using the Zombie based file in the stock ROM would NOT make that ROM work either. IOW I tried to switch files between these two ROMs, to either create a working stock ROM, or break the function of the ZOMBIE Rom. Could not succeed in making or breaking opposing ROMs.
If it as you say it's probably the system framework differs somewhere. Causing mms not to send.
Sent from my SGH-T989 using xda premium
Coming from my nexus one, we needed specidifc kernels built to support wifi calling. Maybe this new wifi calling is implemented different
Sent from my SGH-T989 using Tapatalk
Killbynature said:
If it as you say it's probably the system framework differs somewhere. Causing mms not to send.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I am pretty much confident that you are correct it's a framework issue. I have used file comparison programs and rulled out every other source file, such as all of the lib files etc. And it has nothing to do with kernels. I have tested every kernel on all these ROMs and the same results occur, irregardless of kernel.
---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------
drzplaya1121 said:
Coming from my nexus one, we needed specidifc kernels built to support wifi calling. Maybe this new wifi calling is implemented different
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Nexus one was my first Android too. Bought it the first day of availability to the public, direct from Google back in Jan. 2010. The current Wifi calling is totally a different animal WRT our SGS2 phones. It's more or less based on the Network, itself, the proper Sim Card etc. Unlike the older WiFi calling that uses the Gans lib files and Build.prop edits, this doesn't rely on any of that stuff. And it's also a required Android 2.3.6 min. source. So yes...a totally different implementation.
I know this is an 'older' post but it helped me so here you go:
BeastMOD 5.0 (build Test13)
Sinergy kernel
no mods
The only way I can send mms over wifi is running Handcent. GO and stock wouldn't work. What ever zombie was doing made it's way into Melvins Rom
This issue is fixed in the ics leaks. Rom reconnects.to 4g momentarily to send or receive mms
Sent from my SGH-T989 using XDA
xUnreachablex said:
I know this is an 'older' post but it helped me so here you go:
BeastMOD 5.0 (build Test13)
Sinergy kernel
no mods
The only way I can send mms over wifi is running Handcent. GO and stock wouldn't work. What ever zombie was doing made it's way into Melvins Rom
Click to expand...
Click to collapse
I have the beastMOD 5.1 testbuild13 ROM also, but i could receive MMS and send MMS thru wifi in stock sms app. The only difference is that i have the darkside kernel.
Sent from my SGH-T989 using XDA
I'm using darkside rom with the included kernel, no mods or tweaks. WIFI calling and mms works fine, never experienced blurry mms.
Sent from my SGH-T989 using XDA
I used to have CM7 rom and toggling 2g/3g and GPS was not a problem. But since I moved to MIUI, if I click a 2g/3g toggle it only takes me to the Network menu and tells me that it is not possible to do it on Android directly...
Is there a ways around it, since it is working fine on Cyanogenmods?
I would be interested as well... I am currently using a utility from the market, but as you said, it only takes me to the settings screen, so I have to do 1 more click. All apps in the market mention that direct toggle is not possible.
If you say it works in CM7, then it must have been removed in the newer APIs perhaps?
I don't think so. CM7 I used was a very recent release, though still on 2.3.7 Gingerbread.
Now I am on MIUI which is about half a year older and it can't do switching.
i dont think this is poosible, maybe i might be wrong, but this is the security rules for android system set by google.
Well, since it is working on Cyanogenmod, it obviously IS possible.
impactor said:
Well, since it is working on Cyanogenmod, it obviously IS possible.
Click to expand...
Click to collapse
Yh i used it too on CM7. Have ya tried any of the apps in playstore
Edit.. never mind, they just take u too settings lol
Sent from my HTC Desire
Just install power toggles from market and convert it to system app using titanium. Then you can straight turn on off the GPS and 3g from its widget that you couldn't before. Tried this myself so I know it works.
impactor said:
Well, since it is working on Cyanogenmod, it obviously IS possible.
Click to expand...
Click to collapse
Yes, i said i might be wrong.
The other possibility can be if you are developing an app, it might not be possible, but there might be a way for ROM developers to have such functionality.
Can't you change the icons you see in the toggle menu? One icon is for the mobile data settings, another one to enable it.
In MIUI JB it works fine (by default). Very stable and fast ROM by the way, much better than the ICS ROMS I've tried.
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
Brand Newbian here,
FYI - I've taken consideration, and this seemed to be the best place to post. My apologies if not.
About a week ago I successfully rooted & unlocked my stock Zv9. I had zero knowledge, or vocabulary, to support the leap. I've learned enough to confirm that my initial choice in purchasing the OG was key, and that the Devs here are lighting the candle at both ends to potentiate this device. Brilliant work so far, guys.
I'm hopelessly lurking in XDA threads, looking for "The One", or most efficient build. I've seen many updates on official ZvB(a?) OTAs (I have not received it yet) and other mostly successful JB variants, but to be honest the newer versions seem to either be hit or miss on the OG, or require some hint of development insight.
Ok, so here's my question. I am still struggling with whether to flash a custom ROM, or wait for the official JB release, and figuring out if it even matters to wait. I don't really know if I can even receive Sprint upgrade notices, and if/when I do receive them, do I need to unroot for it update properly? What is the exact process for this scenario? I found similar posts in other threads, but nothing I really understood. For now, I need something simple with little to no workarounds.
Also, the main reason I rooted was for enhanced performance and Internet Sharing. I have the newest versions of CwM/ROM Manager, TWRP, GooManager, ES File Explorer, Titanium Backup, Wifi Tether, and I used FreeGee. But, I don't know which files do what, really. I've read through relevant guides, recent posts, etc.
Wifi Tether doesn't work either, even after switching to generic ICS, setting to wlan/0, etc. I was able to look into LG's hidden menus to manipulate the less risky network/usb/wifi settings, but no luck. I need to share my Internet.
Senior Members/Devs, hold my hand? Lol.
I'm loving this new hobby, and wish to be able to contribute eventually.
Wowww, sorry for the ridiculously long read! I'm a little OCD in caution and understanding.
Thank you in advance for your time and assistance!
Sent from my LG-LS970
well im no dev or senior member but with the little knowledge i have with flashing roms, it really is pretty easy. twrp is very simple to use as long as u can follow directions. dont get me wrong, u can mess up your phone using it or completely wipe things but if you go slow and follow the guides, its simple. it sounds like you have done some homework and the devs will appreciate that. choosing a rom is up to you. go with stok if u dont mind all the sprint and LG junk (aka bloat). if you want performance enhancements and most of the bloat removed, then lifeless rom would be an option. although v13 is supposed to be coming so i would wait for that. if u want all the bloat removed, imperium is a near future choice. anyways, its up to the user. there will be alot more choices once the aosp and cm10 roms start rolling out. so keep reading so youre prepared and confident for when that time comes.
Thanks Bowhunt, that's kind of what I was thinking - to wait.
Would I be fine grabbing other simple random mods in the meantime, or would it make upgrading more complicated when the time comes? Something to deflate the bloat, and enable Wifi or USB Tethering, etc.
Ha. Old lady hates that I F with my phone so much now. Probably because iPhones are no fun!
Sent from my LG-LS970
Welcome to XDA and congrats on getting an LG Optimus G.
To answer your question(s), You would need to re-lock your bootloader and can keep root and do the ZVB update. Or You can just flash the ZVB Radios then flash either Lifeless ROM (Gets rid of some bloat with a lot of mods/perks) or just get the stock rooted ZVB ROM. If you have anymore questions about the process or anything, just let me know.
Illionaire said:
Wifi Tether doesn't work either, even after switching to generic ICS, setting to wlan/0, etc. I was able to look into LG's hidden menus to manipulate the less risky network/usb/wifi settings, but no luck. I need to share my Internet.
Click to expand...
Click to collapse
I got wifi tether to work with the Wifi Tether app with Treve mod. Its the 11-22 kind (will post link when I find it again)
-Just change device profile to generic ics/jb (wlan0)
-And tick Force wifi driver reload 2.
-Mms clamping and routing fix are also ticked by default and I enabled access control.
Now it's working fine for me. Didn't search to see if it's anywhere else but there you go. Should work with regular wifi tether if the settings exist I imagine though
Edit: found it http://forum.xda-developers.com/showthread.php?t=1988735
Sent from my LG-LS970 using xda premium
Sounds good, I was looking at the thread earlier on flashing the ZVB radios and Lifeless ROM, but there were different processes left and right. Someone asked for a solid layout to confirm a most successful process, which to flash first, etc. I haven't checked back recently so I'm not sure if it's been posted yet.
Do you know what some of the apps or mods are that come with Lifeless? Any particular "things to know"?
I'll check that Lifeless JB ROM and come back here or PM you with questions on that if needed.
Thanks again,
Sent from my LG-LS970
I haven't flashed any custom roms as of yet because I like the stock rom surprisingly. Only thing I have done is rooted and used free gee to unlock and flash and update TWRP. I made a backup of ZV9 with data and all. Afterwards I flashed jokers stockish v2.11 and then when ZVB came out I flashed the radio. After that I wiped everything and flashed ZVB and restored data via TWRP and went well. Then I flashed the stock optimized kernel by joker and phone is working fine. I haven't tested wifi yet but I suspect it's broken.
As far as things to know, from experience, always make a backup and also backup the lowest levels of your phone as well and save it to another location like cloud storage or a computer hard drive or somewhere. Generally you can't brick your phone unless you really try or you mess with partitions and other low level things. Lol but yeah feel free to pm me or anyone you think might know something and we'll be glad to help.
Sent from my LG-LS970 using xda premium
hoslayer13 said:
I got wifi tether to work with the Wifi Tether app with Treve mod. Its the 11-22 kind (will post link when I find it again)
-Just change device profile to generic ics/jb (wlan0)
-And tick Force wifi driver reload 2.
-Mms clamping and routing fix are also ticked by default and I enabled access control.
Now it's working fine for me. Didn't search to see if it's anywhere else but there you go. Should work with regular wifi tether if the settings exist I imagine though
Edit: found it http://forum.xda-developers.com/showthread.php?t=1988735
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Right on, I have "Wifi Tether For Root" same thing right?
I'll try that before I flash anything and see what happens.
Sent from my LG-LS970