Database Develop

How do I clear cache?

In the Blue Magic ROM thread, it says to clear cache on every boot, how would I go about doing that?

in Amon-Ra's recovery there as an option to wipe your dalvix cache. Hope it helps

Actually, it does this every boot by itself.

But if you want to clear it yourself, you can get a cache clearing app off the market like Cachecleaner (free) and just use that. And you can also do what Protomanez said

protomanez said:
in Amon-Ra's recovery there as an option to wipe your dalvix cache. Hope it helps
Click to expand...
Click to collapse
regular cache is different than dalvik-cache.
regular cache is stored in /data/data/"app.name.here"
while dalvik-cache is stored in /data/
If you clear the dalvik-cache it will take a while for your phone to boot up because it has to reload the dalvik-cache back to your data directory all over again.

[Q] Back from Cyanogen 6 to Froyo, camera problems

Hi,
First I installed Cyanogen6 to try it. After few days I decide to go back to Froyo again. Now I can't use the camera on froyo. When I try to open it, the screen goes black. How can I reset to the original state and delete everything related to Cyanogen? I made hard reset with no luck. For example, SuperUser APK is still installed after the hard reset... so I suppose Cyanogen stuff are also still on my phone.
someone can help me?
Sorry for my bad english

I made these wipes:
Wipe data/factory reset :: Wipe /data and /cache
Wipe cache : Wipe /cache only
Wipe Dalvik-cache :: Wipe /cache/dalvik-cache , /data/dalvik-cache , /sd-ext/dalvik-cache if present
Wipe SD:ext partition : Wipe the ext partition on your sdcard
Wipe battery stats : Wipe the battery stats in /data
Wipe rotate settings : Wipe the sensor settings in /data

You have to flash a stock image, or if you were smart, NAND restore to before you flashed CM.

I flashed a stock image but I don't have a NAND backup.

Was it a proper stock image, or a repacked one? Might explain the SU app.

I download and installed the following update.zip:
8d1049f5d550.OTA_Passion_Vodafone_Generic_2.15.151.5_R_FRF91-1.13.1700.1_EPF21B_release_signed.zip
Downloaded from android.clients.google. com / packages/ ota
Is it a stock image or a repacked one? What should I flash?

If cyanogen6 write something to /system, Did it get deleted with a wipe? This could be the problem. How can I clean all the storage and revert it to the initial state?

/system isn't touched with a wipe, but it's overwritten when you flash.

I will flash the system.img from FRF91. This should solve my problem.

Indeed it should.

I got the same problem with the camera in cyanogen 6. And now i can't install any Rom because E:Can't open /sdcard/update.zip (bad)

Sounds like a bad download. Download CM7 and compare the checksum. Then try again.

Nexus One Rom/Memory Issues

Hey guys, I have a memory issue with my Nexus One when it comes to available storage space. The rom available memory seems to get lower and lower everytime I flash a rom than the previous time. When I load roms like CM6 or Kang-o-Rang or MicroMod Supercircle 2.7 or any others I have 4-16 MB available and nothing has installed yet. I usually use A2SD EXT3 for these but now its extremely difficult to do anything when booting with so little space to begin with. A week ago, on most roms I have well around 150 MB free before installing anything. What may have caused this issue? I even tried booting CM6 with a different SD card not partitioned for A2SD and wiping everything and same result and now I really can't install anything. So is my phone faulty or is there something I can do? I am currently running recovery Amon RA 1.7.0.1 and issues seemed to have come up since using this recovery. I was using Clockwork Mod latest one before this a few days ago.
Any ideas?

Have you been wiping data + cache each time you flash?

Make sure you're calculating data space and not system space (which can be as low as it gets to be, it doesn't matter).

codesplice said:
Have you been wiping data + cache each time you flash?
Click to expand...
Click to collapse
I have wiped, cleared cache, delvik many many times. I suspect that the wipe is not working properly. I have tried two different recoveries and nothing works. My available space now running on Nexus FRF91 stock with root only I have 53.64 MB free. I have installed no third party apps yet whatsoever. I have not even logged in to google yet because it will download all my apps again. I have rebooted as well. I think theres an issue with my device and memory. Should I call HTC or my warranty is void?

Sounds like a weird problem, I would've tried to wipe a time or two more. I just wiped my device after flashing nightlies for the last two months without wiping and I noticed I had 170MB free when I booted up with a few apps installed.

I agree with SBS_. It sounds like the wipe isn't doing the job properly. Try to do it in all the possible ways (wiping through the ROM - using "Factory Reset" option, wiping through recovery - clearing data, cache and Dalvik-cache, and wiping through ADB command line), see if it changes anything.

