LG G6 G600L dialer issues while in roaming - LG G6 Questions and Answers

I've got LG G6 G600L with Android 7. When it's in roaming, two buttons To Korea and To Global appear in the standard Dialer. Moreover, it's impossible to use any USSD commands since symbols * and # become unavailable - "Cannot make a call to number with symbols while roaming. Enter the number without symbols". Using some another dialer changes nothing with numbers with symbols, they are still unavailable. Another unit (H873) doesn't have this second issue in roaming.
I was seeing these issues starting from the factory firmware version till the latest firmware on Android 7. Stopped updating to keep a possibility to return the phone to the shop, but if you know for sure that following updating resolves the issues, I can do it of course.
I would be grateful for any suggestions.

Just for people who might meet this issue - updating to Android 8 solves it: the dialer still has two buttons in rouming but * and # are allowed.

Related

[Q] HELP - Nexus 4 call log issue with international calling card

So bought a Nexus 4. And I am so upset with one major issue with this phone: it's inability to properly record calling card numbers. I dial internationally a lot, and my phone company provided me with an access number. So all my outbound calls look something like this: 1 800 xxx xxxx , 011 xx xxx xxx xxxxx #
Now, if I dial ten different numbers (already stored in my contacts), the call log or history shows only the access number (the 1 800 number) ten times!!! I have tried this on a Samsung Galaxy S3, on a Samsung Galaxy Blaze, and they all have this problem. I also have an HTC One S, and some old HTC MyTouch and they DO NOT have this problem! An older LG Optimus T HAS this issue. What the heck?!?!
I have tried multiple dialers, and none can handle this properly. I have researched forums as much as I could, and it seems that this is a somewhat common issue with Google Voice calls... I have reached to Google and this is what they said:
"I understand you are having an issue using a calling card for international calls and not having them present in your call log. As of right now there is no current workaround for that and I apologize for the inconvenience. We frequently share customer feedback with our development team and will be sure to pass along your input."
and when I asked if this will ever be fixed:
"It is a known issue and there a solution to the problem is currently being worked on. Unfortunately I do not know when a solution will be available so I can't advise you whether it would be a good idea to return the device or not. If I can assist you further please let me know. Once again sorry for the inconvenience."
I fail to understand how this MAJOR FLAW can exist in the phone that promises to put "the world’s information at my fingertips", and yet, it cannot perform something as basic as remembering the very international calls it made...
Is there something I can do? Install? Am I stuck with HTC? Should I thus take a leap of faith and keep the Nexus 4 hoping for a fix to this problem?

[Q] Emergency calls only after baseband change

Hi everyone, noob here.
After installing CM10 on my Motorola defy the system was working almost flawlessly except for one crucial issue: no mobile service. After some major googling and checking up on the settings (IMEI is still valid, along with phone number, even tried to manually put in VPN settings) a thread suggested that I check my baseband settings. To my surprise, it had somehow defaulted to Europe and to some other carrier I hadn't heard of. I then switched it to North America (where I reside) but was confused as I noticed 2 T-mobile settings with some sort of version number next to them. (I run on Walmart family mobile, a branch of T-Mobile) I randomly chose one hoping for the best but sadly, upon restart my defy still remains with no service, but even worse, I'm stuck at the emergency call only screen. Is there any way I can return to the menu to change the baseband setting once more without totally erasing all data and flashing the device?
Well, I decided to repeat the installation process and am now back in CM 10, but even as change the baseband settings to the other T-mobile selections, I still receive no service. Changing the baseband to 'USA T-Mobile 3.4.2-107-9' causes a AT&T network selection to appear, but even selecting that does no good. Is an extra step required to make calls/texts with walmart family mobile on CM10? Does it have to be unlocked or something? I'm very confused.

[Q] LG G2 Automatically Rejecting Calls - Sleep Mode, Call Reject - Disabled

