topic Re: Cannot setup Chromecast with Google TV remote to control TV "Something went wrong" in Streaming

Cannot setup Chromecast with Google TV remote to control TV "Something went wrong"

palleroy0 — Sun, 21 Jan 2024 22:05:41 GMT

When I originally purchased by Chromecast with Google TV, I was able to set configure it to control the power and volume on my TV. Recently, my TV setup has changed and I needed to change the devices the buttons control. But I am unable to do this.

When I try to "add device" and choose TV, Soundbar, or AV Receiver, all I get is the "Something went wrong" error message and I am unable to add a device.

I factory reset the device today but am experiencing the same issue still. Device is reporting Android TV OS build STTE.230915.005S1.10942527.

Re: Cannot setup Chromecast with Google TV remote to control TV "Something went wrong"

Driftdriven — Thu, 25 Jan 2024 04:44:38 GMT

I have the same problem. I cannot connect my TV or soundbar and keeps saying "something went wrong" but doesn't say what is wrong. Pretty useless statement.

Re: Cannot setup Chromecast with Google TV remote to control TV "Something went wrong"

Carlos_rpg — Thu, 25 Jan 2024 21:50:31 GMT

Same problem. Just bought my CCWGTV with build
STTE.230915.005.s1.10942527 as well.
it seems like a firmware issue that is back or never fixed on the 4k version
https://www.googlenestcommunity.com/t5/Chromecast/set-up-remote-buttons-something-went-wrong/m-p/431130

Re: Cannot setup Chromecast with Google TV remote to control TV "Something went wrong"

Carlos_rpg — Fri, 26 Jan 2024 02:51:50 GMT

Just updating on the same topic. I'm a power user and got ADB working
On windows:
- install chocolatey
- choco install adb
On TV
- Get developer mode clicking on system>buildnumber
-System>Developer Option enable USB debug
On Windows
- adb connect <Chromecast IP>
On TV
- allow USB debug on popup

On Windows

- adb disconnect <IP>

- adb connect <IP>
should be connected with success right now
- adb shell logcat
On TV

- try to add a remote button device (TV, speaker, etc)

I can then see the following log:

01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: Error listing brands 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: bmo: Failure during IRDB call (code cok{code=PERMISSION_DENIED, description=null, cause=null}). 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at bmt.a(PG:7) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at cci.run(PG:4) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at android.os.Handler.handleCallback(Handler.java:938) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at android.os.Handler.dispatchMessage(Handler.java:99) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at android.os.Looper.loopOnce(Looper.java:201) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at android.os.Looper.loop(Looper.java:288) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at android.app.ActivityThread.main(ActivityThread.java:7839) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at java.lang.reflect.Method.invoke(Native Method) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: Caused by: com: PERMISSION_DENIED: The caller does not have permission 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at cok.j(PG:1) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at cyi.h(PG:6) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at cpr.a(PG:2) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at cqj.run(PG:2) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at cvg.run(PG:2) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 01-25 23:42:40.194 6855 6855 E Axel.SelectBrandFragment: at java.lang.Thread.run(Thread.java:920)

Re: Cannot setup Chromecast with Google TV remote to control TV "Something went wrong"

Carlos_rpg — Tue, 30 Jan 2024 02:07:23 GMT

Finally the latest update fixed the issue

Re: Cannot setup Chromecast with Google TV remote to control TV "Something went wrong"

palleroy0 — Tue, 30 Jan 2024 02:09:31 GMT

This Chromecast with Google TV (4K) had an update today to Android TV OS Build STTL.231114.004.11218674. The problem seems to be resolved in this release. I was able to setup a device to be controlled by the remote control. Anyone else confirm it seems resolved for them?

Re: Cannot setup Chromecast with Google TV remote to control TV "Something went wrong"

Kimy — Mon, 05 Feb 2024 01:00:41 GMT

Hi folks,

Just an update. A rollout for the new Android TV OS build, STTL.231114.004, has been released. Kindly update yours, and if it is not available, you may need to factory reset to force it. Let us know how it goes.

Thanks,

Kimy

Re: Cannot setup Chromecast with Google TV remote to control TV "Something went wrong"

