|
Memory Watcher Reveals the Inner Working of Android Device
Therefore, I wrote the Memory Watcher app to confirm whether that was the case. It was. As soon as I had Memory Watch ran in the background of my app, it reported that Android is low on memory. Memory Watcher helped me determine the source of the problem. And I was able to quickly create solutions based on the understanding. Now I keep Memory Watcher running all the time. It sends me notifications and provides insight to system operations and its interaction with activities/services. Chieh Cheng
Did your message disappear? Read the Forums FAQ. Add Comment
TrackBackTrackBack only accepted from WebSite-X Suite web sites. Do not submit TrackBacks from other sites.
No TrackBacks yet. TrackBack can be used to link this thread to your weblog, or link your weblog to this thread. In addition, TrackBack can be used as a form of remote commenting. Rather than posting the comment directly on this thread, you can posts it on your own weblog. Then have your weblog sends a TrackBack ping to the TrackBack URL, so that your post would show up here. Messages, files, and images copyright by respective owners. |
Products
|
Services
32 Users Online
Get Our
|
|
Copyright © 1996 - 2024. All Rights Reserved. |
|
Related Links
|
TrackBack
Recently, while developing an Android app, I found that it gets shut down on a regular basis. Yet, there was no "force close" message with each one of these shut downs. Baffled for days, it finally occurred to me that maybe the Android operating system closed my app, rather than the app crashing itself. The only reason, I can think of, why Android would shut the app down is that the device is low on memory.
