Related
Does anyone who has a fire tv and nexus player know if the fire tv remote will work with the nexus player? I ask because the fire tv remote has a menu button which the nexus player does not. This is a button that would be really useful in XBMC so it would be really awesome if the fire tv remote would work as I could just buy the remote.
I own both devices (with a fire tv stick on the way) but have never seen any way to pair the FTV remote with anything other than the FTV itself.
I'll see what I can come up with though...
Further update I just got a fire TV stick remote in (same as fire TV but without voice) and it works great with the nexus player. All you have to do is hold the home button on the fire remote then on the nexus player is go to settings/add accessory and the nexus will see it and add it. Every button on it works just as it should. Kinda makes me want to buy the voice version to see if the voice button will work with googles voice integration.
Well, I just received a Fire TV Remote w/ Voice in the mail, all excited that I could replace my Nexus remote and have the best of both worlds, but so far, the results do not look promising. My Ubuntu laptop and my CyanogenMod ASUS TF-700T can both see and pair with the remote, but for everything that I have tried, my Nexus Player will not. Nor will my HTC One (M7) for that matter. It just never appears as a selectable device.
I have no idea why. Does anyone else?
I've switched to the fire tv remote because it offers the Menu button in Kodi. Only downside is not having voice search and the center/select button doesn't seem to work in some games. I'm guessing it's a keymapping issue.
Yes I couldn't get the firetv remote to work either, shame as its much higher quality than the Asus one included.
I actually get remote control integration over HDMI with my Sony TV, it maps the controls nicely (mainly because there are so few of them!), it just lacks a mic, which is kind of the point after all!
I played around with my Nexus Player remote, Fire TV remote, and Fire TV Stick remote.
All paired fine with my Note 4. Unlike the other two, the Fire TV remote kept sending active pair requests to my phone until I accepted the activation. Maybe this is how Amazon handles cases where the remote gets lost? If so, why doesn't the stick remote do this? Cheaper BT controller?
I installed "Bluetooth Finder" on my Note 4 and on my NP.
https://play.google.com/store/apps/details?id=com.bluetoothFinder
In this app, I could see that the Fire TV remote would enumerate and return its device name on my Note 4.
On my NP, though, I could detect the Fire TV remote, but it was coming back as "null".
So... Does the NP need a better BT stack or something?
FireTV Stick remote
I figured out how to get the Fire TV stick fully working. I pulled the keylayout file from the Fire TV Stick and added them to the Nexus Player.
Without this pressing the center button sends the keyevent "Keypad_Enter" instead of "DPAD_CENTER", which doesn't work in some apps.
The file must be called "Vendor_1949_Product_0404.kl", add to /system/usr/keylayout/ set permissions to 644, here are it's contents:
# Amazon/Lab126 Remote Control
# Navigation buttons
key 96 DPAD_CENTER WAKE
key 103 DPAD_UP WAKE
key 105 DPAD_LEFT WAKE
key 106 DPAD_RIGHT WAKE
key 108 DPAD_DOWN WAKE
# Control buttons
key 139 MENU WAKE
key 158 BACK WAKE
key 172 HOME WAKE
# Media buttons
key 164 MEDIA_PLAY_PAUSE WAKE
key 168 MEDIA_REWIND WAKE
key 208 MEDIA_FAST_FORWARD WAKE
got Fire TV Voice Remote working!! well partially working...
lunigma said:
I figured out how to get the Fire TV stick fully working. I pulled the keylayout file from the Fire TV Stick and added them to the Nexus Player.
Without this pressing the center button sends the keyevent "Keypad_Enter" instead of "DPAD_CENTER", which doesn't work in some apps.
The file must be called "Vendor_1949_Product_0404.kl", add to /system/usr/keylayout/ set permissions to 644, here are it's contents:
# Amazon/Lab126 Remote Control
# Navigation buttons
key 96 DPAD_CENTER WAKE
key 103 DPAD_UP WAKE
key 105 DPAD_LEFT WAKE
key 106 DPAD_RIGHT WAKE
key 108 DPAD_DOWN WAKE
# Control buttons
key 139 MENU WAKE
key 158 BACK WAKE
key 172 HOME WAKE
# Media buttons
key 164 MEDIA_PLAY_PAUSE WAKE
key 168 MEDIA_REWIND WAKE
key 208 MEDIA_FAST_FORWARD WAKE
Click to expand...
Click to collapse
djwyman said:
Does anyone who has a fire tv and nexus player know if the fire tv remote will work with the nexus player? I ask because the fire tv remote has a menu button which the nexus player does not. This is a button that would be really useful in XBMC so it would be really awesome if the fire tv remote would work as I could just buy the remote.
Click to expand...
Click to collapse
Found an easier way...
I went to ES File Explorer what we use to get to install Kodi
I looked under the bluetooth file share category and the Fire TV Remote popped up in the list i selected it thinking eh what the hell doubt it'd work...
said "Couldn't find device"
I grab the remote hit a home on it and to my surprise it was paired, working great after that fortunate ES File Explorer accident right when I was about to order the STicks remote I just added it cart lol
Only menu button doesn't work on it was hoping it would for Kodi that's why I got it,voice search doesn't you hit the search button it will launch but seems that the mic is deactivated, so not much of a voice remote now... Otherwise everything else works fine.
Pondering on the fire stick version since someone said all buttons are functioning...
BlckMlr757 said:
Found an easier way...
I went to ES File Explorer what we use to get to install Kodi
I looked under the bluetooth file share category and the Fire TV Remote popped up in the list i selected it thinking eh what the hell doubt it'd work...
said "Couldn't find device"
I grab the remote hit a home on it and to my surprise it was paired, working great after that fortunate ES File Explorer accident right when I was about to order the STicks remote I just added it cart lol
Only menu button doesn't work on it was hoping it would for Kodi that's why I got it,voice search doesn't you hit the search button it will launch but seems that the mic is deactivated, so not much of a voice remote now... Otherwise everything else works fine.
Pondering on the fire stick version since someone said all buttons are functioning...
Click to expand...
Click to collapse
It took me a few tries, but this method also worked for me. Here's what I had to do:
1. Connect to my ADT-1 via adb
Code:
adb connection <ip address>:4321
2. Install ES File Explorer from http://www.estrongs.com/?lang=en
Code:
abd install /path/to/ESwenjianliulanqi_223.apk
3. Open ES File Explorer and go to Bluetooth in the side menu.
4. Click Scan
5. Hold Home on the remote for 5 seconds
6. Try to connect to the Android Remote that shows up in ES File Explorer.
I did this several times, removing and reinserting the batteries of the remote. Eventually, it just started working.
The microphone button on the remote works, but the mic itself doesn't seem to pass audio to the device. Until we can figure that out you are probably better off just using the Fire Stick remote.
lunigma said:
I figured out how to get the Fire TV stick fully working. I pulled the keylayout file from the Fire TV Stick and added them to the Nexus Player.
Without this pressing the center button sends the keyevent "Keypad_Enter" instead of "DPAD_CENTER", which doesn't work in some apps.
The file must be called "Vendor_1949_Product_0404.kl", add to /system/usr/keylayout/ set permissions to 644, here are it's contents:
# Amazon/Lab126 Remote Control
# Navigation buttons
key 96 DPAD_CENTER WAKE
key 103 DPAD_UP WAKE
key 105 DPAD_LEFT WAKE
key 106 DPAD_RIGHT WAKE
key 108 DPAD_DOWN WAKE
# Control buttons
key 139 MENU WAKE
key 158 BACK WAKE
key 172 HOME WAKE
# Media buttons
key 164 MEDIA_PLAY_PAUSE WAKE
key 168 MEDIA_REWIND WAKE
key 208 MEDIA_FAST_FORWARD WAKE
Click to expand...
Click to collapse
Thanks for the great info.
Everything works great except in Netflix the select key on my firetv stick remote.
Using a adt 1 with 5.0.2 firmware.
How would I create this file you speak of? Maybe a regular text editor or sqlite and rename it?
I've attached the file to my original post
lunigma said:
I've attached the file to my original post
Click to expand...
Click to collapse
Thank you for this!
Now I have a reason to root my ADT-1 lol.
Sent from my LG-VS985 adorned w/ Illusion ROM
Nice work, any updates on this? Thinking of buying a FireRemote for my Nexus player but I do want the menu button and mic working, Any luck with this yet?
here are the files i used to get the center button of the fire tv stick remote to work in netflix. im pretty sure only the edited generic one is needed but i included the othes i edited them. perms if u have to set them should be rw- r-- r--
whats edited in the generic is key 96 is no longer numpad_enter but is now dpad_center, in the others i just removed wake.
if anyone wants i can upload all the orig keymaps from the fire tv and fire tv stick.
lunigma said:
I figured out how to get the Fire TV stick fully working. I pulled the keylayout file from the Fire TV Stick and added them to the Nexus Player.
Without this pressing the center button sends the keyevent "Keypad_Enter" instead of "DPAD_CENTER", which doesn't work in some apps.
The file must be called "Vendor_1949_Product_0404.kl", add to /system/usr/keylayout/ set permissions to 644, here are it's contents:
# Amazon/Lab126 Remote Control
# Navigation buttons
key 96 DPAD_CENTER WAKE
key 103 DPAD_UP WAKE
key 105 DPAD_LEFT WAKE
key 106 DPAD_RIGHT WAKE
key 108 DPAD_DOWN WAKE
# Control buttons
key 139 MENU WAKE
key 158 BACK WAKE
key 172 HOME WAKE
# Media buttons
key 164 MEDIA_PLAY_PAUSE WAKE
key 168 MEDIA_REWIND WAKE
key 208 MEDIA_FAST_FORWARD WAKE
Click to expand...
Click to collapse
I got my remote paired, but one thing i'm can't seem to figure out, is where to copy the attached files to...
what folder on the nexus tv should they be copied to?
Thanks in advance
--EDIT--
Correction, I found the keylayout folder in System/Users, but i'm unable to overwrite the existing files.
failed:EROFS (Read-only file system)
do you need root access to do this?
Hunglo said:
I got my remote paired, but one thing i'm can't seem to figure out, is where to copy the attached files to...
what folder on the nexus tv should they be copied to?
Thanks in advance
--EDIT--
Correction, I found the keylayout folder in System/Users, but i'm unable to overwrite the existing files.
failed:EROFS (Read-only file system)
do you need root access to do this?
Click to expand...
Click to collapse
yes you need to be rooted
I think that the fire tv voice remote problem with pairing are possibly related to this bug: Issue 95353: Bluetooth HID does not pair with ADT-1 when device also has addtional BT services (I'd make this a link, but I can't as a new user. A search on the android bug tracker will lead you to the actual bug, though.)
I've been researching the problem a bit, trying to get a solution to pairing the voice remote w/ a Shield TV. So far, no luck, though.
Got my Fire Tv Remote paired, no root!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
had to mess with es file explorer and NP Bluetooth settings to work
1st pair saw it as mac address only "in es file explorer", stayed paired only a minute or two and lost connection
NP showed it in list, unpaired the nexus remote tried repairing "scanning" and worked
you must have a keyboard to navigate!!!
DO NOT mess with the voice search, it will unpair remote
menu key does not work
works in kodi "remapping Rewind key to C" EXCELLENT!!!!!!!!!
rebooted NP remote stays paired but takes a couple of seconds to wake
voice search i hit again, does take you to search screen but as others stated, does not work, remote stayed paired
Hi Guys,
Anyone got the Menu key working on this remote? Everything else works and I installed the file from the first post but does not work on LeanBack or in Kodi.
I am trying to setup my Flirc with the Nexus Player, for both native NP keys and the full spectrum of XBMC/kodi keys. I have all of the kodi keys working properly and the UP, DOWN, LEFT, RIGHT, SELECT and PLAY/PAUSE buttons work just fine on the main Nexus Player interface. However, the mapped BACK and MENU keys are not working. For those that don't know, a Flirc USB devices presents itself as a standard keyboard to the Nexus Player and can be programmed on your PC to learn remote control commands to activate specific generic keyboard combinations.
If anyone has a standard keyboard hooked up to their NP either via Blutooth or USB OTG, can you tell me which keys correspond to the BACK and HOME functions on the Nexus Player or if those functions are working at all on your keyboard?
Thanks.
Elrondolio said:
I am trying to setup my Flirc with the Nexus Player, for both native NP keys and the full spectrum of XBMC/kodi keys. I have all of the kodi keys working properly and the UP, DOWN, LEFT, RIGHT, SELECT and PLAY/PAUSE buttons work just fine on the main Nexus Player interface. However, the mapped BACK and MENU keys are not working. For those that don't know, a Flirc USB devices presents itself as a standard keyboard to the Nexus Player and can be programmed on your PC to learn remote control commands to activate specific generic keyboard combinations.
If anyone has a standard keyboard hooked up to their NP either via Blutooth or USB OTG, can you tell me which keys correspond to the BACK and HOME functions on the Nexus Player or if those functions are working at all on your keyboard?
Thanks.
Click to expand...
Click to collapse
I haven't tested this yet, but typically the Windows key + ESC = HOME (or, depending, sometimes the HOME key itself on a keyboard). BACK is typically the ESC key by itself.
My FLIRC arrived yesterday -- just haven't configured it yet. I'll give it a whirl and get back to you!
PearcePowers said:
I haven't tested this yet, but typically the Windows key + ESC = HOME (or, depending, sometimes the HOME key itself on a keyboard). BACK is typically the ESC key by itself.
My FLIRC arrived yesterday -- just haven't configured it yet. I'll give it a whirl and get back to you!
Click to expand...
Click to collapse
Thank you. I got the back key working correctly (and, in the NP, it is indeed ESC), but you'll have to go in to XBMC/kodi and add in the keymapper in programs then globally change ESC to be BACKSPACE and BACKSPACE to be ESC. Otherwise the NP back key would be "previous menu" in kodi. Make sure to update your Flirc with the full keyboard template to change the ESC key to your remote button you wish. Once done, both the NP and kodi see ESC as the back key.
I still haven't figured out the HOME key yet... I have a "HOME" special button atop my wireless keyboard that works, but I can't scancode it properly so I'm not sure what it is yet (I've read it may be scancode 57, but thats normally "space", so not sure and haven't tested it yet) I'll see if WIN+ESC works from my keyboard when I get home tomorrow. Hope to hear your experiences as well... thanks.
Elrondolio said:
I'll see if WIN+ESC works from my keyboard when I get home tomorrow. Hope to hear your experiences as well... thanks.
Click to expand...
Click to collapse
I tested the following three keyboard commands -- WIN + ESC, ALT + ESC, and HOME -- and none work in the Nexus Player to take you home. Grr. I've got everything working but the HOME key as well.
PearcePowers said:
I tested the following three keyboard commands -- WIN + ESC, ALT + ESC, and HOME -- and none work in the Nexus Player to take you home. Grr. I've got everything working but the HOME key as well.
Click to expand...
Click to collapse
There is a topic about this over on the Flirc forums that you may want to follow:
http://forum.flirc.tv/index.php?/topic/1219-flirc-and-android-tv-adt-1/
I have a wireless keyboard that has extra media keys including a Home key (not the regular Home, End, etc). It works just like the Home key on the NP remote. I'm not at home right now, but had hooked it up to one of my laptops and that special Home key sends key code 172.
We just need to figure out how to teach Flirc that key code then map one of our remote buttons to that key.
Elrondolio said:
There is a topic about this over on the Flirc forums that you may want to follow:
http://forum.flirc.tv/index.php?/topic/1219-flirc-and-android-tv-adt-1/
I have a wireless keyboard that has extra media keys including a Home key (not the regular Home, End, etc). It works just like the Home key on the NP remote. I'm not at home right now, but had hooked it up to one of my laptops and that special Home key sends key code 172.
We just need to figure out how to teach Flirc that key code then map one of our remote buttons to that key.
Click to expand...
Click to collapse
Any luck with the home key and Flirc? I noticed no one has responded over in the Flirc forums yet.
PearcePowers said:
Any luck with the home key and Flirc? I noticed no one has responded over in the Flirc forums yet.
Click to expand...
Click to collapse
Not as yet. It seems more complicated than I first thought... the record_api function of flirc_util.exe can map HID commands to remote control buttons, but finding the correct HID for "Home" is difficult. There are thousands of HID commands as referenced in this document:
http://www.usb.org/developers/hidpage/Hut1_12v2.pdf
We're looking at the ones in the Consumer Page starting on page 75. There is a special modifier in the second argument of Firc's record_api, 102, that supposedly tells the Flirc to reference that Consumer Page, but finding the "Home" key for the first argument of record_api is difficult. In other words: no. No luck yet, but still trying.
It'd probably be useful if you were to post a thread over there asking for help with the Home key on the Nexus Player as well. I'd imagine the higher the request for it the more eyes it'll receive.
Could be something that could be setup in llama or tasker? Set NP to listen for XYZ key command and then "Go Home". Just a thought.
Elrondolio said:
Not as yet. It seems more complicated than I first thought... the record_api function of flirc_util.exe can map HID commands to remote control buttons, but finding the correct HID for "Home" is difficult. There are thousands of HID commands as referenced in this document:
http://www.usb.org/developers/hidpage/Hut1_12v2.pdf
We're looking at the ones in the Consumer Page starting on page 75. There is a special modifier in the second argument of Firc's record_api, 102, that supposedly tells the Flirc to reference that Consumer Page, but finding the "Home" key for the first argument of record_api is difficult. In other words: no. No luck yet, but still trying.
It'd probably be useful if you were to post a thread over there asking for help with the Home key on the Nexus Player as well. I'd imagine the higher the request for it the more eyes it'll receive.
Click to expand...
Click to collapse
Did you manage to map a true home function to your Flirc device, Elrondolio? The ALT + ESC key combination works okay for me in most cases although it doesn't work when I use Kodi. It's still better than no home functionality at all, though, so at least I won't always have to use the original Nexus Player remote when I need that feature. There's another thread at the Flirc forum which discusses this topic at http://forum.flirc.tv/index.php?/topic/1462-flirc-with-android-tv/.
ALT + TAB seems to be the ideal key combination to use for the home button. It works no matter which app you're in and although it causes the Nexus Player to display "your recent screens appear here" when you use that key combination, the on-screen message disappears as soon as you release the button.
Now if I can just figure out how to use the Nexus Player's Leanback keyboard with my universal remote so that I can select on-screen keys for searches instead of having the ENTER button close the keyboard off, that would make things just about perfect.
I was the one that posted in Flirc forum about the alt+tab for home.
For search using on-screen, map flirc to window key using command. then combine this key with navigation right key using your universal remote, such as logitech. so WIN + Right will launch search with on screen keyboard to type.
Thanks for posting your solution in the Flirc forum. I'm not trying to map a command to launch an on-screen keyboard but I'm trying to see if I can find a way to press the keys on the Leanback keyboard using my universal remote. This isn't a problem with some apps like Netflix or Kodi that have their own keyboards but for the Leanback keyboard that's used in apps like Google Play and YouTube, pressing the ENTER button on a universal remote causes the keyboard to close off. This problem does not exist with the original Nexus Player remote's select button because it is context-sensitive.
Elrondolio said:
If anyone has a standard keyboard hooked up to their NP either via Blutooth or USB OTG, can you tell me which keys correspond to the BACK and HOME functions on the Nexus Player or if those functions are working at all on your keyboard?
Click to expand...
Click to collapse
Back: Esc
Home: Alt+Esc
Unfortunately, the ALT + TAB key combination is not an ideal option for use with Android 6.0 Marshmallow. It actually brings up the recent apps screen and doesn't give the user easy access to the home screen (unless the recent apps screen is empty). I'll have to reprogram my Flirc back to ALT + ESC for the home screen function until someone finds a better solution for Android 6.0.
I don't have a nexus player but these issues sound similar to the shield tv.
To fix the Enter key issue with the onscreen keyboard, us the flirc_util to record the keypad's enter key (a different dev id than the other enter/return key):
HTML:
flirc_util.exe record_api 0 88
To record the Home button (that works from Kodi too), record Windows Key + Enter (the main Enter key works fine for this). Again, I don't have a nexus player but I assume it will work for it as well.
whiskaz77 said:
I don't have a nexus player but these issues sound similar to the shield tv.
To fix the Enter key issue with the onscreen keyboard, us the flirc_util to record the keypad's enter key (a different dev id than the other enter/return key):
HTML:
flirc_util.exe record_api 0 88
To record the Home button (that works from Kodi too), record Windows Key + Enter (the main Enter key works fine for this). Again, I don't have a nexus player but I assume it will work for it as well.
Click to expand...
Click to collapse
I tried out these key combinations with my Flirc on the Nexus Player and am happy to report that everything now works perfectly! Thank you kindly for sharing that useful information here with the rest of us.
GabbyWC said:
I tried out these key combinations with my Flirc on the Nexus Player and am happy to report that everything now works perfectly! Thank you kindly for sharing that useful information here with the rest of us.
Click to expand...
Click to collapse
Great! Happy to help. I'm glad it worked. Thanks for reporting back!
Windows Key + Enter => Home worked for me too!!! Kodi, Netflix and other apps now behave fine. Thanks a lot @whiskaz77
Hi everbody,
I was playing with a USB keyboard that I connected to my fireTV and I have noticed something that I haven't read in the forums yet.
- The key used by the FireTV remote control for Home button is the Multimedia Key for "ZoomOut" in the browser.
- And the Key that is used to trigger the Microphone corresponds to the "ZoomIn" in the browser.
Maybe these ones are useful to @rbox (I know that he has already the Xposed module to overwrite the Home button), but maybe the mic can be associated with Google Search instead. Or with the voice search in kodi. That way we get rid of the keyboard.
Or maybe they are useful to @elmerohueso to create another addon to map them.
On my side I just connected a flirc and I am programming it with power button, volume from my AVR, subtitles search, etc.
However, I love the fireTV remote and I believe that there is no real need for a keyboard if the voice funcionality can be replaced by a voice keyboard.
How difficult would it be to modify the Leanback keyboard so that it could be used with universal remotes? My Nexus Player is connected to a Flirc USB infrared dongle which I use with a Philips SRP5107 universal remote. I have my universal remote's main OK button mapped to emulate the ENTER key on a keyboard and this works fine in most cases but not with the Leanback keyboard. It isn't a problem with some apps like Netflix or Kodi that have their own keyboards but for the Leanback keyboard that's used in apps like Google Play and YouTube, pressing the OK button on a universal remote causes that on-screen keyboard to close off. This problem does not exist with the original Nexus Player remote's select button because it is context-sensitive. Can the Leanback keyboard somehow be modified to *not* close but rather type the selected on-screen key when it detects an external ENTER key / OK button being pressed?
I have a Samsung TV and I want to use my TV remote to control Shield TV (over HDMI-CEC). This mostly works with one inconvenient problem. Android Back button is mapped to Samsung Exit button. Regular Samsung remotes have Return and Exit buttons and if you are using this remote then it's ok. But higher end Samsung TVs have Samsung smart remote and it only has Return button. The Return button also works as a Exit button if you hold it down for 2 seconds, but that's really inconvenient.
For me it would make a lot more sense if the Android Back button would be mapped to Samsung Return button and if possible then Android Home to Samsung Exit.
I have no idea why or who (Google, Nvidia or Samsung?) mapped the buttons as they are, but it is not usable for me. So is there any chance we can remap HDMI-CEC buttons?
I'm also looking at this thread. Interested to know if its possible.
if u can block the IR sensor, and just get a FLIRC, u can remap any or all functionality
I did some research and it seems it's Samsung's fault. Samsung has mapped it's Exit button to HDMI-CEC KEY_BACK. And the Return buttun is mapped to HDMI-CEC KEY_EXIT (it appears only Samsung is using it). Some manufacturers have added this Samsung specific button to their devices (PS3 for example) and considering that Samsung has the biggest TV market share, I think Nvidia should have added it too.
It seems it is possible to remap HDMI-CEC buttons by editing .kl files in /system/usr/keylayout/. It appears to be using Generic.kl file if there is no hdmi_cec_keys.kl file in that folder. I don't have root, so i cant test this at the moment.
Unfortunately it seems that we can't map Samsung Return button to anything, because Samsung specific KEY_EXIT is missing in kernel. So we would need to find someone who knows how to modify kernel and compile it for us Samsung TV users. Someone has done this for some other Android box there > https://github.com/hardkernel/linux/pull/178/commits/96e8846f78b077add5fdc8a93235deefd262f71b
Any devs here who could make this fix?