[Q] Help: Keyboard Lag - Android Q&A, Help & Troubleshooting

There are some times where I go to type out a text message, but when I type (I've tried different keyboards, so I've ruled that out), nothing shows up. If I wait about a minute, it works again, but sometimes I don't have the time to sit around and wait. I was wondering if it's possibly the application (Handcent) or something else. Any solutions/ideas?
Thanks!
Crystal

Related

Repeatable crash: shell32.exe

I noticed a weird, repeatable crash I'm getting today and I'm curious if anyone else is experiencing it:
Settings>Sounds and Notifications>Notifications tab
Settings as:
Event: Phone: Incoming Call
Ring type: Vibrate and ring
Ring tone: Ring-OldPhone2
When I test the settings, everything works fine, but when I hit OK to leave the page, the Event box goes blank, and it kicks me out to an error message that there's been a shell32.exe crash. (It keeps whatever settings I make, though.)
Whether I pick send or don't send, a new screen then comes up and thanks me for sending the error data. Then, it goes out to a splash screen that shows the phone as locked. I have to hit the lock button to get back to my Today screen.
I can repeat this pretty consistently on my Verizon TP.
kal
Get that alot when Im running opera and it opens up a pgae slowly. What causes this?
mrbonner said:
Get that alot when Im running opera and it opens up a pgae slowly. What causes this?
Click to expand...
Click to collapse
No idea. I've had about 10 Windows Mobiles/Pocket PCs, and I've never had it happen before.
Confirm
I confirm the bug, and its really bugging me! I have to turn off the device completely because some application won't work right.
Please, help!!
i get this error with the TF3D at times and have to restart TF3D
I have had this happen a couple of times too, both times I was previewing ringtones.
I had that problem when I first got my phone I went crazy and used Adv Config to change nearly everything there was, shortly afterwards I got a shell32.exe error and a gwes.exe error. I finally did a hard reset and tweaked more carefully and since then haven't had any problems.

[Q] Has anyone had problems with freezing...

Has anyone had problems with their phone freezing/crashing randomly? Basically my phone would freeze or crash (a force close) when I sleep it too quickly.
Sometimes it's not even sleeping it, it's un-sleeping too. Or even navigating between applications.
When this happens I go in to my messages to type a text and all contacts' names disappear and only numbers show up. If I attempt to click on a text the text will not show up and the screen is just black. It will either take more than 3 minutes for the text to load, or it will not load at all. So I have to shut it down in order for it to work properly again.
My phone has not been rooted, I have not downloaded very many applications, maybe just 5. I haven't even used it to browse because I'm afraid I would have to turn it off and just reboot the whole thing. Does anyone have an idea what is wrong?
You better go get a new one.
use a task killer, maybe it would help you, It worked for me

[Q] Weird Texting Issue (Queued Texts?)

I am having a weird issue with my LTE involving texts. This morning I restarted my phone and then a little bit later I got a couple text from some friends asking what I was talking about. I went into Handcent and looked at my conversations and found one text, which I sent on 6/5 or 6/6, was either resent or just sent for the first time this morning following the restart of the phone.
I called one of the guys asking him about the message sent to him and he said he never received it when I originally sent it, even though my phone showed it sent successfully.
Has anyone experienced anything like this?
this happens to me too. the radios seem to be able to only do one thing, so if while you sending, it needs to reconnect, connect to wifi,3g, or if you get a text, chat, or phone call while the first action is going (sending a text in this case) it seems to just hang. the thing being sent won't finish but looks like hanging forever (I've found some texts like 2 days later still spinning) and whatever the other action was won't come through. I've been told about chats or texts or talks sent to me I never receive if sending something, or usually the thing will hang for like 5 minutes and then I see I voicemail icon pop up and, surprise surprise, it came 5 minutes prior when my txt was hanging(it still is hanging, hangs forever) or a website loading hangs or connecting to wifi that never finishes. something about how this thing handles multitasking is just rubbish.
I think it has something to do with the way switching back to browser reloads the page, switching back to gmail reloads the composing page, switching back to angry birds forgets your pause and restarts the game, basically,I think they borked the multitasking somehow. sense itself reloads, quite embarrassing when trying to show off the phone, when you press home button from certain apps.
I've read if you flash a custom rom, it fixes all this. seems drastic to me, you'd think a hack would fix this.

