View Full Version : [GI-XPEED LX3] Volume turning itself down
I'm seeing a really strange one here - the volume on my LX3 seems to turn itself down randomly!
I thought it was the mrs or my little girl turning it down while I was out but I'm just sat watching TV and can see the box appearing.
No remotes will be touched and the volume bar will appear and turn down a notch.
I've taken the batteries out of the remote and it's still doing it!
I'm currently sat here with tail running against the debug log and you see events where the volume turns down.
For example:
< 2190.794> [eInputDeviceInit] 1 72 1
< 2190.795> [InfoBarGenerics] KEY: 114
< 2190.795> [ActionMap] GlobalActions volumeDown
< 2190.795> [eDVBVolumecontrol] Setvolume: raw: 95 95, -1db: 4 4
< 2190.796> [Volume] setValue 95
< 2190.797> [eInputDeviceInit] 0 72 1
< 2190.798> [InfoBarGenerics] KEY: 114
< 2306.433> [eInputDeviceInit] 1 72 1
< 2306.434> [InfoBarGenerics] KEY: 114
< 2306.434> [ActionMap] GlobalActions volumeDown
< 2306.434> [eDVBVolumecontrol] Setvolume: raw: 90 90, -1db: 7 7
< 2306.436> [Volume] setValue 90
< 2306.436> [eInputDeviceInit] 0 72 1
< 2306.437> [InfoBarGenerics] KEY: 114
< 2306.724> [eInputDeviceInit] 1 72 1
< 2306.725> [InfoBarGenerics] KEY: 114
< 2306.726> [ActionMap] GlobalActions volumeDown
< 2306.726> [eDVBVolumecontrol] Setvolume: raw: 85 85, -1db: 10 10
< 2306.727> [Volume] setValue 85
< 2306.774> [eInputDeviceInit] 0 72 1
< 2306.775> [InfoBarGenerics] KEY: 114
< 2948.057> [eInputDeviceInit] 1 72 1
< 2948.058> [InfoBarGenerics] KEY: 114
< 2948.058> [ActionMap] GlobalActions volumeDown
< 2948.058> [eDVBVolumecontrol] Setvolume: raw: 80 80, -1db: 13 13
< 2948.059> [Volume] setValue 80
< 2948.060> [eInputDeviceInit] 0 72 1
< 2948.061> [InfoBarGenerics] KEY: 114
< 3118.657> [eInputDeviceInit] 1 72 1
< 3118.658> [InfoBarGenerics] KEY: 114
< 3118.658> [ActionMap] GlobalActions volumeDown
< 3118.658> [eDVBVolumecontrol] Setvolume: raw: 75 75, -1db: 16 16
< 3118.659> [Volume] setValue 75
< 3118.747> [eInputDeviceInit] 0 72 1
< 3118.748> [InfoBarGenerics] KEY: 114
< 3158.581> [eInputDeviceInit] 1 72 1
< 3158.582> [InfoBarGenerics] KEY: 114
< 3158.582> [ActionMap] GlobalActions volumeDown
< 3158.582> [eDVBVolumecontrol] Setvolume: raw: 70 70, -1db: 19 19
< 3158.583> [Volume] setValue 70
< 3158.701> [eInputDeviceInit] 0 72 1
< 3158.702> [InfoBarGenerics] KEY: 114
< 3286.191> [eInputDeviceInit] 1 72 1
< 3286.192> [InfoBarGenerics] KEY: 114
< 3286.192> [ActionMap] GlobalActions volumeDown
< 3286.192> [eDVBVolumecontrol] Setvolume: raw: 65 65, -1db: 23 23
< 3286.193> [Volume] setValue 65
< 3286.301> [eInputDeviceInit] 0 72 1
< 3286.302> [InfoBarGenerics] KEY: 114
< 3288.061> [eInputDeviceInit] 1 72 1
< 3288.061> [InfoBarGenerics] KEY: 114
< 3288.062> [ActionMap] GlobalActions volumeDown
< 3288.062> [eDVBVolumecontrol] Setvolume: raw: 60 60, -1db: 26 26
< 3288.062> [Volume] setValue 60
< 3288.131> [eInputDeviceInit] 0 72 1
< 3288.131> [InfoBarGenerics] KEY: 114
It's really strange as in there you can see at one point there's an exactly 30 seconds then 40 second gap between the events which would suggest it's not random enough to be a remote misfiring.
No other remotes are being touched when this happens and there are no active OpenWebif connections.
Any ideas please?
I've got a debug log attached below:
53881
Are you sure you don't have a port forwarded on your router?
Definitely nothing can access from the internet at the moment and it's still happening - it's bonkers!
I can't see a difference in the debug log though from a real remote press to a remote press in OpenWebIf which makes it harder to work out if it's a physical IR command or a command in the box.
Does OpenWebif have a log anywhere I can see if it's being hit that way please?
I've shutdown NCam too just in case that's doing something random (clutching at straws!)
If I can work out port mirroring on the switch I guess I can see if something is sending a command over the network (and if so what!)
Actually I'm not thinking straight with my hangover - I've shut the network port down so will see if it happens then as that will prove if it's something external to the box
If it's something external then you have a security issue. This can affect more than just your STB, so be cautious with port forwarding. You really need a VPN to handle remote access to the STB.
Or else you have a compatible IR remote somewhere else in the room (under the cushions!) and it's being accidentally pressed.
Do you have any other remote controls (for anything) in the room?
Are you sure you don't have a port forwarded on your router?From what I can see any volume change via OpenWebIF doesn't report any "[ActionMap] GlobalActions volumeDown" entry. so it won't be that.
From what I can see any volume change via OpenWebIF doesn't report any "[ActionMap] GlobalActions volumeDown" entry. so it won't be that.
Thanks, tried again and I'm seeing the line "[eInputDeviceInit] 0 72 1" missing when changing the volume via the OpenWebIf virtual remote - as that is in the log it is suggesting it's coming in the IR sensor. I do seem to get that ActionMap command on this box though when done via the virtual remote.
Silly question but do the IR sensors ever go wrong?
I've moved all the remotes out of the room for now to see what happens - this is definitely a random one :)
Bizarrely it seems it could be NCam 1.5 doing this.
It turned out earlier that even though I had stopped it in the softcam manager it was getting restarted again by something when the launch at startup flag was set.
Not sure why it's triggering after a manual stop though but I noticed it was there in the process list.
While NCam was stopped the volume didn't change for over 15 minutes - as soon as NCam was started it changed within seconds!
Looks like it's back to Oscam for now to see if that triggers it :)
Actually no scratch that - NCam has been stopped and I'm watching an IPTV stream and it's done it again multiple times.
It seems it just takes longer to happen when a cam isn't running!
< 8708.058> [eDVBVolumecontrol] Setvolume: raw: 100 100, -1db: 0 0
< 8708.058> [Volume] setValue 100
< 9747.509> [eDVBVolumecontrol] Setvolume: raw: 95 95, -1db: 4 4
< 9747.510> [Volume] setValue 95
< 9879.337> [eDVBVolumecontrol] Setvolume: raw: 90 90, -1db: 7 7
< 9879.338> [Volume] setValue 90
< 10029.057> [eDVBVolumecontrol] Setvolume: raw: 85 85, -1db: 10 10
< 10029.058> [Volume] setValue 85
Is anyone else here using the Xtream Player IPTV plugin? Wondering if maybe it's that doing something weird.
I'm leaving the box on BBC 1 HD for the night with nothing running to see how that goes - if it's still doing it overnight I guess I'll try a fresh build to see if it does the same thing.
I do seem to get that ActionMap command on this box though when done via the virtual remote.Ah, yes - so do I. I was just using the volume slider rather than the virtual remote.
OK so the box has been sat all night with no plugins running, no cams and tuned to BBC One HD and it's slowly turned the volume off overnight!
There were no batteries in the remote either - this is bonkers :D
The box is running 5.0.016 now as it's been updated again after that was fixed and still the same.
< 11351.560> [eDVBVolumecontrol] Setvolume: raw: 100 100, -1db: 0 0
< 11351.561> [Volume] setValue 100
< 11575.173> [eDVBVolumecontrol] Setvolume: raw: 95 95, -1db: 4 4
< 11575.175> [Volume] setValue 95
< 12519.531> [eDVBVolumecontrol] Setvolume: raw: 90 90, -1db: 7 7
< 12519.532> [Volume] setValue 90
< 16110.710> [eDVBVolumecontrol] Setvolume: raw: 85 85, -1db: 10 10
< 16110.711> [Volume] setValue 85
< 18485.367> [eDVBVolumecontrol] Setvolume: raw: 80 80, -1db: 13 13
< 18485.368> [Volume] setValue 80
< 19839.550> [eDVBVolumecontrol] Setvolume: raw: 75 75, -1db: 16 16
< 19839.551> [Volume] setValue 75
< 20561.251> [eDVBVolumecontrol] Setvolume: raw: 70 70, -1db: 19 19
< 20561.252> [Volume] setValue 70
< 22638.401> [eDVBVolumecontrol] Setvolume: raw: 65 65, -1db: 23 23
< 22638.402> [Volume] setValue 65
< 25682.892> [eDVBVolumecontrol] Setvolume: raw: 60 60, -1db: 26 26
< 25682.893> [Volume] setValue 60
< 26043.209> [eDVBVolumecontrol] Setvolume: raw: 55 55, -1db: 29 29
< 26043.210> [Volume] setValue 55
< 26575.775> [eDVBVolumecontrol] Setvolume: raw: 50 50, -1db: 32 32
< 26575.777> [Volume] setValue 50
< 27017.376> [eDVBVolumecontrol] Setvolume: raw: 45 45, -1db: 35 35
< 27017.377> [Volume] setValue 45
< 27129.755> [eDVBVolumecontrol] Setvolume: raw: 40 40, -1db: 38 38
< 27129.756> [Volume] setValue 40
< 27645.781> [eDVBVolumecontrol] Setvolume: raw: 35 35, -1db: 41 41
< 27645.782> [Volume] setValue 35
< 30815.766> [eDVBVolumecontrol] Setvolume: raw: 30 30, -1db: 45 45
< 30815.768> [Volume] setValue 30
< 32115.524> [eDVBVolumecontrol] Setvolume: raw: 25 25, -1db: 48 48
< 32115.525> [Volume] setValue 25
< 33566.751> [eDVBVolumecontrol] Setvolume: raw: 20 20, -1db: 51 51
< 33566.753> [Volume] setValue 20
< 36583.364> [eDVBVolumecontrol] Setvolume: raw: 15 15, -1db: 54 54
< 36583.365> [Volume] setValue 15
< 39063.595> [eDVBVolumecontrol] Setvolume: raw: 10 10, -1db: 57 57
< 39063.596> [Volume] setValue 10
< 43499.145> [eDVBVolumecontrol] Setvolume: raw: 5 5, -1db: 60 60
< 43499.147> [Volume] setValue 5
< 43822.087> [eDVBVolumecontrol] Setvolume: raw: 0 0, -1db: 63 63
< 43822.089> [Volume] setValue 0
< 43822.089> [Volume] setValue 0
< 43905.574> [eDVBVolumecontrol] Setvolume: raw: 0 0, -1db: 63 63
< 43905.576> [Volume] setValue 0
< 43954.864> [eDVBVolumecontrol] Setvolume: raw: 0 0, -1db: 63 63
< 43954.865> [Volume] setValue 0
< 44092.082> [eDVBVolumecontrol] Setvolume: raw: 0 0, -1db: 63 63
< 44092.083> [Volume] setValue 0
< 44411.827> [eDVBVolumecontrol] Setvolume: raw: 0 0, -1db: 63 63
< 44411.829> [Volume] setValue 0
< 44532.149> [eDVBVolumecontrol] Setvolume: raw: 0 0, -1db: 63 63
< 44532.150> [Volume] setValue 0
< 44579.103> [eDVBVolumecontrol] Setvolume: raw: 0 0, -1db: 63 63
< 44579.104> [Volume] setValue 0
< 45444.616> [eDVBVolumecontrol] Setvolume: raw: 0 0, -1db: 63 63
< 45444.617> [Volume] setValue 0
< 47401.432> [eDVBVolumecontrol] Setvolume: raw: 0 0, -1db: 63 63
< 47401.433> [Volume] setValue 0
root@xpeedlx3:/media/hdd/logs#
There's nothing in the logs about it coming from HDMI CEC but I've disabled that now too.
The only bulb in the room is a Philips Hue bulb but isn't turned on (I've seen reference to certain types of light bulbs causing interference in the past).
Still doing it with HDMI CEC disabled too (I'm just grep'ing Volume to keep it easier to read for now):
< 1856.058> [eDVBVolumecontrol] Setvolume: raw: 100 100, -1db: 0 0
< 1856.059> [Volume] setValue 100
< 3008.712> [eDVBVolumecontrol] Setvolume: raw: 95 95, -1db: 4 4
< 3008.713> [Volume] setValue 95
< 4766.268> [eDVBVolumecontrol] Setvolume: raw: 90 90, -1db: 7 7
< 4766.269> [Volume] setValue 90
Just flashing the latest OpenATV and I'll leave that while we're out to see if it does the same thing on that (just trying to work out if it's the hardware or software causing this)
If it does still do it then I'll RMA the box when WoS reopen as it's still under warranty.
The only bulb in the room is a Philips Hue bulb but isn't turned on (I've seen reference to certain types of light bulbs causing interference in the past).Put a book (or similar) over the front of the box to shade it from everything.
I'd tried a bit of A4 paper yesterday with no joy but it didn't completely cover it due to the curve of it :/
The box has just been up for 26 minutes on ATV without the issue so far - it did usually take at least 30 minutes from box startup to it kicking in though previously so not quite there yet.
Well it's been fine for hours on the latest OpenATV even after I put the same plugins on there.
Just about to do a fresh install of OpenVIX and then see what happens as I reintroduce things one by one.
I literally just got past the wizard after USB flashing 5.0.016 - no restores were done and it's already turning itself down as I'm just setting up ABM!!
It was fine for 4 hours on OpenATV so this is bonkers!
I've just configured ABM and will re-enable debug logs and reboot and see what it has in there.
Andy_Hazza
29-05-17, 15:25
I literally just got past the wizard after USB flashing 5.0.016 - no restores were done and it's already turning itself down as I'm just setting up ABM!!
It was fine for 4 hours on OpenATV so this is bonkers!
I've just configured ABM and will re-enable debug logs and reboot and see what it has in there.
Someone is playing silly billies with you. I've done it in the past with family n friends via an iPhone app. Are you sure no one is doing the same? Or defo your ports are not open on your router?
Sent from my iPhone using Tapatalk
Ports are definitely shut mate and there's no-one else in the house - I've even got the curtains shut to stop anything coming in that way :D
As the debug log showed though the events are indicating it's IR traffic and not OpenWebIf but it's strange this doesn't happen on the latest OpenATV - yet they use the same base LX3 drivers
Andy_Hazza
29-05-17, 15:32
I think Abu has an LX3 as does Norman. I'll ask them to look here and see if they can test.
Sent from my iPhone using Tapatalk
Just to update I'm just trying the latest OpenHDF and so far I've not seen any random volume down commands on this image either.
Here's a copy of ActionMap.py that will log a traceback every time it gets a volumeDown request.
Put it into /usr/lib/enigma2/python/Components/ (Take a copy of the existing ActionMap.pyo file, so that you can put it back in place once there is some info produced).
53897
Thank-you very much @birdman - I'm just reflashing back to OpenViX now so will get the output up as soon as I see it happen :)
Just for reference I manually pressed the button and I got the following:
< 139.658> [eInputDeviceInit] 1 72 1
< 139.659> [InfoBarGenerics] KEY: 114
< 139.659> [ActionMap] GlobalActions volumeDown
< 139.664> File "/usr/lib/enigma2/python/mytest.py", line 693, in <module>
< 139.664> runScreenTest()
< 139.664> File "/usr/lib/enigma2/python/mytest.py", line 536, in runScreenTest
< 139.664> runReactor()
< 139.664> File "/usr/lib/enigma2/python/mytest.py", line 122, in runReactor
< 139.664> reactor.run(installSignalHandlers=False)
< 139.664> File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1195, in run
< 139.665> File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1207, in mainLoop
< 139.665> File "/usr/lib/enigma2/python/e2reactor.py", line 150, in doPoll
< 139.665> File "/usr/lib/enigma2/python/e2reactor.py", line 40, in poll
< 139.665> File "/usr/lib/enigma2/python/Components/ActionMap.py", line 50, in action
< 139.665> traceback.print_stack()
< 139.665> [eDVBVolumecontrol] Setvolume: raw: 95 95, -1db: 4 4
< 139.666> [Volume] setValue 95
< 139.850> [eInputDeviceInit] 0 72 1
< 139.851> [InfoBarGenerics] KEY: 114
And then this is what I get when a random one happens:
< 727.660> [eInputDeviceInit] 1 72 1
< 727.661> [InfoBarGenerics] KEY: 114
< 727.661> [ActionMap] GlobalActions volumeDown
< 727.663> File "/usr/lib/enigma2/python/mytest.py", line 693, in <module>
< 727.663> runScreenTest()
< 727.663> File "/usr/lib/enigma2/python/mytest.py", line 536, in runScreenTest
< 727.663> runReactor()
< 727.663> File "/usr/lib/enigma2/python/mytest.py", line 122, in runReactor
< 727.663> reactor.run(installSignalHandlers=False)
< 727.663> File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1195, in run
< 727.663> File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1207, in mainLoop
< 727.663> File "/usr/lib/enigma2/python/e2reactor.py", line 150, in doPoll
< 727.664> File "/usr/lib/enigma2/python/e2reactor.py", line 40, in poll
< 727.664> File "/usr/lib/enigma2/python/Components/ActionMap.py", line 50, in action
< 727.664> traceback.print_stack()
< 727.664> [eDVBVolumecontrol] Setvolume: raw: 90 90, -1db: 7 7
< 727.665> [Volume] setValue 90
< 727.665> [eInputDeviceInit] 0 72 1
< 727.666> [InfoBarGenerics] KEY: 114
This is on a completely clean USB flash of 5.0.016 with nothing restored and set up as a new box.
I actually saw the volume go down on it's own during the setup wizard screen!
Config wise I configured the motor with the longtude and latitude on tuner A, tuner B configured as second cable of motorised dish and tuners C&D not connected, pointed the EPG to the HDD, ran ABM set to North West Yorkshire and with SD and HD swapped and enabled debug logging to the hdd - everything else should be default.
I've got a book pushed up right against the front of the receiver so should be blocking IR - the remote doesn't work from anywhere I can fire it in the room anyway but I got another entry in the log:
< 1378.056> [eInputDeviceInit] 1 72 1
< 1378.057> [InfoBarGenerics] KEY: 114
< 1378.057> [ActionMap] GlobalActions volumeDown
< 1378.059> File "/usr/lib/enigma2/python/mytest.py", line 693, in <module>
< 1378.059> runScreenTest()
< 1378.059> File "/usr/lib/enigma2/python/mytest.py", line 536, in runScreenTest
< 1378.059> runReactor()
< 1378.059> File "/usr/lib/enigma2/python/mytest.py", line 122, in runReactor
< 1378.059> reactor.run(installSignalHandlers=False)
< 1378.059> File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1195, in run
< 1378.059> File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1207, in mainLoop
< 1378.059> File "/usr/lib/enigma2/python/e2reactor.py", line 150, in doPoll
< 1378.060> File "/usr/lib/enigma2/python/e2reactor.py", line 40, in poll
< 1378.060> File "/usr/lib/enigma2/python/Components/ActionMap.py", line 50, in action
< 1378.060> traceback.print_stack()
< 1378.060> [eDVBVolumecontrol] Setvolume: raw: 85 85, -1db: 10 10
< 1378.061> [Volume] setValue 85
< 1378.126> [eInputDeviceInit] 0 72 1
< 1378.127> [InfoBarGenerics] KEY: 114
I just realised the buttons on the front panel of the LX3 are volume up and down too just to complicate things (I've never used them before other than for flashing!)
Although if that front panel was failing I'd have expected it to have affected OpenATV and OpenHDF too which it didn't.
Right so it's been left all night on the fresh install and the volume has worked it's way down to 25 with the front panel totally covered and blocked - I've attached the full debug log:
53898
Going to try a fresh flash of 5.0.013 next to see if that has the problem.
Might be a dodgy contact on the front panel, maybe? You seem to have eliminated an IR source by blocking the sensor and any external influence by closing router ports. Only things left are LAN or fault in the front panel.
You'd have thought so but so far the problem only manifests on OpenViX 5.0.14 or 5.0.16 - I've reverted to 5.0.13 and it's early days yet (the box has only been up an hour) and it hasn't shown the problem.
It ran for hours on OpenATV and OpenHDF without the issue too yesterday which suggests it could be something that's crept in since 5.013 was released?
Are there any other images which are very similar to ViX I could try please just to try and lock it down a bit?
Strange all right. Best to leave it on 5.0.13 for an extended period to ensure the problem is definitely image related.
I always get the weird women and the weird problems (though don't tell the wife that :D)
I always get the weird women and the weird problems (though don't tell the wife that :D)
...maybe she's messin' with your receiver:eek:
Pity you can't swap your wife as easily as you can swap an image.
Sent from my iPhone using Tapatalk
You've got me thinking I need a new bird now for a day or two :D
The box has been up for 3.5 hours on OpenViX 5.0.013 now with no sign of the issue yet - I'll give it 24 hours to see what happens!
All ok for 7 hours now and counting on 5.0.013 :)
Up for 22 hours with no issues on 5.0.13 so definitely looks like it's something in 5.014 that causes it
Here's almost 24 hours of debug log from 5.0.13 which doesn't have the issue:
53905
OK now I'm massively confused - I just upgraded the bootloader to 4.0 which gives onscreen information about the flashing process and after the box booted back up to ViX 5.0.013 the volume has started turning down almost instantly! WTF.
I am starting to think it is something to do with the hardware going tits up.
Just about to try Egami 8.0.2 as a matter of interest to see if that does it.
OK same problem in Egami 8.0.2!
Back to OpenATV to see if that is doing it as well now.
I can only think it's a physical problem with the front panel that's slowly getting worse - bizarre it was fine for 24 hours until the box was rebooted, although on the flip side I did press the up button to flash the bootloader so could be it's sticking.
The front panel has been totally cleaned btw.
I can't seem to enable debug logs on Egami but it is definitely doing the same thing.
Front panel is covered and the network link is down and it still does it.
From what I recall of using egami, there didn't seem to be a debug log option. I think you're chasing shadows with a software cause and you should concentrate on hardware. When you say the front panel was totally cleaned - how? Normally the front panels of these boxes don't get used much, apart from the occasional re-flash where you need to hold in a button, so the buttons don't really get a hammering. Was something spilled on the box?
No mate it's in a hifi rack and nothing has touched it - when I say cleaned just with a dry microfibre cloth in case there was any dust on it :)
Love this thread. It's like a proper whodunnit. Can't wait to find out what the culprit is. :thumbsup::confused:
I just realised the buttons on the front panel of the LX3 are volume up and down too just to complicate things Maybe one of these buttons is slightly depressed and is making occasional contact?
It's a kind of touch panel so does look like it's going to end up being that at fault - just logging a ticket now :)
Mega strange it was fine with OpenATV and OpenHDF for as long as it was and always tripped up when I went back to ViX - I'll go back to OpenATV as there's a chance the prodding of the panel causes it to start going haywire when each flash is done.
Saying that the front panel never gets used so it starting to turn itself down I guess is the sign of it slowly starting to fail. It's certainly been a random one!
Do the front panel buttons actually change the volume in OpenATV when you press them?
When you press them yes they work fine and log the same as the remote button press.
I noticed the latest OpenViX versions are using a newer kernel than OpenATV.
OpenViX 5.0.016 - Linux xpeedlx3 3.14.2 #1 SMP Sat Apr 22 16:21:03 BST 2017 mips GNU/Linux
OpenATV 6 - Linux xpeedlx3 3.14.2 #1 SMP Tue Feb 14 03:48:43 CET 2017 mips GNU/Linux
They show as the same version but with a different build date.
OpenViX & Egami both started turning the volume down while in the setup wizard screens and so far nothing on ATV again so far.
I've tried pressing volume up and down on the front panel to see if it will start triggering the automatic volume down to kick in.
Finally - after much fiddling it's doing it in OpenATV now too - looks like it is the front panel on the way out then so a warranty job.
From the OpenATV debug logs:
11:45:49.8547 [ ] driver/rcinput.cpp:38 handleCode 1 72 1
11:45:49.8565 { } Screens/InfoBarGenerics.py:208 actionA KEY: 114 0 KEY_VOLUMEDOWN
11:45:49.8571 { } Components/ActionMap.py:46 action action -> GlobalActions volumeDown
11:45:49.8576 [ ] dvb/volume.cpp:152 setVolume Setvolume: 98 98 (raw)
11:45:49.8578 [ ] dvb/volume.cpp:158 setVolume [AUDIO_SET_MIXER] Setvolume left: 2 right: 2 (-1db)
11:45:49.8582 { } Screens/Screen.py:151 show [SCREENNAME] Volume
11:45:49.8599 { } Screens/Volume.py:13 setValue setValue 98
11:45:49.8604 [ ] driver/rcinput.cpp:38 handleCode 0 72 1
11:45:49.8624 { } Screens/InfoBarGenerics.py:208 actionA KEY: 114 1 KEY_VOLUMEDOWN
I guess me flashing images and pressing the up button was doing something to the panel which is why sometimes it would be ok post flash and other times not - it was just pure coincidence it was ok with OpenATV and OpenHDF.
Thanks for the help guys but at least now it's looking a bit clearer what the issue is :)
On the plus side I know how to fully configure a lot more images now!
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.