My phone reboots 1-2 times a month because of system error/breakdown (I do not know the exact message, I use it in Hungarian). It happens randomly. I couldn't identify any event that always done before the reboot. I'm not good at android and linux, but last time I checked the log before sending the report to HTC and I found this.
SATAKE TRACE
java.lang.OutOfMemoryError; bitmap size exceeds VM budget(Heap Size=17031KB, Allocated=12418KB, Bitmap Size=15897KB)
and
at the and of SYSTEM LOG
07-27 21:52:59.863 I/am_crash(1337):
[1337,system,-1,java.lang.OutOfMemoryError, bitmap size exceeds VM budget(Heap Size=17031KB, Allocated=12418KB, Bitmap Size=15897KB), Bitmap.java,-2]
Could anybody help me? Is it a problem of app or android? Or a hardware problem?
Related
Log cat dumps it. However it's always being collected. Round buffer or not, it has to be slowing down the processor.
How does one send it to a null file?
At least I think it must be a resource leak. I have multiple WM6 devices that all behave the same way when my application is run. After a while, maybe 15 hours, they gradually deteriorate and refuse to start other applications. At first, it will just be an application like Opera that will not start. Eventually, things like File Explorer will also not start. When I say they won't start, I mean that I get the "not signed with a trusted certificate or one of its components cannot be found" message.
My first thought was that there was a memory leak, but according to the output of GlobalMemoryStatus, the system's memory use is not increasing over time. Then I thought that it might be storage space since I'm generating a big log file. But the storage space still sits above 60MB when this happens.
Restarting the device gets everything back to normal. So far, this is what I know:
1. I'm using the RIL. I noticed today that after about 12 hours, I stop getting RIL notifications.
2. I'm monitoring memory with GlobalMemoryStatus, but the available physical memory doesn't seem to be decreasing over time
3. The thread count remains constant for the life of the application
4. My storage space is decreasing, but there is still over 60MB available when everything starts to go wrong
5. In the end, the device winds up with the screen lock on, even though it is not configured.
It seems that there must be some kind of resource leak. The only other thing I can think of are kernel resources. I tried to rule out things like event handles through static code inspection, but maybe there's something I'm missing.
Does anyone have any suggestions as to how I would troubleshoot this further? I'm using VS2008 and a Tilt2 and an HTC Imagio (it happens on other devices as well).
I tracked this down to a registry handle leak. What bothers me is that I had to do it by static code inspection. I just looked for things like CreateEvent, RegOpenKeyEx, etc.
Since this didn't seem to show up as consumed physical memory, does anyone have any methods for inspecting kernel resource consumption on Windows Mobile? Do I have to rely on KITL and Platform Builder with the emulator? I'm hoping that there's some way I diagnose this kind of problem with a real device. From my perspective, the device just started to fail and there were no external indicators to warn me of the impending failure.
sbaker25 said:
I tracked this down to a registry handle leak. What bothers me is that I had to do it by static code inspection. I just looked for things like CreateEvent, RegOpenKeyEx, etc.
Since this didn't seem to show up as consumed physical memory, does anyone have any methods for inspecting kernel resource consumption on Windows Mobile? Do I have to rely on KITL and Platform Builder with the emulator? I'm hoping that there's some way I diagnose this kind of problem with a real device. From my perspective, the device just started to fail and there were no external indicators to warn me of the impending failure.
Click to expand...
Click to collapse
hi!can somebody to help me?
i have asus p535 and i reset "start""settings"default settings"and i lost all from device.after apear align screen and remain like this
i think i have to install window mobile.can you tell me step by step how?
10000 thanks
Sorry, accidental re-post. Don't think I can delete it altogether...
HI there,
I have written an app and on some devices, using the app freezes the system. My main problem is, that I do not get any log information, because as soon as the device is frozen, logging completely stops and obviously the crash-reports normally would be generated after the crash, which does not work, because the device is frozen.
I have attached the device to my laptop via adb (via USB) and logcat everything, but the logging just stops as the device freezes. I have also checked all possible log locations (/data/tombstones, /data/anr and what else is in /data) and could not find anything.
Since the app crashes only on about 10% of all devices (the devices are identical and have the same firmware) I need to test the app on the device and cannot use the emulator. However if the app crashes, I can relieable reproduce the crash using adb monkey. On the other 90% adb monkey won't crash the device.
Is there anything else I can log / test / check? Is there a way to get a memory dump, once the device is frozen? Any other idea how I can get hold of any information?
Although I don't think this is relevant: The device is a XORO 9718DR tablet and the device is rooted. The app is written by myself and not available in the market. It mainly uses only Buttons, TextView, ImageView, HttpClientConnection, Threads, AsyncTasks and other "normal" Android stuff. It even does not use the webview.
ToBe_HH said:
HI there,
I have written an app and on some devices, using the app freezes the system. My main problem is, that I do not get any log information, because as soon as the device is frozen, logging completely stops and obviously the crash-reports normally would be generated after the crash, which does not work, because the device is frozen.
I have attached the device to my laptop via adb (via USB) and logcat everything, but the logging just stops as the device freezes. I have also checked all possible log locations (/data/tombstones, /data/anr and what else is in /data) and could not find anything.
Since the app crashes only on about 10% of all devices (the devices are identical and have the same firmware) I need to test the app on the device and cannot use the emulator. However if the app crashes, I can relieable reproduce the crash using adb monkey. On the other 90% adb monkey won't crash the device.
Is there anything else I can log / test / check? Is there a way to get a memory dump, once the device is frozen? Any other idea how I can get hold of any information?
Although I don't think this is relevant: The device is a XORO 9718DR tablet and the device is rooted. The app is written by myself and not available in the market. It mainly uses only Buttons, TextView, ImageView, HttpClientConnection, Threads, AsyncTasks and other "normal" Android stuff. It even does not use the webview.
Click to expand...
Click to collapse
What you are saying is an App Not Responding situation where the app does too much work on the Main Thread causing a UI Freeze. You could analyse the ANR Trace file from your phone... I'm not quite sure ... But ... You could use the Below links to know more in detail :
investigating an ANR
How to debug Android ANR
Interpreting an ANR stack trace
No ANR
Thank you niranjan94 for your reply. But by "freeze" I mean that the complete device freezes. It is not accessible via USB or network any more. All apps are frozen (e.g. I had an app in the background, which recorded the logcat and that app stopped the same second the device freezes). Therefore there is no ANR trace. Unfortunately. :crying:
BTW: There is also no tombstone in /data/tombstones....
I compiled Android from the source Nvidia made available on their website and, while the process went smoothly, after flashing the images to the device I experienced a large number of issues:
1. The tablet does not go to sleep (shown as Awake in the Battery settings) while not plugged in, leading to fast battery drain. If plugged in, the device is shown as not awake.
2. While not connected to Wifi, the screen would become completely unresponsive to touch input, after turning on the device (if it previously was on stand-by).
3. A lot of error messages of missing libraries and general files are shown in Logcat. A few examples:
E/phs:governor(14217): failed to load "libgov_gpucompute.so": No such file or directory
E/SoundPool(913): error loading /system/media/audio/ui/Lock.ogg
E/ConnectivityService(834): Unexpected mtu value: [email protected]
E/TLK_Daemon(176): IOCTL_FILE_NEW_REQ returned 61
E/wpa_supplicant(1435): wpa_driver_nl80211_driver_cmd: failed to issue private commands
I did scavange libgov_gpucompute.so from the factory image, but that did not fix any of the symptoms; the error message disappeared.
I built every version Nvidia made available and had the same results.
The recovery image does not suffer from these issues.
Any suggestion on how to get a handle on this would be greatly appreciated.
Hi all. I have Nokia 8.1 for a few months now. Updated to Android 10 immediately and it has been rock stable. Until today.
At about 11am I heard an incoming message notification but was busy and decided to look at it later.
At 11:55am I picked the phone but could not wake it up - tapping didn't work, fingerprint didn't work. Black screen. So I long-pressed the power button and it booted up.
It is working fine since but I'm somewhat concerned about the issue.
I collected a zip log file through "adb bugreport" command.
As I understand, it's tricky to find the cause after the reboot because all log files are generated fresh after boot. I looked in \FS\data\tombstones folders and found three records there, all complaining about the following issue:
Code:
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'FORTIFY: %n not allowed on Android'
But they are almost a month old and I don't remember anything weird happening at that time; except maybe some Android system update and manual reboot.
Is there any place in that log zip or somewhere else on the device (without root) where I could find some info about what happened right before the unexpected shutdown? Kernel panics? Crashes?
Hmm, nobody? Does it mean that everybody else is just ignoring random shutdowns and have never attempted to debug the problem?
AFAIK logcat output isn't persisted over reboot, and maybe that's one reason nobody replied to this thread. But you can always write log to a file every time your phone boots (via shell commands etc) and just check out that file once phone rebooted.
Regarding kernel log, /proc/last_kmsg or /sys/fs/pstore/console-ramoops might be helpful.