Hi, I just got a Nexus 6. I want to move to an aosp based rom as soon as possible. I am on t-mobile and wifi calling is a must. My question is does P.A.C. rom support wifi calling and volte like cm 13 does?
If you can't find your answer in the Opening post features list, or by searching the thread on WiFi calling and volte, I suggest taking a nandroid backup and flashing it to find out. :good:
tjsooley said:
..... I am on t-mobile and wifi calling is a must. My question is does P.A.C. rom support wifi calling and volte like cm 13 does?
Click to expand...
Click to collapse
I am not using wifi calling because it is not available here in the Netherlands. .
T-MOBILE want's to earn money with the services they offer. It seems logical to me that this wifi service only works with T-Mobile branded devices.
When you flash an other rom you need to read about the new rom. In the description there must be stated that wifi calling is supported.
NLBeev said:
I am not using wifi calling because it is not available here in the Netherlands. .
T-MOBILE want's to earn money with the services they offer. It seems logical to me that this wifi service only works with T-Mobile branded devices.
When you flash an other rom you need to read about the new rom. In the description there must be stated that wifi calling is supported.
Click to expand...
Click to collapse
You are correct for all devices but the nexus 6. the stock international nexus 6 rom works with their wifi calling and cm 13 does too.
tjsooley said:
Hi, I just got a Nexus 6. I want to move to an aosp based rom as soon as possible. I am on t-mobile and wifi calling is a must. My question is does P.A.C. rom support wifi calling and volte like cm 13 does?
Click to expand...
Click to collapse
where/what is the "P.A.C." rom?
wase4711 said:
where/what is the "P.A.C." rom?
Click to expand...
Click to collapse
They actually released Lollipop builds but have been largely inactive since then. There are some releases (I believe unofficially) that are floating around on androidfilehost and some other places... But they are in their infancy of Marshmallow. It's based on CM13 with (last time I checked a few weeks ago) not too many features added on top and probably largely considered to be experimental or in the alpha stage of development.
For sure Pure Nexus Project and Dirty Unicorns support wifi calling and I think Chroma and AOSiP do too. Any ROM based on AOSP should really support it but ROMs based on CM13 may or may not. I've seen conflicting information. From a reddit thread, a user said WiFi calling works on CM13 for the Nexus 5X but not his Nexus 5. Nexus 6 I am unsure, but make a nandroid backup of your current setup and go wild on testing different ROMs :good: I can't tell you because I don't have Tmobile anymore (although I did for a short period with my N6)
Dopamin3 said:
They actually released Lollipop builds but have been largely inactive since then. There are some releases (I believe unofficially) that are floating around on androidfilehost and some other places... But they are in their infancy of Marshmallow. It's based on CM13 with (last time I checked a few weeks ago) not too many features added on top and probably largely considered to be experimental or in the alpha stage of development.
For sure Pure Nexus Project and Dirty Unicorns support wifi calling and I think Chroma and AOSiP do too. Any ROM based on AOSP should really support it but ROMs based on CM13 may or may not. I've seen conflicting information. From a reddit thread, a user said WiFi calling works on CM13 for the Nexus 5X but not his Nexus 5. Nexus 6 I am unsure, but make a nandroid backup of your current setup and go wild on testing different ROMs :good: I can't tell you because I don't have Tmobile anymore (although I did for a short period with my N6)
Click to expand...
Click to collapse
Ah, you mean the pacman rom...I used it alot on lollipop, but yeah, not to be seen anywhere since most of us switched to MM..
BTW, almost all the current roms in the N6 dev section have wifi calling now, both the AOSP based ones, and the CM13 based ones...
wase4711 said:
Ah, you mean the pacman rom...I used it alot on lollipop, but yeah, not to be seen anywhere since most of us switched to MM..
BTW, almost all the current roms in the N6 dev section have wifi calling now, both the AOSP based ones, and the CM13 based ones...
Click to expand...
Click to collapse
Oh, thanks for the info. I wasn't aware CM13 had native wifi calling support. I'm glad it's baked into Google AOSP now for Nexus devices. I remember using a Galaxy Note 3 and so bad I wanted to put an AOSP/CM based ROM on it when I had Tmobile but the support for Wifi calling was only available on stock bloatwiz/lagwiz/whatever you want to call the garbage stock firmware. And where I live had zero Tmobile signal. Had to get by with root and wanam xposed. But now I'm back to the glorious nexus master race (and another carrier, so I don't need wifi calling).
Thanks. My last device did not support PAC rom. I was not aware that they are not really active any longer and there is no marshmellow version.
Thanks for all the info.
tjsooley said:
You are correct for all devices but the nexus 6. the stock international nexus 6 rom works with their wifi calling and cm 13 does too.
Click to expand...
Click to collapse
What is P.A.C rom?
I got the impression that it is a custom ROM and not the international stock rom.
Its this rom..
http://forum.xda-developers.com/google-nexus-5/development/rom-pac-rom-mm-alpha-1-t3373817
I dont think there is one for Shamu.
Related
Any one know how Tmobile plans on implementing wifi calling for the nexus 6 been an stock android rom? you guys think all AOSP roms would be able to get wifi calling once this patch goes live?
traicer said:
Any one know how Tmobile plans on implementing wifi calling for the nexus 6 been an stock android rom? you guys think all AOSP roms would be able to get wifi calling once this patch goes live?
Click to expand...
Click to collapse
Honestly, I expect Google to implement it just like Apple does. Develop the feature directly into the device and firmware and then allow minor updates to work with other carriers such as US Cellular and Sprint. If they don't bake it into "AOSP" then I doubt third party AOSP built devices would support it.
altimax98 said:
Honestly, I expect Google to implement it just like Apple does. Develop the feature directly into the device and firmware and then allow minor updates to work with other carriers such as US Cellular and Sprint. If they don't bake it into "AOSP" then I doubt third party AOSP built devices would support it.
Click to expand...
Click to collapse
yes, i'm hoping its an android thing and not a T-Mobile thing.
Here is the reasoning behind my request.
I am on Tmob and have a N6. I was fine stock rooted on 5.0 then 5.0.1. Then I decided to try a few roms. One that said it was for ALL carriers, didn't allow me to get calls unless I was only in 3g.
T-mobile is the ONLY one using a 47m ROM. All others are at 47i, why is there a difference? The radios most likely. I am 95r and 98r doesn't work on TMobile very well.
Can we get a Thread for EACH Carrier? They aren't all the same, at least from my experience. Sprint, VZW are different and have problems. I hear VZW users need to use 98r for "best results"
Go ahead, blast away. Just waiting for the "senior ops" to go to town on this one!
I'm on vzw and every ROM I've tried is fine. Have you updated to the latest image from google. Or are you still on 5.0.1
navyvet420 said:
Here is the reasoning behind my request.
I am on Tmob and have a N6. I was fine stock rooted on 5.0 then 5.0.1. Then I decided to try a few roms. One that said it was for ALL carriers, didn't allow me to get calls unless I was only in 3g.
T-mobile is the ONLY one using a 47m ROM. All others are at 47i, why is there a difference? The radios most likely. I am 95r and 98r doesn't work on TMobile very well.
Can we get a Thread for EACH Carrier? They aren't all the same, at least from my experience. Sprint, VZW are different and have problems. I hear VZW users need to use 98r for "best results"
Go ahead, blast away. Just waiting for the "senior ops" to go to town on this one!
Click to expand...
Click to collapse
With many phones, Samsung in particular - there are massive hardware differences that require several separate forums to manage.
With the nexus 6, the hardware is identical on all of them.
There are 2 specific builds that are slightly different and as you mentioned, they are M and I.
What we think is (but unproven) that M is for T-Mobile USA and I is for Australia. We have no concrete proof of that. Nor am I sure what the differences are. If you're using stock-based ROMs, try to stick to M builds.
As for AOSP, I'm not sure anyone knows what the difference is for T-mo. Maybe one day we'll find out.
rootSU said:
With many phones, Samsung in particular - there are massive hardware differences that require several separate forums to manage.
With the nexus 6, the hardware is identical on all of them.
There are 2 specific builds that are slightly different and as you mentioned, they are M and I.
What we think is (but unproven) that M is for T-Mobile USA and I is for Australia. We have no concrete proof of that. Nor am I sure what the differences are. If you're using stock-based ROMs, try to stick to M builds.
As for AOSP, I'm not sure anyone knows what the difference is for T-mo. Maybe one day we'll find out.
Click to expand...
Click to collapse
Thank You for the Reply.. I would agree with the thinking about M. Like I stated a non-M build killed the incoming calls unless my phone was on 3g with Enhanced 4g unchecked.
I was just asking for a Carrier Specific Rom thread thats all.
toknitup420 said:
I'm on vzw and every ROM I've tried is fine. Have you updated to the latest image from google. Or are you still on 5.0.1
Click to expand...
Click to collapse
Im on a 5.1 with 95r and 47M is my Build (nocturnal rom) its a Tmobile N6.. All other roms killed incoming calls unless I was stock rooted. CleanRom 2.0 and 2.1 with either 98r or 95r had same results. I like @scrosler roms, but can't live without getting business calls.
navyvet420 said:
Thank You for the Reply.. I would agree with the thinking about M. Like I stated a non-M build killed the incoming calls unless my phone was on 3g with Enhanced 4g unchecked.
I was just asking for a Carrier Specific Rom thread thats all.
Click to expand...
Click to collapse
Yeah. I think its a good idea to have a thread that lists all t-mo compatible ROMs, but first we need to learn what the actual difference is. Perhaps its just a RIL or something. In which case, there may just be a flashable zip required.
I just think we need to know more at this stage.
@efrant, do you know the differences? @simms22?
the aosp roms were missing code that made the tmobile devices not receive calls on lte, that has been fixed and should be in all roms that have been recently updated. i use terminus, which includes the code, so tmobile users get calls on lte, and volte is working. besides that issue that has been fixed, all carriers will work on any aosp rom. theres no such thing as a carrier specific nexus rom.
simms22 said:
the aosp roms were missing code that made the tmobile devices not receive calls on lte, that has been fixed and should be in all roms that have been recently updated. i use terminus, which includes the code, so tmobile users get calls on lte, and volte is working. besides that issue that has been fixed, all carriers will work on any aosp rom. theres no such thing as a carrier specific nexus rom.
Click to expand...
Click to collapse
Was the code added to aosp by Google? Or is it a community commit?
rootSU said:
Was the code added to aosp by Google? Or is it a community commit?
Click to expand...
Click to collapse
AOSP contains only Android OS nothing proprietary (proprietaries are included as a standalone) but when Google provided the binaries--proprietary libraries, applications were missing which caused VoLTE not to work properly. Myself and Sykopompos worked on the blobs and having VoLTE working, they were pulled from the factory image / deodexed OTA.
zephiK said:
AOSP contains only Android OS nothing proprietary (proprietaries are included as a standalone) but when Google provided the binaries--proprietary libraries, applications were missing which caused VoLTE not to work properly. Myself and Sykopompos worked on the blobs and having VoLTE working, they were pulled from the factory image / deodexed OTA.
Click to expand...
Click to collapse
this
Answers to this question are either totally unanswered or vague.
Can/will the M7 support VoLTE (Voice over LTE) or not? Three in the UK is upgrading it's network to support VoLTE in the 800mhz frequency range. It would be nice to have it if at all possible. Sadly there is very little info on whether the hardware supports it and if the software (Lolipop and mods) will support it or not on the M7.
Can we have a thread with solid answers as this is quite important for some of us who have reception issues.
deadman3000 said:
Answers to this question are either totally unanswered or vague.
Can/will the M7 support VoLTE (Voice over LTE) or not? Three in the UK is upgrading it's network to support VoLTE in the 800mhz frequency range. It would be nice to have it if at all possible. Sadly there is very little info on whether the hardware supports it and if the software (Lolipop and mods) will support it or not on the M7.
Can we have a thread with solid answers as this is quite important for some of us who have reception issues.
Click to expand...
Click to collapse
I've been searching and curious (without avail) about the same question. I'm currently using Viper/Venom ROM v9.0.0 that uses a base from the M9. The M9 supports VoLTE and thus the option appears in the menu on the M7. However it does not function and if you try to interact with it the phone service crashes. This makes sense since it was developed for M9 hardware. Does this mean it's totally not supported on the M7 from a hardware standpoint - nope. But without the proper software it's not going to happen. Is T-mobile (or whoever your carrier is) going to develop the feature? Probably not. Will google? Maybe, seems to be appearing on google phones as a standardized feature. Same for wifi calling...
sensati13 said:
I've been searching and curious (without avail) about the same question. I'm currently using Viper/Venom ROM v9.0.0 that uses a base from the M9. The M9 supports VoLTE and thus the option appears in the menu on the M7. However it does not function and if you try to interact with it the phone service crashes. This makes sense since it was developed for M9 hardware. Does this mean it's totally not supported on the M7 from a hardware standpoint - nope. But without the proper software it's not going to happen. Is T-mobile (or whoever your carrier is) going to develop the feature? Probably not. Will google? Maybe, seems to be appearing on google phones as a standardized feature. Same for WiFi calling...
Click to expand...
Click to collapse
With the AICP MM ROM for the m7, I called my mom and it said "VoLTE" in blue letters. I never really took notice of it until after I went back to Sense... I'm going to flash that ROM again and give you an update soon (if not I probably forgot, sorry). And btw I know this thread is very old but I just wanted to chime in and say what I've found
firedroidx said:
With the AICP MM ROM for the m7, I called my mom and it said "VoLTE" in blue letters. I never really took notice of it until after I went back to Sense... I'm going to flash that ROM again and give you an update soon (if not I probably forgot, sorry). And btw I know this thread is very old but I just wanted to chime in and say what I've found
Click to expand...
Click to collapse
So, that was an interesting and timely reply. I recently upgraded my M9 (s-on) to a firmware that is too new for MM CM so I went back to my M7 for a while. It's still on a sense based rom but I may give AICP MM a spin on my M7- thanks!
:edit
Now that I think about it, the only reason I upgraded to the M9 was for VoLTE, the M7 is the perfect size phone, god how ridiculous new phones are these days, every iteration just a liiiiitttle bit bigger. enough already lol /rant...
sensati13 said:
So, that was an interesting and timely reply. I recently upgraded my M9 (s-on) to a firmware that is too new for MM CM so I went back to my M7 for a while. It's still on a sense based rom but I may give AICP MM a spin on my M7- thanks!
:edit
Now that I think about it, the only reason I upgraded to the M9 was for VoLTE, the M7 is the perfect size phone, god how ridiculous new phones are these days, every iteration just a liiiiitttle bit bigger. enough already lol /rant...
Click to expand...
Click to collapse
I flashed AICP last night and called my mom again, but unfortunately no VoLTE... It's odd because I clearly remember seeing those blue letters when I was about to hang up :/ If I find anything new I'll post it here!
firedroidx said:
I flashed AICP last night and called my mom again, but unfortunately no VoLTE... It's odd because I clearly remember seeing those blue letters when I was about to hang up :/ If I find anything new I'll post it here!
Click to expand...
Click to collapse
Maybe, you didn't remember well, what you've seen? Because I think, it's impossible.
So this thread is a year old (time to re-activate it?), and I wonder about the same issue. I tried on the M7 with different firmwares (european latest hboot 1.61, GPE hboot 1.54), using LineageOS 14.1 (Android N 7.1.2), but with no constellation it's possible to activate VoLTE.
I figured out, that it depends on "the hardware", but IMHO that's not really the reason because the LTE radio chip performs LTE correctly. So I expect it depends in reality on the "radio firmware" to active VoLTE.
And I have never seen a radio firmware for the M7, which is able to perform VoLTE.
If somebody knows about a "patched" or "modified" radio firmware for the M7, to activate VoLTE, please let me know!!! (Because LOS 14.1 runs well, and is -- from the OS side -- able to perform VoLTE).
Thanks a lot,
samhhmobil
samhhmobil said:
Because LOS 14.1 runs well, and is -- from the OS side -- able to perform VoLTE)
Click to expand...
Click to collapse
Thats not true, Lineage in general doesnt support VoLTE. You can read about exacly this on AICP G+ page because a lot of people asked for VoLTE Support. Official answer was "as long as lineage doesnt implement it we dont have it" There are some unofficial Roms for other devices where the maintainer did implement VoLTE. The big problem with VoLTE is, in nearly every country and provider it has a different standard so its not just add something and it works for everyone.
But Guys, do you realy need LTE while your in a Call and 3G isnt enough? I think 42mb/s should be enough for everything and thats what you actually get while in a call. Btw our m7 only has an internal read and write speed at about 5-15mb/s so its useless :silly:
Anyone received OTA for Marshmallow on T-mobile?
If you received, when did you received it?
Negative on my end still waiting prob gonna root soon
Stll waiting but got it on my N5 on 10/8 (AT&T) and on my N9 on 10/14.
Been waiting for this myself. Checked T-Mobile's software update site and is still shows Android 6 as "In Testing" for the N6.
its not in testing, marshmallow has been released for the nexus 6. just go grab the factory image, and apply it yourself, manually.
Yes, their specific build, IS in testing.
Currently available build is stock Google build. "Should" work well enough as a daily driver. But I'm sure T-Mobile will make some tweaks for WiFi calling and band 12
Sent from my Nexus 6 using Tapatalk
carlz28 said:
Yes, their specific build, IS in testing.
Currently available build is stock Google build. "Should" work well enough as a daily driver. But I'm sure T-Mobile will make some tweaks for WiFi calling and band 12
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
the time around, there is a unified build, instead of many builds for different networks. the build is already out, its not in testing..
Guess we'll have to askdes , to confirm that.
Sent from my Nexus 6 using Tapatalk
simms22 said:
the time around, there is a unified build, instead of many builds for different networks. the build is already out, its not in testing..
Click to expand...
Click to collapse
Google has tested it. But T-Mobile is still doing acceptance testing. Click the Nexus 6 link on this interactive page at T-mobile.s site. At this moment, it shows the status to be "T-Mobile Testing," which is described as this: "During this stage, the device will go through T-Mobile certification process testing to make sure you get the best quality software possible."
Flashed manually. WiFi calling works just fine.
boomerbubba said:
Google has tested it. But T-Mobile is still doing acceptance testing. Click the Nexus 6 link on this interactive page at T-mobile.s site. At this moment, it shows the status to be "T-Mobile Testing," which is described as this: "During this stage, the device will go through T-Mobile certification process testing to make sure you get the best quality software possible."
Click to expand...
Click to collapse
well of course tmobile has to approve it before it goes out over its network. but its still officially out, and anyone can flash it manually
simms22 said:
well of course tmobile has to approve it before it goes out over its network. but its still officially out, and anyone can flash it manually
Click to expand...
Click to collapse
Yes. No one will stop you. But "can" does not necessarily equal "should." There are reports in this forum that there might be issues specific to T-Mobile when this build is flashed. Maybe that's why they call it "testing."
boomerbubba said:
Yes. No one will stop you. But "can" does not necessarily equal "should." There are reports in this forum that there might be issues specific to T-Mobile when this build is flashed. Maybe that's why they call it "testing."
Click to expand...
Click to collapse
i use tmobile. i am running marshmallow. i dont have any issues. and i don't read ANY issues here regarding any tmobile specific issues. if theres any specific issues that you are talking about, maybe you would care to enlighten me?
edit..
i just read what you linked, and im in that thread as well. thats an issue that you will see reported every single release. and its usually a very few that report it.
I used factory images. No problems on T-Mobile so far
Sent from my Nexus 6 using XDA Free mobile app
There have been questions about Mm6 on the Nexus6 and T-Mobile band12 support.
The Nexus6 was one of the two or three phones to support band12 on release. Since then, T-Mobile has built out and converted a lot of their towers to band12, and there have been rumors recently that they no longer want the N6 to be able to use band12.
I don't understand those rumors and press reports.
There are also disturbing reports from T-Mobile users who are on Mm6 that their Nexus6 no longer supports band12 without reverting to the last Lollipop radio.
So, I am holding off installing Mm6 OTA on my new Amazon-bought N6, even though it was offered when my Cricket/AIO prepaid SIM was in place as soon as I first booted.
Band12 is important, and will become more important, on T-Mobile.
Sent from my VS985 4G using Tapatalk
I know that custom ROMs aren't expected for quite some time, but historically speaking, do they have generally have Wi-Fi Calling support for T-Mobile? I would assume they don't.
My perfect custom ROM would be:
- Stock Android
- General S Pen support
- VoLTE + Wi-Fi Calling support
- Good cellular connectivity (some ROMs I used with other devices somewhat crippled cellular connectivity and performance)
besweeet said:
I know that custom ROMs aren't expected for quite some time, but historically speaking, do they have generally have Wi-Fi Calling support for T-Mobile? I would assume they don't.
My perfect custom ROM would be:
- Stock Android
- General S Pen support
- VoLTE + Wi-Fi Calling support
- Good cellular connectivity (some ROMs I used with other devices somewhat crippled cellular connectivity and performance)
Click to expand...
Click to collapse
WiFi calling and VoLTE requires carrier hooks that can usually only be found in ROMs based on stock. If your ROM developer is really, really good, he can create those hooks. My limited experience with ASOP ROMs suggests that they don't quite have that down yet.
You're not going to see ROMs other than stock-based until they can unlock the bootloader.
douger1957 said:
You're not going to see ROMs other than stock-based until they can unlock the bootloader.
Click to expand...
Click to collapse
Just to confirm, when you refer to "stock," you're referring to Samsung ROMs and not stock / AOSP Android, right?
besweeet said:
I know that custom ROMs aren't expected for quite some time, but historically speaking, do they have generally have Wi-Fi Calling support for T-Mobile? I would assume they don't.
My perfect custom ROM would be:
- Stock Android
- General S Pen support
- VoLTE + Wi-Fi Calling support
- Good cellular connectivity (some ROMs I used with other devices somewhat crippled cellular connectivity and performance)
Click to expand...
Click to collapse
So don't expect an AOSP (Stock Android) rom anytime soon (ever) if you are running a Tmo variant because of the locked bootloader. Even those on international variants with unlocked still have to deal with not having the full source for the exynos processor.
If you did have a AOSP rom it would recognize the pen but not specific Samsung apps related to it since those are tied to the touchwiz framework.
AOSP also would not work with VoLTE and Wi-Fi calling.
You would be limited to Samsung Tmo firmware or roms based off of it.
pcriz said:
You would be limited to Samsung Tmo firmware or roms based off of it.
Click to expand...
Click to collapse
I figured as much. With some minor tweaks via root, I think I can be plenty happy with Samsung's latest ROM.
besweeet said:
Just to confirm, when you refer to "stock," you're referring to Samsung ROMs and not stock / AOSP Android, right?
Click to expand...
Click to collapse
Yes.
I didn't think custom roms would be available with the locked bootloader but Jovy23 did it. This is the only one available so far but even though it is mainly stock, it is deodexed, knox removed and so on so it is a custom rom.
http://forum.xda-developers.com/tmobile-note-7/development/rom-n930tuvu1apgc-6-0-1-deodexed-knox-t3461513
The biggest thing is once Nougat hits, with the locked bootloader the end of custom files will end it sounds like from what I have read. If you want to stay custom with the Note 7, you won't be able to upgrade to Nougat. Unless the devs find a way around the secure boot.