Neo A2 Remote not fully working

[ajw107]

Just got my first Minix Box (X8-H) with a Neo A2 remote, and on the whole it seems to work, but I am having a few problems:

1) The three buttons at the top seem to do nothing (Android Buttons: Task Switcher, Menu and Home), as well as the bottom button with the six squares on it (surely that should take you to the Metro Home Screen or the All Apps Screen)

2) The mic does not seem to work. When I use Skype all people can here are 'Clicks' (brand new batteries), and Google Voice Search has incredible difficulty understanding me (probably because it is just hearing clicks, he he).

3) The Sound will Randomly just start coming out of the Remote Speaker instead of the TV. The instructions say to go to settings -> Sound -> Sound Manager. In neither Android Main Settings, Minix Settings or XBMC setting can I find a sound manager. I assume this is for Android 4.2 or something, not 4.4. How do we force the sound to always come out of the TV screen, unless we ask for it to come out of the Remote? Surely there should be a button on the remote to toggle between TV/Remote sound output too?

4) There's a lot of buttons missing for XBMC that the three Android buttons mentioned in question 1) could help with:
a) There's no button to bring up a menu to mark things as watched, delete them, etc. You have to press C on the keyboard, could the Android Menu button not do this?
b) There's no button to go back to the XBMC Home Screen, could the Android Home button not do this?
c) There's no stop button, so if you need to stop a video, there is only really the return button, so the video just keeps on playing behind all the menus. Not sure what to do about this?

Hope you can help, I will post this on the Minix forum too, but this forum seems far busier.
Alex

[HardwareGuru]

Yes there is a function to switch between sound options. It should work on x7 but never tested it. Si i dont know if it will also work on x8. Check manual to see how. I allready reported the keymapping issue but the sound issue is new to me.

Verstuurd vanaf mijn T5 met Tapatalk

[ajw107]

Thank you for such a quick reply. Glad to hear that something is being done about the key mapping at least. Could the mic thing be a hardware issue?

On a side note, just spent ages trying to find something that would EASILY change the mouse cursor (something bigger, or at least a colour which won't blend into a white background). I've found 2 methods:

Change the image '/system/framework/framework-res.apk/res/drawable-mdpi/pointer_arrow.png'
installing Xposed Framework and using that to change the file

but they both seem like a mad thing to do for such an easy option, surely?
Alex

[MINIX]

Hi,

There will be a new official firmware this week addressing your issue.

Regards,
Team MINIX.

[Finless]

FYI for these AML boxes there is a file that supports the remote and key mapping.

it is in /system/etc/remote.conf

If your rooted you can edit it. There is a nice APP on the play store that will show you the codes for keyboard and other input devices. Then you can mod this file to your liking

This is what the minix has now. I believe this currently supports the Minix M1.

#amlogic NEC remote
factory_code	= 0xfe010001
work_mode  		= 0
repeat_enable = 0
repeat_delay = 250
repeat_peroid = 39
release_delay	=	190
debug_enable 	= 0

left_key_scancode  = 0x47
right_key_scancode = 0x15
up_key_scancode    = 0x46
down_key_scancode  = 0x16
ok_key_scancode    = 0x55



key_begin  
        0x47 105  #DPAD_LEFT
        0x15 106  #DPAD_RIGHT
        0x46 103  #DPAD_UP
        0x16 108  #DPAD_DOWN
        0x55 97   #ENTER
        0x40 1    #BACK
		0x04 125  #MENU
		0x14 115  #VOLUME_UP
		0x10 114  #VOLUME_DOWN
		0x0d 102  #HOME
		0x18 116  #POWER WAKE
key_end

What I do not know is if multiple remotes can be defined in here. What I do know is if it's not correct (the factory code) the remote wont work at all.

Bob

[HardwareGuru]

We can add a kcm and kl file if we use the product vendor id right?. I will make it tomorow and see if that works. I think the above was for the ir remote.. could be wrong thuogh....

Verstuurd vanaf mijn U55GT met Tapatalk

[Finless]

We can add a kcm and kl file if we use the product vendor id right?. I will make it tomorow and see if that works. I think the above was for the ir remote.. could be wrong thuogh....

Verstuurd vanaf mijn U55GT met Tapatalk

Yes it's for the IR remote. Other remotes with a wireless dongle to USB should be able to be defined with kcm and kl files. You can probably just pull them from RK ROM's that have them

Bob

[HardwareGuru]

Yes but i havent looked at them yet and heard the layout changed a bit In 4.4.. the a2 is usb so it could be done with kcm/kl . I seen the m1 also has ir, do you know if it swithes between ir and usb with analog and mousemode?

Verstuurd vanaf mijn U55GT met Tapatalk

[NikAmi]

Re: Neo A2 Remote not fully working

seen the m1 also has ir, do you know if it swithes between ir and usb with analog and mousemode?

I assume that is how it works, but I still haven't received mine yet. Unfortunately that makes the remote useless for my theater room with the equipment all hidden in a closet so I guess I'll just have to use the box upstairs. I wish they just made the whole thing RF or at least have the ability to toggle it to fill RF mode.

Sent from my HTC One using Tapatalk

[ajw107]

Wow,thank you all so much for helping so much. I look forward to the new firmware, hopefully it will fix everything. I was going to try Finless's new firmware to see if that had an effect, but by the sounds of it, it would be best to wait until Finless has chance to source the kl/kcm files (plus I've no idea what the product ID and codes are for the A2).
Will there be an update on this forum when the new firmware is available, or do I need to check somewhere else?

[HardwareGuru]

Bob and i will both make our firmwares to choose from. depends on the flavour you want

Verstuurd vanaf mijn T5 met Tapatalk

[ajw107]

Oh right, I didn't realise you will be making a firmware for the X8-H as well Hardware Guru, I'll look forward to seeing that. Is there somewhere to see the differences between the three (including stock), or is it just a case of uploading them and seeing?
Alex

[HardwareGuru]

Yep as it depends on what you want. Mostly bob his fw is full of extras and rooted while mine are allways basic and not rooted. And i bet there will be more devs soon with x8 fw..

Verstuurd vanaf mijn T5 met Tapatalk

[Finless]

Yep as it depends on what you want. Mostly bob his fw is full of extras and rooted while mine are allways basic and not rooted. And i bet there will be more devs soon with x8 fw..

Verstuurd vanaf mijn T5 met Tapatalk

Well when you say extras, I do not add APPs I remove them to debloat the ROM and make it basic. Users should be able to choose what's on their box and not have to remove stuff which can leave the file system a mess ESPECIALLY "system" APPs which cannot be removed unless your rooted!

The extras I do add are for performance like increasing TCPIP buffers, speed, etc... Those are my extras ")

Bob

[ajw107]

Thank you both for replying and letting me know the differences. I'm still waiting for the next version of the stock firmware (apparently out this week, it's thursday now though), as that would seem to solve most of the A2 based issues (not convinced about the mic problem though). If one of you could put in an app that allowed you to EASILY assign remote keys to do what you want )on both Android in general, and XBMC), that would be brilliant. Only coming back to android after a long time, so not sure wjat the best is, but would prefer to not have to edit text files (i.e LCDProc style), but a nice GUI would be great (just point click and assign, sort of thing).
Alex