Share your experience!
Hi All
Has anybody else experenced the loss of the volume level being displayed on TV screen?
The remote does increase and decrease the volume level but the level is not being displayed on the bottom left of the screen as it did upto 11 July 2017.
i get this with my soundbar turned on, soon as its off the bar is back
I am not sure what tv you have (never heard of XD55 nor 8955) but the volume bar in Android is laggy and also buggy. It may take even 10 seconds to show up some times, and in the worst case even more than a minute (probably because the SystemUI is crashing. At least in Android 7.0. During that time I can't see the volume bar, I can't go into settings, and all things like these).
As a guess, I believe the original post is referring to a TV model KD-55XD8599 ?
If you are having problems especially after a firmware update, the first thing to try is a factory reset of the TV. This can fix many weird and wonderful problems. See instructions HERE.
Cheers
All sorted now I had to just unplug power cable in back on TV leave for a few mins plugged back in hey presto all ok again.
Thanks all for your suggestions.
I did a factory reset some days ago, I sometime unplug the power supply as well, but lately the volume bar doesn't appear for a minute or so even a couple of time (or more) per day.
Funny. Luckily enough It just happened now as well (I swear)! Which would be good because I can check the logcat. But this one shows nothing. I expected to see a crash or something. The logcat shows when we press the volume button, with the new volume level, though:
07-21 10:17:35.761 1260 1361 D audio_hw_primary: index:7 previous volume info:100 6 0 100 100 100 100 100 07-21 10:17:35.761 1260 1361 D audio_hw_primary: change speaker volume:7 07-21 10:17:35.761 1260 1361 D audio_hw_primary: change lineout volume:7 07-21 10:17:35.761 1260 1361 D audio_hw_primary: change subwoofer volume:7 07-21 10:17:35.762 1260 1361 D audio_hw_primary: index:7 previous volume info:100 7 0 100 100 100 100 100 07-21 10:17:35.762 1260 1361 D audio_hw_primary: change speaker volume:7 07-21 10:17:35.762 1260 1361 D audio_hw_primary: change lineout volume:7 07-21 10:17:35.762 1260 1361 D audio_hw_primary: change subwoofer volume:7 07-21 10:17:35.762 1260 1361 D audio_hw_primary: index:7 previous volume info:100 7 0 100 100 100 100 100 07-21 10:17:35.762 1260 1361 D audio_hw_primary: change speaker volume:7 07-21 10:17:35.762 1260 1361 D audio_hw_primary: change lineout volume:7 07-21 10:17:35.762 1260 1361 D audio_hw_primary: change subwoofer volume:7 07-21 10:17:35.763 11629 11704 I chromium: [11629:11704:INFO:media_manager_impl.cc(911)] New audio volume: new=0.07, old=0.06
No, never mind. I think I have found it:
07-21 10:19:34.357 1754 3408 W VolumeController: Error calling dismiss 07-21 10:19:34.357 1754 3408 W VolumeController: android.os.DeadObjectException 07-21 10:19:34.357 1754 3408 W VolumeController: at android.os.BinderProxy.transactNative(Native Method) 07-21 10:19:34.357 1754 3408 W VolumeController: at android.os.BinderProxy.transact(Binder.java:615) 07-21 10:19:34.357 1754 3408 W VolumeController: at android.media.IVolumeController$Stub$Proxy.dismiss(IVolumeController.java:162) 07-21 10:19:34.357 1754 3408 W VolumeController: at com.android.server.audio.AudioService$VolumeController.postDismiss(AudioService.java:6453) 07-21 10:19:34.357 1754 3408 W VolumeController: at com.android.server.audio.AudioService.setVolumeController(AudioService.java:6301) 07-21 10:19:34.357 1754 3408 W VolumeController: at com.android.server.audio.AudioService$4.binderDied(AudioService.java:6310) 07-21 10:19:34.357 1754 3408 W VolumeController: at android.os.BinderProxy.sendDeathNotice(Binder.java:688) 07-21 10:19:34.371 1754 2416 W VolumeController: Error calling volumeChanged 07-21 10:19:34.371 1754 2416 W VolumeController: android.os.DeadObjectException 07-21 10:19:34.371 1754 2416 W VolumeController: at android.os.BinderProxy.transactNative(Native Method) 07-21 10:19:34.371 1754 2416 W VolumeController: at android.os.BinderProxy.transact(Binder.java:615) 07-21 10:19:34.371 1754 2416 W VolumeController: at android.media.IVolumeController$Stub$Proxy.volumeChanged(IVolumeController.java:127) 07-21 10:19:34.371 1754 2416 W VolumeController: at com.android.server.audio.AudioService$VolumeController.postVolumeChanged(AudioService.java:6423) 07-21 10:19:34.371 1754 2416 W VolumeController: at com.android.server.audio.AudioService.sendVolumeUpdate(AudioService.java:1881) 07-21 10:19:34.371 1754 2416 W VolumeController: at com.android.server.audio.AudioService.adjustStreamVolume(AudioService.java:1489) 07-21 10:19:34.371 1754 2416 W VolumeController: at com.android.server.audio.AudioService.adjustSuggestedStreamVolume(AudioService.java:1230) 07-21 10:19:34.371 1754 2416 W VolumeController: at com.android.server.audio.AudioService.adjustSuggestedStreamVolume(AudioService.java:1197) 07-21 10:19:34.371 1754 2416 W VolumeController: at com.android.server.policy.PhoneWindowManager.dispatchDirectAudioEvent(PhoneWindowManager.java:6589) 07-21 10:19:34.371 1754 2416 W VolumeController: at com.android.server.policy.PhoneWindowManager.interceptKeyBeforeDispatching(PhoneWindowManager.java:3748) 07-21 10:19:34.371 1754 2416 W VolumeController: at com.android.server.wm.InputMonitor.interceptKeyBeforeDispatching(InputMonitor.java:417) 07-21 10:19:34.371 1754 2416 W VolumeController: at com.android.server.input.InputManagerService.interceptKeyBeforeDispatching(InputManagerService.java:1871)
Something does seem to crash indeed at Java code level. I initially missed it because it is categorized as a warning instead of an error. It took 2 minutes to the volume bar to show up again.
I believe this log should be escalated to Sony. I mean, it does keep crashing far too often.
Added issue to bugs/issues list:
https://community.sony.co.uk/t5/android-tv/android-tv-bugs-and-issues/m-p/2356882#M20917