When phone going to sleep, it crash

[GoogleCodeExporter]

What steps will reproduce the problem?
Every time rhe phone going to sleep

What is the expected output? What do you see instead?
The phone workes

What version of the boot.img and system.img are you using?
bootV6.3-rc6 and systemV6.3-rc6

Original issue reported on code.google.com by bestou...@gmail.com on 12 Feb 2011 at 5:19

[GoogleCodeExporter]

Please provide a logcat during the pre and frozen state.

Original comment by trmfrei...@gmail.com on 12 Feb 2011 at 6:04

• Changed state: NeedInfo

[GoogleCodeExporter]

I have just a logcat before frozen state because the phone don't crash when 
it's connected with the usb cable.

Original comment by bestou...@gmail.com on 12 Feb 2011 at 10:36

Attachments:

• logcat.txt

[GoogleCodeExporter]

This logcat contains the frozen state, right?

Polytheus, please check the logcat.

Original comment by trmfrei...@gmail.com on 12 Feb 2011 at 10:52

[GoogleCodeExporter]

No, because the phone crash only when it isn't connected with the usb cable

Original comment by bestou...@gmail.com on 12 Feb 2011 at 11:10

[GoogleCodeExporter]

You can download aLogCat from the market. It can write logcats to SDCard 
without the need of an ADB shell.

Original comment by oldm...@gmail.com on 12 Feb 2011 at 11:34

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have seen the others issues and I realized it was because of SetCPU.
I uninstalled it and now the phone works normaly.

Original comment by bestou...@gmail.com on 13 Feb 2011 at 5:34

[GoogleCodeExporter]

If its a kernel bug, then we need the output of dmesg. But I do not currently 
know of any tool for android that can archive this.
Maybe the addition of the ramconsole has caused this crashes to happen.
Please try the attached kernel and report back.

Original comment by polyth...@gmail.com on 13 Feb 2011 at 5:49

Attachments:

• boot.img

[GoogleCodeExporter]

tested... it still hangs if you enable then disable wifi.

Original comment by figgelu...@gmail.com on 13 Feb 2011 at 9:01

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Perhaps you can try:

Issue this after starting your phone:

cat /proc/kmsg > /sdcard/dmesg.txt &

With a bit of luck you will get what you need, at least if kernel crashes after 
syncing to card.... it would be great if cat synced everytime a write was made 
(only for debug of course).

Original comment by trmfrei...@gmail.com on 14 Feb 2011 at 12:39

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Since freezing is not followed each time by using this boot.
Lack bit to find the solution.

Original comment by DavidGF....@gmail.com on 14 Feb 2011 at 2:59

[GoogleCodeExporter]

To reproduce: Go to Setting->Wireless & Networks, then toggle Wifi multiple 
times (for about 30 seconds). Then the phone freezes.

Original comment by polyth...@gmail.com on 15 Feb 2011 at 3:29

• Added labels: Priority-High
• Removed labels: Priority-None

[GoogleCodeExporter]

Just commenting that I have the same issue: rc5 phone hangs after leaving it 
alone for an unspecific amount of time (several hours, or several minutes after 
booting). 
I've been trying a rc6 (completely clean, with gapps installed) the last 4 
hours and the phone hanged twice.

Trying to obtaing a logcat after phone hangs was not possible (phone wasn't 
showing with lsusb).

With 6.3-rc5 also I had several hangs with the screen turned on, so probably (I 
don't remember for sure) I had it connected to USB cable at that moment (as I 
have the "screen always lit when connected to USB" setting turned on). 

I'll try to have the phone connected as much as possible dumping logcats to 
laptop, if something shows up I'll to provide a log with crash information.

Original comment by eloi.and...@gmail.com on 15 Feb 2011 at 4:32

[GoogleCodeExporter]

Hi,

In my case, I cannot set SetCPU (2.1) above 595MHz it crashes when the screen 
is off! ( If I leave it on, I dont have any problems )

