i came from sc 2.92, odined back to stock, and OTA to froyo. wiped data, dalvik, and cache. the first go at it gave me FC whilst trying to use my dialer, and a few other issues.
Then i realized that i hadnt disabled voodoo lagfix.
after doing such, i ODIN back to stock, then did the double jump OTA to ea28, then ed01. wipded data, dalvik, and cache. ODIN cwm 3x, then flashed the community rom. this morning, NO dialer problems or stupid FC.
Point being, if you flashed the community rom, and got FC on your dialer, this may be a fix.
bruno is a happy camper now.
There is now a patch that I believe addresses this and some other issues.
Related
i have eb01 on my phone with super clean rom 2.3. ive tried all the other eb01 roms and they keep randomly turning off when the phone is fully charged but wont shut off when its hooked to the charger.. i dont know..any help
I haven't noticed this on Superclean 2.0 or 2.2. And please post questions in general. This is not development related. The devs do, in fact, check general.
Have you tried stock EB01? Try flashing the Odin EB01 file and do a complete wipe
I had the same problem also. I could never get it to come back on either unless I pulled the battery.
Tried clearing your dalvik cache and flashing a theme overtop and it should fix the issue.
I was instructed to do the same and its been working fine for a couple days now.
I too had the same issues. Both on DL30 and EB01. I was using Superclean with the midnight theme flashed. Being very frustrated, I updated to the newest Superclean NV and switched themes. I noticed last night Midnight was updated, flashed it and still no problems. I didn't wipe or clear the dalvik cache.
Maybe a problem with your theme?
Send from my FASCINATING Froyo'd DROID
Mine did the same thing when I updated to the 2.3 but when I went to the 2.4 it stopped.
Sent from my eb01 super fast fascinate
I've got a Fascinate that I've rooted, flashed Super Clean 2.5 EB01 with voodoo. It was working fine until I upgraded CWM. I finally got all that straightened out and reflashed Super Clean. Now immediately after every call I get the message "The process com.android.phone has stopped unexpectedly" I hit Force close and it's fine until the next call. What's weird is I started with SC 2.6 then flashed 2.5 to try to get rid of it, which it did for about 2 hours, then it started again. What do I need to do?
Sounds like a cache issue. Boot into CWM and wipe both the cache and (from advances menu) dalvik cache, and reboot. It will take quite a bit longer than normal to reboot the first time after doing this, as it takes some time to rebuild the dalvik cache. To avoid FCs and other issues, the caches should be cleared every time you flash a rom or theme.
Posted from my EB01 SuperClean Fascinate with Voodoo
Unable to post in developer section, have been using custom roms since February.
Sorry if this is in the wrong section, merge it and delete this paragraph if you must with http://forum.xda-developers.com/showthread.php?t=911364&page=1278
Had wolfbreaks rom running previous to installing FXP030 and unlocking bootloader, had issues with wolfbreaks rom. FXP030 seemed great and worked well, aside from the odd glitch. Had ran it for 2 days. Tried to update to FXP030b to test out new fixes (use the camcorder often) and upon flashing new kernel FTF file, phone booted, wiped cache, factory reset, wiped batt stats, wiped dalvik cache. loaded up the custom zips, for FXP030b + gapps, booted fine, couldn't get wifi working, couldn't connect with 3g. Tried to crash system server inside bad behavior in the dev tools as per instructions from collosus. upon crashing system service, phone hung hard for over 20 mins stayed on same screen, did not boot again till i flashed stock kernel. Not even FXP030 worked at that point. Hope I was not close to bricking my device.
quanium said:
Unable to post in developer section, have been using custom roms since February.
Sorry if this is in the wrong section, merge it and delete this paragraph if you must with http://forum.xda-developers.com/showthread.php?t=911364&page=1278
Had wolfbreaks rom running previous to installing FXP030 and unlocking bootloader, had issues with wolfbreaks rom. FXP030 seemed great and worked well, aside from the odd glitch. Had ran it for 2 days. Tried to update to FXP030b to test out new fixes (use the camcorder often) and upon flashing new kernel FTF file, phone booted, wiped cache, factory reset, wiped batt stats, wiped dalvik cache. loaded up the custom zips, for FXP030b + gapps, booted fine, couldn't get wifi working, couldn't connect with 3g. Tried to crash system server inside bad behavior in the dev tools as per instructions from collosus. upon crashing system service, phone hung hard for over 20 mins stayed on same screen, did not boot again till i flashed stock kernel. Not even FXP030 worked at that point. Hope I was not close to bricking my device.
Click to expand...
Click to collapse
Hi Buddy,
What you should have done when your phone froze after crashing the system server is to have taken your battery out and then just re-booted your phone, all would have been good.
If you are still at the same stage now from when you posted just flash the fxp kernel in the flashtool provided by J, your phone will now boot with FXP030b.
You was never close to bricking your phone so do not worry.
I cant post in the development forum so hopefully someone herw sees this and can help me. Background info: Got S4 a couple weeks ago and gor the OTA update on my way home and wasnt even thinking and updated to mja. Looked into rooting at that time and seemed there were alot of issues with it so I waited. Finally found a root and rom method to work. Then I got the mk2 ota. Waited till I saw it was no problem and installed stock (ish) v01. Ran it with no issues. V02 came out so i downloaded it and sacs to try sacs out. Installed his and had a few issues so I completely wiped everything. All cache and dalvik and everything philz recovery could wipe. Now on v02 of stockish and programs are stopping out of nowhere. Not force closing just unexpected stops. I start back up and they will run. Also getting invalid signatures from play store when I tey to download some apps. After trying 2-3 times it will finally install. So doea anyone have a fix or solutiom tk these 2 issues?
Sent from my SPH-L720 using Tapatalk
heltonlevi85 said:
I cant post in the development forum so hopefully someone herw sees this and can help me. Background info: Got S4 a couple weeks ago and gor the OTA update on my way home and wasnt even thinking and updated to mja. Looked into rooting at that time and seemed there were alot of issues with it so I waited. Finally found a root and rom method to work. Then I got the mk2 ota. Waited till I saw it was no problem and installed stock (ish) v01. Ran it with no issues. V02 came out so i downloaded it and sacs to try sacs out. Installed his and had a few issues so I completely wiped everything. All cache and dalvik and everything philz recovery could wipe. Now on v02 of stockish and programs are stopping out of nowhere. Not force closing just unexpected stops. I start back up and they will run. Also getting invalid signatures from play store when I tey to download some apps. After trying 2-3 times it will finally install. So doea anyone have a fix or solutiom tk these 2 issues?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
A couple things that seemed to help when using Philz...
Don't just wipe, manually format system,cache under the advanced option...
after you do all the wiping and formatting under power options reboot recovery, Philz likes the reboot before flashing
Ive had a couple flashing issues like you were describing with different roms and philz but since I started using this approach they seem to flash much better.
I manually formatted system/cache/data under mounts and storage and reboot after clean wipe but I got a response from creator he said to wipe cache and dalvik again and see if things run smooth
Sent from my SPH-L720 using Tapatalk
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
EtherBoo said:
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
Click to expand...
Click to collapse
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
xxxrichievxxx said:
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
Click to expand...
Click to collapse
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
EtherBoo said:
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
Click to expand...
Click to collapse
Yeah it can be such a pain, I flashed nightlies when they sounded like they fixed an important issue (it'd be every other day) and I flashed clean all the time. Now im just going to stick to CM11 M4 until the next milestone.
try changin network type to GLOBAL.