Database Develop

How much free memory should I have after running taskiller?

I have task killer set to ignore two applications: Battery Widget and Weather Widget (donation version).
I've rooted my phone and am running Cyanogen 4.0.1 with Ted's hero theme. And I've formatted my SD to have FAT32, EXT3, and Linux Swap partitions and have my apps installed to my SD.
However, when I use taskiller to close all my applications I'm usually left with only 28 to 30 M free. Sometimes I'll only have 26 M or all the way up to 33 M left. Is this normal?
How much memory do you guys have left after you kill your tasks? Are my numbers low enough to make you think I've not partitioned my SD correctly or something else?
I feel like my phone should be much much faster than it was before I rooted it, but I don't see the huge improvements many people seem to.
Any help is appreciated.

yeah, I have questioned this too. I use Advanced Task Manager with 2 apps excluded. I usually am at 41 MB when all are ended. Prior to rooting this was in the 50's. I assume it is because the ROM has used some of this memory?
I also seem to have a lot less internal memory than others. I have 54MB when I go review my memory under settings. Not sure how others are in the 70-80 MB range. I clear cache frequently.
Also have 3 partitions 7.5GB/500MB/32MB
to the OP - have you deleted the cache of programs like browser, google maps?

I'm not sure how. I'd love to delete both of those and a few others (voice dialing I will never use you!!). I've gone into the apps manager but it won't let me uninstall them.
Yes, I'm a complete noob at this .

One thing I may have done wrong. I didn't reflash my cyanogen rom after formatting my SD. Could that be a problem?

Nagh, the rom would do it on the next reboot... go to menu... settings... sd card and phone storage. It should show all memory there (including second partition).
To delete cache, go to menu... settings... applications... app manager.
Click on browser, scroll down and delete cache. How much was there?

There wasn't much. It was like 1 to 1.5 megs, but it's gone now. I also set my gmail sync down to 1 day and cleared out it's data. Still though, my phone just feels like it's not getting the big speed upgrades others talk about.

I am hoping someone else will chime in on the low memory reported by task killer/manager in our cases.
How much internal memory were you showing under settings and removing cache?
You can sort the app manager by size too (of course the apps are on your sd card) but the cache is not.
I take it you confirmed your partitions were working?

They seem to be working. I've got 486 MB for my ext3 partition and only 413 available. I'm assuming 73 MB are being used by my programs.
I have 64 MB of internal phone storage available. I don't know what it was before.
I also have 5 desktops with a lot of icons on each one, plus I have a background that is about twice as wide as normal (1067x480 vs 640x480). Still the background is only 70k.

If you want to delete stock apps
Code:
adb remount
adb shell
cd system/app
ls
This will let you see the actual names of apps. From there you can just rm -r them as usual
example
Code:
rm -r VoiceDialer.apk
rm -r com.amazon.mp3.apk
rm -r VoiceSearch.apk
rm -r LatinIME.apk
Don't forget to clear your dalvik-cache after you done nuking stuff!!!
Code:
rm -r system/sd/dalvik-cache
mkdir system/sd/dalvik-cache
You can do all of this from terminal as well but adb make is much easier.
@ OP. I too have only 28-33MB of free ram after closing most of my widgets but I think it's pretty normal as too much free memory means too much wasted memory. And you will not see HUGE improvements in speed neither... there's only so much developers can do. What Cyan is trying to do is to introduce new features (global search, vpn, exchange) without bogging down the system (and doing a great job at it IMHO).
Good luck

^ that is an awesome post. Thank you for that.

Thanks a ton for that. Very helpful post. If I won't see any speed improvements by uninstalling apps I'll just pass on doing that.
Are there any ways I could see speed improvements beyond what Cyanogen already provides?

Limit the amount of desktops, and limit the use of widgets. Power wideget from donut seemed to use a lot of ram and slow things down a little.

