Open GoogleCodeExporter opened 9 years ago
I believe the pegged CPU and two threads has to do with the Home action.
When I'm running another app, and instead of using the "exit/curl-back" button
on the phone, I use the Home button. Since I have more than one launcher
downloaded, I am presented with a prompt asking which launcher to use. I
always 'set default' then choose ADW.Launcher (for whatever reason, I still get
prompted for future home clicks).
Could this "confusion" be spawning another thread? Perhaps it's causing some
sort've lock-contention for system files, etc?
Original comment by gacan...@gmail.com
on 14 Sep 2010 at 2:37
http://code.google.com/p/adw-launcher-android/issues/detail?id=111
this link seems to describe the same issue of having to choose the home button
again, but without the cpu spike reported.
Original comment by gacan...@gmail.com
on 15 Sep 2010 at 1:11
There really is no need to use a third party app "home switcher" to change home
apps.
This is probably causing your high CPU use.
Please uninstall the "home switcher" and follow these steps:
The proper way to clear and "switch" without any third party app is to go to
Settings > Manage Applications > ADW.Launcher and select clear default.
Pressing home will now present a prompt to choose your home..
Please report back using these steps.
Original comment by klinster...@gmail.com
on 23 Oct 2010 at 8:29
Agreed: I do not use "home switcher" any longer.
I still see two threads, with same PID, spiked at 100% in the Android System
Info app.
Does this seem normal then?
I'm not sure if Android System Info (ASI) is reporting this correctly. I tried
another app to show CPU usage on the notifications bar. It sits very low, if
not idle, even when ASI indicates 100% CPU -- weird.
Original comment by gacan...@gmail.com
on 24 Oct 2010 at 3:11
Using ADW Launcher 1.2.0 CPU usage is much higher than without; it won't reach
100% overall CPU usage but AndroidSystemInfo shows 2 processes with 100% CPU:
PID 2746 UserID 10010 background org.adw.launcher 22.98mb
I tried LauncherPro before using ADW Launcher but that app caused a 100% CPU
usage on my phone. So maybe it's something with the phone using alternative
home replacements...
Samsung Galaxy 3 I5800 with Eclair2.1 (root)
Original comment by tm2...@googlemail.com
on 14 Nov 2010 at 12:43
I do not use a homeswitcher mod... just adwlauncher as default for home and
return buttons.
I have two processes using nearly 50 mb memory and 100% cpu (system info pro).
process - android.process.acore
threads - 10
package name - org.adwfreak.launcher
nexus s
android 2.3.1
kern 2.6.35.7
build GRH78
Original comment by jessdf...@gmail.com
on 6 Jan 2011 at 12:16
Having the exact same problems with two android phones. Tried two different
launchers and the exact same thing is happening with both (two instances of
android.process.acore goes to 100% usage).
Tried both with launcher pro as well as adw launcher.
The two phones i've tried with are
ZTE Blade running stock 2.1
HTC Desire running stock 2.2
Original comment by dome...@gmail.com
on 13 Feb 2011 at 5:45
I also am using ADW EX and have the same issue - two .acore processes with
org.adwfreak.launcher at 100% CPU. I used to have the home switcher app but
removed it. I still have the stock launcher loaded. Is it safe to remove that
or "freeze" it with Titanium backup and would that help?
Original comment by rmdri...@gmail.com
on 18 Apr 2011 at 10:17
Same problem,
Xperia x10 MINI running 2.1 , upgrade from Sony Ericsson web.
With the stock launcher every thing is OK, but I try ADW / Launcher Pro / Go
Launcher and this 3 launchers have same issue.
two android.process.acore using 100% cpu.
This happens only if wifi is active (I try to disable all syncs and the same
problem happens)
If I open 3 launchers I can see 3 android.process.acore running, so every time
I try a launcher I kill all of the android.process.acore process.
I don't know why, but it'll be really useful to use a custom launcher because
the default launcher is really bad.
Federico
(Sorry for my English, I'm from Argentina)
Original comment by sk8feder...@gmail.com
on 4 May 2011 at 4:38
Hi guys,
I can confirm a similar issue with what seems all 3rd party launchers including
adw.
I have not seen two processes but when a 3rd party launcher runs as acore the
cpu does appear to be under more load than it would otherwise be. I use a
samsung galaxy S GT-I9000 and while idling on the home screen with a cpu
monitoring set running I get a regular 100% cpu while the cpu is clocked to
200mhz. The internal samsung Touchwiz launcher (twlauncher) when in use as it
would be the cpu runs at 100mhz at about 10% utilisation at that frequency.
This phone is running android 2.3.3 stock firmware. Please contact me if there
is any additional information I can provide.
Original comment by netsu...@gmail.com
on 1 Sep 2011 at 6:26
is my problem in x10 xperia android 2.3
Original comment by marceloh...@gmail.com
on 13 Dec 2011 at 4:18
I am also experiencing high CPU usage. I am on a Samsung Epic 4g (Samsung
Galaxys S for Sprint), rooted but stock everything else and I find CPU usage
spikes any time I use the home button from an application. The high-er end, or
HD apps make it worse (especially out of games like Angry Birds, or Plants vs.
Zombie) or any time I change setting in ADW EX. I usually have to open the
standard task manager (that comes up when long-pressing home button and
selecting task manager), sometimes the CPU spikes for a good 5 mintues into the
red-zone, making my phone virtually unuseable during that time.
I am currently running Froyo, 2.2
Original comment by PokeAshe...@gmail.com
on 31 Dec 2011 at 4:23
Saw this problem on a Sony Ericsson Xperia Arc.
It had Gingerbread 2.3.8 with ADW Launcher and everything was fine.
When it was upgraded to ICS 4.0.4, com.google.media and com.google.acore
started eating up most of the CPU time. Searching Google for the .media, the
advice was to search /mnt/sdcard/media/audio/ for ringtones and delete them. I
did not have any ringtones there, but did have one notification for facebook. I
deleted it, and it helped a bit.
After that .media continued to eat CPU time. Only after I killed Xperia Gallery
using Automatic Task Killer (ATK) did the phone go back to normal, and neither
.acore nor .media were eating up CPU.
Here is the output of top -n 7, either from adb shell or from ConnectBot.
While com.google.media is eating CPU
User 55%, System 12%, IOW 32%, IRQ 0%
User 56 + Nice 116 + Sys 38 + Idle 0 + IOW 100 + IRQ 0 + SIRQ 0 = 310
PID PR CPU% S #THR VSS RSS PCY UID Name
456 0 44% S 16 292200K 17956K bg app_26 android.process.media
2456 0 11% S 23 295108K 14484K bg app_87 com.sonyericsson.gallery
310 0 4% S 76 390468K 35008K fg system system_server
3403 0 1% R 1 924K 448K fg shell top
114 0 0% S 1 0K 0K fg root yaffs-bg-1
140 0 0% S 3 28024K 1192K fg drm /system/bin/drmserver
111 0 0% D 1 0K 0K fg root mmcqd
While both com.google.acore and com.google.acore is eating CPU
User 83%, System 10%, IOW 6%, IRQ 0%
User 40 + Nice 214 + Sys 33 + Idle 0 + IOW 19 + IRQ 0 + SIRQ 0 = 306
PID PR CPU% S #THR VSS RSS PCY UID Name
612 0 29% S 17 297168K 21596K bg app_23 android.process.acore
456 0 28% S 16 292200K 18064K bg app_26 android.process.media
3132 0 24% S 21 299632K 30064K bg app_23 com.sonyericsson.android.socialphonebook
2456 0 3% S 16 287828K 15000K bg app_87 com.sonyericsson.gallery
310 0 2% S 76 390468K 37596K fg system system_server
2670 0 1% S 10 286736K 38716K fg app_11 android.process.acore
3203 0 1% R 1 924K 448K fg shell top
After .acore stops eating CPU
User 0%, System 2%, IOW 0%, IRQ 0%
User 1 + Nice 0 + Sys 9 + Idle 296 + IOW 0 + IRQ 0 + SIRQ 0 = 306
PID PR CPU% S #THR VSS RSS PCY UID Name
5614 0 1% R 1 928K 460K fg shell top
393 0 1% S 12 291432K 25576K fg system com.android.systemui
3 0 0% S 1 0K 0K fg root ksoftirqd/0
4 0 0% S 1 0K 0K fg root events/0
5 0 0% S 1 0K 0K fg root khelper
6 0 0% S 1 0K 0K fg root async/mgr
7 0 0% S 1 0K 0K fg root suspend
Original comment by kba...@gmail.com
on 23 Aug 2012 at 12:44
Original issue reported on code.google.com by
gacan...@gmail.com
on 11 Sep 2010 at 6:32