Develop Bugs

VoLTE how do we turn on?

I see some people saying they already turned on their VoLTE, how does one go about doing this? I'm on the latest Kernel, running the latest PacMan ROM.
Sent from my SM-N900T using XDA Free mobile app

It's in call settings. Isn't pacman AOSP? it might be limited to TouchWiz roms.
Sent from my SM-N900T using Tapatalk

you need to return to stock in order to get the volte. when you try to restore via KIES it will ask you if you want to upgrade to the ne6 baseband. click on yes and be patient

So we can't use custom roms to get volte? We have to stick to stock rom?

visiovis said:
So we can't use custom roms to get volte? We have to stick to stock rom?
Click to expand...
Click to collapse
Correct

PhilPan said:
I see some people saying they already turned on their VoLTE, how does one go about doing this? I'm on the latest Kernel, running the latest PacMan ROM.
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
Volte will not and does not work at all if you are using Pacman rom
or any other AOSP, AOKP, CM or ported roms.
You will need to flash a Samsung N900T Kitkat 4.4.2 Touchwiz stock or
stock based custom rom if you want to get the Volte feature working.
Good luck.

yea i tried flashing all the different options/roms trying to figure it out. only the stock telco rom works for volte. thanks

XtreStoLite custom rom
visiovis said:
yea i tried flashing all the different options/roms trying to figure it out. only the stock telco rom works for volte. thanks
Click to expand...
Click to collapse
I have been searching for custom ROMs that can do VoLITE and i think I found one called XtreStoLite but I do not think it will work yet on your device. Someone told me something about wrong kernals, and until they make it install from a universal zip it is not workable yet.
But I would keep an eye out on that one and I think they are going to soon come up with more custom roms with volte.
:fingers-crossed:

***voLTE, WiFi calling, Tmobile***
=======================================
(linked from "David Ruddock, XDA" )
T-Mobile Unofficially Speaks To Us About Band 12 LTE / VoLTE And Unlocked Smartphones,
And Yep It's Still Confusing
-----------------------------------
Yesterday, we published an article asking an open question: what is up with T-Mobile band 12 support being removed from some unlocked smartphones?
Today, T-Mobile contacted us to speak about said article. Unfortunately, T-Mobile was unwilling to provide any official on-record responses to our questions. But after a short discussion, I can provide you some information I have learned on background (journalist speak for "cannot be directly quoted or attributed to anyone"). First:
On T-Mobile, any device on its network with band 12 LTE data support must also support T-Mobile Voice over LTE services and E911.
The E911 part isn't particularly important in terms of the certification requirement - all phones sold in America are technically E911 compliant, because by law they have to be. The problem is that E911 compliance is inextricably linked to T-Mobile's VoLTE requirement for band 12. Without VoLTE support, a device on band 12 service would be unable to make phone calls of any kind if no other T-Mobile band was available (it will not know to fall back to AT&T roaming - the call will just flat-out fail), and that would include making 911 calls, meaning the device would for legal purposes likely be out of E911 compliance, and T-Mobile could get in trouble with the FCC. Not to mention, you could have somebody trying and failing to dial 911 in an emergency, which would of course be terrible. And yes, by removing band 12 support, you can make E911 work, because the phone then has no signal at all and knows to try to roam onto another compatible network (AT&T usually) to complete the call. This is both a safety and liability issue, and it is easy to understand where T-Mobile would be coming from in terms of concern about this - they do have something of a history with E911 debacles. Clearly this is a very real safety concern, and I do sympathize with T-Mobile in the sense that they obviously can't just sit here and do nothing about it. But there are practical concerns for OEMs here - adding T-Mobile VoLTE isn't just as easy as flipping a switch.
In order to obtain VoLTE compliance for band 12, phones must go through T-Mobile's rigorous network certification process (and yes, unlocked phones can go through this certification).
Speaking off the record to one major smartphone vendor, we have learned that there are very real costs and complexities associated with obtaining that certification, and it must be done on a device-by-device basis. Many phone OEMs, then, may simply choose to remove band 12 support from their unlocked smartphones sold in America. This could mean phones like the Alcatel OneTouch Idol 3 (4.7 and 5.5), the Huawei Ascend P8 Lite, the Huawei SnapTo, OnePlus 2, Moto X Style (aka Moto X 2015 PE), Moto X Play, HTC One M9 Unlocked and Developer Edition, Saygus V2, and various imported phones (ie, some global unlocked Sony or Samsung devices) or unlocked branded AT&T phone models may lose band 12 support in future software updates. The fact is, we don't know what will happen, or to which phones, or when. Some manufacturers may choose to get T-Mobile VoLTE certification (Motorola has hinted as much with the new Moto X 2015 PE), but many may also simply choose to quietly disable band 12 for T-Mobile in software updates. Motorola, as we know, has already done this with the Moto E.
It is not clear what action, if any, T-Mobile will take if a smartphone vendor refuses to remove band 12 data support from their device and also refuses to undergo the T-Mobile VoLTE certification process. (Ie, they want to keep B12 data but not bother with B12 VoLTE certification.)
This is basically the kicker. What will T-Mobile do if a vendor says "no way" to dropping band 12 data, but also doesn't want to go through the VoLTE certification process? We don't know. They might not do anything. But they might do something. Again, this is why speaking to T-Mobile about this situation was so frustrating. Not only we were unable to directly quote or attribute any of the information we were provided, but there was also no clarity as to what would happen in the event the band 12 situation comes to a head with an OEM that refuses to "play ball."
It seems unlikely that any OEM would refuse T-Mobile's request here, though, as most of them are also partnered with the company on T-Mobile-branded devices.
We have asked T-Mobile again for an on-record statement about this entire situation, because it would help clarify it immensely. As things stand now, T-Mobile is attempting to put the ball in the court of manufacturers. Which, to be fair, manufacturers do have a role to play here - they have to make the decision to drop band 12 or go through the T-Mobile certs for these unlocked band 12 devices. Or, potentially, just ignore T-Mobile's band 12 requirements entirely and see what happens. Unfortunately, as you might guess, most smartphone OEMs have zero desire to discuss upcoming software updates in detail, or to ever put their product in a situation where it is being highlighted for losing a feature. That makes our job here a difficult one.
We will update you on any more information we receive about this situation, including any response from T-Mobile or potentially-affected device manufacturers we have reached out to.
---------------------------------------------------------

