Related
I've owned my Rogers Dream (rooted, no custom ROM) for a couple of weeks now - this bug has been around since the start but it's getting worse these days and it's really starting to bother me.
Basically what happens is I'll get the notification for a text message. I can see the summary in the notification bar (with the new message), but when i open a messaging app (the default one or Chomp) the message won't be there. SMS Popup will also just display the previously most recent SMS in the conversation.
It seems like the system just isn't saving the message. Besides for the notification (which disappears after i clear), it's as if I never got the message. It kind of sucks...
My searching skills came up with nothing so i'm wondering - has this happened to anyone else - any idea what the reason could be - please let me fix this.
Thanks!
Well blyn100, interesting you should point this flaw out. I have a similar issue, but so far only 1 contact has given me this same summary with no msg. Trying to figure out the source of this problem, right now I have one suspicion. A few times, i think i received these msg's after being in a no service area. I am curious if this might be a possibility for you?
Also, I have similar phone setup as you, ie same stock Rogers ROM, obviously since no choice...yet.
i have the same issue
i had a thread started, but no response yet as to how to fix this
http://forum.xda-developers.com/showthread.php?t=542178&highlight=SMS+issue
but now it seems like more and more ppl are having this issue (or it is more apparent)
its the same with Chomp, handcent, even the native app
Looks like this is mostly just a Rogers issue then?
Most of mine are occuring when I have pretty good reception, so I think i can confirm that that's not it.
Proccessor usage / avaiable RAM is what I'm leaning towards though. I might try uninstalling the virtual keyboard to free up some RAM and see if it helps anything.
Or just a bug in the stock ROM. Seems like for this to happen, the network is sending the message to the device and the device just forgets to save it, but confirms to the network that it got it. Still, i have a hard time believing a problem like this would suddenly appear for the Rogers build.
I had like 3 dropped ones last night, it's starting to get really annoying.
Are you sure it's not the timestamp bug? Look further up in your conversation to see if SMS' have been inserted there.
hellfenix said:
Are you sure it's not the timestamp bug? Look further up in your conversation to see if SMS' have been inserted there.
Click to expand...
Click to collapse
Yup, i checked all of the conversations, this isn't the case for any of them.
I had this issue on my T-Mobile G1 with the Rogers' ROMs. But I haven't had issues with Cyanogen builds...
Hey all,
Within the HD2 when you send and receive messages from people with different timezones ordinarily I might expect that it would use the old users time and show me that the reply was say +3 hours, whereas actually it was a few minutes ago.
However it appears that when it orders the messages it takes your local time always, so you can get the situation:
Me: 4.40pm
Reply: 4.45pm (7.45pm users time)
Me: 4.50pm
Reply: 4.55pm (7.55pm users time)
So the message thread becomes:
Me
Me
Reply
Reply
So it becomes completely out of sync and is actually really useless, is there a fix or something I am missing in regards to this?
Thanks!
I have the problem of mine being time stamped 3 minutes earlier than when I got them so when it should be:
Me
Reply
Me
Reply
it becomes
Reply
Me
Reply
Me
Seems like they've really screwed up the whole conversational messaging thing
I've not been able to fix mine yet
Yes this is a really annoying issue and keeps happening, is there anyway or any fix that is forthcoming for this?
It will mean that threaded messaging just wont work properly with this phone.
SMS Timing
What cell company do you all have? I've noticed other post about this, and I have had the same issue. The common carrier is T-Mobile. My Girlfriend is having the same issue, and she is on T-Mobile with a Touch HD. I am running a Touch HD2, so it's not the phone. I recently flashed the new official ROM 1.403.405.1 (70124). Since then my problem has gone away and not using the SMStimefix.cab file that is out there available (it didn't work).
Hope this helps
[email protected] said:
What cell company do you all have? I've noticed other post about this, and I have had the same issue. The common carrier is T-Mobile. My Girlfriend is having the same issue, and she is on T-Mobile with a Touch HD. I am running a Touch HD2, so it's not the phone. I recently flashed the new official ROM 1.403.405.1 (70124). Since then my problem has gone away and not using the SMStimefix.cab file that is out there available (it didn't work).
Hope this helps
Click to expand...
Click to collapse
Hey,
Yes I am on T-Mobile, its not something I have experienced in the past with a carrier (O2, Orange). So I guess T-Mobile do / dont do something that other carriers do which cause this.
I'll try to look into the SMStimefix to see if it does work or such like. So do other people on O2, Vodafone not have this issue?
i had this problem.... tooo
it really terrbile as i wont able to know which is my sms with his reply
Hi all,
I was wondering if I can't start a partition for the sms problem for leo. This is still a phone people and the two major functions of a phone are to be able to call and send text messages. Meanwhile all HTC seems to do is fix some little calendar and sd-card bugs but where is the WORKING fix for the sms messaging problem? I think if we start a petition and show HTC how much people are struggling with this problem, they will need to hurry up and fix this problem once and for all. Only problem is that I don't know how to start this off and I could use a little help. Thnx in advance.
Grtz
P.S. Still loving my snappy Leo, but it's very frustrating when you can't send messages when you're used to do this a lot..
totally agree. they should stop all other fixing not fixing anythng nd work on this issue.
I don't believe in petitions; needs someone to organise, etc.
Better idea, if you feel so strongly about it, is to write to HTC's technical department and copy their publicity and marketing people in.
WB
i dont know which problem you talk about.
but there is already a hotfix for sms-problem from htc.
http://www.htc.com/de/SupportDownload.aspx?p_id=297&cat=0&dl_id=812
i hope this will help you. otherwise, which problem do you mean?
Fonzy85 said:
i dont know which problem you talk about.
but there is already a hotfix for sms-problem from htc.
http://www.htc.com/de/SupportDownload.aspx?p_id=297&cat=0&dl_id=812
i hope this will help you. otherwise, which problem do you mean?
Click to expand...
Click to collapse
He knows that, but that hotfix dosent work. This is why he put WORKING hotfix in his message. HTC need to sort this out. coz i'm seriously thinking of selling this phone and getting another iPhone now.
Protip: The hotfix works. If it doesn't, you're doing it wrong.
DexyG said:
Protip: The hotfix works. If it doesn't, you're doing it wrong.
Click to expand...
Click to collapse
doesnt work
Gotta agree hot fix did nothing for me. Seriously annoying trying to send messages. Its rather embarrassing when i show off the phone!
The only thing that gets me by is the little work around someone suggested. When loading a contact Open and Close the menu(bottom right) then you can type. Its annoying but much faster than waiting for nearly a minute to start typing.
they should remove and return me back the old classic outlook sms!!!!
bzdemes said:
Its rather embarrassing when i show off the phone!
Click to expand...
Click to collapse
Exactly, when people use the phone to try it out and it gets stuck on one of the most basic functions, they just think "why would someone use a phone that doesn't text?". It won't do much for the "i want one" mentality that HTC want people to have when they see their friends using their phones.
DexyG said:
Protip: The hotfix works. If it doesn't, you're doing it wrong.
Click to expand...
Click to collapse
What makes you think so? There are loads of people who've installed the fix and experienced the bug since. And more are cropping up every day. Just because some people haven't had the bug come back after installing the fix doesn't mean it wont. Some users had the phone for weeks before the bug cropped up initially. Moreover, HTC themselves are not advertising the hotfix as relating in anyway to the stuck outbox problem. The accompanying description on their site is a load of marketing speak nonsense.
My 2p worth.
Firstly I have a love hate relationship with HTC Messaging. I've always used PocketCM anyway instead of the standard MS c#@* and it has worked lovely until the recent ROMS came along. Now it simply won't run alongside. Just crashes out. I don't know why and the developer can't assist as he does not have a machine to test it with and can't recreate the issue etc, etc...
Last week T-Mobile made me an offer that could not be refused and so I upgraded to the HD2. It has been with some trepidation that I have used it the past week or so as I send and receive a lot of texts on a daily basis but I have to say I have not had the problems you guys are having. They go straight away and there is none of the lag that has been reported. I'm beginning to think I must be very lucky! On the other hand I would agree that to me the two basics of these phones that must work faultlessly are the calls themselves and SMS. The fact that there is issues is pretty dreadful...
My next hope is the arrival of hacking SPL so I can flash a decent ROM onto the device and hopefully one without this program built in!!
The SMS outbox build-up (and therefore non-sending) bug is intermittent. I had it after around 4 days on my original handset. I installed the hotfix immediately upon unboxing the replacement and encountered the problem within 24 hours. There is also another, more nasty and even more intermittent SMS bug - mentioned by only a couple of people on this forum - and that is texts going to someone other than the intended recipient. I have had it happen twice to me and that is enough to give me ZERO confidence in sending texts on this device. I don't discuss anything that I would be embarrassed about if it were to get into the wrong hands. This is a bit of a disaster for a seasoned texter like myself, I used to text more than I made calls.
HTC need to address this, they obviously can't locate the 'bug' or don't fully understand the problem. Intermittent faults are notoriously difficult to fix as they never occur when the 'tester' is checking for them. Therefore if a fault cannot be replicated, how can it ever be fixed? My 2 cents is that the whole messaging app should be rewritten from scratch and the plans for the old system should not be looked at - it should all be fresh. If they can't find the bug, write some new code.
sunking101 said:
The SMS outbox build-up (and therefore non-sending) bug is intermittent. I had it after around 4 days on my original handset. I installed the hotfix immediately upon unboxing the replacement and encountered the problem within 24 hours. There is also another, more nasty and even more intermittent SMS bug - mentioned by only a couple of people on this forum - and that is texts going to someone other than the intended recipient. I have had it happen twice to me and that is enough to give me ZERO confidence in sending texts on this device. I don't discuss anything that I would be embarrassed about if it were to get into the wrong hands. This is a bit of a disaster for a seasoned texter like myself, I used to text more than I made calls.
Click to expand...
Click to collapse
Now that would be a major pain in the a#*&! As I've said I believe I must have struck lucky and have none of those issues but if I did.... God doesn't bear thinking about!
sunking101 said:
HTC need to address this, they obviously can't locate the 'bug' or don't fully understand the problem. Intermittent faults are notoriously difficult to fix as they never occur when the 'tester' is checking for them. Therefore if a fault cannot be replicated, how can it ever be fixed? My 2 cents is that the whole messaging app should be rewritten from scratch and the plans for the old system should not be looked at - it should all be fresh. If they can't find the bug, write some new code.
Click to expand...
Click to collapse
+1 to that idea but I wouldn't hold your breathe!!
One again, I repeat: I haven't seen anyone in America have this issue. I use ATT and have no issues with texts. None. I've had my HD2 for almost a whole month, as well.
*knocks on wood*
Lucky indeed
TonyJ999 said:
My 2p worth.
Firstly I have a love hate relationship with HTC Messaging. I've always used PocketCM anyway instead of the standard MS c#@* and it has worked lovely until the recent ROMS came along. Now it simply won't run alongside. Just crashes out. I don't know why and the developer can't assist as he does not have a machine to test it with and can't recreate the issue etc, etc...
Last week T-Mobile made me an offer that could not be refused and so I upgraded to the HD2. It has been with some trepidation that I have used it the past week or so as I send and receive a lot of texts on a daily basis but I have to say I have not had the problems you guys are having. They go straight away and there is none of the lag that has been reported. I'm beginning to think I must be very lucky!
Click to expand...
Click to collapse
That's the problem. Although I've read and followed these threads about this problem as they came across the forum, I had'nt had any problems myself and considered myself lucky too! But after regaining confidence in messaging with my leo, and I started to send texts again it turned out this problem occurs quite random. Sometimes I send a text and it gets delivered right away, but another time I'll send a text and a few others to other recipients, and they all get delivered 2 days later!! That's where it gets tricky for HTC I think. Then again, if they are able to create these beautiful devices, they're certainly able to rewrite a flawless messaging-app from scratch.. Only hope that this will be fixed soon Or HardSPL will be released soon.
DexyG said:
Protip: The hotfix works. If it doesn't, you're doing it wrong.
Click to expand...
Click to collapse
If you're saying that, YOU know nothing.
I too suffer this problem.
Today I got really pi**ed with it and uninstalled the Hotfix, leaving just the ROM Update, so far so good - probably just today though!
This is a really buggy phone throughout though, probably the worst I've had, but somehow this appeals to me deep down
I've had the phone since November, seen the sms problem only twice. Kinda got the impression that it only occurs if the phone has been on a good while, i.e a number of charges with no soft-resets. That could easily be coincidence.
Both times also after spotting the messages in the outbox and doing a soft reset the queued messages sent.
Still not working for me too
While there are several threads announcing the release of Android 5.0.1, in regard to the Nexus 6, most of them seem to be filled with posts relating to the availability, instructions for sideloading, etc.
This thread is to discuss the CHANGES that you have noticed between 5.0 and 5.0.1, and as this is the Nexus 6 section, it should really relate to changes on that device only. You may list changes you've personally noticed, or published changes, but please indicate the source. I, like many of you, no doubt, am very curious to see what is new, fixed, broken, etc.
http://aosp.changelog.to/aosp-LRX21V-LRX22C.html
On 5.0 I kept having the cloud print service or whatever keep crashing, on 5.0.1 I had the Amazon kindle app keep showing a notification Amazon kindle stopped for about 12 hours and had to reboot my phone. (Kept throwing the notification up about every 20 minutes on 5.0.1)
My phone has also been unable to chromecast netflix for the last week and I have to use my gf's nexus 6 to chromecast netflix. Weird little problems with applications on both operating systems.
Edit: Finally re-installed netflix and it fixed chromecasting.
It would be nice to see a list of changes (In language a typical person speaks rather than the jumbled mess that those AOSP changes look like)
I agree. Those AOSP changes are not that easy to understand. Also, they are just to the Android Operating System but doesn't the OTA also contain a new Modem and possibly other driver updates that would fix other issues with our phones? Those fixes and changes would not be in the AOSP list.
On a second note, why does Google do this? They obviously know whats changed. How hard is it to publish a simple list?
Is 5.0.1 fixing the slow text/multiple texts sent issue for Sprint users? People are getting my texts like 10 times quite frequently, I read somewhere that this version fixes that.
agentfazexx said:
Is 5.0.1 fixing the slow text/multiple texts sent issue for Sprint users? People are getting my texts like 10 times quite frequently, I read somewhere that this version fixes that.
Click to expand...
Click to collapse
It doesn't.
Hell, I'm on AT&T and have the slow text issue. It'll stay stuck on "sending" for 3-4 minutes sometimes. Not sure if it sends multiple times or not, haven't had anyone complain to me that they got the same message several times.
I think I saw there is a new radio... Would be interested to know if signal reception is any better
Sent from my Nexus 6 using XDA Free mobile app
banzaiwolfe said:
It doesn't.
Click to expand...
Click to collapse
What does?
Sent from my Nexus 6 using XDA Free mobile app
On 5.0 I could not connect to my company’s Wi-Fi (it would show as ‘Saved’ but no connection).
On 5.0.1 I have no issues connecting to the same Wi-Fi.
fdan100 said:
On 5.0 I could not connect to my company’s Wi-Fi (it would show as ‘Saved’ but no connection).
On 5.0.1 I have no issues connecting to the same Wi-Fi.
Click to expand...
Click to collapse
sweet, thanks for letting me know that this works now.
digging in a little deeper
https://android.googlesource.com/platform/external/wpa_supplicant_8/+/1d13911
Work around AP misbehavior on EAPOL-Key descriptor version
It looks like some APs are incorrectly selecting descriptor version 3
(AES-128-CMAC) for EAPOL-Key frames when version 2 (HMAC-SHA1) was
expected to be used. This is likely triggered by an attempt to negotiate
PMF with SHA1-based AKM.
Since AES-128-CMAC is considered stronger than HMAC-SHA1, allow the
incorrect, but stronger, option to be used in these cases to avoid
interoperability issues with deployed APs.
This issue shows up with "WPA: CCMP is used, but EAPOL-Key descriptor
version (3) is not 2" in debug log. With the new workaround, this issue
is ignored and "WPA: Interoperability workaround: allow incorrect
(should have been HMAC-SHA1), but stronger (is AES-128-CMAC), descriptor
version to be used" is written to the log.
Bug: 18411110
Change-Id: I9ae12e8882adc9e785f6e4cef9f30b89bf72dcd2
Signed-off-by: Jouni Malinen <[email protected]>
Click to expand...
Click to collapse
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1 I was roughly 34%, which was not really bad, after 12 hours of my normal use. Today, 50%, same time as yesterday. I will keep an eye on it, but thats what I'm seeing. Everything else seems about the same to me.
The issue with the face unlock camera is fixed.
5.0 is had huge problems in dim rooms buy now no issues
jackpollard said:
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1
Click to expand...
Click to collapse
I was kinda seeing this too.
N6
land2634 said:
Hell, I'm on AT&T and have the slow text issue. It'll stay stuck on "sending" for 3-4 minutes sometimes. Not sure if it sends multiple times or not, haven't had anyone complain to me that they got the same message several times.
Click to expand...
Click to collapse
FWIW I'm on AT&T and have not had this happen to me even once.
jackpollard said:
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1 I was roughly 34%, which was not really bad, after 12 hours of my normal use. Today, 50%, same time as yesterday. I will keep an eye on it, but thats what I'm seeing. Everything else seems about the same to me.
Click to expand...
Click to collapse
Now that's more like it!
Not sure if it was 501 or the gplay music update, but my music sounds much more clear now. No more cloud print crashes.. Hoping my signal issue was fixed (sprint) but as im deployed right now i only use wifi.
Is anyone else having issues adding an exchange email account using the Gmail app? BTW, I flashed my phone to the stock 5.0.1 (LRX22C) version. After returning to complete stock I rooted and flashed TWRP but the issue was present before I made those changes.
cavalier11 said:
Is anyone else having issues adding an exchange email account using the Gmail app? BTW, I flashed my phone to the stock 5.0.1 (LRX22C) version. After returning to complete stock I rooted and flashed TWRP but the issue was present before I made those changes.
Click to expand...
Click to collapse
i am not having that issue with my exchange account and gmail app
My phone just updated to android pie and now my camera and YouTube app freezes occasionally. The only way to get them working again is to keep restarting the phone. Anyone have any fixes? Thanks!
Turning off wifi calling seems to have helped a little.
Same here.
This update is an absolute ****show: The notification bar breaks, YouTube too, SnapChat too. I have to reboot twice a day.
Anyone tried a factory reset and had improvements ?
I have done a factory reset and still no improvements. I've called samsung tech and I got the runaround.
I have a SM-G892A with a Cricket sim card running Android 8.0.0 and came here looking for a way to update it but if there are problems it may be best that I don't update yet. Unfortunately there does not seem to be much info for the S8 Active on these forums. I'll just have to keep my eye on here.
I wouldn't update. My phone worked flawlessly on android 8. I wish I could go back.
A new update is out ! It's stable so far.
What carrier?
markstibbyspot said:
What carrier?
Click to expand...
Click to collapse
Unlocked Sprint ! But the problems came back 3 days later
Samsung, shame on you, the S8 Active is your best hardware, but certainly has the worst software I've seen in a phone in a long time.