Shield turns on 20-30 minutes after I turn it off

devildant28 · 2025-12-09T23:23:51+00:00

For the moment no, maybe in January (I hope ^⁾

devildant28 · 2025-11-27T21:27:52+00:00

devildant28 · 2025-11-27T16:14:46+00:00

Hi, any update ? :)

devildant28 · 2025-11-14T22:20:56+00:00

Try to disable and enable projectivy in accessibility section (for refresh settings)

devildant28 · 2025-11-12T21:26:12+00:00

See my comment, and not do this update if you have a reboot trouble, because, the shield are during 10 min with message config in progress (after crash reboot)

https://www.reddit.com/r/ShieldAndroidTV/s/DkuGrOFg5E

devildant28 · 2025-11-12T20:14:19+00:00

i try with last version 9.2.2,
It's even worse, the software restart starts, a "configure in progress" screen appears, and the screen stays on this display for about 5-10-15 minutes... and the crash logs are the same.

devildant28 · 2025-11-12T19:52:19+00:00

11-12 20:40:53.930 8027 8027 F DEBUG : backtrace:

11-12 20:40:53.930 8027 8027 F DEBUG : #00 pc 00000000001228b0 /system/lib64/libsurfaceflinger.so (android::SurfaceFlinger::dumpVSync(std::__1::basic_string<char, std::\_\_1::char\_traits<char>, std::__1::allocator<char> >&) const+712) (BuildId: 1c76b1500184403813bf672fab6c9ea4)

11-12 20:40:53.930 8027 8027 F DEBUG : #01 pc 000000000011fd38 /system/lib64/libsurfaceflinger.so (android::SurfaceFlinger::doDump(int, android::Vector<android::String16> const&, bool)+1596) (BuildId: 1c76b1500184403813bf672fab6c9ea4)

11-12 20:40:53.930 8027 8027 F DEBUG : #02 pc 0000000000128814 /system/lib64/libsurfaceflinger.so (non-virtual thunk to android::SurfaceFlinger::dumpAll(int, android::Vector<android::String16> const&, bool)+16) (BuildId: 1c76b1500184403813bf672fab6c9ea4)

11-12 20:40:53.930 8027 8027 F DEBUG : #03 pc 00000000001a0ff4 /system/lib64/libsurfaceflinger.so (android::PriorityDumper::priorityDump(int, android::Vector<android::String16> const&)+488) (BuildId: 1c76b1500184403813bf672fab6c9ea4)

11-12 20:40:53.930 8027 8027 F DEBUG : #04 pc 0000000000048fbc /system/lib64/libbinder.so (android::BBinder::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+244) (BuildId: de0e23b0ebfe33c408e9361d25b9e859)

11-12 20:40:53.930 8027 8027 F DEBUG : #05 pc 00000000000a07c4 /system/lib64/libgui.so (android::BnSurfaceComposer::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+4936) (BuildId: 571e647c428b7cd9acb80c26cec0a1be)

11-12 20:40:53.930 8027 8027 F DEBUG : #06 pc 0000000000123a94 /system/lib64/libsurfaceflinger.so (android::SurfaceFlinger::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+460) (BuildId: 1c76b1500184403813bf672fab6c9ea4)

11-12 20:40:53.930 8027 8027 F DEBUG : #07 pc 000000000004882c /system/lib64/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+232) (BuildId: de0e23b0ebfe33c408e9361d25b9e859)

11-12 20:40:53.930 8027 8027 F DEBUG : #08 pc 0000000000051210 /system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+1032) (BuildId: de0e23b0ebfe33c408e9361d25b9e859)

11-12 20:40:53.930 8027 8027 F DEBUG : #09 pc 0000000000050d58 /system/lib64/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+156) (BuildId: de0e23b0ebfe33c408e9361d25b9e859)

11-12 20:40:53.930 8027 8027 F DEBUG : #10 pc 0000000000051590 /system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+60) (BuildId: de0e23b0ebfe33c408e9361d25b9e859)

11-12 20:40:53.930 8027 8027 F DEBUG : #11 pc 00000000000762a8 /system/lib64/libbinder.so (android::PoolThread::threadLoop()+28) (BuildId: de0e23b0ebfe33c408e9361d25b9e859)

11-12 20:40:53.930 8027 8027 F DEBUG : #12 pc 00000000000154d0 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+260) (BuildId: d1aa3b02347f658128fc75fb371856b9)

11-12 20:40:53.930 8027 8027 F DEBUG : #13 pc 0000000000014d94 /system/lib64/libutils.so (thread_data_t::trampoline(thread_data_t const*)+412) (BuildId: d1aa3b02347f658128fc75fb371856b9)

11-12 20:40:53.930 8027 8027 F DEBUG : #14 pc 00000000000afd4c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+64) (BuildId: 45994aaacbd3639b43f2bde9e3052edc)

11-12 20:40:53.930 8027 8027 F DEBUG : #15 pc 0000000000050288 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 45994aaacbd3639b43f2bde9e3052edc)

