Has anybody had problems with Voice Command 1.6?
Whenever I try and install it I get an error message that it didn't install properly. I then get Shell32.exe crashing...
On one occassion I managed to soft reset it and everything seemed to work ok except whenever I tried to access settings. Then I would get Shell32 crashing again and forcing me to factory restore settings.
Thanks in advance.
Might have to try Voice Commander instead...
Related
Well after applying a couple tweaks to my KJAM. I have a problem now, I cant uninstall any program. I go to add remove and select remove it then says cant remove, do i want to delete from program list. I also cant reinstall the same app...unless i delete the old directory manually. It seems to me that it is some form of read only protection. any ideas ??
I'm getting the same error as well. I used to have an app on my Jam that would uninstall files and its better then the built in uninstaller. Right now i'm lookin for it but can't remember its name..
i got the same problem
Same here :twisted:
I have had that problem as well. I have found that if I soft reset the device, then run the uninstall, the program is conmpletely removed without issue. I believe that this error is caused by something related to the program still running in the background.
Alex
Tried using ActiveSync to add/remove programs?
I too have the same problem and i soft reset to properly uninstall anything.
You can use SKtools 2.3.30 at http://s-k-tools.com/ to uninstall any program you wish to
works well? thanks for the suggestion
So I just installed skype yesterday, and it ran fine, somehow today when I try to run it, the window busy logo pops up but than it never launches! I tried uninstall than reinstall to my device, than the SD card, but still no luck.... I click on the icon and it just won't launch, I check all my running apps, it's not listed in there......
same thing with my pocketSnes, it will launch fine, but when I try to load any ROM, it will just disappear.
I have 23mb free on my o2 exec and they are all on my device instead of my SD....
can anyone please help or give any suggestions?
thanks in advance.
skype needs lots of rom to run
shut down everything else, if necessary, do a soft reset.
Hello,
I have a problem with sipchange. I installed it to set the Touchpad as standard keyboard. The install was ok, I can start the prog, but when I reboot my X1, he cannot start SIPCHANGE because of a problem with the security of an certificate. Now I want to uninstall sipchange but it is not in the list where I can uninstall programs. What can I do?
Greetings
Pluppi
Thats a tough one.... Umm did you try reinstall SIPCHANGE?
Hello,
I donĀ“t know how to reinstall
Just throw the cab back on ur phone and run it from file explorer. Most likely it will say it needs to uninstall the previous version and even it fails to do so it fix what ever caused the problem.
If I do that, I get a message that it can not be erased, but I can install it if I want. If I do that and try it a next time, I recieve the same message
Do a hard reset, that will get rid of it.
Something happened to my over the weekend. I found it had reset and kept resetting on the loading screen. I took the battery out, popped it on and turned it on. It made it to the home screen but all the apps I had stored on the SD card would close unexpectedly. It looked like ext2 partition crapped out or something as none of those apps would run. So I restored a backup from Nandroid and everything was working again EXCEPT for my SMS/MMS.
Whenever I go into messages, it crashes with a "force close" prompt stating com.android.mms closed unexpectedly. I'm thinking if I could clear all the messages I had save that would solve the problem, but I have no clue where they're stored.
Any advice?
Found what I needed here: http://forum.xda-developers.com/showthread.php?p=2976069&highlight=messages+stored#post2976069
I deleted the DB with the messages, all is well.
same problem here,
clicking "sms" pops up an error msg "com.android.mms ended unexpected"
I have not found any .db files yet :-(
Hello,
Did you deleted mmssms.db or some of "PART_XXXXXXXXXX" files too?
Thanks!
Deleting the mmssms.db file
For no apparent reason my phone's messaging app suddenly started force closing. After multiple reboots, even taking the battery out while phone was on, changing the language settings, and even doing a data factory reset, nothing worked. Found this post and deleted the mmssms.db file, now messaging app works fine, tho I lost all the old messages. That's ok, I had all but the last day backed up to Gmail anyway. So, just delete the database file.
VirtuallyNadine said:
For no apparent reason my phone's messaging app suddenly started force closing. After multiple reboots, even taking the battery out while phone was on, changing the language settings, and even doing a data factory reset, nothing worked. Found this post and deleted the mmssms.db file, now messaging app works fine, tho I lost all the old messages. That's ok, I had all but the last day backed up to Gmail anyway. So, just delete the database file.
Click to expand...
Click to collapse
I have the same problem. Did you permanently delete the database or is it still there? Cos I tried to delete the database throught root explorer but it still remains altho it has deleted all the messages saved in it.
any news on the com.android.mms subject????? I feel very frustrated with my android and i looked everywhere on the internet and can't manage to fix it!
A possible fix
Here's what I did that fixed mine:
I think the root-cause of this error occurred from restoring old messages. There must have been a character/corruption somewhere that was screwing everything up.
Please note the following: I'm using an Evo 4G, running gingerbread-evo-deck-1.2 ROM. I realize this is a G1 thread, but this came up first on google, so I think it would be most helpful here. I was getting the error as described when using the "Messaging" app.
What I did:
Terminal Emulator
su (allow root if prompted)
rm /data/data/com.android.providers.telephony/databases/mmssms.db
Menu > Reset terminal (probably an unnecessary step, but it's what I did)
home screen > remove battery while running
wait 20 seconds
reboot
I don't know why removing the battery that way works. I did try force closing the "Message" app and it didn't work. I realize now I probably should have tried to figure out how to kill the underlying framework, but oh well. I'm not going to try breaking it again.
echoota said:
Here's what I did that fixed mine:
I think the root-cause of this error occurred from restoring old messages. There must have been a character/corruption somewhere that was screwing everything up.
Please note the following: I'm using an Evo 4G, running gingerbread-evo-deck-1.2 ROM. I realize this is a G1 thread, but this came up first on google, so I think it would be most helpful here. I was getting the error as described when using the "Messaging" app.
What I did:
Terminal Emulator
su (allow root if prompted)
rm /data/data/com.android.providers.telephony/databases/mmssms.db
Menu > Reset terminal (probably an unnecessary step, but it's what I did)
home screen > remove battery while running
wait 20 seconds
reboot
I don't know why removing the battery that way works. I did try force closing the "Message" app and it didn't work. I realize now I probably should have tried to figure out how to kill the underlying framework, but oh well. I'm not going to try breaking it again.
Click to expand...
Click to collapse
Works for me thanks
Does anyone else keep getting force close errors? The last 3 builds ive tried keep force closing to the point where I have to delete the data.img and start over. I have tried changing the rom and have tried formatting my sd card. Is anyone else having this problem? Any body have a possible solution?
Which applications do a forced close?
mms, phone, a bunch of other ones. it restarts itself and resets my wallpaper if that helps at all
go into any terminal application (ex: Terminal Emulator)
type in and press enter afterwards
su
fix_permissions
let it do its thing then restart. i make it a habit after a fresh install or after installing many applications to fix permissions.
hope this helps.
-Static
I had the same problem when I switched android builds and tried to restore all my apps. If you clear the problem application's data, uninstall and reinstall, then it should work fine. Statics way might work, Ive never tried it. Jus sayin how I fixed a few of my apps,