Jack_R1 said:
I agree with SBS_. It sounds like the wipe isn't doing the job properly. Try to do it in all the possible ways (wiping through the ROM - using "Factory Reset" option, wiping through recovery - clearing data, cache and Dalvik-cache, and wiping through ADB command line), see if it changes anything.
Click to expand...
Click to collapse
I've tried everything except ADB command line. I will have to read into doing that as I am unsure what to do. I have wiped from recovery and through the rom at least 15 times each! lol

When you load a new ROM, did you try to use Root Explorer to see what's on your DATA partition? (under directory /data).

Jack_R1 said:
When you load a new ROM, did you try to use Root Explorer to see what's on your DATA partition? (under directory /data).
Click to expand...
Click to collapse
Great idea. Actually I have but not sure what suspicious files I should be looking to delete. I do own root explorer so any suggestions would be great. Thanks!

timahawk said:
Great idea. Actually I have but not sure what suspicious files I should be looking to delete. I do own root explorer so any suggestions would be great. Thanks!
Click to expand...
Click to collapse
I have this exact issue. I know how to wipe. I have gone as far as reloading HBoot and placing the stock EPF30 image. I have gone thru using clockwork and Amon. I know how to do factory resets. I know how to go to storage options with clockwork and format all partition options. I have spent months on this. Below is a readout, after blowing away everything.
~ # du -hc /data
du -hc /data
2.0K /data/lost+found
4.0K /data
4.0K total
~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 192.9M 0 192.9M 0% /dev
/dev/block/mtdblock5 196.3M 109.5M 86.8M 56% /data
~ #
Another user that I have been working with has the exact issues as the user here and me. He contacted HTC. They are replacing his N1. There is something weird going on with some of these units. Just like a few months back, no one knew anything about the bad boot blocks issue causing many developers to change their ROM installs to accommodate those users with this issue. This low space on /data issue is another one that sooner or later will start to show up more and more, IMHO. For instance, at best using either Evils Sense Roms or MicroMods Hybrid sense Roms, I have 23MB free on initial install. This is after basically wiping formatting, resettings factory Data etc etc. At best, lets say using Enoms latest AOSP, I have maybe 75Mb free Internal memory, after initial install and NO applications downloaded installed on my part.
I really wish that folks here and on other threads would start to take this issue a little more seriously than basically saying a user isn't properly wiping his setup prior to an install. I have my beloved N1 since third week of January this year. Never had a problem with rooting, installing any of the original CM, or Paul M stuff from the early days here and on their Kitchen setups. Something has basically changed to cause these issues on a number of Nexus one setups. I have root explorer too and no manner of deleteing, via changing partition permissions from RO to RW makes any difference after wiping, formatting whatever prior to a fresh clean install of any current ROM.

I have approximately the same issue. I can't install anything..
Even after a full wipe of /data and all caches, I installed latest nightly-219-passion and the only possible way to install apps is by manually typing the adb push commands in commandline. It DOES NOT WORK using Market, File Manager, Titaniumbackup, ....
When I nandroid restore I have all my apps back but still CANNOT install any new apps using Market, File Manager, Titaniumbackup, ....
I already tried the fix_permissions script in both Amon_RA and RomManager but without success. I have system:system permissions on /data.
Is there a way to wipe /system aswell prior to an install, or does that happen when you flash a .zip?

Saphroxx said:
I have approximately the same issue. I can't install anything..
Even after a full wipe of /data and all caches, I installed latest nightly-219-passion and the only possible way to install apps is by manually typing the adb push commands in commandline. It DOES NOT WORK using Market, File Manager, Titaniumbackup, ....
When I nandroid restore I have all my apps back but still CANNOT install any new apps using Market, File Manager, Titaniumbackup, ....
I already tried the fix_permissions script in both Amon_RA and RomManager but without success. I have system:system permissions on /data.
Is there a way to wipe /system aswell prior to an install, or does that happen when you flash a .zip?
Click to expand...
Click to collapse
How did you install the nightly. Even with my issues of 109Mb used up on data before I install anything, I have the latest nightly running along with latest Gapps and approx 50 of my own apps, with 79Mb free internal. I used clockwork recovery, then under storage options, you can run format options, on boot, system, data, cache, and SD-EXT and then under advanced, wipe dalvik-cache. I also added the data factory reset option also. I then clean installed the nightly. Then after an initial setup to just have it running, flashed the gapps. I did initially have approx 75Mb free Internal before the Gapps install. Then I went down to 53MB after gapps. I verified I had the correct settings in settings:Cyanogen Mod for the file system. I then flashed the latest Dark Tremor script, ran the commands for a2sd check, a2sd reinstall, a2sd zipalign and a2sd cachesd to move the dalvik-cache to sd. I have an EXT3 setup on my SD card. After moving Dalvik cache I jumped from 28Mb free to 79Mb free where it's pretty much staying now. Not as much as others that don't have the issues on /Data but at least useable.

Reduce /cache partition under CM7

