I'm liking the phone a lot but what bothers me the most is the dialer app. Is non responsive at times, you press a contact from any call log and it doesn't do anything until the third time you try it, now it got stuck into a recent calls log and I haven't found a way to go back, it's features are great, there are a lot of them (block list, recording...), I'm only missing it being smart as the Motorola dialer for dual sim where it automatically learned which line you preferred to call your contacts with and sim switch one you initiated a call.
Anyone having dialer issues too?
Thanks
With updates phone is almost perfect for me EXCEPT THE DAMN DIALER, I can't believe anyone else has this issues too. Basically you have to press 2-3 times over a contact so it will bring the sim selection screen, maybe very few people actually uses both sims? Is the last thing that bothers me with it.
Litoven said:
With updates phone is almost perfect for me EXCEPT THE DAMN DIALER, I can't believe anyone else has this issues too. Basically you have to press 2-3 times over a contact so it will bring the sim selection screen, maybe very few people actually uses both sims? Is the last thing that bothers me with it.
Click to expand...
Click to collapse
Have you tried wiping cache and data
Sent from my ASUS_Z00AD using Tapatalk 2
Have you tried restarting the phone? Please ensure to update firmware and ASUS dialer app to latest version.
Sincerely,
ASUS_USA
[email protected]
Yes, phone is on 2.19, have done it since the beginning, recently wiped all data too, still same thing, you press a contact from the call history, it makes the click sound and all but does nothing, have to touch the contact two-three times more and then the sim selection screen comes, if you dont touch it again, it just stays there doing nothing, also after the first touch, the click doesn't sound anymore, even when it actually opens. I assume that the people that only has a one sim maybe don't see this.
I use 2 sims and I have never faced this issue.
Sent from my ASUS_Z00ADA using Tapatalk
Ok, found that issue worsens a lot with bluetooth active on the car, sometimes need to hit a contact 4-5 times.
Update, the issue was more frequently present when connected to car's Bluetooth but since 2.20.40.40 it's working as expected, sim selection screen takes 1-2 seconds to show but has come every time it has been requested. Good job.
Sent from my Nexus 9 using Tapatalk
I'm facing the same issue. It's irritating, need to touch 8-10 times or even more to make a call. Has anyone know the solution to it. Model No ASUS_Z010D. Just FYI, I have already updated to latest firmware & latest dialer, but issue persists.
Pls help
Asusarpit said:
I'm facing the same issue. It's irritating, need to touch 8-10 times or even more to make a call. Has anyone know the solution to it. Model No ASUS_Z010D. Just FYI, I have already updated to latest firmware & latest dialer, but issue persists.
Pls help
Click to expand...
Click to collapse
copy all contacts to google before doing below
if 5.0
go to settings > apps> all
find
androidsystem, asuscallingscreen, asusconfigupdater,asuscontacts, asus zenui, asus zenuiservices, contacts, contact storage, device config,google play services, google play store,setting,settingstorege, systemui, zenuikeyboard,zenuilauncher
clear data of all above apps
for 6.0 setting>apps and click thre dots and click show system and clear data of above apps.
restart device and allow permissions if required and tell if still the same
Related
Hello all,
Suddenly I'm having this problem where one of my contacts will start dialing, then quickly beep, and then crash back out to the Home Screen. No matter how I call, via the shortcut or dialing the number digit by digit, it crashes. Every other number works. When I dial the number via Google Voice it's fine. Texting that contact is fine. But calling is impossible. Anyone ever hear about this? Any ideas on what to do? I kinda need this contact.. it's my wife!
Thanks!
Wait, so even if you delete the contact and dial the number directly, it crashes? I suspect it is a contact that had something in it. For example, on the stock ROM, the way the stock contacts apps saves Pauses and Waits is different than some of the custom ROMs contact/dialer apps. So when I went to a new ROM, some of those contacts had data simply not supported by the ROM. I bet if you open the contact in Google from a PC, there is some sort of item stored in the contact that is throwing the dialer app out of whack.
tinpanalley said:
Hello all,
Suddenly I'm having this problem where one of my contacts will start dialing, then quickly beep, and then crash back out to the Home Screen. No matter how I call, via the shortcut or dialing the number digit by digit, it crashes. Every other number works. When I dial the number via Google Voice it's fine. Texting that contact is fine. But calling is impossible. Anyone ever hear about this? Any ideas on what to do? I kinda need this contact.. it's my wife!
Thanks!
Click to expand...
Click to collapse
I think we all know what really happened here...
You forgot to call your wife, so you told her that it was because your phone won't let you. She wouldn't believe you so to convince her, you started this thread.
jk man. Seriously, its probably what fermunky said. Are you rooted, and if so, on a custom rom?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Hey guys,
Yeah, I'm rooted on Cyanogen's ROM. My wife is as well, she's had no such issues and I didn't do anything that could have prompted this. I deleted the contact, texts, emails so there was no trace of it and I still can't dial her number at all. This is ridiculous. Will I have to re-root??? I'm not synced to Google so I can't do that PC edit.
Thoughts???
Sent from my T-Mobile myTouch 3G Slide using XDA App
Hey again... just tried exporting and re-importing my contacts and it still refuses to let me dial the one contact. I'm afraid I'm facing a hard reset because I can't go to work tomorrow without fixing this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Normally I would ask for the number to try and test it, but I am sure giving the number is out of the question... Have you tried swapping SIM cards, and then use her phone, with your SIM, and tried dialing the number again? If it follows your SIM card then I could only think of two things:
1: The SIM card has the contact on it, and is buggin the phone out
2: By some WEIRD fluke, your provider is somehow screwing up the handling on this one particular call.
I'm also getting this weird, blank, nameless System Group when I choose which contacts to display in Display Options. Never seen that before. Every time I make a new app it automatically decides to make it a Google contact. WHY?? I don't use Google for contacts. I don't get the option not to do that. And the contact goes to this blank group. I also see "System Group: My Contacts" and "All Other contacts" in addition to this blank one.
I don't even know how to see the SIM card contacts. But I don't use the SIM card as a rule. Not saying it couldn't have ended up copied or backed up there, just saying I don't use it for the obvious fields limitations.
So, since I'm on CM6, can I use Titanium to back everything up, then hard reset or is that not doable on a custom ROM?
You said this phone is not tied to a Google account?
It's tied to a Google account for Maps, etc but I don't have the contacts synced up. so I can't go to the PC as suggested and clean out the contact.
Well, as a troubleshooting measure, why not sync it to a PC and then view that contact in GMail to see if something is there.
However, you said you've completed deleted the contact, and direct-dialed the number with the same result? If so, do what I said and swap your SIM card into the other phone and dial the number again please.
Yes, that's right. However, if there were remnants on the SIM card, I wouldn't know. I certainly didn't put them there.
Soon as I meet my wife in about an hour I will do that test to see what happens and I'll reply back.
But meantime, any thoughts on my hard reset questions? I'm just thinking that if I use Titanium to back up the phone, and export the contacts, maybe I should just start from scratch? Any idea on the blank group I mentioned?
It may be doing that since you're not syncing contacts, not really sure.
As for swapping the SIM card, I am not suggesting it is a contact on the SIM card, just want to eliminate it as being a provider issue.
Do you notice if this only happens when calling the number from the same geographical location? Like, will it do it when you're at home versus when you're at work, grocery store, etc?
As for the backing up, cant help ya there. Never used titanium.
Happens everywhere. Not geo-specific.
Any other ideas for backing up and hard resetting? I'm actually more concerned about whether hard resetting on CM6 is a problem or complicated or anything.
Ok, I swapped cards with my wife...
- Called her number with HER phone using MY Sim, call went through fine.
- Called her number with MY phone using HER Sim, got to voicemail no problem.
Put MY Sim back in MY phone, beep and crash again.
Grrrrrrr......
Sent from my T-Mobile myTouch 3G Slide using XDA App
Just hard reset my phone. Did nothing. Still can't dial the number.
Dang... how did you do the reset? I usually suggest doing the wipe from recovery.
If that still doesn't work, I'd try maybe un-rooting, make sure it works on stock rom, and if it works, then try rooting again and try again. That is pretty bizarre though.
I just did the standard power off, reboot holding down volume down, then "clear storage". Also, since doing this and then restoring everything with Titanium, I've noticed I'm not getting email updates even though it's on.
Oh man.... I've never had to even think about unrooting and rerooting. No idea where to start. Any tips on how to do that or a good guide I can follow?
This is so annoying.
Try wiping from recovery. The Clear Storage option you're using is in hboot, I believe.
Trying to wipe from recovery now. I'll see what happens. Before and after restoring from Titanium.
No dice... still happening. I'm officially stumped. I called T-Mo. They were shocked. They're sending me a warranty replacement.
Now, though, I've gotta unroot. Never done that before.
I'm having an issue with my SMS where after a while they will sit in my inbox trying to send but not actually send or fail. I physically have to reboot the phone for them then to send. S-off, rooted running ARHD 10.2. I'm not sure if it's more network related or handset related as I can receive and everything else works solidly.
Anyone else experienced this?
I am running a similar set up like you, im on ATT, I can't say I've had that problem enough to say its a problem..
Obviously your service is good in that particular area?
xavier2k3 said:
I'm having an issue with my SMS where after a while they will sit in my inbox trying to send but not actually send or fail. I physically have to reboot the phone for them then to send. S-off, rooted running ARHD 10.2. I'm not sure if it's more network related or handset related as I can receive and everything else works solidly.
Anyone else experienced this?
Click to expand...
Click to collapse
Have you upgrade the firmware? Check this link http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
US users may wish to try the 2.22.1540.3 fw
jmoneste said:
Have you upgrade the firmware? Check this link http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
US users may wish to try the 2.22.1540.3 fw
Click to expand...
Click to collapse
Yeh I have upgraded my firmware before flashing 10.2. It's an intermittent problem which is the most annoying thing. In the ARHD post there seem to be at least 2 others with this same issue as well which is strange...
xavier2k3 said:
Yeh I have upgraded my firmware before flashing 10.2. It's an intermittent problem which is the most annoying thing. In the ARHD post there seem to be at least 2 others with this same issue as well which is strange...
Click to expand...
Click to collapse
I had an issue with sms notifications after I installed a custom rom. Then learned that my problem comes from the hearbeat interval settings. I think my carrier uses a custom value (5min is default) and since I changed the rom, their settings have not been pushed to my phone.
Testing several things I came across this app. It will not hurt to try it:
Install an app called "pnf push notification fixer". Is free from store.
Set the heartbeat mobile interval to 3 minutes.
Reboot.
Make sure the value did not change itself
Monitor and see if the problem stays the same.
This maintains the connection alive for me.
Have you checked when you experience the issue if the sms carrier center number removes or changes?
On the dialer press *#*#4636#*#*
Select phone info
Scroll down to smsc and hit refresh. Note the number when working. When it stops, repeat the process and check if the number is diff or was removed. You can also hardcode one there.
jmoneste said:
I had an issue with sms notifications after I installed a custom rom. Then learned that my problem comes from the hearbeat interval settings. I think my carrier uses a custom value (5min is default) and since I changed the rom, their settings have not been pushed to my phone.
Testing several things I came across this app. It will not hurt to try it:
Install an app called "pnf push notification fixer". Is free from store.
Set the heartbeat mobile interval to 3 minutes.
Reboot.
Make sure the value did not change itself
Monitor and see if the problem stays the same.
This maintains the connection alive for me.
Have you checked when you experience the issue if the sms carrier center number removes or changes?
On the dialer press *#*#4636#*#*
Select phone info
Scroll down to smsc and hit refresh. Note the number when working. When it stops, repeat the process and check if the number is diff or was removed. You can also hardcode one there.
Click to expand...
Click to collapse
Was your problem with notifications or actually having the messages send?
xavier2k3 said:
Was your problem with notifications or actually having the messages send?
Click to expand...
Click to collapse
I had a bit of both. The cellphone was not maitaining the network alive fast enough.
I have the same issue.
I've tried what jmoneste wrote, but the problem still persist. SMS keep failing. Everytime I want a message to be sent I have to activate airplane mode and then desactivate en resend the SMS. It's so annoying.
This problems comes from stock rom and now I'm using the Viper One ROM but it still fails.
Has anyone found the solution?
KamixD said:
I have the same issue.
I've tried what jmoneste wrote, but the problem still persist. SMS keep failing. Everytime I want a message to be sent I have to activate airplane mode and then desactivate en resend the SMS. It's so annoying.
This problems comes from stock rom and now I'm using the Viper One ROM but it still fails.
Has anyone found the solution?
Click to expand...
Click to collapse
I too have the sms not sending until put in flight mode and then off it again occasionally. Cant believe that its so common, but theres no fix. My phones completely stock too!
*EDIT
This is a known issue per Google. Thread on their product forum here https://productforums.google.com/for...A/tMN4y-GZAAAJ A huge thank you to uicnren for finding it!
I can't seem to find other reported instances of this when web browsing so thought I'd try here.
For the past week or so, anytime I make a phonecall there is no sound to indicate the phone is actually ringing. It's just silent until someone picks up, I get voicemail, etc.
Conversely every single time someone calls me I'm having to press option 1 to talk to them instead of just answering normally. (this part is a user option I've since disabled).
Not sure if I did something to settings, if this a bug, etc. It's driving me nuts though so any suggestions would be appreciated. I have not tried a factory reset yet because if I can about the hassle I'd like to.
Currently running 8.1 March update, on the non Verizon version. Bootloader is locked, not rooted.
Should also add that I use Google Voice, so maybe the issue is on that end.
Thanks in advance!
Sent from my Pixel 2 XL using Tapatalk
paxderomano said:
I can't seem to find other reported instances of this when web browsing so thought I'd try here.
For the past week or so, anytime I make a phonecall there is no sound to indicate the phone is actually ringing. It's just silent until someone picks up, I get voicemail, etc.
Conversely every single time someone calls me I'm having to press option 1 to talk to them instead of just answering normally.
Not sure if I did something to settings, if this a bug, etc. It's driving me nuts though so any suggestions would be appreciated. I have not tried a factory reset yet because if I can about the hassle I'd like to.
Currently running 8.1 March update, on the non Verizon version. Bootloader is locked, not rooted.
Thanks in advance!
Click to expand...
Click to collapse
I would first try clearing the google phone dialer app cache and data, reboot, and see it helps. If not, then I would uninstall it, reboot, then dl it again from the play store :good:
Or, side load the April OTA update
paxderomano said:
I can't seem to find other reported instances of this when web browsing so thought I'd try here.
For the past week or so, anytime I make a phonecall there is no sound to indicate the phone is actually ringing. It's just silent until someone picks up, I get voicemail, etc.
Conversely every single time someone calls me I'm having to press option 1 to talk to them instead of just answering normally.
Not sure if I did something to settings, if this a bug, etc. It's driving me nuts though so any suggestions would be appreciated. I have not tried a factory reset yet because if I can about the hassle I'd like to.
Currently running 8.1 March update, on the non Verizon version. Bootloader is locked, not rooted.
Thanks in advance!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Do you use Google Voice at all?
Badger50 said:
I would first try clearing the google phone dialer app cache and data, reboot, and see it helps. If not, then I would uninstall it, reboot, then dl it again from the play store :good:
Or, side load the April OTA update
Click to expand...
Click to collapse
I'm going to try the April update, the rest didn't work.
igknight said:
Do you use Google Voice at all?
Click to expand...
Click to collapse
Yes I do use google voice. I hadn't even thought of that. COuld definitely ber a google voice issue.
paxderomano said:
Yes I do use google voice. I hadn't even thought of that. COuld definitely ber a google voice issue.
Click to expand...
Click to collapse
The pressing 1 to answer was what made me think of that. I know there is an option to enable/disable that. Not sure about the no ringing issue, however.
igknight said:
The pressing 1 to answer was what made me think of that. I know there is an option to enable/disable that. Not sure about the no ringing issue, however.
Click to expand...
Click to collapse
I just looked through the Gvoice settings and didn't find anything (that I could tell) that does that. But thanks for the suggestion!
I think it is the Screen Calls option, under the Calls settings in the web interface. Don't quote me on that.
I have the same problem regarding not hearing the ringing sound when making a call. I also use Google Voice. I have not experienced the press option 1 to answer problem.
machostallion said:
I have the same problem regarding not hearing the ringing sound when making a call. I also use Google Voice. I have not experienced the press option 1 to answer problem.
Click to expand...
Click to collapse
Okay so I was able to get rid of that (it's the option that asks if you want to hear the name of the caller, definitely doesn't work like I thought it would).
Loaded the April update and still have the issue with outgoing calls.
"Loaded the April update and still have the issue with outgoing calls. "
Same here. It stated happening after installing google voice and uninstalling it.
paxderomano said:
I can't seem to find other reported instances of this when web browsing so thought I'd try here.
For the past week or so, anytime I make a phonecall there is no sound to indicate the phone is actually ringing. It's just silent until someone picks up, I get voicemail, etc.
Conversely every single time someone calls me I'm having to press option 1 to talk to them instead of just answering normally. (this part is a user option I've since disabled).
Not sure if I did something to settings, if this a bug, etc. It's driving me nuts though so any suggestions would be appreciated. I have not tried a factory reset yet because if I can about the hassle I'd like to.
Currently running 8.1 March update, on the non Verizon version. Bootloader is locked, not rooted.
Should also add that I use Google Voice, so maybe the issue is on that end.
Thanks in advance!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Press 1 to talk? What do you mean?
paxderomano said:
I can't seem to find other reported instances of this when web browsing so thought I'd try here.
For the past week or so, anytime I make a phonecall there is no sound to indicate the phone is actually ringing. It's just silent until someone picks up, I get voicemail, etc.
Conversely every single time someone calls me I'm having to press option 1 to talk to them instead of just answering normally. (this part is a user option I've since disabled).
Not sure if I did something to settings, if this a bug, etc. It's driving me nuts though so any suggestions would be appreciated. I have not tried a factory reset yet because if I can about the hassle I'd like to.
Currently running 8.1 March update, on the non Verizon version. Bootloader is locked, not rooted.
Should also add that I use Google Voice, so maybe the issue is on that end.
Thanks in advance!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
maybe? https://productforums.google.com/forum/#!msg/voice/48CgSY067GA/tMN4y-GZAAAJ
uicnren said:
maybe? https://productforums.google.com/forum/#!msg/voice/48CgSY067GA/tMN4y-GZAAAJ
Click to expand...
Click to collapse
Yes, that is it exactly! For whatever reason, I was having zero luck finding anything about it on the product pages. Thank you, I'm glad that it's a known issue and not just me.
uicnren said:
maybe? https://productforums.google.com/forum/#!msg/voice/48CgSY067GA/tMN4y-GZAAAJ
Click to expand...
Click to collapse
pcloadletter1 said:
"Loaded the April update and still have the issue with outgoing calls. "
Same here. It stated happening after installing google voice and uninstalling it.
Click to expand...
Click to collapse
pcloadletter, this is apparently a known issue. thread on google product page above. Thanks again uicnren!
Sooo I got the phone last Thursday and am using it on Verizon. I've had a few issues that I figured I'd throw a thread together incase anyone else has the same...
Known Issues that I have:
"GroupMe" application will not update unless I am in the application and clicking on a specific chat. - Worked on every other phone I have and cant even find anything on this subject on google. If someone sends a message in a chat it will not update or notify me. I have to click on the specific chat for it to update. I've reinstalled the app 3 times and cleared the cache. un-optimized it with battery settings, nothing is working.
Fixed Issues that I have:
Phantom vibration. - Almost like a notification is happening but nothing is showing on the screen. Cant figure out this one for the life of me. I even have a notification log downloaded and it just vibrates away with nothing being logged.
Found out it was Verizon Caller ID app. Apparently it keeps crashing and "starting" over and over again. I disabled notifications on it and the vibration went away!
MMS Cannot be received only sent. - I've gone through this extensively with Verizon support. Tried everything on another thread, switched out sim blah blah blah, finally they have opened a ticket with the engineers and will get back to me in 48 hours.
Works now in default app just not android messages......................................
Anyone else having any other issues?
That's disappointing that there are mms issues. MMS on the U11 using anything but the stock messaging app was a complete ****show. I hope you can get more bands than just 13 as well.
Sent from my Pixel 2 XL using Tapatalk
MMS works fine on my European un-locked (and rooted) U12+. Got one as late as yesterday... Using stock SMS app.
Pr3dict said:
Sooo I got the phone last Thursday and am using it on Verizon. I've had a few issues that I figured I'd throw a thread together incase anyone else has the same...
Known Issues that I have:
MMS Cannot be received only sent. - I've gone through this extensively with Verizon support. Tried everything on another thread, switched out sim blah blah blah, finally they have opened a ticket with the engineers and will get back to me in 48 hours.
Phantom vibration. - Almost like a notification is happening but nothing is showing on the screen. Cant figure out this one for the life of me. I even have a notification log downloaded and it just vibrates away with nothing being logged.
"GroupMe" application will not update unless I am in the application and clicking on a specific chat. - Worked on every other phone I have and cant even find anything on this subject on google. If someone sends a message in a chat it will not update or notify me. I have to click on the specific chat for it to update. I've reinstalled the app 3 times and cleared the cache. un-optimized it with battery settings, nothing is working.
.....................................
Anyone else having any other issues?
Click to expand...
Click to collapse
Someone on Android Central had Verizon block messaging and then re-add it for everything to work. Maybe worth a shot?
Same here... Unlocked US model. Send but not receive texts...
I've done the same, reset, new SIM, swapped Sims etc.
I'll take a look on AC and see if they have something there for a solution... Thanks for the heads-up. Glad I'm not alone.
CJ
I have found that Android messages app doesn't work as you can't select the preferred sim for messages. Having to use stock at the moment.
Somewhere in another thread, there was an adb command I think that set and enforced the default sim slot. Wonder if that would help with your issue, Nestacres? Sorry, I would search myself and link but just checking in on a quick break at work.
Nestacres said:
I have found that Android messages app doesn't work as you can't select the preferred sim for messages. Having to use stock at the moment.
Click to expand...
Click to collapse
Android Messages isn't comiled for usage with Dual-SIM, as Google Nexus/Pixel phones are all Single-SIM devices. If you know how to use adb you cand do the following:
From adb shell run the following command
Code:
adb shell settings put global multi_sim_sms 1
This did the trick on the U11 DUGL as well, and Android Messages could be used and worked just fine. Thanks to @Electronic Punk for pointing that one out to me!
Soooo Got MMS to work on the default app and with Verizon Message +.... Android messages still does not work and that is something many others have said as well....
Very sad.
Pr3dict said:
Soooo Got MMS to work on the default app and with Verizon Message +.... Android messages still does not work and that is something many others have said as well....
Very sad.
Click to expand...
Click to collapse
Pr3dict: did you do anything different other than what you originally posted? I've been on vacation since i got the U12 and haven't called Verizon. I can send everything, but not receive. I can pop the SIM and put it in my iPhone x and the texts just role in immediately...I really want to love this phone! Lol
5m4r7ph0n36uru said:
Android Messages isn't comiled for usage with Dual-SIM, as Google Nexus/Pixel phones are all Single-SIM devices. If you know how to use adb you cand do the following:
From adb shell run the following command
Code:
adb shell settings put global multi_sim_sms 1
This did the trick on the U11 DUGL as well, and Android Messages could be used and worked just fine. Thanks to @Electronic Punk for pointing that one out to me!
Click to expand...
Click to collapse
It actually works great with dual sim, for some reason HTC left out the default SMS sim option out on Oreo (simply doesn't exist in settings.apk anymore) and only left the data one. Fortunately that fix is basically a fire and forget, once it sees a default it has no issue picking between them.
HTC handle it differently on phone and SMS as they have a button for each sim.
Electronic Punk said:
It actually works great with dual sim, for some reason HTC left out the default SMS sim option out on Oreo (simply doesn't exist in settings.apk anymore) and only left the data one. Fortunately that fix is basically a fire and forget, once it sees a default it has no issue picking between them.
HTC handle it differently on phone and SMS as they have a button for each sim.
Click to expand...
Click to collapse
Yeah they handle it quite different. But let's see. Maybe we'll get an overhaul with Android P.
Sent from my HTC U12+ using XDA Labs
cramjammer said:
Pr3dict: did you do anything different other than what you originally posted? I've been on vacation since i got the U12 and haven't called Verizon. I can send everything, but not receive. I can pop the SIM and put it in my iPhone x and the texts just role in immediately...I really want to love this phone! Lol
Click to expand...
Click to collapse
I did everything possible. Even got a new SIM... What seemed to do the trick (and was the last thing I did) was having Verizon block my messages and then unblock them.
Then I could send + receive. Beforehand I could only Send... But beware it does not work with Android Messages.
cramjammer said:
Pr3dict: did you do anything different other than what you originally posted? I've been on vacation since i got the U12 and haven't called Verizon. I can send everything, but not receive. I can pop the SIM and put it in my iPhone x and the texts just role in immediately...I really want to love this phone! Lol
Click to expand...
Click to collapse
How did you first activate your phone? If it's not activated properly on Verizon it can fry your SIM card or cause things to not work.
I first swapped my SIM from my U11 and could not make calls but was able to use internet and send and receive text and mms. But just like the U11, I can only receive MMS on the stock apps like HTC messaging and Verizon message+. Cannot receive MMS on third party apps.
But the proper way to activate the U11 and U12+ is to first register your imei with Verizon then you have to transfer your SIM from a Verizon device that has advanced calling/VoLTE in the settings.
The U12+ does not have any Verizon advanced calling or VoLTE setting so if you just pop a new SIM in without first having it activated on a Verizon advanced calling device, it could cause problems and fry your SIM card.
It sucks but that is the best way to activate it.
Manually attached IMEI to SIM, and toggled messages/on/off on my account.
All is well and working for receiving SMS/MMS on stock messages! It worked immediately...
Thanks for the feedback and discussion everyone.
CJ
In my case, after updating (purely, after RUU) to v1.21.401.3 I have noticed a few times that after picking up the device and "squeezing" I should wake up, scan my face and unlock my smartphone (I have my preferences set) .
But just the few times after "squeezing" the device does not react at all, there is no vibration.
After the traditional unlocking (applying the finger to the fingerpront or pressing the POWER button) the smartphone wakes up properly.
This happens when the smartphone is not used for a long time (deep sleep?).
But this is not the rule.
I also had ONE total reboot.
On the other hand, the update did not improve in the first few months the best inflections of the volume up button (Vol +). Very often you have to press many times "to surprise", and pressing and holding it to turn up in series - is very difficult to achieve
regards
q.
Is anyone else having issues with the youtube app? Im finding it buggy. To be precise: if I start a video and then turn the phone landscape to go into fullscreen, if I then turn back the phone vertical and come out of fullscreen and then try minimise the still playing video it goes a bit haywire, parts of the screen goes grey and I can't minimise the video. Can any replicate?!
Sent from my HTC U12+ using Tapatalk
New issue thats bothering THE CRAP OUT OF ME!!!!
The phone isnt vibrating on incoming calls. I thought I just kept not feeling it or hearing it but nope, the phone literally turns the screen on and it just doesnt vibrate. I don't have battery saver on, and I don't have "Do not disturb" on. Its weird.
sentient85 said:
Is anyone else having issues with the youtube app? Im finding it buggy. To be precise: if I start a video and then turn the phone landscape to go into fullscreen, if I then turn back the phone vertical and come out of fullscreen and then try minimise the still playing video it goes a bit haywire, parts of the screen goes grey and I can't minimise the video. Can any replicate?!
Click to expand...
Click to collapse
I have the same problem. It also happens when I press back on the navigation bar
tdwpkidd said:
I have the same problem. It also happens when I press back on the navigation bar
Click to expand...
Click to collapse
Discovered a slight work around since. It doesn't happen if you go in and out of fullscreen using little button in the bottom right. So it only happens with auto rotation.
Sent from my HTC U12+ using Tapatalk
Good morning. Does anyone have any idea how I can solve the problem I have with the google dialer? When I am called, it takes a long time for the screen to turn on while the sound is ringing and it is generally slow to show who is calling .... I have tried to clear the application cache .... I have checked that irrelevant applications do not have access to the phone application but nothing .... Is there a solution? Thanks
I have the same issue, it actually started with my Pixel 4 XL. Back then I thought maybe it's just getting old. Now I'm having the exact same issue with my P6P. Tried a factory reset thinking it might have been something that migrated with my backup but that did not help.
I'm chiming in only to say I haven't seen this problem, and hope you figure it out. Not rooted? No custom kernel?
Not rooted and no custom kernel, been considering those as a solution
I never tried the google dialer. Didn't trust the phone enough to put a sim in it until I had self-built google-free aosp (now grapheme) installed. I have not experienced this with aosp dialer.
eddiedimitris said:
Good morning. Does anyone have any idea how I can solve the problem I have with the google dialer? When I am called, it takes a long time for the screen to turn on while the sound is ringing and it is generally slow to show who is calling .... I have tried to clear the application cache .... I have checked that irrelevant applications do not have access to the phone application but nothing .... Is there a solution? Thanks
Click to expand...
Click to collapse
Did you ever solve this? Not even a factory reset seems to solve it for me
slimfady said:
Did you ever solve this? Not even a factory reset seems to solve it for me
Click to expand...
Click to collapse
Which update is your phone on? November or December? If November, maybe try manually flashing the December update, potentially removing the "-w " so that it doesn't wipe your phone.
roirraW edor ehT said:
Which update is your phone on? November or December? If November, maybe try manually flashing the December update, potentially removing the "-w " so that it doesn't wipe your phone.
Click to expand...
Click to collapse
I'm on the December update, but had it even on the November build
When I open the Google dialer and click on the button to pop up the numbers it's very slow to open up
slimfady said:
I'm on the December update, but had it even on the November build
Click to expand...
Click to collapse
When you factory reset, did you test the Google dialer without restoring any of your old apps or data?
If the January update doesn't fix it for you when it comes out, I'd consider trying that.
Tried before restoring the apps, but I did restore my contacts and SMS. Same result. Could it be something related to my contacts (around 1400 contacts)?
slimfady said:
Tried before restoring the apps, but I did restore my contacts and SMS. Same result. Could it be something related to my contacts (around 1400 contacts)?
Click to expand...
Click to collapse
I doubt it, although I "only" have 635 contacts. Right now I'd say everything is suspect, however. You've got to eliminate every possibility.
I might suspect the number/size of SMS before the number of contacts, but it's worth eliminating both at the same time just to see. Or, as I said, wait until the late January update, but if you still have the problem then you'd have to start from scratch yet again to eliminate those possibilities.
roirraW edor ehT said:
I doubt it, although I "only" have 635 contacts. Right now I'd say everything is suspect, however. You've got to eliminate every possibility.
I might suspect the number/size of SMS before the number of contacts, but it's worth eliminating both at the same time just to see. Or, as I said, wait until the late January update, but if you still have the problem then you'd have to start from scratch yet again to eliminate those possibilities.
Click to expand...
Click to collapse
Thanks, will give it a shot after the January update drops
My best guess is that this delay happens when you have got paired an android wear with your phone. Just for testing, I paired amazfit gtr 3 pro with my P6P and this delay does not occur.
But at the same time, If you are running aosp rom, this delay doesn't happen with the dialer even with android wear paired. Strange
asif4self said:
My best guess is that this delay happens when you have got paired an android wear with your phone. Just for testing, I paired amazfit gtr 3 pro with my P6P and this delay does not occur.
But at the same time, If you are running aosp rom, this delay doesn't happen with the dialer even with android wear paired. Strange
Click to expand...
Click to collapse
Interesting thought, I don't have an Android wear watch paired but I have a fitbit Versa. I haven't had this issue since the January update plus a full wipe.
I had a seperate theory which is related to the number of Google accounts I have on my phone (I had 4 before wiping). I'll keep an eye on it and try to unpair the watch if it re-occurs.
slimfady said:
Interesting thought, I don't have an Android wear watch paired but I have a fitbit Versa. I haven't had this issue since the January update plus a full wipe.
I had a seperate theory which is related to the number of Google accounts I have on my phone (I had 4 before wiping). I'll keep an eye on it and try to unpair the watch if it re-occurs.
Click to expand...
Click to collapse
Well well well, I acted as per your theory and deleted all my google account except one that is linked to contacts and I am experiencing quite instant call-in and call-out screen and the contacts also show almost instantly.
Its a shame that android is google's own product and these issues (having more than google account) jeopardize the whole experience. I have read a lot of posts on reddit and other forums for the the same issue and all what google guys suggest is factory reset which is not a pleasant way and the problem persists after that.
Maybe I am too quick to give my feedback and this issue resurfaces even with 1 account. Will keep an eye on that and will post my further findings.
asif4self said:
Well well well, I acted as per your theory and deleted all my google account except one that is linked to contacts and I am experiencing quite instant call-in and call-out screen and the contacts also show almost instantly.
Its a shame that android is google's own product and these issues (having more than google account) jeopardize the whole experience. I have read a lot of posts on reddit and other forums for the the same issue and all what google guys suggest is factory reset which is not a pleasant way and the problem persists after that.
Maybe I am too quick to give my feedback and this issue resurfaces even with 1 account. Will keep an eye on that and will post my further findings.
Click to expand...
Click to collapse
I think it's confirmed. I've added two more accounts and the call screen is now back to taking forever to showup when I get a call
slimfady said:
I think it's confirmed. I've added two more accounts and the call screen is now back to taking forever to showup when I get a call
Click to expand...
Click to collapse
Yeah I reconfirm it as well, no delay in call screens if having 1 Gmail account only.
Culprit is Google phone app I guess, may be it goes through all accounts to search n display the contact that cause this delay. I have tried Google phone app on samsung s21 ultra too n there is same delay with having more than 1 accounts while Samsung own dialer app doesn't suffer this issue.