hey there, im using galaxy note 3 t-mobile running on AOKP rom android 7.1.2 with synergy kernel, the problem is when i switch my network to LTE from GSM, my device getting freezed and unresponsive after 3-4 minutes, this occured in Resurrection Remix and Linage OS, can anyone help me fixing this problem? and i dont want to go back to stock rom, thanks in advance

Questions about 5.0 on LG G3.

I recently bought a used LG G3, it should be arriving later today. I had a few questions regarding 5.0 Lollipop.
Looking through the threads here, it seems to be that some folks still haven't gotten the OTA in the US. Is this still the case, or is it widely released now?
Also, are there any issues with the 5.0 update on the T-mobile G3? Any reason to stick with KK over it?
Thanks!

The original release gave some of us issues with wifi calling being stuck on enabling and blue tooth being wonky so they halted the roll out but now they have approved an updated version and is starting to roll out or should start rolling out any time. The only issue my wife and I have with the original release was the wifi calling not enabling, we have no other problems. I have the white one and she has the black one so the issue affected both.

Not all Xposed modules work for lollipop just yet but lollipop seems pretty stable to me. Wifi calling is sketchy but I have perfect signal so it doesn't bother me. Battery life is better on lollipop for sure. Backup kitkat and try Lollipop and if you don't like it you can always go back

Thanks for the quick replies!
The phone arrived yesterday and I've been busy setting it up. I checked, and it came with 5.0.1 installed. Is there a way to know if that's the original release, or the second, fixed version of Lollipop?
Thanks again!

rubejb said:
Thanks for the quick replies!
The phone arrived yesterday and I've been busy setting it up. I checked, and it came with 5.0.1 installed. Is there a way to know if that's the original release, or the second, fixed version of Lollipop?
Thanks again!
Click to expand...
Click to collapse
The first version of lollipop was 20B, while the newest version is 20E. Go into settings, general, about phone, and then click on software info and look at the software version and it will tell you if it's 20B or 20E. It's most likely 20B since the 20E just started rolling out yesterday afternoon.

