Posts: 28
Joined: Aug 2013
Reputation:
0
marson
Junior Member
Posts: 28
I have upgraded to Kodi 15 on my T8 Android box , but when I use the volume up & down , I now have two volume displays at the same time , the Android box & Kodi displays volume on screen together , is there a way to turn one off , has anyone else had this problem , Thanks for any help or info on this
Posts: 5,952
Joined: Sep 2008
Reputation:
201
Koying
Retired Team-Kodi Member
Posts: 5,952
The android volume bar is out of our reach. Removing the update of the Kodi bar for 16 on Android is under consideration.
For 15, no solution (besides skinning hacks, maybe)
Posts: 31,445
Joined: Jan 2011
IMO, we should do what used to be done with linux (not sure if this is still the case). A toggle in settings for volume key control that says volume keys should either control system volume or Kodi volume, and then we only show Kodi volume change when Kodi's volume is changed/has control of volume keys.
Posts: 31,445
Joined: Jan 2011
2015-07-29, 09:51
(This post was last modified: 2015-07-29, 09:59 by Ned Scott.)
Damn, it's no longer there, lol.
Seems it was no longer needed when SDL was dropped for linux, and was removed for Helix.
Posts: 28
Joined: Aug 2013
Reputation:
0
marson
Junior Member
Posts: 28
2015-07-29, 13:20
(This post was last modified: 2015-07-29, 13:48 by marson.)
Is this a problem for all android devices, with the Android box & Kodi displays volume at the same time
Also this has stopped my VideoScreensaver app working , i have it set to start after 3 mins
When my screensaver starts up with two volumes, android volume starts then there is a slight delay before the kodi volume starts , this then shuts down the screensaver
Posts: 5,952
Joined: Sep 2008
Reputation:
201
Koying
Retired Team-Kodi Member
Posts: 5,952
Yes, it's on all android devices.
Obviously, hitting a key cancel the screensaver, so not sure what you mean by "stopped working"
Posts: 28
Joined: Aug 2013
Reputation:
0
marson
Junior Member
Posts: 28
This is without touching the keyboard or remote , its when the screensaver first starts , the screensaver reads the volume in settings as it starts ,but with there being being two and a slight delay between them , this acts as though you have touched the keyboard or remote thus closing the screensaver
Posts: 5,952
Joined: Sep 2008
Reputation:
201
Koying
Retired Team-Kodi Member
Posts: 5,952
A debug log would help...
Posts: 6
Joined: Oct 2010
Reputation:
0
Ok I have a 1G/8G MXIII from ~2014. I think its just about a year old now that it came with 108k4 at stock... 8 here being August.
As like most amlogic S802 Devices... I have had the 1/4 Screen Bug as well. Apparently the trick here is to unpack the boot.img File with something like Android Kitchen, and alter the Permissions needed to run XBMC / Kodi to 666 from inside that, before repacking it up, and flashing it again. Having had somebody else do this for me... (All I originally asked for was to have init.d support), so as to run a script at boot time to make those changes. kodi 15 is now woking on that front.
My beef is now solely with the the way Isengard is handling the Volume's Up, Down, & Mute. I'd really like to see a return to how it was done in 14.2 where Kodi had the full control over the Volume from inside Kodi. As it is now Android has near full control over the Volume, and its breaking my Dolby / DTS Pasthough normaly a Prohibited Sign Passthough in use dialog pops up in these instances. Now if I'm not thinking and I alter the Volume I'm then greeted by some very annoying distortion, until I increase the volume back to 100%
And, the way I'm reading this Thread... You lot have no interest in fixing this until Version 16?!
Ok fine... Then tell me One thing HOW THE [REDACTED] can I continue to use 14.2 (Which actually worked, and works!), and be able to continue to use my Play Store to update my Apps without having to resort to having to install EVERY APP by hand, ONE BY ONE! just to avoid installing this broken v15?! As I can recall I downloaded it here originally, and NOT on Google. AFAICR this is the first ever App I've installed outside of the Playstore that was treated that way. And to be frank I really hate you all for it! I'd have a much greater chance of accepting this had I downloaded the Playstore branch from the start.
But please don't put this Bug off till v16!
Posts: 31,445
Joined: Jan 2011