Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Nexus 10 - Waking up from sleep when charging using pogo cable

OP mnemonics

13th April 2014, 04:47 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: Apr 2014
Hello all,

I hope anyone can assist with this problem I'm having with my nexus 10. I have looked in the forum but could not find anyone with similar issue.

My device

Nexus 10 running KitKat 4.4.2 build KOT49H

Problem

When I'm charging my device using the pogo cable, if I turn the device to sleep (pressing the power button once), leaving it in sleep mode anywhere from 5 seconds to 1 minute, it sometimes doesn't want to turn on. The problem happens randomly not all the time. At times, I can just unplugged the pogo cable and it would immediately turn on. Other times, the device would restart by itself or I would have to long press the power button until it restarts itself.

I also noticed that if I turn on the "Screen lock sound" under "Sound", at random times it would make a humming noise before it restarts itself and the screen would flicker.

What I have tried

1) If I use the micro usb cable, this works fine. No crashes/restart/weird humming noise i.e. works normally when I charge with the micro usb

2) Flash the roms from 4.2.2 to the latest version 4.4.2 via Factory Images for Nexus Devices page on Google Developers. All versions have this issue except for maybe 4.3 (tried to do the sleep / wake up tests a few times it works fine).

3) I cannot figure out how to give the log output just before the device restarts itself. The log would reset itself (I'm using ADT). Maybe someone can shed some light on how to do this.

Is my pogo cable damage? To be honest I haven't noticed this issue until about a month ago. Hope anyone can help me out with this. Thanks!
13th April 2014, 06:08 PM   |  #2  
lj50036's Avatar
Recognized Contributor
Flag Muti-Verse
Thanks Meter: 1,632
 
2,057 posts
Join Date:Joined: Feb 2013
Donate to Me
More
Quote:
Originally Posted by mnemonics

Hello all,

I hope anyone can assist with this problem I'm having with my nexus 10. I have looked in the forum but could not find anyone with similar issue.

My device

Nexus 10 running KitKat 4.4.2 build KOT49H

Problem

When I'm charging my device using the pogo cable, if I turn the device to sleep (pressing the power button once), leaving it in sleep mode anywhere from 5 seconds to 1 minute, it sometimes doesn't want to turn on. The problem happens randomly not all the time. At times, I can just unplugged the pogo cable and it would immediately turn on. Other times, the device would restart by itself or I would have to long press the power button until it restarts itself.

I also noticed that if I turn on the "Screen lock sound" under "Sound", at random times it would make a humming noise before it restarts itself and the screen would flicker.

What I have tried

1) If I use the micro usb cable, this works fine. No crashes/restart/weird humming noise i.e. works normally when I charge with the micro usb

2) Flash the roms from 4.2.2 to the latest version 4.4.2 via Factory Images for Nexus Devices page on Google Developers. All versions have this issue except for maybe 4.3 (tried to do the sleep / wake up tests a few times it works fine).

