My A101 (2.2) sometimes gets unusable slow! I enabled swap (512M on SD Card) but thats not the point, /usr/sbin/audiomixer takes all the CPU, over 85% in "top" (using Terminal Emulator)
What happened here?
Hi!
I am facing the same problem on my A101.
/usr/sbin/audiomixer is using up to 95 % of the cpu. The device reacts with a very high latency to my inputs. After a reboot it works fine. I haven't done anything, no music playing, etc. I just put in the power supply.
I have looked into the logcat output via adb. I'll get the following warning nearly every second:
W/AudioTrack( 1214): obtainBuffer timed out (is the CPU pegged?) 0x17e18 user=00002000, server=00000000
killing the process or rebooting the device is not allowed within the adb shell.
I hope Archos will fix this soon!
Is there any official Archos bug forum, where we could report this issue?
Stefan
Related
Hi there,
my 101IT 8Gb runs extremely slow when resuming from standby.
Scenario and tests:
It happens normally after severals hours in standby mode (more than 5~6 hours)
It takes about 7~10 seconds since I touch the screen until the icon or button is pressed
It happens with or without the microSD inserted
I have killed all running apps using the Archos System Monitor option (it takes ages), without any success
I've run the system diagnostics from the Recovery Menu and everything seems OK
It is updated to FW version 2.1.08
I have Google apps and only a few of other apps installed:
- Aldiko
- Angry Birds (of course )
- DroidWall
- ES File Explorer
- Google AppsWidgetsoid
- SiMi Folder
- Zuma's Revenge
It only works fine again after a reset (pressing the power button 10secs)
Any idea?
Thank you.
enteo said:
Hi there,
my 101IT 8Gb runs extremely slow when resuming from standby.
Scenario and tests:
It happens normally after severals hours in standby mode (more than 5~6 hours)
It takes about 7~10 seconds since I touch the screen until the icon or button is pressed
It happens with or without the microSD inserted
I have killed all running apps using the Archos System Monitor option (it takes ages), without any success
I've run the system diagnostics from the Recovery Menu and everything seems OK
It is updated to FW version 2.1.08
I have Google apps and only a few of other apps installed:
- Aldiko
- Angry Birds (of course )
- DroidWall
- ES File Explorer
- Google AppsWidgetsoid
- SiMi Folder
- Zuma's Revenge
It only works fine again after a reset (pressing the power button 10secs)
Any idea?
Thank you.
Click to expand...
Click to collapse
I have the same issue. Any suggestions would be great.
Hi,
I don't if this will help or is applicable, but in some other devices, I've seen suggestions that turning wifi off before putting the device to sleep mode might prevent this.
Just a guess.
Jim
i had this problem before installing Uruk, after that this problem is no longer existing
I had the same issue. Now i switch off Angry Birds before i send my Archos 101 to standby. Its enough to press the home button before Archos will sleep.
For me this fixes the issue.
best regards
trilu
I have the same issue.
I do not have this issue with my A101 or my A43. It does take about 10 seconds from the time I hit the power button for the WiFi to reconnect, but that's not what you are talking about.
Maybe I don't have this problem because of the way I use computers in general. Before going into standby, I close down or kill all processes that are running that I don't really need running. So that means if I was playing Angry Birds, I not only exit the program, I always run System Monitor and kill all processes I don't absolutely need to keep running. This is a habit from the stone age of computing when machines were not that good at going into or out of standby or sleep. In reality, all of the machines I use from day to day are actually quite good at handling standby, sleep or hibernation - I just don't trust these modes and avoid them if at all possible.
So, do you just put your tablet to sleep with all sorts of stuff running, or at least resident, or do you act as if it's still 20 years ago?
Bye.
oops sorry thread changed
CrunchyDoodle said:
...
Before going into standby, I close down or kill all processes that are running that I don't really need running. So that means if I was playing Angry Birds, I not only exit the program, I always run System Monitor and kill all processes I don't absolutely need to keep running. This is a habit from the stone age of computing when machines were not that good at going into or out of standby or sleep.
...
So, do you just put your tablet to sleep with all sorts of stuff running, or at least resident, or do you act as if it's still 20 years ago?
Click to expand...
Click to collapse
Well, I believe this would be really useful if we were using 20 years old computers, but this is not the case . Actually, one of the strengths of Android, from Froyo onwards, is the memory and processes management.
Anyway, I tried switching WiFi off before sending it to sleep, uninstalled Zuma (suspicious for me) and everything seemed to be OK for some days but, this morning it has happened again.
I have tried killing all processes using the System Monitor, restarting the launcher (Zeam) and, finally, I've had to do a reboot.
By the way, I'm also very careful with my computers and OS; I always use to close applications properly, install as few applications as possible, avoid unnecessary services or autorun programs (specially in Windows), etc. I mean, I also know what happens inside the box.
Conclusion: No clue!
Regards,
Carlos.
Hi,
I have a very similar device like "Cat Stargate Epic", it is "em73_sis_hy30_v2" and should be like this: TC702 7" Capacitive Touchscreen Android 2.3 Tablet with Telechips 8803 1.2GHz CPU + 512MB DDR3 RAM + 4GB Storage
After startup wifi has normal speed, I test it everytime with Speedtest.net-app ~ 5-8 Mbit/s. When I put the tablet into standby and wake it up again I only get ~ 500 kbit/s max. For getting full speed again I have to reboot. That's very odd. I tried several apps for wifi not to sleep etc, but nothing helps. It seems that the wifi-module is not waked up and still is in any sleeping mode...
Does anyone have the same problem or any hint for me to solve this issue? Thanks!
I have the same problem on my T8031 (with Telechips 8803 and Android 2.3.3).
Still don't know what to do with it =(
Hey guys,
I'm currently running into a problem where I (and the internet) don't have an explanation.
i'm logging processor usage using SystemPanel (https://play.google.com/store/apps/details?id=nextapp.systempanel.r1) and displaying CPU stats using CPU Spy.
The log of System Panel shows, that ADBD is unsing 16% of CPU time over large periods (e.g. over night). CPU Spy shows that the processor is goping to deep sleep.
How can I get further information on the ADB Daemon and how can I prevent it from using cpu when the phone is asleep WITHOUT turning off usb debugging every time i'm finished?
My phone is latest german stock rom, rootet but no system apps deinstalled (yet..)
thanks for your help!
-Acid
anybody?!
Do you notice heavy battery drain? It sounds to me that it uses 16% out the little power that is used overnight. So it would hardly affect battery life at all. Does adbd show up if you look at the usage of a regular day?
Currently working on adding an auto reboot function for an app on rooted devices, which is causing us some issues.
The Auto-reboot is performed using a shell command under the SU identify and whilst this works for a few boots, the
app then crashes. We have tested 4 minute and hourly cycles and the issue usually occurs after 5-6 reboots, although there
isn't a consistent pattern of the number of reboots before it dies The issue is seen across different devices (Scroll Extreme and Archos
80 G9 Tablets PC's). Anyone got any experience of auto-reboots and could advise of a possible solution
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Nafiganado said:
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Click to expand...
Click to collapse
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
es0tericcha0s said:
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
Click to expand...
Click to collapse
Hi,
yes, i've used Wakelock detector app as well as its advanced colleague - BetterBatteryStats. So that's how I've found out about "s5p-ehci" wakelock. And I can see there is no other reason of phone insomnia, besides s5p-ehci.
All other apps and processes consume CPU moderately. When s5p-ehci activity is moderate - phone sleeps well. When it gets berserk and is active during several hours - phone does not sleep at all during whole this time (deep sleep is 0%), instead works on minimal frequency (300MHz), however, it's about 40% of battery draining per night.
If it's a hardware issue - I wonder who can help me with that investigation. Services do not deal with such cases, since there is no permanent problem signs. In my case the process can behave properly during a day. Then, all of a sudden, it's getting active and some its activity lasts hours! Then it's getting back to normal again. I've looked at kernel log and system log. There is a lot of various events happening there: something is going on, then device sent to sleep, then again something is going on, then wakeup, in various cases wakeup reasons are different, I was unable to find some relevant info... I would send this log to anyone who could help me to find source of the problem.
I've rolled back to Android 4.1 firmware and installed custom kernel.
Here situation is better, but what I have discovered:
phone seems not to detect when it's being plugged off from charger - no matter, USB cable from computer or wall socket wire. s5p-ehci does not go away and sucks off my battery. What only helps is manually resetting EHCI power: setting 0 in ehci_power file. As a result, something is reset, ehci power is on again, but this sucker goes away and after that everything is fine until next charge. But I need to find a root of the problem!
Going on investigation - too view info in Internet...