Ah, okay. Thanks!

Okay, time for some more dumb questions (sorry!) First, I'll start by saying I'm apparently still on the 20B version, and checking for updates says I'm still up to date. So if this would cause my network issues, I guess I"ll just wait it out...
I got my account activated last night and all seemed well. But now I'm in a location without wifi and I see I have no data connection. When I rebooted, it came up and said I was connected to AT&T, not T-mobile. Since I'm on the $30 plan with TM, I thought I wasn't allowed roaming, or perhaps it's no roaming for data? Anyway, it was a bit odd to see AT&T to come up...
So, I'm trying to make it only connect to Tmobile. If I go into "Tethering and Networks" and "Mobile networks" in the settings, I can change the "Network operators". After doing a search I see the following:
T-Mobile
RAT: LTE
T-Mobile
RAT:WCDMA
Followed by 3 AT&T options, the same as the TM ones and a GSM option.
Should I select one of the T-Mobile ones, or set it to auto?
I checked the T-mobile coverage map site and it shows my area has having 4G coverage, so I would think I'd get a better signal than I am. Although it's hard to tell if it's 4G or LTE, as the two shades of pink are so close together.
Are there other network related settings I should be checking or changing to get it to work better?
edit:
Okay, so I'm doing some semi-answering of my own questions here..
It looks like from what I'm reading that on the $30 prepaid plan, voice roaming is certainly allowed, but not data. So connecting to AT&T isn't a problem, I just can't use data on it.
And the reason I'm getting such poor reception on T-mobile is that their signal doesn't penetrate buildings very well, by nature of the band they use. I sort of wish I had learned this before switching from Virgin Mobile, but I'm still loving my new phone so much, I'm not too upset.
I was also able to use the LG update software on my computer to get to the 20E version, and the reception is still terrible, so that wasn't the problem.
Guess I'll just to do some connection tests outside of a building to see if I actually get a 4G connection, as per their coverage map, or if I'll have to call them up and find out whats going on.

P605V - Verizon Edition - A Few Questions

I swapped from the original 10.1, to the 2014 10.1 P605-V, Verizon stamped edition.
I have a few questions after spending a good bit of time reading up and looking for some clarification.
I started on 4.4.2 and with no SIM in, could not OTA. I'm not shocked. I downloaded the 5.1.1 USA Verizon ROM from sammobile, and was able to flash it with Odin, with no issues. <-- Not a question, just letting you know where I'm starting from to reduce confusion
I can't find any way to root the Verizon model. I tried using the regular 605 root in XDA forums, from chainfire, and Odin gives it a fail. I'm guessing there isn't a root for the 605V, at least on 5.1.1, based on the posts of others here. I also tried GeoHot's root, and the device removes it before it can even try to root. I gave full permissions, but it gets deleted during the install process anyways. Can anyone confirm that is the case?
It appears the bootloader is locked, and I'm fine with the fact that I might not be able to unlock it, but I just wanted confirmation.
I downloaded a paid unlock carrier option (not bootloader unlock), and it says that it's compatible with this model, however it comes back with saying I need to be rooted, which leaves me in the dark as to if you can swap to a carrier like StraightTalk. Verizon told me there's no need to unlock this tablet, and it can be swapped to StraightTalk without doing anything. StraightTalk confirmed this on the phone. I'm ok with staying on Verizon anyways, but was looking for confirmation that this is the case, and the Verizon branded tablet (fully paid for) is capable of using other US carriers that are using the CDMA Verizon network (the Verizon model appears to have a secondary modem that allows it to talk on the US bands, whereas the international 605 does not appear to have that option).
If I'm unable to root, and on a locked bootloader, is there a way for me to use google phone apps on the CDMA network? I see that Verizon has a service that allows you to do so, sort of, but it sounds like it works in a way similar to how google voice used to work. It also appears to require your phone to be on Verizon (my Note 3 is on ATT). Can I get the AOSP dialer running on a tablet, and use it as a phone/message device, with the phone number that comes with a 4G SIM card? Verizon seemed to think I could text no problem, but I didn't discuss rooting, sideloading, or anything of that nature, regarding calling on the actual network (ie not through wifi or cellular data)? I've read that the international version can make calls on the standard network, but I got the impression that people doing so are using cyanogen or aosp, etc, so based on the bootloader/root questions I posted above, I'm a little unsure if there's a way for me to use an aosp dialer on the tablet while it's running on samsung/verizon software. I'm concerned about trying to drop gapps for cyanogenmod on it, especially since I do not have a custom recovery. Any idea if I can run the "phone/dialer" app safely, or an alternative, where it would use the actual cellular network instead of purely being data based?
Can I revert back to a previous stock ROM (4.4.2) and obtain, and continue to keep, root, without serious risk?
I'm plenty happy with the tablet as-is, and very happy that it has a secondary modem for the US CDMA Verizon network, as well as international bands, but I'm a tweaker and would really like to do a bit of de-bloating and customization that it sounds like are tricky with this particular variation.
Thank you for your time in reading my long post.

