No, let's start with info on your phone, what you have done step by step.

 

Here is a link for dalvik to sd.
http://forum.xda-developers.com/showpost.php?p=11688173&postcount=65

 

Before trying anything else, as MandaNick said start with what you have already done step by step to get to this point - plus as many phone details as you can like PVT, erase size, hboot, original software version.

The extremely helpful experts on here will need to know this stuff to understand what the problem is and therefore tell you what the solution is.

 

Dude, you need to slow down. Let's start with is your phone up and running?

 

do what is asked please. were here you help you, dont tell us what you "think" we want to hear. do what we ask and well be able to help you quicker.
it my seem frivolous but infact its extremely important we know more about your device as each one is different

and another thing. dont use CWM4. any CWM higher than 2.5.0.7 is not built by the CWM team for desire and nearly all of them have bugs
use 2.5.0.7 or amonRA

however answer the above asap

 

listen, if you get an attitude no one will help you.
were friendly here but weve asked you a question which is important
its a desire forum, we know you have a desire. there are currently 5 different versions of desire with about 6 different hboot versions with s-on and off

boot to hboot and get us the PVT, hboot, original software version.

that is if you want help.........
weve all had broken bootlooping desires here

 

You're attitude isn't helping. The guys on here know their stuff. Drop the attitude and let them help you

 

Rasta' has already asked
Answer the above and progress can be made...

 

Dude, just boot to recovery, volume down and power and tell us what your setup is PLEASE!!!

 

yes thank you,
first off change your recovery to cwm 2.5.0.7 it can be found on the link in my signature
CWM4 has lots of options but trust me stability is most important and there are issues with every build of CWM after 2.5.0.7 as koush didnt build them

secondly what did you use to create your ext3/4 partition. if it was not gparted, get to using gparted (following our guides) and recreate your partition.

PVT is important as if it was pvt4 you could have an erasesize of 40000 which would require amonRA 2.0.1
we dont want to give you bad advice and thats why we needed it

 

Which script for a2sd does oxygen use?

 

you dont need to worry about erase size as you are pvt1

wipe data/factory reset only wipes the device rom of user data and apps and clears sd-ext if there is data there
it will not delete data from the fat32 partition of the device

you will need to do this before flashing a new rom

if youve used gparted to repartition thats good.

reflash the rom once youve wiped it and it should work
confirm the device is working before you flash anything like darktremor or the dalvic to sd

 

Having an a2sd script doesn't mean that your internal memory won't change when you install an app. In addition to the apk there is the app's data and cache, the dalvik cache, and some apps also have a library. Data and cache are always internal, but on a fresh install will generally be small. The lib will also be on internal, and this can be non-existent or quite large (several MB), depending on the app.

And then there's the dalvik cache. With DarkTremor this is in internal by default, but can be moved (the famous "a2sd cachesd" command). With Oxygen it's simply internal, unless you flash an extra patch to move it to SD.

Either of these last 2 points could explain internal storage decreasing when you install apps, and the last one could explain why it seems different from DT (though that could just be installing different apps as well).

Not saying that there isn't something else going on here - there clearly was at the start of the thread - and the advice you've been given is good. But a change in internal space, even of a few MB, after installing an app, need not automatically mean that something is not working, especially if the apk is appearing on the ext partition.

Edit: Sorry, too slow - while I was typing this you've made clear you know at least the dalvik bit!

 

OK, I'm not going to install what I guess is a paid app to check this, but there are two things to check:

* that the apk itself is in /sd-ext/app

* the app will also have a folder in /data/data. How big is that? And how much space is it using in /data/dalvik-cache?

If the answer to the first one is "yes", and the second add to 12MB, then you have your answer, and things are actually working correctly.

In this case, you can move the dalvik-cache to ext. As for the stuff in /data/data/<app directory>, if you move the app to fat32 with a GB ROM the lib part of that moves, but while that's space efficient it's not pretty to have bits of the app in 3 locations (internal, sd-ext and fat32).

 

Astro can't browse that, but ES File Explorer can. Unfortunately the market won't let me install asphalt 5 free with my current ROM (guess it knows I'm using 2.3.5), so I can't check myself. But if that is your ext partition then you have both apk and dalvik there, so the a2sd script is working.

But if this game has a shared object library then that will still be internal, and sometimes they can be large (Google Earth has 16.6MB there, twice the size of the apk).