3) I cannot figure out how to give the log output just before the device restarts itself. The log would reset itself (I'm using ADT). Maybe someone can shed some light on how to do this.

Is my pogo cable damage? To be honest I haven't noticed this issue until about a month ago. Hope anyone can help me out with this. Thanks!

After it will not turn on for you, let it do its thing, than once you get it to turn on, power it off and let it boot back into rom, once there run

This from command prompt.. on your PC

Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory on your PC

Post this so I can take a look

THx Josh
13th April 2014, 08:53 PM   |  #3  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: Apr 2014
Post
Quote:
Originally Posted by lj50036

After it will not turn on for you, let it do its thing, than once you get it to turn on, power it off and let it boot back into rom, once there run

This from command prompt.. on your PC

Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory on your PC

Post this so I can take a look

THx Josh

EDIT: Does my device need to be rooted to do this?

Attached are the files. Interestingly the last_kmesg file has this:

Quote:

[ 144.113910] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0
[ 144.114092] Backtrace:
[ 144.114295] [<c0012bf8>] (dump_backtrace+0x0/0x10c) from [<c062f240>] (dump_stack+0x18/0x1c)
[ 144.114392] r6:de85c000 r5:c0868f80 r4:c08db980 r3:00000001
[ 144.114844] [<c062f228>] (dump_stack+0x0/0x1c) from [<c062f388>] (panic+0x90/0x1e0)
[ 144.115019] [<c062f2f8>] (panic+0x0/0x1e0) from [<c00a1044>] (watchdog_timer_fn+0x2bc/0x304)
[ 144.115115] r3:00000001 r2:01266000 r1:00000000 r0:c076d558
[ 144.115608] r7:c0868f80
[ 144.115792] [<c00a0d88>] (watchdog_timer_fn+0x0/0x304) from [<c0057008>] (__run_hrtimer+0x70/0x23c)
[ 144.115962] [<c0056f98>] (__run_hrtimer+0x0/0x23c) from [<c0057ff0>] (hrtimer_interrupt+0x128/0x2c4)
[ 144.116140] [<c0057ec8>] (hrtimer_interrupt+0x0/0x2c4) from [<c0023b90>] (exynos4_mct_tick_isr+0x48/0x68)
[ 144.116316] [<c0023b48>] (exynos4_mct_tick_isr+0x0/0x68) from [<c00a1c68>] (handle_irq_event_percpu+0x64/0x2b0)
[ 144.116481] r5:c084d510 r4:c0879d80
[ 144.116747] [<c00a1c04>] (handle_irq_event_percpu+0x0/0x2b0) from [<c00a1ef8>] (handle_irq_event+0x44/0x64)
[ 144.116920] [<c00a1eb4>] (handle_irq_event+0x0/0x64) from [<c00a4920>] (handle_fasteoi_irq+0xa0/0x160)
[ 144.117085] r6:de85c000 r5:c084d510 r4:c084d4c0 r3:00000000
[ 144.117527] [<c00a4880>] (handle_fasteoi_irq+0x0/0x160) from [<c00a1568>] (generic_handle_irq+0x2c/0x40)
[ 144.117692] r5:c08432a4 r4:c0868f80
[ 144.117965] [<c00a153c>] (generic_handle_irq+0x0/0x40) from [<c000f7f4>] (handle_IRQ+0x54/0xb8)
[ 144.118135] [<c000f7a0>] (handle_IRQ+0x0/0xb8) from [<c0008520>] (gic_handle_irq+0x2c/0x60)
[ 144.118295] r8:00000001 r7:de85dedc r6:de85dea8 r5:c0868460 r4:f8810000
[ 144.118718] r3:c0075f5c
[ 144.118977] [<c00084f4>] (gic_handle_irq+0x0/0x60) from [<c000eb00>] (__irq_svc+0x40/0x70)
[ 144.119072] Exception stack(0xde85dea8 to 0xde85def0)
[ 144.119242] dea0: 3b9ac9ff 534afc23 00c4a919 000312a4 c1aaf370 00000000
[ 144.119343] dec0: c1aaf370 c041afe0 00000001 c0878aa8 c0992fb4 de85df14 534afc23 de85def0
[ 144.119511] dee0: c0075f5c c0022cd0 200e0013 ffffffff
[ 144.119672] r6:ffffffff r5:200e0013 r4:c0022cd0 r3:c0075f5c
[ 144.120108] [<c0022c9c>] (exynos_enter_idle+0x0/0x68) from [<c041affc>] (cpuidle_enter+0x1c/0x20)
[ 144.120272] r5:00000021 r4:8d5446a1
[ 144.120537] [<c041afe0>] (cpuidle_enter+0x0/0x20) from [<c041b708>] (cpuidle_wrap_enter+0x3c/0x9c)
[ 144.120705] [<c041b6cc>] (cpuidle_wrap_enter+0x0/0x9c) from [<c041b018>] (cpuidle_enter_tk+0x18/0x1c)
[ 144.120868] r7:c08c6c90 r6:c1aaf370 r5:00000000 r4:c1aaf370
[ 144.121301] [<c041b000>] (cpuidle_enter_tk+0x0/0x1c) from [<c041b280>] (cpuidle_enter_state+0x1c/0x78)
[ 144.121473] [<c041b264>] (cpuidle_enter_state+0x0/0x78) from [<c041b3bc>] (cpuidle_idle_call+0xe0/0x31c)
[ 144.121638] r6:de85c000 r5:00000000 r4:c1aaf370 r3:0000004c
[ 144.122080] [<c041b2dc>] (cpuidle_idle_call+0x0/0x31c) from [<c000fe5c>] (cpu_idle+0xa4/0x10c)
[ 144.122257] [<c000fdb8>] (cpu_idle+0x0/0x10c) from [<c062c454>] (secondary_start_kernel+0x124/0x144)
[ 144.122430] [<c062c330>] (secondary_start_kernel+0x0/0x144) from [<4062be14>] (0x4062be14)
[ 144.122592] r5:00000015 r4:5e84806a
[ 144.122858] CPU0: stopping
[ 144.122947] Backtrace:
[ 144.123191] [<c0012bf8>] (dump_backtrace+0x0/0x10c) from [<c062f240>] (dump_stack+0x18/0x1c)
[ 144.123282] r6:c0868f80 r5:c0868460 r4:00000000 r3:c088d4ac
[ 144.123693] [<c062f228>] (dump_stack+0x0/0x1c) from [<c0015454>] (handle_IPI+0x190/0x1c4)
[ 144.123852] [<c00152c4>] (handle_IPI+0x0/0x1c4) from [<c000854c>] (gic_handle_irq+0x58/0x60)
[ 144.123948] [<c00084f4>] (gic_handle_irq+0x0/0x60) from [<c000ecc0>] (__irq_usr+0x40/0x60)
[ 144.124100] Exception stack(0xdd119fb0 to 0xdd119ff8)
[ 144.124186] 9fa0: 75f286b0 00000022 6d627f70 00000007
[ 144.124341] 9fc0: 6e59b164 6d4858a0 4151b408 000010f8 41539cc0 41979458 6d48588c 419a9bc8
[ 144.124499] 9fe0: 000000f8 be93b638 00000000 4153dae4 200b0010 ffffffff
[ 144.124585] r6:ffffffff r5:200b0010 r4:4153dae4 r3:75f286b0
[ 144.125053] CPU1 DBGPCSR: ffffffff
[ 144.125139] CPU1 PC: <fffffffa> 0xfffffffa
[ 144.125288] Rebooting in 5 seconds..
[ 149.115359] Restarting Linux version 3.4.39-g5b5c8df (android-build@vpbs1.mtv.corp.google.com) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Nov 20 15:12:05 PST 2013
[ 149.115370]

No errors detected
Last reset was software reset (RST_STAT=0x20000000)

Attached Files
File Type: txt dmesg.txt - [Click for QR Code] (51.4 KB, 1 views)
File Type: txt last_kmsg.txt - [Click for QR Code] (50.3 KB, 2 views)
Last edited by mnemonics; 13th April 2014 at 11:17 PM. Reason: Added files
15th April 2014, 11:31 AM   |  #4  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: Apr 2014
Quote:
Originally Posted by mnemonics

EDIT: Does my device need to be rooted to do this?

Attached are the files. Interestingly the last_kmesg file has this:

Anyone?
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes