After getting android 12, I have no notification sounds. More specifically, I have no notification sounds through the phones speaker. I have sounds through the headphone jack and over Bluetooth. If I go into the sounds settings, I can change my ring tone and hear it, but there's no sound when I change my notification sound. I did a hard reset this morning and when my phone was "factory new" there was still no sound. If only I could find someone to revert my phone back to 11. google only makes the world worse.
You don't mention what version/carrier is your V60. If it is T-Mobile/US Cellular then you could easily download the relevant firmware for Android 11 and flash it using LGUP. You should use partition download mode.
Royaltiger said:
You don't mention what version/carrier is your V60. If it is T-Mobile/US Cellular then you could easily download the relevant firmware for Android 11 and flash it using LGUP. You should use partition download mode.
Click to expand...
Click to collapse
It's an "unlocked" phone that shows the T-Mobile logo when I turn it on. I'm using Mint Mobile for my service, not that that matters.
So you're saying that I can just download android 11 and reinstall it? Which one should I get... the last "Android 11 R" or the last "Unknown"? Do I need the "LGUP Store Frame"? I'm definitely going to be looking into this.
Thanks
Here is the problem in your case:
Since you are using the MVNO (i.e., Mint Mobile), none of the T-Mobile firmware will work. The reason is that even if you are on the T-Mobile network (via Mint Mobile) the functional operating bands are different assigned. So the firmware that you are seeing for T-Mobile are only for the individuals who are direct subscribers of the network not the ones who are MVNO.
You could give it a try but if you flash the T-Mobile firmware on your phone and if it does not work then you are in a nightmare. Because you will need the Mint Mobile firmware to re-flash your V60 in order for it to work on their network. And as far as I know, there is no firmware provided by MVNOs publicly.
I thought that link you sent was just a generic LG firmware. So who's to blame for my phone being worthless then... LG, T-Mobile or Mint? This is why I generally hate technology. Someone comes out with an "update" that completely screws me over. I can't go back and their response is "Sucks to be you".
I totally understand your frustration. MVNOs don’t inform their customers all the detail. They just push their lower prices trapping their customers. I am not saying that they are deceptive but simply that they are not as transparent. And they just don’t give their customers all the options.
May I suggest that you go to a Mint mobile store and inform them your problem? If they have a technically informed person there, your problem could be fixed.
To console you, here is a problem that was posted here relating to MVNO. Audio was an issue there as well but from microphone.
To answer your earlier question, if you have to use a firmware it will be the ones marked for T-Mobile. Please don’t use the ones marked “unknown”.
Thanks for your patience and responding. How do I know if the firmware from that link is for T-Mobile? Because of the TM in the number? The software version on my phone is V600TM30e. It's the security patch from September 1st. It doesn't say anything about it being for T-Mobile when I click on the last Android 11R firmare.
EDIT: Sorry. It says it's for U.S. Cellular in the description.
I don't understand how Mint factors into this. They aren't the ones providing the updates. I assumed they came from LG.
I have a timer app that, when the timer goes off, the alarm works. This makes me assume it's a purely OS problem. Have you heard of a ring tone app that overrides the system sound the way that timer app does? I'm going to see if such a thing exists. Even if it costs money, it's would be cheaper than having to buy a whole new phone because of a garbage update. And I don't see LG ever fixing the problem as they've stepped out of the phone market.
Actually Android updates have not been satisfactory for many people. I had initially Android 10 that updated to 11. All kind of problems started happening (including battery drain and band allocation). So I went back to Android 10 and things were back to normal. When Android 12 rolled in, I tried it and found it to be better than 11 but still buggy. So I am again on Android 10 and staying here.
I am glad to learn that your phone was working well on Android 11. In terms of your ringer not working, here are possible scenarios:
1. Please check if your phone is in do not disturb mode.
2. See if your ringer‘s volume is mute.
3. If you change the ring tone, does the phone ring to give you a sample?
4. Have you installed any modded application (like Dolby Atmos, DTS etc.) that do interfere with ringer many times.
5. Please try these ringtones that are here. See if these work.
6. I am going do some research to find a solution.
As for the firmware, if you look at the list the T-Mobile ones are labeled TMO in the first column.
The firmwares are originally written by LG but given to various carriers who customize it to their phones and operating bands. So Mint Mobile operates on a pre-allocated band by T-Mobile. Now T-Mobile does not put its direct subscribers on those bands/frequencies. Hence the T-Mobile firmware does not include the Mint mobile bands or frequencies.
If you do flash a T-Mobile firmware, for example, your phone will be fine but the modem may not operate as it will be looking for T-Mobil network bands not Mint mobile. That’s the arrangement that MVNOs have with their carrier partners to protect each other from customer defection. In other words, if you go to the carrier directly you get better service and option albeit higher price. And if you go to MVNO, price is lower but you sacrifice service options.
With 11 everything worked great. For me a phone is just a music / podcast / audiobook player that people can reach me on. I guess they still can. I just don't know it.
For the possible scenarios...
1. It's not in do not disturb mode.
2. It's not muted.
3. Yes. If I pick a ring tone, it will play play it. But not when the phone actually rings. When the phone "rings" it does vibrate and the light on the phone starts flashing. However, if I pick a different notification sound, it makes no noise at all.
4. I haven't installed any modded modded audio effects. I have several players installed, not that that should matter. Just to see, I ejected my 1TB card to see if that was somehow a problem. It's not, and I'm really grasping for straws with that one.
5. All of those ring tones play.
Your explanation of firmwares makes sense. I guess that's why Mint requires you to have an unlocked phone. So whose version of android 12 do I have? LG's, or T-Mobiles modified version of LG's modified for T-Mobile modified for Mint?
The firmware that you have was initially written by Google then customized by LG. LG directly submitted that to Mint Mobile (or via T-Mobile) who further customized that to their specifications.
Try to boot your phone in safe mode and see if it rings.
PROCEDURE:
1. Hold the power button on the phone till the option to power off/restart appears.
2. Press the power off (on the screen) and keep it pressed till "boot into safe mode" appears.
3. Choose "Turn on" to restart the phone in Safe mode.
4. When the phone restarts you will see the "safe mode" on the screen.
5. Now try to make a call to your phone to see if it rings.
Please make sure bluetooth is off.
DO THIS AFTER ABOVE PROCEDURE:
Take your SIM card out and replace it with a different active sim card (if you have one). See if your phone rings with the new sim card when in normal mode (not safe mode).
Let us know the result of both events.
I've tried starting in safe mode a couple of times already. Nothing. When my phone is connected to a portable speaker via the headphone jack, I can hear notification sounds when I change it. The same for when I'm using Bluetooth headphones.
I was thinking of other things that might have caused the problem, and you might be pretty upset that I'm just mentioning this now. Over the summer I had dropped my phone and it was no longer able to be charged unless I was using a high speed charger. I brought it to a shop in my town and the guy replaced the little circuit board the charging port is on, as well as the battery. But I'd swear I still had system sounds through the speaker after that. For the life of me I couldn't say if that was before or after I got 12.
Since you don’t have ringer working even in safe mode, it is highly unlikely that it is a software issue. I am leaning towards hardware problem. That’s why I suggested using a different sim card in your V60. SIM cards also create the exact same problem.
I had assumed the opposite. That since I couldn't hear the notification sounds in the settings, even after do a full factory reset, that it was a software problem. The fact that I can hear all other audio out of the speaker, except the system sounds further made me think that. The ringer it very odd to me. I can hear it when I change ring tones, but not when the phone rings. All of thing made me think it was a driver problem.
I don't have another sim card I'm afraid. Could I put in someone else's from a different phone and a different carrier?
Do you think that new charging port could be a problem?
I am not ruling out the Android 12 as the culprit but since we don’t have the access to Mint mobile firmware, there is only that much we can do. You can use a SIM card from a different carrier as long as your V60 is unlocked to other carriers. Have you tried taking your SIM card out and reinstalling it after two minutes?
DO THE FOLLOWING:
1. On your phone, dial *#546368#*600#
2. It will give you some options.
3. Choose “Device test”.
4. Then choose “SAAT”.
5. Now choose “Service menu — Manual test”.
6. From there choose “Ring test”.
What happens?
From the above screen, you could choose “SVC Menu” and then choose “Factory Reset”. That will try to hard reset your phone. Could solve your problem but it will wipe out all your data. So make sure you have a backup of data.
I already did a hard reset Friday morning. It started installing my backup right away, so I went into settings as soon as I could, and it made no noise changing the notification sound.
I ran that ring test and there was sound. Does that mean anything?
I'll try pulling my sim card out in a little bit. I have nothing to push it out with. Remember how bad it was when you could just push it in to pop it out? Progress!
Thanks for all of your help so far.
I turned off the phone, ejected the sim card and turned the phone back on without it. No notification sounds. I turned the phone back off and waited 2 minutes, put the card back in and turned it on. No sound. Touch sounds works though. I hear a click everytime I touch the screen. It also makes a noise when I plug it in to charge it.
Try installing Disable Headphone Fix Earphone app.
See if the solution suggested by engage4 above works. If not, let me recap where you stand.
You have an LG V60 phone T-Mobile variant. Although the phone is for T-Mobile, you decided to signup with Mint Mobile. You did not buy the phone from Mint. So after signing up, you got the sim card of Mint Mobile. And your phone was working fine. It was on Android 11 before you got Mint Mobile.
Then Mint pushed an update to Android 12. Since the update, the ringer is not working. Am I getting it right?
I am going to get a Mint Mobile sim card from a friend and see if my Android 10 T-Mobile V60 works fine (with configured bands). If it does, then you can absolutely flash an Android 11 firmware (of T-Mobile) on your phone. Problem solved.
Related
Hey all I was given an Eris by a friend so I rooted it easy enough at 1.5 last August. Since then I have had a few different custom roms loaded and everyone of them that I tried to activate the phone on didn't work. This phone was not activated when I rooted it, and I have to take it to my local verizon shop to have them try to activate it after they deactivate my moto droid 1. I' ve been digging for awhile now trying to figure out if it's the baseband version or what. Can someone please help if at all possible.
Current phone info:
Firmware: 2.1
Baseband: 2.42.01.04.27
Kernel: 2.6.29,
Build: 2.36.605.1 case release-keys
Software 2.36.605.1
Browser WebKit 3.1
PRI: 2.11_002
PRL: 58003
ERI: 5
When the phone boots it shows the verizon logo which doesn't completely mean the radio is flashed for versions network, but I have no idea how to tell otherwise.
Thanks.
If you activate the phone with a stock, or near-stock ROM (let's say Ivanmmj's "Official 1.0"), then thereafter, nothing you do to the phone with dev ROMs from this site will change the phone's activation data (stored in the phone) afterward - not flashing a different radio, nor performing a "wipe/factory reset" (in Amon_RA), nor installing a different ROM will change that.
When it comes to deactivating the phone - or more precisely, clearing the activation state of the phone, the only thing that seems to accomplish that is one of the factory recoveries - Amon_RA does not touch it. This happens if you perform a "factory reset" in the regular OS, which actually causes a boot to the recovery, which does all the "dirty work". You can also manually boot the stock recovery, and use the wipe menu to achieve the same result.
You can see that this makes de-activation inconvenient for rooters - but most of them don't need to do that.
So I'm reluctant to conclude that the radio firmware is affecting your result.
What happens when you try dialing *228 option 1? The call goes through, but you get an error voice announcement after some delay?
I was under the impression that people that flip back and forth between two phones on the same service don't ever bother to de-activate the phone in use: they just make sure that current phone is turned off before they attempt to activate the next phone.
I suppose you could restore the phone back to complete stock (including the stock recovery) before activating it, and then re-root it and reload a nandroid backup... but that's sort of a pain in the neck if this is something you plan on doing regularly.
bftb0
PS I could swear I have activated my phone (*228 option 1) with a dev ROM on the phone, but don't remember the specific details.
First off thanks for the quick reply. I've been researching this whole time and when I dial *228 I don't even get prompt to pick an option. This tells me that somehow the radio itself is possible damaged. Is there anyway a rom could damage it? I ask knowing it's highly unlikely... I know the phone worked fine up to the release of the droid x when the friend upgraded to it. And all I've done is rooted and flashed, so I'm curious, can I test the radio at all?
Thanks.
RnkG said:
First off thanks for the quick reply. I've been researching this whole time and when I dial *228 I don't even get prompt to pick an option. This tells me that somehow the radio itself is possible damaged. Is there anyway a rom could damage it? I ask knowing it's highly unlikely... I know the phone worked fine up to the release of the droid x when the friend upgraded to it. And all I've done is rooted and flashed, so I'm curious, can I test the radio at all?
Thanks.
Click to expand...
Click to collapse
I just re-read your initial post and actually can't tell if the phone has ever been successfully activated since you received it. You mentioned taking it in to the Verizon store, but you didn't say what the outcome was - was the Verizon store unable to activate it?
Normally when you dial *228 it just sounds like a normal voice call - you hear audio, the recorded lady's voice provides a menu, etc. Since that needs to happen in order to activate the phone, it is fairly obvious that the cellular radio must be working completely for that to happen - so the fact that you don't hear any audio seems to indicate something is wrong.
Why don't you try and reflash the phone back to stock using the download from this thread which also flashes the radio:
[ROM][10/20/2010]FlashBack21 v1 -Return to Factory Stock - UPDATED
And see if that gets you any different result. That would eliminate any effect of "dev" software, and also reflashes the radio with the July 2010 version - the last one officially shipped by VZW/HTC for the Eris. If you can't get audio (and you are sure from playing music that there isn't a speaker problem), that would point to a hardware problem.
BTW - even if the phone is working completely, VZW needs to already be aware that it's ESN/MEID is associated to your account, and I think that your other phone needs to be turned off at the time you attempt activation.
cheers
Thanks again. I'll work through that and then post back here.
Thanks again!
So I followed the simple to use guide as directed and everything flashed just fine. When when I got to the activate screen I tried to activate and when it dialed the number I hear nothing. So I turned the speaker on and hit number on the dial pad to make sure the volume is working and it appears to, but it doesn't make the ringing sound when you normally call a number. Soooooo as a desperate act to see if the radio was working what so ever I did something crazy... dialed 911, and I heard it ring one time, then hung up and pulled the battery. So i think the radio works fine in it, I'm going to go to the verizon store and have them try and activate it again.
Thanks a million for all of your help! I really, really appreciate it!
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
RnkG said:
So I followed the simple to use guide as directed and everything flashed just fine. When when I got to the activate screen I tried to activate and when it dialed the number I hear nothing. So I turned the speaker on and hit number on the dial pad to make sure the volume is working and it appears to, but it doesn't make the ringing sound when you normally call a number. Soooooo as a desperate act to see if the radio was working what so ever I did something crazy... dialed 911, and I heard it ring one time, then hung up and pulled the battery. So i think the radio works fine in it, I'm going to go to the verizon store and have them try and activate it again.
Thanks a million for all of your help! I really, really appreciate it!
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
Click to expand...
Click to collapse
If they activated it I don't know how they could be blocking it. I would've checked to see if it was working before I left the store, and when it wasn't, would've brought this issue up with them.
Are you just going by their word that they activated it, or is there some other way you can tell that it's activated, even though you're not getting any service? What I mean is, if you're not getting any service, how can you be sure they activated it successfully?
RnkG said:
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
Click to expand...
Click to collapse
Other than bad hardware, the only thing which would cause this problem would be a "blacklisted ESN" - that would usually be a stolen phone, or a phone that was on a Verizon account that was abandoned by the subscriber with an unpaid balance. (Verizon doesn't want customers who cheat them to continue to cheat them by habitually opening new accounts under assumed identities, so they just blacklist the ESNs of phones that were used on abandoned accounts with unpaid balances)
Verizon won't activate phones with blacklisted ESNs - but if you walked in the phone store and asked them to activate it for you, I would presume that they would have told you straight up "We can't/won't activate this phone".
The radio does not use a separate technology for 911 calls, so, yeah - there is something odd going on here. Perhaps you had a "green" VZW customer assistant that isn't familiar with what happens when someone wants to activate a blacklisted phone, and simply didn't take notice when "something unusual" popped up on the computer they used to enter in your activation request.
You've got stock software on the phone now, so I wouldn't hesitate to pick their brains about it. Telling a VZW tech about the 911 call might convince them a little better - but just remember that you are admitting to a criminal activity (calling 911 without due cause).
Also - bear in mind that by law (in the US) every cell phone has an aGPS unit in it, precisely for the purpose of emergency services locating a cellular handset when the user is incapacitated. ( There is a small risk that if you make a 911 call, cops will end up at your door even if you hang up.)
When I make a call I can hear the person on the other end perfectly, but they either say they cant hear me or that they can but just barely. I called several friends, same results. It's not a volume issue, everything is maxed, I'm not one of those idiots who wonders why TV wont turn on but it isnt plugged in.
I first had this issue on @AndyZhang's 20L ROM. So I tried Eliminater74 20L instead. Same issue. After that I tried @tungkick's 20L rooted TOT. Same issue.
My phone is a T-Mo v10, but I'm SIM-unlocked and my current carrier is MetroPCS. This didnt start until yesterday. Internet and texting work, I dont make calls often, so I didnt immediately notice.
What else I've tried:
1. Changing APNs (including setting the MetroPCS APN that I know to be correct, as provided by their in-store support reps awhile back)
2. Turning Volte on/off
3. Changing Network Mode in Settings > More > Mobile Networks.
I'm going to try flashing a KDZ next but I'm all out of ideas for now.
I just finished reflashing a stock KDZ. No root, Xposed, nothing. Just pure stock. Same results as before. I'm beginning to think this is either a carrier issue, or worse, my mic is maybe defective. Everything else works fine, including the speakers. So this basically makes my phone useless for calls, but good for everything else. Although I do now wonder now if my phone is going to die soon.
I did buy insurance when I got the phone from a T-Mo store, but since I'm no longer a customer, can I still use the insurance to get a replacement v10? I did have to pay extra money for it, so I figure they should let me cash in regardless of customer status.
Worst comes to worst, I'll just throw this in the trash, and go buy the v20.
Thanks for any advice!
Edit: Apparently my mic does work, just tested with Google App/Voice Search and it detects my words instantly. Saying "OK Google" seems to work too, regardless of whether screen is on or off. Now I'm really stumped.
More info: Apparently people can hear me fine if I turn on speakerphone during a call, although I almost have to yell. But if I turn it off, they immediately report not being able to hear me. This is really strange, never experienced anything like this before.
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 have an Samsung S9 Plus that was an AT&T unit (I think) and I flashed it over to the global firmware so I could use it on Visible (Verizon). It has been working for months, but I have now had this problem happen twice. I get up on a Monday, and notice that my phone has no service. I think it says "No Network Connection" or something like that. The first time I tried many of the usual steps - switching airplane mode, resetting network, wiping the cache, long support chats with Visible. What finally got it working again was putting in another sim(from Red Pocket - AT&T). That made the phone go through a reboot to swap over to the new sim. Then I put the old Visible sim back in. The phone does another reboot, and now everything is working again.
Is there a way that I can get the phone to go through this process without swapping the sims? I would just like to know if there is a more efficient way of fixing this problem when it pops up.
Phone info
SM-G965UA
Android 10
brotherhaslip said:
I have an Samsung S9 Plus that was an AT&T unit (I think) and I flashed it over to the global firmware so I could use it on Visible (Verizon). It has been working for months, but I have now had this problem happen twice. I get up on a Monday, and notice that my phone has no service. I think it says "No Network Connection" or something like that. The first time I tried many of the usual steps - switching airplane mode, resetting network, wiping the cache, long support chats with Visible. What finally got it working again was putting in another sim(from Red Pocket - AT&T). That made the phone go through a reboot to swap over to the new sim. Then I put the old Visible sim back in. The phone does another reboot, and now everything is working again.
Is there a way that I can get the phone to go through this process without swapping the sims? I would just like to know if there is a more efficient way of fixing this problem when it pops up.
Phone info
SM-G965UA
Android 10
Click to expand...
Click to collapse
Call your carrier and have them to a reprovision. I had this happen with T-mobile coming from Sprint.. They will have you turn off the phone, do something on their end, and after that it should work.
Just to update, I have switched over to ATT Prepaid. Since the change, I have not had the problem happen. I think it must have been an issue with Red Pocket. Either that or something that got fixed with an update. Just putting these data points out there for anyone else that is having issues like this.
Hello!
Can someone please help me with this?
Everything was fine until 2-3 days ago. When all of a sudden I was unable to send text messages or make phone calls. All the while I could access internet without any issues.
If I switch to 2G or EDGE for the Subnetwork, I can make calls and send SMS.
How can I fix this?
Could dropping the phone have caused this?
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
schwinn8 said:
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
Click to expand...
Click to collapse
Carrier texts should theoretically still work as they are "data". It's the "voice" part of VoLTE that won't work. That's why I can still receive carrier texts on my Galaxy Note 9 with AT&T -- which still has older firmware (so I can be rooted). A few months ago, I lost the ability to make/receive phone calls on my AT&T number when 3G towers were decommissioned in my area... But luckily I have Google Voice number, which also uses "data" (VoIP) so I make/receive all my Google Voice phone calls. (That's been my main phone number for years.)
However, I no longer can make/receive AT&T phone number calls -- which is fine. I switched Google Voice settings to data/Wi-Fi only instead of piggy backing on carrier phone number. Yet, I still receive AT&T texts, which is good because my bank insists on using a "real" (carrier) phone number for SMS security code confirmation.
Amer28 said:
Hello!
Can someone please help me with this?
Everything was fine until 2-3 days ago. When all of a sudden I was unable to send text messages or make phone calls. All the while I could access internet without any issues.
If I switch to 2G or EDGE for the Subnetwork, I can make calls and send SMS.
How can I fix this?
Could dropping the phone have caused this?
Click to expand...
Click to collapse
You are in Portland? What carrier are you using that still has 2G and Edge?
ChazzMatt said:
You are in Portland? What carrier are you using that still has 2G and Edge?
Click to expand...
Click to collapse
I'm with a company that uses T-Mobile towers. I connect just fine with 4G LTE, and get reasonably good speeds over it. But when I'm on 4G, I cannot make or receive calls or text. It says Emergency Calls Only.
So far, I've tried everything. I resettled network. I looked for different APN values that may fix the issue. When I couldn't think of anything else, I did a factory reset. (I mean, I wiped Data, and all other partitions in TWRP except for System and SD Card.) There have been no changes.
I'm starting to think the issue may be hardware, I did drop the phone a couple of times the day it stopped working. Though I usually end up dropping the phone once a day or every two days. I can't believe the screen hasn't cracked yet, at all. Could a drop from 3-4 feet on hard surface like tiles damage the antenna in such a way that only 4G data works?
I'm ready to give up and buy a new phone even though I can't really afford it. It would be awesome if I can get this to work.
schwinn8 said:
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
Click to expand...
Click to collapse
I'm on T-Mobile towers with the US998. I don't think there is an issue with IMEI. How would I connect to data with 4G if that was the case?
I never had Volte on this phone. I do recall seeing it when I first got it but I'm running stock rooted Android 9.
When I say it used to work a few days ago, I mean it just stopped working at one point. I wanted to make a phone call, and all of a sudden, I couldn't. I noticed then that it says Emergency Only sign, so I walked around the house for about 15 mins to try to get signal. Then I went to my car and drove around, but nothing.
I messed around with Network settings, and figured out that Voice and TXT worked when I switch to a lower 'Sub-Network' setting that says, "GSM / GSPR / EDGE Only".
To get 4G Data back, I have to switch it back to "LTE/Legacy 3GPP multi"
These two are found under "GSM/UMTS Settings", after clicking on "System Select" in "Mobile Networks ".
I want to also mention that my carrier website has been talking about a data migration that would affect phones using their old SIM Card.
When I saw that, I called them and had them send me a new SIM. I thought surely this must be it, but the new SIM works exactly like the old one.
Perhaps the migration or whatever it is they did that required new SIM cards just doesn't work well with my phone? Even though, before putting the order in, the rep I spoke to did check my IMEI and said that my phone is compatible.
Agreed, it doesn't sound like an IMEI issue.
FWIW, I showed a 4G connection on a phone (I don't remember if it was my V30 or a Galaxy S10+ that I was going to replace it with). On that phone, at one point, but there was no actual connection. So, the indicators aren't always accurate. That's why I thought maybe the data isn't really working, and if data isn't working then VOLTE won't work... and with many of the carriers switching off non-VOLTE calling, that could kill the ability to make calls?
In your case, you said data worked... but if VOLTE was never enabled, and the carrier dropped non-VOLTE, then, again, you may lose calling.
In any case, these were my theories. I think you're on top of the situation but I don't have any other ideas for you to try...
Instead of buying a new phone, have you considered installing and setting up Google Voice, as ChazzMatt said? I recently had to do that because AT&T's 3G shutdown meant that I could no longer place or receive calls. My quick guide on doing that is here: https://forum.xda-developers.com/t/...-based-custom-roms-when.4138223/post-87342453
I don't know why you can't also send or receive texts, but the Google Voice app has the ability to do that, so maybe try using that after you've set it up.
Amer28 said:
I'm on T-Mobile towers with the US998. I don't think there is an issue with IMEI. How would I connect to data with 4G if that was the case?
I never had Volte on this phone. I do recall seeing it when I first got it but I'm running stock rooted Android 9.
When I say it used to work a few days ago, I mean it just stopped working at one point. I wanted to make a phone call, and all of a sudden, I couldn't. I noticed then that it says Emergency Only sign, so I walked around the house for about 15 mins to try to get signal. Then I went to my car and drove around, but nothing.
I messed around with Network settings, and figured out that Voice and TXT worked when I switch to a lower 'Sub-Network' setting that says, "GSM / GSPR / EDGE Only".
To get 4G Data back, I have to switch it back to "LTE/Legacy 3GPP multi"
These two are found under "GSM/UMTS Settings", after clicking on "System Select" in "Mobile Networks ".
Click to expand...
Click to collapse
There's been reports T-Mobile which is now merged with Sprint has borked the ability for VoLTE/VoWiFi calling on US998 firmware phones (native or Frankenstein'ed). Apparently they only allow it now on T-Mobile H932, whereas pre merger they were happy to give VoLTE and voWi-Fi calling to "US998" phones
First, it was reported with new SIM cards they were distributing earlier this year. Then people who kept their old SIM cards found they didn't work after a forced "security update."
This seems to have also trickled down to the T-Mobile MVNOs.
This is why we told someone else recently they should probably convert their phone from US998 on T-Mobile to Verizon VS996 firmware.
Then get a Verizon sim card or Verizon MVNO SIM card, and activate it in an old cracked screen Verizon phone off eBay, then put that already-activated SIM card into their "VS996" V30.
They will have VoLTE and VoWi-Fi calling.
Alternatively, if you really want to stick with T-Mobile network, you can do what @osprey00 suggested -- which is get a Google Voice number and use it as a tool to forward your carrier calls to it.
You can read his post, see his experiences, and see if this would apply to you.
For ME -- I've been using Google Voice for the past 10 years as my main phone number. I ported my carrier phone number at the time to Google Voice. Then got throwaway carrier numbers (whoever had cheapest plan) but never gave those to my friends. To my friends nothing ever changed. I've had the same "number" for the past two decades.
But within the past couple years, I had to start giving my bank and my cable company my carrier phone number for SMS security codes. Very annoying, because in the past they used my Google Voice number to text me with no problem.
So, even though under my current firmware (on my rooted Note 9) I cannot get carrier phone calls, I still have LTE data. And with the LTE data, I can use Google Voice (calls and texts) because it's VoIP. I also get AT&t carrier texts, as that is also data. It's just AT&T phone calls I cannot send or receive.
AT&T deactivated the SIM card in my native US998 V30+ and sent me a replacement phone, which is a Samsung Note 9. I'm staying with AT&T for a reason. Otherwise I would probably pull the "V30" Verizon trick also.
I bought both my wife and my elderly mother 64GB V35 phones -- which is basically an upgraded 64GB V30. (They previously had native US998 V30.) AT&T gives V35 VoLTE and WiFi calling, and for them there was nothing new to learn.
ChazzMatt said:
There's been reports T-Mobile which is now merged with Sprint has borked the ability for VoLTE/VoWiFi calling on US998 firmware phones (native or Frankenstein'ed). Apparently they only allow it now on T-Mobile H932, whereas pre merger they were happy to give VoLTE and voWi-Fi calling to "US998" phones
First, it was reported with new SIM cards they were distributing earlier this year. Then people who kept their old SIM cards found they didn't work after a forced "security update."
This seems to have also trickled down to the T-Mobile MVNOs.
This is why we told someone else recently they should probably convert their phone from US998 on T-Mobile to Verizon VS996 firmware.
Then get a Verizon sim card or Verizon MVNO SIM card, and activate it in an old cracked screen Verizon phone off eBay, then put that already-activated SIM card into their "VS996" V30.
They will have VoLTE and VoWi-Fi calling.
Alternatively, if you really want to stick with T-Mobile network, you can do what @osprey00 suggested -- which is get a Google Voice number and use it as a tool to forward your carrier calls to it.
You can read his post, see his experiences, and see if this would apply to you.
For ME -- I've been using Google Voice for the past 10 years as my main phone number. I ported my carrier phone number at the time to Google Voice. Then got throwaway carrier numbers (whoever had cheapest plan) but never gave those to my friends. To my friends nothing ever changed. I've had the same "number" for the past two decades.
But within the past couple years, I had to start giving my bank and my cable company my carrier phone number for SMS security codes. Very annoying, because in the past they used my Google Voice number to text me with no problem.
So, even though under my current firmware (on my rooted Note 9) I cannot get carrier phone calls, I still have LTE data. And with the LTE data, I can use Google Voice (calls and texts) because it's VoIP. I also get AT&t carrier texts, as that is also data. It's just AT&T phone calls I cannot send or receive.
AT&T deactivated the SIM card in my native US998 V30+ and sent me a replacement phone, which is a Samsung Note 9. I'm staying with AT&T for a reason. Otherwise I would probably pull the "V30" Verizon trick also.
I bought both my wife and my elderly mother 64GB V35 phones -- which is basically an upgraded 64GB V30. (They previously had native US998 V30.) AT&T gives V35 VoLTE and WiFi calling, and for them there was nothing new to learn.
Click to expand...
Click to collapse
I think it was a hardware problem, honestly.
No matter what I did, I even tried different ROM to ensure I didn't mess around with root settings and somehow enabled or disabled something that I should not have. I tried flashing stock radios, and no, nothing would fix it.
I took my brothers phone to see if the SIM card would work with his phone, an unlocked Google FI phone. As soon as I installed the SIM, and booted up the phone, I could tell it was working perfectly even on the lock screen. Right away the status showed the name of the wireless company, and active 5G data icon on the status.
I must have damaged the internal radio or the LTE data modem when I dropped the phone last. The screen of the phone never broke even though I dropped the phone countless times, though the back glass has cracked lines all over even if the surface is still smooth and the phone continued being waterproof (I tested).
Anyway, I have since bought a new phone and the Data/Text/Talk all work perfectly on it.
I'm not sure what I'll do with this phone, as selling it wouldn't be ethical. And I doubt anyone would buy a phone with the warning that service may not work.
Ah well, I may just keep and use it as a test device.
Thanks to all who tried to help.
Amer28 said:
I think it was a hardware problem, honestly.
No matter what I did, I even tried different ROM to ensure I didn't mess around with root settings and somehow enabled or disabled something that I should not have. I tried flashing stock radios, and no, nothing would fix it.
I took my brothers phone to see if the SIM card would work with his phone, an unlocked Google FI phone. As soon as I installed the SIM, and booted up the phone, I could tell it was working perfectly even on the lock screen. Right away the status showed the name of the wireless company, and active 5G data icon on the status.
I must have damaged the internal radio or the LTE data modem when I dropped the phone last. The screen of the phone never broke even though I dropped the phone countless times, though the back glass has cracked lines all over even if the surface is still smooth and the phone continued being waterproof (I tested).
Anyway, I have since bought a new phone and the Data/Text/Talk all work perfectly on it.
I'm not sure what I'll do with this phone, as selling it wouldn't be ethical. And I doubt anyone would buy a phone with the warning that service may not work.
Ah well, I may just keep and use it as a test device.
Thanks to all who tried to help.
Click to expand...
Click to collapse
tried a rom on a j7 2015 because android 6 is going to be left and I only get emergency calls on lte and on 3g, no problem. It's not imei problem maybe exynos processor. I went back to 6.0.1 and no problem with 4g lite. By the way, I'm not in the USA.