mako: soft reboot when using the nav ring

[GoogleCodeExporter]

The problem seems to be when I use the nav ring, some of the time the phone 
just suddenly soft reboots. I use the nav ring mostly to start Google Now but I 
had it happen when attempting to start other apps I have on the ring. Sometime 
I get to see Google Now showing up for a fraction of second before reboot, 
sometimes the phone boots instantly on selecting a target from the ring without 
the app having time to load (or at least to display something).

I am not able to reproduce this, it seems to happen randonmly. The last_kmsg I 
get after reboot does not show anything, there is nothing in there before 
reboot. I was not able to get a logcat, even tho I had the phone reboot while I 
was connected to USB, I just never had logcat running at the right moment. 

I am currently using the latest AOKP ROM (milestone 2) but this issue happened 
with previous nightly versions. I am using now the latest Mako stable kernel:

G:\Documents\Android>adb shell uname -a
Linux localhost 3.4.0-bricked-mako-master-g8fa9be1 #1 SMP PREEMPT Sat Jun 22 
23:31:10 CEST 2013 armv7l GNU/Linux

I had the reboot happen with the latest betas too, I can't seem to find a 
pattern. 

Does this ring a bell ? Are there any known issues which might cause this?

Best regards,
Sylaan

Original issue reported on code.google.com by sylaan@gmail.com on 29 Jul 2013 at 7:00

[GoogleCodeExporter]

Soft reboots are usually not caused by the kernel and I never had any issues on 
4.2.2 stock. So it stands to reason that AOKPs modifications to the nav ring 
are at fault.
I would like to see the kmsg though, even though you say that there was nothing 
in there.

Original comment by showp1984 on 29 Jul 2013 at 7:04

• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

I also thought of that, posted on the mako AOKP forums but nobody there heard 
of something like this. 

I am attaching the files I have. 

Original comment by sylaan@gmail.com on 29 Jul 2013 at 7:06

Attachments:

• dmesg.txt
• last_kmsg

[GoogleCodeExporter]

I took those right after reboot when the phone become available over adb.

Original comment by sylaan@gmail.com on 29 Jul 2013 at 7:07

[GoogleCodeExporter]

"[    0.000000] Linux version 3.4.0-perf-g85ba2bc (hudson@koushik-lion) (gcc 
version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Apr 13 
14:37:58 PDT 2013"

Not my kernel :)

Original comment by showp1984 on 29 Jul 2013 at 6:15

[GoogleCodeExporter]

Original comment by showp1984 on 29 Jul 2013 at 6:15

• Changed state: Done

[GoogleCodeExporter]

WTF! It is your kernel I am running now, see the uname -a output. I don't know 
why that appears in the last_kmsg :-/ . I am serious, I pulled that last_kmsg 
as soon as the phone soft rebooted. 

What kind of sorcery is this!!!

Original comment by sylaan@gmail.com on 29 Jul 2013 at 6:21

[GoogleCodeExporter]

I just checked again, I am running the latest bricked stable according to uname 
and to Settings-About Phone. How do you explain that last_kmsg though ? I 
always flash the ROM in recovery and then immediately flash bricked over it, I 
never even booted with the default AOKP kernel. 

Original comment by sylaan@gmail.com on 29 Jul 2013 at 6:29

[GoogleCodeExporter]

It can be that you pulled the last_kmsg from the recovery kernel. A soft reboot 
will not restart the device, just android. Therefore the last_kmsg will not be 
generated from the actual kernel running, because there was no reboot :)

Original comment by showp1984 on 1 Aug 2013 at 5:16

[GoogleCodeExporter]

Are you saying that  a soft reboot will not generate a last_kmsg? What if I do 
a hard reboot myself right after the soft reboot, will the last_kmsg be 
generated and be useful? 

Original comment by sylaan@gmail.com on 1 Aug 2013 at 5:21

[GoogleCodeExporter]

The last_kmg will always hold kernel log information from the last kernel boot 
(except on power failure or when the kernel crashes horribly horribly hard).
Since a soft reboot (hence soft) does not reboot the kernel, but just the 
Android shell, there won't be anything written to the last_kmsg.
If you reboot right after the soft reboot the last_kmsg will be useful.

Original comment by showp1984 on 1 Aug 2013 at 4:46