Members,
I've never been a fan of LG and the issues that I'm getting into with G2 seems to be never ending.
The most nerving one is this:
Complete factory reset and use phone for 10-15hrs
Then calls would automatically start getting rejected
Quiet Mode is switched off, Block Incoming Calls is disabled
Call Reject is Turned off
Still when the number is called, the phone's display would come up, but there won't be any notification. The call would get rejected after 1 ring.
No 3rd party application is installed, heck, even Google account is not configured.
Anyone in the same boat or any advise to solve this?
Tx
I am also facing the same issue. I am completely stock, rooted.
Problem Solution?
I am also having the issue. Did you find the solution?
Same problem here
After first unlock LG LS980, it shows vodafone network and all working fine. But Data Connection was not running. After then doing some tweaks and installing some patches and resetting and adding VPN, etc.. It shows Data Connection. Now Data Connection is working perfectly but all incoming calls are rejected automtically.
Have you found any solution?
If any one can help then would appreciate a lot..
Thanks.
Same probelm
I have an LG G2 D802 32GB from Germany. Installed custom ROM and then flashed to the stock ROM. Then I found out that there is 10GB only. Tried your method and flashed by LG Mobile Support Tool to Android 5 from 4.4.2. Still 10 GB. I don't think that deleting 2 partitions (there was a post who fixed it by this) will be a good idea.

[Q] Need help - Unlocked Japanese Note 3 no longer works!

