I am running android 4.4.2 KitKat on an older device that only has 512 MB ram.
If I enable KitKat's optimizations for low-memory devices (by setting
ro.config.low_ram=false in build.prop), the Alarm Klock app misbehaves. Each
time the phone is rebooted, the logcat is spammed with the following messages
repeatedly:
03-30 22:38:52.687 I/ActivityManager(1673): Delay finish:
com.angrydoughnuts.android.alarmclock/.ReceiverNotificationRefresh
03-30 22:38:52.702 I/ActivityManager(1673): Resuming delayed broadcast
03-30 22:38:52.718 I/ActivityManager(1673): Delay finish:
com.angrydoughnuts.android.alarmclock/.ReceiverNotificationRefresh
03-30 22:38:52.734 I/ActivityManager(1673): Resuming delayed broadcast
(see attached logcat_1). This process continues and keeps the CPU busy at
99-100% indefinitely, until I manually open the Alarm Klock app. Then the
logcat messages stop and the CPU usage goes back to normal (see attached
logcat_2). However, I have to manually open the app after each reboot;
otherwise it will bog down the CPU and quickly drain the battery.
The problem does not occur if I disable KitKat's low-memory optimizations (by
setting "ro.config.low_ram=false" in build.prop), but I'd really like to keep
that feature enabled, as it makes my old phone a lot faster.
Hopefully this information helps to solve the issue. Thanks!
Original issue reported on code.google.com by JoshuaHe...@gmail.com on 31 Mar 2014 at 3:04
Original issue reported on code.google.com by
JoshuaHe...@gmail.comon 31 Mar 2014 at 3:04Attachments: