Hi!
I have noticed that the size of the application fluctuates frequently. From 300MB it goes up to 750 and then goes down again. What happens?
Related
Hello good people of XDA, I am having a bit of an annoying issue with my Cyanogenmod 7.1 "stable" install on my Evo 4G. Tiamat 4.1.0 SBC+ Kernel.
When I run a gps related application like Ulysse speedometer, Google Maps and Navigation, after a seemingly random amount of time the phone crashes and reboots itself. The time that I can use the app may be a few seconds to a few minutes and I havent noticed anything that would help determine the timing issue.
I have been doing a little testing and while running logcat on my PC via ADB, I have pulled the last events that occur immediately before the crash. It seems to me that the issue is more/only likely to occur when the phone is also not connected to a wifi network. Everything works fine when using GPS while connected over wifi.
Is anybody interested in reading through the end of my log file? How should I post it?
Please, any help at all?
sntmods said:
Please, any help at all?
Click to expand...
Click to collapse
I've been having the same problem as you and I think I've figured out a fix for it. I'm on Deck's 1.3 stable (which is essentially CM7.1) with Tiamat 4.1.0 SBC, using the smartass governor (the original one) with a CPU frequency range from 128 MHz to 768 MHz, and undervolted by 100 mV.
I've only encountered the issue sporadically and it's only occurred when using Google Maps or Navigation. I would be using Maps and moving the map around a lot, rotating it, or zooming in and out and all of a sudden the screen would freeze and the phone would reboot after 10 seconds or so. I figured out that I could reproduce the problem by opening up a bunch of apps to get the free memory (RAM) down to about 100 MB, open up Google Music and start streaming a song on the handset speaker, then open up Maps and just move around the map a lot; after less than a minute of doing this, the screen would freeze and the phone would reboot.
I tried uninstalling and reinstalling Maps; wiping the cache, dalvik cache, and fixing permissions; reverting to an older version of Maps (5.10); reversing the undervolting; changing governors; and changing the CPU frequency range; but none of these things fixed the problem.
I noticed that if I tried the Music and Maps crash technique when there was more free RAM (say 150 - 250 MB free), it wouldn't work, so I figured the problem probably had to do with the apps in use not having enough available RAM to operate properly and the default values that Android uses to kill idle apps was set too low. Fortunately, I remembered about Autokiller Memory Optimizer, which allows you to set those values, so that you always have above a certain level of free RAM. First, I tried the “Aggressive” preset (82, 90, 98), which didn’t fix the problem, so I then tried the “Extreme” preset (150, 160, 170) and that fixed it (for a full explanation of what the numbers mean and how the app works, see the Autokiller Memory Optimizer). I tried several different combinations of values between the Aggressive and Extreme presets and finally settled on Hidden app: 110, Content provider: 120, Empty app: 130. I was able to use lower values and still prevent the crash/reboot issue, but I figured I should leave a little buffer room to be safe and the 110, 120, 130 combo seemed low enough to prevent idle apps from being unnecessarily killed.
So, I’m not exactly sure what the root cause of the problem is, but Autokiller Memory Optimizer seems to be a nice workaround to fix the problem.
Well after testing this workaround for some time now, I can say that it doesn't prevent the reboots completely, but it does seem to have decreased their frequency, such that it's only happened one or two times since I started using it. I tried changing the cutoff values for when certain types of apps are killed, but eventually returned to the original levels I went with (Hidden app: 110, Content provider: 120, Empty app: 130) as they seemed to work the best (the one or two reboots that did happened, occurred when I was experimenting with the values).
Not only killed my battery while downloading the needed DLC.
On top of that, my phone was boiling to the touch! And, after all that hassle.....the game lags! Didn't expect bad performance at all
Alright, just to add...
For some ODD reason, the CPU usage on this phone spikes HARD It's usually bouncing around 40-70%, that would explain the stutter in some games. Now to figure out how to fix this problem...
bmxant said:
Not only killed my battery while downloading the needed DLC.
On top of that, my phone was boiling to the touch! And, after all that hassle.....the game lags! Didn't expect bad performance at all
Click to expand...
Click to collapse
I've noticed that this phone stutters randomly when switching from app to app sometimes. I notice it happen when I am playing music via Poweramp, and then switch to maps, n when it loads the map, the song stutters hardly. I dont mean it skips a beat or something, it actually breaks the song and make it sound mechanical for a second before resuming the song properly.
Now I don't know if it's the phone itself, an app installed (maybe ram manager?) or just the lack of available Ram on the phone that is causing this, but it's sad and worrying to see a dual core 1.5Ghz cpu stutter under a light load switch. Anybody notice that the free Ram left on this phone is generally alarmingly low, around 130MB left out of 783MB? What is eating up so much Ram on this phone? When I was on the Atrix, I generally still have 300-400MB left free to be used (I dont recall whether it actually has the full 1000MB available or also 783MB though) and I never experience stuttering.
Is this resolution really tasking the CPU? or is it because it has to render these apps to fit properly in the 720P resolution?
p.s. Another game that lags: Jelly Defense, when you have a lot of enemies flowing down the path, it starts getting choppy.
As I mentioned, I'm pretty sure it's the CPU spikes doing it. I have around 400mb free of ram also. I know Dungeon Defenders lags on the Galaxy Nexus as well, but I'm pretty sure it doesn't have as many problems. Then again, it was built on ICS
Grab Memory Booster Lite and you can monitor how much RAM is being used as well as the CPU % for each task
Is Dungeon Defenders working for everyone else? I can run it for about 30 seconds and then it just closes. No force close message or anything, it just freezes for a second or two and then disappears.
aquariuz23 said:
Anybody notice that the free Ram left on this phone is generally alarmingly low, around 130MB left out of 783MB?
Click to expand...
Click to collapse
after a thorough freezing, go launcher shows me at ~580M free on a fresh reboot and usually running low 500M free mem at any time, running 510M free right this second. this is with RAM manager, which by my estimates accounts for 5% in that #
scott0 said:
after a thorough freezing, go launcher shows me at ~580M free on a fresh reboot and usually running low 500M free mem at any time, running 510M free right this second. this is with RAM manager, which by my estimates accounts for 5% in that #
Click to expand...
Click to collapse
Do you experience any lags on Dungeon Defenders (if you have it)? Or do some of your games stutter like bmxant's?
Mine sure as hell does, I can tell when I open texting from notifications, and when I go to home, the keyboard stays there for like 5 seconds, I have like so much running like Auto Memory Optimizer SetCPU max 1024 and min 1024, and SD Card Booster. and finally I run smooth <3 wbu?
Hi so my phone for my galaxy s3 sucks! My RAM in the background just keeps building up. On average my RAM is usually at 0.94 GB or 1.01 GB when i close all the apps in the background. Why is this? Sometimes it goes to 584 MB when i press "Clear background RAM" and then 10 seconds later it jumps to 900 MB. My battery life also sucks. I turn on power saver and reduce auto sync. I left my phone on the table one night when it was at 100% and 30 minutes later it was down to 81%. I DIDNT EVEN RUN ANYTHING!!! What do i do? I dont have many apps installed on my phone either. i have about 15 GB of space left.
rydmen said:
Hi so my phone for my galaxy s3 sucks! My RAM in the background just keeps building up. On average my RAM is usually at 0.94 GB or 1.01 GB when i close all the apps in the background. Why is this? Sometimes it goes to 584 MB when i press "Clear background RAM" and then 10 seconds later it jumps to 900 MB. My battery life also sucks. I turn on power saver and reduce auto sync. I left my phone on the table one night when it was at 100% and 30 minutes later it was down to 81%. I DIDNT EVEN RUN ANYTHING!!! What do i do? I dont have many apps installed on my phone either. i have about 15 GB of space left.
Click to expand...
Click to collapse
It sounds like some sort of rogue app causing this. My suggestion to you is that you either try a custom ROM or you try factory resetting your phone. A good way to tell what exactly is eating your battery is to purchase an app called better battery stats from the play store and that will give you an extremely detailed listing of what is eating your battery. Best of luck.
So basically the issue is that whenever I close out of an app it takes roughly 2-4 seconds for my app icons, widgets, etc to load on my homescreen. This is very annoying, and I've noticed that the ASUS Launcher app is always a cached process in my app manager. Is there a way to force it to stay running instead of caching?
I have the 4GB version of this phone and RAM is never an issue, so I can't fathom why it's deciding to cache this, an 83MB process.