Related
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...
Alright, so I was trying to use a program that some other people have said work fine but it wouldn't work, so I figured I would unroot/reroot and see if it helped. I restored the phone to factory settings, used the instructions that are readily available here and other places to unroot my phone and rooted it using the manual method (just like I did the day I got my phone) and tried to set everything back up, but have run into a few problems.
1) Text messaging
-I have used Handcent for a long time on old phones, and used it just fine on this phone, but when I got my phone set back up, texts were coming in from the wrong people. I would get a text from PersonA, but it would show up as PersonB and when I responded it would go to PersonB. The only way that I could respond to PersonA was to back out, go into the people app, choose PersonA and text them. When I did this, it would take me into the exact same thread but have PersonA's name at the top now. When PersonA responded, it would show up as PersonB again and I would have to do it all over.
2) Google Wallet
-Was working fine, even used it at McDonald's, but now when I try to load it up for the first time, it sits at a black screen until eventually it says "Wallet is not responding. Would you like to close it? (Wait) (OK)"
Oh, and the program that I originally went through all of this for is still giving me the same error about not being able to locate a partition to remount to write to. What do I need to do to get this thing back to working correctly?
shane_huskey said:
1) Text messaging
-I have used Handcent for a long time on old phones, and used it just fine on this phone, but when I got my phone set back up, texts were coming in from the wrong people. I would get a text from PersonA, but it would show up as PersonB and when I responded it would go to PersonB. The only way that I could respond to PersonA was to back out, go into the people app, choose PersonA and text them. When I did this, it would take me into the exact same thread but have PersonA's name at the top now. When PersonA responded, it would show up as PersonB again and I would have to do it all over.
Click to expand...
Click to collapse
This is happening to me! I am rooted, completely stock otherwise and using Handcent. Is this a handcent issue? Anyone have more insight into this?
I'm in the process of unrooting my phone again to see if it happens when I'm not rooted.
Update:
Unrooted, same issue with Google Wallet and messaging
Rooted again, same issue
I was kindof hoping that someone would have come in here by now with some "here, try this" or "yeah, that happened to me and this is how I fixed it" type post. Am I the first person that has run across these issues after flashing to stock files from code.google.com?
I'm on 2nd nexus and haven't had that issue with handcent on either phones. Stock or rooted..
Sent from my Galaxy Nexus using XDA App
Are you uninstalling and reinstalling your apps? Have you tried deleting your apps' respective caches?
Sent from my Galaxy Nexus using XDA App
Well the 3 obvious problems could be:
1) I am either following the steps to unrooting incorrectly. (I don't think that it is rooting that is causing the problem since I a) didn't have the problem before I unrooted the first time and b) the problem is recreated whether I am rooted or not.)
2) My phone is faulty
3) The files that I am using (downloaded directly from http://code.google.com/android/nexus/images.html) are damaged.
The MD5 matches the .tgz file.
Everything looks like it is going through correctly when I am flashing the files.
I don't think that I am following the instructions in correctly, so that narrows it down (in my head anyway). Has anyone else used the factory images for code.google.com? Have you tried running Google Wallet afterwards?
esuohe said:
Are you uninstalling and reinstalling your apps? Have you tried deleting your apps' respective caches?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I have tried going into settings, force closing the app and clearing cache and I have tried resetting the phone to factory defaults. Neither changed how the app behaved. I still just get a black screen with the not responding message.
I did some more research into the Handcent problem, apparently it is fairly widespread on ICS and goSMS has the same issue. Stock is apparently not affected, so I am using that but it sucks...
I have seen a few of the GoSMS and Handcent posts, but I'm not completely sure that I am experiencing the same issue. Every post I have seen speaks of erratic problems. Mine is with every text message. Also, it didn't start happening until I flashed the factory images from code.google.com. Also, the problem only popped up when I started experiencing other problems (like with Google Wallet). Although we are having a similar issue, I believe the root problem of the issue is different, which is why the issues are slightly different.
Went and exchanged my phone today, rooted as soon as I walked in the door, installed everything back to the way that I had it and everything is working fine again. On my way to McDonald's for lunch.
Hello there,
I'm relatively new to XDA but I've heard that pretty much any problem can be solved through you guys. So here we go. I have an original HTC Incredible (hence the title) which is rooted and has the Android Business Gingersense 2.3.5 ROM installed. My problem is hard to explain, yet may be very simple. I simply cannot send or receive text messages to my knowledge.
So here are the details. Whenever I compose a text message in the native "Messages" app, I click send and the "Loading..." little window with the spinny circle pops up for a split second, disappears and nothing happens. It doesn't show me that the message was sent, nor does it give me an error message saying that it didn't send. Nothing. I have heard, however, from the people I sent the messages to that some of them did in fact go through, but I just didn't know they did cause it didn't show up on my screen. They also said they texted me back multiple times trying to get a hold of me to no avail, which is the other problem. I also cannot receive any messages. It may be that these issues are connected in some way but I am not sure.
Another problem. My native email app has the same sort of issue, only when I compose a message and hit send, it force closes the app saying, "an unexpected problem has occurred." Therefore I cannot send or receive emails as well. Quite inconvenient as many of you probably know.
One last issue involving the texting problem. May not have anything to do with the native sms app, but I believe there is still a possibility. I mainly text with Pinger's TextFree application, which not surprisingly has the same problem as the native app. Every time I try to send a message, NOTHING happens, yet I get reports from the people I "sent" the message to that they actually got the message and tried to get back up with me multiple times. Still, I didn't receive anything. But I did go on the web based version of the app and saw both of our messages between each other and the web app worked fine.
Any help at all is greatly appreciated and I hope I can get this resolved.
Thanks alot!
Almost sounds like a data/mms config problem. Are you able to receive any messages or emails at all?
Sent from my ADR6300 using xda premium
Well, the weird part is, it goes on and off... like one minute I could receive SMS and email another minute I'm back to where I've been
Sent from my Droid using xda premium
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
ousuxndallas said:
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
Click to expand...
Click to collapse
Have you tried a complete wipe and reflash?
Shano56 said:
Have you tried a complete wipe and reflash?
Click to expand...
Click to collapse
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
ousuxndallas said:
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
Click to expand...
Click to collapse
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Open the stock messaging app then hit menu - settings - connection settings, there will be 5 settings greyed out in there. What are the current settings for those 5?
Edit: Nevermind i forgot were talking about cm9, might not the same settings as sense. Better yet go to the market and download "apn backup and restore", do a backup and then go to the sdcard then the apn backup folder and then open the xml backup with a text editor and copy and paste its contents to here. You are on verizon correct?
Shano56 said:
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Click to expand...
Click to collapse
Radio: baseband version 2.15.00.07.28
ousuxndallas said:
Radio: baseband version 2.15.00.07.28
Click to expand...
Click to collapse
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Shano56 said:
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Click to expand...
Click to collapse
Okay, I think I have figured it out. Before I reflashed, I deleted my Google account. Then, reflashed C9 and when prompted on reboot to sign into Google, I clicked "later".
So, now I received several test text messages I had sent the past 2 days.
So far, so good.
Also, when I restore from Titanium, I am only going to restore Apps, but not the System Data.
I think Google is somehow interfering with things. Maybe something funky with how my Google Voice is interacting with my phone. Who knows. Anyway, I will be sure to report back here to help others that may have similar problems.
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
ousuxndallas said:
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
Click to expand...
Click to collapse
haha yes. its never a good idea to restore system data
Hester topeico
One more follow-up. I now Restored all data for the apps separately through Titanium.
Texting still works.
I think when I flashed the new C9 ROM, when I restored Apps+Data in Titanium, something got screwed up and thus the texting function got screwed up.
Now able to send SMS texts but NOT receive them
I'm reviving this thread.
I have checked out a few other threads, and this comes the closest to describing my issues with my rooted unlocked (SEC OFF) HTC Droid Incredible (version 1).
I did NOT change ROMs -- right after getting the DINC, I installed a rooted stock deodexed GB 2.3.4 ROM from DINC.DOES-IT.NET, and I have not touched the ROM since.
BTW, the ROM build is 4.06.605.3 CL 140944 release-keys
Ditto baseband radios, no change. Version: 2.15.10.07.07
I did recently update the kernel to a version of gingertiny that allows apps to record phone conversations without the speakerphone being turned on.
Old version: 2.6.35.14-gingertiny-v2+ Feb 2012
New Version: 2.6.35.14-gingertiny-v2 Nov 6 2012
It is POSSIBLE that the problems started with the change of kernel, because I don't use texting very much at all, but that was still a few weeks ago.
Based on what I have read on XDA, I went into Clockwork Mod 5.x Recovery, deleted and reformatted the data cache, and rebooted.
After that, I could SEND but NOT RECEIVE text SMS.
I had some doubts about whether all my calls were ringing through properly. I am still not entirely sure, but test calls from a landline and mobile phone did ring the phone, so maybe that is no longer (or maybe was not ever?) a problem.
I have seen suggestions to do everything from reinstalling ROM (being sure to restore only apps+data, NOT system data) to flashing a new radio to running *228 over-the-air update to manually upgrading the PRL list.
And then there is the question I have about the kernel change somehow being the culprit...
EDIT: One other thing I did right before changing the kernel was run Convert2Ext4 v2.0 using the "no data limit normal dalvik" version. My reason for running this was to get rid of the low memory/no memory warnings, lockups and crashes I was expriencing despite having over 300MB left out of 775MB on internal memory.
How should I go about trying to restore the ability to receive SMS without totally bricking or otherwise disrupting my DINC and causing more harm than good?
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Some more details
tiny4579 said:
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Click to expand...
Click to collapse
Thanks for having a look in, Tiny.
I use PagePlus running off VZW towers. PagePlus service rep sent me an SMS while I was in contact with her by phone, she said it got deducted from by cash balance. The only thing is, it did not actually reach my phone!
I have only used the stock SMS app until just yesterday, when I installed Handcent SMS. That did not help. Will uninstall, but I doubt that will make a difference.
Will go back to the old gingertiny kernel and see what that does, and report back here.
If that doesn't do it, maybe it's time for a Touch of Blue ROM, with which many seem to be doing so wiell...
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
Apologies if I am posting this in the wrong spot. I have a Pixel 2 XL(obviously) and had been on the Android beta program for some time now. The android p beta had been running really solid for me with no issues. So when they pushed it out officially last week i of course went for it. However, all of a sudden now, when *sending* texts, it gives me a notification sound (same as incoming notification). Anyone run into this? I searched the forums briefly but didnt see anyone with the issue although I couldve missed it.
Note- I'm using the Google Messages(I believe thats the official name) app, I just prefer it to Hangouts. I did check the settings, and disabled the setting for outbound notification sounds- but it persists.
Here's the kicker- it cant be isolated to just me, as my mom has the same phone -she messaged me last week and asked if she should update (I'm typically the guinea pig) and I said yep, been rock solid for me.. now she's getting the exact same behavior. So barring it being the messages app itself which i suppose is possible, I dont know.
Thoughts? Suggestions? I havent tried a different messenger app yet, suppose I could(textra maybe), I'm just partial to this one for whatever reason.
Thanks in advance!
Disregard. I guess its specific to Android Messages app. Installed another text app and the issue went no longer occurs.
I have the same issue with my Android Messages app