HopelessFantasy / openetna

Automatically exported from code.google.com/p/openetna
0 stars 0 forks source link

Phone randomly doesn't react / phone freezing/slow - dhd_dpc / system_server #391

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Phone is freezing without apparent reason.

Top shows dhd_dpc as the first suspect. (using too much cpu).

After some minutes it stopped and all was good again.

What is dhd_dpc?

Using 6.3-rc2

Noticed that lower corner is becoming more and more darker.

Original issue reported on code.google.com by trmfrei...@gmail.com on 7 Feb 2011 at 5:06

GoogleCodeExporter commented 9 years ago
System locked up again. This time it was system_server.

And then dhd_dpc.

Original comment by trmfrei...@gmail.com on 7 Feb 2011 at 5:19

GoogleCodeExporter commented 9 years ago
logcat.

Phone is still locked. 
I am going to reboot phone by removing battery.

Original comment by trmfrei...@gmail.com on 7 Feb 2011 at 5:27

Attachments:

GoogleCodeExporter commented 9 years ago
Turned Wifi off. I believe dhd_dpc problem is gone.
system_server is always above 35% without touching the phone and screen is off.

This will probably drain the battery.
Logcat does not show anything new.

Original comment by trmfrei...@gmail.com on 7 Feb 2011 at 5:37

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Verified that system_server only uses +/- 40% cpu when screen is off/locked.
When unlocked it goes to +/-0%.
Is this an issue? Might be fine if cpu is scaled down to 1/20th.

Disabled GPS also. Same thing.

See issue: http://code.google.com/p/android/issues/detail?id=3453

Original comment by trmfrei...@gmail.com on 7 Feb 2011 at 5:57

GoogleCodeExporter commented 9 years ago
The thread in system_server which is using too much cpu is WindowManagerPolicy.

Original comment by trmfrei...@gmail.com on 7 Feb 2011 at 6:10

GoogleCodeExporter commented 9 years ago
User 33%, System 19%, IOW 0%, IRQ 0%
User 211 + Nice 0 + Sys 125 + Idle 302 + IOW 0 + IRQ 0 + SIRQ 0 = 638

  PID   TID CPU% S     VSS     RSS PCY UID      Thread          Proc
  170   196  33% R 196736K  39136K  fg system   WindowManagerPo system_server
  757   757  13% R   1100K    504K  fg root     top             top
  170   177   7% S 196736K  39136K  fg system   SurfaceFlinger  system_server

User 31%, System 16%, IOW 0%, IRQ 0%
User 210 + Nice 0 + Sys 110 + Idle 342 + IOW 0 + IRQ 0 + SIRQ 0 = 662

  PID   TID CPU% S     VSS     RSS PCY UID      Thread          Proc
  170   196  27% R 196736K  39140K  fg system   WindowManagerPo system_server
  757   757  13% R   1100K    504K  fg root     top             top
  170   177   5% S 196736K  39140K  fg system   SurfaceFlinger  system_server

Original comment by trmfrei...@gmail.com on 7 Feb 2011 at 6:21

GoogleCodeExporter commented 9 years ago
dhd has to do with wifi. Did you have it enabled?

Original comment by polyth...@gmail.com on 7 Feb 2011 at 7:14

GoogleCodeExporter commented 9 years ago
Yes I did. After disabling it, that problem stopped and system_server started.
I don't know yet if it is a problem.

How do I check if the cpu has been throttled down?

Original comment by trmfrei...@gmail.com on 7 Feb 2011 at 10:27

GoogleCodeExporter commented 9 years ago
I also noticed that the phone gets sluggish if you turn the screen off when 
wifi is enabled.

Original comment by GiorgioM...@gmail.com on 8 Feb 2011 at 8:35

GoogleCodeExporter commented 9 years ago
Today I connected the phone and run top and system_server is completely normal!

Today the phone is fine.

Did not try to turn on Wifi. Probably the same.

Original comment by trmfrei...@gmail.com on 8 Feb 2011 at 10:34

GoogleCodeExporter commented 9 years ago
Issue 263 has been merged into this issue.

Original comment by trmfrei...@gmail.com on 8 Feb 2011 at 11:51

GoogleCodeExporter commented 9 years ago
See issue 263 for more comments about problems with wifi/locksreen.

Original comment by trmfrei...@gmail.com on 8 Feb 2011 at 11:52

