NEO U22-XJ: 006A FW (20210203) - Bugtracker [OTA Now Available]

John_S

Trusted Helper
Hi All,

V006A (20210203) OTA Firmware Update for NEO U22-XJ is now available to download and install.

You can find it by going to the FOTA Update app.

Please post any bugs or issues found on 006A FW in this thread.

---

Changelog
  1. Removed Root Switch
  2. Fixed Ethernet
  3. Fixed NEO A3 Voice Input
Important Note (1): The HD audio pass-through issue has not been fixed yet.

Important Note (2): During the OTA firmware update process, your TV may show a static noise screen for approx. 5 seconds.

Do not worry, do not touch anything or turn off the NEO U22-XJ. The firmware update process will be completed shortly.

NEO U22-XJ - Firmware Update.jpg

Important Note (3): The Root Switch has been permanently removed.

We shall not include it in any future OTA firmware updates because it is detected by too many streaming services, even when disabled.

The rooted version of 006A FW (20210203) is available to download from here:

https://theminixforum.com/index.php...ion-this-is-not-a-bugtracker.3739/#post-31307

---

Manual Installation

NEO U22-XJ 006A FW is available to download from this link:

https://files.theminixforum.com/shared/firmwares/U22-XJ-V006A-Android_9.0-20210203.7z

Carefully follow attached installation instructions.

---

Amlogic USB Burning Tool v2.2.0

You must use Amlogic USB Burning Tool v2.2.0 in order to manually install the NEO U22-XJ firmware.

Amlogic USB Burning Tool v2.2.0 is available to download from below link:

https://files.theminixforum.com/shared/tools/Amlogic-USB_Burning_Tool_v2.2.0.zip
 

Attachments

  • MINIX NEO U22-XJ - Firmware Installation Instructions.pdf
    319.6 KB · Views: 252
It is a pity that the root switch has gone, although I appreciate that it seems to have caused an issue for some apps. Hopefully you will be issuing rooted versions of future updates for those who want them, although I imagine that will involve having to manually install them.
 
You remove root switch,but my app again say 'device is rooted" :mad:

I try factory reset,but I got same message.
 

Attachments

  • Screenshot_20210205-144233.png
    Screenshot_20210205-144233.png
    36.3 KB · Views: 91
  • Screenshot_20210205-144250.png
    Screenshot_20210205-144250.png
    109.2 KB · Views: 89
Can anyone confirm if the issue with the generic.kl file is resolved in FW006A. See below content for the issue from FW005. I used the rooted version of FW005 to resolve the issue (deleted the redundant generic.kl). I did not check FW006 as have been out of town. I am ready to update from FW005 (rooted version) but want to know that the issue below is resolved first as there is no root option for FW006A.

Thanks


There are 2 Generic.kl files included in this and previous FW versions.
1) /vendor/usr/keylayout/Generic.kl which has key 28 = DPAD_CENTER
2) /system/usr/keylayout//Generic.kl has key 28 = ENTER

Having 2 of these seems redundant as they are meant to serve the same purpose - generic key mapping for standard PC style external keyboard. Both myself and others have had to edit file 1 (which has priority) to map key 28 to ENTER.

As a resolution to this issue, I would like to suggest that the file "/vendor/usr/keylayout/Generic.kl" be removed in the next FW release. The file in /system would be used, thus providing a correct generic mapping for key 28 = ENTER.
 
Fixed NEO A3 Voice Input - Thank you for the fix!!

Frame rate switching no longer works, can anyone test and confirm, i still get the blinks but frame rate stays at 60 for 24 movies. Thanks

edit: after disabling DV and setting HDR10 preferred, its working like it was in 006. Sorry for false flag lol :D
 
Last edited by a moderator:
Just a note of interest. In minix settings >display>screen resolution, after fw006a update the settings had reverted as follows:
1. Hdr Policy from "Adaptive Hdr" to "Always Hdr". I had set mine to Adaptive Hdr previously, because it provided a better black/white contrast. Now back on Adaptive Hdr

2. "Hdr Priority" had switched to "Dolby Vision" from "HDR 10". It is now back on HDR 10. It provides, (at least for me), a better picture. Might not suit everyone.
 
Just a note of interest. In minix settings >display>screen resolution, after fw006a update the settings had reverted as follows:
1. Hdr Policy from "Adaptive Hdr" to "Always Hdr". I had set mine to Adaptive Hdr previously, because it provided a better black/white contrast. Now back on Adaptive Hdr

2. "Hdr Priority" had switched to "Dolby Vision" from "HDR 10". It is now back on HDR 10. It provides, (at least for me), a better picture. Might not suit everyone.
Agreed ? 2 provides best experience in Coreelec
 
Btw don’t be spooked if the upload process show an image like this (attached) Update went fine i just had to patiently watch this crazy screen lol
 

Attachments

  • 213CC55C-9B6B-45ED-9688-087A5F66DC71.jpeg
    213CC55C-9B6B-45ED-9688-087A5F66DC71.jpeg
    1.6 MB · Views: 64
It is a pity that the root switch has gone, although I appreciate that it seems to have caused an issue for some apps. Hopefully you will be issuing rooted versions of future updates for those who want them, although I imagine that will involve having to manually install them.
We shall post a rooted version of 006A FW on the forum soon, so users who require root can manually install it.

EDIT:

The rooted version of 006A FW (20210203) is available to download from here:

https://theminixforum.com/index.php...ion-this-is-not-a-bugtracker.3739/#post-31307
 
Last edited:
Just one minor point for the Bugtracker. If you enter settings >device preferences>storage>internal shared storeage>cached data.
It takes 2 and sometimes 3 goes to clear.
This has been an issue since day one of receiving my box. Not really a big issue, but posted for info. And to add to the list of bugs.
 
Just one minor point for the Bugtracker. If you enter settings >device preferences>storage>internal shared storeage>cached data.
It takes 2 and sometimes 3 goes to clear.
This has been an issue since day one of receiving my box. Not really a big issue, but posted for info. And to add to the list of bugs.

My exprience with that, from day one, is:
It does clear, yet the info is not immediately displayed. Please do cache clear, then go back to the previous menu and reenter cache clear immediately after, you might see it did in fact clear as it should.
 
Thanks for that. I am already doing that. I just wondered why it did not show as " cleared" at the first attempt, as in the U9h or other android devices I use.
 
Back
Top