eversince ive installed the beta4 on my x10 im getting random force close nd even reboot is not fixing the problem can anyone please help!!!!
Did you restore data from eclair? If yes then that causes random reboots and force closes. I would recommend you to perform a full system wipe and install beta 4 afresh. Now after doing that don't restore data from eclair. That will cause the above problems again.
I hope this has helped you out.
Cheers!
AdY
Also, did you flash new baseband?
i have the latest baseband 2.1.54 and i did restore my contacts from eclair through
the contacts import and export do that also cause fc?
Related
i updated wolfbreak‘s v60 from v54
when i reboot all stuff fc fc fc fc
how can i fix this???
i think u must flash it new with full wipe etc
YEA what he^^ said.. I just did a full wipe and installed v55 yesterday, then I saw that v6 was up so I flashed that on top.. I have had a few FCs but no big deal
Wolfbreak himself recommends us to do a fresh installation of the new v06 update, which means starting from wiping and installing the base v05 first.
same here after i had my apps restored it goes FC FC FC FC .v.
Do not restore apps' data.
- Do a full wipe.
- Clean cache.
- Clean Dalvik cache.
- Wipe battery status.
- Install WB v05.
- Reboot, log in into Market, etc.
- Install WB v06.
- Install your apps manually. I installed them using Titanium Backup, no data restore, just the apps, and got no FCs.
ricardofago said:
Do not restore apps' data.
- Do a full wipe.
- Clean cache.
- Clean Dalvik cache.
- Wipe battery status.
- Install WB v05.
- Reboot, log in into Market, etc.
- Install WB v06.
- Install your apps manually. I installed them using Titanium Backup, no data restore, just de apps, and got no FCs.
Click to expand...
Click to collapse
how can you not restoring data?
like in titanium, for the batch mode
all of them are 'restoring missing apps with DATA'
Hi
probably I solved this FC.
change this line in build.prop and reboot phone
dalvik.vm.dexopt-data-only=0
-> dalvik.vm.dexopt-data-only=1
When I installed Miren Browser,get many FC.
I changed it and get no FC
but I cant test your situation, so please test yourself.
I hope youe FC is solved.
tsuyo.kou said:
Hi
probably I solved this FC.
change this line in build.prop and reboot phone
dalvik.vm.dexopt-data-only=0
-> dalvik.vm.dexopt-data-only=1
When I installed Miren Browser,get many FC.
I changed it and get no FC
but I cant test your situation, so please test yourself.
I hope youe FC is solved.
Click to expand...
Click to collapse
Testing this now.. i just need to reflash cm v6
This change made us no FCs in v06
Sent from my SO-01B using XDA App
jyth said:
how can you not restoring data?
like in titanium, for the batch mode
all of them are 'restoring missing apps with DATA'
Click to expand...
Click to collapse
Yea you can. Under the batch command just select restore and on the next window you have the option to restore app+data, app only or data only.
Just that 1 line can change the fate of my X10? Cool..
Sent from my X10i using XDA Premium App
Wolfbreaks V06 update problems???
I did the V06 update tonight and i had abunch of force closes and now my phone is locked on the sony ericsson logo screen when i tried a reboot to enter Xrecovery but Xrecovery isn't working. Nor does the sony update service work to repair/ reflash the stock 2.1. does anyone know what i need to do or is the ****ed? I've never had any problems flashing custom roms till now. I don't know what i did wrong.
How is it not letting you update from SEUS? It just doesn't detect it or what? If so restart your computer and try it again.
Sent from my X10i using XDA Premium App
Slnkmt is right. SEUS should be able to reflash your phone to stock 2.1. Although i would suggest removing battery and reinserting. I had to do that when i broke my phone to make sure SEUS can detect it..
Sent from my X10i using XDA Premium App
I've installed KennethPenn's ROM for 2.3.4 and loving it, however whenever I try to change my camera to front facing mode, it fails and causes the camera to FC.
Is anyone else seeing this issue or is it possible that I simply have a defective/corrupted com.camera module?
TIA for any advice/solutions.
im runnings kens rom, faux kernal, and front facing camera works fine...have your tried using QIK and see if it fc's?
I hate to say, but it works fine for me also.
No issues with mine either....did you freeze anything?
Sent from my MB860 using Tapatalk
OK...thanks. I'm reflashing the ROM now. I hadn't seen others complain about it, so I figured it was likely just me.
Love 2.3.4!
Hmmm....after fresh flash, I still can't get the front facing camera to work. Fails and FC. I'll have to look into after I restore things.
I just verified that my front facing camera has no issues on KP's 2.3.4 beta 3.
Just tested. Working fine for me on beta 4.5
Sent from my MB860 using XDA Premium App
OK...so apparently I have a corrupted file for my camera app or a hardware issue. Any thoughts on how to repair/replace?
Error: The application Camera (process com.motorola.Camera) has stopped unexpectedly. Please try again.
The regular camera seems to be working fine, otherwise. Just freezes when I go to front cam (same thing happens in QIK), then I get the error.
Used KennethPenn's Rom .... going back to 1.83 safe?
Maybe you missed something. Here are the instructions I followed on 3 occasions now to flash 2.3.4 beta 3:
reboot into CWM
do a complete wipe( this order, DALVIK, CACHE, factory)
install beta 3
do another complete wipe
install the root zip
reboot and quickly press up to start in RSD mode
flash the new radio reboot in CWM
wipe cache and dalvik
Maybe following this procedure will help you.
<edit> If you follow this, and get reboots when installing apps from the Market, what worked for me was boot into CWM, wipe Dalvik, cache, and factory reset, install root.zip again, then wipe Dalvik, cache, and factory reset again, then reboot. Should fix that issue.
I'll give it a try.
I think when I restored from Ti b/u, it just rewrote the fault. I'll uncheck the camera app for the next restore
What do you mean by install beta 3 do wipe then install root.zip ???? I only have beta 4.5.
carlharsch said:
I'll give it a try.
I think when I restored from Ti b/u, it just rewrote the fault. I'll uncheck the camera app for the next restore
What do you mean by install beta 3 do wipe then install root.zip ???? I only have beta 4.5.
Click to expand...
Click to collapse
you shouldn't restore ANY of your system apps from TiBu if going between OS versions.
Well...reinstalled with lots of cache wipes, and first thing I did was (after initial motoblur stuff) to try the camera....no dice. Looks as if it's bad.
I think going back to stock and calling Moto for a replacement might be in order
carlharsch said:
OK...so apparently I have a corrupted file for my camera app or a hardware issue. Any thoughts on how to repair/replace?
Error: The application Camera (process com.motorola.Camera) has stopped unexpectedly. Please try again.
The regular camera seems to be working fine, otherwise. Just freezes when I go to front cam (same thing happens in QIK), then I get the error.
Used KennethPenn's Rom .... going back to 1.83 safe?
Click to expand...
Click to collapse
Why dont you just take the data/app com.motorola.Camera
and the system/app/BlurCamera.apk
and system/app/BlurCamera.odex
from one of these peoples working phones, then paste them into their according directories on your phone. Should fix it.
Edit: also, you will probably need system/framework/com.motorola.hardware.frontcamera
dLo GSR said:
you shouldn't restore ANY of your system apps from TiBu if going between OS versions.
Click to expand...
Click to collapse
Agree with above completely! This is what caused me to have FCs with the contact manager. When I used TiBu to restore, I only restored my apps + data, not system apps. Worked like a charm.
Magnetox said:
Why dont you just take the data/app com.motorola.Camera
and the system/app/BlurCamera.apk
and system/app/BlurCamera.odex
from one of these peoples working phones, then paste them into their according directories on your phone. Should fix it.
Edit: also, you will probably need system/framework/com.motorola.hardware.frontcamera
Click to expand...
Click to collapse
I could try that.
Anyone with a working copy of Ken's 2.3.4 want to email me the files?
carlharsch said:
I could try that.
Anyone with a working copy of Ken's 2.3.4 want to email me the files?
Click to expand...
Click to collapse
I would either pm ken or pm one of the people on the first page ( or all of them! Haha ) asking for the specific files. I would but im on bell.
Cheers
Did you search logcat and dmesg? Probably there is some info about what is the problem.
Enviado desde mi MB860 usando Tapatalk
After several more reinstalls, I "believe" I have it working again.
Hello Community,!
I have been using CM since the nighties unitl the early 30's before Kernel got hacked I have stopped using CM around that time and switch back to near stock rom (TSM Resurrection) due to force close on every single applications. Now that CM is official, I hope the problem is gone but it is still there. I can use the phone for couple hours and then force close everywhere.
I have tried the following with that I can find on the forums:
1. Fix Permissions.
2. Fix Permissions and then reflashing CM.
3. Wipe data and reflashing.
4. Went back to stock (with atlas and all that) and then back to CM.
5. Rebooting/pulling battery out does not fix it either.
I read that it would be running out of memory causing it, but closing apps did not help.
Could it be rogue app(s) causing it or something entirely different?
Thank You!
Hyper_Warp said:
Hello Community,!
I have been using CM since the nighties unitl the early 30's before Kernel got hacked I have stopped using CM around that time and switch back to near stock rom (TSM Resurrection) due to force close on every single applications. Now that CM is official, I hope the problem is gone but it is still there. I can use the phone for couple hours and then force close everywhere.
I have tried the following with that I can find on the forums:
1. Fix Permissions.
2. Fix Permissions and then reflashing CM.
3. Wipe data and reflashing.
4. Went back to stock (with atlas and all that) and then back to CM.
5. Rebooting/pulling battery out does not fix it either.
I read that it would be running out of memory causing it, but closing apps did not help.
Could it be rogue app(s) causing it or something entirely different?
Thank You!
Click to expand...
Click to collapse
just went thru this the other night with another member...try going back to dl09 and reformat your sd card. worked for him
I have not tried in addition to reformatting my sd card whild doing the whole DL09 restoring. I will give that a go.
It would probably also be a good idea to redownload the apps fresh from the the market instead restoring them from titanium backup?
Hyper_Warp said:
I have not tried in addition to reformatting my sd card whild doing the whole DL09 restoring. I will give that a go.
It would probably also be a good idea to redownload the apps fresh from the the market instead restoring them from titanium backup?
Click to expand...
Click to collapse
with tibu just make sure to restore app only w/ out data. Should be no different than redownloading the app from market.
Your solution seems to work so far, I did however redownload fresh copies of apps from the market and just restore the data from titanium backup just incase any full restore are corrupted. I do get random phantom keys from time to time.
ty
Hi,
I loaded Cognition 777 rc onto SGS2 i777 from the latest Cognition X2 beta 4 and got trapped in a com.android.phone force close-relaunch-force close loop. So I went back to beta 4, and loaded just the 11132011 kernel. That worked fine, so I tried loading C777 again. Same issue.
I am back on beta 4 with the 11132011 kernel and all's well. I have seen some discussion in other forums about dealing with com.android.phone FC. But I wonder if it is a c777-specific issue because I've not had the problem with previous Cognition revs.
Thoughts? Thank you very much!
Mike
I have that problem, too. I think we had to wipe it beforehand, but yeah, not sure...
Had the same issue when I attempted to flash from Serendipity 8 just to check it out. Problem went away after wiping from CWM then flashing.
tysj said:
Had the same issue when I attempted to flash from Serendipity 8 just to check it out. Problem went away after wiping from CWM then flashing.
Click to expand...
Click to collapse
Thanks to both of you. I wiped from CWM and then flashed - and it did go away. But it came back after I restored my apps and data. Tried restoring from CWM, then wiped again and restored with Titanium. I guess this latest rev conflicts with one my apps for some reason? I don't think I've got anything terribly exotic, but who knows?
I guess my options are: 1) load apps one at a time to isolate the problem child or 2) see if it goes away with the next rev ...
Don't restore all the data. Like, don't restore stuff like the phone application or some system data stuff related the phone. Call history and stuff is alright, but yeah, just go through it rather than just restoring everything.
What are you restoring? User apps are always good. System settings will cause problems. It sounds like you're restoring the call log or phone settings, use another app to backup sms and call log.
You two were right. I'd restored all apps and all data, including system data. That was the problem. It's all good now. Thanks for setting me straight.
I was wondering if anyone else had this problem with the DSC rom. I am on a clean installed patched to .72. I notice that I cannot do a full restore from a backup made using the Dell Backup/Restore app. I also notice that you cannot make a new backup - it crashes with an 'internal error' - whatever that is!
I find the app useful for restoring SMS's and phone settings - especially when setting up a new rom. Any pointers would be appreciated.
I am also finding the battery life on DSC VERY poor - less that 6 hours! I may have to blow the install away and start again! I am pretty careful with these things, so SteakMod reset, clear dalvik, fix perms etc, then as soon as new update.zip applied - reboot and factory reset.
I have had a couple if SOD's too. I also found SPB 3d shell seemed to cause some issues, so now I'm on GO Launcher.
Sent from my Dell Streak running DSC .72
Battery calibration after each update
Does anyone know if this issue is fixed in DSC .73?
Broken Dell Back Up
Broken Dell Back Up here also. Running 0.72.