Related
Hello,
I bought my Diamond yesterday from PDA plaza in Montreal. I am very puzzling with the memory I have on my unit. By clicking on Setting and Memory, this is what I have:
Storage: Total: 83.06 MB In use: 26.41 MB Free: 56.66 MB
Program: Total: 113.08 MB In use: 61.20 MB Free: 51.88MB
Very far from the specifications, which are ROM: 256 MB
RAM: 192 MB DDR RAM.
So is my unit defective? or this is normal.
Thanks in advance, because if I need to replace it, it need to be done as soon as possible...
Philippe
This would appear to be either a Grey Import or Pre-production specification? You should double check:
Go to - Start> Settings> System Tab> Device Information> Hardware Tab>
There you will find all the information about the physical memory?
If your correct then you may want to return it to the supplier or ask for a price reduction if your happy to keep it?
Hope this helps?
Thank you,
Yes, it is written Ram size 192 MB and Flash 256 MB. But why is that so different when I check on setting and memory?
Philippe
A chunk of memory is taken up by the Rom (System Software) and other system resources as they run. As you see new "cooked" roms become available you will see an improved level of memory usage - its nothing to worry about as long as performance is as expected?
I am incredibly envious that you already have the device though - looks like we here in the UK are going to have to wait a while longer unless we want an imported model?
Again - Hope this helps!
Because of all application running on your PDA...I heard that, with the 3D touchflo, there is "only" 90 Mo of Ram available !!
I'm using the Diamond to post right now. Touchflo 3d is a memory hog. only about 30% is free with no other applications running. the browser uses another 10%.
Thanks for all your comments. So to compare with my unit, please could you tell me how much memory you have for Storate and Program. So I will know how my unit compare to others...
Cheers,
Philippe
**** ME! How can it only have 50 MB of RAM free? Ive always got at least 60 free and I have 60 less to start with. Maybe TF3D is a massive hog?
But looking at the things you said, something like 113 available, 50 in use and 60 free, thats a good thing, you must have 192 built in, usually with 128 build in, you'll get figures of 80 available, not 113.
The one thing I dont understand is why the program memory never says that available is the amount of RAM you actually have. Because on startup I've usually got about 20 in use, and thats by the OS. So, when you take available program from the RAM you're meant to have, and get a number, lets say 80MB in this case, whats that used for?
rorydaredkign said:
**** ME! How can it only have 50 MB of RAM free? Ive always got at least 60 free and I have 60 less to start with. Maybe TF3D is a massive hog?
But looking at the things you said, something like 113 available, 50 in use and 60 free, thats a good thing, you must have 192 built in, usually with 128 build in, you'll get figures of 80 available, not 113.
The one thing I dont understand is why the program memory never says that available is the amount of RAM you actually have. Because on startup I've usually got about 20 in use, and thats by the OS. So, when you take available program from the RAM you're meant to have, and get a number, lets say 80MB in this case, whats that used for?
Click to expand...
Click to collapse
With 128Mb RAM in machine Touch Dual shows 101Mb total, but Asus P750 120Mb. so adding another 64Mb we only gaining 12Mb total? Is that what you are trying to say???
83+113=196 is more than 192MB. Isn't the 256MB only for ROM (so WM6.1 OS+pre-installed programs?)
83 + 113 should not equal anything
Storage is the free space after a rom has been installed and is basically the free part of the ROM. With a lite made rom, it should be as large as possible, and the used storage on first boot should be near zero.
The 113 part is the RAM.
What I'm trying to say is where is the other 79MB of program memory (RAM)?
Because its not like on soft reset, you have say 113MB program free, no you have that available and about 60MB free. the approx 50 that is used up in this case is by startup items, and the stuff windows needs to rum. So where is this 79MB?
rorydaredkign said:
The one thing I dont understand is why the program memory never says that available is the amount of RAM you actually have. Because on startup I've usually got about 20 in use, and thats by the OS. So, when you take available program from the RAM you're meant to have, and get a number, lets say 80MB in this case, whats that used for?
Click to expand...
Click to collapse
I'm sure it has some use. Hard drives are never quite as big as they say because of things like pagefiles, file allocation tables, etc.
Maybe that hidden 80MB is being used by system processes that are kept hidden. That's the only explanation I can think of, because computers don't seem to have a similar problem.
Dark Fire said:
I'm sure it has some use. Hard drives are never quite as big as they say because of things like pagefiles, file allocation tables, etc.
Maybe that hidden 80MB is being used by system processes that are kept hidden. That's the only explanation I can think of, because computers don't seem to have a similar problem.
Click to expand...
Click to collapse
I'm going to agree with you on that! No way they released all these phones with bad chips in them!
So i was using JACHero 2.63(the fastest of the Hero ROMs) and i still can't stand the lag. Before everyone suggests i format the card and make sure i have a linux-swap partition. I did that...and it is the fastest version i have found. But still to slow on certain things. There are times when i can't even see who is calling before the call is placed in voicemail.
But enough of that, i was wondering if anyone knows exactly why its so slow? I ran cat /proc/meminfo and free in terminal and if i remember correctly the same amount of ram was free on both JAC2.63 and JF1.51, there may have been a Mb difference but not something i thought would be a big deal. Now from what i have read i believe the HTC Hero has the same CPU but double the storage and memory. So i would think its a memory problem...but if both versions show the same amount of memory free wouldn't both be laggy as the other?
I maybe missing something but just wanted to try and see if i could get some answers.
Anyone?
More stuff is running in the background at all times in Hero ROMS than in JF ROMS. If you run a task manager you will see that there are alot more services running than in JF ROMS. Also Rosie runs in the background and uses alot of memory no matter how optimized because it searches for widgets. My only suggestion would be to like you said reformat sd card with the 3 partitions and also make sure you have a class 6 sd card. If it's still slow try cleaning up Rosie and modifying the build/removing all unnecessary widgets. There's a modified Rosie, 333kb compared to the ~600+ kb available at leakdroid.com Hope that helped.
Having more stuff in the background running will cause more RAM Usage. but i didn't see it. Can someone who is running JACHero 2.63 reboot the phone and once it is up and running, go to Terminal and run
Code:
cat /proc/meminfo
and post that info. Also in terminal run
Code:
free
JF1.51 meminfo:
Memtotal: 98668 kB
Memfree: 3892 kB
JF1.51 free:
Memtotal: 98668
Used: 97132
Free: 1536
damnitpud said:
Having more stuff in the background running will cause more RAM Usage. but i didn't see it. Can someone who is running JACHero 2.63 reboot the phone and once it is up and running, go to Terminal and run
Code:
cat /proc/meminfo
and post that info. Also in terminal run
Code:
free
JF1.51 meminfo:
Memtotal: 98668 kB
Memfree: 3892 kB
JF1.51 free:
Memtotal: 98668
Used: 97132
Free: 1536
Click to expand...
Click to collapse
sure give me a second
EDIT:
JACHero2.63:
cat /proc/meminfo
MemTotal: 98328 kB
MemFree: 2960 kB
Buffers: 140 kB
Cached: 23544 kB
SwapCached: 2060 kB
Active: 37880 kB
Inactive: 43604 kB
Active(anon): 29372 kB
Inactive(anon): 29524 kB
Active(file): 8508 kB
Inactive(file): 14080 kB
Unevictable: 948 kB
Mlocked: 0 kB
SwapTotal: 31440 kB
SwapFree: 26832 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 57000 kB
Mapped: 14584 kB
Slab: 3976 kB
SReclaimable: 984 kB
SUnreclaim: 2992 kB
PageTables: 5048 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 80604 kB
Committed_AS: 1511656 kB
VmallocTotal: 155648 kB
VmallocUsed: 61248 kB
VmallocChunk: 33788 kB
JACHero2.63:
free
total used free shared buffers
Mem: 98328 96544 1784 0 140
Swap: 31440 4608 26832
Total: 129768 101152 28616
Thanks, alritewhadeva i have some research to do. i'm not sure those tests are giving the right values. Your total is different then mine.
If they are correct i don't see why JF1.51 would be running much faster...the difference in memory doesn't seem like enough to cause lagginess...I could be wrong i guess...maybe those small amounts are huge in mobiles?
damnitpud said:
Thanks, alritewhadeva i have some research to do. i'm not sure those tests are giving the right values. Your total is different then mine.
If they are correct i don't see why JF1.51 would be running much faster...the difference in memory doesn't seem like enough to cause lagginess...I could be wrong i guess...maybe those small amounts are huge in mobiles?
Click to expand...
Click to collapse
Linux will fill the memory as close to 100% used as it possibly can.. Things load faster from memory, so it keeps everything it possibly can in RAM. Free memory is wasted memory.
So as long as there isn't something grossly wrong with the memory management in a ROM, they should all be pretty similar when you look at "free."
The difference is, in a lighter ROM like JF or Cyanogen, more of the actual framework fits in RAM under normal use, so you can access it quickly. In Hero, the framework is larger so parts of it don't fit and get swapped out - causing lag.
Saiboogu said:
Linux will fill the memory as close to 100% used as it possibly can.. Things load faster from memory, so it keeps everything it possibly can in RAM. Free memory is wasted memory.
So as long as there isn't something grossly wrong with the memory management in a ROM, they should all be pretty similar when you look at "free."
The difference is, in a lighter ROM like JF or Cyanogen, more of the actual framework fits in RAM under normal use, so you can access it quickly. In Hero, the framework is larger so parts of it don't fit and get swapped out - causing lag.
Click to expand...
Click to collapse
That's what i was starting to think, thanks for the info Saiboogu.
Run sh /system/bin/swap -s to check swap status and other mod values.
Ok so I did this to check on my stuff, cause i wanted to make a compcache.
*** CompCache ***
compcache_en=0
cc_memlimit=16
cc_disksize=32
cc_backingswap_en=0
cc_backingswap=/dev/block/mmcblk0p3
swappiness=30
*** Linux Swap ***
linux_swap_en=1
linux_swap_partition=/dev/block/mmcblk0p3
....................
=== Linux Swap status ===
Linux SWAP enabled on /dev/block/mmcblk0p3
Linux Swap: swappiness - 30(system) 30(user)
i'm running JACxHEROSkiv1.5r2 and want to know what I can do to inprove the speed of the ROM.
Any suggestions are welcome i'm not much of a programmer
Looks nlike you need to edit the"cc_disksize=32" value, but I doubt that affect the speed tbh.
What size swap partition are you running?
Im running with 96 MB linux swap
btw what is that (cc_disksize=32) ?? the linux swap size ?
I read i a couple of posts about the linux swap and compcache and read that if you enable comcache it could speed up your device slightly.
YuYe said:
Im running with 96 MB linux swap
btw what is that (cc_disksize=32) ?? the linux swap size ?
I read i a couple of posts about the linux swap and compcache and read that if you enable comcache it could speed up your device slightly.
Click to expand...
Click to collapse
Ah thought CC was already enabled.
compcache_en=0 < This needs to be changed to one to enable CC.
cc_disksize=32 < That's the CC size, I wouldnt change it.
I would *strongly* recommend reducing your swap size. It seems to be that the bigger the size, the faster it is at first, but then the phone starts to get really slow. Go for 48 or 64mb.
I don't really know a lot about CC, I've never edited the config files for it as it's generally set up for optimum performance already (and I also don't like the idea of it wearing out the nand). If you look in the xHero there are other configurations for CC, CC+swap, swap, CC +backing swap that you may want to look at.
twistedUmbrella said:
Alright. Ran a 96 mb swap all day to test. Load screen about equal. It was "ghost lag" where you do something and it freezes for a minute
Click to expand...
Click to collapse
Ok then i better change the size of my swap. also does it matter if your on ext3 or 4 ?
And what is the difference between linuxswap and compcache ?
Sorry for these noob questions but I'm a bit lost
YuYe said:
Ok then i better change the size of my swap. also does it matter if your on ext3 or 4 ?
And what is the difference between linuxswap and compcache ?
Sorry for these noob questions but I'm a bit lost
Click to expand...
Click to collapse
no ext doesn't matter.
Compressing pages and keeping them in RAM virtually increases its capacity. This allows more applications to fit in given amount of memory.
Click to expand...
Click to collapse
The problem is the Hero UI is quite CPU intensive, so less CPU power can be devoted to compressing/decompressing files in RAM.
Linux-swap is a separate partition where files are paged, increasing the amount of memory. The difference being it's outside the RAM.
Most chefs have optimized their custom ROMS with a large "file system cache" to, in theory, increase performance. After much experimentation, I have found so far that this seems to directly correlate with some of the memory leaking we see in these ROMS! (perhaps the WM6.5 file caching algorithm is faulty?)
Anyway, you have nothing to loose but time, so please consider this simple tweak...
If your ROM has a HKLM\System\StorageManager\FATFS\CacheSize of a large value (4096, or 0x1000 in hex, seems to be common) change this instead to 0x100 (256) and soft-reset.
Now, use the phone a bit, and notice how much free RAM you get back after closing everything down. Even if the free RAM doesn't initially jump right back up to almost where it was at boot, you'll notice that CleanRAM does a *much* better job of getting it right back there.
To me, the phone doesn't feel slower in any way with this small of a file system cache. Turning it off completely did feel a bit slower, but I could have just been imaging things.
Either way, I've had a cache value of 0x100 since my last reset several hours ago, and have had Opera, CorePlayer, IE, YouTube, Adobe Reader, and several other things opening and closing and running concurrently, and once I shut them all down, I am right back to about where I was at boot. The one time it didn't get there, cleanRAM gave me back 18MB and there I was!
Try it !
* UPDATE: I don't claim this will completely fix memory leaks -- I'm sure there's many factors at play here -- but it does seem to really help!
i just tried it and it dropped down to 52% after i was at 70%. it feels a bit slower for me but nothing to major.
thanks for sharing
Tried it on NRG's Latest, changed from Auto to 256k (using Schaps advanced config).
Mem Usage seems to stay a little lower, and the performance seems similar.
Just my experience.
Dave
will try it and report back
attached a cab
This really does work... I even noticed sometimes if I leave my phone alone the memory usage will go down a little bit now instead of leak. No performance issues. Using dotcompt's latest ROM. Works great, hangs around 65% memory in use now even with heavy use. I changed my cache setting to 128kb.
I tried this tweak with the 6.5 stock ROM from HTC on a unbranded model. De default value was 0, i changed it to 128 and now i'm hoping for some action
I will report back tomorrow if i notice any change.
Thx for the tip ^.^
Hi all, well i tried this tweak. It does seem to slow things down a bit. I saw there was an option to disable the cache, i'm going to test this now.
For me 128 was the best value.
Grtz,
FeareX
I'll give it a try at 128kb .... let's see
edit: After first reset upcoming appointments and weather forecast in home tab were missing ( -> changed mem size to 256kb ... let's see
when i went to try this out, my cache was set to 0, so i changed it to 256 and didn't notice any change and the same thing occurred when changing to 128
does this work?
titan427m said:
when i went to try this out, my cache was set to 0, so i changed it to 256 and didn't notice any change and the same thing occurred when changing to 128
Click to expand...
Click to collapse
zero means that windows mobile takes what ever it wants/needs. If you want zero you should disable the cache.
also watch out for this: http://wiki.xda-developers.com/index.php?pagename=Windows_Mobile_6_Standard
I also played around with the maximum buffer size for HTC Sense. Found somewhere in HKLM\Software\HTC\ResProxy
Some Custom ROMs already have a lower value. In Advanced Config you also find a setting for the glyph cache.
And I kicked out many tabs. For example the music tab is locking memory once it is used.
But keep in mind that caching is done for speed. And the best tweak is not to even use HTC Sense! ;-) But a blank today screen is not very useful, so I am still looking for a good solution and testing alternatives.
At least Windows Mobile devices should have much more RAM
I changed mine to 256, rebooted and 2 things i notice. SMS that comes in does not display the caller name. It only displays the number. I can view the SMS from the tab but when i tap on the sms and goes into the sms compose window, no sms is displayed at all
Changed back to 0. It's probably just me but FYI
unclemiltie said:
yes you can
blocks are the same to the mechanical parts are simple, out with the old in with the new.
You'll need a tune in the 9-3 that knows about the new engine though. Fortunately the usual suspects can do that for you.
(Oh, and that's exactly what was in the 9-3 Viggen, a B235R)
Click to expand...
Click to collapse
Even though the Viggen has the same motor. That monster must have more to it. Viggen is the fastest Saab I know of. I own a 2002 convert.
---------- Post added at 05:44 PM ---------- Previous post was at 05:41 PM ----------
jsmith8858 said:
Most chefs have optimized their custom ROMS with a large "file system cache" to, in theory, increase performance. After much experimentation, I have found so far that this seems to directly correlate with some of the memory leaking we see in these ROMS! (perhaps the WM6.5 file caching algorithm is faulty?)
Anyway, you have nothing to loose but time, so please consider this simple tweak...
If your ROM has a HKLM\System\StorageManager\FATFS\CacheSize of a large value (4096, or 0x1000 in hex, seems to be common) change this instead to 0x100 (256) and soft-reset.
Now, use the phone a bit, and notice how much free RAM you get back after closing everything down. Even if the free RAM doesn't initially jump right back up to almost where it was at boot, you'll notice that CleanRAM does a *much* better job of getting it right back there.
To me, the phone doesn't feel slower in any way with this small of a file system cache. Turning it off completely did feel a bit slower, but I could have just been imaging things.
Either way, I've had a cache value of 0x100 since my last reset several hours ago, and have had Opera, CorePlayer, IE, YouTube, Adobe Reader, and several other things opening and closing and running concurrently, and once I shut them all down, I am right back to about where I was at boot. The one time it didn't get there, cleanRAM gave me back 18MB and there I was!
Try it !
* UPDATE: I don't claim this will completely fix memory leaks -- I'm sure there's many factors at play here -- but it does seem to really help!
Click to expand...
Click to collapse
If the transmission is good in the 95. I would use it and swap ecus. Have to make sure the motor mounts are in the same location. I would also use the CV shafts from your 95. I have thought about that when we still had our 2001 93. Going with a newer motor to get out of the sludge year Ect. 93 would be a sleeper though. Vroom vroom!!!
Hello there,
two days ago i flashed teamhacksung's ICS aka CM9.
Firstday: everything smooth and okay
Second day: launcher starts to FC here and there, in the cm9 thread i found this "guide" (to bad that i just copied it to an txt and didnt copied the link...)
Code:
1. download Rom Toolbox from market, install, open
2.change to performance tab
3.build.prop tweaks
4.VM heap size to 48 mb
5. program will ask to reboot do it, go to toolbox again and choose Auto Memory Manager
6.choose presets->default
7.reboot and/or wipe cache
i downloaded Rom Toolbox and checked heapsize, currently its 128MB. So my question, is step 4 meaning to increase heap size from somthing default (<48mb) to 48mb or is it meant to decrease from current 128 to 48 mb? if i'm not remembering wrong, i had to increase heap for my tomcat server after having problems. so, (if its meant to) why decrease heap in android from 128 to 48? a short explanation would be cool.
I hope someone can help me with the heapsize question, i dont really want to make it even worse
Thanks in advance
Maybe will help u:
VM Heap Size
The heap is an area of dynamic memory allocated to programs. With a larger heap size, there is more memory for the program and the garbage collector can run more efficiently. Therefore, it is possible to get better performance by setting a larger VM heap size.
However, if you set it too high, you can run out of free memory which can trigger swapping which will degrade performance. Therefore the VM setting is a trade-off.
The optimal value will depend on the RAM on the device as well as the programs and usage patterns, therefore the optimal setting can often only be determined by the user experimentally.
Default value: varies between devices
Click to expand...
Click to collapse
source: droidgram[dot]com
It should be noted that in the ICS builds the build.prop now contains 3 variables pertaining to the heap size:
Code:
dalvik.vm.heapgrowthlimit
dalvik.vm.heapsize
dalvik.vm.heapstartsize
With the size in the tweaker referring to dalvik.vm.heapsize, the other two are new.
I have no clue as to what any of this means but I thought I should mention it.
Thanks for this informations, i'll try a lower value than 128
dodgex said:
Thanks for this informations, i'll try a lower value than 128
Click to expand...
Click to collapse
+ this Archive will help u :
http://forum.xda-developers.com/archive/index.php/t-1025915.html
damn...
it was way smoother (at least what i saw until now)...
but at least mp3 player (default music app) does not start...
first i set to 64m but as i saw that mp3 didnt work i thougt, maybe to less... i increased to 96 but here was mp3 also not working, after setting back to 128, still not working mp3...
as in the guide, i always cleared cache after changing value.
someone got an idea? do i have to reflash cm9?