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.
Related
Hello,
Looking for help with a strange and sporadic problem.
95% of the time when I start a new text message (includes replying to other messages in a thread), the first letter of the first word I type disappears almost immediately after I type. If I retype the letter, it remains and I can continue typing normally.
I've gotten to the point where I double tap the first letter on every new message but it's an annoyance.
Also, I have another sporadic problem with my text messaging screen closing in the middle of typing out a new message.
I hope someone can help.
I did a hard reset and after no problems I started by installing cabs one by one. The problem started after the first install. > SPB Shell 3.0
I have further found the issue only occurs when the phone goes to sleep. The first time you try to type a message after waking the phone up, the first letter of the message disappears and you have to double tap it to continue. All messages after that type in fine unless you let the phone go back to sleep, then the very first message after that has the same problem again.
Any help would be appreciated.
Ah well. I was able to find a solution. I figured I would update the thread in case anyone else had the same problem in the near future.
Solution: Upgrade to the Spb Mobile Shell 3.0.1 beta-version Whatever the bug was is now fixed in the newer version.
Disregard
Disregard. Problem came back about as quickly as it went away.
I have further realized the problem only occurs when the following 3 conditions exist:
1/ SPB Mobile Shell is installed.
2/ SMS messaging in threaded conversation mode.
3/ Only when the messaging has been completely shut down. If the conversation window has been closed and reopened, everything is still fine. It is only when the messaging has been completely shut down.
With all the knowledgeable brains here, I thought someone might have a suggestion or solution. :-(
It has nothing to do with shell...I dont have that onb my phone and mine does that every once in a while
Hmmm of all issues i thought this would be the easiest to find solution, but seems to still be apparent
http://forum.xda-developers.com/showthread.php?t=490071
what kind of rom it is?
I have this problem too.. Just letting the community know if it's any extra inspiration to keep attacking this bug.
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
I pulled down the update this morning (finally) and now I am not getting my ring/chime when I receive a text or call. Just vibrate. And no, I'm not on vibrate... If I go into settings>sound and try to open the volume, ringtone, or default notification menus, the settings app freezes. Eventually I get a pop up asking if I want to wait or kill it. I've waited and waited and it never works. Killing it and trying again doesn't work either. Neither does a reboot. Everything else seems to work ok, from what I can tell so far. What is going on here?
Not sure if there is any relation, but as it finished up the app updates during the upgrade (I think it said starting apps) it froze. I did power + vol- to turn it off and then rebooted. Got the upgrade successful message.
Thanks for your help.
My phone froze on the exact same screen and I ended up doing the same thing. Here's the thing: From what I can tell, the phone wasn't really stuck. For some reason, it might take up to 2 hours for some people to make it past that point. So, something is running in the background, even though it is stuck.
If you perform a Power + Volume Down force shutdown, when you reboot it will eventually tell you that the install was successful. But..., everything that it needed to do wasn't really done. In my case, the only way to fix things was to perform a Factory Reset (not as scary as it really sounds). That fixed it for me.
Can't say it will work for everyone, but I do recommend it anyone who performed the forced shutdown because s/he though the phone had frozen.
illinicj said:
I pulled down the update this morning (finally) and now I am not getting my ring/chime when I receive a text. If I go into settings>sound and try to open the volume, ringtone, or default notification menus, the settings app freezes. Eventually I get a pop up asking if I want to wait or kill it. I've waited and waited and it never works. Killing it and trying again doesn't work either. Neither does a reboot. Everything else seems to work ok, from what I can tell so far. What is going on here?
Not sure if there is any relation, but as it finished up the app updates during the upgrade (I think it said starting apps) it froze. I did power + vol- to turn it off and then rebooted. Got the upgrade successful message.
Thanks for your help.
Click to expand...
Click to collapse
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.
First i noticed that whenever i chat with someone over messenger, it starts calling them randomly while i type.
I thought it's about messenger and i cleared the cache and reinstalled it. Problem is still occurring.
Later, i noticed in one game that screen does that touch again - on the very same spot as in messenger - somewhere in the top right corner (where's the call button in messenger).
I turned off the phone, waited 2-3 minutes and then turned it on. Problem is still occurring.
I started service "thing" (found on the internet what to type in the dial to activate it) and tested the touch screen, everything seems to be okay. So from my experience it seems it's not hardware problem. Do you have any suggestion or experience with this kind of problem? I wish i could fix my phone
And one more thing, it happens only when i'm touching the screen too, it wont do that when i leave it alone and just watch the display.