Was wondering if anyone could lend me a hand with this.
Getting a common system UI crash caused by:
"ANR Broadcast of Intent {act=android.intent.action.TIME_TICK flg=0x40000014 (has extras)..."
What can I do to start troubleshooting this?
Thanks
Related
I have had the lurvely DHD for a week now, and I've recently noticed on OSMonitor a process that comes in pretty regularly and uses up between 60-80% ocp load.
Its called Customization Setup and its PID is 1552 and seems to be there hogging ocp everytime I check. Is this normal?
If so is there something I can set to prevent it coming?
Thanks
Hey guys. I've been looking around all over for info on the problem with my app. Nothing I found was a concrete answer. here's the problem. I made an app that works really well except it force closes when I hit the back button to finish activity and then start another of the same activity as before. It force closes once in a while when I do this, throwing a log cat error that says out of memory, pointing to where I fill my bitmap cache. There's two reasons im thinking it would be doing this. 1) My bitmap factory is having a problem or 2) I have the context of my activity stored as a variable so I can close activity and that is too much memory. I'm using a panel, which also may add to the problem. Also, another phone can't even start the activity the first time. Any help would be greatly appreciated. This is only problem on app and this fix will make it market ready.
Sent from my SCH-I500 using XDA App
Did you try to explicitly clean up the bitmap references? you should call Recycle() on every bitmap in your activity's onDestroy or wherever you do your cleaning. Another issue I had was with the Bitmap.CreateScaledBitmap method - it leaks, apparently. I made a small static method that uses a transform matrix and then calls Bitmap.CreateBitmap (the overload that takes a matrix, obviously). That change alone solved half my memory issues.
The thing about not loading at all on another phone might be a heap issue. My game loaded just great on my customized SGS, but on the emulator with 24mb of heap it crashed. The reason was that I pre-load all the sprites at the beginning, and apparently 24mb isn't that much
Solution was downscaling and lowering resolution and color depth for the sprites, not much possibilities here - too many bitmaps take too much memory...
I'm guessing the phone you tested likely has a smaller heap than the phone that doesn't make your app crash.
Of course all of the above is mostly guess work, but that's what I can supply right now
i have the problem fc too, but after i upgraded to 2.2. the seem the problem fixed automatically.
Thanks so much! I made it recycle my bitmaps, along with a few minor changes, and it worked great! Thanks for your help!
Sent from my SCH-I500 using XDA App
I've tried a couple of different ROMs recently and my phone keeps randomly freezing when I leave it idle.
I'm assuming it's one of the many apps I've got installed, so I'm wondering if there's an app that might help me find out what app is causing it exactly.
I've never used logcat before - but does this sound like the kinda thing it could be used for? Are the logs actually readable by a n00b like me?
Any advice appreciated!
Thanks
Already tried a clean install, without restoring a cwm backup?
Use Titanium to save your apps.
To view the logs of your phone you can use e.g. alogcat from the market.
did you found out what is freezing your phone? Mine is also freezing randomly. Is it better to flash android to your phone with CLK or MAGLDR?
This has happened on several different ROMs, each time i've totally wiped my SD and repartitioned it (with GParted) and also re-flashed with CWM.
sometimes logs get wiped or damaged when you remove the battery, so if you don't find logs useful, here's the hard way:
install apps one by one. Every time you install an app, leave your phone idle and see if it freezes. Use this as a last resort.
when you find what's causing the problems we'd like to know which app was causing the problem
Hmm just managed to log a crash (so to speak!)
The last entry in the log, before it crashed was:
--------------------------------
05-31 09:13:00.207 D/AppWidgetHostView(17704): updateAppWidget mInfo = AppWidgetProviderInfo(provider=ComponentInfo{com.levelup.beautifulwidgets/com.levelup.beautifulwidgets.ClockWidget41})
--------------------------------
So maybe it's my Beautifulwidgets that are causing the lock-ups... or maybe that was just a coincidence.... either way I'll carry on logging and see if a pattern emerges!
usally it's the widgetsthat makes your phone crash.
yz.hd said:
usally it's the widgetsthat makes your phone crash.
Click to expand...
Click to collapse
Yeah. Plus i've just done some Googling and it seems that other people have had issues when using LauncherPro (which i'm also using) alongside BeautifulWidgets...
Might have to ditch one of them!
I have to FC launcherpro every single time I turn on my phone on
Hmm annoying The last few lines of the most recent crash look totally unrelated:
--------------------------------
06-02 23:55:13.918 D/PowerManagerService( 241): New lightsensor value:40, lcdValue:83
06-02 23:55:14.918 D/PowerManagerService( 241): New lightsensor value:90, lcdValue:83
06-02 23:55:14.918 D/PowerManagerService( 241): lightSensorChangedLocked, buttonValue >= 0, mPowerState = 3
06-02 23:55:14.918 D/PowerManagerService( 241): setPenMenuButtonLed: 4
--------------------------------
For anyone that might also get a similar issue (or even cares) I've uninstalled LauncherPro+ and my lockups have completely stopped (just using bog-standard Sense now).
Pooper said:
For anyone that might also get a similar issue (or even cares) I've uninstalled LauncherPro+ and my lockups have completely stopped (just using bog-standard Sense now).
Click to expand...
Click to collapse
I've got Launcher Pro on my phone and it's freezing constantly.
No matter what Launcher I use, no matter what SD card, no matter what build I use.....freeze freeze freeze.
matt
I'm sorry for posting here, but since I haven't posted much to the forums in the past, I haven't hit 10 posts and can't post to the appropriate thread here: http://forum.xda-developers.com/showthread.php?t=1932826
Regardless, with that ROM, I'm seeing two issues:
1) My wifi password is not remembered, and hence has to be re-entered every time I reconnect.
2) My System process is eating the CPU, and probably not coincidentally, my logs are filled with sections like this, repeated forever:
Code:
rmt_storage( 3300): rmt_storage user app start
rmt_storage( 3300): rmt_storage open success
rmt_storage( 3300): rmt_storage shared memory ioctl success
rmt_storage( 3300): rmt_storage mmap addr = 40011000
rmt_storage( 3300): rmt_storage wait event ioctl failed
I can watch the logs and see this being repeated again and again while the ROM is running, but I can't trace it to a process that's causing the problem.
Finally, I hope this post is seen. It's extremely irritating to be forced to post to the wrong forum. Sorry about that.
Thanks a ton for any help!
Hmm, looks like the wifi thing at least is a known issue...
...and for what it matters, apparently others are seeing things like what I'm seeing in the logs, but with no resolution (and not necessarily only in this rom)
beanfootage said:
...and for what it matters, apparently others are seeing things like what I'm seeing in the logs, but with no resolution (and not necessarily only in this rom)
Click to expand...
Click to collapse
I finally had to revert to another ROM to address this. Strangely, I can't even tell what rmt_storage does. If anyone has any insight, let me know; in the meantime I'll keep googling, I guess.
Hi !
I'm developing me first "real" (some minor projects before) app for android. Right now i'm trying to optimize the memory usage, regarding to this I have a question. I hope someone can help me.
I've implemented a foreground service, which also updates some UI-elements via a static reference of the MainActivity.
My question is, what happens if the UI is not visible (i.e. MainActivity is destroyed) ? Are these calls ignored ? Are they using memory ?
Thanks in advance!
You shouldn't keep reference objects with short lifecycle from an object with long lifecycle, unless you carefully manage these references.
To answer your question: UI-elements will be kept in memory till ClassLoader will be destroyed or the references will be nullified.
LinuxForce said:
Hi !
I'm developing me first "real" (some minor projects before) app for android. Right now i'm trying to optimize the memory usage, regarding to this I have a question. I hope someone can help me.
I've implemented a foreground service, which also updates some UI-elements via a static reference of the MainActivity.
My question is, what happens if the UI is not visible (i.e. MainActivity is destroyed) ? Are these calls ignored ? Are they using memory ?
Thanks in advance!
Click to expand...
Click to collapse
Once the activity is destroyed there should be no more running resources, ie. memory usage. If you want to stop other UI-elements such as lingering toasts or dialogs, you can overwrite the onDestroy method to do so.
bbish937 said:
Once the activity is destroyed there should be no more running resources, ie. memory usage.
Click to expand...
Click to collapse
What if class has static reference to one of Views, will it be nullified by itself once the Activity destroyed or it will be kept in memory?