Closed GoogleCodeExporter closed 9 years ago
If your phone reboots get me /proc/last_kmsg
A logcat is useless in this case.
Original comment by showp1984
on 28 Mar 2013 at 4:30
Sorry. Attached. What about the LED?
Original comment by RusNERD....@gmail.com
on 28 Mar 2013 at 5:54
Attachments:
The kernel log looks clean.
Usually that happens if the device experiences a hardware error (too much uv,
too much oc, loose battery, etc) that causes the device to reset hard.
The LED should be fading out:
[LED]pwm_lut_delayed_fade_out
Since my Sensation got lost at the carrier (when it was sent in for repair) I
have to work solely on logs.
Original comment by showp1984
on 28 Mar 2013 at 6:11
I see. Maybe I made a mistake of getting kernel's logs? I did it as soon as a
sensation left in the reset. Command was executed in the terminal "System tuner
pro" app
-su cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Upon rebooting the battery was 76%. The Stock kernel didn't reboot. The Bricked
1.36 too. Maybe there is another way to check?
See here (sorry for quality) http://youtu.be/4aLxLrVls1E
Steps in video:
I press power button until "screen lock sound"
Wait a few seconds.
Press it again when screen locks and then within 10-20 sec I get dark screen
(no backlight). After this HTC logo etc... ie reboot happen.
As for the indicator, it doesn't fade out. I'm not alone with this trouble. On
analog XDA -dev -> 4pda.ru I asked others, they also have this on viperS 1.6.3
with Bricked and SebastianFM kernels. On Faux all is OK. Can do you check it
somewhere? Thanks.
Original comment by RusNERD....@gmail.com
on 28 Mar 2013 at 10:04
I guess this is because of the updates in 1.4, if it does not work for you use
1.36 (as you have said that it does not reboot) :)
I can't check or fix that without having the device.
Original comment by showp1984
on 28 Mar 2013 at 10:19
I've been thinking. I looked in OC tweaks and saw this.
CFQ 2048kb / interactive mode / min 192Mhz - max 1566Mhz - max screen-off
192Mhz / UV -50mv (minus 50 mv).
Can be reset by max screen-off 192Mhz and UV-50mv? Or dead battery. Its 1.5
years old. What best kernel configuration would you recommend? Thanks.
Original comment by RusNERD....@gmail.com
on 29 Mar 2013 at 9:37
Maxfreq @ 192 is too low. Set at least 486Mhz.
Seems that something is overwriting this on your device, that is probably
what's causing the reboots.
Original comment by showp1984
on 29 Mar 2013 at 4:35
Thanks a lot. I've already changed it . Perhaps the System tuner Pro has
changed preferences. Now it refuses to root access. May I test the kernel for
couple of days and then to write here my result? If it's possible, don't close
this topic, OK?
Original comment by RusNERD....@gmail.com
on 29 Mar 2013 at 5:09
Sure, and you can't really close an issue :) (only delete it, which I have
never done)
Original comment by showp1984
on 29 Mar 2013 at 5:24
All is well, the problem is solved. Reboots are gone. Thanks.
Original comment by RusNERD....@gmail.com
on 2 Apr 2013 at 7:34
np
Original comment by showp1984
on 2 Apr 2013 at 8:58
Original issue reported on code.google.com by
RusNERD....@gmail.com
on 28 Mar 2013 at 8:49Attachments: