futeko.com FORUM
Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: guyrab on July 14, 2017, 08:15:35 AM
-
-
I'm getting similar unexpcted effects with the supplied remote on Q5 Pro Android 7 2.0.4. I particular, the Menu key does not access the Menu functions when playing videos in Kodi (with Wrapper enabled).
-
i wonder if we're the only two...
-
I'm getting similar unexpcted effects with the supplied remote on Q5 Pro Android 7 2.0.4. I particular, the Menu key does not access the Menu functions when playing videos in Kodi (with Wrapper enabled).
This is a Kodi 17 problem. From FAQ:
* Stop Kodi 17 new remote message and disabled back / menu buttons? In Kodi, go Add-ons / My add-ons / Peripheral libraries / Joystick Support / Disable
-
i wonder if we're the only two...
Your problem is different to the other poster.
I suspect you might be the only person experiencing it because 2.0.4 has been installed by thousands of users with no similar reports.
-
-
You can see the Minor fix/update/change for 2.0.4 here:
https://forum.softpedia.com/topic/1056055-himedia-q10q5-pro-android-511-tv-box/page__st__720#entry21414255 (https://forum.softpedia.com/topic/1056055-himedia-q10q5-pro-android-511-tv-box/page__st__720#entry21414255)
-
yes it causes for the radio to starts playing if it is installed,
not a kodi problem as it is also happening in the normal himediaplayer
-
yes it causes for the radio to starts playing if it is installed,
not a kodi problem as it is also happening in the normal himediaplayer
Witch radio apps you have instaled?
I got similar problems when I install Velvet(googlequicksearchbox) every time after reboot first play on HiMediaVideoPlayer start Google search.
-
I have a slightly different problem with remote in 2.0.4. and Himedia player. When I play a movie and press back once (twice actually to exit movie), it exits the movie but it also goes up two or three folders - as I would press back two more times.
It doesn't happen always, but it did definitely not happen before 2.0.4. It's true I'm using Logitech universal remote, but as it worked fine until 2.0.4. it should not be the issue.
-
ok tested again it does happen in kodi and sometimes in thehimediaplayer...... mostly kodi
i installed 1.fm and kodi opens it and starts playing whenever i hit the exit button playing a movie or pause/play
-
Hi,
I've tested a little bit more with HiMedia player and there is indeed bug with remote control. This time I used original remote control and figured out the sequence that almost always demonstrates the bug:
- turn device on
- go to Media player (above Youtube)
- go to SAMBA/LAN shortcut and three levels of subfolders to reach the movie
- start/play movie and few second later press Back button on remote
- label is displayed saying that one more press will exit the movie - press it again
Instead of landing in the subfolder where the movie is, player exist to the main menu of HiMedia player (not home screen). This only happens once when you turn the device on (and/or use Back button on the remote for the first time). All other repeats work fine.
Probably bug, someone else detected it?
-
Hi,
I've tested a little bit more with HiMedia player and there is indeed bug with remote control. This time I used original remote control and figured out the sequence that almost always demonstrates the bug:
- turn device on
- go to Media player (above Youtube)
- go to SAMBA/LAN shortcut and three levels of subfolders to reach the movie
- start/play movie and few second later press Back button on remote
- label is displayed saying that one more press will exit the movie - press it again
Instead of landing in the subfolder where the movie is, player exist to the main menu of HiMedia player (not home screen). This only happens once when you turn the device on (and/or use Back button on the remote for the first time). All other repeats work fine.
Probably bug, someone else detected it?
I can confirm this exact problem.
-
I have sent a bug report to Himedia.
-
This bug was reported way back in 2.0.5 version and wasn't fixed in 2.0.6.
Can you please fix it in 2.0.7?
-
Issue remains in 2.0.7... :(