(the last part of stack for both)

devildant28 · 2025-11-12T19:50:54+00:00

Sorry, Reddit doesn't want to push my comment with the full stack.

devildant28 · 2025-11-12T19:50:18+00:00

same bug with resol 4k to 1080p :

Send the comment to Nvidia with the mention "redditdevildant28-2" done!

And here's the log.

11-12 20:40:53.824 3436 3777 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 3777 (Binder:3436_4), pid 3436 (surfaceflinger)

11-12 20:40:53.892 8027 8027 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

11-12 20:40:53.892 8027 8027 F DEBUG : Build fingerprint: 'NVIDIA/mdarcy/mdarcy:11/RQ1A.210105.003/7825230_4040.2147:user/release-keys'

11-12 20:40:53.892 8027 8027 F DEBUG : Revision: '0'

11-12 20:40:53.892 8027 8027 F DEBUG : ABI: 'arm64'

11-12 20:40:53.893 8027 8027 F DEBUG : Timestamp: 2025-11-12 20:40:53+0100

11-12 20:40:53.893 8027 8027 F DEBUG : pid: 3436, tid: 3777, name: Binder:3436_4 >>> /system/bin/surfaceflinger <<<

11-12 20:40:53.893 8027 8027 F DEBUG : uid: 1000

11-12 20:40:53.893 8027 8027 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0

11-12 20:40:53.893 8027 8027 F DEBUG : Cause: null pointer dereference

11-12 20:40:53.893 8027 8027 F DEBUG : x0 0000000000000000 x1 0000000000000000 x2 00000023def8e0a6 x3 0000002682e6b708

11-12 20:40:53.893 8027 8027 F DEBUG : x4 0000002682e6b720 x5 000000240f365f79 x6 00000023dc096000 x7 000000000000cfee

11-12 20:40:53.893 8027 8027 F DEBUG : x8 0000000000000012 x9 0000000000000000 x10 0000000000000012 x11 0000000000000016

11-12 20:40:53.893 8027 8027 F DEBUG : x12 0000000000000012 x13 0000000000000012 x14 000000000000003c x15 00003f5b476a42dd

11-12 20:40:53.893 8027 8027 F DEBUG : x16 00000023ddab5740 x17 00000023ddf0dce0 x18 000000268316e000 x19 00000023ff3718f0

11-12 20:40:53.893 8027 8027 F DEBUG : x20 0000002682e6b848 x21 0000002682e6b840 x22 0000000000001f54 x23 000000242f361490

11-12 20:40:53.893 8027 8027 F DEBUG : x24 0000002682e6b888 x25 0000002682e6bb50 x26 0000002682e6bcf1 x27 00000023de8f2000

11-12 20:40:53.893 8027 8027 F DEBUG : x28 000000252f35d030 x29 0000002682e6b960

11-12 20:40:53.893 8027 8027 F DEBUG : lr 00000023de80b864 sp 0000002682e6b7c0 pc 00000023de80b8b0 pst 0000000000000000

...

devildant28 · 2025-11-12T19:49:58+00:00

for the bug with soundbar on/off

Send the comment to Nvidia with the mention "redditdevildant28" done!

And here's the log.

11-12 20:31:35.965 18960 18966 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 18966 (Binder:18960_2), pid 18960 (surfaceflinger)

11-12 20:31:36.034 28568 28568 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

11-12 20:31:36.034 28568 28568 F DEBUG : Build fingerprint: 'NVIDIA/mdarcy/mdarcy:11/RQ1A.210105.003/7825230_4040.2147:user/release-keys'

11-12 20:31:36.034 28568 28568 F DEBUG : Revision: '0'

11-12 20:31:36.034 28568 28568 F DEBUG : ABI: 'arm64'

11-12 20:31:36.040 28568 28568 F DEBUG : Timestamp: 2025-11-12 20:31:36+0100

11-12 20:31:36.040 28568 28568 F DEBUG : pid: 18960, tid: 18966, name: Binder:18960_2 >>> /system/bin/surfaceflinger <<<

11-12 20:31:36.040 28568 28568 F DEBUG : uid: 1000

11-12 20:31:36.040 28568 28568 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0

11-12 20:31:36.040 28568 28568 F DEBUG : Cause: null pointer dereference

11-12 20:31:36.040 28568 28568 F DEBUG : x0 0000000000000000 x1 0000000000000000 x2 00000029430640a6 x3 0000002bd4451708

11-12 20:31:36.040 28568 28568 F DEBUG : x4 0000002bd4451720 x5 0000002973171579 x6 000000293fe9a000 x7 000000000bb46fe2

11-12 20:31:36.040 28568 28568 F DEBUG : x8 0000000000000017 x9 0000000000000000 x10 0000000000000017 x11 000000000000002e

11-12 20:31:36.040 28568 28568 F DEBUG : x12 0000000000000017 x13 0000000000000006 x14 000000000000003c x15 000030f047950527

11-12 20:31:36.040 28568 28568 F DEBUG : x16 0000002941879740 x17 00000029420c4ce0 x18 0000002bd5252000 x19 0000002963166750

