I have a couple of problems which I want to fix. My system is 1.9.1 + perfmod +
up to 1,11 GHz.
First of all is the Cut the rope game. I'm getting continual freez at the end of every level after cardboard box with the message in system log: Exception! thread id=11: thread exeteng with uncaught exception (group=0x4001d888) and previous that can be the cause - failed to map the memory for fd=37 offs=7774208. I'm using version with perfmod. Original 351 firmware also has problems with this game (but I have no logs from it).
I've found that this game works stable only with 318 stock rom. 351 stock rom, 1.9.0/1.9.1 update of 351 or 318 rom with/without perfmod - made this game practically not playable. But has no sign on other bugs.
I've managed to solve the problem in Cut the rope by using 16 bit colour setting in chainfire. But do not know the normal solution.
The second is the problem with Juice defender. If I use it the system comes unstable and laggy. If I use tunable settings it comes fully unstable, inspite of my understanding of every setting.
And the last - my system was stable for some days but after I tried to use Juice defender my phone began to reboot continiously. Can I define the reasons of reboot somehow?
UPDATE
The problem with Juice defender/reboots was solved by reflashing firmware.
The problem with Cut the rope is appared to be the problem of memory heap size. Inspite of the max heap size of 64 mb the reaching of the 16 mb size cause an error of subsequent memory allocation. If I change start heap size to 20 mbytes the game working properly. But I don't think this is right, because it can lead to memory overflow by the apps that need few kilobytes of memory but getting 20 meters instead.
UPDATE
The problem with the game was fixed by applying the change of min heap size once without saving. So it IS the solution, but strange.
Related
How much memory do you guys generally see as "available" when you first start up your phone. I generally have 160-180mb of supposedly "used" memory. This is after a root and almost all possible bloatware being removed. Normally I would just figure it'll be freed up when I need it but I have had such issues playing Dungeon Defenders which is memory intensive. Sometimes it plays smooth as a champ, other times it stutters a lot. Other times it freezes during load times.
So is all that memory available and it'll just free it when it needs it? Or is that number unusually high?
Oh also my comic book viewer will force close sometimes on some images, even with its options set to use less memory, and I don't think it takes hundreds of MB of ram to open a zipped 500kb image. Then again I could be wrong.
Memory is used differently on Android than on your PC. Just because you have 100+ megabytes of available memory doesn't mean an application can use all of it. Each app has a hard limit of how much RAM it can use, which I believe is around 16mb but differs from device to device.
If you experience issues when running a game I would check to see what background services are running at the time that could be using up CPU cycles.
I have a Huawei Ascend G300 running Gingerbread. I've noticed a strange problem involving the memory.
The other day, my launcher kept restarting every time I pressed the home button. So I checked the running services and very few things were running. When I looked at the memory bar at the bottom however, it said 57mb used/1mb free. This device has 512mb of RAM supposedly, so something is obviously wrong here.
Since then, I have been checking the RAM usage bar in running services more often, and adding the used and free values together. From this I've noticed that the amount of total RAM varies wildly, I've seen values between 220 and 350. My RAM seems to just disappear and reappear randomly.
Does anyone know why my RAM could be disappearing like this?
Hey guys,
What i9300 ROM uses the least amount of ram?
My stock rom uses some 600mb after a reboot, and about 680mb after clearing ram.. I only have some 150mb available for apps, and even that amount isn't fully used, as some 50 megabytes are never used.
Background apps such as Skype always get killed by the system, even with persistent notifications, the launcher reloads all the time, it's impossible to switch between 3 applications without one of them reloading and losing progress, slowing me down and wasting my time.
Do you know of any roms that use 300-400 megabytes of ram?
Thanks.
Perhaps look into changing oom or "Out of Memory" values instead. It can easily be done with an init.d script, but if you need an easy way to do it, look for the V6 supercharger script.
[Q] Free ram 0.0bytes android 4.1.2 [low memory msg for all apps & frequent crash]
Hi!
I bought iball andi 5li android smart phone a few days back. The configuration of the phone is:
512mb ram
4gb internal
1.2ghz cortex a9 processor
android 4.1.2
Although my device runs almost every app out there (including temple run, subway surfers etc.) but occasionally im facing problems.
problem occurs after 3-4 days of restarting the phone.
when i restart and check the ram usage it says 350 mb (approx) as used and 150mb(approx) as free ram every app runs smoothly but as days pass by gradually the free ram starts decreasing down to 30 mb where all the apps (games and browsers) start crashing with a low memory message. then the conditions get worse after approx 2 hrs free ram is now 0.0 bytes and even the launcher,settings etc crash with a low memory message. The only solution out is to restart the phone.
[used androids before and is quite aware of closing or killing apps but none is working]
Already Tried:
# removing apps from recent list
# stopping apps from Setting>apps>running apps & cached apps as well
# restoring to factory defaults
# used ram freeing apps (no change on ram)
Well just like on PCs if you keep your phone running for quite a while a lot of dead apps will fill your RAM and reduce performance, the workaround as you know it is restarting your phone.
I don't know that how this can be permanently solved. I myself restart my phone after one or two days.
Regards,
RaHBeR
Sent from my A2 using xda premium
One of your main issues is that your ram is the min to even run Android. With 5.0 they are supposed to optimize it for devices with low ram. Not a whole lot you can do right now.
Wayne Tech Nexus
a little fix
it is a common problem with all low ram devices
root your phone and install greenify (or maybe greenify pro with xposed framework ) and hibernate those apps that are using the ram on your device u will get much more free ram now explore around a bit
I'm playing rr3 now for years on my HDX7 and the 'out of memory' problem was always with us, starting with CM11 and growing over the time, because the game become bigger and bigger with every update.
I started to free up memory as much as possible by installing only the minimum of apps (nano gapps) and deactivating unnecassarcy system apps, but nothing helped.
Playing with the Low Memory Killer and setting it to 'very light' in Kernel Adiutor helped for some time.
With the latest update to LineageOS 14.1 from ggow [!! BIG THANKS !!] the problem seams to be controlled in rr3 V7.5.
But with the latest update from RR3 (V7.6) things become so bad, that I had to restart the game after nearly every round of lemans.
At this time I was searching the net for a way to make us of our 1GB Cache partition and by accident found a hint to my theory, that the problem with the systems garbage collection.
Here comes the solution, which is working for me now for a week without "out of memory".
Tweak 2 settings in the build.prop (Tip: Use also kernel adiutor) :
Set davlik.vm.heapsize from 512m to 256m (this makes the difference)
Set davlik.vm.heapgrowthlimit from 192m to 128m (this is perhaps not neccesarry, 64 worked also fine)
After restart, I got 1.15 GB free space on the home app. Checked with CPU Memory widget). The memory report from android settings is not real time.
After loadinng rr3, memory goes down to 580mb.
Playing the biggest course (lemans 10 laps), memory goes down to 430mb free.
Ending the 10 lapper, memory recycles to 580mb.
===> Problem solved.