Lineage phones that will work with AT&T 5G?

Dear Experts,
The cell phone I've been using
here in the USA is a Motorola G7 Plus,
with the Lineage 17.1 OS.
Yesterday, March 2, 2022, I couldn't
make a phone call. Immediately, the
call would end, and a message displayed:
"Call ended".
The folks at the ATT store in the mall
immediately suggested that I get a new phone.
My question was, why was I not warned about this?
It's been planned for a while now.
T-Mobile, Verizon, AT&T, and Sprint 2G/3G/4G LTE network shutdown dates: the sunset!
T-Mobile, Verizon, AT&T, and Sprint 2G/3G/4G LTE network shutdown dates: the sunset!
When are the carriers retiring their legacy 2G/3G/4G LTE networks? Here are the dates...
www.phonearena.com
However, ATT docs says that the G7 Plus will work.
Mysterious.
https://www.att.com/idpassets/images/support/wireless/Devices-Working-on-ATT-Network.pdf
After swapping my SIM card with various
phones, turns out the issue is the Lineage OS.
Results:
...
Motorola G7 Plus, Lineage 17.1
- call ended
Motorola G7 Plus, Lineage 18.1
- call ended
Samsung Galaxy A32, out of the box Android
- calls work
Motorola G7, out of the box Android
- calls work
...
This is disappointing, as I like to use Lineage.
I've been looking at the Lineage compatible devices:
Devices | LineageOS Wiki
wiki.lineageos.org
Of the 165 phones there, many look to be a
number of years old, and would not be a
candidate to work with ATT 5G.
q1:
Is there a setting that I need to tweak to
make Lineage work with ATT 5G?
q2:
What current phones can be converted to Lineage, and
are now compatible with ATT 5G?
Is there a list/link?
Or does anyone speak from experience?
Thanks a lot

I found out that it wasn't necessarily my phone. Over the past 5 -7 days in my area and maybe everywhere, ATT was doing switching to eliminate all 3G. I had been warned last June that this was going to happen and even tho my phone was VoLTE and 4G, consumer cellular was adamant about making me get a new phone, so I bought their samsung A01for $100 just to shut them up. Consumer Cellular actually shut my service off, forcing my hand and that was when I was living down in Alto Texas. However, I didn't like their phone because it was all googled up and I went back to using my Moto G7 plus with LineageOS. It has been the phone I depend on and I like it best. When my phone stopped working a couple days ago, it was right after an update, so I assumed the update was the problem or my phone was haywire. Then, I found out thousands of people were having the same problem from https://downdetector.com/status/att/ and they do consumer cellular, too.
Now, the new minimum requirement is to be 4G LTE compliant.
After giving up on Moto G7 plus, I put my sim card into my old Galaxy S9+ and it worked. I made a phone call and talked for more than an hour. After I hung up, I tried to make another call and as soon as I dialed, I was returned the message, "call ended" and I couldn't get it working again. So I moved the sim card over to the phone that Consumer Cellular sold me last summer, the samsung A01 and no mojo. I messed around with it for an hour or so. Also, I forgot to mention that whenever I put the sim into a different phone, I would get a text message from Consumer Cellular letting me know that they have somehow configured my phone to work on their network and I have no idea how that works because when tried to show someone the messages they sent me, they were gone as if someone had deleted them and I had no idea that the sender of a text could delete the sent message on the recipient's phone, nor push a configuration. Long story short, nothing worked.
I stopped in at the local ATT store, today. The guy looked at my phone and changed 1 thing (my APN) and it started working. He changed it from Pure Talk USA (att.mvno) to ATT Nextgenphone (nxtgenphone). So now I can make phone calls and check my voice mail etc.... however, I am NOT able to use data from the tower. My wifi works, but I should be able to get data from the darn tower. no luck. I just wanted to let everyone know that I dont think it's my phone. I think it's consumer cellular and ATT or maybe just ATT because consumer cellular uses ATT towers.

