CM13 wifi calling on T-Mobile? - ONE Q&A, Help & Troubleshooting

Anybody here any idea if or when will wifi calling be implemented on the CM13 builts?
Thanks.

kusgan said:
Anybody here any idea if or when will wifi calling be implemented on the CM13 builts?
Thanks.
Click to expand...
Click to collapse
It was supposed to be. CM came out before the 13 release and said they figured out how to add it in and will be putting it in, but it isn't in the rom yet. I'm waiting for it too.

Don't hold your breathe on it. Unless they made some miraculous deal with T-mo to get their proprietary code for wifi calling, it aint gonna happen. If CM and/or OnePlus said that they are gonna implement this, they are full of crap.

kenboyles72 said:
Don't hold your breathe on it. Unless they made some miraculous deal with T-mo to get their proprietary code for wifi calling, it aint gonna happen. If CM and/or OnePlus said that they are gonna implement this, they are full of crap.
Click to expand...
Click to collapse
CM did say they were going to add it and also wifi calling is native in android 6.0. Here's the article where they said it too http://www.androidpolice.com/2015/1...-include-support-for-t-mobiles-wi-fi-calling/

Wow, looks like it is so. Guess T-mo finally wised up and released their source. Like the article stated, more and more are going to no contract services and bringing their own phone. Just makes a better business sense allowing custom roms to have this running on their network.

This seems hopeless huh?

I thought it was working on the nexus series, not sure why it wouldn't work with us
Sent from my A0001 using Tapatalk

Related

[Q] Where will updates come from?

