Did you search through the other issues to make sure that this issue has not been already reported? Did you look at the FAQ http://openetna.com/openetna/test ?
What steps will reproduce the problem? 1. Use the phone without turning it off for more then 24 hours 2. 3.
What is the expected output? What do you see instead? Expected: Phone continues to operate normally. Instead: Phone becomes sluggish and slow, to the point where the keyboard has about 5 seconds of lag. At this time if I check avail memory its around 40-50M. A reboot puts me back at 80M and the speed is instantly back.
What version of the boot.img and system.img are you using? This started in rc3
Can you provide logcat output during that error? It would be massive and require me not to unplug my phone for a day..
Please provide any additional information below. I am only assuming that it is a memory leak, I have no hard proof except that has happened to me twice since rc3 has been released... I am wondering if anyone else has this issue.. upgrading to a nightly build now and will post if same situation occurs. (I never reboot unless I must and have had the phone running more then 3 days on previous builds and never seen this amount of sluggishness.
Comment #1
Posted on Nov 8, 2010 by Swift HippoI would bet you installed some third party apps which is using your memory. In fact, if i'm not wrong, Froyo handles the memory very well and has some very effective mechanism to free up memory. You said that when you check the available memory, it says 40-50M. If you can achieve to go under 10M then i would think it's a memory leak.
But it just looks like the processor is being overloaded :/ Anyway using a task manager may help a little (but google officialy says that these are useless on Froyo). Everybody has some slow downs from time to time...
Comment #2
Posted on Nov 8, 2010 by Quick Rhinothis problem happened to me too, i think... after 3 days of NO reboot i have alarm clock not working because the time doesn't update every minute...
Comment #3
Posted on Nov 8, 2010 by Swift HippoOk. Maybe i'm wrong. Do you mind providing a logcat after a long time with no reboot ? We would see what is being done on the memory or what app is currently using your device.
Thanks !
Comment #4
Posted on Nov 8, 2010 by Quick Rhinoi've flashed new build moments ago, if the issue persists i'll post a logcat tomorrow!...
Comment #5
Posted on Nov 10, 2010 by Quick CamelI don't like new so i changed the status to NeedInfo. We are waiting for your logcat if you still have this problem andreabelli93
Comment #6
Posted on Nov 26, 2010 by Grumpy WombatI have this probleme too, my phone is very slow after some time, I think it's because some application lauches alone :/, I think it is the worst on openetna, but thank for you very good work !!
Comment #7
Posted on Nov 26, 2010 by Quick RhinoTry to install OsMonitor from the market, and see what apps are eating your CPU/RAM. U can also add a nice notification icon on the upper bar to watch the cpu usage.
I noticed that sometimes the web browser refuses to go sleep, and start using the cpu.
Comment #8
Posted on Nov 26, 2010 by Happy CamelI'm using advanced task killer and i have the same issue. i can get almost 90M free when first powered on. as time marches on, it drops and even with killing all tasks, i only have about 60M free. when i check to see whats using the battery most, its almost always the display but I know thats not using 30M of memory.
Comment #9
Posted on Feb 7, 2011 by Massive Dogis this still an issue?
Comment #10
Posted on Feb 9, 2011 by Massive DogClosing this issue as it refers an old version and did not have more updates.
Comment #11
Posted on Mar 8, 2011 by Happy ElephantI'm experiencing this same issue on 6.3rc7. After reboot I have 100Mb of free memory, after 1 or 2 days I can't get over 30Mb even killing everything with ATK. I realized about this when LauncherPro was giving FCs after any application opened.
Comment #12
Posted on Mar 8, 2011 by Massive Dog(No comment was entered for this change.)
Comment #13
Posted on Mar 8, 2011 by Happy ElephantOk, I'm going to reboot and get a logcat, 2 days later I'm going to get a second one and post them here.
Comment #14
Posted on Mar 10, 2011 by Happy ElephantDone. Here are the logcats. The first one after reboot gives 100MB of free memory. Two days later only I have 24MB of free memory with ADW restarting after every application I run (Seesmic in this case). Thanks for change the status and wait. I hope this helps.
Comment #15
Posted on Mar 10, 2011 by Swift HorseI originally reported this issue way back in rc3.. since then I have no clue how your phone can even go 2 full days without a reboot.. I have my phone lockup at least once a day.. does anyone else have this?? I use CPU Tuner, however just for the battery life extension (and it works amazingly) I have the cpu freq set to 595 for all profiles..(this is our default right?)
ALSO is there no way to calibrate our screen in the current version?
Comment #16
Posted on Mar 10, 2011 by Happy ElephantI don't have many lockups (probably one every 4 or 5 days I guess). I'm experiencing launcher restarting since 6.1rc5 probably but not so often then as now. Maybe you should provide some logcats too.
Screen calibration? I'm not pretty sure if that feature exists even on stock Cupcake.
Comment #17
Posted on May 4, 2011 by Helpful KangarooI installed the rc7 5 days ago and noticed that my phone goes into an unrecoverable freeze every 24-26 hours. I have not installed many apps besides the stock system (rc7) no task killers and similar. Maybe it has something to do with this issue.
Comment #18
Posted on May 5, 2011 by Quick MonkeyMine does last for weeks, but while using setCPU freezes often. So I would recommend testing without setCPU (or setCPU min=max=528Mhz)
Comment #19
Posted on May 13, 2011 by Swift Horseive had mine crash 3x today alone. I dont use setcpu or cpu tuner anymore. Sometimes it lasts for weeks. Something is wrong and I dont think its related to memory leaks. 3x in one day.. all I do is text basically. Does noone else have the problem? have updates on this completely stopped?
Status: NeedInfo
Labels:
Type-Defect
Priority-Medium