This problem only exists for WeChat, my WhatsApp is fine. I have auto-startup enabled for both and even when I launch WeChat app I do not receive messages immediately, only after a few mins I see messages incoming but it could be from a day before or a few hours before. I am on the latest firmware V2.19.40.22 and have factory reseted my phone, also tried re-installing WeChat and cleared cache, same problem occurs. Anyone else having this problem?
Known issue and it has been reported many times in the Zentalk forum (Official zenfone forum) without any acknowledgement. We're unlucky to have picked up an Asus phone. It's my first and my last. Best thing is to wait until enough people report it and perhaps Asus will address it.
Related
hi, i got a problem with whatsapp.
I dont have any mobile reception (I use wlan, it's stable btw) in my room, so my friends only send messages over facebook or whatsapp.
But I have a huge delay problem, when I get whatsapp messages.
Sometimes I receive them without delay, sometimes with a delay of half an hour or so and sometimes I don't get any messages, until I open What's App and wait some minutes.
Do you know where the problem is?
I re-installed the app several times, cleared the cache etc.
rom installed: bigxie's 4.0.3 Build 9-2
kernel: franco #13
baseband: i9250XXKL1
thx in advance...
no idea ??
Sounds like WhatsApp server issues. They aren't pushing the messages to you immediately, probably some type of queve system.
Sent from my Galaxy Nexus using XDA App
Does it happen to other push notifications too? I have a similar problem with ALL push notifications and it is my router. I switch back to 3G and it pushes instantly.
Had lot's of delays with WA push notifications the last couple of days, too.
Install the new version released yesterday, it seems to have fixed things.
Okay thx!!!
What'sApp is known for having server issues. It just means a delay until it catches up. A pain yes, but it's still one of the better apps out there. It's not your phone.
They deliver 1.000.000.000+ messages per day, about 11.000 per second.
Hey all,
I've been a bit out of touch as I managed to lose my phone so was unable to use my 360 fully for a while.
I now have a phone back and am back to full use, the problem is now I seem to have a problem.
If I reply to a Whatsapp or FB Messenger message on the watch, it looks as if it has worked fine until I check on the phone when I realise there's no sign of the message I just sent.
Also, I've seen plenty of news and people telling my I can use tinder on the watch but all it seems to do is just 'open on phone' .
I wonder if these issues are related? maybe some sort of sync problem. I've reset the watch and reinstalled wear, FB messenger and tinder on the phone but the problem persists.
Thanks for any advice you might have!
All on my Zenfone 2. Starting today, in addition to never getting notified when receiving a message I found when emailing people I was trying to text they weren't getting my texts nor I theirs. After going through the helps apps one of the suggestions to do was a factory reset. Reluctantly I did that only to find that the problem persisted as well as realizing I could no longer connect to my WiFi which caused me not to be able to download all my apps that had been backed up. Haven't found any solutions as of yet.
Ever since December 23rd or so, when I first rooted my stock Nexus 5X, Google Messenger has been behaving strangely. Long SMS messages have seemingly random characters attached to the end of them, which do not show up on the sender's end. The most common is a "¿", but occasionally I get a delta ∆ on the end. I cannot find anyone else with this problem either here or elsewhere online. Does anyone have ideas? It's not necessarily a problem, but it is a mysterious inconvenience.
I am running the latest update of Marshmallow (stock ROM), with systemless root (SuperSU 2.61 I believe) and TWRP recovery. Nothing else out of the ordinary. This did only become a problem after rooting my phone, which may be part of the problem. Any help would be appreciated!
Edit: it should be noted that while these are valid characters, they do not appear when searched for with Messenger's built-in search function.
just to be sure: these symbols appear on your end after receiving a sms? in that case it would be interesting to know what phones/apps the sender of those uses.
if this is the case with sms you have written, it could be useful to know what keyboard/input method you are using. did you restore your sms' and/or the messenger app from a previous backup?
first thing you could try is clearing the app data and maybe de-/reinstalling possible updates of it.
interested to see how your case turns out, since i never heard of anything like this.
Broken303 said:
just to be sure: these symbols appear on your end after receiving a sms? in that case it would be interesting to know what phones/apps the sender of those uses.
if this is the case with sms you have written, it could be useful to know what keyboard/input method you are using. did you restore your sms' and/or the messenger app from a previous backup?
first thing you could try is clearing the app data and maybe de-/reinstalling possible updates of it.
interested to see how your case turns out, since i never heard of anything like this.
Click to expand...
Click to collapse
Yes, they are on my end. It has happened so far with iPhone and Android senders using their stock messages application. And I have already cleared cache/data for Messenger with no change. It is a most unusual problem. I may just try uninstalling and reinstalling the app.
(I am unable to insert image links, or else I would provide a screenshot)
OGNatan said:
Yes, they are on my end. It has happened so far with iPhone and Android senders using their stock messages application. And I have already cleared cache/data for Messenger with no change. It is a most unusual problem. I may just try uninstalling and reinstalling the app.
(I am unable to insert image links, or else I would provide a screenshot)
Click to expand...
Click to collapse
Also seeing this behavior occasionally, from both iPhone and Android senders. Haven't been able to figure out a pattern yet as it's only happened three times so far (three different senders, one time each). It's the strangest thing. I wish Messenger had some sort of bug reporting utility, since I've found several already.
Sent from my Nexus 5X using Tapatalk
plwalsh88 said:
Also seeing this behavior occasionally, from both iPhone and Android senders. Haven't been able to figure out a pattern yet as it's only happened three times so far (three different senders, one time each). It's the strangest thing. I wish Messenger had some sort of bug reporting utility, since I've found several already.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have switched to Textra indefinitely, as this does not solve the problem, but does support many features that Messenger is lacking. If you find a way to submit a bug report, I would be interested in that information
For months I have hardly problems with this android.process.acore has ended message in my cm11 rooted fire phone installed nano GAPPS (but even with other versions of GAPPS the Problem stayed the same). I have no idea what to do any more, flashed and backuped everything again and again, deleted and restored the contact-datas the way it is discussed in many forums. The problem disappears while disabeling the contact-storage, but this way I cannot use my Fire Phone for phoning from the contacs anymore much less using contacts in Whatsapp . The problem seems to come along with WhatsApp and Facebook and its Messenger, but once installed the problem android.process.acore does not disappear when uninstalling these programs. Anyone got an idea? Thanks a lot for your help!
That's strange, has there been any recent updates to your phone?, i don't know how long you've been on cm11 but amazon recently stopped supporting Facebook who also owns whatsapp. I know someone on stock whose messenger and whatsapp stopped working and the tech on mayday had to relay that to them. Idk if they stopped support through an update or some other means since I haven't been on stock for a very long time. My advice would be to take a logcat and post the issue in the cm11 thread if you can
<romario3600> Thanks for yor advice. I've been with CM 11 from the very beginning and I don't really remember when the problem started, might be like half a year before.. That's weird, for any reasons that android. access. accore disappeared now after uninstalling both facebook and its messenger. Didn't know that the support stopped and this might have caused it. I got a solution now with a third party facebook version by apache. It's working well until I found a solution for my problem.
I have still no idea...
Now the android.process.acore is happening again. I uninstalled all the apps (facevook and it's messenger) that caused the malfunction. Now I got another app called Immonet that claimed the same rights with synchronisation owitg contact data. I uninstalled this app with all data and even wiped the old folders. But the error promt does not disappear anymore I did not find anything all over the net anyone having the same problems that I do.. Anyone got an idea how to solve this one out? I'm so much disappointed,hardly thinking of buying another phone but I like this fire phone with CM11 a lot.
ticklisheye said:
Now the android.process.acore is happening again. I uninstalled all the apps (facevook and it's messenger) that caused the malfunction. Now I got another app called Immonet that claimed the same rights with synchronisation owitg contact data. I uninstalled this app with all data and even wiped the old folders. But the error promt does not disappear anymore I did not find anything all over the net anyone having the same problems that I do.. Anyone got an idea how to solve this one out? I'm so much disappointed,hardly thinking of buying another phone but I like this fire phone with CM11 a lot.
Click to expand...
Click to collapse
As a last resort if you have the time and effort to put in, id say revert to stock and do a factory reset the normal way using the fire phone's recovery. That should at least ensure that everything is wiped and back to default. After that try downloading and installing CM11 again, don't cut any corners where you might have to wonder if something went wrong. Once the systems boots properly try installing the play store as well as messenger and whatsapp and see how things go from there. avoid rooting the device until you are sure things work
I got another completely new fire phone, rooten CM11 now from the latest FireOS 4.6.1..1. and at the beginning everything worked fine up to now. Now I got the same android.process.accore message again on this completely different device. As this problems is not very common I got now the idea that it might have anything to do with the synchronisation of google contact and it's permission management with these programs that have the rights to read sync the contact storage. But no idea ehat it might be exactly. A while ago I deleted all my contacts on the Google server. Is it possible that the synchronisation got a problem now with my different devices that were once registered on the server with not always having the very same telephone directories? How to solve it if my venture is right?
I just solved this (I hope, so far so good) on my Sony Xperia Z2 tablet. I cleared data on any and every app that had anything to do with Contacts. I went right down the list in All Apps. If it used contacts, I cleared it. That meant Gmail and Hangouts, Messenger, etc.
Before I did this, I tried to write an email and litterally had the error with every single letter. Since I did this, I haven't seen it once. I wrote out an email address on a draft email and posted 2 posts (this will be the third) here. No error yet!
Not an expert. Just a user and fellow acore victim, sharing what worked for me. Though I have been in tech support for 17 years (just more of a Windows PC tech really).
Gabrielle
I will check this out on the weekend when there's some time for me doing so. Will tell you if it worked.