The issue is the current build of gapps - quick workaround is to manually set the Phone/Dialer app as the default Phone App in Settings -> Apps -> -> Default Apps -> Phone App.
The only thing that worked for me is to stop the Phone Application. It restarts itself again, so you don't have to worry for missing calls or anything.
Settings -> Apps -> ALL -> Phone.
Click Force stop
Clear Voice Mail Notification Icon
I am in the same boat as you. Since I found no way to actually disable voicemail notifications on my Nexus 5, I instead configured the longest possible voicemail greeting the T-Mobile system would allow, which consists of complete silence for 3 minutes. I have not gotten a single voicemail notification since.
You can install and configure T-Mobile's own Visual Voicemail app. You will get notified about your voicemails through it instead of the system's Phone/Dialer app, with the ability to dismiss that notification. As a bonus, you can also listen to and delete your voicemails without having to dial in and waste prepaid minutes.
Be aware that this app needs to ...
You could make your phone to act as a VPN Gateway
vpn server (can obtain any free openVPN from playstore)
Using a VPN gateway will make tethered traffic to go through the VPN.
Turn on portable hotspot
Open terminal as root and enter the following codes (you can paste them)
iptables -t filter -F FORWARD
iptables -t nat -F ...
I've just found an issue in AOSP that tracks this and has a suggested fix for it:
I tried Textra as a texting replacement app (for other reasons). In
the settings it has an option to use either System or Legacy protocols
for MMS. It even tells the user to try System if they have a VPN
enabled. I switched to System from the default Legacy, and now my ...
Deleting info on the Visual Voice Mail app itself was as simple as deleting the db file. This was located just above the folder containing the voice mails. It was in the format: email@example.com.
I used Tasker to delete that file, and then went back into the app. No more voicemail showing.
It's probably best practice to delete the cache files as ...
First off, you unfortunately can't get an S9/S9+ in the US that supports dual SIMs. Theoretically, you could import a European model to get that, but don't—compatibility with US carriers (especially CDMA ones like Verizon and Sprint) will be severely limited.
Second, I'd definitely recommend you purchase an unlocked S9/S9+ from Amazon or Samsung, rather ...
One possibility is that "characters" is not what you think. SMS was originally designed for single-byte languages, so in languages that use non-Latin characters, one "character" in that language counts as 2 or 4 characters in the SMS message. The problem is particularly noticeable in Chinese. Emoji also count as multiple characters for this purpose.
This took a lot of searching, and 10 phone reps before one could help. The default APN protocol was wrong: APN protocol: IPv4/IPv6.
It wasn't set to use both. That one little change to the APN fixed the problem, and now I have data again.
Name: T-Mobile US LTE
SCH-I535 is not a GSM phone so will not work with any 2G or 3G T-Mobile tower. Also that phone only supports LTE frequencies of 700 MHz & 1900 MHz, neither of which are bands that T-Mobile use to any significant degree. Instead T-Mobile uses 1700 & 2100 MHz.
T-Mobile is however in the process of rolling out 700 MHz & 1900 MHz, so you might get ...
Okay, here's what I can gather...
There should be no real loss of capability if you move to AT&T. While AT&T does not advertise LTE Band 8 capability on its S5s, Band 8 is largely used in South Korea, Japan, and Taiwan; unless you travel to those places, it shouldn't be a problem. I would, however, check AT&T's coverage map to be certain.
This is not an Android question, but more like a generic mobile question.
But to answer your question: YES, the old one will still work. SIM cards are not tied to cellphones. So, you can always transfer SIM cards to other phones that have SIM card slots, assuming that the phone allows the network your SIM card is for. i.e. If the phone is locked to a ...
The relationship between Google and the carriers for this purpose is a purely ...
The Moto X does not support T-Mobile's WiFi calling. Customer support reps have stated that this is because it is not a carrier branded device, meaning they have not modified the system ROM to add this feature:
The Moto X does work on our network but because it is not a T-Mobile branded device we do not support WiFi Calling on it.
You'll either need to ...