Just a quick question:
What happens to system-dalvik-cache under /cache, if I resize this partition to e.g. 5 MB?
I've read somewhere that CM7 moves it to /data. true? Are there any other disadvantages of such a small cache-partition?
many thanks!

Someone?
10chars

Yes, on CM7, if the cache partition is too small, it will move it to the /data partition. I think it is /data/local/cache

Dalvik-cache never resides on /cache anyway. /cache is for Market and OS OTA downloads. If you make it too small - your Market downloads might fail.

I didn't even realize he was talking about dalvik cache. The dalvik cache resides on the /data partition by default for both system and data apps.
As Jack_R1 said, the cache is only used for temporary files, like OS upgrades and market downloads. If the cache partition gets below a certain point (I think it is 5MB), CM7 will automatically change the cache directory to the /data partition.

On my device the market download folder has already a symlink to my /data partition. Other then my system dalvik. At least it seems so.
Thanks for your help. So i can go ahead and resize with blackrose

Formating /system

Just wanted to know what happens when you format /system and /preload partitions.
Suppose you format /system from recovery. Can you boot into you ROM after that? Or is that where the ROM was?

dark_polok said:
Just wanted to know what happens when you format /system and /preload partitions.
Suppose you format /system from recovery. Can you boot into you ROM after that? Or is that where the ROM was?
Click to expand...
Click to collapse
If you format /system in recovery you blow away the ROM, definitely cannot boot after that. If you format /data as well, the only way you'll be able to recover is with an ADB sideload.

you_eeeeeediot said:
If you format /system in recovery you blow away the ROM, definitely cannot boot after that. If you format /data as well, the only way you'll be able to recover is with an ADB sideload.
Click to expand...
Click to collapse
Thanks.
What if I format /system + /data + cache and dalvik chache and then flash a custom rom right after that, without rebooting the phone in any way [meaning not rebooting into system or bootloader or recovery] that should be ok right? Coz I came from a S3 and that combination worked perfectly for it.
Also still have no idea what the /preload partition and formatting it does.

That's what I do when I update within a rom.
Wipe system, cache, dalvik. Flash rom, then wipe cache/dalvik again.
Just a habit after all the different recommendations from previous devs in the past.

dark_polok said:
Thanks.
What if I format /system + /data + cache and dalvik chache and then flash a custom rom right after that, without rebooting the phone in any way [meaning not rebooting into system or bootloader or recovery] that should be ok right? Coz I came from a S3 and that combination worked perfectly for it.
Also still have no idea what the /preload partition and formatting it does.
Click to expand...
Click to collapse
Yes you can wipe /system, /data and /cache and you're good to flash a ROM, no need to reboot back into recovery again. Dalvik-cache is located on /data, so no need to wipe dalvik when you're wiping data, it's redundant. There is no need to worry about wiping or formatting /preload in almost all situations, otherwise the ROM devs would be telling us to do it. Back in my Galaxy s3 days I remember some ROMs would wipe and flash /preload but I don't think it's a big deal on the One. If it needs to be done, the ROM installation script will handle it.
Most ROM installation scripts wipe /system so it usually isn't necessary to do it yourself. However I do it anyway just to insure a completely clean installation in case the dev's script is messed up (it does happen). Wiping /data is optional of course but it is recommended when changing the base version (for example, 4.1.2 to 4.2.2) or if you're anal like me you can wipe data when upgrading between HTC base versions (2.17 to 2.24 for instance). Some people don't ever wipe /data and don't have any problems, but I can guarantee many of the weird odd-ball issues on this forum could have been prevented with a full wipe.

erikikaz said:
That's what I do when I update within a rom.
Wipe system, cache, dalvik. Flash rom, then wipe cache/dalvik again.
Just a habit after all the different recommendations from previous devs in the past.
Click to expand...
Click to collapse
henrybravo said:
Yes you can wipe /system, /data and /cache and you're good to flash a ROM, no need to reboot back into recovery again. Dalvik-cache is located on /data, so no need to wipe dalvik when you're wiping data, it's redundant. There is no need to worry about wiping or formatting /preload in almost all situations, otherwise the ROM devs would be telling us to do it. Back in my Galaxy s3 days I remember some ROMs would wipe and flash /preload but I don't think it's a big deal on the One. If it needs to be done, the ROM installation script will handle it.
Most ROM installation scripts wipe /system so it usually isn't necessary to do it yourself. However I do it anyway just to insure a completely clean installation in case the dev's script is messed up (it does happen). Wiping /data is optional of course but it is recommended when changing the base version (for example, 4.1.2 to 4.2.2) or if you're anal like me you can wipe data when upgrading between HTC base versions (2.17 to 2.24 for instance). Some people don't ever wipe /data and don't have any problems, but I can guarantee many of the weird odd-ball issues on this forum could have been prevented with a full wipe.
Click to expand...
Click to collapse
Very helpful replies guys. Thanks =}