I recently had a problem with cm 4.2.13. Whenever I opened the Dialer or the Contacts and tried to make a call I got an acore system force close. I don't know what happened. I tried a backup restore, but I had just done one after flashing 4.2.13 before I found out about the dialer issue. After a couple hours of being pissed off, I decided to reflash 4.2.12.2 and it fixed the problem. Just putting it out there that this worked for me in case anyone is having the same problem.
Its mention in the changelog in the post along withh an updated apk
dglowe343 said:
I recently had a problem with cm 4.2.13. Whenever I opened the Dialer or the Contacts and tried to make a call I got an acore system force close. I don't know what happened. I tried a backup restore, but I had just done one after flashing 4.2.13 before I found out about the dialer issue. After a couple hours of being pissed off, I decided to reflash 4.2.12.2 and it fixed the problem. Just putting it out there that this worked for me in case anyone is having the same problem.
Click to expand...
Click to collapse
Did you flash contacts 2.8 afterwards? i did and i dont have any problems.
I had this issue too, had to revert to a backup and reinstall *.13 and the 2.8 dialer
Should this not be in the CM thread?
dglowe343 said:
I recently had a problem with cm 4.2.13. Whenever I opened the Dialer or the Contacts and tried to make a call I got an acore system force close. I don't know what happened. I tried a backup restore, but I had just done one after flashing 4.2.13 before I found out about the dialer issue. After a couple hours of being pissed off, I decided to reflash 4.2.12.2 and it fixed the problem. Just putting it out there that this worked for me in case anyone is having the same problem.
Click to expand...
Click to collapse
Have you try this trick
http://jjpda.blogspot.com/2012/07/android-404-contacts-force-close.html
jjamain said:
Have you try this trick
http://jjpda.blogspot.com/2012/07/android-404-contacts-force-close.html
Click to expand...
Click to collapse
You resurrected a two year old thread related to Android 2.1 to spam about your blog w/ a Android 4.0 post?
Related
{First of all, i DID search high and low to find the answer to my problem before i made this thread.}
I have been using Cyanogen 4.1.11.1 ROM for sometime now without any problems. A couple of day ago i started getting force closes everytime i tried to go on the android market. I tried reflashing my phone using the CM Updater as i thought this might solve the problem, but that didn't work. I have cleared the market data via setting>application settings>manage applications>market>clear cache. That didnt solve the problem either.
Is anyone else using the same ROM as i am and experiencing the same problem?
Does anyone know how i can fix this problem.
Thanks.
This is an APP question post in the correct area!!!
shaun1509 said:
{First of all, i DID search high and low to find the answer to my problem before i made this thread.}
I have been using Cyanogen 4.1.11.1 ROM for sometime now without any problems. A couple of day ago i started getting force closes everytime i tried to go on the android market. I tried reflashing my phone using the CM Updater as i thought this might solve the problem, but that didn't work. I have cleared the market data via setting>application settings>manage applications>market>clear cache. That didnt solve the problem either.
Is anyone else using the same ROM as i am and experiencing the same problem?
Does anyone know how i can fix this problem.
Thanks.
Click to expand...
Click to collapse
wrong section or not, i have the exact same rom on my dream and the market runs fine. just move the cm-update zip folder out of the cm updater and put it in the root of your sdcard then try wiping and reformating it. might help, might not. it's not a rom issue though as the market works fine on mine.
Ok thanks for the info ill try that now
Problem Solved
I wiped/factory reset, rebooted and it works fine again now. i dont know what caused this though.
Thanks
Hello!
GTalk on my sensation keeps crashing!! It tries to open then just dies! Any ideas? I'm running stock 2.3.4 and its been doing this for a few days now.
Everything else works fine!
Thanks in advance for any help.
eibbig said:
Hello!
GTalk on my sensation keeps crashing!! It tries to open then just dies! Any ideas? I'm running stock 2.3.4 and its been doing this for a few days now.
Everything else works fine!
Thanks in advance for any help.
Click to expand...
Click to collapse
I had a similar problem after I deleted something from my rooted stock ROM. Reinstalling voice search from Market caused force closes (I tried to install different versions). Solved the problem after re-flashing.
AlexFlexy said:
I had a similar problem after I deleted something from my rooted stock ROM. Reinstalling voice search from Market caused force closes (I tried to install different versions). Solved the problem after re-flashing.
Click to expand...
Click to collapse
Its not even rooted haha so couldnt have deleted any sys info or anything! Not sure if it might be some kinda glitch in the f/w variant?
If you are using the APEX launcher instead of the Sence launcher DO NOT install the update that came down today for the apex launcher. It causes a fatal stop responding error. Clear all the caches did not work. The only thing that ended up working was a factory reset. If you happen to have a backup from a couple days ago that will work too.
Please get the word out, I don't have enough spam posts to post in the development thread but people need to know before they lose their phone setups and have to start all over.
*It has come to my attention that other custom ROM users are experiencing similar things as this. Be Aware!*
Gwraith said:
If you are using the APEX launcher instead of the Sence launcher DO NOT install the update that came down today for the apex launcher. It causes a fatal stop responding error. Clear all the caches did not work. The only thing that ended up working was a factory reset. If you happen to have a backup from a couple days ago that will work too.
Please get the word out, I don't have enough spam posts to post in the development thread but people need to know before they lose their phone setups and have to start all over.
Correction: Nocturnal 3.7 SE
Sorry I typed it way too fast.
Click to expand...
Click to collapse
Have u sent a pm to the dev of the Rom letting him know the issue you were having? That way if there is a problem he can look into for the other users.
Its true for any ICS ROM. I'm on stock 2.20 and the update killed it.
EDIT: The developer released an update and it fixes the FC.
Sent from my HTC One X using Tapatalk 2
Please change the title, it's misleading
Sent from my HTC One XL using Tapatalk 2
Lol for a second I thought we screwed up..
Sent from my HTC One X
Gwraith said:
If you are using the APEX launcher instead of the Sence launcher DO NOT install the update that came down today for the apex launcher. It causes a fatal stop responding error. Clear all the caches did not work. The only thing that ended up working was a factory reset. If you happen to have a backup from a couple days ago that will work too.
Please get the word out, I don't have enough spam posts to post in the development thread but people need to know before they lose their phone setups and have to start all over.
Correction: Nocturnal 3.7 SE
Sorry I typed it way too fast.
Click to expand...
Click to collapse
You can do this.. remove/uninstall older version using titanium backup, try installing new version ( try manually pushing apk to /system/app if you still have issues)
kancherlapraneeth said:
You can do this.. remove/uninstall older version using titanium backup, try installing new version ( try manually pushing apk to /system/app if you still have issues)
Click to expand...
Click to collapse
Hmmm, that would require some in-depth CMD prompt knowledge with ADB. Since the error crashes the Launcher there is no way to access the phone anymore. It just continue to crash loop. I did however find that if you left the use this every time between Sense and APEX you can switch to Sense and then access your phone. If you checked it then the only way I found to correct the problem is a format or back-up pre APEX update.
Now my Nocturnal Apps / Mods are gone and reinstalling after factory reset corrupted the load again and I have to factory reset again. I didn't delete the SD card might have something to do with that. Either way, they'll fix this soon enough or NSE 3.8 might be out soon for upgrade.
Gwraith said:
Hmmm, that would require some in-depth CMD prompt knowledge with ADB. Since the error crashes the Launcher there is no way to access the phone anymore. It just continue to crash loop. I did however find that if you left the use this every time between Sense and APEX you can switch to Sense and then access your phone. If you checked it then the only way I found to correct the problem is a format or back-up pre APEX update.
Now my Nocturnal Apps / Mods are gone and reinstalling after factory reset corrupted the load again and I have to factory reset again. I didn't delete the SD card might have something to do with that. Either way, they'll fix this soon enough or NSE 3.8 might be out soon for upgrade.
Click to expand...
Click to collapse
I have seen posts about these issues for apex launcher in several threads. I downloaded and apk file , installed it and did not get any force closes
Sent from my One X using Tapatalk 2
this has been fixed
Hey guys,
since a few days I have this very annoying problem that apps disappear from my phone. I definitely don't unistall them or anything like that. When I reinstall the missing app all my data is still there. Is there a sollution for it?
I'm running Trickdroid 3.0.0
.TanTien said:
Hey guys,
since a few days I have this very annoying problem that apps disappear from my phone. I definitely don't unistall them or anything like that. When I reinstall the missing app all my data is still there. Is there a sollution for it?
I'm running Trickdroid 3.0.0
Click to expand...
Click to collapse
Similar issue
Are they only disappearing from the drawer, i. e. Are the apk in data/app? Could just be randomly frozen which you can fix with titanium backup
The whole apk is disappearing...
Sent from my HTC One S using Trickdroid v3.0.0
It could be a problem with the ROM or the way it was flashed. Backup everything and then wipe /data and /cache. Then reflash the ROM but DON'T restore your backup up. Wait and see if the app disappears by itself. If so, the ROM is the problem. If the problem seems to go away you can try to restore your backup.
Hi,
Thanks for a very helpful forum!
I have installed [ROM] Android 4.3 (JSS15J) on Nexus S in thread:
http://forum.xda-developers.com/showthread.php?t=2380527
Camera works but every 1-4 photo i hangs with message "unfortunately, gallery has stopped" and i have to reopen the camera.
When switching from front to back camera it happens every time. Both cameras work.
Everythins else on the phone works like a charm.
- I'm using TWRP.
- Rooted with UPDATE-SuperSU-v1.51.zip
- I have tried different gapp packages: gapps-jb43-20130810-dmd151.zip and gapps-jb43-20130726-signed.zip
- I have reinstalled everything severals times from scratch.
- Before every install i have wiped everything thats possible, cache/dalvik etc.
- Tried different camera apps and they dont produce this problem.
- Tried "Take bug report" several times but nothing happens after that, weird.
Ive searched the internet and read every thread on this forum with similar problems, nothings helps.
If anyone out there know anything i dont about fixing this, let me know
I went from stock 4.1.2 and never had any camera problems.
Use only doomed gapps
leap_ahead said:
Use only doomed gapps
Click to expand...
Click to collapse
As i wrote ive tested gapps-jb43-20130810-dmd151.zip from http://forum.xda-developers.com/showthread.php?t=2379296
Is that what you mean with doomed?
Thanks for your reply!
okopop said:
As i wrote ive tested gapps-jb43-20130810-dmd151.zip from http://forum.xda-developers.com/showthread.php?t=2379296
Is that what you mean with doomed?
Thanks for your reply!
Click to expand...
Click to collapse
yes that I use and I don't have any problem
From posts i have read i feel im not alone with this problem, or am i??
Switching from front to back camera makes it FC every time.
Any tip how to dig deeper to find whats going on?
This is how i fixed it!
I changed to this ROM instead.
http://forum.xda-developers.com/showthread.php?t=2402655
And this gapp package:
http://forum.xda-developers.com/showthread.php?t=2397942
Much more stable, for me at least.
No more FC when switching camera or taking shots.
Im a very happy puppy!