Database Develop

Total cleanup?

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.

Interesting Problem

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

Is this a problem for others? Or am I doing something wrong?

I've tried an assortment of different costume firmware options. CM from bacon, up to the most recent. King's nexus2desire, etc. I've followed the directions as far as I know completely... But this always seems to happen, with either of the two roms.
I'll get some sort of random bug, and it causes a total freeze to where I have to pull the battery to restart it.. But then once I do that, the phone fails to reboot, in which I have to restore the firmware (factory data wipe + delete dav don't help).
It could be working fine for a couple of days, then all of a sudden this happens and screws everything up? Is this to be expected early on since it's development, or is there something wrong on my end?

wrong section, but yea, never happeend to me before.

I wasn't sure if should ask here, since it's based on the development roms here.
When I flash, I always do complete wipe (Factory, Dav, SD:ext, Batt, rotation), then reboot. I never wipe after flashing new rom. I'm using the newest radio, but have had these issues with all the previous radios too. Could there be a hardware malfunction possibly adding to this?

CDRacingZX6R said:
I wasn't sure if should ask here, since it's based on the development roms here.
When I flash, I always do complete wipe (Factory, Dav, SD:ext, Batt, rotation), then reboot. I never wipe after flashing new rom. I'm using the newest radio, but have had these issues with all the previous radios too. Could there be a hardware malfunction possibly adding to this?
Click to expand...
Click to collapse
Yeah something similar would happen to me. I said F it and had HTC send me a new one.

I have only had experience with CM 5, so if you install 5.0.4.1 and get this issue WITHOUT modifying the ROM with other mods, then you probably have a hardware fault. Warranty case that is.

Moved as not Android Development.

Constant rebooting

i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.

If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?

I do have a overclocked under volted kernal

sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...

WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !

Does your phone lock up (unresponsive) before rebooting?

Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.

Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.

I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.

Lagging and slowed down UI(everywhere) even after clean flashing

Hi there, Merry Christmas to y'all everywhere( We don't have Christmas here in my country, anyway.
Ok. Here we go:
I wanted to give my Mi A2 to someone else( completely working and smooth like it should be, has AICP Rom for long time), since that person doesn't like totally vanilla ROM, I decided to flash a more feature packed ROM on mi a2(in this case Pixel Experience), I do this, clean flash,following the usual procedure since I'm used to flashing ROM and stuff
after booting up, everything is sluggish and laggy, even in Phone Setup Wizard, started using phone, setup the apps needed, still laggy and sluggish.. Until that person starts complaining that phone is seriously slow, I say "OK, maybe I did something wrong or maybe this ROM has problems that I'm not aware of" I flash another ROM (Lineage OS), I do the previous stuff, still sluggish, just like previous ROM, exactly same scenario, it doesn't even matter if I have installed apps or just flashed phone, still lags.
Frustrated, why A2 became like this? Did it hit number of flashing rom attempts?(LOL, such thing exists? Flashing cant slow down the phone unless that ROM has problems) decided to go back to stock ROM, successfully flahed stock, boot up, still sluggish and laggy.. I don't know wth is going on...
My mind is racing:
"what is happening?"
"The phone was just fine when on AICP, after flashing, what happned?"
"Is it my fault? "
"Should I have just used factory reset instead of flashing ROM?"
Guys, there is something wrong
,will update the post with logcat and recording if needed and I have the time to do it. Feel free to ask questions.
TIA

Encrypted? Maybe encryption has some problems.
Kernel? Tried to flash just another kernel?
And how about frequencies? Are they ok? Phone is getting hot?
It's risky, but the last thing to do is to reflash other partitions too, like vendor or others (if you have them), maybe one of them get corrupted.
Ps: I'm currently on Android 12 DerpFest (Build of 26Nov) and I can tell you that after 2 months of usage my UI is getting really laggy and I'll change ROM soon. Maybe it's because Android 12, but I'm just letting you know.