[Q] Slow Galaxy s3 Performance

Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
The least invasive solution will be to clear the cache for the all the apps affected and reboot.
Or just wipe cache from recovery and see where it goes.
sammy.sung.me.a.song said:
The least invasive solution will be to clear the cache for the all the apps affected and reboot.
Or just wipe cache from recovery and see where it goes.
Click to expand...
Click to collapse
thanks i'll give that a bash.
Was also considering just flashing CM10 jelly bean?
Flash cm10 or Sammy jb
Sent from my GT-I9300 using xda app-developers app
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
Reduce animation scale to 0.5
go to setting>developer option>animation scales
You can also set no animation so that phone will response in less time
5aq1b said:
thanks i'll give that a bash.
Was also considering just flashing CM10 jelly bean?
Click to expand...
Click to collapse
How is that very different from a restore?
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
Unfortunatlly mate, i think ur having problem with this stock rom did you try to factory reset your device to eliminate those bugs. or flash another Rom because this is definitly a Rom problem.
sammy.sung.me.a.song said:
How is that very different from a restore?
Click to expand...
Click to collapse
it's not lol but at least this way i'll gain as well by upgrading to jelly bean - 2 birds with 1 stone etc etc
kachrukamble said:
Reduce animation scale to 0.5
go to setting>developer option>animation scales
You can also set no animation so that phone will response in less time
Click to expand...
Click to collapse
i'll try this as well mate - thanks!
Same issues that I'm facing
I'm also facing the same issue.... Long black screen pause when exiting or moving from one app to other. Very very frustrating ....
Tried all the trick in world including those that mentioned below.... Will be returning the device and going for a iPhone 5 !
Same exact issue, any results?
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
I am having the exact same issue with my S3. Sometimes calls take up to two minutes before they register. The phone remains completely responsive the whole time, and I can try to dial a bunch of different numbers (doesn't matter if I dial a number directly or if I quick dial a favorite or whatever). Suddenly, two minutes later it appears to register that, "Oh, I'm a phone!" and then dials all of the numbers all at once. Two minutes is a very long time to wait for the damn thing to dial. Especially when some iPhone user is sitting next to me going, "Seriously? You put up with that?" It is embarrassing.
I am also on the stock android 4.0.4 (verizon) and I would really really rather not have to wipe it clean and re-install.
The rest of the phone is fast (I am using go launcher) with the exception of the "Negative Colors" widget and the "Assistive light" widget. Both of those act just like the dialer. I hit the widgets and sometimes nothing happens for a minute. Again, the phone is completely responsive the whole time and I can hit these buttons over and over. Suddenly it all registers and then my screen flashes between normal and negative about a hundred times (once for each time I hit the button in frustration), and the led flash strobes on and off (again, once for each time I tried to get it to work).
This does not happen every single time though. Sometimes it behaves properly. Other times, it is super slow, but once it reacts, then I can make calls quickly until I let it sit untouched for a while. Then it gets all slow again.
I thought I'd try flushing the cache, but I cannot seem to find what cache I should flush. I can't find a dialer app, and the only other app that looks appropriate is the Dialer Storage app, but it does not have a cache I can flush.
Can anyone point me to a diagnostic tool that I can use to determine just what the phone is doing at this time? I have tried emailing myself the logs using log viewer, but they are huge and I can't seem to find anything there that I can sink my teeth into. Any help would be appreciated. My iPhone owning friends are becoming insufferable.
bvz2000 said:
I am having the exact same issue with my S3. Sometimes calls take up to two minutes before they register. The phone remains completely responsive the whole time, and I can try to dial a bunch of different numbers (doesn't matter if I dial a number directly or if I quick dial a favorite or whatever). Suddenly, two minutes later it appears to register that, "Oh, I'm a phone!" and then dials all of the numbers all at once. Two minutes is a very long time to wait for the damn thing to dial. Especially when some iPhone user is sitting next to me going, "Seriously? You put up with that?" It is embarrassing.
I am also on the stock android 4.0.4 (verizon) and I would really really rather not have to wipe it clean and re-install.
The rest of the phone is fast (I am using go launcher) with the exception of the "Negative Colors" widget and the "Assistive light" widget. Both of those act just like the dialer. I hit the widgets and sometimes nothing happens for a minute. Again, the phone is completely responsive the whole time and I can hit these buttons over and over. Suddenly it all registers and then my screen flashes between normal and negative about a hundred times (once for each time I hit the button in frustration), and the led flash strobes on and off (again, once for each time I tried to get it to work).
This does not happen every single time though. Sometimes it behaves properly. Other times, it is super slow, but once it reacts, then I can make calls quickly until I let it sit untouched for a while. Then it gets all slow again.
I thought I'd try flushing the cache, but I cannot seem to find what cache I should flush. I can't find a dialer app, and the only other app that looks appropriate is the Dialer Storage app, but it does not have a cache I can flush.
Can anyone point me to a diagnostic tool that I can use to determine just what the phone is doing at this time? I have tried emailing myself the logs using log viewer, but they are huge and I can't seem to find anything there that I can sink my teeth into. Any help would be appreciated. My iPhone owning friends are becoming insufferable.
Click to expand...
Click to collapse
have you tried a different modem( also use getril to match modem and ril)
slaphead20 said:
have you tried a different modem( also use getril to match modem and ril)
Click to expand...
Click to collapse
Thanks for the quick reply. I didn't know what a ril was and did a little research. Fascinating.
As far as I can tell, and please bear with me since I am a complete noob here (though I am resonably facile with Linux), since I am running the original ROM, I don't have any influence over the RIL. Is that correct? I downloaded getril, but it says that my device (Verizon GS3) is not supported.
What is the text that would show up in a log if I made a call? I'm going to try and search the logs again, maybe that will tell me something,

[Q] GS3 waits up to two minutes before placing a call

My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
bvz2000 said:
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
Click to expand...
Click to collapse
So several days have passed, and it appears to still be working. I suspect the sd card was the culprit. No idea why. But I am a happy camper again.

Categories

Resources