Redmumba — Fri, 23 Feb 2024 04:59:30 GMT

Just found this thread; I’m on this latest version, but I’m having a similar issue—trying to add a device immediately goes back to the device screen. No error, but I’m assuming this is the same behavior.

Going to connect using adb when I have a chance.

Re: Cannot setup Chromecast with Google TV remote to control TV "Something went wrong"

Redmumba — Fri, 23 Feb 2024 23:33:52 GMT

This is *stock* Google TV 4K w/ Chromecast, setup a few weeks ago. Attempting to setup the remote by going to Remotes & Accessories > Set up remote buttons > Add Device > selecting either TV, Soundbar, or AV Receiver, results in the following exception:

02-23 15:19:26.787 3519 3519 D AmlogicKeymaster: Received 4 byte response 02-23 15:19:26.787 3519 3519 E AmlogicKeymaster: Response of size 4 contained error code -66 02-23 15:19:26.787 3519 3519 E AmlogicKeymaster: Failed to send cmd 0 err: -66 02-23 15:19:26.788 3518 3518 E keystore2: keystore2::error: In generate_key. 02-23 15:19:26.788 3518 3518 E keystore2: 02-23 15:19:26.788 3518 3518 E keystore2: Caused by: 02-23 15:19:26.788 3518 3518 E keystore2: 0: While generating Key without explicit attestation key. 02-23 15:19:26.788 3518 3518 E keystore2: 1: Error::Km(ErrorCode(-66)) 02-23 15:19:26.791 7233 7233 D AndroidRuntime: Shutting down VM 02-23 15:19:26.793 7233 7233 E AndroidRuntime: FATAL EXCEPTION: main 02-23 15:19:26.793 7233 7233 E AndroidRuntime: Process: com.google.android.tv.axel, PID: 7233 02-23 15:19:26.793 7233 7233 E AndroidRuntime: java.security.ProviderException: Failed to generate key pair. 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.security.keystore2.AndroidKeyStoreKeyPairGeneratorSpi.generateKeyPairHelper(AndroidKeyStoreKeyPairGeneratorSpi.java:620) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.security.keystore2.AndroidKeyStoreKeyPairGeneratorSpi.generateKeyPair(AndroidKeyStoreKeyPairGeneratorSpi.java:545) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at java.security.KeyPairGenerator$Delegate.generateKeyPair(KeyPairGenerator.java:727) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at bng.c(PG:25) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at bng.b(PG:8) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at bni.a(PG:2) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at bmw.c(PG:7) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at bkj.c(PG:3) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at bkg.a(PG:7) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at cje.a(PG:14) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at cdz.H(PG:15) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at cjg.B(PG:1) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at ap.d(PG:160) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at ak.ap(PG:112) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at ak.aq(PG:10) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at ak.ag(PG:8) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at n.run(PG:100) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7839) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: Caused by: android.security.KeyStoreException: Unable to attest device ids 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.security.KeyStore2.getKeyStoreException(KeyStore2.java:356) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.security.KeyStoreSecurityLevel.handleExceptions(KeyStoreSecurityLevel.java:57) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.security.KeyStoreSecurityLevel.generateKey(KeyStoreSecurityLevel.java:145) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: at android.security.keystore2.AndroidKeyStoreKeyPairGeneratorSpi.generateKeyPairHelper(AndroidKeyStoreKeyPairGeneratorSpi.java:587) 02-23 15:19:26.793 7233 7233 E AndroidRuntime: ... 24 more

Android TV OS build: STTL.231114.004.11218674

Re: Cannot setup Chromecast with Google TV remote to control TV "Something went wrong"

Kimy — Mon, 26 Feb 2024 00:33:06 GMT

Hi Redmumba,

Thanks for joining this thread. Different users acknowledged that the “Something went wrong” bug that they’re experiencing has been resolved by the latest patch update. Your case is related to a failure to add devices, but not the exact “Something went wrong” bug. I suggest you do a full clean-up by performing a factory reset and setting it up from scratch to remove any corrupted files or data. Let us know how it goes.

Thanks,

Kimy