When receiving a text message and swiping to respond using active display, text typing functions are suspended until exiting and re-entering the message. Running latest nightlies on Nexus 5 with SwiftKey as input.
same thing happens to me on t-mo s4 (jfltetmo). I use chompsms and swype (also happened with kii). I was wondering if converting them to a system app with tibu would change anything...using 12/19 build right now
Related
Hi all,
I have searched through the (hundreds!) of messaging threads but noone seems to report this issue. When I am replying to a message in the HTC message app, seemingly randomly the message loses focus, and an earlier message is highlighted. What I type is not lost, but is not shown until I tap back on my reply.
I've tried the sensitivity tweaks, tried typing slower and more accurately, but still happens.
Really annoying, is this at all common?
Cheers,
I have seen same issue and not been able to find a fix. was thinking it could be a faulty touchscreen
yeah i have some issues with this im guessing software problem sometime, i carry on typing and its still there click the screen and its fine again, i just thought it was a software fault so never asked anything.
http://forum.xda-developers.com/showthread.php?p=5777104
I believe this is also related to the messaging app issue, as it tends to follow the same trend.
The annoying thing is I know why it's happening. When you tap on the text from the sense tab, it loads messaging app, then loads all of the messages, and then selects the message you tapped on from the tab. If there are a few previous messages from the same person, tap on an earlier message and you'll see what I mean.
If there was a way to change it to only open the messaging app and choose the same contact, not that same sms, then it would be fixed. I ended up just binding one of my hardware keys to messaging client, and I use that instead of the messages tab.
Thanks for the replies!
That makes sense. And whilst its loading the messages it types pretty slowly, particularly the space bar is not detected, and thats really irritating!
Will raise it as an issue with HTC, and see what happens.
EDIT:
A work-around is to click send on a blank message, and cancel. All messages are then loaded instantly, type away!
You'd think, now that we are 10 years on from greyscreen Nokias, with all this lovely hardware and software to play with, that simple text message would be no problem.
Instead, we have this problem (which I get as well), and a very glitchy messaging program which every fifth text seems to lag to infinity. For me, it's the weakest part of the HD2 and I hate sending texts sometimes. I hope they build in a solid messenger soon.
Mine has been doing this for ages, its worse with more messages. I wish they would hurry up and fix this. grrr
Hmmm... Yes, mine does this too - but I thought it started after applying a hotfix from the HTC site. I am on ROM 1.48.405.2 and I assume that the fix would have been http://www.htc.com/uk/SupportDownload.aspx?p_id=297&cat=0&dl_id=812
I applied the fix as I was finding that sometimes when I tapped in the typing area to reply, I got no response at all. The fix certainly sorted out that issue, it appears but my text now suffers from the above issue. - There is no 'uninstall' for this hotfix.
So - I've just seen this post
http://forum.xda-developers.com/showthread.php?t=636911
it seems that the hotfix and subsequent new ROM including the hotfix proves that it is an update related issue.
I'm running a ROM based on 2.10, it certainly isn't fixed in this version!
Running latest nightly cm7 (5). With netarchy's latest kernel. Using handcent for text.
When sending text under 160 everything works great. Once going over causing a split, the recipients of my text gets gibberish. Scrambled letter and symbols. Is anyone else getting this? Both my phone and my brother's phone do the same thing, so I know you should get the same results if you use the same setup as me. My question is why and what can we do to fix it?
I have read about this before but not actually experienced it yet (no long texts). I am running CM7 on my ns4g. I heard the simple solution was to go into your sms settings and simply select to have the app split up your texts at 160 characters.
Oh - sorry - you are using handcent. forgot. I just use cm7 sms app. hmmm. not sure. handcent doesn't have the same option?
Handcent has those options. They don't do anything. I ran cm7 on my evo with handcent, never had this problem before. So I'm thinking its a phone specific problem.
joebags said:
Running latest nightly cm7 (5). With netarchy's latest kernel. Using handcent for text.
When sending text under 160 everything works great. Once going over causing a split, the recipients of my text gets gibberish. Scrambled letter and symbols. Is anyone else getting this? Both my phone and my brother's phone do the same thing, so I know you should get the same results if you use the same setup as me. My question is why and what can we do to fix it?
Click to expand...
Click to collapse
Search is your friend
Its a CDMA issue. Have your texts split up into multiple txts at the 160 character count. There is even a setting in Handcent that says something about compatibly with CDMA
eagercrow said:
Search is your friend
Its a CDMA issue. Have your texts split up into multiple txts at the 160 character count. There is even a setting in Handcent that says something about compatibly with CDMA
Click to expand...
Click to collapse
i have used both settings in handcent for splitting by character and by word at the 160 limit. neither of them seem to work. the recipient receives two texts but it's all gibberish. I never once had this problem on my evo which is cdma also. both phones ran CM and handcent. I've gone through each and every setting in handcent and CM to double check I wasn't missing something. regardless it should work without me changing a setting to allow long texts. It is something that needs to be fixed.
What i'm thinking the problem is, is a setting that was forgotten to change from the gsm phones in the sms settings.
I just installed Miui, using the stock sms app from that it still scrambles the texts over 160. It says it's sending two texts, but something is horribly wrong on the receiving end of the text. So i'm pretty sure it's not a problem with handcent settings. It's the fact that these roms are ported from the GSM NS and we're missing something yet.
I'm going to install a stock image after work today and confirm that it works on stock roms.
I'm very shocked no one else has complained about this. I have two NS4G phones both of which have the same symptoms.
Just confirmed that 160+ sms messages send fine from a stock os on the ns4g. using stock messaging or handcent.
Using CM or Miui is causing gibberish to come through. There seems to be a problem using non stock based roms at the moment.
That is interesting. I had the problem, but I resent the same exact text except I broke it into 2 smaller sms and it was received fine. I can't remember what rom that was though, because I've been through so many and havent heard of the issue since I setup the automatic split sms in handcent.
This sounds bizarre because this is one of many Android devices but the only one I have this problem with... When I send an exchange email via the stock app, whenever I use an apostrophe I get random characters produced in the sent copy of the email. I don't see them when typing it, but when reading the copy after sending on the GT10, EVO, Laptop or my Blackberry I see the characters. It wouldn't bother me so much if I didn't know that anyone who gets my email sees them too. Anyone else have this issue?
And by the way the EVO and my Sammy GT7 don't do this while using the stock android email app on my exchange email.
Yeah I was getting this also, seems to happen when "auto-correction" occurs or when you backspace and replace characters, it seems to inject what almost looks like HTML language for the action performed, I've confirmed this happens when using the "stock" -English (US) Android Keyboard, however when I switched over to using the "samsung keypad" or my FlexT9 keyboard it did not experience the same behavior.
only the stock keyboard in the email app during auto-correction or manual correction appeared to experience this behavior.
I was going to look for another copy of the Android "stock" honeycomb keyboard and see if the problem continued but I haven't had a chance.
For the time being try switching over to one of the other pre-installed keyboards. [such as the Samsung one] and see if you still get strange characters in your sent mail messages.
Just noticed i have this same issue as well. Im using the stock mail app with my exchange acct but im using thumb keyboard and still get the random characters. Very embarrassing sending an email to my boss this am to see random characters included in it. I love thumb keyboard but cant have this happen! Hopefully its an issue in the mail app and Samsung addresses it.
followup
Yeah after looking into this some more I found that it appears to happen on any keyboard with auto correction, I've switch to Swype / T9 and the honeycomb stock keyboard and they all post the same results in emails that are sent.
ex. if you type the work "I'll" however you don't put the " ' " in the word auto correction may insert this character for you.
problem is when it does it places "'" instead of the auto corrected " ' "
so if you miss a ' in I'm you get I'm as a result. it really tears up the outbound emails.
for the time being I've switched to using non-auto corrective keyboards such as the Samsung stock keyboard. and this seems to prevent this condition from reoccurring.
of course this is just a work around to a much larger problem.
anyone else have any insight as to why the auto correction would place "'" in each corrected spot in the email?
Hello All!
I've been having this problem for a few weeks now and im all out of ideas of what to do.
Carrier: T-Mobile
Wearable: S3 Rugged
Extra Service: DIGITS
Coming From: LGV20 which never had these issues with the same plans and accesories
So to start, when i got the phone inittially during setup of the google accounts i noticed that my OTP SMS Pushes were not being received, or auto filling the information. I skipped past all of that and noticed that anywhere that OTP text were suppose to autofill in different applications, it would not even when i received the text and got a notification.
So after a while of using TEXTRA which was working fine, one day i stopped receiving ALL text not just mms. I was able to send but never was I able to get anything from anyone. I ditched TEXTRA and went back to the stock Samsung app and noticed that all text were there, even though it was not default. After using the Samsung messages app i decided to go back to textra, heres whats funny. After Textra did it's initial setup, it only showed half of the recieved text from up to that day. Messages were incomplete, some just had one reply from a user and nothing else. So I also tried this with Android Messages and it had the EXACT same message log as textra. Both were not receiving the full logs from the server. Today Android Messaging was working for a good part of the day, then it just stopped all of sudden again.
Can someone help me with this, I've wiped the cache and factory reset the phone. Ive added and removed the multi-line settings in the samsung settings. I've tried the legacy settings on textra. I've called the DIGIT's customer service to see if they could fix it but they made and interesting point that it couldnt be digit because it wouldnt interfere with 3rd part messaging apps. When i switch apps i always make them default, i wipe the app cache etc.
I have a gut feeling this has something to do with something with the default Samsung Messages app and it somehow restricting use outside of it.
I just wanted to reply and say that I've been experiencing the exact same issue and haven't had any luck Google engineering my way around it. For me, I'm seeing the issue with Signal, so I don't believe it's the 3rd party app's problem. I can send messages (SMS/MMS), but the Samsung Messages app is the only one that "receives" them. A strange workaround I found was to download Android Messenger, set that as the default messaging app, then set Signal as the default messaging app again. This worked for a while, but I think the Samsung Messages app recently updated, and it broke this again until I repeated the above workaround.
It's annoying enough that, without a fix, I'll definitely be flashing a completely stripped ROM on this phone once we have the ability to do so to get away from all of the Samsung apps that I can't disable. And don't even get me started on Bixby...
wjm3982 said:
I just wanted to reply and say that I've been experiencing the exact same issue and haven't had any luck Google engineering my way around it. For me, I'm seeing the issue with Signal, so I don't believe it's the 3rd party app's problem. I can send messages (SMS/MMS), but the Samsung Messages app is the only one that "receives" them. A strange workaround I found was to download Android Messenger, set that as the default messaging app, then set Signal as the default messaging app again. This worked for a while, but I think the Samsung Messages app recently updated, and it broke this again until I repeated the above workaround.
It's annoying enough that, without a fix, I'll definitely be flashing a completely stripped ROM on this phone once we have the ability to do so to get away from all of the Samsung apps that I can't disable. And don't even get me started on Bixby...
Click to expand...
Click to collapse
I haven't had any issues with my At&t model...Been using Yaata since day one (about 2 months).
Also, there are some "package disabling" apps in the play store that will allow you to disable any app you want, you don't even need to be rooted. It cost me $1.99 (or around there), but was well worth it! You can even completely disable Bixby, so the button is even non-responsive.
Having the same issue and I may have fixed it. I logged completely out of Digits on the phone (settings/cloud accounts/multi line/hit the ... menu and choose log out.
I have this same issue. No matter which 3rd party SMS app I use I have missing text messages on the T-Mobile S8. Has anyone fixed this? It is driving me crazy. T-Mobile replaced my S8 and the new one does it (not as bad but it does it more than I'd like). How can I resolve this? My friend haf the same issue, he has an unlocked T-Mobile working on AT&T.
I don't use Digits or anything like that... any ideas?
hi guys
all you need to do
go to setings
device maintence
battery
scrool all the way down to unmonitored apps and add your 3rd party sms app
youre welcome
This still didn't work for me and I am having the same exact issues. I have tried installing 2 different 3rd party messaging (Textra and Mood) and both were not working properly. I can send messages out just fine but when I receive them they are delayed (like 5 minutes or longer). Sometimes, I don't get the messages at all. Of course, the Samsung Messaging app (which I hate) works just fine. I have even "Force Stopped" it! What to do?
go into the stock messaging app, and turn off advanced messaging
Has anyone found a solution? I've been using textra for years & suddenly in March I started having this problem but with sent messages. All incoming texts are displayed but my sent texts aren't. I did try the 2 suggestions above. On a note 8, Android 8.0.0,Samsung experience 9.0.
SOLVED. I had the same issues and found the solution. Before you install your 3rd party sms/MMS you need to disable the default messenger. I uninstalled signal, disabled the built-in messenger, reinstalled signal. Now I can receive texts. Also my phone is not a Samsung.
So I have another bug that MAY have started after the Nougat update.
I use Google Android Messages for sms and GBoard for my keyboard...
Lately when i'm texting to someone, when I go to reply to a text (maybe when the text thread is already open?) my keyboard doesn't work and I have to hit the back button which makes the keyboard go away then click on the message box to activate it again so it will work.
Is anyone else having this issue? Any fixes found?
I've tried clearing cache on both apps, this didn't fix the issue for me.