Related
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.
I am wondering if anyone else is having an issue where after making setting adjustments (such as ring tone, or screen brightness), once being plugged in for charging, there settings are reverted back or simply enough...changed.
Ive been having this issue and clawing at every possible solution. any suggestions anyone?
Have not had this issue. Are you stock?
no im not stock. im rooted. however ive never had a similar issue with this before. and it did this before root.
For me it's the System Volume
Yes! I have noticed this too. I keep setting my System Volume to about 50%, and it just randomly gets reset back to 100%. I can't figure out of it is an app that is changing it or if turning the phone off and back on does it, or what. It's very annoying.
Hopefully we can determine what's causing it, or if it's a bug and we need Samsung/T-Mobile to fix it.
Your volume is problably from Maps. Everytime I used Google Maps my volume went from whatever I had it set to to 100%
I was having problems with everytime I turned my phone on my animations went from none to full. Drove me crazy. I ended up switching my rom from Stock to Vibrant6 and the issue went away. I haven't tried going back to the first Nandroid Backup I made to see if it was a stock problem or if it was something I installed.
I do recall that after I played with my Font it started happening. Of course I'm not sure if that caused it or not.
I have had this problem ever since Clockwork recovery. if I reboot to do a nandroid my fonts go back to default however whatever i have chosen (ie choco) is still highlighted. the system volume changes at the same time too.
i asked over at cyanogenmod and i seemed to be the only one.
i was about to post a thread about this too lol. mine isn't rooted. i had my ringtone on the silent one, but all of a sudden i hear the tmobile jingle. i was confused cause i had it on the silent ring tone. also have this issue: once i get a text my lockscreen stays on, it doesn't turn off or anything.
I have the issue with ring and notification tones getting changed back to default.
It doesn't seem to matter where I store them.
my phone is rooted, but no other mods
1) Can't set the default ringtone. I can go into settings and select a ringtone but for some reason the defauls stays on silent. Have to set ringtone for each contact. If a non contact number calls, no ringtone just vibrate. FYI the power control widget only has two options, speaker with vibe lines and phone with vibe lines. nothing else.
2)With Update 4.0.4c moving from one remembered wifi connection to another I got an error in the menu. Can't turn wifi on at all. Restoring to original WB rom if this is a consistant problem.
Can someone give me some advice here?
Forever a noob
Re-installed rom for a 5th time. Installed doom kernal. Took care of the first problem. Have not updated to 4.0.4 c yet. Not sure if I want to now
Okay, I would have liked to post this in development but apparently I dont have enough posts. What is th deal with the phone dropping out on CM10 when the screen goes black from the sensor, then coming back when the call is dropped by the other person. Does anyone have a fix for this, the CM10 thread gets so diluted with different issues you'd think people would start making other topics regarding issues rather than discussing them throughout a 30 page thread.
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
tallyforeman said:
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
Click to expand...
Click to collapse
Yeah but it also drops the phone call when that happens.
Thanks really strange. Try getting a fresh download with the gapps and flash it again.
It's a good thing you didn't post this in the development because it would have been moved here. You can always PM me with questions and I try my best to respond to everyone in a timely manner.
Anyhoo. I'm not quite sure as to why this isn't working yet. I've called my family, friends, girlfriend, whomever a few times already and haven't ran into the problem yet. With this being said, no one is giving any real details on what leads up to the problem or how to really reproduce it. The best I've received so far is "I make a call, the screen goes off and won't go back on." What I need is someone to get me the logs of this happening. As weird as this may seem it's the only way I can help anyone with it. Apparently from what I hear the phone is still "working" but with the screen just not turning back on. If this is the case, anyone should be able to plug their phone into their computer and get me a logcat of what is going on (this doesn't require any screen interaction if the phone is setup properly). If you have any questions on how to get one, search the forums. It's been posted in just about every development forum for every phone including ours.
My phone did that last night. People in the CM10 thread have been blaming it on the bluesleep fix but who knows. I had that flashed at the time too. When it happened, I was on a call and the call dropped a few minutes into the conversation, the screen stayed black and didnt come back on. I had to pull the battery and restart. I called the person back and it happened again. Long story short, due to my own error, one thing led to another and I ended up SBF'ing. Since last night, I made one call and it didnt happen. I need to make more calls to see if it persists. The problem is, I dont call people very much. lol
Just want to add that I was having this issue also. I only noticed it after I installed the bluesleep fix... I SBF'd and installed clean with no bsfix and have not had this issue since... Maybe it has nothing to do with bluesleep but thats some really strange timing if it doesnt.
If it happens to me again I'll get a log for you DZK but seeing as I don't plan on flashing the bluesleep fix back I don't think it will happen.
Well I sent a message to you DZK cause i'd really rather avoid SBF if I could. But if I have to I will because most people are linking it to the bluesleepfix which I did indeed install. In any case, the phone just hangs when the screen shuts off until the other person hangs up the phone then the call is ended and the screen comes back, but until then voice is dropped the call is droped and the screen remains off as that person tries to talk to me but isnt disconnected until they end the call.
[Tutorial] How To Logcat
Logcat or it never happened.
download adb
place it in folder I use
Code:
c:/root
open command prompt
Code:
cd/
Code:
cd c:root
Code:
adb logcat *:E > oh_nos_it_crashed.txt
should work
oh_nos_it_crashed.txt will be in root folder can name it
Code:
adb logcat *:E > dropped_call.txt
if you want
I'm having similar issues. The phone locks up on a call and can't be unlocked. I just have to pull the battery. The call continues for me, so at least I can finish the call, but to hang up - pull the battery.
I currently have the CM10 ROM, gapps v5, and bluesleep fix applied.
So, how does one get rid of the bluesleep fix? Can I delete is somehow using a root browser, adb, or... ? If not, can I just reflash the ROM and gapps files (without the bluesleep fix) without a factory reset, etc.? Or am I in for a complete refresh of the phone and reflash of the ROM and gapps?
TIA
no way to remove bluesleep that i remember
just restore nandroid of rom other than cm10, then reflash cm10
This started happening to me tonight.
I haven't installed the Bluesheep fix... unless that's the MX2 wifi patch.. if that's the case then I have that too.
My current workaround is using headphones, which disables the proximity sensor.. I also put my phone to stay cycle a little longer.
I just flashed my phone with CM10a3 Wednesday and ran into this issue with the first call I tried to make. I'm still new to rooting and flashing ROMs (my first time lol) so I don't have too much useful information, I will try and gather some logs next time it happens. Unfortunately it is not something that seems to happen every call. My current work around is to use bluetooth or speaker phone as the issue does not happen then.
I'm using
CyanogenMod 10-20130113-Daytona Alpha 3
gapps-jb-20121011-signed
I'm also running into issues with the mount locations and losing settings upon restart, however I still need to do more research on those items first.
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
licwid said:
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
Click to expand...
Click to collapse
lol carrying headphones around? that sounds a bit overkill.
This seems an overly obvious question. Does the watch have vibrate? I just got it two days ago, but no setting of vibrate anywhere seems to make it shake. I would think I'd have run across someone else saying something if it lacked the ability...
So, kinda wondering if mine is broken or if I totally missed that it isn't there.
Thanks
jd
jdommer said:
This seems an overly obvious question. Does the watch have vibrate? I just got it two days ago, but no setting of vibrate anywhere seems to make it shake. I would think I'd have run across someone else saying something if it lacked the ability...
So, kinda wondering if mine is broken or if I totally missed that it isn't there.
Thanks
jd
Click to expand...
Click to collapse
Mine vibrated yesterday and now it wont vibrate. If you scroll down from the top on your home screen, click the icon in the top right corner, that should bring up your wifi, airplane mode, gps, battery, etc icons. If you scroll down to audio profiles, there is one called meeting that has a picture of a phone vibrating. That should make calls and messages vibrate your phone. You can also manually turn them on because if you go to settings/device/audio profile/settings for general where you can select vibrate plus ring, and if you scroll down there is an option for vibrate on touch. Even though I have both these settings checked, and they used to work, they are no longer working. I tried a factory reset, and that didn't fix it. Now, when I power on my watch, I get a message that says headphones disconnected. It seemed to stop working after I started getting this message, not sure if that is normal or if it has anything to do with it. I will let you know if I figure out a way to get mine vibrating again, but for now it looks like mine could be broken. Can anyone else chime in on this if this has happened to you?
flimmyflam said:
Mine vibrated yesterday and now it wont vibrate. If you scroll down from the top on your home screen, click the icon in the top right corner, that should bring up your wifi, airplane mode, gps, battery, etc icons. If you scroll down to audio profiles, there is one called meeting that has a picture of a phone vibrating. That should make calls and messages vibrate your phone. You can also manually turn them on because if you go to settings/device/audio profile/settings for general where you can select vibrate plus ring, and if you scroll down there is an option for vibrate on touch. Even though I have both these settings checked, and they used to work, they are no longer working. I tried a factory reset, and that didn't fix it. Now, when I power on my watch, I get a message that says headphones disconnected. It seemed to stop working after I started getting this message, not sure if that is normal or if it has anything to do with it. I will let you know if I figure out a way to get mine vibrating again, but for now it looks like mine could be broken. Can anyone else chime in on this if this has happened to you?
Click to expand...
Click to collapse
I cannot get my vibrate to work again, if anyone has experienced this, please reply and let me know how to fix it, for now, i am giving up, and extremely disappointed
jdommer said:
This seems an overly obvious question. Does the watch have vibrate? I just got it two days ago, but no setting of vibrate anywhere seems to make it shake. I would think I'd have run across someone else saying something if it lacked the ability...
So, kinda wondering if mine is broken or if I totally missed that it isn't there.
Thanks
jd
Click to expand...
Click to collapse
It does vibrate. But very few things use that function it seems. I was thinking about setting up a tasker script to vibrate on any notification.
mortis2600 said:
It does vibrate. But very few things use that function it seems. I was thinking about setting up a tasker script to vibrate on any notification.
Click to expand...
Click to collapse
Anyone have any ideas on how to get mine vibrating again? I've done the backup and restore option, is that how you do a proper factory reset, or is there another way I can try to get this thing to start working again?
update: Just flashed 1900_20140120 firmware using the excellent guide on here, and still no vibrate
flimmyflam said:
Anyone have any ideas on how to get mine vibrating again? I've done the backup and restore option, is that how you do a proper factory reset, or is there another way I can try to get this thing to start working again?
update: Just flashed 1900_20140120 firmware using the excellent guide on here, and still no vibrate
Click to expand...
Click to collapse
Mine started working. Not sure why; I tried to reset to factory and despite following the directions and watching Loki's video, i managed to lock the watch up. Popped the battery, put it back together, wiped the device. Now it vibrates and that is good. Just wish i knew what I had did that fixed it.
Thanks all!
Jd
Mine does not vibrate either, never did.
I tried with the stock firmware, Loki's firmware, stock with enhanced security... no luck...
Thoughts?
jdommer said:
Mine started working. Not sure why; I tried to reset to factory and despite following the directions and watching Loki's video, i managed to lock the watch up. Popped the battery, put it back together, wiped the device. Now it vibrates and that is good. Just wish i knew what I had did that fixed it.
Thanks all!
Jd
Click to expand...
Click to collapse
stanelie said:
Mine does not vibrate either, never did.
I tried with the stock firmware, Loki's firmware, stock with enhanced security... no luck...
Thoughts?
Click to expand...
Click to collapse
Mine started vibrating again. I went to take the battery out, but couldn't get the screws off, so I gave up, when I rebooted, all the sudden vibrate worked again. Not sure if it was powering it on and off a few times, or shaking it around, try taking the battery out and putting it back in if you can, if not, just try turning it off and then on and maybe lightly shaking it around
Well,
It looks like a bad electrical contact, I've downloaded an app called "vibrater" that does just what it says, and it won't start the vibrator until I lightly tap the watch on it's side while the app is turning the vibrator on.
But it does not stick. I guess I will have to return the watch to have it fixed...
Until tonight, I thought the TrueSmart just didn't have a vibrator...
Vibration doesnt work
Hey, just received my Omate Trusmart! (Kickstarter edition)
Overall I am extremely happy with the watch, but there are a couple of major problems:
1. The vibration doesn't work, I have tried rebooting, factory restore etc but nothing seems to work. Does anyone know a fix to this or is it a hardware problem?
2. My screen has very faint dark spots in the center. Looks like a manufacturing defect.
Is it possible to return the watch to get a replacement? I havent opened the back cover yet.
Thanks.