Related
I've been flashing various ROMs, but continuously am running into force close/waits, lag, apps shutting down, but only random reboots on one of the ROM's and it got fixed. I get fc/w's on android.process.acore, calendar storage, alarm clock, you name it, I've probably had it error out on me.
I'm wondering how I can clean up my phone entirely.
I don't know what a ROM writes, or doesn't, but I think I've got something in there that escapes a wipe and a flash that seems to be interfering with the system.
I'm not the only one in the Cyanogen's Experimental thread, nor the lastest stable thread that has had this issue. I haven't been keeping up on the other ROM threads, so I can't say if anyone has had these issues with other ROMs or not.
The Mod on Cyanogen's thread has recently threatened bans for non-ROM -related posts, and to be honest, I don't think this is the ROM because it happens to few, but not all. I'ts not a ROM related question, since it shouldn't matter what ROM I'm using, if I'm rooted, I just want to clean off my phone entirely.
I'm also wondering f these issues could be hardware related, perhaps a different manufacturer of a chip or something.
So, how do I really scrub the thing?
From what I understand, going back to a stock, unrooted phone and going through the rerooting process should "unclutter" things.
I followed this how to
http://forum.xda-developers.com/showthread.php?t=491350
I think I solved my issue
Going back to an unrooted phone doesn't deal with anything on the apps2sd partition that might be messing things up if I go back to it.
I ended up deleting the ext4 partition on my card and recreating it. The last time I cleaned up, which didn't do the trick, I just deleted everything I saw. I don't know if there was something left in lost&found or something hidden, but that's what I did.
I also flashed from RC29 instead of JF1.5.1. The first time I thought it would be easier to flash to a ROM I had on my PC that already had Terminal Emulator and Telnet already on it than to download the two apps. I don't think anything would get left in place from that, and I think people have had success with flashing CM's from JF, so I doubt it was that, but who knows. I did both just to be sure.
I also didn't enable any swapping, but i can't imagine that swapping would create acore force closes. ???
So, flashing from RC29 and starting from a freshly created ext4 did it for me.
Looked at the sticky, but did not see this issue. It was happening on my cyan builds once I went to donut. I swapped, updated all, wipe, install per instructions, but the prob found me again. This time I am not the official 1.6(DRC83, 2.22.19.26I) Anyone else have this happen to them?
Fixes?
Okay, so the time ranges between 30 seconds and a minute.
From what I am seeing, I may have to revert back to stock settings and give it a go. If that works, then I will attempt to ROOT again.
I only began having this issue after I upgraded to 1.6 via cyanogen.
I swapped ROMs hoping to solve the issue ( thought it may have been b/c of the experimental/beta version)
But after being on this build for one day, I am already experiencing the issue again. I even went as far as repartitioning and wiping before I started so it would be a clean slate.
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
derfolo said:
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
Click to expand...
Click to collapse
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
ljnick19 said:
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
Click to expand...
Click to collapse
The HTC recovery may have messed your radio up. Try reflashing the radio.
Thanks for the input! I was worried no would have any ideas. I'll give that a shot. Now when reflashing the radio, do I need to do the whole-radio, spl, rom, wipe thing? Or just radio?
I am also using Ra v1.2.2 recovery, could that be causing issues w/ 1.6, Donut ROMs?
One more issue to add: AdvancedLauncher (processandroid.process.acore) has stopped unexpectedly. FC almost every time i press the home button. Made the mistake of making advanced launcher my default home button action...
For the launcher make sure you have the latest version. Then reinstall or run fix permissions. U only have to flash the radio, and the recovery should only affect flashing the roms
Thanks a mill for the help, I really thought this was going to fall flat. I'll attempt later this afternoon and post results.
For those of you that took a moment to not only read, but to assist, THANK YOU!
Results are:
I went from OTA 1.6 to Cyan 4.1.999
I wiped and repartitioned the sd as well as redoing the radio
So far, I have not experienced any FC's. Unfortunately, I have not made a lot of calls either. Crazy thing was that on the OTA build today, calls seemed to be functioning, but the FC's were excessive.
I also ran fix permissions as well as cleared the dalvik cache.
Again, thanks for the support. I hope to pass it on if I am ever able to help, it is appreciated!
LJ
I'm fairly new to working with Linux and the Android OS, though I have pretty broad knowledge in most other systems. Hopefully someone here's willing to help me
First, a little background. From straight out of the box, I ran The Unlockr's steps to root and flash my phone. The root instructions I followed are located here.
I am running radio verison 2.22.19.26I
And using SPL version 1.33.2005
My SD card is partioned in a Fat32/EX2/Linuxswap configuration
And I'm using Dwang's Android 1.6 Donut rom. (Located Here!)
The problem:
During Black Friday, I found amazing deals on Micro SD cards. I'm moving from a 2GB to a 4GB. I copied everything over on the fat 32 partition from one to the other, but forgot about the other partitions When I switched SD cards, all of my apps and widgets crashed and whatnot. The problem is when I swapped back to the original card...they were still crashing.
I've tried a bunch of things, Nandroid restores, reflashing the ROM and starting fresh, and I'm still having problems with crashing apps. The interesting thing, is that only apps that were downloaded from the market, and use the internet refuse to work now. Here's a list of working VS non working apps.
Working apps:
App Manager
Melon (Notetaking program)
Any application that came "Stock" on the phone. (Youtube, Messaging, Browser)
Non-Working Apps:
Wikidroid
Autolock
Toggle Settings
Hi AIM
Almost anything downloaded from the market.
Other than that the phone runs fine. Texts, calls, uses the internet browser without a hiccup. It's just download apps either spam force close, or can't connect to the internet. (which the browser can)
I was wondering if anyone knew what causes a problem like this, or where I could be pointed in the direction of someone with a similar problem. I've google'd all morning and searched through the forums, but can't find anything. I'd try more things, but i have bricked a G1 in the past and am pretty damn terrified to mess with things too much.
Thanks in advance for any advice or help.
Just start from scratch.
1) Repartition the new card.
2) Wipe
3) flash
Problem solved.
Reformat the card, wipe the data in the recovery mode, and reflash the rom (Dwang's in my case?) I think I've done this which is what's causing my apps to act all funky anyway. I will try it one more time though. There's no risk in a brick doing this, no? Since I'm using the same rom that worked before?
Again terrified. If a brick shows up, I don't get a third chance
Plus I'm a mobile/program developer. I'd kinda like to know what causes this, or where I can find some resources so I can prevent it frmo happening in the future on stuff that I write.
[email protected] said:
Reformat the card, wipe the data in the recovery mode, and reflash the rom (Dwang's in my case?) I think I've done this which is what's causing my apps to act all funky anyway. I will try it one more time though. There's no risk in a brick doing this, no? Since I'm using the same rom that worked before?
Again terrified. If a brick shows up, I don't get a third chance
Plus I'm a mobile/program developer. I'd kinda like to know what causes this, or where I can find some resources so I can prevent it frmo happening in the future on stuff that I write.
Click to expand...
Click to collapse
Okay, for clarification, the only way you can brick is through flashing a radio image or SPL without the requirments for either. In other words, wiping and flashing ROMs physically can't brick your phone. Stop worrying
I'm honestly not sure what happened to your partition, so I can't tell you what caused it, but honestly, reformatting the card, wipe and reflash will solve your problem, as everything is clean. If the problem persists then something has been left behind.
flashing the roms and repartition the card should fix it. its most likely caused by corrupted permissions or something to the likes. The sdcard should not be removed while the rom is on or replaced with an unidentical ext partition. Some apps that are supposed to be in the card arent there, which will cause failures. since its a hacky method for getting apps on the sd, there is no fail-safes in place
I've been tinkering with this phone for probably around a year now. I have a good understanding of flashing and whatnot, but that is probably the extent of it. I've had tons and tons of roms on this phone, and never once been given trouble.
Recently, I flashed to King's Eris2G1 rom, and that seemed to start my problems. I had lots of problems getting this ROM to work properly. Eventually, I got a working load, but I noticed that Apps2SD stopped working. Everything else seemed to work OK so I ignored it and used the rom.
Now, this morning, I went to flash his Legend2G1 rom, and got an error during verification that files were corrupt. Redownloaded and tried to reflash, same thing. So I said screw it, tried going back to an older 1.5 senses rom (I forget which, MLING or something like that), and I got errors on verification for that too. I never had any trouble previously installing that rom. So, I tried Eris2G1 again, and got the same errors there. Last time, it always flashed fine, just worked a little buggy.
So I tried Kings AOSP2.1. That worked. It flashed fine, booted fine, but I did notice, Apps2SD isn't working here either. So, my thoughts are all the Senses roms failed because they are larger and install files to the SD card, where as this smaller rom does not?
I went to test my theory by popping in a different SD card, but I got the exact same errors. So, it's not the card, it's the phone, but it appears to be related to the card. I am able to access the FAT32 partition without problems. I tried repartitioning the card many times (96-128MB swap, 128-512MB ext2) and I tried with ext2, 3, and 4. No luck no matter what.
So, does anyone have any ideas as to 1.) what happened and 2.) how can I fix it? I am not 100% sure what all I have on my phone as far as SPL, recovery, ect go. On recovery, it says "Build: RA-dream-v1.5.2". No idea what SPL I am using... I flashed it a little bit ago to whatever a particular rom I was interested in required. All I know is I never had a single problem like this, and now even the roms that used to work like a champ are not functioning. I've got my phone to a usable state with this current ROM, but i'd really like to play around with the Senses roms more (nevermind the fact that I want A2SD back). Can anyone help?
EDIT: For ****s I just tried flashing 1.6.2 recovery, as well as reflashing radio and SPL. Didn't make a difference.
This phone is driving me crazy. I haven't seen this issue reported by anyone else before, so I'll try to sum it up:
I have a Galaxy Mini, with CM 7.1 RC1 installed, which I can no longer update or replace its ROM, no matter what ROM I install(I've already tried CM7.2, Andro-ID and every other ROM that I could get my paws on, it's hopeless; CM9 also seems to work, but it's so buggy, it's unusable), the microphone won't work anymore, even after clearing everything and fixing the permissions, I have to revert to CM 7.1., which is the only release which has a halfway working microphone implementation(it's buggy, to say the least, people just barely hear what I'm saying). There is a patch for libaudio which suposedly fixes the mic, but after installing it, ceases working, so I always have to revert to my CM7.1 Nandroid backup. I would install the vanilla Gingerbread again, because everything was working fine on that, but there is one small issue...the data cable broke not too long ago, so I'm stuck with only a MicroSD card reader, which is not of much help, because I can't flash it with Odin and, as this will be sold next week(the buyer asked me to reflash it with the original firmware), I'm not willing to buy a new one for it either.
My biggest mistake was that I forgot backup the original firmware, which might have been the simplest solution for this problem, so I'd be very grateful if someone could kindly dump and upload his/hers stock ROM backup from cwm, so I can try to restore it and finally get the mic working again. Also, if you know any other solution that might fit in this scenario, I'm willing to try anything.
mihait39 said:
This phone is driving me crazy. I haven't seen this issue reported by anyone else before, so I'll try to sum it up:
I have a Galaxy Mini, with CM 7.1 RC1 installed, which I can no longer update or replace its ROM, no matter what ROM I install(I've already tried CM7.2, Andro-ID and every other ROM that I could get my paws on, it's hopeless; CM9 also seems to work, but it's so buggy, it's unusable), the microphone won't work anymore, even after clearing everything and fixing the permissions, I have to revert to CM 7.1., which is the only release which has a halfway working microphone implementation(it's buggy, to say the least, people just barely hear what I'm saying). There is a patch for libaudio which suposedly fixes the mic, but after installing it, ceases working, so I always have to revert to my CM7.1 Nandroid backup. I would install the vanilla Gingerbread again, because everything was working fine on that, but there is one small issue...the data cable broke not too long ago, so I'm stuck with only a MicroSD card reader, which is not of much help, because I can't flash it with Odin and, as this will be sold next week(the buyer asked me to reflash it with the original firmware), I'm not willing to buy a new one for it either.
My biggest mistake was that I forgot backup the original firmware, which might have been the simplest solution for this problem, so I'd be very grateful if someone could kindly dump and upload his/hers stock ROM backup from cwm, so I can try to restore it and finally get the mic working again. Also, if you know any other solution that might fit in this scenario, I'm willing to try anything.
Click to expand...
Click to collapse
for stock rom is very simple go here http://forum.xda-developers.com/showthread.php?t=1464896 and get this rom flash with CWM and Voila!!! ^^
Hmmm...I wonder why that one isn't in the rom list. Anyway, downloading and reporting back.
well-it sure looks like stock, yet mic is still dead
bump......