Will the phone get updates from Google or T-mobile?
I'm guessing neither. LG has a desktop app that they push updates through. Unless something's different with the G2X I'd assume they'll come through the LG app.
You could also get them from www.cyanogenmod.com!
jimbo831 said:
You could also get them from www.cyanogenmod.com!
Click to expand...
Click to collapse
Quoted for truth.
Hmm. So we could possibly be waiting for LG to do this? That is a potential deal-breaker for me. With pure Google experience and updates we are much more future proof.
borchgrevink said:
Hmm. So we could possibly be waiting for LG to do this? That is a potential deal-breaker for me. With pure Google experience and updates we are much more future proof.
Click to expand...
Click to collapse
You're looking at getting a Nexus S or Nexus One then. For those of us not willing to pay full price, and wanting better hardware, we have to deal with manufacturers instead.
MWBehr said:
You're looking at getting a Nexus S or Nexus One then. For those of us not willing to pay full price, and wanting better hardware, we have to deal with manufacturers instead.
Click to expand...
Click to collapse
I know, but this has more appealing hardware. I just don't get it if it really is LG pushing updates... Why not just let Google handle everything?
Yeah but the update has to go through tmo first before the release it, the have to make sure their crapware is in there.
Sent from my LG-P999 using XDA App
borchgrevink said:
I know, but this has more appealing hardware. I just don't get it if it really is LG pushing updates... Why not just let Google handle everything?
Click to expand...
Click to collapse
What I'm saying is no phone out there but the Nexus S or Nexus One has AOSP Android. Every other phone has a version modified by the manufacturer. Google has nothing to do with these changes. The only one who can release updates is the manufacturer (or service provider if the manufacturer chooses to send the update to them first).
That's just the way it is.
Are you opposed to rooting your phone and installing custom ROMs? If you are interested in that, CM will be your best bet by far as you get the best of both worlds (CM had Gingerbread on even the Nexus One before Google did!).
If you don't want to use unofficial software, you should stick with the Nexus line. Even pure vanilla Android devices get updates through the carriers, that is how it is and how it always will be. Nexus phones are different as they are not sold through the carriers, just designed to work on them. They are managed entirely through Google which means updates come from Google.
MWBehr said:
What I'm saying is no phone out there but the Nexus S or Nexus One has AOSP Android. Every other phone has a version modified by the manufacturer. Google has nothing to do with these changes. The only one who can release updates is the manufacturer (or service provider if the manufacturer chooses to send the update to them first).
That's just the way it is.
Click to expand...
Click to collapse
I was under the impression that the vanilla devices (like the G2x obviously) was AOSP. Do you know what is modified on this version by LG? I know there is preinstalled software, but that is different than changes to AOSP.
borchgrevink said:
Hmm. So we could possibly be waiting for LG to do this? That is a potential deal-breaker for me. With pure Google experience and updates we are much more future proof.
Click to expand...
Click to collapse
LG's committed to before Summer. The O2X forum has them giving June as a time frame.
BarryH_GEG said:
LG's committed to before Summer. The O2X forum has them giving June as a time frame.
Click to expand...
Click to collapse
Just because they have the update for the O2x by June, doesn't mean the G2x will be ready. The two use different software, plus there are different expectations I think between the US market and European. I hope they come together, but I wouldn't be surprised if LG does the O2x first and then gets working on the G2x.
Bob from Wirefly.com said that he talked to someone from T-Mobile when he got the G2X for review and they said the 2.3 update was coming in one month. I'm not holding my breath, though.
Sent from my LG-P999 using XDA Premium App
scmurphy13 said:
Bob from Wirefly.com said that he talked to someone from T-Mobile when he got the G2X for review and they said the 2.3 update was coming in one month. I'm not holding my breath, though.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
LOL. "Bob from Wirefly" has the inside scoop, huh.
Don't ever believe anything somebody tells you when they're trying to sell you something. That's all I'm saying.
jimbo831 said:
I was under the impression that the vanilla devices (like the G2x obviously) was AOSP. Do you know what is modified on this version by LG? I know there is preinstalled software, but that is different than changes to AOSP.
Click to expand...
Click to collapse
It's not AOSP vanilla, but it's the closest you will get to it without buying a Nexus phone. There's lots of little tinkering to the OS on the LG2x. For example there's a "DTS" button in the music player to enable dts sound. Also, there's the T-Mobile motto when you drag down the status bar. There's a "tethering may incur charges" warning when you turn on wifi hotspot. There are different notification and ringtones put in. Etc etc. If you put this phone next to a Nexus phone, you will see lots of little differences beyond just the T-Mobile bloatware installed.
mapin0518 said:
It's not AOSP vanilla, but it's the closest you will get to it without buying a Nexus phone. There's lots of little tinkering to the OS on the LG2x. For example there's a "DTS" button in the music player to enable dts sound. Also, there's the T-Mobile motto when you drag down the status bar. There's a "tethering may incur charges" warning when you turn on wifi hotspot. There are different notification and ringtones put in. Etc etc. If you put this phone next to a Nexus phone, you will see lots of little differences beyond just the T-Mobile bloatware installed.
Click to expand...
Click to collapse
Interesting. Mine will be delivered tomorrow so I guess I'll see soon. I've had a Nexus One since release, so I'm sure whatever is different, I will notice. Thanks for the clarification.
Not sure where, but I read from one of the CM guys (I think, don't kill me) that it's not AOSP at all! It's actually that same O2X ROM themed to look like AOSP Froyo

Verizon officially announces buggy thunderbolt OTA

Can't say I'm surprised: http://support.vzw.com/system_update/thunderbolt.html
No voicemail notifications and FFC issues. Wonderful. How did this pass VZW testing again?
Nothing against you but people have een crying about other devices getting GB first and how we are getting screwed and blah blah and now GB is finally just around the corner and people are going to complain again. Can't be pleased it seems. Just root and run a custom ROM that runs better than stock and it's smooth(er) sailing!
I am running a custom rom. My point is that it's been how long since we were promised GB? 4 months? Weren't we supposed to get it in June? You'd think they would at least be able to iron out the bugs with this long of a delay. It's the end of September and they can't fix voicemail notifications which have plagued every leaked build for months? That's a huge bug (especially since voicemail is a Verizon feature) and it hasn't been fixed yet. Come onnnnn.
arh2o said:
I am running a custom rom. My point is that it's been how long since we were promised GB? 4 months? Weren't we supposed to get it in June? You'd think they would at least be able to iron out the bugs with this long of a delay. It's the end of September and they can't fix voicemail notifications which have plagued every leaked build for months? That's a huge bug (especially since voicemail is a Verizon feature) and it hasn't been fixed yet. Come onnnnn.
Click to expand...
Click to collapse
I see your point but I guess it all boils down to is GB worth not being notified of a VM especially with the other alternatives that are out there. With that said I do agree they should of made VM notifications work but I guess that means they will put out another update to fix that and other issues soon (hopefully).
Mustang302LX said:
I see your point but I guess it all boils down to is GB worth not being notified of a VM especially with the other alternatives that are out there.
Click to expand...
Click to collapse
I think what it really boils down to is the fact that VZW is releasing this buggy version as an OTA update, which will be rolled out to lots and lots of people who have never heard of ROMs or rooting or anything, and they will be stuck without voicemail notifications or a properly working front camera until VZW (I'm guessing) releases *another* OTA update later on to fix those problems. That's pretty bad customer service. I think they're just releasing it so they can (finally) actually stick to a release date, even if the release is buggy.
People who run custom ROMs won't have to worry about it too much but we are a small minority of all the people who have Thunderbolts.
Jacquestrapp said:
I think what it really boils down to is the fact that VZW is releasing this buggy version as an OTA update, which will be rolled out to lots and lots of people who have never heard of ROMs or rooting or anything, and they will be stuck without voicemail notifications or a properly working front camera until VZW (I'm guessing) releases *another* OTA update later on to fix those problems. That's pretty bad customer service. I think they're just releasing it so they can (finally) actually stick to a release date, even if the release is buggy.
People who run custom ROMs won't have to worry about it too much but we are a small minority of all the people who have Thunderbolts.
Click to expand...
Click to collapse
This is true but nothing anyone can do about it. VzW will have to deal with all the customer service calls they get for lack of VM notifications then and that sucks for them.
Jacquestrapp said:
People who run custom ROMs won't have to worry about it too much but we are a small minority of all the people who have Thunderbolts.
Click to expand...
Click to collapse
Actually, people who run custom roms WILL have to worry about it. Custom roms do not fix this problem. Using this phone for business it will be a HUGE problem...a liability problem.
I doubt they VM problem will be in this build thats pushing out whenever.
*Madmoose* said:
Actually, people who run custom roms WILL have to worry about it. Custom roms do not fix this problem. Using this phone for business it will be a HUGE problem...a liability problem.
Click to expand...
Click to collapse
You have usable, valid alternatives so it's not a make-or-break deal.
---------- Post added at 12:05 PM ---------- Previous post was at 12:03 PM ----------
Mustang302LX said:
This is true but nothing anyone can do about it. VzW will have to deal with all the customer service calls they get for lack of VM notifications then and that sucks for them.
Click to expand...
Click to collapse
Those who don't use Google Voice or YouMail and so on should call and call and call to get VZW and HTC motivated enough to fix it quickly. Maybe that will motivate them enough.... On the other hand, I have to think fixing VM notifications, for whatever reason, must be extremely difficult. I really don't see either company releasing an update without seriously trying to have fixed this.
People who use the Thunderbolt but do not know about leaked RUUs will not know about the VM bug. They will see their phone prompt them to update and click accept just to get rid of it. If they're in the subway, underground, or a place with no reception and someone leaves them a VM, they will have no idea it's broken until their find out the good old hard way. As you said, VZW will have their hands full with custom complaints in a few days after the OTA hits.
hallstevenson said:
You have usable, valid alternatives so it's not a make-or-break deal.
Click to expand...
Click to collapse
We were speaking specifically about custom roms, not 3rd party software. Everyone has access to those alternatives, whether its a custom rom or not.
Ahhh, yes, I overlooked that aspect of the issue. One won't KNOW they've rec'd a voicemail with this update.... I doubt people randomly check their voicemail to see if there's a new VM. People only do it when their phone tells them they have a VM waiting.
I really expected VZW to acknowledge this issue in their 'announcement' and to at least say "a minor s/w update will be released in the near future to resolve this".
Those are the details for the last ota update
MrCapcom said:
I doubt they VM problem will be in this build thats pushing out whenever.
Click to expand...
Click to collapse
The build number is the same as the leak from the other day, so it's there. Let's hope they do change the build before they push it.
Is there a way to not accept the ota? And just prevent it from downloading on its own? My wife's phone is stock and unrooted
Running Team Name SoaB .73, using XDA premium
So where's that new dock we were supposed to get with this OTA? I flashed it and nothing...
solarpolitiks said:
So where's that new dock we were supposed to get with this OTA? I flashed it and nothing...
Click to expand...
Click to collapse
No new dock here either. I'm hoping the actual ota is different from this leak.
hallstevenson said:
Ahhh, yes, I overlooked that aspect of the issue. One won't KNOW they've rec'd a voicemail with this update.... I doubt people randomly check their voicemail to see if there's a new VM. People only do it when their phone tells them they have a VM waiting.
I really expected VZW to acknowledge this issue in their 'announcement' and to at least say "a minor s/w update will be released in the near future to resolve this".
Click to expand...
Click to collapse
Use google voice. Problem solved!
Guys it's possible that voice mail and other things will work. The update according to them will be 147mb, much smaller than the full rom leak. As this is an "update" the camera and voice mail may work just fine.
Sent from my ADR6400L using Tapatalk
MrCapcom said:
I doubt they VM problem will be in this build thats pushing out whenever.
Click to expand...
Click to collapse
Wanna make a friendly wager?
5 bucks?
Send me your paypal.
I'll drop 5 that they do not have it fixed.

USA ICS release - T-Mobile/HTC update

Full article from Android and Me
HTC has delivered a ROM to us however it is still having issues the reason that other sensation types have the update without issue and ours did not come out that way is because every ROM must be adapted to the hardware of the device because we use a different radio than other providers and also have applications such as wifi calling it also has to be compatible with those. What the HTC rep told you is most likely correct because once a ROM is delivered we have 2 weeks to test it and then approve it or send it back they then have 4 weeks to fix the bugs and return it back to us, where we are exactly in that process I do not know but that is how a ROM is delivered to the customer.
The original ROM was not delivered to us in November, we started testing it just recently but I think it has been longer than 2 weeks so at this point HTC most likely has the ball.
You bought a phone and it has been announced that you are getting ICS you have every right to know what’s going on with it and when you can see these awesome features. I did go into a lot of detail about how a ROM gets to the end user (you guys) but that wasn’t to point fingers only so you would have a better understanding of why you don’t have it yet, the bottom line is the Sensation has T-Mobile’s and HTC’s name all over it and both companies want to make you proud to be a Sensation owner so we are working as fast as we can to deliver it but also want to make sure that it stands up to your expectations.
Click to expand...
Click to collapse
A fairly meaty update that helps explain the process, the holdup and a possible time frame for when we might see the release.
So T-Mobile can't get their WiFi Calling and other bloatware to work, but our custom ROM chefs don't seem to have a problem?
Thank God for our chefs!!!
Zylograth said:
So T-Mobile can't get their WiFi Calling and other bloatware to work, but our custom ROM chefs don't seem to have a problem?
Thank God for our chefs!!!
Click to expand...
Click to collapse
+1!
Sent From My HTC Sensation 4G
Zylograth said:
So T-Mobile can't get their WiFi Calling and other bloatware to work, but our custom ROM chefs don't seem to have a problem?
Thank God for our chefs!!!
Click to expand...
Click to collapse
It seems that HTC can't get the Wifi calling to work within spec. It didn't work the first time and TMO told HTC that they needed to work on it some more. It's going back and forth between TMO and HTC.
And no offense to our devs here, but lets be realistic. Our roms here aren't without their issues. Ie. wifi calling still crashing, mms not working, proximity sensor issues, wifi issues, bt issues, etc. but the positive is that the roms here get better than their respective base.
totalundone said:
And no offense to our devs here, but lets be realistic. Our roms here aren't without their issues. Ie. wifi calling still crashing, mms not working, proximity sensor issues, wifi issues, bt issues, etc. but the positive is that the roms here get better than their respective base.
Click to expand...
Click to collapse
Now I don't think that's fair our devs don't have the resources tmob has and we are ahead of them with 4.0 almost working and got 60 3.6 roms out there if one dev had what HTC had or tmobl we be in next stage ics 4.0 is far from last Rom this phone will do
I do think HTC watches this as do all phones and leak so they have free help
Sent from my HTC Sensation 4G using xda premium
craven667 said:
Now I don't think that's fair our devs don't have the resources tmob has and we are ahead of them with 4.0 almost working and got 60 3.6 roms out there if one dev had what HTC had or tmobl we be in next stage ics 4.0 is far from last Rom this phone will do
I do think HTC watches this as do all phones and leak so they have free help
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
I don't think it's fair that the devs don't have access to the same resources that tmo and htc have either. If they did we would probably also have perfect 'native' ports of Samsung's, Sony's, and Moto's UIs, lol. it is what it is. the devs have improved on what's been released (although, I would like to see a rom that emphasizes stability instead of tweaks - Maybe I'll take a crack at it if I can find enough time, we'll see).
As far as free help is concerned... I don't know how much work they actually take off XDA (although, i'm sure it's happened, i feel like it's little). The X10 (in which I had a little previous experience) had a number of things fixed that's never (and never will be) fixed in any official rom.
but the original point was to contradict this statement: "our custom ROM chefs don't seem to have a problem" and "So T-Mobile can't get their WiFi Calling and ...". There are issues and it's not just TMO but HTC can't fix wifi calling in a timely manner. Just trying to dispel inaccuracies (IMHO).
I would rather have a clean ROM straight from HTC without T-Mobile adding junk to it anyway, including WiFi calling...
Well what it is that tmobl locked the phone up so it can't use att making HTC redo there **** its out everywhere but here in us
Looks like a corp had a hand trying to block the progress of something with hardware changes and bloatware I would love a Rom from HRC or google with out tmob trash but I am not on tmob now so I have no bloat lol
Sent from my HTC Sensation 4G using xda premium
totalundone said:
And no offense to our devs here, but lets be realistic. Our roms here aren't without their issues. Ie. wifi calling still crashing, mms not working, proximity sensor issues, wifi issues, bt issues, etc. but the positive is that the roms here get better than their respective base.
Click to expand...
Click to collapse
Speak for yourself, my friend.
I'm using bluetooth, video recording, wifi, wifi calling, all cell radio features, proximity working find, light sensor as well.
I don't mms. I gmail.
So. The devs and chefs are doing a FANTASTIC job, especially with these kernels.
Just like i tell everyone in every single rom forum for the sensation. T-Mobile's Wifi calling is just useless bloatware that is a program easy as hell for, supposed amazing techs of their caliber to make and now we have to wait for official Ics due to an app that don't work stock or rooted. Everytime i use wifi calling, and yes on stock, all i get is" HUH,WHAT DID YOU SAY, I CANT HEAR YOU",. And thats why it also rarely works in roms. It's not HTC's fault T-Mobile has a shi%$ program that is useless out the box. Wouldn't be useless if it ever worked. And now we have to wait for Ics because of it.
Zylograth said:
I would rather have a clean ROM straight from HTC without T-Mobile adding junk to it anyway, including WiFi calling...
Click to expand...
Click to collapse
Yep, this would be the best scenario!
xHighAlert said:
Speak for yourself, my friend.
I'm using bluetooth, video recording, wifi, wifi calling, all cell radio features, proximity working find, light sensor as well.
I don't mms. I gmail.
So. The devs and chefs are doing a FANTASTIC job, especially with these kernels.
Click to expand...
Click to collapse
Ditto. I've been on ARHD for three weeks and I have not looked back. I haven't found anything that doesn't work.
Sent from my HTC Sensation 4G using xda premium
tony53220 said:
Just like i tell everyone in every single rom forum for the sensation. T-Mobile's Wifi calling is just useless bloatware that is a program easy as hell for, supposed amazing techs of their caliber to make and now we have to wait for official Ics due to an app that don't work stock or rooted. Everytime i use wifi calling, and yes on stock, all i get is" HUH,WHAT DID YOU SAY, I CANT HEAR YOU",. And thats why it also rarely works in roms. It's not HTC's fault T-Mobile has a shi%$ program that is useless out the box. Wouldn't be useless if it ever worked. And now we have to wait for Ics because of it.
Click to expand...
Click to collapse
Wifi calling is a great feature. I never have problems with voice quality. Maybe your interner sucks.
Sent from my SX-SP715A using XDA
masondoctorjt said:
Wifi calling is a great feature. I never have problems with voice quality. Maybe your interner sucks.
Sent from my SX-SP715A using XDA
Click to expand...
Click to collapse
I agree Wifi calling is not perfet but for me it is a must. I use it when I'm overseas and in basements where I can't get reception. My friends who have iphones are jealous because they have to go to the first floor to get reception and make calls.
We are not getting the official update until tmobile makes sales on the one-s ..it will probably be in May when we see the update..good thing I have a nexus with 4.0.4..**
Sent from my HTC Sensation 4G using XDA
bigmizz79 said:
We are not getting the official update until tmobile makes sales on the one-s ..it will probably be in May when we see the update..good thing I have a nexus with 4.0.4..**
Sent from my HTC Sensation 4G using XDA
Click to expand...
Click to collapse
your info is based on....?
sroach23 said:
your info is based on....?
Click to expand...
Click to collapse
History of tmobile updating process
11hani11 said:
I agree Wifi calling is not perfet but for me it is a must. I use it when I'm overseas and in basements where I can't get reception. My friends who have iphones are jealous because they have to go to the first floor to get reception and make calls.
Click to expand...
Click to collapse
^ Likewise I depend on wifi calling. I'll pass on the other bloatware, but this isn't an optional app for me. I'm afraid that I've had no consistent luck with the ROMs available here.
I suspect that will change once T-Mobile has released their ICS update with a working configuration and (possibly) an updated app. In the meantime, I am content to wait.
It's based on my opinion.**
Sent from my HTC Sensation 4G using XDA
WiFi calling is not bloatware to people who use it. I use it everyday at home. There's no way I can make or receive call without it. I also use it every time I'm overseas. For me, WiFi calling is a must. That's why I don't dare play around different roms for fear of messing up the WiFi calling feature. I can also wait for the official update with a working WiFi calling.

worst fear, cdma (sprint) data issues already?

so stock is great but we all know we love our custom roms and have our favorite devs. i saw cataclysm rom pop up the other day and flashed, all working fine (data provisioned like it should, etc). this morning i noticed a good number of custom roms appeared for us. so i naturally wanted to give them a run (alpha or not), 3 different roms (omni, unofficial carbon, and asylum) all with the same result. it will sit on the provisioning data service screen until it times out and asks you to try again. now somebody in omni replied saying it was a known issue.
here is my concern/question i guess, are we going to see issues bc sprint didnt actually get out of the way and just give up binaries to google? my understanding was one rom should work on all variants. i am not foreign to data issues and sprint as i had the sprint gnex but this was me giving them one last chance before taking it to tmobile, which we can fortunately do with the n5.
Definitely frustrating today for sure. There's a lot of cool ROM's that we're not able to enjoy yet.
I've been sending some PM's around and I can assure you that there are people looking into it. I see the following scenarios as possibilities:
- We may need to create a flashable zip of the Sprint APN settings. It would need to be flashed after every ROM/Gapps install. AT&T and Straight Talk already have a thread for this.
- The devs (except for Rascarlo who already said he will not do this) may start to take notice and try to fix it when building their ROM's. It may be a HiddenMenu issue.
- Worst Case Scenario - we have a separate Sprint Development Forum. Because we have the same model number, I doubt it will come to this though.
mjs2011 said:
Definitely frustrating today for sure. There's a lot of cool ROM's that we're not able to enjoy yet.
I've been sending some PM's around and I can assure you that there are people looking into it. I see the following scenarios as possibilities:
- We may need to create a flashable zip of the Sprint APN settings. It would need to be flashed after every ROM/Gapps install. AT&T and Straight Talk already have a thread for this.
- The devs (except for Rascarlo who already said he will not do this) may start to take notice and try to fix it when building their ROM's. It may be a HiddenMenu issue.
- Worst Case Scenario - we have a separate Sprint Development Forum. Because we have the same model number, I doubt it will come to this though.
Click to expand...
Click to collapse
well this is really dissapointing then. this "one phone for all" seems to be a bill of goods. will probably just be switching to tmobile when i can and not having to deal with sprint being in the way. if it is this way already and there hasnt even been an update, i do not have high hopes for us cdma users.
edit: i am sure devs are working on this and will get it working in some way. just stinks and its weird that cataclysm is working just fine when it comes to data but 3 others didnt.
chasew83 said:
well this is really dissapointing then. this "one phone for all" seems to be a bill of goods. will probably just be switching to tmobile when i can and not having to deal with sprint being in the way. if it is this way already and there hasnt even been an update, i do not have high hopes for us cdma users.
edit: i am sure devs are working on this and will get it working in some way. just stinks and its weird that cataclysm is working just fine when it comes to data but 3 others didnt.
Click to expand...
Click to collapse
Looks like we have a fix already. More to come son.
Sent from my Nexus 5 using Tapatalk
mjs2011 said:
Looks like we have a fix already. More to come son.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What's the fix?
Sent from my Galaxy Nexus using Tapatalk
mjs2011 said:
Looks like we have a fix already. More to come son.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second jboyer, whats the fix? flashable zip?
Cordell was able to add something to the SlimROM he's been working on. In not going to post it without his permission, but what he did today should fix any future issues of compatibility.
Sent from my Nexus 5 using Tapatalk
mjs2011 said:
Cordell was able to add something to the SlimROM he's been working on. In not going to post it without his permission, but what he did today should fix any future issues of compatibility.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
nice...i remember slimkat having working data when i gave it a go the other day. i am happy to test the fix if you or he wants to pm me. i used to test for sourcery on sprint gnex so i am good at putting things through the paces and can run logcats if need be.
I also think someone is going make flashable zips that I'll be testing later as well. That way we'll have options for ROMs where the devs don't build the fix in their ROMs.
Sent from my Nexus 5 using Tapatalk
mjs2011 said:
Cordell was able to add something to the SlimROM he's been working on. In not going to post it without his permission, but what he did today should fix any future issues of compatibility.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What about a link to github
Sent from my Galaxy Nexus using Tapatalk
Honestly the devs need to post roms compatible with cdma or not post them in this forum. nexus firmware is the same for both variants and custom/aosp roms should follow the same rule.
patience, padawans. http://forum.xda-developers.com/showpost.php?p=47396073&postcount=192 answers you will find.

T-Mobile wifi calling

With the latest announcement is there any chance people on prepaid getting some love? I'm on the $30, 100 minute, be nice to get wifi calling
From what I've read Wi-Fi calling is something that has to be built into the OS, framework, etc. It's also closed source, so it's pretty tricky to reverse engineer. Who knows though, it's not impossible!
I don't think they'd put it in the oneplus one. The new uncarrier features leans users to stick with t mobile branded phones. Phones that have monthly payments to t mobile. Even the nexus isn't supported
Sent from my A0001 using Tapatalk
SteveG12543 said:
From what I've read Wi-Fi calling is something that has to be built into the OS, framework, etc. It's also closed source, so it's pretty tricky to reverse engineer. Who knows though, it's not impossible!
Click to expand...
Click to collapse
I thought as much. Hoping they would make the necessary api available to Cyanogen...pipe dream for now I guess
AntLyoN2053 said:
I thought as much. Hoping they would make the necessary api available to Cyanogen...pipe dream for now I guess
Click to expand...
Click to collapse
I'm hoping Voice over LTE gets enabled for the OPO.
edit: https://jira.cyanogenmod.org/browse/BACON-1197 upvote

Categories

Resources