Camera and CallUI force closes - G4 Q&A, Help & Troubleshooting

I don't know what happen,but i will try to explain my problem.
I tryed different ROMS, but never switch out from Stock Roms (Stock, Genisys and now Imperium). I never had problems, everything always runs fine as it's supposed to be. However, yesterday afternoon i got the first "Camera has stopped working", Whatsapp can't access camera and also the camera Apps keeps FC. I tryed to reboot, clean data and cache, cleank dalvik. Nothing helped, so this morning i flash the last Imperium versio (5.0, i was onto 4.0).
It helps, because than camera starts to work again and no problem. After 7-8 hrs, the problem comes back again but also with "InCallUI has stopped working". So i flashed again Imperium Rom, but even at the startup Wizard the "Camera has stopped working" message appears istantly. When i finish the wizard, if i try to Call the UI does not appear (but the call starts and who i call receive my call lol). I tryed few flash but no helps, still got problems.
When i flash i go to TWRP, clean system, data, dalvik cache, cache. Then i flash the zip. I haven't installed any mods after, just messaging apps and social apps.
What the hell is happening and what i need to do to resolve this problem?! I thought switch to CM/AOKP/RESURRECTION and try another rom but i prefer to stay into stock .. I have also thought to flash KDZ of the last 815 release and than again Imperium, maybe it helps.
Any tips? Thanks for your time.

Vipery said:
I don't know what happen,but i will try to explain my problem.
I tryed different ROMS, but never switch out from Stock Roms (Stock, Genisys and now Imperium). I never had problems, everything always runs fine as it's supposed to be. However, yesterday afternoon i got the first "Camera has stopped working", Whatsapp can't access camera and also the camera Apps keeps FC. I tryed to reboot, clean data and cache, cleank dalvik. Nothing helped, so this morning i flash the last Imperium versio (5.0, i was onto 4.0).
It helps, because than camera starts to work again and no problem. After 7-8 hrs, the problem comes back again but also with "InCallUI has stopped working". So i flashed again Imperium Rom, but even at the startup Wizard the "Camera has stopped working" message appears istantly. When i finish the wizard, if i try to Call the UI does not appear (but the call starts and who i call receive my call lol). I tryed few flash but no helps, still got problems.
When i flash i go to TWRP, clean system, data, dalvik cache, cache. Then i flash the zip. I haven't installed any mods after, just messaging apps and social apps.
What the hell is happening and what i need to do to resolve this problem?! I thought switch to CM/AOKP/RESURRECTION and try another rom but i prefer to stay into stock .. I have also thought to flash KDZ of the last 815 release and than again Imperium, maybe it helps.
Any tips? Thanks for your time.
Click to expand...
Click to collapse
try the KDZ. if it continues then it must be a hardware problem..

raptorddd said:
try the KDZ. if it continues then it must be a hardware problem..
Click to expand...
Click to collapse
Thanks for reply, i have fixed the problem. Just pull out and put in the battery, idk what happen it seems to be solved now.

Related

Strange Browser Crashing

Hi,
First off, apologies if this doesn't belong here, getting confused as to where things should go, can someone move it if it's in the wrong place please.
I have Flashed the LeeDrOiD v2.2d ROM and when accessing the Stock browser it will randomly crash, it's a strange crash because normally a crash will mean that you will exit from the browser and next time it will load to the homepage, on mine though it will sort of crash but then load the page I was on, even if it wasn't my homepage, if I had any tabs open I would also lose all of those, which is how I know it's crashing.
This isn't specific to this version of the ROM though as I've had this since v1.4 or to any ROM because I've Flashed 3 different other ROM's (2 Sense and 1 Stock) and this still happens. I've asked before in the XDA LeeDrOiD thread and they said it could be related to backing up and restoring data whilst moving from Android 2.1 to 2.2.
What I have done this time though is not backup anything, no SMS, no system settings, nothing! I deleted everything off my SD Card, cleared the cache, then cleared the Dalvik cache, did a factory reset, Flashed the ROM and then Flashed the radio but still this problem exists, I haven't backed up anything this time, even created a new Google account so it didn't sync my contacts.
There's no particular website that does it, I've got the Flash setting to "On Demand", so that's not crashing it.
This is really starting to annoy me now but I can't figure out for the life of me why it happens, I've tried replicating it to narrow down the cause but I can make it happen one time doing it a certain way but then doing it that way again it'll be fine.
Has anyone got any ideas of how I can overcome this problem or how to Flash the ROM so that my browser will work correctly, this browser problem is the only problem I have with the ROM, apart from that it is superb.
To Flash the ROM I would do the following:
I go into the Recovery mode, wipe the Dalvik cache, then wipe the cache, do a Factory Reset and then Flash the Radio and then the ROM.
Isn't that supposed to completely wipe the phone and then anything Flashed from there is brand new, which is confusing if it is happening in different ROM's.
Also, the browser can crash whether I'm connected to a data plan/Wi-Fi or not!
Any help very much appreciated!
HTC Desire btw.
Anyone?
Someone must have an idea.
It has happend to me few times also, altho it seems preaty random but for me the latest version of lee it seems kinda laggy on stock hrowser, i even flashed the text reflow fix, i started to hate it on some forums since it was scrooling me back to the top of the page... welak with u'r problem and mine, no idea, but well u aint alone
littlej said:
It has happend to me few times also, altho it seems preaty random but for me the latest version of lee it seems kinda laggy on stock hrowser, i even flashed the text reflow fix, i started to hate it on some forums since it was scrooling me back to the top of the page... welak with u'r problem and mine, no idea, but well u aint alone
Click to expand...
Click to collapse
In a strange way that's good to know mate, at least it's not just me.
Hopefully there's a fix to this problem, finding the cause is hard enough though!
Well, I've managed to narrow it down as much as possible, seems to happen more when downloading from the Market or the Internet connection switches from 2g, H or to WiFi.
I personally think it has something to do with the cache, once it starts happening it happens alot, a restart later and it probably won't happen for most of the day, it's like something leaks and builds up and then crashes the browser with a restart resetting everything.
Anyone got any ideas?