Tested both with 6.3 rc5 and rc6 (clean install)

Original comment by geeko.s...@gmail.com on 16 Feb 2011 at 10:20

[GoogleCodeExporter]

I also had same problems with 6.3 rc5 and continuing having them with 6.3 rc6. 
Phone hangs after some time and only battery removal helps to get it back 
working. Also, once I had the problem that menu button stopped working and once 
it crashed when it was connected to USB and I tried to make a call.

I do not recommend people using 6.3 rc5 and rc6 because they are too unstable 
and you can expect your phone to crash at any time. :(

Original comment by oleg.gol...@gmail.com on 16 Feb 2011 at 2:56

[GoogleCodeExporter]

Having this problem too on 6.3 rc5. With the phone charging from the mains and 
WiFi on the phone is fine, with WiFi off the phone crashes and will only turn 
back on after the battery has been removed.

Original comment by worsley...@googlemail.com on 16 Feb 2011 at 7:16

[GoogleCodeExporter]

Original comment by trmfrei...@gmail.com on 16 Feb 2011 at 9:28

• Changed state: NeedVolunteer

[GoogleCodeExporter]

I'm currently setting up the android ramconsole, which preserves the kernel 
messages of a crash in ram. This way I can trace the crash.

Original comment by polyth...@gmail.com on 17 Feb 2011 at 10:59

[GoogleCodeExporter]

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

• Changed state: Started

[GoogleCodeExporter]

Should be fixed in repository. If there is another bug that causes those 
crashes, I have added more debugging to the kernel. The kernel will 
automatically reboot after crash; then you will be able to retrieve the log of 
the crash by adb shell cat /dev/last_kmsg. (Does not work if one removes the 
battery!)

Original comment by polyth...@gmail.com on 17 Feb 2011 at 12:17

• Changed state: ConfirmFix

[GoogleCodeExporter]

The fix is "Reboot Kernel after crash"? has it sense?

Original comment by andreabe...@gmail.com on 17 Feb 2011 at 1:08

[GoogleCodeExporter]

"Reboot Kernel after crash" is just an addition to the real fix, which was in 
the wifi driver and could crash the phone even after becoming disabled.

Original comment by polyth...@gmail.com on 17 Feb 2011 at 1:42

[GoogleCodeExporter]

Thanks poly this issue It's fixed ;)
 but WiFi disconnects itself after some time...at least for me...can anyone confirm this?

Original comment by andreabe...@gmail.com on 17 Feb 2011 at 4:42

[GoogleCodeExporter]

see 418 and 307.

Original comment by trmfrei...@gmail.com on 17 Feb 2011 at 4:47

[GoogleCodeExporter]

My phone rebooted but I don't have the dev /dev/last_kmsg

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

[GoogleCodeExporter]

Are you running 6.3-rc7?

Original comment by polyth...@gmail.com on 17 Feb 2011 at 5:40

[GoogleCodeExporter]

Yes.

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

[GoogleCodeExporter]

@andreabelli93: Have you changed your Wifi Sleep policy? Wifi is supposed to 
disconnect when the phone goes to sleep and reconnect when it wakes up. This is 
to save battery.

Original comment by polyth...@gmail.com on 17 Feb 2011 at 5:42

[GoogleCodeExporter]

Mine is disconnecting too.

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

[GoogleCodeExporter]

I'm sorry, the right path is /proc/last_kmsg.

Original comment by polyth...@gmail.com on 17 Feb 2011 at 5:56

[GoogleCodeExporter]

issue fixed for me, thx.

Original comment by stephane...@gmail.com on 18 Feb 2011 at 8:04

[GoogleCodeExporter]

When I said disconnecting is because connection is dropped and then reconnected.

There is another issue for it.

I'll close this as this appears to be fixed.

Original comment by trmfrei...@gmail.com on 18 Feb 2011 at 10:40

• Changed state: Fixed