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
Related
Howdy,
Before I upgraded to CyanogenMod 9.0, I would get a Google Voice message notification for a text message. I'd go into the web version of Google Voice, answer the text and then after a bit, the notification would go away on my phone.
Now switched to CM9 and the notification doesn't go away unless I answer the text on my phone or clear it out on the phone.
I've tried GummyNex and CM9 and they both do it.
Has anyone else seen this? I've done the thing where I've uninstalled GV, did the *73, deleted all the Verizon VMs and the reinstalled GV but it still does it.
Don't think its related to your ROM as I'm having the exact same issue on stock 4.0.4 and have always been on stock. Seems to have started a couple weeks ago....
Been pulling my hair out trying to figure out what's going on and was about to start a thread myself asking if anyone else had the issue. Thought I was just crazy at first, but I know for a fact this is not how the app acted before. I've tried changing all kinds of things for my browser use of voice.google.com, deleted/re-installed the app, and nothing works.
I'll be texting using just the browser for a bit and look at my phone and I'll have a notification for "25 Google Voice Messages" or whatever. They never clear. I notice that when opening the GV app to the thread I'm texting in, it hasn't synced in the background, and takes a few seconds for the messages I had sent to show up in the thread. It seems as though Google Voice isn't getting background sync anymore.
Aww man So it was just highly coincidental that it happened around the same time I switched over to a different rom.
It's surprisingly frustrating for such a little thing. I just use it so much that it forces me to check the phone and clear it manually to make sure I don't *actually* have a new message when I'm using both my phone and the web app.
Argh.
Yeah - nothing I've found has fixed the issue.
Seijin said:
Aww man So it was just highly coincidental that it happened around the same time I switched over to a different rom.
It's surprisingly frustrating for such a little thing. I just use it so much that it forces me to check the phone and clear it manually to make sure I don't *actually* have a new message when I'm using both my phone and the web app.
Click to expand...
Click to collapse
Yes I think it's actually a coincidence as I said I've been on stock and it all of a sudden stopped working as it was. This is just really weird because there's been no update to the app or anything.
It's extra frustrating because Google Voice is my primary #, so I'm doing about 99.9% of my texting with it, and really enjoy being able to use voice.google.com. Dealing with clearing GV notifications every time I pick my phone up is very lame.
I don't believe I'm experiencing this, gv on GSM nexus, stock 4.0.4 rooted. Straight talk tmo mvno
Sent from my Galaxy Nexus using Tapatalk 2
I don't currently have this with my yakju 4.0.4 OTA stock ROM, but I have seen it before on this phone and every other phone I've owned across stock & custom ROMs. Fairly confident it's a problem with the app itself
@crachel - are you on cdma or gsm?
crachel said:
Fairly confident it's a problem with the app itself
Click to expand...
Click to collapse
What could it be though? I've done everything short of a factory reset. Nothing about the app itself or the settings I used changed and it started happening out of nowhere.
Seijin said:
@crachel - are you on cdma or gsm?
Click to expand...
Click to collapse
GSM
martonikaj said:
What could it be though? I've done everything short of a factory reset. Nothing about the app itself or the settings I used changed and it started happening out of nowhere.
Click to expand...
Click to collapse
I don't know.. I agree though that the problem just comes and goes, which is odd. Just a couple weeks ago they weren't clearing for me, but right now it's working fine. I remember thinking that's it's ridiculous this happens on stock firmware
crachel said:
I don't know.. I agree though that the problem just comes and goes, which is odd. Just a couple weeks ago they weren't clearing for me, but right now it's working fine. I remember thinking that's it's ridiculous this happens on stock firmware
Click to expand...
Click to collapse
Even moreso ridiculous if this is a known issue and they haven't addressed it even with these several early 2012 updates to the GV app, which made it a lot better overall in UI and UX. I just don't see how it can come and go with no changes whatsoever to your settings.
Mine definitely does the same thing... I thought it used to clear them for me, but I wasn't sure, and figured I was just thinking of how Google Talk clears the messages.
Not a huge deal to me, but it would definitely be nice if they would fix this. Our best bet is to make a post on the help forums with a bunch of posts in it.
xur17 said:
Mine definitely does the same thing... I thought it used to clear them for me, but I wasn't sure, and figured I was just thinking of how Google Talk clears the messages.
Not a huge deal to me, but it would definitely be nice if they would fix this. Our best bet is to make a post on the help forums with a bunch of posts in it.
Click to expand...
Click to collapse
If I get some time I'll put up a bug report on Google Groups/Google Code.
Edit: Nevermind! Someone's on it already from February: https://code.google.com/p/android/i...on&colspec=ID Type Status Owner Summary Stars
I'd appreciate if you're having this issue to star and comment there (as well as here).
martonikaj said:
If I get some time I'll put up a bug report on Google Groups/Google Code.
Edit: Nevermind! Someone's on it already from February: https://code.google.com/p/android/i...on&colspec=ID Type Status Owner Summary Stars
I'd appreciate if you're having this issue to star and comment there (as well as here).
Click to expand...
Click to collapse
Thanks for the link!
If anyone has a chance, they should make a post in the Google Voice forums here (I'll try to do it later when I have a chance if no-one else gets to it): http://productforums.google.com/forum/#!categories/voice/using-google-voice-on-a-mobile-device. I heard that Google Engineers do monitor / read these sometimes, so if we all post in a thread there is a chance it will get read / fixed.
I really wish there was a better way to get stuff like this fixed.
Bit late to the party. Just wanted to chime in that in my experience I don't think I've ever seen the GV notification clear itself after checking the web interface on my computer.
I've been using android for a year now and have gone through 3 phones and the asus transformer tablet. My current phone is running a CM9 based rom, but still it doesn't clear these notifications.
Man, I'd love it if it did.
Note: I think that if you use the GV widget, you will see that the notification on the widget DOES clear after checking the web interface (or at least it did in GB because I just tested this on my current phone and widget doesn't clear it either). I suppose this means that GV is pushing the "read" status of an sms to our phones. The notification on the notification bar, however, still persists despite this.
EDIT: Given my last test on my current phone, it looks like the widget doesn't clear the notification like it used to on GB. It looks like it is, in fact, a syncing issue.
LeoBloom. said:
Bit late to the party. Just wanted to chime in that in my experience I don't think I've ever seen the GV notification clear itself after checking the web interface on my computer.
I've been using android for a year now and have gone through 3 phones and the asus transformer tablet. My current phone is running a CM9 based rom, but still it doesn't clear these notifications.
Man, I'd love it if it did.
Click to expand...
Click to collapse
I can confirm that it actually did used to clear when viewed on another device, and this is the intended action. It should work exactly like an IMAP e-mail account (say, the GMail app). If you view a message on the device or in a web browser, it is cleared as read on the other. Google Voice used to do the same, and stopped doing so randomly. It's completely a backend problem.
Really wish they would fix this. Still happening on JB. Very annoying for those of us who text from the web all day.
xdp said:
Really wish they would fix this. Still happening on JB. Very annoying for those of us who text from the web all day.
Click to expand...
Click to collapse
Still a problem, go over to the google group link posted above and star the issue to (hopefully) increase it's priority and visibility:
https://code.google.com/p/android/i...s Owner Summary Stars&groupby=&sort=&id=25301
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!
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
I'm not sure if this is a Oreo issue or not, as soon as I got the phone I updated it to Oreo and wiped it. When I go into my call log and try to view the details of a call, the app crashes non stop no matter what I do. I can go into either Contacts app and look at a contact and get call details there just fine. Anyone have any ideas? I went to the phone app and cleared the app cache and data but its still doing it.
Also, anyone know why Razer duplicated what seems like random apps? Calculator, Contacts?
Can anyone looking at this at least try it and report back? I use call details a ton for keeping track of call time and right now its a huge pain in the butt.
I am reporting in. I have come across this bug. Honestly we should report it on the Razer insider forum....
Alright I'll get on there and report it too.
Yeah, same thing is happening to me as well.
They are wanting me to upload a bug report which I'll be doing sometime later today. The thing that really sucks, the phone app doesn't appear to be listed on the play store so they will have to issue a system OTA, which I'm assuming is going to take longer.
I also just noticed, voicemail notification cause the dialer app to crash. I have 4 voicemails I was not notified about.
I'm almost positive that I've gotten voicemail notices just fine.. but I'll test this later today to see.
Anyone get a fix or update on this?
gatorgal88 said:
Anyone get a fix or update on this?
Click to expand...
Click to collapse
Are you still experiencing this on O MR1?
All of these issues are fixed according to some users on XDA or the Razer forum. I wouldn't know cause I sent mine back. Hopefully the 2nd one is a little less of a mess.
lonetormenter said:
Are you still experiencing this on O MR1?
Click to expand...
Click to collapse
My phone is not experiencing a problem. My sister, however, started having the problem after upgrading to Oreo and she is up to date and still has the issue.
Very bizarre.
We have cleared cache and data and no change. She is currently using a 3rd party dialer in the mean time.
gatorgal88 said:
My phone is not experiencing a problem. My sister, however, started having the problem after upgrading to Oreo and she is up to date and still has the issue.
Very bizarre.
We have cleared cache and data and no change. She is currently using a 3rd party dialer in the mean time.
Click to expand...
Click to collapse
Problem solved. She factory reset her phone and all is good!
Oops. Didn't see all the other replies before replying. Couldn't delete post so had to edit.
I have not experienced this bug, I'm on latest firmware O MR1
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.