Hey guys,
So it seems there is an issue with the 10c FOTA update which also contains the Nov security patch. I accepted it and found that there are issues with LTE on it where you may experience issues sending and receiving text messages, miss calls and lose data connection constantly. I found this was also reported on Reddit by several people too . I've reached out to LG and we'll see what they have to say. They will get back to me likely in a few days. So after playing around with network settings, apn and even factory resetting and reflashing via LGBridge there is no known fix. I was unable to find whatever the previous software was (I presume it was 10b) but I didn't really take note of the name of it. I have changed my network from GSM/WCDMA/LTE auto to GSM/WCDMA auto and it seems to have made the device usable again. Although no LTE so that's not exactly a good solution. But hopefully they'll fix this up sooner than later.
Anyway you've been warned that if you have the Canadian variant you may have issues if you accept the 10c ota
If anyone else has this problem ping me. I may have found a fix for this. I need to get someone else to test this out.
Update: I'm 99% sure I've fixed this
Ok guys I've found a fix for this and made a new thread here.
This thread can serve as a warning still but it really no longer is needed so I'm closing it. Participation is however welcome in the thread referenced above.
Related
Hello All,
I have been looking around and seeing if anyone else is experiencing the same issue I have. But I have not had much luck. I have seen similar cases, but for whatever reason, some of the workarounds found that worked for others have not been successful for myself, or are temporary.
For the past three months, I have been experiencing an off and on issue where I am unable to receive texts, but I am able to send out text. And it is something that I would not realize until people actually notify me, or it is awkwardly silent on the "texting front", which makes me second guess myself. Almost every other week or two weeks this has occurred. At the time, I am running Darky's 8.8 [4.1.2] ROM for the i9300. I have tried rebooting, taking out the SIM, re-flashing Darky and re-flashing Stock (full wipe, etc), and replacing my old SIM with a new one. None have been successful thus far. The only success I have found is that inserting my SIM in a different phones allows the text to flow through almost immediately. I would then place the SIM back in the i9300 and any new texts sent I would receive immediately. After a week or two, it randomly just stops receiving text again, and the cycle continues.
I was wondering if whether this may be a bug with the Android OS itself? I have seen a few posts in regards to SMS being handled by Jelly Bean, but I am not 100% sure if my issue would fall in the same boat. Or if it is possibly faulty hardware? Or some kind of network issue. My network is AT&T, but I'm ruling out a network issue since I am able to receive text almost instantaneously on other phones.
Any information, advice, or help would be greatly appreciated.
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
JJEgan said:
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
Click to expand...
Click to collapse
I've verified that the MMS APNs and SMS settings are correctly configured to AT&Ts network. If it were incorrect from the beginning, I would not get text messages (or MMS) at all. But in this case, it is intermittent and only resolved when I get to "unload" the text messages on to another device.
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
b-eock said:
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
Click to expand...
Click to collapse
Ahh! Thank you b-eock! I don't mean this in the wrong way, but I'm glad that I'm not the only who has experienced this. When this occurred to you, were you on some version of 4.1.2? From what I can remember, this issue never came up until I upgraded from 4.1.1 to 4.1.2. Just trying to find some kind of trend here...
I have had to call up AT&T a number of times regarding this issue. And each time they were of no help. Although they were able to confirm that everything on their end of setup correctly, I got the same BS that you got. And they even gave me the whole baloney that I should upgrade so that they can help assist me better and that since it is not their branded phone, it may not be fully compatible.
I really do not want to give up on this. And I definitely want to find a solution. So I am hoping there is a lucky one out there that has tried different ways of getting fixed. Whether that be trying a new ROM, or downgrading from Jelly Bean to ICS, etc.
Came up a few weeks after I upgraded to 4.1.2 but there isn't really a connection between that. It worked before. Its just random crap. And them telling us everything is good on their end, that's complete BS. They don't know what's going on behind their computer screen.
Same exact thing happens to me. It's ROM dependent i'm thinking. Samsung roms from other countries do it the most for me. Has done it on AT&T and AT&T with StraightTalk. Experiencing it on Purelok HD v3.1 right now. I love this rom but im probably going to go AOSP/AOKP as I don't experience it on those kind of roms.
Camera just isn't the same without the Samsung software to me.
Short version... I installed CM12 official. From that point forward I have been plagued with a persistent network issue. Obviously I know this is my go to group of peeps. So here I am.
As pictured below I have many more options in preferred network type then I probably should have. Also I have more APNs then I remember previously having. I'm not even sure the APNs are setup correctly. I just need to know how to revert to how it was before the CM12 install. I have sense changed the radio twice to attempt a fix and have also installed two other ROMs. One of which worked fine before the aforementioned issue. If I select from below LTE / WCDMA, I get data with no cellular service. If I select CDMA + LTE/EvDo I get cellular service with only 3G data. Please someone have an answer for this one.
Bump. I have done plenty of searching. What I did see was there are three files that I maybe missing. They are referred to in another very similar posting on how to unbrick a bad flash from N7100. That being said. Those files mentioned are not available. So I'm hoping someone can shed some light on this.
I have this exact same issue except at times I have no data whatsoever where I did before installing CM 12. Came from Alliance rom on my Note 2. Any help would be appreciated. It's very frustrating.
ΜΟΛΩΝ ΛΑΒΕ
At the very moment I have most functionality back short of having to reselect my APN at each restart. I don't know specifically what got Mme to this point. Although I used a combination of NV Reader/Writer, Samsung Phone Info+, reinstalling a EFS directory using ODIN, IMEI changer, and a new sim. I also forced the cellular band to auto and set the PNT to LTE/CDMA. Although as I said Im not sure what helped most and even so its not all fixed 100%. Let me know if you want more details how I got to this point.
Crotty.Josh said:
At the very moment I have most functionality back short of having to reselect my APN at each restart. I don't know specifically what got Mme to this point. Although I used a combination of NV Reader/Writer, Samsung Phone Info+, reinstalling a EFS directory using ODIN, IMEI changer, and a new sim. I also forced the cellular to 800Mhz and set the PNT to LTE/CDMA. Although as I said Im not sure what helped most and even so its not all fixed 100%. Let me know if you want more details how I got to this point.
Click to expand...
Click to collapse
Really messed up before and ended up with almost(if not the) the same problem.
I contacted http://www.mobiletechvideos.com/samsung-galaxy-note-2/
And they got me back up and running within minutes.
Just something to check out if you still find youre having issues after you finish trying more.
Take care
I hope you don't mind. I read all your other posting to make sure you were not an advertiser. Awsome feedback BTW. I'm surely going to look into what they have to offer. Sense I have only managed to get so far on my own. I would like to find out they are a company who has the ability to bring it back to out of the box condition. Then I will take the proper steps to ensure I don't make this mistake twice.
My parents both have the VS990 and recently their Wi-Fi calling has stopped receiving calls- calls can still be made (outgoing) but they go straight to VM incoming. My Verizon s7e on the same plan works just fine, leading me to rule out Network and Verizon. What is left is LG and Android (since I'm on N and they're still on MM). It seems that it occurred after the recent vzm upgrade from 27a to 28a. Nobody on Reddit responded to my thread, Verizon has been 0 help (they told my parents it was a SIM issue, swapped their SIM, "tested them" without putting the phones on airplane mode and sent them on the way telling them it was fixed..... thanks guys). I can't find any documentation or bug reports of this happening to anyone else- but, I'm not sure how many ppl depend on wireless calling like we do (satellite is our only method of telecom out here- no phone lines run, no dsl, no cell service.. we're in the middle of nowhere). I've tried resetting the Advanced Calling features. I've restarted the phones. I haven't done a factory reset.
A) Anything I've missed?
B) I found an img for 27a on here, is LGUP a feasible means still of downgrading/rolling-back?
TL;DR: When an MMI command fails, is that the fault of the phone (firmware), phone configuration, or carrier?
Have a LG G6 (unlocked/rooted), activated it on AT&T with no problem. Ported my T-Mo number over, also with no problem. Went to the call-forwarding settings menu to make sure forwarding was set up for Google Voice , and got "call settings error: service unavailable". Following the prompts from GV setup, tried instead the MMI commands ("**004*1<GVnumber>#") and got "call forwarding Connection problem or invalid MMI code".
Hours later- 2 on tech support with AT&T, and another two of scouring the web (and XDA-dev) and nothing seems to help.
Some references to the Pixel 5X simply state it can't be done, and AT&T support needs to set it (and pray it doesn't unset). Others try futzing with the "*#*#4636#*#* " menu, which is handily disabled on my phone. One referenced the APN config screen, and comparing my phone to AT&T's recommended options I made a slight change; still doesn't work but appears to take longer to fail. I've tried swapping between mobile modes (Global/CDMA/GSM), turning off "Enhanced LTE services", finding region.... no help.
Since I can find on AT&T's site the helpful n00b guide FOR THE G6 that shows the phone Call -> More -> Additional Settings menu working, I'm assuming the phone itself is capable, and something is misconfigured... but what?
Can anyone explain how to get more logging, details, or anything that could hint at how to get this to work?
Just wondering if you ever got this resolved? I have same phone same issue.
I eventually got it escalated to a supervisor- from the conversation, far beyond a canned response from a support page. They were very confident that it was a firmware issue- that LG screwed it up. Since I unlocked my bootloader the legit way, I no longer get upgrades.
I bought a One Plus 6 (which has the same sim and feature near parity) so I could use that phone while I flashed a custom ROM or even stock image to try to call AT&T on that bluff.
The good news is with stock firmware (after unlocking/rooting, but no changes otherwise) all the MMS commands work perfectly, as well as the GUI in settings. So... yeah... looks like AT&T's network is in the clear, at least under most circumstances.
Someday I'll get enough time to breathe and flash over this image with the newest upgrades, and hopefully it will work. I just can't speak to if it is in the Radio ROM (which I assume isn't published) or the Android package itself. The more senior folks here may be able to chime in on this.
SomeRandomGuy said:
I eventually got it escalated to a supervisor- from the conversation, far beyond a canned response from a support page. They were very confident that it was a firmware issue- that LG screwed it up. Since I unlocked my bootloader the legit way, I no longer get upgrades.
I bought a One Plus 6 (which has the same sim and feature near parity) so I could use that phone while I flashed a custom ROM or even stock image to try to call AT&T on that bluff.
The good news is with stock firmware (after unlocking/rooting, but no changes otherwise) all the MMS commands work perfectly, as well as the GUI in settings. So... yeah... looks like AT&T's network is in the clear, at least under most circumstances.
Someday I'll get enough time to breathe and flash over this image with the newest upgrades, and hopefully it will work. I just can't speak to if it is in the Radio ROM (which I assume isn't published) or the Android package itself. The more senior folks here may be able to chime in on this.
Click to expand...
Click to collapse
And to be clear, the "work perfectly" was on the OnePlus, not the LG G6. The commands do seem to stick, though, as I can put the sim back in the LG and the call forwarding stuff stays in place.
I'm pretty new to both rooting and this website, so I apologize in advance for any newbie mistakes I'm gonna make.
Background:
I have a VS-996 which frankensteined and unlocked by following this post . After doing that I flashed pie and then flashed lineage os from here . That rom wasn't very stable and kept crashing, so I tried others. I wound up going with Havoc OS. I believe it was in 3.4 when I first flashed it. I've kept up with the updates up to 3.7.
The Problems:
Havoc OS works fine for me, very stable, except for some reason phone calls and messages(both sms and MMS) are spotty at best. Sometimes texts won't send at all, or they'll act like they sent but the text won't be recieved. Sometimes my phone will say I can make emergency calls only. Group messages and sending pictures don't seem to work at all, at any time. These issues seem most prevalent immediately after booting my phone up. Data works perfectly except sometimes when the phone doesn't like to register that the SIM is inserted for a little bit after booting up.
What I've tried:
I've tried reinstalling the rom.
I've tried installing different Android 10 roms.
I've tried going through the process again starting at the the Frankenstein method and going from there.
I've tried messing with the apn
If I flash back to a stock pie ROM everything goes back to working perfectly, and I'm using my sim in my old V20 while I try to sort this out, so I know the SIM is not to blame.
I've been unable to find anybody else with this particular problem, though that could just be because the problems cover so many different aspects that I'm not sure exactly how to search for answers.
Any help is appreciated, thanks.
olliethehobo said:
Havoc OS works fine for me, very stable, except for some reason phone calls and messages(both sms and MMS) are spotty at best. Sometimes texts won't send at all, or they'll act like they sent but the text won't be recieved. Sometimes my phone will say I can make emergency calls only. Group messages and sending pictures don't seem to work at all, at any time. These issues seem most prevalent immediately after booting my phone up. Data works perfectly except sometimes when the phone doesn't like to register that the SIM is inserted for a little bit after booting up.
Click to expand...
Click to collapse
Are you Verizon customer? You say you have VS996.
There's an LOS ROM bug for Verizon SIM card users where upon rebooting the phone you have to make a phone call first to then receive texts. This phone call "registers" the SIM card or whatever. Many people call their voicemail number to satisfy this requirement.
This bug affects all LOS-based ROMs.
Yes I am a verizon customer. I had noticed that making a phone call seemed to help things along when messages wouldn't send. I guess I managed to let my phone die or turn it off enough to hide the fact that it fixed me. Giving it a test just now it seems to be working correctly. I don't know if I'll be happy or mad if the solution turns out to be this simple.
olliethehobo said:
Yes I am a verizon customer. I had noticed that making a phone call seemed to help things along when messages wouldn't send. I guess I managed to let my phone die or turn it off enough to hide the fact that it fixed me. Giving it a test just now it seems to be working correctly. I don't know if I'll be happy or mad if the solution turns out to be this simple.
Click to expand...
Click to collapse
Was noted extensively on LOS-16 ROMs, but not discussed as much with LOS-17 (Android 10) ROMs. But earlier this month someone in the Havoc 3.7 (LOS-17 based) thread did bring it up...
July 9, 2020
https://forum.xda-developers.com/lg-v30/development/rom-havoc-os-3-3-t4062657/page39
XxD34THxX said:
Would anyone happen to know a fix for the having to make a call on verizon to receive incoming calls/text messages-
It's the main thing preventing me from running any android 10 rom. Have an unlocked (True) US998
Click to expand...
Click to collapse
gimpy1 said:
I don't know of a fix, but, I always called my voice mail to get it to work. I haven't been on a custom room for a little while. I assume that still works, though.
Click to expand...
Click to collapse
However, the larger problem is in six months you will not be able to use LOS-based custom ROMs with V30 on Verizon.
* As of December 31, 2020 Verizon is dropping 3G CDMA to repurpose bandwidth for 5G.
After that date, to make any phone calls on Verizon you will need VoLTE. No LOS-based custom ROMs have VoLTE. You will need stock Verizon firmware. It can be rooted stock firmware; you can use Magisk modules to add features -- but needs to be Verizon firmware for VoLTE.
* T-mobile users are in the same predicament.
In January 2021, T-mobile will be dropping 3G HSPA for same reasons. T-mobile users will need VoLTE, which only comes with V30 stock firmware. However, T-mobile is less stingy. They also allow US998 firmware to have VoLTE and Wi-Fi calling with T-mobile SIM. Whereas Verizon requires Verizon stock firmware, and it needs to have been activated on a phone with Verizon IMEI at some point.
* AT&T will also eventually drop 3G HSPA -- but not until February 2022 (18 months from now).
So, for U.S. V30 owners who wish to run custom ROMs a little longer, you should check out AT&T Prepaid. It's a lot cheaper than "regular" AT&T, but is only for people who own their phones.
18 months is a long time. Anything can happen in 18 months!
AT&T only gives VoLTE to AT&T IMEI phones, as well as iPhones and some other phones I would never own. I've never used an AT&T branded phone on AT&T. I'm an AT&T customer with three native US998 for myself, my wife, my mother -- so I'll cross that bridge when I come to it in February 2022. Will probably give my mother an AT&T V35. Maybe my wife, too. Also, LG may get their act together and produce a good phone fro the LG V70 or LG V80.
Any Verizon, T-mobile (and Sprint), and AT&T MVNOs (Straight Talk, Ting, etc.) will also be affected by these decisions.
I have a more extensive discussion of this issue here:
All U.S. V30/V3O+/V30S will need stock firmware, not LOS-based custom ROMs. When?
https://forum.xda-developers.com/lg-v30/how-to/s-v30-v3o-v30s-stock-firmware-los-based-t4138223