So randomly, but only a couple of times a day or every other day, ims.services stops working, also everytime I try to place a phone call, ims.services stops working, and the call automatically ends and goes to the screen right after a call that has the call back button on the left, view contact up above, the text message button on the right and video call in the center. If I click on the call back button then the call will go through. Does anyone have any suggestions or solutions for solving that issue?
The second issue, the keyboard one is as follows. I use SwiftKey 3,and ONLY when I'm typing in Chrome, the text prediction will not show an entire word, it only shows the letter I had just typed, and at the end of every word when I press the space bar (pressing the space bar automatically selects the center word prediction) it will add a second of the same letter to the end. For example, the word, "world" would be, "worldd". Now this ONLY occurs when I'm using Chrome. Does anyone have any solutions, or suggestions for this one as well?
Thank you everyone ahead of time, you all are awesome and always so extremely helpful.
Oneraindrop said:
So randomly, but only a couple of times a day or every other day, ims.services stops working, also everytime I try to place a phone call, ims.services stops working, and the call automatically ends and goes to the screen right after a call that has the call back button on the left, view contact up above, the text message button on the right and video call in the center. If I click on the call back button then the call will go through. Does anyone have any suggestions or solutions for solving that issue?
The second issue, the keyboard one is as follows. I use SwiftKey 3,and ONLY when I'm typing in Chrome, the text prediction will not show an entire word, it only shows the letter I had just typed, and at the end of every word when I press the space bar (pressing the space bar automatically selects the center word prediction) it will add a second of the same letter to the end. For example, the word, "world" would be, "worldd". Now this ONLY occurs when I'm using Chrome. Does anyone have any solutions, or suggestions for this one as well?
Thank you everyone ahead of time, you all are awesome and always so extremely helpful.
Click to expand...
Click to collapse
U might have to try a few things im no proffesional so take with a grain of salt..the 1st issue i never had so either a downloaded app interfering with things or u jus needa clear your cache up a bit..for chrome you can try lookinf at ya swiftkey auto correct settings n jus turn it off n see if it solves dat issue
Oneraindrop said:
So randomly, but only a couple of times a day or every other day, ims.services stops working, also everytime I try to place a phone call, ims.services stops working, and the call automatically ends and goes to the screen right after a call that has the call back button on the left, view contact up above, the text message button on the right and video call in the center. If I click on the call back button then the call will go through. Does anyone have any suggestions or solutions for solving that issue?
The second issue, the keyboard one is as follows. I use SwiftKey 3,and ONLY when I'm typing in Chrome, the text prediction will not show an entire word, it only shows the letter I had just typed, and at the end of every word when I press the space bar (pressing the space bar automatically selects the center word prediction) it will add a second of the same letter to the end. For example, the word, "world" would be, "worldd". Now this ONLY occurs when I'm using Chrome. Does anyone have any solutions, or suggestions for this one as well?
Thank you everyone ahead of time, you all are awesome and always so extremely helpful.
Click to expand...
Click to collapse
You did not say whether you are rooted or unrootted, and if the latter if you are on a custom ROM (assuming you are not).
If you are on stock OEM and have not updated it recently, that would fix it - as it overwrites the entire ROM and would clear this up. Whichever firmware/ROM version you are on, you could ODIN the AP module and that would also write over your problem.
As for Chrome - I don't use it.
Related
Anyone else get the problem where when you repy to a text you get numbers instead of letters, is there a fix for this yet?
If that happens I just hide the keyboard and then press the bit where it says 'Press here to type' or something like that. Takes a second to do and always seems to work for me when that happens
Didnt know you could do it that way, I tend to go into quick text or whatever its called then cancel back out and its ok after that.
Damned annoying though and surely something that would of been picked up in pre release testing?
I find that when trying to reply, it instructs you to tap screen to reply, but it takes several seconds and lost of tapping before it starts allowing me to type. Very annoying!
One problem that's becoming a royal pain with this hd2, is that whenever I am inside call history, for whatever reason, half of the time I end up dialing a number by mistake because my finger slightly touches the screen on a random entry and the software decides to call that number.
Most of the times I manage to press the "end call" button, but on other occasions I just can't make it in time.
You can imagine how this can be bothersome both for the wasted money, and for the called person.
I searched the whole forums to find something that even remotely could help me in this but surprisingly to no avail, so maybe someone can direct me to a app/workaround that prevents the call history from triggering a direct dialing as soon as an entry is touched?
This is just a work-around and not a permanent solution... what i usually do is scroll by moving my fingers vertically on the extreme right side of the screen (along the contact details icon), that way, you bring up the contact details accidentally instead of dialing mistakenly.
You can also try the 'decrease screen sensitivity' cab and see if that helps.
mikron15 said:
This is just a work-around and not a permanent solution... what i usually do is scroll by moving my fingers vertically on the extreme right side of the screen (along the contact details icon), that way, you bring up the contact details accidentally instead of dialing mistakenly.
You can also try the 'decrease screen sensitivity' cab and see if that helps.
Click to expand...
Click to collapse
yes, I noticed cliking the right icon brings up the detailed call history for that contact... but it's the random touches that create the danger, because you don't see what's happening, you just feel the phone vibrating when the line is up, and that's a problem
Decreasing sensitvity may be a good idea as well, if I wasn't fine with the normal sensitivity of the phone (actually I'd like something even more sensitive sometimes...)
I have the TMOUS HD2 and I am having 2 problems and I want to see if anyone else is either experiencing this or if it's just my phone.
On SENSE SMS messages, the keyboard will auto deploy and I will begin to type or Swype and nothing will show, unless I select or highlight the last message and then refocused on the blank area of my current message and then it will show. It's almost as if the screen doesnt redraw the text as I input it. It's VERY annoying.
When I'm in a call, and pull the phone away from my face, the screen will come on, but I can't press or access any button on the dialpad (Eg, Red Endcall or Keypad button) but I am able to press all of the hardware buttons and go to the home screen of Sense and do everything else on the phone. This is really frustrating, because I call my bank and I can't use the touch tone features to access my account or put a caller on hold and do the other features while on a call.
I would just like to know if these are isolated incidents that I'm just experiencing with my HD2, or is there a solution to theses issues. Any help would be GREATLY appreciated. Thanks guys.
Bigcountryed said:
On SENSE SMS messages, the keyboard will auto deploy and I will begin to type or Swype and nothing will show, unless I select or highlight the last message and then refocused on the blank area of my current message and then it will show. It's almost as if the screen doesnt redraw the text as I input it. It's VERY annoying.
Click to expand...
Click to collapse
I think that's just something you have to deal with, I used to get it on the O2UK stock 1.43 ROM after installing the hotfix (I assume it's cooked into the TMOUS ROM). After installing Windows Mobile 6.5.x I haven't come across the issue.
Bigcountryed said:
I have the TMOUS HD2 and I am having 2 problems and I want to see if anyone else is either experiencing this or if it's just my phone.
On SENSE SMS messages, the keyboard will auto deploy and I will begin to type or Swype and nothing will show, unless I select or highlight the last message and then refocused on the blank area of my current message and then it will show. It's almost as if the screen doesnt redraw the text as I input it. It's VERY annoying.
Click to expand...
Click to collapse
This is a known bug that we all have. When you start typing, sense is busy loading all your txts from that contact, and when it has finished loading them it auto focuses on the last text. During that time you cannot see what you are typing, though it is still being typed. When you then select the text input area your typing appears.
The fix is to not have many texts saved.
When I'm in a call, and pull the phone away from my face, the screen will come on, but I can't press or access any button on the dialpad (Eg, Red Endcall or Keypad button) but I am able to press all of the hardware buttons and go to the home screen of Sense and do everything else on the phone. This is really frustrating, because I call my bank and I can't use the touch tone features to access my account or put a caller on hold and do the other features while on a call.
Click to expand...
Click to collapse
you have either bsbtweaks "increase tap time" tweak turned on, or the increase taptime cab from the hints tips thread.
This tweak stops the incall screen from registering presses. Turn it off.
These are both very common, and there must be a few hundred threads asking the same questions.
The BST thing fixed the call problem I was having. And imma try to clean out the sms message to regain speed. Thankyou VERY much Samsamuel and Kalavere! Luv ya like a play cousin!
I am trying to solve this issue for my mom. She is running completely stock from Verizon. The issue is when she tries to forward a text message from the stock app, it occasionally will not recognize the long press on the text bubble. The issue seems to be intermittent . When I attempted to test the issue, it was having no problems, then I closed all open processes / applications and the problem reappeared.
When I attempt a long press on the text bubble, it will grey out for a split second, then act as if I never touched the screen. However it recognizes the touch to scroll if that makes sense. The problem seems isolated to the text messaging app. A long press in Gmail still will start the copy / paste function.
I pulled the battery and loaded the messaging app first and the problem seems to start from start up. Unless there is a process that loads on startup that I need to make inactive.
Anyone else have a similar issue, or possible solution?
This has happened twice today. I am using the phone and the voice typing display will not go away. I can use the phone.. .i can go to the homescreen, open apps, look at settings, etc, but i cannot close the voice prompt, and i can't use it.
It essesentially makes the phone useless until i reboot.
I am not sure why it is doing this. Not rooted nor unlocked or anything.. just stock.
The other thing it is doing is that sometimes when i wave my hand over the screen i will see the unlock screen. it will have the time and a lock icon below it ... if i touch the lock icon, it moves to a lower (on the screen) position and when i re adjust to hit the lock again it moves back up. Not sure how to screen shot this... maybe a video from a different phone.
when this happens, it will unlock by pressing the power button. I think this has something to do with the smart lock. DAMN google for forcing you to have a lock when you use Android Pay. Never had this problem on my Note 4 with Wallet.
Anyway, any help on either of these bugs would be appreciated
ok, i can reproduce the bug.
can someone else try this to confirm?
- with the phone screen off have someone send you a text message.
- swipe up directly to messages. ( use the google one, but i am not sure if it matters.)
- reply to the message with a google voice typing
- hit the power button to turn off the screen.
- Have the person text you again.
- open message by swiping up to it.
At this point the tap to speak screen will be there and not go away until you reboot.
no one else?
here is a video showing the problem I can't believe I am the only one experiencing this
https://dl.dropboxusercontent.com/u/11731783/20150929_123443.mp4
crash613 said:
no one else?
here is a video showing the problem I can't believe I am the only one experiencing this
https://dl.dropboxusercontent.com/u/11731783/20150929_123443.mp4
Click to expand...
Click to collapse
I can try it when I get my phone, but that's a few weeks away...