Hello,
I am curious if anyone has ever found a definitive solution to this issue that has plagued android since Gingerbread. I have been on multiple phones, multiple brands, multiple revisions of the software and have seen this issue on every single one. Here is a list of the phones I have had:
OG Droid (2.2-2.3)
Droid 2 (2.3)
Samsung Charge (2.3)
Droid 4 (2.3-4.2)
Galaxy Note 3 (4.3-4.4)
The issue is:
Your friend sends you a message and they receive a notification that you received it. However, your phone neither alerts you to a message received or shows it in your inbox. However the message IS getting to your phone, because if you install GhostlySMS it catches incoming messages that don't make it into your inbox. So I must then conclude it is a database writing error or something of the like? Is there someone that can help me? I can reproduce the issue rather easily and can grab a logcat if needed.
I am currently running a rooted Verizon Note 3 (running the stock slot, but safestrap is installed) and am getting hardly any of the texts my wife sends me, and I miss quite a few from my father. She is running a rooted Galaxy S4 with Safestrap and Eclipse ROM.
I have searched and searched but so far all I can find are a bunch of "try this, try that" or "factory reset" without any real solid fix. I would like to find a real solution, not a workaround or a factory reset (if possible). I would especially love to know the root cause.
I know I may be asking for the world here, but hoping we could pool our collective consciousnesses to squash this issue once and for all!
Thanks!
screwedbyexisten
So I did a factory reset (actually I completely wiped the entire stock slot, odin'd stock MJE, and then followed Beanstown's guide to get to KK using towelroot. The issue has gone away. However I have my SMS database and so far as I can tell there is nothing wierd. But I am not a DB admin by any means.
I would love to find out why Android eventually loses its ability to reliably write new SMS to the database after a while.
Anyone have any ideas?
Screwedbyexisten
Sent from my SM-N900V using XDA Premium 4 mobile app
Hi,
My s5 has been randomly rebooting. Sometimes, it has happening when I am on the call, or in the mid night. Is any one has the same issue? Is the phone defective or hardware problem? My phone is never rooted.
jc_hwz said:
Hi,
My s5 has been randomly rebooting. Sometimes, it has happening when I am on the call, or in the mid night. Is any one has the same issue? Is the phone defective or hardware problem? My phone is never rooted.
Click to expand...
Click to collapse
My wife got hers a week ago and has till this Friday to take it back. This started happening a few days ago Also. Random. I know she also got that security update just a couple days ago
Sent from my HTC One_M8 using XDA Free mobile app
jc_hwz said:
Hi,
My s5 has been randomly rebooting. Sometimes, it has happening when I am on the call, or in the mid night. Is any one has the same issue? Is the phone defective or hardware problem? My phone is never rooted.
Click to expand...
Click to collapse
I have been having the same issue. I have had the phone since release and haven't had any problem, until about a month ago. It has rebooted a few times randomly. I am completely stock non-rooted.
I got one time today when I opened the YouTube app. I uninstall the update for the YouTube, and see what is going on
So I've noticed this happening for a few weeks now. Thought something was wrong with the phone and did a warranty replacement. New phone (not referb) does the same thing, just not as often. I think maybe it's an app running in the background now that had a bad update. I'm in the process of removing apps to see if it still happens.
1sae said:
So I've noticed this happening for a few weeks now. Thought something was wrong with the phone and did a warranty replacement. New phone (not referb) does the same thing, just not as often. I think maybe it's an app running in the background now that had a bad update. I'm in the process of removing apps to see if it still happens.
Click to expand...
Click to collapse
It has happened last mid night again. In today moring, I found my phone restart one time, because I saw the popup notice for reminding the back cover that means the phone restart already. Please tell us what happen after you remove the apps. I think it is the software problem rather than the hardware problem. I don't want to get replacement phone because it is refurbished phone.
jc_hwz said:
It has happened last mid night again. In today moring, I found my phone restart one time, because I saw the popup notice for reminding the back cover that means the phone restart already. Please tell us what happen after you remove the apps. I think it is the software problem rather than the hardware problem. I don't want to get replacement phone because it is refurbished phone.
Click to expand...
Click to collapse
Well I'm still trying to determine which app is causing it. For all I know, it could be the firmware T-mo pushed out prior to the latest one. T-mo says they haven't had reports on this issue so I don't want to blame the FW right off the bat. I have ruled out about 70% of my apps and right now have about 5 uninstalled and phone hasn't restarted in 3 days. Below is are the apps I have yet to try and the ones currently removed.
Current Removed:
Code:
'Disable Increasing Ring'
'netflix'
'uber'
'hbo go'
'battery widget'
'2x rdp client'
'pandora'
Yet to try:
Code:
Google Maps
Facebook
Chrome
chromecast
hangouts
tinder
lookout security
Touchpal Keyboard
Reuters
Beep'nGo
Might help if you let me know which ones you have in common above. FYI, I also tried removing my sd card like I saw in a few forums. Also, Tmobile says they don't give you referb phones. They give new phones that were returned to the store within a few days. So openbox, mine looked perfect.
1sae said:
Well I'm still trying to determine which app is causing it. For all I know, it could be the firmware T-mo pushed out prior to the latest one. T-mo says they haven't had reports on this issue so I don't want to blame the FW right off the bat. I have ruled out about 70% of my apps and right now have about 5 uninstalled and phone hasn't restarted in 3 days. Below is are the apps I have yet to try and the ones currently removed.
Current Removed:
Code:
'Disable Increasing Ring'
'netflix'
'uber'
'hbo go'
'battery widget'
'2x rdp client'
'pandora'
Yet to try:
Code:
Google Maps
Facebook
Chrome
chromecast
hangouts
tinder
lookout security
Touchpal Keyboard
Reuters
Beep'nGo
Might help if you let me know which ones you have in common above. FYI, I also tried removing my sd card like I saw in a few forums. Also, Tmobile says they don't give you referb phones. They give new phones that were returned to the store within a few days. So openbox, mine looked perfect.
Click to expand...
Click to collapse
I just do some research online. Many articles are talking about that the android 4.4.2 has randomly reboot bug. I think this the common bug for the 4.4.2. Hopefully, the 5.0 is rolling out for international version. I think t-mobile will update the s5 to 5.0 soon.
Its the 4.4.2 firmware. Its because of all the apps updating to the new lollipop 5.0 but where still on kit Kat. Remember now these apps are set to run on art now so i believe there conflict between the dalvik thats the norm. On 4.4.2. I noticed if i run my SM-G900T 4.4.2 in art mode the rebooting stops. So at the end of the day this means when 5.0 is released to our S5 the reboots should stop. If your bothered by the reboots just run the 4.4.2 in art mode. Good day☺
Sent from my SM-G900T using XDA Free mobile app
beachbum40 said:
Its the 4.4.2 firmware. Its because of all the apps updating to the new lollipop 5.0 but where still on kit Kat. Remember now these apps are set to run on art now so i believe there conflict between the dalvik thats the norm. On 4.4.2. I noticed if i run my SM-G900T 4.4.2 in art mode the rebooting stops. So at the end of the day this means when 5.0 is released to our S5 the reboots should stop. If your bothered by the reboots just run the 4.4.2 in art mode. Good day☺
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
I just turn off the VoLTE, and the phone runs for 10 days without any reboots. Do you think it is the problem of the VoLTE?
jc_hwz said:
I just turn off the VoLTE, and the phone runs for 10 days without any reboots. Do you think it is the problem of the VoLTE?
Click to expand...
Click to collapse
Could be.? I'm just making an educated guess that it's the fact that when our apps like YouTube, Gmail ,ect.. updated it seems that's when my reboots started. Volte could be a cause to. Your guess is as good as mine. But I truly believe it's the fact that the updated app where modified to art and 4.4.2 is dalvik. ?? I'm sure when the 5 update comes this will be resolved ☺
Sent from my SM-G900T using XDA Free mobile app
Will stock 4.4.2 unrooted run art? How would I enable that?
chazel3 said:
Will stock 4.4.2 unrooted run art? How would I enable that?
Click to expand...
Click to collapse
1.) Go into Settings, and About Device. Where it says: Build number press on this over and over again until it gives you the Toast message: Developer Options Turned On (something to that effect).
2.) Go back into Settings, and just below Security and above About device, you will see Developer options. Open this.
3.) 4th Item down is: Select runtime system. It should say: Use Dalvik. Change this option to: Use ART. It should work for a little bit, then Reboot your phone.
4.) All done!
Note: If you plan to Root your phone, and use Xposed, it is NOT compatible with ART runtime. If you plan to stay unrooted, or not use Xposed if you do root, then you are fine. You can always switch back if you decide to do this.
For almost 3 years now, around the time I purchased my Nexus 6 in December of 2014, I've had delayed notifications. I always thought it was a Nexus 6 issue but it seems I was wrong.
Any help at all would be greatly appreciated. Thank you!
Having recently purchased a Note 8, one thing I was really looking forward to was no longer having these delayed notifications. From the moment I set everything up, the issue was and is still present - even on a brand new, unmodified Note 8 purchased directly from my carrier (Telstra, Australia).
This has lead to me to look further into the issue and to finally get to the bottom of what might be causing it and hopefully, get it fixed.
From what I can tell, pretty much anything that uses Google's Cloud Messaging, which I beleive is everything from Gmail to Facebook, Google+ and many others, the notifications will be delayed. Sometimes only a few minutes, sometimes much longer.
Anything that doesn't rely on GCM works perfectly fine. For example, if I use Nine (an Exchange client app) and connect to an Exchange server, those notifications are always perfect. I'll get notified within seconds of receiving the email.
My partner, who has the exact same phone (Note 8) as well as Gmail and Facebook setup, receives notifications instantly (within seconds) and has never had the issue on previous Android devices either. So it's not a carrier issue, nor a WIFI issue, nor a phone issue. It is something directly related to my Google account.
Has anyone ever come across this issue that has been able to successfully resolve it? I've seen a couple of apps on the Play Store that apparently let you fix the issue but you need to be rooted in order for the apps to run. This is simply not an an option.
Given all testing points to something Google Account related, where would be the best place to start looking for a fix?
NOTE:
- I don't use any battery optimisation or task killer apps nor anything related. Never have.
I've come across the following information. It appears as though it may be something to do with this: https://productforums.google.com/forum/#!msg/nexus/fslYqYrULto/lU2D3Qe1mugJ
Although this looks promising, it doesn't really explain why it would affect some and not others. My partner who is using the same phone with the same carrier, connected to the same WIFI networks doesn't have the issue.
Nucleotide said:
Although this looks promising, it doesn't really explain why it would affect some and not others. My partner who is using the same phone with the same carrier, connected to the same WIFI networks doesn't have the issue.
Click to expand...
Click to collapse
I've never had this issue before, but I've had friends that ran into issues similar to the one you've explained. I'll be sure to ask them what they did to resolve them, and get back to you when I know!
WillyWilliams said:
I've never had this issue before, but I've had friends that ran into issues similar to the one you've explained. I'll be sure to ask them what they did to resolve them, and get back to you when I know!
Click to expand...
Click to collapse
Thank you!
I haven't made much progress here however, I can confirm my carrier is actually taking the time to do some thorough research themselves and ensure there is actually nothing wrong in the background.
Hello,
I asked this question on reddit, and was referred to this forum, so I hope someone might be able to help.
Every time I try to open my LINE app (Galaxy S7, stock 7.0 Nougat, unrooted), it says "LINE has stopped" and I am presented with the option to restart it or submit feedback. When I restart, it changes to "LINE keeps stopping" and only lets me send feedback.
I've tried everything short of uninstalling, including waiting since February for my phone to get an Android update. But it hasn't helped.
When I contacted LINE support, they said it was a known issue with Android phones and they were working on it, but none of the updates since have helped things. Is there a way to fix the app without uninstalling?
I've had this on my phone since I got it, nearly 2 years ago, but neglected to backup my chats, which are now inaccessible to me. So I'd very, very much prefer to find a way to preserve the years of chat history I've accumulated somehow. Can anyone point me towards a guide or program that can help me extract this data from the app without it opening?
Thank you.
I'm using a Moto G5 Plus and everything was fine as I was on Android Nougat. But having taken the offered upgrade to Android Oreo I've had to iron out a few problems. The biggest problem which to date I've not been able to iron out is the disappearance of the voicemail icon to let me know that someone has left a message. I inquired with Moto via their Facebook page and of course they suggested that I contact my carrier. I contacted the carrier, Cricket, and they only offered to reset my voicemail which didn't really do anything. I've asked on a few Android related boards one of which suggested I do a factory reset after the upgrade to clear out any remnants of the old OS. Since then I've done a second factory reset. The voicemail icon seems to have come back for a bit but has gone again. One user suggested using Nova Launcher and Tesla notifications which is fine as I do use Nova Launcher but it'll give me a count that someone called but no indication of whether or not there's a voicemail in the inbox.
You should also know that I don't use the stock dialer, but rather a third party dialer called TruePhone https://play.google.com/store/apps/details?id=com.hb.dialer.free and I think I have it set up correctly as it has a few selections about how to handle missed calls. I've also been tinkering with the notifications in the stock dialer and have reset to all the apps more than once. I've at a loss about what to do because I just really want to know when someone has left a voicemail, missed five phone calls yesterday alone two of which were important... I regret taking the upgrade from Nougat to Oreo, I thought Oreo would be fun but it's been a chore, and this experience has made me nostalgic for my old dumb Moto phone from way back when which I never had a problem with...