curious to see if any one else has this issue.
when I say (or even type) something to the affect of, "Read my text messages", Google app just force quits. When I try immediately again, I get the "Google keeps stopping" with choices of App Info, Close App, or Send Feedback. I have all permissions enabled, only Android Messages installed (thus being my one and only choice as the default messaging app). I have tried to disable the dns.adguard and disabling advance chat features. I have also tried other apps, but to no avail.
If I say, "read me my email", it properly lists and reads my latest e-mail messages.
so why is this not working for the messaging app?
I have the Pixel 3 on VZW with the latest 9.0 installed. I have using both the beta google/messaging apps and without.
this happens on both WiFi and mobile data. I do have a Huawei Watch 2 (Wear OS) running - and trying the same command through the watch yields similar undesirable results.
any help would be greatly appreciated.
thanks!
Related
Hmm so I downloaded 8sms as I thought it might be a suitable replacement. It looked great, just like the stock messaging app. Made it default. Came back and I just got a blank white screen that says "Loading conversations.". Rebooted and it looked fine. Then opened it a second time and again lost my conversations. Switched back to Hangouts and my messages were still missing after a reboot. Opened 8sms again and my threads were there, went back to Hangouts and my threads were there.
Switch back to 8sms and I get a notification for 8305 new messages. Opened the notification and it's again "Loading conversations".
Something very strange is going on with the 3rd party functionality in KitKat. In logcat I get messages like:
"The connection pool for database '/data/data/com.android.providers.telephony/databases/mmssms.db' has been unable to grant a connection to thread (###) (Binder_#) with flags 0x# for 150.003 seconds" where the #s are a bit different with each entry.
Running pure stock rooted here. Any thoughts? I know that there is some sort of database transfer when switching in and out of Hangouts, but this is really disconcerting.
Given this instability, I guess I will be back to Hangouts for now until I can figure out what will work consistently.
Any thoughts on this, anyone?
Sent from my Nexus 5 using Tapatalk
Hi,
Could you please check your mms settings are correct?
http://8s.ms/mms-settings
It shouldn't be related, but I've heard from other users of weird phone behaviour when this is not configured correctly.
You might also want to try an uninstall-and-reinstall as well. There are a few reports of phones also behaving strangely which then fix themselves after a second install.
Other than that ...
"The connection pool for database '/data/data/com.android.providers.telephony/databases/mmssms.db'
Click to expand...
Click to collapse
That sounds like an Android problem.
That's the database which stores the sms and mms messages. You can think of it as a "server" and 8sms (and Hangouts) are just clients to the server.
Hence, the database is managed by Android, not by 8sms (nor Hangouts) which is why I think this is an Android problem .
I know that there is some sort of database transfer when switching in and out of Hangouts, but this is really disconcerting.
Click to expand...
Click to collapse
There is no "database transfer". Both apps read from the same database, but only one (the default sms app) is allowed to write to it.
When the default sms app is changed, no data copying takes place, it's just a change of a simple string setting (to remember which is the default sms app and is allowed to write to the databse), and is instantaneous.
Hence again, this is why I think it's an Android problem.
Perhaps you have file system corruption or a problem with your Nexus 5?
Thanks, yes my MMS settings are correct. I would be surprised to see any corruption as I only just got this phone Friday. Anyways I haven't had any problems keeping it set to Hangouts.
Sent from my Nexus 5 using Tapatalk
Well, please try the reinstall I suggested above.
Then, another suggestion ... what about you force stop both apps (8sms and Hangouts) before you change the default sms app (via the Android settings)?
Perhaps in your previous switch, Hangouts was still writing data to the messages database?
(Just a random wild guess)
didnt they change how sms/mms worked in 4.4.
I think the app needs to be updated for it to be compatible no? correct me if im wrong, probably i am.
expertzero1 said:
didnt they change how sms/mms worked in 4.4.
I think the app needs to be updated for it to be compatible no? correct me if im wrong, probably i am.
Click to expand...
Click to collapse
Yes, but 8sms has already been updated to work in 4.4, and there are lots of instances of it working on other Nexus 5 phones.
bengtan said:
Well, please try the reinstall I suggested above.
Then, another suggestion ... what about you force stop both apps (8sms and Hangouts) before you change the default sms app (via the Android settings)?
Perhaps in your previous switch, Hangouts was still writing data to the messages database?
(Just a random wild guess)
Click to expand...
Click to collapse
OK: Tried uninstalling/reinstalling 8sms. Then force closed Hangouts and 8sms each. Then changed default sms app via Android settings.
Then launched 8sms. Everything looked fine. Then opened a conversation and everything was blank. Backed out to the conversation list and got "Loading conversations" again.
I have taken a logcat filtered for anything mentioning sms. Removed identifying phone numbers from it. I have attached it here, starting with the time when 8sms is reinstalled. You can see at 01:47:05.776 the SMS app is switched to Messaging (8sms). At time 01:47:52.886 the first SQLiteConnectionPool error message appears. The messages appear every 30 seconds.
Oh! Interesting. After 10 minutes (01:57:23.016) the last error message is seen. Two seconds later we see an "onQueryComplete finished" message from 8sms. From this point on I was able to open 8sms and see my messages again.
So for a span of 10 minutes, something went on that was locking me completely out of seeing messages, and then it stopped and everything worked. I rebooted to see one more time if it was still working, and yes it does. Perhaps in order to reproduce this error you need to have a big pile of messages already present. Obviously not a lot of Nexus 5 users have this because they just got their phones, but I do because I restored a large archive of messages from my last device.
Hi,
I recognise the query "UPDATE sms SET seen=? WHERE seen=0". It's 8sms marking the messages or threads as seen. Perhaps you had a lot of messages or threads that weren't marked as seen.
Or else, maybe there was a big delay because the database was optimising itself for it's first run or something like that.
In any case, it looks like the problem is fixed now?
Yes it looks like it. However it might be worth looking into whether this problem commonly occurs when switching Kitkat to your client while a large number of messages is present. I believe I had something on the order of 17000 messages in a hundred or so threads. Yes I should probably clean up a bit
Sent from my Nexus 5 using Tapatalk
I had a similar issue. Deleted all my messages (kept the backup file though) and uninstalled and reinstalled. It worked fine.
I plan on restoring over the next few days doing it in chunks.
So, ever since the N update on my S7 and now on the S8, my email doesn't push/sync right away at all anymore. I have to go into the email for it update. I'm not sure whyy it's doing this. I haven't set it up that way, have background data allowed, and don't have any battery saviors set up to do this...
Any ideas on this why this is happening?
Nougat's overly aggressive doze is the cause here. Fix: https://androidtutorial.net/2017/05/02/fix-delayed-push-notifications-galaxy-s8s8/
The option under Special Access you want to look at is Optimise battery Usage.
I have the same issue. I have gmail set so that it is NOT Optimized for battery. I still don't get gmail updates (and therefore no notification) until I open the app (usually). Sometimes I do get the notification soon after the email is sent to me. Rather random.
After messing around for a while, I think it is a no notification thing and not a lack of synchronizing the emails. If I send myself a gmail, I get no notification, but I can look in my google account and see where gmail has synchronized. Then I go to gmail and the message is there.
^yep, could be related...but how to resolve?
Possible Solution - Worked for Me (So Far)
galaxys said:
^yep, could be related...but how to resolve?
Click to expand...
Click to collapse
So, I solved it by going to the app manager and disabling the gmail app. Since it is a system app, it doesn't uninstall it, but reverts it back to some previous version. That version has been giving me the appropriate notifications for every email I have received since.
I think I will look at disabling updates for gmail for a while.
Smithfolk4 said:
So, I solved it by going to the app manager and disabling the gmail app. Since it is a system app, it doesn't uninstall it, but reverts it back to some previous version. That version has been giving me the appropriate notifications for every email I have received since.
I think I will look at disabling updates for gmail for a while.
Click to expand...
Click to collapse
I deleted data for the app. That also fixed the problem (for now anyway)
This has been an ongoing issue for me for over a year. It was an issue on this phone, my S7 edge and Note7.
Often I will see an email on my phone, read and archive it, then go about my business. Several hours later I go into Gmail on my PC and that email is still sitting there, unread.
Actually sending out an email on the phone seems to make the sync update, but other actions like reading, moving, or deleting emails doesn't. I've had times where my emails were still unread on the Gmail website 12 hours after reading them on the phone. I have the app's battery optimization settings turned off, and I have even gone into the app several times during that period and pulled down to check for new messages. It's pretty awful that the sync has such serious issues and nobody is fixing it.
Deleting the app's updates doesn't work for me. It might fix the issue briefly, but it always comes back pretty quickly, even without any updates to the app.
The only thing that fixed the issue for me was installing an app called something like "Gmail Push Fixer". It worked wonders on my S7 edge. Unfortunately, the app requires root so it isn't an option on my Snapdragon S8+.
My watch suddenly stopped being able to send an SMS using 'ok google', 'send a text to <contact name>' . it now tells me "Something went wrong. That's not available on this device". I have un-installed 'google' and reinstalled it on my watch. I have factory reset the watch, and installed a new messenger app on my phone/watch (google message) etc. Nothing is working unfortunately. Unsure what else to do.
Any ideas?
I have the same problem! Happened since friday, before it always worked fine. Also other messages like whatsapp same problem...i guess it has something to do with an update of play services or google assistant....
Replying fortunately still works. But initiating new messages not...
glenner05 said:
I have the same problem! Happened since friday, before it always worked fine. Also other messages like whatsapp same problem...i guess it has something to do with an update of play services or google assistant....
Replying fortunately still works. But initiating new messages not...
Click to expand...
Click to collapse
Exactly same. I also went over all of the security settings etc for each app on wear and phone. I use my watch a lot to initiate sms conversations so hopefully this will be fixed soon.
I have an older model of the Huawei Smartwatch and just recently I'm experiencing the same thing-- however my husband's newer version (but not Smartwatch 2) can still send text messages and make voice calls. I'm hoping this Google update has not my Smartwatch obsolete.
Same issue, but with phone not watch (SOLUTION)
I had this same exact problem... started about a week ago. I finally sat down the other morning and spent a few hours trying ever solution I could find until BOOM... I found the issue, the "Google Web and App Activity" was turned off!! I hadn't been in my Google Account setting for years, so my guess is that this was a recent Privacy Policy update rolled out by Google recently. Anyway, here are my notes on how to turn it back on for yourself (provided you have permissions to manage your own Google account):
Go into Google Home App
Hamburger Menu
Settings
Google Assistant Settings
Prompted about "Web and App Activity" settings that needed to be turned on, I had never turned them off, but they were off, I had previously logged into Google Admin for the account and turned it "on for everyone" earlier, so maybe do this first.
Then was prompted with a "I'm In" pop-up. I clicked on that button I was taken to the standard Google Account Setting Page.
I exited and tried "ok google" again, it worked
the google app updated on my watch today and now the issue seems to have been resolved.
Hi,
Google Messages (both the beta and the standard version) keeps crashing. On my Fold 1st gen, I never had any issue...
For now I reverted back to Samsung messages but the RCS doesn't work (even though the setting is there) so I'd rather go back to Google Messages...
Anyone else having the same issue?
I tried clearing both the Google Play Services and Google Messages storage, doesn't make a difference as after a few seconds I get the Android message that Messages keeps crashing.
For what it's worth, I was able to fix my issue by installing the Google app "Carrier Services" which was missing from my Fold2 and is apparently used by the RCS protocol of Google Messages...
Now it's all good
Hi,
I have the IQOO Neo5 (chinese variant of the IQOO 7).
I uninstalled Vivo's browser (and basically most of their apps). When I'm trying to open linked from SMS messages I get an error saying "feature is not available". I obviously did set a different browser as a default one in the settings (also tried to do that again).
Did anyone encounter that?
Thanks
I have uninstalled the browser in indian version Iqoo 7 ..no such issue..i get the option to chose browser..Bromite as my default one..
It just does not work with Vivo's messaging application. I ended up just using another one, which is actually quite a lot better (Textra). This app does recognise the new default browser.
Did you check this option, issue is resolved by first option
Is this the Indian variant ROM? In my Chinese one I cannot have an empty option.
An issue I had while traveling after I had uninstalled the browser is that I had issues with WiFi networks that requires the opening of a log in page. When clicking on the notification that says that I need to log in, nothing has opened.
I now realised that I might have needed to let my new default browser (FF) permissions to auto launch. That might have solved that. But I have no way of checking it out right now as in my living area I have no networks that require a log in via a browser.
Yes..its the Indian variant...i would suggest to factory reset if you're facing trouble...