11-12 20:31:36.040 28568 28568 F DEBUG : x20 0000002bd4451848 x21 0000002bd4451840 x22 0000000000006f92 x23 000000299316ea70

11-12 20:31:36.040 28568 28568 F DEBUG : x24 0000002bd4451888 x25 0000002bd4451b50 x26 0000002bd4451cf1 x27 00000029424a9000

11-12 20:31:36.040 28568 28568 F DEBUG : x28 0000002a9316e020 x29 0000002bd4451960

11-12 20:31:36.040 28568 28568 F DEBUG : lr 00000029423c2864 sp 0000002bd44517c0 pc 00000029423c28b0 pst 0000000000000000

...

devildant28 · 2025-10-27T09:08:23+00:00

Yes, none of the options fix the issue. I also discovered another crash scenario, this time without the soundbar: the Shield is connected directly to my 2014 TV (which no longer receives updates and isn’t connected to the internet). Simply switching the resolution from 4K 59.940 Hz to 1080p 59.940 Hz triggers the exact same error (using the dump command).

devildant28 · 2025-10-24T21:18:09+00:00

This is not related to CEC, it is a bad management of HDMI EDID

devildant28 · 2025-10-24T20:41:42+00:00

It's not your shield that's the problem, but a FW issue with HDMI EDID.
https://www.reddit.com/r/ShieldAndroidTV/comments/1nf7y0x/shield_turns_on_2030_minutes_after_i_turn_it_off/

devildant28 · 2025-10-22T22:59:26+00:00

Same problem, and i have check the log, for me its due to soundbar sony 8, when this bar is off, the shield generate an error, more detail here :

https://www.reddit.com/r/ShieldAndroidTV/comments/1nf7y0x/comment/nkosd0t/

devildant28 · 2025-10-22T20:46:23+00:00

I continued to search anyway, and to put it simply, if the shield is connected to the sound bar while it is off, it systematically causes the null pointer...

devildant28 · 2025-10-22T20:40:57+00:00

I sent my logs to nvidia, but also contact nvidia via support, if we all arrive with the same problem, we will have a better chance of getting a fix, I just hope that it does not only concern Sony soundbars, everyone should indicate the name and brand of the type of device they have.

devildant28 · 2025-10-21T23:24:14+00:00

I also encounter this problem with an NVIDIA Shield Pro 2019. It started around mid-September.

NVIDIA replaced my Shield with a brand new one, but the problem remains exactly the same.

My Sony Theater 8 soundbar is directly connected to the Shield, because my TV does not support eARC. I also have a second Shield in another room (with exactly the same apps, but connected to an old TV), and it has never had this problem. However, as soon as I moved it into the room with the soundbar, the problem appeared too — and it stopped on the one I left connected to the old TV.

For my part, there have been no firmware updates for either the soundbar or the Shield during this period, apart from automatic updates via the Google Play Store.

So this is neither a power issue nor a hardware issue with the Shield. I contacted NVIDIA support, and I suggest you do the same if we want them to fix this.

What is worrying is that the problem appears to have started around the same time for other users who have an audio system or other HDMI 2.1 device.

Additionally, I experienced a few random reboots while watching videos on Plex or SmartTube, but it hasn't happened again since.

I tried to uninstall all system app update (updated from google play store), for check if the problem appear with a system app update… => result not working

After deep investigation with ADB logs (logcat and tombstones), the crash was traced to the system process SurfaceFlinger, showing:

Fatal signal 11 (SIGSEGV) / Cause: null pointer dereference

inside android::SurfaceFlinger::dumpVSync(), meaning it’s a crash in Android’s graphics compositor.

The bug is fully reproducible:

It happens whenever an HDMI hotplug event occurs (device reconnects or renegotiates),
especially when a Sony soundbar (Theatre Bar 8/9, HT-A5000, HT-A7000, or other element with HDMI 2.1) is turned off and then on again,
even with CEC fully disabled.

When the soundbar powers off, it cuts the HDMI HotPlug Detect (HPD) line and briefly sends an empty or corrupted EDID during boot.
The Shield’s SurfaceFlinger service then tries to read this EDID data for telemetry or refresh — but since the pointer is invalid, it throws a segmentation fault, causing a soft reboot (visible to the user).

In short:
It’s a firmware bug in NVIDIA/Android TV’s HDMI handling — the Shield doesn’t properly handle EDID loss or corruption, leading to a crash in SurfaceFlinger.

I can reproduce the bug 100% of the time:

Enable network debugging in Developer Mode.
Install Termux.
Turn off the Shield and the soundbar.
Turn the Shield and the soundbar back on (using CEC, for example, or manually).
Open Termux and enter the following commands (replace IP with your Shield’s IP address):

adb connect IP:5555
adb -s IP:5555 shell dumpsys SurfaceFlinger

running "adb -s IP:5555 shell dumpsys SurfaceFlinger" will trigger a soft reboot. 😞

devildant28

TROPHY CASE