I've seen others post about this issue. Here's what I've observed, and what I just sent to LG. Be sure to let them know this needs to be fixed!
"I have owned a G5 RS988 (Android 7.0) for 3 weeks, and am disappointed in its cellular reception on Cricket Wireless, which uses the AT&T network.
The RS988 frequently drops from LTE to HSPA connectivity. In my area, using the same SIM card, other phones ALWAYS maintain an LTE connection.
I believe that the problem is the G5 will not use Band 17, even though the specifications list Band 17. Using a monitor app on a Nexus 5X and my G5 while I travel locally (both using Cricket SIM cards), I find that the Nexus selects from Bands 2, 4, 5 and 17, and stays linked via LTE. The G5 selects from Bands 2, 4, and 5 only, and frequently drops to HSPA.
I hope you already know of this problem (it is being discussed on forums frequently) and have plans to update the software to solve it.
Thank you for your attention to this issue. "
Cellular signal -LG G5 RS988 vs Nexus 5X - same time, same place
I'm assuming you've already set up and selected the cricket wireless APN as follows:
Go to Settings, More, Mobile networks, Access point names, and hit + to add the new APN as bellow, then Save it, and select it.
Name: Internet
APN: ndo
MMSC: http://mmsc.aiowireless.net
MMS Proxy: proxy.aiowireless.net
Multimedia Message Port: 80
MCC: 310
MNC: 150
APN type: default,mms,fota,hipri,supl
APN protocol: IPv4
APN roaming protocol: IPv4
Turn APN on/off: ON
If you've already done this, then you can try a "Network reset" with your sim card removed. After the network reset and reboot, enter your WiFi password, turn off the phone, re-insert the SIM, turn on the phone, and verify the correct APN is selected.
Hope it helps!
Sent from my RS988 using XDA-Developers Legacy app
Thanks for your idea, C64. I had clicked the configuration link Cricket sent to me when I first powered up with the SIM installed, and never checked the APN settings.
I did find some differences and will edit them. I'll post my results here.
I just noticed a new post in the AT&T LG G5 Q&A forum in which the writer is having very similar issues. Numerous "me too" comments follow the OP. I assume these folks are using the AT&T model, not the RS988, and they are on AT&T, so that seems to indicate the problem more wide-spread.
I hope the G5 is not so far back in LG's rear-view mirror that they have no interest in solving this!
Commodore 64 said:
I'm assuming you've already set up and selected the cricket wireless APN as follows:
Go to Settings, More, Mobile networks, Access point names, and hit + to add the new APN as bellow, then Save it, and select it.
...
Hope it helps!
Sent from my RS988 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from mTalk
RS988 Problems
I've also noticed this and contacted LG about it. Definitely has to do with the update from Android 6 to Android 7. I actually went so far as to purchase a second RS988 and not allow it to update, and if I run them side by side, the updated version won't see band 17, which is widely used in my area (by ATT). I expect this is what your seeing as well. I also suffer from frequent drops, because of the location of the towers and signal strength. I've contacted LG twice, both times they denied knowledge of the problem, and only offered to send the phone in for repair. Two weeks without the phone is what they said for timing. I just got an OS update, thought it might address this, but it didn't.
Let me know if you find an alternative to sending in for repair.
Thanks for the input. After seeing your results and several others, I have no doubt the problem is built into the Nougat image for the RS988, and possibly for the AT&T G5 version as well.
I didn't contact LG tech support, because I knew their standard response would be, "never heard of this problem, send your phone in for repair". (Of course, not criticizing just LG here, this is standard for all tech support these days.) But sending it in would deprive me of the phone for 2 weeks or more, risk actual damage in the process, cause me to rebuild my apps and phone after they reset it, and accomplish nothing except (maybe) receiving the phone back with Marshmallow on it. Even if all bands show up on Marshmallow, I really don't want to pass up on the Nougat upgrade - there are too many benefits to miss out on.
So I made sure to register a complaint at LG customer service: http://www.lg.com/us/support/chat-and-email-information. Don't know if it will go anywhere, but rep promised it would be forwarded up the chain.
I'm finding that where I live, I'm getting by okay on the mostly LTE, occasionally HSPA signals I'm seeing. But I had one instance of no cellular signal at all (neither phone nor data) while in a medical building in an important part of town. If that was not just a fluke, it is a problem. Still investigating.
This is clearly a software blunder, not a hardware problem. So it can probably be fixed fairly easily during an update. The question is, without a massive number of complaints, does LG care to fix it on a phone is no longer their flagship?
cadteach said:
I've also noticed this and contacted LG about it. Definitely has to do with the update from Android 6 to Android 7. I actually went so far as to purchase a second RS988 and not allow it to update, and if I run them side by side, the updated version won't see band 17, which is widely used in my area (by ATT). I expect this is what your seeing as well. I also suffer from frequent drops, because of the location of the towers and signal strength. I've contacted LG twice, both times they denied knowledge of the problem, and only offered to send the phone in for repair. Two weeks without the phone is what they said for timing. I just got an OS update, thought it might address this, but it didn't.
Let me know if you find an alternative to sending in for repair.
Click to expand...
Click to collapse
Sent from mTalk
barotropic said:
Cellular signal -LG G5 RS988 vs Nexus 5X - same time, same place
Click to expand...
Click to collapse
I thought you should get an H820 instead if you stuck with Cricket.
damiloveu said:
I thought you should get an H820 instead if you stuck with Cricket.
Click to expand...
Click to collapse
The RS988 is the unlocked North American model of the G5, and has all the sensors and specs to be fully compatible with the AT&T/Cricket network, as well as with Verizon, and mostly compatible with TMo.
Being unlocked gives it many advantages over the AT&T model. I've suffered being AT&T's hostage with 2 previous carrier-locked, flagship phones - bloatware, locked bootloaders, slow updates, and downright broken updates which weren't fixed for weeks. Guess I'm a slow learner, but I finally vowed "never again!".
The problem being discussed here is apparently a software error introduced with Nougat by LG. The phone has Band 17 capability, which is very important on the AT&T network. It apparently used that band perfectly while running Marshmallow, but does not do so with Nougat.
Sent from mTalk
barotropic said:
The problem being discussed here is apparently a software error introduced with Nougat by LG. The phone has Band 17 capability, which is very important on the AT&T network. It apparently used that band perfectly while running Marshmallow, but does not do so with Nougat.
Click to expand...
Click to collapse
if this is software related, do you think trying a 3rd party rom could resolve the issue?
x000x said:
if this is software related, do you think trying a 3rd party rom could resolve the issue?
Click to expand...
Click to collapse
Possibly. But, as you know, the custom ROM's usually come with issues of their own - camera problems, GPS ,etc.
I've heard many reports that LTE was solid on the AT&T network before Nougat. I think I would find a way to go back to Marshmallow if it were a big enough problem for me. But 80% LTE / 20% HSPA is working okay for me, at least temporarily.
Sent from mTalk using a Dell Venue 8
barotropic said:
Possibly. But, as you know, the custom ROM's usually come with issues of their own - camera problems, GPS ,etc.
Click to expand...
Click to collapse
curious, have you installed the update? maybe this is related the this issues in this comment https://forum.xda-developers.com/lg-g5/how-to/rs988-software-update-21c-t3663768/page2
x000x said:
curious, have you installed the update? maybe this is related the this issues in this comment https://forum.xda-developers.com/lg-g5/how-to/rs988-software-update-21c-t3663768/page2
Click to expand...
Click to collapse
Thanks for pointing out that thread; I hadn't noticed. Yes, I installed 21c when it came out (a week ago?). I haven't noticed a change in behavior, but haven't been looking much either.
Sitting at my desk this morning, I'm still seeing HSPA on Band 5, where the Nexus 5X always has LTE on Band 17. So I doubt it's fixed, but I'll check it carefully while I'm out and about today.
Sent from mTalk
Related
This may be totally obvious and non informative to some and for that I apologize, but I'm putting it out there anyways.
I recently traveled around South Africa for a bit and was able to use my Verizon LG G3 VS985 rooted bumped running official CyanogenMod 11 latest nightlies (via cyandelta) with absolutely no problems. I put the Vodacom sim (South African cell company) in the phone and it worked perfectly. I was able to get HSPA, 3G, and EDGE without any problems and no modifications made to anything. The phone did all the work automatically.
Supposedly there was LTE available in some parts of the country, but I could never get it. I tried switching APNs, changing radio radio bands in the *#*#4636#*#* and still could not get it. I was tempted to try and unlock the other LTE bands (as seen in a thread that I'm too lazy to look up at the moment) but I decided to hold off until later.
I also put the Vodacom sim into my LG G2 that was running a stock rooted something and that worked perfectly too(still no LTE). Was weird using that again though after the G3. Made me really appreciate the bad ass-ness of the G3.
Anyways hope this was not a waste of post. Rock on G3
Always good to hear a firsthand account from a traveler.
It would be useful if you could post what you used for APN entries as well.
trent999 said:
Always good to hear a firsthand account from a traveler.
It would be useful if you could post what you used for APN entries as well.
Click to expand...
Click to collapse
All the APNs were auto populated and I just experimented with a couple different ones. Vodacom.sa and vodacom.lte.sa were the two that I tried. Ended up just keeping it on the LTE one hoping that it would pick up LTE at some point. Both APNs gave me similar performance and service. I never had to mess with the actual APN settings or manually input anything.
That's great, but pretty strange since the vs985 requires a new APN setting to be manually entered in the USA each time I switch to either my T-mobile or AT&T sim.
Sent from my VS985 4G using Tapatalk
Unlocked AT&T-branded PadFoneX. I'm getting low reception on Band 4 and no HSPDA+ reception whatsoever.
I upgraded the unit to the PadFoneS firmware and did the four Asus upgrades to bring it up to date with no better result. Applied the 99.99.99 down-grade back to KitKat and still no love. I use the APN settings for Fast T-Mobile USA and have tried others as well. My Huawei MediaPad Pro T1 8.0 gets strong T-Mobile reception and then switches over to HSPDA+ coverage once I enter my office building. The PadFone gets weak 4G LTE and then switches over to EDGE once I enter the building.
I was really hoping to replace my 8-inch Huawei with the PadFone but the radio reception just doesn't compare and I can't stand being forced to use EDGE inside my office building when I know that T-Mobile HSPDA+ coverage is usable within my building using the Huawei Phablet.
Can someone please please please help me in "fine tuning" this thing for T-Mobile. By the way the PadFone is rooted and I've unlocked the bootloader as well. Maybe there is updated modem firmware to flash? I just don't know what else I can do..
If you get HSPDA+ coverage from T-Mobile on your PadFone can you please share your configuration and APN settings??
Thank you!!!!!!
Chris R.
I have a PFX flashed to PFS Kitkat running on T-Mobile. Connects to the LTE network fine using the fast.t-mobile.com APN. Yes, reception seems to be on the weak side, but it gets the job done for me. Suspect that Mediapad gets a better signal due to it being larger = larger antenna.
HSPA works fine for me as well, but as this is an AT&T/International device, you'll only connect to HSPA on Band 2 (1900MHz). It lacks HSPA Band 4 (1700MHz/2100MHz) for T-Mobile's more extensive 3G network. It looks like that Mediapad has HSPA Band 4 (http://pdadb.net/index.php?m=specs&id=7233&c=huawei_mediapad_t1_8.0_pro_4g_td-lte_t1-821l), so that's probably why it's able to get HSPA signal while the PF does not.
Thank you!
xtermmin said:
I have a PFX flashed to PFS Kitkat running on T-Mobile. Connects to the LTE network fine using the fast.t-mobile.com APN. Yes, reception seems to be on the weak side, but it gets the job done for me. Suspect that Mediapad gets a better signal due to it being larger = larger antenna.
HSPA works fine for me as well, but as this is an AT&T/International device, you'll only connect to HSPA on Band 2 (1900MHz). It lacks HSPA Band 4 (1700MHz/2100MHz) for T-Mobile's more extensive 3G network. It looks like that Mediapad has HSPA Band 4 (http://pdadb.net/index.php?m=specs&id=7233&c=huawei_mediapad_t1_8.0_pro_4g_td-lte_t1-821l), so that's probably why it's able to get HSPA signal while the PF does not.
Click to expand...
Click to collapse
Thank you for your detailed answer! Finally, someone that understands this stuff! Hey, could I get the exact model number of your model?? I'm wondering if I could buy one like yours and then have it unlocked..curious...
Thanks!!!
Chris R.
crodgers79 said:
Thank you for your detailed answer! Finally, someone that understands this stuff! Hey, could I get the exact model number of your model?? I'm wondering if I could buy one like yours and then have it unlocked..curious...
Thanks!!!
Chris R.
Click to expand...
Click to collapse
My device is the AT&T Asus Padfone X (ASUS_T00D). On the white label under the back cover it lists the manufacturing date as 2014/05/31 and is H/W Revision 1.6 (PFX was launched in July 2014, so this is probably a launch model). Bought it from Ebay a year ago pre-unlocked. Used it on AT&T's firmware for a few months before flashing the latest Asus Padfone S (ASUS_T00N) Kitkat firmware, "WW_11.10.7.18". I think I had to manually set my APN, but was able to connect fine.
Looking at the signal levels, the PFX pulls in -108dBm at my desk, while my Moto E2 pulls in -100dBm, both on LTE Band 4. Moto devices tend to have better radios, but I didn't expect the smaller, budget Moto E2 to pull in a better signal than the PFX.
OK, now I'm confused....
xtermmin said:
My device is the AT&T Asus Padfone X (ASUS_T00D). On the white label under the back cover it lists the manufacturing date as 2014/05/31 and is H/W Revision 1.6 (PFX was launched in July 2014, so this is probably a launch model). Bought it from Ebay a year ago pre-unlocked. Used it on AT&T's firmware for a few months before flashing the latest Asus Padfone S (ASUS_T00N) Kitkat firmware, "WW_11.10.7.18". I think I had to manually set my APN, but was able to connect fine.
Looking at the signal levels, the PFX pulls in -108dBm at my desk, while my Moto E2 pulls in -100dBm, both on LTE Band 4. Moto devices tend to have better radios, but I didn't expect the smaller, budget Moto E2 to pull in a better signal than the PFX.
Click to expand...
Click to collapse
I pulled the back cover off of mine, it too is a T00D and, get this, manufacturing date was 2014/05/22 (!!!) FCC ID is MSQT00D, and H/W is 1.6 (!!).
I too did the X-to-S conversion and yesterday I applied each successive update until I got to the very latest 12.2.2.43 (16 Dec 2015).
So if we have nearly identical hardware, is there anything that I can do to improve reception? Could you send me the settings you used for APN?
Thanks!
Chris R.
By the way, your Moto is the better device, the lower the db number the better AFAIK..
crodgers79 said:
I pulled the back cover off of mine, it too is a T00D and, get this, manufacturing date was 2014/05/22 (!!!) FCC ID is MSQT00D, and H/W is 1.6 (!!).
I too did the X-to-S conversion and yesterday I applied each successive update until I got to the very latest 12.2.2.43 (16 Dec 2015).
So if we have nearly identical hardware, is there anything that I can do to improve reception? Could you send me the settings you used for APN?
Thanks!
Chris R.
Click to expand...
Click to collapse
Don't know how to improve the reception, but here's my APN settings:
Name: T-Mobile LTE
APN: fast.t-mobile.com
MCC: 310
MNC: 260
APN Type: default
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
Everything else is set to Not Set/None.
I didn't set up the MMS proxy as I'm using a tablet data-only plan on the PFX. (I think data-only plans come with free SMS/MMS, but I don't use it.)
crodgers79 said:
By the way, your Moto is the better device, the lower the db number the better AFAIK..
Click to expand...
Click to collapse
I know, which is why I was surprised that the cheap budget Moto E2 got a better signal than the PFX
crodgers79 said:
By the way, your Moto is the better device, the lower the db number the better AFAIK..
Click to expand...
Click to collapse
I probably know why you are not receiving a a good signal on your device.
The thing is when you do the conversion, from padfone x to padfone s, the partiton gets overwritten and causes some of the bands to be lost.
That partition is called the efs partition, and probably you have lost some bands that probably would have worked better before you flashed.
The side effects can be seen through the software when additional call settings does not work. (SIM doesnt get recognized)
That is a known problem, and to avoid that you had to back up the efs partiton prior to the conversion so you could restore those kinds of connections after the conversion.
--- You had to use adam outlers repacked twrp version to do all that.
I know many of the guides there have replaced mine but they forgot that one thing that has been talked over, and thanks to tjsooley and the people during that time, they were able to figure it out.
Thanks..but consider this..
Justatechie said:
I probably know why you are not receiving a a good signal on your device.
The thing is when you do the conversion, from padfone x to padfone s, the partiton gets overwritten and causes some of the bands to be lost.
That partition is called the efs partition, and probably you have lost some bands that probably would have worked better before you flashed.
The side effects can be seen through the software when additional call settings does not work. (SIM doesnt get recognized)
That is a known problem, and to avoid that you had to back up the efs partiton prior to the conversion so you could restore those kinds of connections after the conversion.
--- You had to use adam outlers repacked twrp version to do all that.
I know many of the guides there have replaced mine but they forgot that one thing that has been talked over, and thanks to tjsooley and the people during that time, they were able to figure it out.
Click to expand...
Click to collapse
Thanks! I did read through all these threads searching for an answer before I posted my question. the first time I did the X-to-S conversion I thought exactly what you said (destroyed the efs partition containing the modem info). So I went back and loaded the 99.99.99.99 version posted on the Asus site which is supposed to restore it to factory settings and back to KitKat but that had no effect. Since 99.99.99 is for the PadFone S maybe that doesn't make use of the partition under KitKat, I don't know.
What I would dearly love to load is a flashable version of the original AT&T software (thereby restoring the partition and the modem info). I saw one guy had posted TWRP backups of stock but when I tried to restore them to my phone the script bombed and it aborted.
I agree with the other gentleman, I need UMTS Band 4 - (1900/2100) for this thing to work well in my area and it looks like this phone doesn't support it. If I could find someone familiar with QPST to tell me if that band is unlockable that wold be great!
Thanks!!!!
Chris R.
Unfortunately QPST couldn't work with this device, idk know why.
You could find out by searching through using the xda search engine, but the question is, did you back up your modem for this device prior, because it could be restored when the phone is on a stock fw, then you could create an efs backup afterwards.
To answer the question with the tarp backups, those were created from the repacked twrp version so flash that first and back up everything before you restore back to at&t fw. I don't think the quarx version could work with that since the repacked was based on the nexus 5. (Similar parts) (be aware that you need to wait a couple of mins for the black screen to go away, on that version of twrp.)
The thing is that I could use band 2 and 4 on at&t with this fw, (I did not restore my efs partition since the conversion since I lucky live in a good area) but it looks like band 4 doesn't work for t-mobile, hmmm maybe it is incompatible like the other guy said, but we'll see. After wards you gotta see if these bands would restore upon restoring back to the at&t fw.
Justatechie said:
I probably know why you are not receiving a a good signal on your device.
The thing is when you do the conversion, from padfone x to padfone s, the partiton gets overwritten and causes some of the bands to be lost.
That partition is called the efs partition, and probably you have lost some bands that probably would have worked better before you flashed.
The side effects can be seen through the software when additional call settings does not work. (SIM doesnt get recognized)
That is a known problem, and to avoid that you had to back up the efs partiton prior to the conversion so you could restore those kinds of connections after the conversion.
--- You had to use adam outlers repacked twrp version to do all that.
I know many of the guides there have replaced mine but they forgot that one thing that has been talked over, and thanks to tjsooley and the people during that time, they were able to figure it out.
Click to expand...
Click to collapse
The EFS partition contains the modem, yes, but this isn't the issue here. When it comes to bands used in the USA, the Padfone S firmware has all the bands the Padfone X uses except for LTE Band 17, which is only used by AT&T, and would not affect T-Mobile in this case. I was able to use my PFX-converted-to-PFS on T-Mobile without restoring EFS fine.
Thanks!
xtermmin said:
The EFS partition contains the modem, yes, but this isn't the issue here. When it comes to bands used in the USA, the Padfone S firmware has all the bands the Padfone X uses except for LTE Band 17, which is only used by AT&T, and would not affect T-Mobile in this case. I was able to use my PFX-converted-to-PFS on T-Mobile without restoring EFS fine.
Click to expand...
Click to collapse
I think the PadFone's lack of UMTS Band 4 is what's keeping me from getting HSPDA+ inside my office building. Once I head into the building my 4G on Band 4 reverts to Edge (ugh!) and I have a 14Gb tethering plan so that I can run my tablet while inside the building..arrggh!
Thanks for your response!
Chris R.
So my lg v30 will connect to LTE on extremely rare cases, any other time it will not. I've been monitoring signal and events through Network Guru. According to it my LTE has a problem attaching. Whatever it is that means. So when it does connect to LTE and I move out of range of one tower, I get Tracking Area Update Failure. What could be causing this? How can I fix it. I've set the APN to the best of my ability, but currently I get message APN settings not available for this user. I can still add an APN and save it, but I have no idea if it actually saves cause I can't view the list of APNs. However even before this APN message I had these problems and I knew for a fact the APN was correct. Any help is appreciated!
What variant do you have
What firmware are you on
What carrier are you using
ChazzMatt said:
What variant do you have
What firmware are you on
What carrier are you using
Click to expand...
Click to collapse
At&t
I am on lineage is
I am using google fi, but since is not fully fi featured its basicay T-Mobile
DTexUS said:
At&t
I am on lineage is
I am using google fi, but since is not fully fi featured its basicay T-Mobile
Click to expand...
Click to collapse
So you have H931 converted to US998 and then with Lineage custom ROM installed.
But you are limited to T-Mobile coverage.
Do you live in good T-Mobile area? For instance my mother doesn't. There's no T-Mobile towers near her.
If you are in a good T-Mobile area, you have two options:
1) Ask in Lineage custom ROM thread how to edit/create APN.
2) For test purposes, sign up for cheap T-Mobile MVNO like Mint to see if you get better "T-Mobile" LTE signal. You're only using T-Mobile anyway... First sign up and get "new" phone number just to get a Mint SIM card for test purposes. If you like it, then port your real phone number over and let the "test" phone account die (it's prepaid, so not much money).
Or any T-MOBILE MVNO which allows you to "Bring Your Own Phone".
ChazzMatt said:
What variant do you have
What firmware are you on
What carrier are you using
Click to expand...
Click to collapse
ChazzMatt said:
So you have H931 converted to US998 and then with Lineage custom ROM installed.
But you are limited to T-Mobile coverage.
Do you live in good T-Mobile area? For instance my mother doesn't. There's no T-Mobile towers near her.
If you are in a good T-Mobile area, you have two options:
1) Ask in Lineage custom ROM thread how to edit/create APN.
2) For test purposes, sign up for cheap T-Mobile MVNO like Mint to see if you get better "T-Mobile" LTE signal. You're only using T-Mobile anyway... First sign up and get "new" phone number just to get a Mint SIM card for test purposes. If you like it, then port you real phone number over.
Or any T-MOBILE MVNO which allows you to "Bring Your Own Phone".
Click to expand...
Click to collapse
I have tried many different carriers, all the same no LTE but gsm/edge works fine. Today I got to my jobs workshop and LTE started working, but as soon as I got into the town I was working in I lost it, LTE attach failure, or Tracking update failure. I'll see what I can do on the APN side of things. But do you have any information as to why it could get LTE sometimes and then other times the LTE attach failure comes up? At this point I'm likely just gonna get a fi compatible phone (Edit: one that has the auto network switching, the v30 is supported just will only work on T-Mobile towers), but just for learning's sake I'd love to figure this out. I looked at the coverage map for T-Mobile and I appear to be in a good area, and both the shop and the town mentioned above seem to be as well. Its almost as if the phone struggles to switch between towers. (I'm no service expert)
My question/problem. What/why do I have a good 4 bars (of 5 bars) of data signal normally, but, when I decide to dial and make a telephone call, the signal strength goes to barely one bar as soon as I hit the dial button on the phone? I have not moved myself or the phone's location. The call may dial, but goes in and out and, more often than not, drops the call. At the same time, if I receive a call from someone, it is normally a much better signal, and does not drop or go in and out.
I am on Verizon phone (vs996) Frankenstein to us998 30b (pie). I have recently tried android 10 roms (Havoc, POSP). I don't know if that has anything to do with it or not? Very frustrating when trying to call someone.
Any thoughts or explanations or, hopefully, fixes?
Thx
gimpy1 said:
My question/problem. What/why do I have a good 4 bars (of 5 bars) of data signal normally, but, when I decide to dial and make a telephone call, the signal strength goes to barely one bar as soon as I hit the dial button on the phone? I have not moved myself or the phone's location. The call may dial, but goes in and out and, more often than not, drops the call. At the same time, if I receive a call from someone, it is normally a much better signal, and does not drop or go in and out.
I am on Verizon phone (vs996) Frankenstein to us998 30b (pie). I have recently tried android 10 roms (Havoc, POSP). I don't know if that has anything to do with it or not? Very frustrating when trying to call someone.
Any thoughts or explanations or, hopefully, fixes?
Thx
Click to expand...
Click to collapse
If you are using Verizon on US998 firmware, then you don't have access to VoLTE (which is phone calls over LTE, Voice over LTE). LTE started out as a data-only service but for actual phone calls, carriers were still using 3G HSPA or CDMA (Verizon, Sprint). When making a phone call, phones temporarily bump down to 3G, and then jump back to LTE after the phone call is over.
With the VoLTE protocol, that finally allowed phone calls with LTE. It added VOICE capability to LTE.
However, different carriers treat VoLTE differently. T-mobile allows VoLTE and Wi-Fi calling for US998 phones, while AT&T and Verizon are more stingy. They reserve VoLTE mostly for their branded phones running their carrier firmware.
I'm an AT&T customer and I've never had VoLTE because I've never used a branded AT&T phone. For me, on AT&T, when I make a phone call I am bumped down temporarily to AT&T HSPA. Then, after the phone call, it jumps back to LTE.
If I were to flash the AT&T TWRP flashable zip, possibly I could enable that. But it's not just firmware, it's also a setting on the carrier side that has to be enabled.
Bottom line, what's happening is you are seeing you STRONG LTE signal. But when you make a phone call, you are being temporarily bumped down to Verizon CDMA. However, Verizon is in the process of dismantling all their CDMA towers. That's why your CDMA signal is so weak. Verizon plans to shutdown CDMA entirely by end of 2020. After that, you will need VoLTE to make phone calls on Verizon.
Since you have an actual VS996, you can flash the VS996 TWRP-flashable zip. Once on that firmware, see if VoLTE is enabled on your account (carrier side setting) and see if when you make phone calls you stay on LTE and are not bumped down to CDMA?
Thx, Chazz. So, it's a Verizon thing? Not necessarily something I caused by going back and forth trying out the different Android 10 roms. Good to know. I will try the 996 rom later today, since I don't need the Hotspot for a couple of days. As always, you've been very helpful, thx. :good:
gimpy1 said:
Thx, Chazz. So, it's a Verizon thing? Not necessarily something I caused by going back and forth trying out the different Android 10 roms. Good to know. I will try the 996 rom later today, since I don't need the Hotspot for a couple of days. As always, you've been very helpful, thx. :good:
Click to expand...
Click to collapse
Yes, especially if you see strong LTE signal before making the phone call. Control freak Verizon (mostly) only allows VoLTE on Verizon firmware with Verizon branded phones. There may be exceptions (maybe Pixel phones?) and I know the ZTE Axon 7 (not a branded Verizon phone) somehow got VoLTE not only on ZTE stock firmware but also on LOS ROM -- but I believe ZTE paid Verizon to allow that. It's the exception that proves the rule.
Here's a a more in depth article about Verizon CDMA being shut down end of this year.
https://grantcountyreview.com/content/verizon-wireless-postpones-its-shutdown-3g-cdma networks
when Verizon closes its 2G and 3G networks at the end of 2020, 3G phones will become obsolete and non-VoLTE LTE phones will not be able to make or receive calls.
Click to expand...
Click to collapse
You DO have a Verizon VoLTE capable phone -- a Verizon VS996 -- but for V30 only on Verizon firmware. If you were using T-mobile with US998 firmware, you would have no problems with VoLTE or Wi-Fi calling. T-mobile is more open than Verizon about such perks.
I don't get VoLTE with AT&T on US998 firmware, but AT&T has no plans to end 3G HSPA anytime soon.
Chazz, I thought I would give a quick update. Late Last night/early this morning, I switched to vs99630c. I have made two phone calls, one to Florida, one to Washington state. Both connected and sounded so much better than when with the us99830b Rom. Even though both dialers had a little HD in the upper left hand corner. This Rom kept the same 3 or 4 bar designation for the signal strength. Much happier with it. Even though I don't have a hotspot (may have to pay the $10(?)or so to set it up, if I decide to stay on here.
Also, I have just seen a 99630c debloated Rom someone has made, that I might try in the next day or so.
I so wanted to try the android 10 Roms, but I just had too many small issues (reboots, no hot spot, system ui crashes, etc.).
Thnx, again for your help and guidance.
gimpy1 said:
Chazz, I thought I would give a quick update. Late Last night/early this morning, I switched to vs99630c. I have made two phone calls, one to Florida, one to Washington state. Both connected and sounded so much better than when with the us99830b Rom. Even though both dialers had a little HD in the upper left hand corner. This Rom kept the same 3 or 4 bar designation for the signal strength.
Much happier with it. Even though I don't have a hotspot (may have to pay the $10(?)or so to set it up, if I decide to stay on here.
Also, I have just seen a 99630c debloated Rom someone has made, that I might try in the next day or so.
I so wanted to try the android 10 Roms, but I just had too many small issues (reboots, no hot spot, system ui crashes, etc.).
Thnx, again for your help and guidance.
Click to expand...
Click to collapse
Then you are now probably using Verizon VoLTE, which is using LTE signal -- not the increasingly degraded CDMA signal Verizon will completely shut off December 31, 2020.
Verizon is probably already deprecating those towers -- leaving just enough, like when you're on the highways.
ChazzMatt said:
Then you are now probably using Verizon VoLTE, which is using LTE signal not the increasingly degraded CDMA signal Verizon will completely shut off December 31, 2020.
Verizon is probably already deprecating those towers -- leaving just enough, like when you're on the highways.
Click to expand...
Click to collapse
I really want volte and vowifi for my unlocked us998. The only way to have that is to flash the vs rom, which is 30c? I'm on US99820h, what do I lose by going to the vs rom? Is there a vs 20h variant?
ldeveraux said:
I really want volte and vowifi for my unlocked us998. The only way to have that is to flash the vs rom, which is 30c? I'm on US99820h, what do I lose by going to the vs rom? Is there a vs 20h variant?
Click to expand...
Click to collapse
Yes, we have Oreo VS996 KDZ. It's actually "20k", because it took Verizon two attempts to fully release LG V30 Oreo. And they released a couple extra updates for Verizon related bugs. So, although it's equivalent to US998 20h, it's a higher letter.
https://forum.xda-developers.com/lg-v30/development/vs996-lg-v30-verizon-vs996-t3865398
You need to have VoLTE enabled in your Verizon account, besides flashing this firmware. It helps to have it already enabled from a Verizon branded phone. But sometimes a helpful store rep willing to bend the rules can do it for you.
ChazzMatt said:
Yes, we have Oreo VS996 KDZ. It's actually "20k", because it took Verizon two attempts to fully release LG V30 Oreo. And they released a couple extra updates for Verizon related bugs.
https://forum.xda-developers.com/lg-v30/development/vs996-lg-v30-verizon-vs996-t3865398
You need to have VoLTE enabled in your Verizon account, besides flashing this firmware. It helps to have it already enabled from a Verizon branded phone. But sometimes a helpful store rep willing to bend the rules can do it for you.
Click to expand...
Click to collapse
I thought the Pie variants were not great, lots of broken features? Or was that just the US998 versions? What were the tradeoffs to staying on Oreo?
ldeveraux said:
I thought the Pie variants were not great, lots of broken features? Or was that just the US998 versions? What were the tradeoffs to staying on Oreo?
Click to expand...
Click to collapse
You asked for Verizon Oreo equivalent to US998 20h and that's what I gave you.
I'm not recommending Pie for US998.
Verizon Pie may be a lot better. I don't know. Someone using Verizon Pie will have to answer.
ChazzMatt said:
You asked for Verizon Oreo equivalent to US998 20h and that's what I gave you.
I'm not recommending Pie for US998.
Verizon Pie may be a lot better. I don't know. Someone using Verizon Pie will have to answer.
Click to expand...
Click to collapse
I misread, somehow thought the ROM you linked was Pie. My bad. I know dirty flash is never recommended, but could I get away with it here? What do I lose by going with the VS ROM over the US998? Apparently the only things I have to gain are VOLTE and possibly VVM?
ldeveraux said:
I misread, somehow thought the ROM you linked was Pie. My bad. I know dirty flash is never recommended, but could I get away with it here? What do I lose by going with the VS ROM over the US998? Apparently the only things I have to gain are VOLTE and possibly VVM?
Click to expand...
Click to collapse
Do you have VoLTE already enabled in your Verizon account?
You'll lose the no bloatware experience, but you can fix that with Titanium Backup.
As for dirty flashing, you can try... If it doesn't work, then you have to factory reset and clean install. Don't forget to reflash Magisk.
ChazzMatt said:
Do you have VoLTE already enabled in your Verizon account?
You'll lose the no bloatware experience, but you can fix that with Titanium Backup.
As for dirty flashing, you can try... If it doesn't work, then you have to factory reset and clean install. Don't forget to reflash Magisk.
Click to expand...
Click to collapse
I logged into my VZW account and after 8745 menus, finally found the HD Voice section. It says it's "Active", so I should be good for the VS ROM yes?
ldeveraux said:
I logged into my VZW account and after 8745 menus, finally found the HD Voice section. It says it's "Active", so I should be good for the VS ROM yes?
Click to expand...
Click to collapse
Seems like, yes.
I had to do a few steps to manually activate HD/VOLTE on my VS996 phone when I was on VZ. I documented the steps somewhere here (using ShortcutMasterLite). I know at least one other member here used the same steps on his phone. I'm thinking you'll be fine once you're on VS996.
I have not switched to Pie... still running Oreo. I have heard too many issues with Pie, so I have no desire to bother. I can't imagine VZ's Pie release is any better than Pie US998. VZ is too lazy to do anything else right, so why would they bother fixing what's wrong on US998.
Just want to quickly update this thread. I dirty flashed the VS99620K.zip in TWRP, then immediately flashed the latest Magisk zip. Everything updated perfectly, installed about 10 VZ apps, and I now have VOWIFI (and can send/receive texts!), though haven't been able to check VOLTE as I'm currently in a dead zone.
I'd already had HD calling active on my account, but can't select the option to also enable Video Calling. It says I need to contact support. I chatted multiple times with VZ support who claim it's active, though every time I try to enable it, it gives me the same error. What is this option, and do I need it? I'm pretty sure I was able to use Duo, Skype, Zoom, etc before the ROM update, am I spinning my wheels here?
Also, independent of this upgrade, my motion GIFs in any text app don't move. I thought it might have something to do with the non-VZ specific kernel, but after flashing, still just shows a static picture.
ldeveraux said:
I'd already had HD calling active on my account, but can't select the option to also enable Video Calling. It says I need to contact support. I chatted multiple times with VZ support who claim it's active, though every time I try to enable it, it gives me the same error. What is this option, and do I need it? I'm pretty sure I was able to use Duo, Skype, Zoom, etc before the ROM update, am I spinning my wheels here?
Click to expand...
Click to collapse
Are you the account holder? Some people can't get to it as they are just user.
https://community.verizonwireless.c...video-calling-feature-is-disabled/td-p/853001
I'm not sure what Verizon video calling is. I'm guessing some Verizon-only video chat -- like Apple's FaceTime is only for iOS? If you are already using Duo, Skype, Zoom, it would seem you don't need it. But you do make sure you have voice over LTE (VoLTE, called "HD calling" Verzion) --before end of this year.
ChazzMatt said:
Are you the account holder? Some people can't get to it as they are just user.
https://community.verizonwireless.c...video-calling-feature-is-disabled/td-p/853001
I'm not sure what video calling is. I'm guessing some Verizon-only video chat -- like Apple's FaceTime is only for iOS? If you are already using Duo, Skype, Zoom, you don't need it. But you do need to get voice over LTE.
Click to expand...
Click to collapse
I am the only user on this account, so definitely the account holder. After more wasted chats with VZ, they said that since my phone is not VZ branded, it's not eligible for Video Calling, which apparently is exactly as you described; Facetime for non-iphone Verizon users. I don't need that, as you said all my other platforms work fine.
How do I determine if VOLTE works? Like I said, I'm in a dead zone now, but going out to a good cell region in a few hours and can check then somehow. I did confirm that I can make calls and text over WiFi, so that's half the battle. How to check VOLTE?
ldeveraux said:
How do I determine if VOLTE works? Like I said, I'm in a dead zone now, but going out to a good cell region in a few hours and can check then somehow. I did confirm that I can make calls and text over WiFi, so that's half the battle. How to check VOLTE?
Click to expand...
Click to collapse
I think if you have Vo-WiFi that means your VoLTE is also activated. They seem to be packaged together.
If you make a call in a good signal area, see if the "4GLTE" icon stays on when you make the call. It may even change to VoLTE icon? or HD calling icon? A Verizon user can probably tell you better. But the key is to see if there are any status bar icon changes and what they are. Also see if there is any information in the dialer GUI during the call, where you click on the dialer timer.
Yeah, don't talk to VZ. They're too stupid to help and downright liars. Your phone will work fine on their network even if it's not VZ branded (I've used US998 and H931 phones on VZ without issue).
On my phone, I did have to do some setting changes in SML (ShortcutMasterLite) to get VOLTE working. I don't think most people have to do that, but I did... and I agree, I think that got VOWIFI working as well. I'm guessing you have both, too... just need to try it. If not, you can force-activate it as I documented earlier (via SML).
I plan to keep updating this XDA forum thread with what I find out about this problem, potential solutions, and hopefully what solves it. Hopefully this will be useful to those with the same or similar problem.
Please excuse typos...
The Solution
The reality is, prevention is the best solution here, do a bunch of research to make sure you don't encounter this problem. Read the rest of the post to better understand.
Original
Thank you in advance for reading this and helping me. (I also posted this in r/LGG8X, and am posting it here because some people don't have accounts with both. The more people that see it, the better, if by chance someone has ideas, wants to help, and has time to post the ideas)
It seems like a lot of people are having this issue, so maybe someone might have an idea.
I bought this phone to replace my Xiaomi Mi 9 (which was on the fritz, turning itself off randomly), about 1.5 weeks ago. I did my research and reasonably concluded that this phone has LTE band 12 and VoLTE; also it would be foolish of LG to not to have that. I could not find the VoLTE or Wifi Calling switches anywhere in the settings app, or in the phone app. I then dialed " *#*#4636#*#* " which opened up the "Testing Settings" (as usual). I click on the "Phone Information" tab, scroll down and find both the VoLTE and Wifi Calling switches, which are, to my dismay, greyed out.
I called Ting and they said, (after getting the IMEI), that this doesn't have LTE band 12, therefore no VoLTE. That confused me, because like I said, my research before buying had already concluded that it has band 12. The Ting rep said that's all he could do for me, so we ended the call. I did another 30 mins of research, again concluded it has band 12 with VoLTE. I also called LG themselves, and the rep there confirmed that this phone has band 12 with VoLTE, they also said "we would be more than happy to verify that the phone works with you carrier through phone conferencing". I asked the rep about about the previously mentioned VoLTE and Wifi Calling switches being greyed out, and they said that's because the phone has those 2 capabilities, but the carrier has to enable them.
I really love this phone, especially in comparison to the Mi 9 (even tho the Mi 9 is a good phone). I love the software better (even with the weird quirks that it has), and the value proposition is quite good. I really don't want to have to get a 3rd new phone in one year. If anyone has any ideas/help that would be greatly appreciated.
Thank you
[Edit]: P.S. I think this is partly a problem with LG, and partly with the carriers. I suspect that LG messed up with the IMEI/etc and other important identifiers as to what the device is, what exact version (i.e. LM-G850UM, etc) of a particular model (i.e. LG G8X Thinq Dual Screen, etc). This leads to the cell carrier's infrastructure seeing this phone as incompatible (doesn't see LTE Band 12, when it really is. The cell carriers, (from my own experience with 2 Ting Reps, and from what others have said on other forum threads), can't or won't solve this problem, even tho it may be solvable. From what I have seen on other forums, some got it solved by the cell carrier entering codes on the phone and doing something on their side. If LG and the all the networks would talk to each about this problem and get it solved if possible that would be awesome...
Update - 11/04/2020:
It seems I unintentionally bought a G8X with the Canadian rom LMG850UM20e. I am doubtful, but is the hardware the same or similar enough to flash the USA unlocked rom LMG850QM? Or is there something else I can do to make the Ting network allow VoLTE? As far as I can tell, the Canadian model still supports VoLTE LTE Band 12, but correct me if I'm wrong.
Update - 11/05/2020:
Ting says that my phone has LTE Band 12 and therefore VoLTE, but that will only work on ATT. A bit confusing because (like I said) the particular rom on my phone is Canadian (LMG850UM20e), so why ATT? The explanation for that, it seems is that ATT, (and Sprint), and the unlocked Canadian version have the same sub-model: LMG850UM. The USA unlocked version has a different sub-model (LMG850QM), the rest of the world has yet another sub-model (LMQ850EMW). There are around 15 different versions it seems; see this reddit post on the different models: (can't post the link yet) title: "Hey G8X owner, what is the submodel number and regional code of your unit? And where did you buy it from? I am trying to complete this list, also relating to timing of security updates and Android 10 release." posted in r/LG G8X
It seems like all the versions (LMG850......) have the same hardware, the only difference are the roms, which seem artificially disable certain capabilities of the phone. I am pretty sure my phone would do VoLTE just fine on Ting (or most other carriers). The thing wrong here, I think, is that the IMEI and other specific identifiers of the phone artificially show that the phone does not have the functionality, so the networks don't enable it. It also seems like LG made an agreement or something with ATT as well as Sprint (separately), to release carrier-specific version (as most brands seem to do), and that the phone would fully work on their respective networks and MVNOs, at least the versions in the LMG850UM sub model group, and the USA unlocked sub-model group. LG and T-Mobile seem to have come to no such *official* agreement, unfortunately. I am wondering any of the versions work with T-Mobile and it's MVNOs out of the box, some *modifications* may have to be done in order to get it working on TM towers. There may also be unintentional bugs in some or all roms that are possibly causing, or more likely, adding on to the problem.
Obviously, I am still trying to find my around this problem. I'm considering flashing a USA unlocked rom (LMG850QM sub-model), though not sure if that's possible, or if it'll change what the IMEI and the other specific identifiers tell the cell carrier about compatibility. I also wonder if carriers have the ability to override the artificial restrictions. There is also one report of T-Mobile supposedly fixing the same/similar problem with Sprint for a customer, see u/Veshtarii's comments on this reddit post: (can't post link yet) title: "LG G8X unlocked models having issues with US carriers." Posted in r/LGG8X. Another reddit user used a cheap Tracfone sim card to make his phone work on T-Mobile: (can't post link yet) title: "Tutorial: How to Update eBay Unlocked ATT / AT&T LG G8x" Posted in r/LGG8X. I am unsure if he also has VoLTE working.
Update - 11/06/2020
I'm done with this... It is pretty much impossible. I commented on the "Tutorial: How to Update eBay Unlocked ATT / AT&T LG G8x" post, and the OP responded and said he can't get VoLTE working, even with doing that update. The only thing that could possibly work, is flashing the USA unlocked sub-model onto it. However I probably don't know enough to do it right, but the bigger reason is that it'll probably brick it. I've realized, and should realized when I was doing the research for a new phone, that ATT and TMO's VoLTE/Wifi Calling work differently. They both use propriety coding, which they license to each brand to use in the models they both come to agreement on, and a similar agreement with each MVNO under their towers. LG and TMO seem to have made no such agreement for the G8X, therefore in all practicality, no G8X will work on any of their towers. Also, I called H2O Wireless just to see if my phone works with them, but they said my IMEI is not compatible; so I'm not the Canadian model that I have works in the US at all, that makes me think that not even the versions inside each sub-model aren't even compatible with each other. There is that one situation I mentioned, where the person who was having problems with Sprint before the merger, took it to TMO after the merger and the TMO tech fixed it for him. But I think he must've been having a different problem, because his phone is probably still technically running on Sprint towers. Sprint made the agreement with LG, so VoLTE would work in that instance. Flashing is practically not a solution for most people.
I should've done more research than I did before buying the phone. That is the moral of this story; make sure you do all your "homework" before buying any phone anywhere but the shop of the carrier you are using (or plan to use). That leads me to my number one complaint with phone brands and especially cell carriers as whole: they make it incredibly annoying, often difficult, and confusing to find a compatible phone that isn't on the carrier store. And the problem with that is that everything in any carriers' stores is everything is stupidly overpriced, and then they get you hooked with pricey deals you don't want. If you're reading this, you're most likely like me, you know better than to spend more than you have to on a phone and plan in the carrier store, you know (or at least kinda know) how to get past that. I get that cell carriers want to make money, but I tell you, this is too far. Anyways, the point is, there is no immediate solution, in other words, your only worthwhile solution is prevention, doing a bunch of research. I'm done with this... I'm returning this phone and getting the vanilla G8...
I have the LMG850QM. It has no VOLTE icons while in call even if on band 12. It uses HD+ and that will be shown in dialer during call. Internet does work while in call so believe that it is working. The switches are on like yours but greyed out. Wi-fi calling does work. By turning on airplane mode and then turning back on wifi the dialer will show that calls are being made over Wifi. The OnePlus 6T has VoWifi icons in status bar and this phone doesn't. I will say that this phone gets service in buildings where neither of my 6t's would have service.