Related
Hi guys
As you all know there are tons of different varients for note 4. Now lets talk about snapdragon version for example.
There is n910s-f-g which are all have snapdragon soc. And as far as i know the only difference is modems-lte bands. So do you think that n910f rom will work on n910s? Also I doubt about the modem will work... Ok guys I'm wating for yourcommands. Thank you.
The S is exynos
And no, roms only work with their specific model numbers. Except for the H models which seem to work with C roms.
All these questions have been answered many times.
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
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.
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.
Hello. I am thinking about going towards this device to buy. I noticed on the Moto G5 Plus page that alot of users are having VOLTE, 4G and IMEI problems when they are flashing roms.
Is this commonly a problem with the Moto G5s Plus? because having VOLTE and 4G are very important factors for me. Also, is it just for Custom Oreo roms that this is happening to, or all roms in general? Thanks!
royredman said:
Hello. I am thinking about going towards this device to buy. I noticed on the Moto G5 Plus page that alot of users are having VOLTE, 4G and IMEI problems when they are flashing roms.
Is this commonly a problem with the Moto G5s Plus? because having VOLTE and 4G are very important factors for me. Also, is it just for Custom Oreo roms that this is happening to, or all roms in general? Thanks!
Click to expand...
Click to collapse
Some do and some don't