The HTC Diamond reserves 64MB for Opera which leaves 112mb for programs.
I dont use opera that much, is there a way to decrease that 64mb to something like 32mb?
AFAK, it's not for Opera, 64 mb is dedicated to the graphics acceleration. You cannot change this amount.
Related
from the HTC specification we have in our Diamond's 198 RAM, but available is only ~115 MB. I assume that 64 MB is used by graphic card and another few MB is used bu gps, gsensor, phone, etc
My question is why is needed 64 MB allocated all the time for graphic card? Why its not used dinamically allocation? And what the hell is doing the graphic card with 64 MB? My laptop with extended screen and with 1040x1050 resolution is using only 16 MB of RAM (shared memory)
Why not allocate by default 16 MB to graphic card and free some RAM to be used in application? - especially that there are no application to use the HW acceleration? This is mine only dissapointed - all the time i don't have enough RAM (IGO 8 + Opera and RAM its 100% used)- and that-s why i bought it -to have it enough
Has it occured to you that your premise of the graphic's card using 64MB RAM could be wrong? In which case, the rest of your question makes no sense.
I'm not saying it does/doesn't but it sounds like you've just guessed and then posed a question based on a potentially flawed fact!
Mathew
maybe soon will be program with you can be able to change that.
ROM: CM6 from 08.12.2010
Overclocking: Interactive governor : 1000mhz : vsel 62
Launcher: Launcher Pro
Note: I disabled "keep home in memory"
I was using 800mhz with 52 vsel and vm heap size 32 and I wanted to test an app "TV Flash"
It's an app that plays tv through flash and I was keep getting app crashes everytime I played my favorite channel.
I overclocked as mentioned above (1000mhz ....) and I set the vm heap size to 50m.
I believe this is the amount of ram that can be alocated to an app. Am i right?
Now my favorite channel plays flawless.
My question is:
Is there a problem of keeping the vm heap size to 50m, 64m?
Thanks guys!
Nope, no problems. Just that you'll run out of memory very quickly if you do something intensive.
Lollipop_Lawlipop said:
Nope, no problems. Just that you'll run out of memory very quickly if you do something intensive.
Click to expand...
Click to collapse
Well then...It seems that I missunderstood what vm heap size is!
Can you please explain and recommend a way so I wont run out of ram when watching live streams?
And do you think that the release of froyo will fix this issue?
There's nothing you can really do about it. You'll just have home reloaded and other applications closed. The only solution is to buy a phone with 512mb of memory.
Froyo isn't a magical upgrade. The most we will probably see from the firmware is feature parity with the Milestone 2 (minus Milestone 2 specific features and BLUR). All performance related stuff is mostly in our hands already (think JIT).
[EDIT] JIT actually takes up a bit more of your RAM. The difference is quite noticeable if you multitask a lot.
Is there a optimal heap size we should use? What effects does it have if you set the heap size smaller or greater?
Just tried increasing the heap size on my phone. Set it to 48MB and angry birds, my text editors, etc, all finally run consistently smooth. Launcher reloads more often now, but that's not a big deal given the much improved in app experience for me.
Sworkhard said:
Just tried increasing the heap size on my phone. Set it to 48MB and angry birds, my text editors, etc, all finally run consistently smooth. Launcher reloads more often now, but that's not a big deal given the much improved in app experience for me.
Click to expand...
Click to collapse
Yes...Apps seem to not crash because they are being allocated more memory..
I was wondering:
A friend of mine said something like this "Android doesnt need more than 256mb of ram to run smoothly...but due to poor coding app developers dont seem to align or match their apps with the specifications of the android system"
Example: Dolphin HD crashes a lot when playing or viewing flash content and it seems to eat (when selecting heap size 64m) all of those 64mb that can be alocated to a process(app)...
What do you think guys?
yes, Dolphin HD really crashes more than the stock browser on my machine, with heap size set to default 32M
Dolphin HD crashes when I read some forums with very long passages, but the stock browser can display without problem.
Dolphin also occupies a lot of space for caching.
Would a ROM with more ram available run large 3D games better, than a fully loaded Sammy ROM?
Does more free Ram allow more applications to run in the background ?
Or does the ROM make no difference to how Android runs?
more ram= more apps running in the background
now for 3d games, if your phone already had enough space of free ram for the game, i dont see how more ram will will make the game faster, as your the game already had what it needs from ram, but of curse, having more ram will allow you to run more apps in the background such as music apps or myabe downloading files while playing etc...
hope this helped
I want tnow the partition size. Applications memory. How much apps i could install in mobile.
Hi there,
I have a rooted 2019 F7 (Mustang) - stock rom - to be honest it's not a great performer but the form factor is spot on. I need a fix or workaround for playing music + browsing at the same time.
I'm struggling to get the F7 to do simple multi tasking for example, playing music via Spotify, or a Radio app whle browsing the web.
I've tried the usual "tricks" to keep Android memory manager at bay, and stop it closing my music in the background e.g:
- a 4gb swap partition in /data/ via apps2sd;
- using termux to create a swap file, both in /data/ and /cache/;
- Using Swapper (root) to create a swap file; and
- various swappiness settings using teh above.
Swap seems to work superficially, as the partitions are shown as free memory whenI run
Code:
free -m
in terminal, however, the amount of memory used suggests the system is not utilising them beyond a few MB over ZRAM.
In any event - is there some clever workaround I can use to either keep my apps music alive / listen adn browse in the same browser etc?
thephatmaster said:
Hi there,
I have a rooted 2019 F7 (Mustang) - stock rom - to be honest it's not a great performer but the form factor is spot on. I need a fix or workaround for playing music + browsing at the same time.
I'm struggling to get the F7 to do simple multi tasking for example, playing music via Spotify, or a Radio app whle browsing the web.
I've tried the usual "tricks" to keep Android memory manager at bay, and stop it closing my music in the background e.g:
- a 4gb swap partition in /data/ via apps2sd;
- using termux to create a swap file, both in /data/ and /cache/;
- Using Swapper (root) to create a swap file; and
- various swappiness settings using teh above.
Swap seems to work superficially, as the partitions are shown as free memory whenI run in terminal, however, the amount of memory used suggests the system is not utilising them beyond a few MB over ZRAM.
In any event - is there some clever workaround I can use to either keep my apps music alive / listen adn browse in the same browser etc?
Click to expand...
Click to collapse
Best solution IME is a 192MB (or so) swap file in the /cache partition with priorities set to favor the exiting 64MB ZRAM based swap. Set swappiness to ~10 and call it a day. Spinning up a huge static swap partition in /data won't help (will likely have the opposite effect) as the low-end eMMC overtaxes the annemic processor on large comprssion/decompression tasks. The small static swap gives the ROM some 'breathing room' which reduces most lags/stalls on boot and wake from sleep. Better but not great.
Browsing is particularly taxing on this device (albeit typical behavior on a low RAM gizmo). Might try a browser that renders in the cloud like Opera Mini or Opera w/data saver enabled. Stick to a tab or two and use the integrated ad blocker (I prefer VPN based blockers but that's OT). Even with those measures browsing will be a painful experience if the tab is doing anything else that actively utilizes limited resources. Good luck.
I'll give that a go. Two things:
My system reports 256mb Zram - is that compressed into 64mb or something?
Opera mini doesn't work on the Fire 7, nearest I found is puffin - which is heavy slow and buggy
thephatmaster said:
I'll give that a go. Two things:
My system reports 256mb Zram - is that compressed into 64mb or something?
Click to expand...
Click to collapse
My error; forgot Mustang defaults to 256MB ZRAM on FireOS v6. That could part of the problem when fully utilized as it reduces available uncompressed RAM which is much faster given the low end processor which must handle compression/decompression. Note ZRAM only consumes as much RAM as needed. A tool like DiskInfo will give a graphical readout of utilization.
thephatmaster said:
Opera mini doesn't work on the Fire 7, nearest I found is puffin - which is heavy slow and buggy
Click to expand...
Click to collapse
Try the full version of Opera with 'data saver' enabled. In that mode it operates much like Opera Mini from a workload and memory footprint perspective. Mini works fine on the hardware; FireOS v6 is the bad boy (likely missing libraries).