I use advanced task killer to keep things under control, and handcent in favor of the stock msg app. I notice that I have upwards of 80mb free memory after killing tasks after a reboot. Over the course of the day, with only my ignored apps running, that number shrinks to 48-50mb. Does that indicate a leak somewhere?
View 6 Replies
I think I've got a memory leak somewhere. I'm running DC v2.08.1 and I've got a low memory error. It may be because I flashed from Fresh 2.0D to this without wiping, but I'm not sure. Does anyone have any ideas how I can figure it out without wiping. I'd really rather not wipe again.
View 3 Replies View RelatedI wiped and flashed fresh 2.1.2 and initially it gave me about 90mb free after a clean and fresh install. After I installed all my apps I still had about 70mb left. But during the past few days I've noticed the internal memory slowly decreasing or leaking even though I haven't downloaded anything new. I've lost about 10mb by doing absolutely nothing.
View 6 Replies View RelatedIn Taskiller the amount of free memory is showing between 90-105mb. Is this normal? I have deleted text messages, cleared cache, deleting emails from inbox and trash etc. I going to get rid of a few apps too, but its a bummer if I cant have many apps due to it affecting memory!
Also I understand that if flash it with the Modaco custom ROM. I can create a swap partition, does this help a lot? Also would I lose quite a lot of the HTC Hero features such as Sense UI for example if I flash it with Modaco?
Has Anyone tried installing the first RUU leak after installing the Official release on their hero. Would this work to get root back? Just a thought. I have installed the official release, and I am very happy with it, and I will be moving to the EVO in June. Just wondering about this possibillity for those who want to go back to root.
View 1 Replies View RelatedWas wondering if you can root your phone after installing the leaked 2.1 RUU? And if you can, is it the same procedure and codes?
View 26 Replies View RelatedLatest HTC Hero 2.1 ROM leak [with how-to video] | DroidDog Android Blog
check it out. I am running 2.1 without rooting and took about 5 minutes.
If you guys are still suffering from this issue upgrade to the Maintenance Release, it fixes it for the most part, except for the occasional failure to connect. No ROM leak though.During the past few weeks my my Hero has been exhibiting signs of a ROM memory leak. It led to not being able to receive SMS messages even after hard resetting the phone. See these threads for that issue.
View 36 Replies View RelatedI had just posted on these forums about my phone not sleeping. That was with 1.5. The next day, I put the 2.1 leak on my phone. And that seemed to fix the problem and the phone's up time was far greater than its awake time. A couple days later - and once again, the up and awake times are the exact same and my battery seems to be going down faster. I've been poking around for any other posts with the same issue - but haven't found any.
View 2 Replies View RelatedHow to download the new 2.1 leak to my hero? This is not only for me their are a couple of people out there that all.
View 3 Replies View RelatedFinally. I guess no need to download the official?
View 1 Replies View RelatedI'm in the process of re-installing my apps, trying to find a culprit that might be keeping my phone awake - and was wondering if anyone else thinks they've found some guilty parties. So far the only app I've installed is the HTC Battery widget. Everything else is stock from the 2.1 leak. I'll probably put the official rom on there eventually (especially if I still can't fix the awake problem), but since it doesn't seem to be any different, I'm not in a hurry. Now, my phone seems to be going right to sleep when I press the end button. My awake time is a fraction of the up time.I just started using the Seido extended life battery (1750 I think), and I've put the phone through some heavy use - a one hour phone call using bluetooth, several other shorter calls, some instant messaging, lots of texts, some internet use and camera use. And I've not charged it since leaving the house. So far, I'm at 57% - which far exceeds anything I've experienced before 2.1, and before the extended battery. Right now I'm looking at all-day use with the phone - which is ideal.My issue is that I want to prevent the phone from staying awake again. 100% awake time always seems to cut my battery life in half, if not more. There doesn't seem to be a clean way for me to do this. Even after I uninstall all of my applications, the problem doesn't seem to correct itself until I restore the phone to factory settings. For this reason - it's hard to pin down which application (or setting) might be the culprit.
View 6 Replies View RelatedI have to tell you, I am getting hella better battery life out of the leaked update versus 1.5 on the Hero. I am sitting at 1.5 days since last charged, and am at 50% battery. On the old firmware, I am possibly close to dead at this point. I wonder if the native support in 2.1 for the Sprint network is making that large a difference, or if wiping the phone somehow purged an energy guzzler from my machine. Whatever it is, I wondered if anyone else who updated is noticing a similar gain in battery longevity.
View 8 Replies View RelatedLooks like it will be a few weeks before Sprint pushes a "bug free" 2.1. I install the leak via RUU exe file. Phone is trashed, completely useless as a phone, have to pull the battery reboot and quickly make a call before it locks up or crashes. Can you guys tell me how to roll back, hack, crack, smack, or otherwise install a working ROM?
View 35 Replies View RelatedIf I create and release multiple AudioTrack objects, the GREF count continually increases which eventually causes an application crash. Even with a forced garbage collection, I end up with the same high GREF count at the end of the loop.In my application, I continuously create AudioTracks from variable lenght buffers.I guess I can try and use a fixed size pool of AudioTracks each with a buffer large enough to fit my longest sound, and try and reuse them.Is there a better/correct way to completely clear resources used by an AudioTrack?
View 5 Replies View RelatedI have been banging away at this one for weeks and I feel like I have exhausted my research capabilities. I am hoping that someone will see my error in the code posted below. The code is completely functional doing everything I need, but there is a major memory leak. When I try to track memory in the DDMS, the VM Heap tells me that my object count is relatively stable and the used memory is also relatively stable (it comes back down to a similar value after each GC after panning).
When I look at the memory pie chart, the free memory loses over 1meg of capacity with each map pan (overlay reload) and the Unknown memory grows. I have not found anything with the allocation tracker. Functional Summary: I load overlays onto a map based on data I get from polling my server. When I pan the map far enough I clear the overlays and load new ones.
MapFrontEnd.java (snippets): //header info private List<Overlay> overlays;
//in onCreate overlays = mapView.getOverlays();
// here I attempt to fully clean up my old Overlays for (Overlay i : overlays) {
if (i instanceof ParcelOverlay) ((ParcelOverlay) i).cleanUp(); }
In my app, I'm fetching data via HTTP and use the response string to create an ArrayList of objects. So what I'm doing once I get the response is:
String[] fields = response.split("<field>");
and use the field[] values like this:
ArrayList<Movie> movies = new ArrayList<Movie>(); for (int row = 1; row < fields.length; row += 9) { movies.add(new Movie(fields[row], fields[row + 1], ..., fields[row + 8]);
}
I have an application that uses a Service and some list activities. When the activities are opened, I can see the heap usage increase in DDMS. When the activities are closed, the heap usage decreases slightly. The service is still running in the background at this point. If the activity is started again by re-running the application and then closed, the heap usage increases again then decreases, but never returns to the original level before the activity was first opened. If it repeatedly (10-15 times) open the activity then close the activity, the heap size (both MB and # Objects) balloons!
I'd expect ListActivity's onDestroy to take care of itself when it gets destroyed. What am I missing with this? Am I using ListActivity incorrectly?
If I examine the heap using MAT, I see 10-15 ListView objects. Unfortunately, I've not got much experience with MAT, but I think it means that the instances are still hanging around rather than being garbage collected. Can anyone explain what's going on?
A test app similar to my real code is below. Create a new android application, add this to the manifest:
CODE:................
When I first boot up the phone and check the memory (after shutting down all the apps I don't want running) I notice my phone has about 220-250 MB free after leaving the phone on for about 2-3 hours, with no activity on my part, that number gets smaller and smaller. I just rebooted my phone again because it was down to 125 MB free with no applications running.
Also, "Android System" is consuming 65% of my battery life. I realize that number is inaccurate after a fresh reboot so I played with the phone for a good 4 hours running apps and such, so that I could get a good test of how much the OS is eating up in comparison to other apps. 65% is a bit much no?
I am experiencing a memory / resource leak on a T-Mobile G1 device with my application. I installed the "Task Manager" application from Android market and my memory usage is not monotonically increasing. It stays relatively flat over time. Furthermore, none of the other processes are chewing up tons of memory either (really, I can get into this state with just my app running). I am not experiencing this problem on any of the other Android phones (including Eris, Hero, and Droid).
The interesting thing is that if I kill my application, the phone is *still* very slow and sluggish. The only thing that seems to be able to get me out of this situation is a battery pull. If I run my application for about 3 hours, the phone starts to become very sluggish. Even simple operations like hitting the "home" button take many seconds. I'm not sure what to do at this point and am wondering where I can go from here.
In my app activity A creates activity B, however when the back key is pressed it goes back to activity A. This is a simplified version of my application. I would expect memory to be reclaimed when going back to Activity A. Going to activity B allocates more memory. I am using dumpsys meminfo to get the allocated kbs. How can I easily tell what memory is creeping? I do not keep any references to activity B. I know about the ddms allocation tracker, but wondering if there is a more better tool to figure this out.
View 2 Replies View RelatedI'm parsing a document with large text field. In my characters section I am using StringBuilder
currentStory.append(ch, start, length);
then in my endElement i'm assigning it to the appropriate field on my object.
if (name.equals(tagDesc)) { inDesc = false;
if (currentItem != null ) { currentItem.setSummaryText(currentStory.toString());
} currentStory.setLength(0);
} setSummary is public void setSummaryText(String text) { Story = text;
}
And I am running out of memory. If I change setSummaryText to something completely weird like this:
public void setSummaryText(String text) { char[] local = text.toString(
) Story = new String(local);
}
I am fine. I just cant figure out where I am holding that reference?
Story is a member var of this object initialized with "";
Note - assigning to local String variable instead of char[] - fails as well.
I know that's a subject which was discuss a lot of time and I try to find a solution since more than 6 day for the memory leak which appears in my application.
I've read this page: http://www.curious-creature.org/2008/12/18/avoid-memory-leaks-on-andr...
So, I don't use static member fields, I always use recycle() and I don't use inner class.
My application use a gallery and some bitmap. I use finalize to monitor garbage collection in each class of my application: protected void finalize() throws Throwable {try {Log.d("FINALIZE", this.toString());} finally {super.finalize();}
After several hours of searching for the cause of a Out Of Memory Error, I found a wierd problem with Strings. To keep it simple, trimmed it down to something like this:
ArrayList<String> someStringList = new ArrayList<String>(1000);
for (int i=0; i<1000; i++) {
String someBigString = new String(new char[100000]);
String someSmallString = someBigString.substring(0,1);
someStringList.add(someSmallString);
}
There appears to be a leak when using PhoneStateListeners. The following code simply reigsters in onResume and unregisters in onPause a PhoneStateListener. Repeatedly launch then press BACK (so the app is finished & onDestory is called before the next launch) and the number of activities reported by meminfo will equal the number of launches. For instance, here is the output I get after launching (and finishing) 11 times in sequence:
dumpsys meminfo com.example.leak Currently running services: meminfo
DUMP OF SERVICE meminfo: Applications Memory Usage (kB): Uptime: 12204322 Realtime: 12204322
** MEMINFO in pid 1358 [com.example.leak] ** native dalvik other total size:
2648 3079 N/A 5727
allocated: 2604 2254 N/A 4858
free: 43 825 N/A 868
(Pss): 913 1305 1475 3693
(shared dirty): 1080 3864 568 5512
(priv dirty): 808 936 1056 2800
Objects Views: 77
ViewRoots: AppContexts: 12
Activities: 11
Assets: 2
AssetManagers: 2
Local Binders: 36
Proxy Binders: 21
Death Recipients: 0
OpenSSL Sockets: 0
SQL heap: 0
dbFiles: 0
numPagers: 0
inactivePageKB: 0
activePageKB: 0 #
Without the PhoneStateListener, the number of activities is always 1 no matter how many times the app is launched & finished. So, am I doing anything wrong here? Or is this a bug in the TelephonyManager?
Here's the code package com.example.leak;
import android.app.Activity; import android.content.Context; import android.os.Bundle; import android.telephony.PhoneStateListener; import android.telephony.TelephonyManager; import android.util.Log;
public class LeakExample extends Activity {
private class MyPhoneStateListener extends PhoneStateListener {
@Override public void onCallStateChanged(int state, String incomingNumber) {
if ((state == TelephonyManager.CALL_STATE_RINGING)
|| (state == TelephonyManager.CALL_STATE_OFFHOOK)) {
LeakExample.this.finish();
} } }
MyPhoneStateListener phone_listener = new MyPhoneStateListener();
TelephonyManager telMgr ;
@Override public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
telMgr = (TelephonyManager) getSystemService (Context.TELEPHONY_SERVICE);
} @Override protected void onPause() { super.onPause();
telMgr.listen(phone_listener, PhoneStateListener.LISTEN_NONE);
} @Override protected void onResume() { super.onResume();
telMgr.listen(phone_listener, PhoneStateListener.LISTEN_CALL_STATE);
} @Override protected void onDestroy() { super.onDestroy();
Log.v("LEAK EXAMPLE", "onDestory");
}
Every since I updated launcher pro I get the updated service app running. Anyone else experiencing this problem?
LauncherPro Forum View topic - Newest version 7.7.1 memory leak?
I've been rooted and running roms for a while, starting when Pete was just coming out with his first Bugless Beauties. I've been through a bunch of ROMS, and installed them pretty much all the ways you can. Lately I've been on DroidMod 1.0. I had originally installed it without flashing /data. However, I noticed that my memory was getting pretty low, down to about 90 MB according to mini info widget. So I re-flashed, but this time I allowed it to wipe /data. Wow, what a difference. Immediately, I was up to almost 180M of memory! But it's been dropping steadily since then. I'm down to about 145M and that's with not loading very many new programs. I'm very conscientious about deleting cache, etc.
View 8 Replies View RelatedI don't know if it's just me, but my HTC Magic becomes very laggy after few minutes of use. Cleaning the Market and Navigator's cache and stopping all background tasks with TaskPanel Lite helps, but then after few minutes of use it becomes extremely laggy again. Don't know what to do.
Note: When I clear all the background tasks and cache, TaskPanel indicates that the phone available memory is from 20 -> 24mb (seems to be to few) but after some minutes of use it goes to 3 -> 5 mb of available memory.
I upgraded from 1.5 to the "new" 2.1 leak.so far it's snappier, but I've noticed a couple anomolies. I'm hoping that someone here can enlighten me.If I do a fresh reboot then use Advanced Task Killer to kill all the apps that run on startup, I can usually get around 104 MB of free memory.But, for whatever reason, it always seems to trickle down to about 30 to 40 on any given day.I have to run ATK again just to get it back up to around 70 MB free.Is there a memory leak? Or is this caused by random apps running in the background eating memory?There are some, like MP3 Store, Market, and Voice Dialer that seem to run even after I kill them with ATK.Next question, and kind of an observation...I have a Kia Forte Koup with built in Bluetooth.The Eris syncs up just fine and I can voice dial. I've noticed that others have said that the Eris wouldn't let you voice-dial with Bluetooth, but mine does.It worked with 1.5, too. My question is whether there's a way to increase the volume further.when I had 1.5 I could easily hear calls over bluetooth, but 2.1 is much quieter. I've got the "Bluetooth In-Call Volume" maxed out, and my volume in my car is almost maxed, but it's still quieter than it used to be.Any ideas?
View 10 Replies View RelatedI am using a simple frame animation and when I exit and reenter my activity the activity is still referenced in memory.
//This is a sample activity I created to simulate the problem public class MemoryLeakActivity extends Activity {
@Override public void onCreate(final Bundle savedInstanceState) super.onCreate(savedInstanceState);
} @Override public boolean onKeyDown(final int keyCode, final KeyEvent event) {
final Intent i = new Intent(MemoryLeakActivity.this, LeakyActivy.class);
startActivity(i); return super.onKeyDown(keyCode, event);
} }