Question Changing carriers in the US -- also change the firmware?

I have a Samsung S21FE (Snapdragon) model SM-G990U bought from Samsung and originally configured for Verizon. I've used it on the Verizon network since I got it, but just recently switched to T-Mobile. The phone is still using the Verizon firmware however data IS working, as well as calling, texting, and voicemail. But there are still a few things that don't seem quite right and I'm wondering if a firmware update would solve it (also, what is the best to update the firmware?).
For instance, I used to see "5G UW" when I was on Verizon, and now on T-Mobile it should display "5GUC" but I'm just seeing "5G". Also, when it boots up I still see the Verizon logo. Also, even when it's displaying "5G" I am not getting true 5G speeds --> more in the range of 70-100 Mbps. I use the OpenSignal app and it tells me other T-Mobile users in my area are getting way faster speeds. I thought the S21FE had all the necessary bands to get full 5G but either it doesn't, or maybe the firmware is blocking it?
For comparison, we also just switched my daughter's Galaxy S21 at the same time from Verizon to T-Mobile. On her phone, the first time she booted up with the T-Mobile SIM card, she started seeing the T-Mobile logo on bootup and now she sees "5GUC" next to her signal (I do not).
In the Software information section under Service provider software version, my phone has: SAOMC_SM-G990U_OYN_VZW_13_0017 VZW/VZW/VZW.
My daughter's S21 now says "TMB" in her software version.
It seems like her phone automatically updated the firmware over to T-Mobile but mine did not.
Again, not sure if a manual firmware update would solve any of the above issues, and what is the best way to change the firmware. Anyone have any experience with switching carriers on a S21FE? Did you update firmware?

skokielad said:
I have a Samsung S21FE (Snapdragon) model SM-G990U bought from Samsung and originally configured for Verizon. I've used it on the Verizon network since I got it, but just recently switched to T-Mobile. The phone is still using the Verizon firmware however data IS working, as well as calling, texting, and voicemail. But there are still a few things that don't seem quite right and I'm wondering if a firmware update would solve it (also, what is the best to update the firmware?).
For instance, I used to see "5G UW" when I was on Verizon, and now on T-Mobile it should display "5GUC" but I'm just seeing "5G". Also, when it boots up I still see the Verizon logo. Also, even when it's displaying "5G" I am not getting true 5G speeds --> more in the range of 70-100 Mbps. I use the OpenSignal app and it tells me other T-Mobile users in my area are getting way faster speeds. I thought the S21FE had all the necessary bands to get full 5G but either it doesn't, or maybe the firmware is blocking it?
For comparison, we also just switched my daughter's Galaxy S21 at the same time from Verizon to T-Mobile. On her phone, the first time she booted up with the T-Mobile SIM card, she started seeing the T-Mobile logo on bootup and now she sees "5GUC" next to her signal (I do not).
In the Software information section under Service provider software version, my phone has: SAOMC_SM-G990U_OYN_VZW_13_0017 VZW/VZW/VZW.
My daughter's S21 now says "TMB" in her software version.
It seems like her phone automatically updated the firmware over to T-Mobile but mine did not.
Again, not sure if a manual firmware update would solve any of the above issues, and what is the best way to change the firmware. Anyone have any experience with switching carriers on a S21FE? Did you update firmware?
Click to expand...
Click to collapse
What's the model number?