why are you people confusing internal storage with system ram?
The information available under settings/sdcard-phone storage/available space reffers to the space available in the /data partition of your phone. Wether you have 1 or 100 (well, 89) mb free in this partition is irrelevant to your phone's performance. All that gets written to this partition is installed apps (not part of the system), dalvik-cache (for ADP or AOSP based roms that don't have their classes pre-compiled), and user data and settings.
People who have 70-89 mb free in that partition are using a2sd, data2sd, and cache to sd, which, imho, is a flippin waste because the internal nand is a lot faster than the bottlenecked bus for the sd card and it's just going to waste if you're not using it. Nothing, i repeat NOTHING is gained by having a free data partition (much like having free space in system which is never going to be used).
Your system has 192 mb of RAM, which is the actual working memory of the device, of those 192, only 90 are available to the dalvik VM, which is the Android part of your phone. This ram can be checked using "free" (if your build has busybox) at the terminal, and this will tell you how much ram is being used by the system, along with how much swap space (if you're using it) is being used. The used ram space fills up fast, and that's a good thing, because unused RAM is wasted RAM. Linux manages things and drops processes as required (to a swap file if available) to free up ram for processes that require it.
To keep your phone running smootly, I'd recomend a reboot every night (when you put your phone to charge). Android is full of memory leaks that have to be fixed, and until they're worked out, the 90 mb ram you have available is all you have to go with (unless you use swap, but one should never really consider that space memory anyway)

The biggest performance difference I've seen has been to shut down my battery widget. After I did that phone's responsiveness has been great.

Froyo FRF85B issues

So I just installed Froyo FRF85B and well, I have a couple issues. First off, the boot up now seems to take almost 10 minutes, second off, I went into Froyo with 50 megs free, and I came out with 50 megs free as well.
My understanding is Froyo should have freed up more memory for me. Anyone have any ideas?

Who told you Froyo would free up space? It might clear out your cache, but that's about it.

ATnTdude said:
Who told you Froyo would free up space? It might clear out your cache, but that's about it.
Click to expand...
Click to collapse
Eclair didn't have access to the full 512 ram. The people who had installed prerelease Froyo reported more available internal ram. I also have more available running memory as well. Went from 30 megs to 250 megs of available application memory. Which is kind of useless if I can't install that much in programs.

naturefreak85 said:
So I just installed Froyo FRF85B and well, I have a couple issues. First off, the boot up now seems to take almost 10 minutes, second off, I went into Froyo with 50 megs free, and I came out with 50 megs free as well.
My understanding is Froyo should have freed up more memory for me. Anyone have any ideas?
Click to expand...
Click to collapse
1st boot always takes a while

flybyme said:
1st boot always takes a while
Click to expand...
Click to collapse
Any viewpoint on the free memory? And it was the 2nd and 3rd boots that seemed to take forever.

naturefreak85 said:
Eclair didn't have access to the full 512 ram. The people who had installed prerelease Froyo reported more available internal ram. I also have more available running memory as well. Went from 30 megs to 250 megs of available application memory. Which is kind of useless if I can't install that much in programs.
Click to expand...
Click to collapse
get your terms right else you will confuse people. memory can be rom or ram
rom hasnt been changed. available ram has been increased. your rom is whats used for installing applications. ram has no effect on available storage

Problems!
I just got the T-mobile update to FRF85B but I am still having problems playing WAV files from an exchange account. Can someone please test theirs and see if they are able to listen to WAV files? I get the message:
"Sorry, the player does not support this type of audio file."
Btw, it worked fine on Android 2.1.
Also, whenever I get notifications, the pulse notification light is only flashing a white LED and not repeatedly.

astroblack said:
Also, whenever I get notifications, the pulse notification light is only flashing a white LED and not repeatedly.
Click to expand...
Click to collapse
this is controlled by applications. froyo brings colored trackballs, but only if apps support it

I had trouble with swype saying that it's not compatible with my device. But got it to work after I re installed swype and rebooted.

flybyme said:
get your terms right else you will confuse people. memory can be rom or ram
rom hasnt been changed. available ram has been increased. your rom is whats used for installing applications. ram has no effect on available storage
Click to expand...
Click to collapse
Really? ROM is where I install my applications? Are you sure? I install my applications in READ ONLY Memory? That would be wrong. The ROM is where the actual firmware is stored, not where applications are stored.

That's because it's EEPROM, that is, Electronically Erasable and Programmable Read Only Memory.
Just because it can be flashed with new data doesn't make it Random Access though.

ChronoReverse said:
That's because it's EEPROM, that is, Electronically Erasable and Programmable Read Only Memory.
Just because it can be flashed with new data doesn't make it Random Access though.
Click to expand...
Click to collapse
Right and that is used for the actual OS not for the application storage. When people put say Cyanogen on their devices it is using the ROM (as far as my understanding) the RAM is used for the application storage and the memory for running applications. My issue was resolved when I wiped out my device, gave me access to 180 MB and still left nearly 250 of memory for running applications.
From what I can tell the RAM is split between the program storage and the running application memory.

ok buddy. you know what your talking about....

naturefreak85 said:
Right and that is used for the actual OS not for the application storage. When people put say Cyanogen on their devices it is using the ROM (as far as my understanding) the RAM is used for the application storage and the memory for running applications. My issue was resolved when I wiped out my device, gave me access to 180 MB and still left nearly 250 of memory for running applications.
From what I can tell the RAM is split between the program storage and the running application memory.
Click to expand...
Click to collapse
The RAM is the memory programs run in. RAM is volatile and will lose its contents when power is cut. You certainly don't lose your programs if you pull out your battery.
I shouldn't have said EEPROM actually. The Application Storage is actually flash-type memory, the same kind used in SD cards for instance.
So there are three basic parts: ROM, 512MB internal flash (+ external flash) and 512MB RAM. HOWEVER, it's possible part of the flash is used as the ROM.

ChronoReverse said:
The RAM is the memory programs run in. RAM is volatile and will lose its contents when power is cut. You certainly don't lose your programs if you pull out your battery.
I shouldn't have said EEPROM actually. The Application Storage is actually flash-type memory, the same kind used in SD cards for instance.
So there are three basic parts: ROM, 512MB internal flash (+ external flash) and 512MB RAM. HOWEVER, it's possible part of the flash is used as the ROM.
Click to expand...
Click to collapse
flash memory is still a type of EEPROM lol
@OP read these articles
http://en.wikipedia.org/wiki/ROM_image
http://en.wikipedia.org/wiki/Random_access_memory
http://en.wikipedia.org/wiki/Volatile_memory
http://en.wikipedia.org/wiki/Non-volatile_memory

naturefreak85 said:
Really? ROM is where I install my applications? Are you sure? I install my applications in READ ONLY Memory? That would be wrong. The ROM is where the actual firmware is stored, not where applications are stored.
Click to expand...
Click to collapse
yes he is exactly right. the nexus has 512 mb of RAM and 512 mb of ROM. the 512 of ROM is where the OS, your installed apps, and user data all gets installed. the 512 mb of RAM is active memory that runs the apps. you cannot install apps to the RAM, it is volatile as said above. you sure can install apps to the 512 mb ROM though, and that is exactly the way the nexus works. any app you have installed to your phone goes on the 512 mb of ROM. the OS takes up some of that, so when you check in your settings, you only see like 180mb left or so on a fresh factory install with no apps yet installed. as you install apps, that amount goes down as you use it up.

flybyme said:
flash memory
Click to expand...
Click to collapse
Yes but it works differently from traditional (or rather, the original) EEPROM so I wanted to distinguish it.

In short
RAM = the place where all processes running. OS will load the apps/programs to RAM before it can processed by CPU, and at this stage it called processes.
From 512MB RAM, typical N1's Froyo's stock kernel can access up to 394MB of RAM. Here is the dmesg ouput f
Code:
<6>[ 0.000000] Memory: 128MB 91MB 175MB = 394MB total
<5>[ 0.000000] Memory: 394360KB available (3936K code, 971K data, 120K init,
272384K highmem)
How many processes can be run at the same time are limited to the RAM availability.
ROM = the place where the apps/progs being stored. Same thing as we stored/installed programs/apps in hard disk drive.
in N1, "ROM" is just a flash memory, similar to usb thumb drive. The contents always available even if you powered your device down. Yeah, apps also can be stored into microSD card.
How many apps you can install are limited to how may free spaces left in your storage, ie, "ROM" and SD card.
Thank you.

I have frf85b for att version (using for vodcom in Tanzania) but my tether doesn't work. I can see the network and connect but no internet. I think its DNS problem because my computer can ping the internet but nothing past that.
Sent from my Nexus One using XDA App

michaelbart0n said:
I have frf85b for att version (using for vodcom in Tanzania) but my tether doesn't work. I can see the network and connect but no internet. I think its DNS problem because my computer can ping the internet but nothing past that.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Mine was doing the same thing at first. Then I opened the browser on my phone to check that the 3G connection was working, and suddenly the computer had access too. It might have just been a coincidence...

[Q] internal memory usage list?

As many others have, I frequently run into a lack of internal memory on my nexus. I only ever have about 20 mb free. So today I decided to try and figure out what takes up all my internal mem.
I have a stock, non rooted phone running 83d.
I use apps 2sd and dolphin browser with cache on sd
I went to apps2sd and added up all the package sizes of the apps on my phone memory, came up to about 93mb. Yet I only have about 20mb free. That means about 70mb is being used up by other crap. Phone and contact storage is only 2mb each. So what is eating my memory and how can I find out? is there an app that'll chart out internal memory usage by app/file?

Disk Usage, from the market may help...
Sent from my Nexus One using XDA App

Imbalance said:
As many others have, I frequently run into a lack of internal memory on my nexus. I only ever have about 20 mb free. So today I decided to try and figure out what takes up all my internal mem.
I have a stock, non rooted phone running 83d.
I use apps 2sd and dolphin browser with cache on sd
I went to apps2sd and added up all the package sizes of the apps on my phone memory, came up to about 93mb. Yet I only have about 20mb free. That means about 70mb is being used up by other crap. Phone and contact storage is only 2mb each. So what is eating my memory and how can I find out? is there an app that'll chart out internal memory usage by app/file?
Click to expand...
Click to collapse
93mb of apps is just for the actual app .apk file. app data takes a HUGE amount of space.

most things i've got left on the phone don't really have much associated data from the ones i've checked anyway. Still, can't believe there's no app to show internal mem usage. There's tons of them for the SDcard... Also, diskusage is only for sdcard. I'd still like an easy way to see what's taking up all my internal mem and decide if i want to uninstall it or clear the data or whatever.

As soon as you open diskusage, it asks if you wanna see internal or external...
Sent from my Nexus One using XDA App

I like this disk usage app,i find it interesting how the developer used the tap to com on the different layouts and how data is used

[Q] Nexus one flash partition layout, lowest 63MB...

I've been trying to recover some space on my Nexus one and have been largely successful in doing so with a combination of tricks, but while looking at my partitions and tallying up the numbers something didn't seem to be adding up right; the unit is supposed to have 512MB flash, but I was coming up about 60MB short.
I found this thread which discusses the partition layout of the N1; the sizes they show all seem to match up well with what my device shows. Now, the hex address of the end of the last partion (user data) ends just a couple MB short of 512MB; the start of the first partion (misc) however seems to start over 60MB into the memory space... is there a reason for this, and if so what's occupying those lowest 63.75MB of flash space?

Baseband, AKA "radio", is what you're looking for. Unless you want your Nexus not to boot anymore, it's not advisable to try and repartition baseband space.
Instead of working hard and uselessly wasting effort, use A2SD or any other kind of linking to SD-mounted EXT partition. No matter what you try, Nexus doesn't have nearly enough internal space for any common use.

That answers my question, thank you.
As I mentioned in my original message, I was successful in freeing enough space on my device; a combination of moving apps and libraries (copy to system/lib and symlink back to original location) into the system partition and clearing out bulky or unnecessary apps has left me with over 60MB of free data space without even having to resort to fancy A2SD business (just normal android move to SD card). I was simply curious about what was filling in the remaining space on the flash chip and the radio pretty much fits the bill.

As someone with pretty average amount of user apps (a bit less than 100) and 700 MB user space taken, I can't see the point in doing what you mentioned for anything but pure fun. But if that suits you - I won't argue.

Well, by my app drawer I'm sitting at ~125 (44 purely in data, 34 moved to SD with standard android method, rest either native system or moved there) apps, and if my "puny" N1 can have 60MB free and not even need ext-style A2SD I'm not quite sure how the N1 doesn't have "nearly enough internal space for any common use". Seems to me the point (not "pure fun" as you dismissively imply) of doing what I've done is to able to keep using a pretty decent phone that still has more than enough storage space if you make the least bit of effort to manage it.
But hey, who am I to judge if you prefer to buy whatever latest phone the carriers tell you you should want every 12 months just so they can cram more bloated apps on it?
I appreciate the answer to my initial question about what's using the lowest block of flash storage (I was simply curious about what was using it - I couldn't find information if it was flash overprovisioning or some other low-level portion of the OS using it), but I don't really appreciate the unnecessary negative attitude and commentary for what was just a simple question. Thanks anyways.