GoogleCodeExporter commented 9 years ago
I am using 6.3-rc2.
I don't use wifi. But I still have these symptoms. 
I use SetCPU. It random restarts at times, doesn't matter what mode ( 
ondemand,interactive ... etc )and what freq setting I use.

I haven't seen the problem since when I switch back to overclock widget. SetCPU 
works fine before rc6.2-xxxx builds.

Thanks for getting the home and touch button vibrates :) Appreciated.

Original comment by justfort...@gmail.com on 8 Feb 2011 at 8:53

GoogleCodeExporter commented 9 years ago
Rc4 happens to me after a while off the phone screen does not react with wifi 
off to my in rc2 not occurred to me, for me the only downside to rc2 was the 
dark corner of the screen.

Original comment by chachepo...@gmail.com on 9 Feb 2011 at 10:50

GoogleCodeExporter commented 9 years ago
Yes, this is still happening in 6.3-rc4.

Original comment by trmfrei...@gmail.com on 9 Feb 2011 at 11:00

GoogleCodeExporter commented 9 years ago
Are you getting something like this
<4>[  897.288851] dhdsdio_htclk: HT Avail request error: -35
<4>[  897.565762] dhdcdc_query_ioctl: dhdcdc_msg failed w/status -5
in "adb shell dmesg"?
Those error seem to occur when wifi was on while the phone goes to suspend. 
After waking up, you see those error. But this even happens on the official LG 
froyo rom, if you set "WiFi sleep policy" to never.

There are big fragments of code in lg's kernel about how to handle the Wifi 
sleep correctly, but they are all disabled. It seems that even Lg did not get 
this working...?

Original comment by polyth...@gmail.com on 9 Feb 2011 at 11:50

GoogleCodeExporter commented 9 years ago
If this is really the same problem as I wrote in comment 17, then its fixed in 
6.3-rc5.

Original comment by polyth...@gmail.com on 9 Feb 2011 at 2:57

GoogleCodeExporter commented 9 years ago
The same fault that rc4 with the wifi shut off the screen for a while the phone 
is no longer responding, it is rare to not get done rc2 to rc4 and rc5 if you 
do, and tried to put the suspension policy wifi and the wifi never disconnected 
and keeps crashing, finally return to rc2 to be a solution.

Original comment by chachepo...@gmail.com on 9 Feb 2011 at 4:56

GoogleCodeExporter commented 9 years ago
I could not understand what you intended to say.

This problem was present in 6.3-rc2 and 6.3-rc4 in 6.3-rc5 this is probably 
fixed.

Original comment by trmfrei...@gmail.com on 9 Feb 2011 at 5:17

GoogleCodeExporter commented 9 years ago
This appears to be fixed.

About system_server I have no idea about what happened nor if it will happen 
again.

Original comment by trmfrei...@gmail.com on 10 Feb 2011 at 9:54

GoogleCodeExporter commented 9 years ago
Sorry for my English is translated by google, in 6.3-rc2 the only problem is 
the dark corner of the screen, with 6.3-rc4 with the wifi off, to turn off the 
screen no longer responds and I have to remove and replace the battery to turn 
it on again, and with 6.3-rc5 has exactly the same problem as with 6.3-rc4.
Is there any way to fix the issue of the dark corner of the screen without 
re-flash, 6.3-rc2 is that I work well? thank you very much.

Original comment by chachepo...@gmail.com on 10 Feb 2011 at 11:14

GoogleCodeExporter commented 9 years ago
Your problem appears to be related with issue 401. 
In this issue the problem was Wifi.

I have that problem. Crashing after lock without apparent reason.

Original comment by trmfrei...@gmail.com on 10 Feb 2011 at 1:29

GoogleCodeExporter commented 9 years ago
Well I had a problem as well with the wifi on V6.3-rc6 but on me the phone 
crashed few sec after I swiched the wifi off and the mobile net started 
working. Anyway the wifi was really unstable swiching on and off it self all 
the time. I will make a few more tests to see if problem persist.

Original comment by rae...@googlemail.com on 13 Feb 2011 at 12:37

GoogleCodeExporter commented 9 years ago
OK.

Thank you

Original comment by trmfrei...@gmail.com on 13 Feb 2011 at 1:00

GoogleCodeExporter commented 9 years ago

Original comment by trmfrei...@gmail.com on 20 Feb 2011 at 5:38