Hi All,
Please help. I'm a rookie at rooting and have an unlocked Japanese Note 3 through AU (my Japanese service provider). I was in a rush and paid someone to unlock it before heading back to the States last year. The phone works with my AT&T sim card but when I am back in Japan (with Japanese sim) I am constantly being dropped from the network. 4G service usually works for internet, etc, but I cannot make/receive phone calls and only occasionally can send/receive text messages. I need to know if I should re-root the phone (and leave it rooted) or just do a factory reset (or perhaps change some other setting to get things working again)? The problem with a factory reset is that it will probably re-lock the phone and I don't have a code.
Strange Detail:
Whenever I try to dial a number, the name of a Chinese Province shows up under the Contact's Name. This suggested to me some network issue where the phone somehow thinks it's in China (though texts still kinda work...) and doesn't connect correctly to the Japanese network.
Details:
Model: sm-N900J (per the download screen) i believe this means it has a SnapDragon Processor
Knox warranty has been tripped (apparently by the guy I paid to unlock it originally - is that bad?)
Android 4.3 (looks like I'm still in the original version of Jellybean. Should I upgrade to Kitkat or Lollipop?)
Other Issues:
As of two days ago, the phone now restarts after about 5 minutes of use. Like many Note 3 phones, it's always done the occasional random restart (another reason to root?) but now it's making the phone almost unusable. Also, since having the phone rooted/unlocked/re-rooted I always get a series of warnings upon start-up. Typically, standard Samsung apps like S Planner, Calendar Storage, Keyguard and Index Service have stopped. I have never been able to use the Calendar (or other basic apps) since it always crashes. Is this an issue with Knox clashing with something from the original root (I still see SuperSU loaded -but "turned off"- in the apps menu)?
Idealy...
...someone can help me decide the best course of action (Root, Reset, Other), and how to make sure I can connect back up to my Japanese network properly. I think I'd prefer to root since what I want is an unlocked phone that works smoothly, with good battery life, little to no bloatware, a custom theme and a working S pen. If I root, what's the best method (already have SuperSU apparently) and which ROM and version of Android would be the most stable?
Main Issues Recap:
No connection to phone network (or limited 4G internet).
Phone restarts every few minutes.
Many Apps crash upon Start-up.
Thanks in advance!
So, here's an update that someone with a similar problem might find useful...
Japan uses CDMA for voice and GSM for LTE Data. Somehow (probably through using my phone in the states on a GSM network) the phone was no longer connecting to the CDMA network. Since I'd gotten no responses and felt like there was a good chance that a factory reset would not reverse the sim-unlock I'd stupidly paid to have done, I did a factory reset. Despite appearing to have solved my Index Service, Calendar Storage, S Planner crashing issues, I was still having the exact same problem of LTE working but no CDMA network.
Somehow I stumbled on to this website...(well, I'm unable to post as a new user but searching for "How To Fix Samsung Galaxy error while searching for network" should bring it up).
There, I found some really odd directions that solve network error issues. The only part of the instructions I was really able to carry out was take out the battery and simultaneously press the home and power buttons 10 times. I restarted my phone and miraculously was able to place a call for the first time in a year in Japan!
But then I no longer had any data. I figured it had to do with the APN settings being wiped in the strange reset I just tried. But when I went into Settings>More Networks>Mobile Networks there was no longer an Access Point Names option in the menu. There is no longer a "Network Mode" option either. I used to have that set to LTE/WCDMA/GSM but now I only see a System Select option that simply lets me change my CDMA roaming mode from Automatic to Home Only.
I tried searching everywhere for the missing Access Point Names menu to no avail (and almost attempted to try flashing CyanogenMod for the time hoping this would bring back the APN settings menu) but then I realized that I could do a search in the settings app. I searched APN and the option came right up (though it's frustrating that this now appears to be hidden). Using the following settings (copied below) from the AU by KDDI website I created a new APN profile. Now mobile date appears to be working just fine too!
So, now I just need to decide if I want to keep running Touchwiz in Jellybean or use my new found confidence to try rooting and custom roms...
I'm also kind of curious to see that the next phone bill comes in as expected and I'm not being charged for a bunch of crazy usage! Also, any suggestions to help explain how I got into this problem in the first place, or how to clean up any loose ends would be appreciated.
APN Setting for LTE NET for DATA
APN name au.au-net.ne.jp
User name [email protected]
Password au
Authentication type CHAP

G935V on Android N 7.0 issues with receiving calls/texts [Total Wireless]

I have been going through a weird issue on Total Wireless. When I use Android 6.0.1 and below, I have no issues with my service at all, everything works as it should. The issue comes into play when I use any Android 7.0 ROM, be it official or custom. Outgoing calls/4G data are fine, but I cannot receive any phone calls or send/receive texts. The only way for me to be able to receive calls and send/receive texts is to dial out once. After this, everything works as it should, that is until I reboot. Then I it goes back to the partial working state until I dial out again.
The issue persists whether I am using CDMA/LTE or Global Network modes. I have tried every single possible combination of starting with a fully working 6.0.1 firmware and upgrading through Smartswitch, with and without a full Wipe performed afterwards, doing a full 7.0 firmware flash. The issue is always present, and I am not sure if TW has issues with Android 7.0 or if there is a problem with my account. Their CS is absolutely useless in helping me with the issue, and our chats always end with if I can make a phone call, then the issue is resolved. They don't understand that the issue is still present, but it only crops up after a reboot of my device.
I have tried 3 different SIM cards and they have deleted and re-added/reprovisioned my device/number to their system but nothing seems to help this issue. APN is the usual TRACFONE.VZWENTP. It's really weird that it happens on two separate devices that I activate with my mobile number.
My only thought as to what it could be is maybe some weird provisioning error with the number coming from Verizon. Total Wireless doesn't have any type of VOLTE capabilities on their network, yet I was able to use a rooted Note 4 device and activate Advanced Calling/HD Voice and I believe Wifi calling as well and use it fine on their service. One oddity I noticed is that when the phone is in the initial 'Searching for Service' state on a fresh boot when I dial out while connected to Wifi, sometimes I will see Mobile Network Type change to IWLAN, whereas it usually says LTE. After dialing everything works correctly.
Any ideas on further troubleshooting steps I can take? If nothing can be done, maybe there is some way I can have a boot up script that makes a ghost phone call to any random number and immediately disconnects so I don't have to remember to dial out whenever I reboot my device?
Thanks
I don't have a solution yet, but you're not alone. I have a stock G935V (running Nougat) with Tracfone service running over Verizon's network. Whenever I start up the phone, the phone will indefinitely remain in a "Searching for Service" status until I initiate one phone call. Then the network instantly switches to "Verizon Wireless" and everything works correctly for as long as the phone remains on.
A long phone call with Tracfone and Verizon yielded no solution: They indicated everything is configured correctly in my account. Various replacement SIM cards didn't change anything either.
This issue happens with both stock Samsung S6 phones and the Samsung S7 phone in my household. All are running Nougat.
Any update here? My girlfriend's phone has the same issue since moving from Verizon to StraightTalk.
dbldown7 said:
Any update here? My girlfriend's phone has the same issue since moving from Verizon to StraightTalk.
Click to expand...
Click to collapse
Tracfone tried, half-heartedly, to solve the problem by sending me 3 different sim cards. The problem never went away. I just got in the habit of initiating a call to voicemail whenever I restarted my phone.
The problem went away when I upgraded my S7 Edge to Android v8 Oreo.
I have flashed the Nougat "U" firmware on my Verizon S7 Edge. I had VoLTE, hotspot, HD voice when calling someone on Verizon (but the HD symbol doesn't show on my dialer, only on theirs).
Only issue was that. when I introduced the TW SIM, the APN was auto set for Tracfone (and it wasn't working), so I had to manually change it to the TotalWireless one.
Since then I had received the Oreo upgrade and the following security update... and it's still OK.

Categories

Resources