[Q] Force Closes after Flashing Sense ROM

Ive installed the "HTC Sense" ROM numerous times.
(http://forum.xda-developers.com/showthread.php?t=837042)
After installing everything works good for a while, things start messing up after i leave the phone down for a while or restart the phone. After the phone restarts i constantly GET FC's.
android.process.acore has stopped working
android.process.swype.inputmethod has stopped working
Occasionally GMail will FC to but that stopped after a factory reset.
Ive installed this ROM a good 5 times. IM coming from a deodexed STOCK android ROM.
Ive Wiped Dalvik
Did a factory/data reset
Chose the ZIP file
and booted back into system
and it works good until i leave the phone for a bit or restart it.
I flashed back to stock since i cant use the phone with the constant force closes.
I REALLLY would love to use the Sense ROM. Any help would be appreciated.
Thanks!

CM10.1.3 crashed and softbrick

I have been running CM 10.1.3 for quite a while, and 10.1.2 for a while before that, and out of nowhere last night I was on the browser and it closed, and wouldn't open again. Then every other app I tried wouldn't open, just forced closed right away. Next thing I know, trebuchet starts force closing over and over. So I reboot my phone, and no bootscreen. I used TWRP to recover back to stock and it works fine. But everytime I try to re-install CM it just bootloops. I didn't change anything on my phone for it to crash, i haven't even changed any apps for a few weeks. Anyone know why it would do this?
jamesclay89 said:
I have been running CM 10.1.3 for quite a while, and 10.1.2 for a while before that, and out of nowhere last night I was on the browser and it closed, and wouldn't open again. Then every other app I tried wouldn't open, just forced closed right away. Next thing I know, trebuchet starts force closing over and over. So I reboot my phone, and no bootscreen. I used TWRP to recover back to stock and it works fine. But everytime I try to re-install CM it just bootloops. I didn't change anything on my phone for it to crash, i haven't even changed any apps for a few weeks. Anyone know why it would do this?
Click to expand...
Click to collapse
Do you have TWRP version 2.6.3 by any chance? Most of the bootloop bugs have been attributed to that specific version.
If you do have 2.6.3, downgrade to, I believe, 2.6.1. Otherwise, did you forget to do a cache, dalvik cache, data, and system partition wipe before upgrading your ROM?
sagirfahmid3 said:
Do you have TWRP version 2.6.3 by any chance? Most of the bootloop bugs have been attributed to that specific version.
If you do have 2.6.3, downgrade to, I believe, 2.6.1. Otherwise, did you forget to do a cache, dalvik cache, data, and system partition wipe before upgrading your ROM?
Click to expand...
Click to collapse
Actually, I am running 2.4.4. Whats still odd about it though is that it ran fine for at least a month and had been on all day. The problem didn't start with a reboot, I had been on it for a while and everything forced closed on me. I am about to try to update TWRP to 2.6.1 and try that. I haven't tried any other roms yet either, I would really like to stay on CM though if I can get it to flash back.

Problem Booting

so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Are you still using the same version of TWRP you used to flash slimbean 4.1? If you are trying to flash newer ROMS with an older version of TWRP, that could be causing the problem.
supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Try TWRP 2.6.1.0

[Q] com.android.phone has stopped after reverting to stock

Hello,
I rooted my M919 and tried a few ROMs to hopefully find one that I liked, but it seems that they all have bugs that make the phone unusable for me. (Flashed a Google Edition rom, the proximity sensor didn't work anymore, so I couldn't end a call, ever).
Now I am trying to flash the stock firmware, and it seemed to have worked, except I get the com.android.phone has stopped, CONSTANTLY. I already have tried clearing data/cache several times, no luck.
Any ideas?
Thanks!
jtleniger said:
Hello,
I rooted my M919 and tried a few ROMs to hopefully find one that I liked, but it seems that they all have bugs that make the phone unusable for me. (Flashed a Google Edition rom, the proximity sensor didn't work anymore, so I couldn't end a call, ever).
Now I am trying to flash the stock firmware, and it seemed to have worked, except I get the com.android.phone has stopped, CONSTANTLY. I already have tried clearing data/cache several times, no luck.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Try using a different recovery. I've had that problem before, baseband and IMEI were shown as unknown and com.android.phone would force-close constantly. I don't know why the recovery would cause that, but switching recoveries worked for me.
I had this same issue yesterday, very strange that I would see this listed here about the same time. I haven't done anything different, that I haven't done before. Then I flashed the stock T-Mobile rom and it still kept doing it. Apn settings disappeared when this happened.

Categories

Resources