exchange email receiving not sending stuck in outbox - Samsung Galaxy Nexus

looks like this is an inherent bug on Android.
Any fix?

blinkjona said:
looks like this is an inherent bug on Android.
Any fix?
Click to expand...
Click to collapse
Before calling it a bug:
Have you checked your settings on outgoing mail? Right servername, port, authentication, security settings and so on?
I haven't heard this one before. That alone is not proof or anything, just that I would suspect with a bug that more people where complaining in these forums.

Diger36 said:
Before calling it a bug:
Have you checked your settings on outgoing mail? Right servername, port, authentication, security settings and so on?
I haven't heard this one before. That alone is not proof or anything, just that I would suspect with a bug that more people where complaining in these forums.
Click to expand...
Click to collapse
Oh yes sure did checked my settings , remove account, reboot etc
having looked around for a fix i did noticed many others having the same problem right from G1.

Related

FIXED: SMS Timestamp Issue

UPDATE: I've found a fix for this issue - AWESOME!
Just go to the Android Market and install the SMS Time Fix app by Matt Precious.
http://www.androlib.com/android.application.com-mattprecious-smsfix-pAFq.aspx
It works perfectly, and updates the time stamp on all messages to relfect PHONE time and not network time. HINT: Make sure the "Last Resort" option is checked in the settings and offset is set to zero. This little app now makes the Evo Messages app usable. Finally...
Hope this is helpful info
So, I've been reading and experiencing several issues with SMS timestamps on the Evo 4G.
It seems there are three distinct issues with SMS timestamps on the the Evo and I believe they all have the same root cause.
Issue 1: When roaming texts are received with the wrong time stamp, offset by several hours (typically 4 or 5 hours off). This causes them to not be threaded in the conversation correctly. Very annoying.
Issue 2: When receiving SMS messages on any network (Sprint or Roaming), the time stamp is off by an hour. The result is the same as Issue 1, but a less extreme example.
Issue 3: When texting back and forth in quick succession, SMS messages are not logged in the order in which they are received, and received text messages ALWAYS appear before sent text messages if they are sent during the same minute, regardless of which one was actually sent first. This is also very annoying.
I believe the root cause is that the native Sense UI messaging app is using the timestamp of the tower of each SMS rather than using the time stored on the phone. To prove this, if you use Handcent and set it to use "phone time" and ignore the tower time, it works perfectly. The thing is that I don't want to use Handcent and I want to use the native app. Is there a setting that can be tweaked to fix this? Has anyone talked to HTC or Sprint about the issue and is a fix in the works?
For such a major problem, I am surprised more people haven't come forward. It's a pretty significant bug...
Thanks,
Matt_TX.
Click to expand...
Click to collapse
I agree and its getting really annoying since it causes me to miss texts.
NM, too easy
Has anyone talked to Sprint or HTC about it? I am sure there HAS to be a fix in the works. The good news is that the native Froyo messaging app does not do this (as far as I can tell). I used a Nexus One on T-mobile and it doesn't occur. It appears to be using the phone's timestamp, as it should...
As long as HTC don't apply their "logic" (or lack thereof) over Froyo, it should be fixed soon.
I also can't believe that Sense UI stops the user from having more than one Exchange account. Android 2.1 (Eclair) does this by default. Why on earth would they remove it?
Anyway, back on topic... Please please post with your thoughts and discoveries around the SMS timestamp issue.
Thanks!
How is this related to development?
tkrechel said:
NM, too easy
Click to expand...
Click to collapse
I'm not sure what you mean by "NM, too easy". Can you explain or provide any insight. Please help if you can. For those of us with this issue, it's REALLY annoying. I apologize if the question is dumb and there is an easy fix.
I realize that some of you may not feel that it is related to development, but I disagree. For those geniuses out there that make ROM's, maybe there is some way to fix this with a setting or minor change in the Sense UI messaging app...
Additionally, there is no need to berate someone that's genuinely asking for help. It's obvious that this forum gets the most traffic, and it's obvious that the smartest "Evo User" minds are located here. I don't think there is any harm in reaching out for help, isn't that the purpose behind these forums
The samething was happening to me last night.
Sent From My HTC EVO 4G
nebenezer said:
How is this related to development?
Click to expand...
Click to collapse
Agreed. If its not happening with Handcent nor the AOSP apk, then its a direct HTC issue.
General Discussion. Also, probably not really that urgent.
./agree on all poins with OP.
I posted in Q&A about this same issues, with no replies 8(.
Anyway, I thought it was related to the modified prl that I installed. However it would do it even when I was on the stock prl.
Long story short, I called sprint and said I was having the issue. They said they were going to refresh something on their side, to wait 20 mins then power cycle the phone.
Did that and to my surprise it worked! Then yesterday I re-flashed a custom rom and the sms timestaps went all wonky. /sigh
suck it up and use handcent or chomp, they are overall better apps, just not as nice of a UI.
this has been a problem for quite some time. I've looked everywhere for a solution. This was a problem on winmo phones as well.
I switched to handcent and never looked back. Once you get it all customized, it's awesome.
davebu said:
suck it up and use handcent or chomp, they are overall better apps, just not as nice of a UI.
Click to expand...
Click to collapse
look at this guy.
handcent didn't work on my froyo rom, not sure about chomp, didn't try it.
at work i always have this problem, texts are recieved 5 hours into the future, whereas the ones i send are the correct time. occasionally ones they send are the correct time so i have to scroll up and down and it is very annoying.
not a fan of handcents pop up notifications, i guess i could turn em off.
guess i'll just 'suck it up'
regulator207 said:
this has been a problem for quite some time. I've looked everywhere for a solution. This was a problem on winmo phones as well.
I switched to handcent and never looked back. Once you get it all customized, it's awesome.
Click to expand...
Click to collapse
yup, had the same problem on my old HTC Diamond with Sense/TF3d on it.
Updated First Post...

G-mail bug

I was wondering if anyone else was experiencing this bug I am being faced with...
If I click an e-mail address link in Gmail app, it crashes Android System.
holycow1 said:
I was wondering if anyone else was experiencing this bug I am being faced with...
If I click an e-mail address link in Gmail app, it crashes Android System.
Click to expand...
Click to collapse
Same here - seems clicking on such a thing results in an inability to find a particular class (com.android.mail.providers.Account). Very strange.
Just checked and I don't seem to have that problem.
Perhaps there is something you loaded or perhaps froze/deleted??
krelvinaz said:
Just checked and I don't seem to have that problem.
Perhaps there is something you loaded or perhaps froze/deleted??
Click to expand...
Click to collapse
While I don't have an issue w/ this - fwiw I'm all kinds of bloated outside of removed CIQ/Knox things.
krelvinaz said:
Just checked and I don't seem to have that problem.
Perhaps there is something you loaded or perhaps froze/deleted??
Click to expand...
Click to collapse
I don't think so... I'm only using wanam which shouldn't be affecting the gmail app...

[Bug List]KitKat 4.4.2 Upgrade Bugs

Here's a list of reported bugs since the 4.4.2 kitkat upgrade (bugs may not affect everyone)
1. Horizontal lines during video playback - happens randomly - Rebooting the tablet fixes it / enabling "Disable overlay" in developer settings seems to work -elzeus
2. Audio quality degradation - happens randomly - Rebooting the tablet fixes it / going to test after a clean stock install -elzeus
3. Battery life issues - inaccurate battery level reporting (5% turns 25% after reboot) - alexandruene
4.Chromecast systemui crash is pretty serious. - GldRush98
5.Lockscreen widgets are broken. - GldRush98
6. Emails not showing up in sent folder - jaytee23
7. long press the "period" the "?" doesn't work - RTbar
Battery life
The big issue i have is the battery life. today i couldn't get more then 2 hours on the internet. Did a factory reset and the same thing.
Once it reaches 5 percent if i restart it goes up to 25 but it drops back down to 5 percent in like 5 minutes. Tried with no sd card, no other app's but the same thing. Anyone with a tip on how to get this fixed?? Before the update it was working fine.....
I've added your issues. I have not come across that battery issue on my tablet. Have you tried wiping your cache and user data from recovery before setting up the tablet?
Update for my issues I did a Odin restore with the stock 4.4.2 image and so far no video or sound issues but they took some time to show up before so I'll be keeping a close eye on it.
elzeus said:
So far I've come across 2 major bugs and I'll be updating the list with other bugs when found.
1. Horizontal lines during video playback - happens randomly - Rebooting the tablet fixes it / going to test after a clean stock install -elzeus
2. Audio quality degradation - happens randomly - Rebooting the tablet fixes it / going to test after a clean stock install -elzeus
3. Battery life issues - inaccurate battery level reporting (5% turns 25% after reboot) - alexandruene
Click to expand...
Click to collapse
I can verify random audio quality issue. Happened to me four times since the KK update.
It seems to happen either after you quit an app/game or waking the Note from sleep. I haven't been able to trace the trigger to an exact action or app yet, if there is one.
You don't have to reboot to fix. You can fix by locking and unlocking... maybe once, maybe a few times. But it comes back to normal after one or a few tries for me. Reminds me of the audio bug we had on the HP Touchpad after its final firmware update. Damn! I thought I wasn't going to have to deal with that anymore!
I'll try to be more specific on the lock/unlock fix as I gather more info when it happens again.
And by the way, the fix on the Touchpad was also very similar - lock, wait ten seconds, unlock... lol... maybe Samsung is using the Touchpad audio driver!
jaytee23 said:
I can verify random audio quality issue. Happened to me four times since the KK update.
It seems to happen either after you quit an app/game or waking the Note from sleep. I haven't been able to trace the trigger to an exact action or app yet, if there is one.
You don't have to reboot to fix. You can fix by locking and unlocking... maybe once, maybe a few times. But it comes back to normal after one or a few tries for me. Reminds me of the audio bug we had on the HP Touchpad after its final firmware update. Damn! I thought I wasn't going to have to deal with that anymore!
I'll try to be more specific on the lock/unlock fix as I gather more info when it happens again.
And by the way, the fix on the Touchpad was also very similar - lock, wait ten seconds, unlock... lol... maybe Samsung is using the Touchpad audio driver!
Click to expand...
Click to collapse
Got lines again on video tried to lock a bunch of times didn't work (ill try for audio). Don't they test these updates? This is a pretty nasty bug that didnt happen pre kitkat, I think im going to downgrade until its fixed.
Update after reading this youtube thread https://www.youtube.com/watch?v=NEasAq2ik_A
I'm trying out forced gpu rendering to see if it fixes it. It seems like it is a software issue as it affects the pro 12.2 model as well.
elzeus said:
I've added your issues. I have not come across that battery issue on my tablet. Have you tried wiping your cache and user data from recovery before setting up the tablet?
Did everything but didn't help, last night i left in recovery mode so i can make sure the battery dies completely and to day i saw a big improvement.
I hope it will stay that way.. I will keep you updated
Click to expand...
Click to collapse
Mh, as developer I am always careful to call something a bug.
And for these "bugs" my question is: Why not everyone have it? Why only a small group? Therefore I don't think that these are bugs but have to do with your installation.
Did anyone of your try a factory reset? Try out on a clean installation, which means without any settings changed, any app installed, any sd-card inserted?
Elim said:
Mh, as developer I am always careful to call something a bug.
And for these "bugs" my question is: Why not everyone have it? Why only a small group? Therefore I don't think that these are bugs but have to do with your installation.
Did anyone of your try a factory reset? Try out on a clean installation, which means without any settings changed, any app installed, any sd-card inserted?
Click to expand...
Click to collapse
I've done a factory reset & clean installation. I haven't rooted but did add my normal apps after getting it setup with sd card. The next time it happens I'll try unmounting the sd card.
If you check out this video https://www.youtube.com/watch?v=NEasAq2ik_A they also had the issue on their Pro 12.2 but that tablet received a stability update in early April that may have fixed it. It may be that our version was trailing there's or there is some other variable (no magazine UI etc) that is causing it http://forum.xda-developers.com/showpost.php?p=50527314&postcount=20 that person also had the lines in late Feb. I'll pm him and ask him if the issue went away after their update.
Forcing GPU 2d rendering from the developer options didn't seem to work as the corruption came back, but I did enable the "Disable UI overlay" and it did end up going away "crossing fingers" as this is the only thing I've tried that has gotten rid of the lines while the tablet is powered on (usually it only goes away after rebooting).
Another bug I found so far is with the included Email app. I'm using it with my gmail account. The new version included with KK has an issue with sent mail. Specifically, it doesn't update the sent mail folder - at least for me. It used to work perfectly. Now when you send an email from the app, the email doesn't show up in your sent mail folder within the app. I have tried deleting all the email data on the tablet, and the cache, and set it up four times since KK and it it just won't show email you send from the tablet in the sent mail folder. Note, I'm not talking about email that is already in your sent email folder in your gmail account. I'm saying, send a new email from the tablet, and that email should immediately appear in your sent mail folder, but it doesn't. It doesn't ever show up there. Kind of a problem. Can anyone else confirm this? Send an email from the Email app and see if it shows up in your sent mail folder within the email app. Thanks.
---------- Post added at 10:40 PM ---------- Previous post was at 10:19 PM ----------
Elim said:
Mh, as developer I am always careful to call something a bug.
And for these "bugs" my question is: Why not everyone have it? Why only a small group? Therefore I don't think that these are bugs but have to do with your installation.
Did anyone of your try a factory reset? Try out on a clean installation, which means without any settings changed, any app installed, any sd-card inserted?
Click to expand...
Click to collapse
You're a developer and you say that? Are you serious? I'm an expert user. Every platform I've ever owned for the past 30 years from the Commodore 64 to this Note 10.1 has had bugs, some minor, some major. Just like the 24-second touchsceen timeout bug I found and reported in the last firmware version. The new KK update is so new its still rolling out to users. I've already encountered two bugs for sure - the audio quality bug and the email bug I just described in the previous post. The audio bug has been confirmed and I believe the email bug I just reported will also be confirmed. The fact is that certain people are more adept at finding and reporting issues. It also depends on how you use the device and with what regularity. Are you suggesting that we sit on our hands and not report the problems we find? Please.
jaytee23 said:
Another bug I found so far is with the included Email app. I'm using it with my gmail account. The new version included with KK has an issue with sent mail. Specifically, it doesn't update the sent mail folder - at least for me. It used to work perfectly. Now when you send an email from the app, the email doesn't show up in your sent mail folder within the app. I have tried deleting all the email data on the tablet, and the cache, and set it up four times since KK and it it just won't show email you send from the tablet in the sent mail folder. Note, I'm not talking about email that is already in your sent email folder in your gmail account. I'm saying, send a new email from the tablet, and that email should immediately appear in your sent mail folder, but it doesn't. It doesn't ever show up there. Kind of a problem. Can anyone else confirm this? Send an email from the Email app and see if it shows up in your sent mail folder within the email app. Thanks.
Click to expand...
Click to collapse
I normally just use gmail but I setup the stock email app to test it for you. I set it up as a push account and sent a test email. It was briefly in the "Outbox" folder then it was sent out leaving the outbox folder empty. I then checked the Sent folder right underneath the outbox folder and it wasn't updated yet so I hit the refresh button in the top right corner and my test email showed up.
jaytee23 said:
Every platform I've ever owned for the past 30 years from the Commodore 64 to this Note 10.1 has had bugs, some minor, some major.
Click to expand...
Click to collapse
I never said that there are no bugs. I am only saying that not every issue is a bug. I mean when your are playing with the developer options (which normally hidden with a reason) then you should understand what yiu are doing and not call then probelms because of it a bug.
jaytee23 said:
I've already encountered two bugs for sure
Click to expand...
Click to collapse
No, I am not sure and that is what I am saying.
jaytee23 said:
Are you suggesting that we sit on our hands and not report the problems we find? Please.
Click to expand...
Click to collapse
I never did that. I only mentioned not to call issues a bug. This didn't help anyone. People who didn't have this problem begin to fear it and people who have will stop searching the real reason because it is a bug.
I mean what I see are already hundreds of downloads of KK and only 3 persons complaint the video "bug". Did you think that only 3 "power" users are watching videos?
---------- Post added at 08:36 AM ---------- Previous post was at 08:16 AM ----------
elzeus said:
and my test email showed up.
Click to expand...
Click to collapse
Same here and I checked it also with other KK devices and there it is the same, which is for me also normal. But maybe I didn't understand your problem?
elzeus said:
I normally just use gmail but I setup the stock email app to test it for you. I set it up as a push account and sent a test email. It was briefly in the "Outbox" folder then it was sent out leaving the outbox folder empty. I then checked the Sent folder right underneath the outbox folder and it wasn't updated yet so I hit the refresh button in the top right corner and my test email showed up.
Click to expand...
Click to collapse
Do you have an SD card inserted?
I just tried something where:
1) I deleted my email account from the client again
2) deleted the data/cache from the Email app
3) ejected my SD card
4) set up the account again in the Email client
5) sent a test email
6) sent email now shows up in sent email folder but only after a manual refresh
7) reinserted SD card
8) sent another test email
9) sent email still showing up in sent email folder, but only after a manual refresh (shouldn't have to do that) and it takes awhile.... hmmm....
I tried this because I was reading a thread in the 12.2 forum (http://forum.xda-developers.com/showthread.php?t=2670065) where a guy mentioned a similar issue. I thought I would try dismounting the SD card and setting up the account again... still not happy... still uncertain about this... something wonky here.
I'll try more tomorrow... must sleep now.
Chromecast systemui crash is pretty serious.
Lockscreen widgets are broken.
jaytee23 said:
Do you have an SD card inserted?
Click to expand...
Click to collapse
Yes SD card inserted 24/7 never removed it after the initial 4.4.2 recovery setup.
GldRush98 said:
Chromecast systemui crash is pretty serious.
Lockscreen widgets are broken.
Click to expand...
Click to collapse
Adding to the list, I could have sworn before I reinstalled 4.4.2 that my lockscreen widgets were working after upgrading from 4.3 but now I have no option to enable them in 4.4.2.
Elim said:
Same here and I checked it also with other KK devices and there it is the same, which is for me also normal. But maybe I didn't understand your problem?
Click to expand...
Click to collapse
I didn't have any problem with email I was tracing my steps for jaytee in case I did anything different from him in the way his email is setup. As for the list if they aren't bugs then what are they? People make bug lists so they can get fixed or so people can post workarounds. The only reason I enabled the developer options was to find a solution for the video lines...so far the disable overlay checkbox has worked.
elzeus said:
As for the list if they aren't bugs then what are they?
Click to expand...
Click to collapse
Maybe it is personal but I would call them problems and not bugs. The difference for me is that a problem is my problem and I have to find a solution or work-around (or someone else for me) and a bug came from Samsung and normally can only be solved by Samsung. A problem didn't have anybody, can be constructive be solved and create a positive atmosphere here in xda. A bug have anybody, can be solved only by experts and is something negative because the product didn't work like it should be.
Therefore I find good that you start such a list but I would more mentioned what you did before (how you get the update), which update, if rooted or not, what happens and what was expected and then if a solution or work-around exists.
Elim said:
Mh, as developer I am always careful to call something a bug.
And for these "bugs" my question is: Why not everyone have it? Why only a small group? Therefore I don't think that these are bugs but have to do with your installation.
Did anyone of your try a factory reset? Try out on a clean installation, which means without any settings changed, any app installed, any sd-card inserted?
Click to expand...
Click to collapse
jaytee23 said:
You're a developer and you say that? Are you serious? I'm an expert user. Every platform I've ever owned for the past 30 years from the Commodore 64 to this Note 10.1 has had bugs, some minor, some major. Just like the 24-second touchsceen timeout bug I found and reported in the last firmware version. The new KK update is so new its still rolling out to users. I've already encountered two bugs for sure - the audio quality bug and the email bug I just described in the previous post. The audio bug has been confirmed and I believe the email bug I just reported will also be confirmed. The fact is that certain people are more adept at finding and reporting issues. It also depends on how you use the device and with what regularity. Are you suggesting that we sit on our hands and not report the problems we find? Please.
Click to expand...
Click to collapse
You're both sort-of correct. There are pervasive "bugs" and situational bugs. @Elim is right, it's pretty clear that some of the issues being reported are situational bugs caused by some combination of elements that affect a subset of users. Add to that no two Android devices are configured the same way and it's easy to see how things that affect one user (or set of users) don't affect another. Some people rooted, some use tons of system/memory managers and battery boosters, some flashed over 4.3, and some are using a ROM from a different CSC than assigned to their h/w. All those things can cause issues of varying degrees.
Not everyone's having the battery life, Chromecast, and video lines issues so you can pretty much assume it's not the 4.4 s/w alone causing some folks to have problems. Like Elim said, if it were in the core ROM s/w everyone would be experiencing the issues equally. His advice was solid; do a restore through recovery and before loading any personal apps or settings see if the problem(s) still there. If it's not, it's something related to an individual configuration.
I don't have a problem with Chromecast or lockscreen widgets.
Sent from my SM-P605V using Tapatalk
KwestJones said:
I don't have a problem with Chromecast or lockscreen widgets.
Click to expand...
Click to collapse
Are you on official 4.4.2?
elzeus said:
Are you on official 4.4.2?
Click to expand...
Click to collapse
Yes... Got an official OTA update
Sent from my SM-N900P using Tapatalk

[Q] Notifications not working when phone is asleep

Hey everyone, has anyone else been having issues with Gmail notifications not working when the phone is locked or asleep. The notifications come in a few moments after I turn on the phone, but they don't come in when the phone is asleep. I checked every setting and it seems like it might be a hardware or software issue with the Note 4 that is preventing the notifications to come in during sleep. Anyone have any ideas as to how I can fix this. This was never an issue with my Note 3 and I matched every setting to it and it all seems to be the same.
aturyan said:
Hey everyone, has anyone else been having issues with Gmail notifications not working when the phone is locked or asleep. The notifications come in a few moments after I turn on the phone, but they don't come in when the phone is asleep. I checked every setting and it seems like it might be a hardware or software issue with the Note 4 that is preventing the notifications to come in during sleep. Anyone have any ideas as to how I can fix this. This was never an issue with my Note 3 and I matched every setting to it and it all seems to be the same.
Click to expand...
Click to collapse
Did you ever resolve this, i'm having the same problem with my new S6 edge. thanks
make sure background data isn't disabled for gmail and that you have either wifi always on or data on
floatingtrees said:
make sure background data isn't disabled for gmail and that you have either wifi always on or data on
Click to expand...
Click to collapse
all those are setup right, i suspect this is some bug with gmail's latest update or lolipop issue but still testing. I do know I'm not the only one
arf8 said:
all those are setup right, i suspect this is some bug with gmail's latest update or lolipop issue but still testing. I do know I'm not the only one
Click to expand...
Click to collapse
forgot to mention turning sync on, also did you disable background data for anything else like google play services? when I did cloudmagic stopped syncing emails for me, if that doesn't work try using a different client
floatingtrees said:
forgot to mention turning sync on, also did you disable background data for anything else like google play services? when I did cloudmagic stopped syncing emails for me, if that doesn't work try using a different client
Click to expand...
Click to collapse
yes way beyond baisic stuff
Update, i called samsung and had them create a ticket, the rep said they have not heard of this issue at all. Long story short if they come up with a fix it will be after 5.1.1 which carriers like ATT have not pushed out and that means it could be a year or longer before it is resolved. They do not work directly with end customers so we are out of luck basically. Frankly for me this is deal breaker and I might be returning my phone and going back to blackberry.

Question Pixel 6 pro-Google dialer

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.

Categories

Resources