I guess you didn't understand my point(s). I'll elaborate:
First and foremost, my point is this: N1 is a crap of a phone. Having it for over 1 year, and trying to adapt it to my wife for 3 or 4 months later on before giving up on it, taught me that this phone can't be dealt with by anyone who doesn't want to accept its touchscreen limitations. It was so refreshing having the phone (MT4G in my case) just react without fuss and not expecting it to crap out at any given time - not even mentioning the huge speed-up. The price of "upgrade" (selling the N1 and buying any previous-generation phone, like DHD/MT4G/DS/DZ) can be brought down to as low as $50, and the benefits are huge, I already wrote it a couple of times on the forum.
To the storage point (actually, several points):
N1's NAND is painfully slow, compared to anything, even to regular Class 2 SD card. You can try copying any large file from NAND to EXT and back, from NAND to NAND and from EXT to EXT and see what takes more time. You're likely to discover that A2SD actually adds performance instead of hurting it.
My app data (/data/data/*) alone takes roughly the same space as your whole internal /data storage has, so I guess the amount of apps alone isn't that meaningful of a measurement. I still call it a perfectly normal and average data usage - I don't have anything special installed, no heavy games that save 200+ MB of data on internal memory, just apps like Goggles, Flash, iGO and a couple of other big apps that aren't movable by normal means (and tend to crap the system out when they're forced to move). The problem in your approach is not even the one-time amount of work you had to invest to make that space, but the amount of work you'll have to invest to keep the phone running - moving system updates to /system upon every update, clearing browser cache, etc - generally, keeping things in constant check. Free time is something you learn to appreciate when you don't have enough, and more hassle-free setup is always preferred IMHO.
But again, different people have different needs, so while I can post my point of view - I don't argue with yours.

Thank you for elaborating, actually; it clarifies much that was not apparent in your earlier posts. This thread isn't really about the pros and cons of the N1 so all I'll say is that the advantages of the N1 (small size, OLED, build quality, tricolor trackball LED, etc..) still outweigh its manageable downsides for me, even compared to very modern handsets - so I'll stick with it until I can find a suitable upgrade that I'm happy with (is it so hard for HTC to make a <=4" qHD AMOLED? Seriously...).
Your point about the NAND being slow is interesting; this is something I hadn't heard and will have to benchmark; if it pans out it would be a point in favor of A2SD, but not really in favor of replacing the device over it
The upkeep I don't find that bad; Titanium backup makes integrating updated system apps a single touch for the batch, and I've only got a couple libraries symlinked into system that are unlikely to be frequently updated. With the space I've freed I shouldn't need to clear browser caches nearly as often - so it actually saves me time and frustration regularly for the one-time effort.
Thanks again for taking the time to reply and to clarify your points

If a2sd+ doesn't work for you you could do custom mtd partitions like I did using fireats custom mtd if u google it u will find it basically you can shrink ur system partition down to almost half because it is being wasted I mean whatever size u want to define it as. I'm using miui and my system partition that i defined is 120 mb (4 mbs are free just in case) and my cache partition is 15 mb. Now that leaves 301 mbs free for user data. I have 107 user apps installed about 10 games or so and I still have 120 mb free for user data for me that's more than enough. This way ur phone won't be buggy because u will only use the system partition for ur rom again I would suggest miui since it takes minimal space and is very smooth and stable with amazing battery life (I use tiamat kernel). Hope this helped
---------- Post added at 06:57 PM ---------- Previous post was at 06:52 PM ----------
Oh if u use a2sd in conjunction with custom mtd then u can have close to 750 mb of space available for user data given that ur sd ext partition is 512 mb (which was stable for me using 8gb card) that's basically rivaling new phone memory so don't just call the nexus one off just yet it can surprise anyone that knows how to play with it or stuck with it for 2years like me lol.

I've already been using root access with shell and titanium backup to move apps and libraries into the system partition without resizing it, so I'm already using the available space there. The only major difference is you've dramatically shrunk your cache partition from the default of (IIRC) 100MB down to 15MB; this seems like a pretty huge reduction, and I feel this would have performance implications, especially when running larger apps...
Other than that, if I find my current space as set up proves to be inadequate in the future (it seems just fine for now) then a2sd appears to be the best option for those who need even more additional space on a nexus one.

15 mb is more than enough for cache partition unless u plan to download huge 3d games and as we all know gaming isn't the reason that we have held on to nexus one for so long I haven't seen any app large enough to not install due to my partition size. I messed around with that too first I had it set at 5 mb but that made market force close every time then I set it at 10 was stable but large apps couldn't download and then I tried 15 and hasn't given me a single problem. Otherwise all that space is wasted so why not dedicate it to user data? With 20 mb partition u can download almost all games that can function on nexus one but since I'm not a big mobile gamer I stuck with 15 mb cache.

Most normal programs don't use /cache.
To fix your cache market issue:
Code:
su
busybox mv /cache/download /sd-ext/download
ln -s /sd-ext/download /cache/download
If you don't have a sd-ext you could use /sdcard/download instead. The directory will already exist if you've downloaded anything from the browser, so I just remove /cache/download before linking. I used to get package file invalid errors from this setup though...
Ti backup will also let you move stuff to /system and re-odex your rom instead of shrinking /system. Sure, everytime system stuff updates you need to click a few times, but unless space is real tight, it works fine. The re-odex-ed rom seems to boot faster for me than with external dalvik-cache, too, but that could just be me pretending. I've never busted out the stop-watch.
I like to keep apks on a2sd and put dalvik-cache on internal memory. It's kinda like raiding the two interfaces together to get the sum of the bandwidths of both when launching a program.
siberx: I'm sticking with the N1 until I find a decent phone that has been designed to fit in my pocket instead of sitting in a purse or on the bar too... I considered the glacier for a while, but, near as I can tell, the only benefits of going there are better touch screen and gpu.

I used firerat's mtd patch to rejigger my girlfriend's desire paritions to something more sensible (something like a 230mb system partition stock? ridiculous!) and that worked smashingly; the same trick against my N1 didn't go so well though. Seems like my Nexus with CM6.1 on it is still using the cache partition for dalvik at least partially, and I think shrinking it down to 20mb made it too small to boot right. Not a big deal anyways; I've got enough space to work with as is
I tried to do some benchmarks on my internal flash for comparsion, but the only decent benchmark I could find (without getting manual about it on command line) was Passmark's mobile benchmark; problem is they wan't 90MB free to run the internal memory benchmark, so my 60MB isn't cutting it for that
Anybody know of a decent benchmark that will bench both internal and SD read/write speeds that doesn't need such a huge chunk of free space?
ezdi: I considered for awhile buying a G2 for the faster CPU/GPU and improved touchscreen, but ultimately decided against it due to the extra weight and thickness (combined with the nexus' other advantages like OLED and tricolour LED). Eventually some manufacturer will figure out there's a still a market for compact high-end phones...

ezdi said:
siberx: I'm sticking with the N1 until I find a decent phone that has been designed to fit in my pocket instead of sitting in a purse or on the bar too... I considered the glacier for a while, but, near as I can tell, the only benefits of going there are better touch screen and gpu.
Click to expand...
Click to collapse
Better touch screen is a reason enough by itself.
GPU, much faster and bigger internal memory (both system and data), much faster and bigger RAM, and most of all - 90% HW-compatibility to one of the most popular devices in the world (DHD) - means staying updated and speedy with ROMs that fly where they crawl on Nexus (if they exist at all). Plus - all ROMs besides ICS are 100% functional, CM, MIUI, Sense 3/3.5, you name it. And if it's not enough, 20% hassle-free overclock is standard.
From quite satisfied Glacier owner.

[Q] All available space disappearing ( AllianceROM Galaxy Note GT-N7000)

Hi all. Today i started experiencing a very peculiar problem. I opened the Camera app and got a message: "Not enough memory". I had some megabytes left actually, but i checked Settings>Storage and it didn't report any available space. I deleted some files (~169 MB). Storage then showed 169 MB of free space. I opened Camera again, same problem. Went to Settings>Storage, 0 space available. Deleted more files(34 MB). Free space 34 MB. Open Camera, same message. Check Storage, no space available. (Settings>Storage Only shows Pictures, video; Audio; Download; Miscellaneous files. Available space is not even shown, but the USB storage bar has a grey part)
My phone is GT-N7000 running on AllianceROM ICS Final, I've been on this ROM for about a month. If more technical information is needed for your answer, just ask.
I have tried: rebooting, clearing data and cache of Camera and Gallery, wiping cache partition.
Any solutions for this problem?
Thanks for your answers in advance!
P.S. Sorry if this question was asked already elsewhere, I wasn't able to find any useful information.

Download an app that will show you what is taking up so much space, just have a look in google play

Also check your data/log file. Delete if lot of memory used there.

So... I deleted 400 more megabytes, and then I got 200 MB free space. If this space doesn't disappear, the problem is gone, I guess. All of this was very strange.
Thanks for the support anyway.