Just tested here with Minix A2 Lite and Minx NEO T5, working without problems on 9.2.2.
My question was more about knowing if he bl301 injection and the IR code MINIX allowed for controlling a non-minix box.
I was just lucky and had the NEO T5 connected what have bl301 injected. Who will deny the wake up by Minix IR code on any box?
ok, then I have an issue with my box, I will investigate and report back. thanks for your help.
Hi, updated to 9.2.2 on my Odroid N2. All working well except I now have this inject BL301 thing running and it leaves a log in my storage directory stating my device is not supported. I have no need for this, everything was working fine before. How can I disable it? Can’t find any controls and if I run inject_bl301 from an ssh session it says my device is not supported, thanks.
No need to run inject_bl301 for N2
I understand that, as I said I have no need for it. I can see it’s running on startup since I see an HK logo on startup (dislike that) and it’s leaving a log. I want to disable it, preferably uninstall it. How can I do that?
When you don’t like then just ignore it and disable any option in config.ini!?
Also you need to disable the service:
systemctl mask update-bl301.service
Then you need to compile your own version and unset this linux config value:
Not sure I understand. So is there a way I can tell it not to run without actually rebuilding the whole thing? Compiling my own version is not something I can do. Thanks.
Let me reiterate that last comment, I don’t really care if it runs or not, I just want to disable the HardKernel splash screen on startup and tell it not to create a log in the root of my storage directory.
If that’s not something I can do without a recompile I won’t worry about it. I’m just asking if there’s any controls for that. I’ve been setting my options in config.ini all along so no problem for me to continue doing that.
I don´t understand the problem ?
I never used inject_bl301 on my N2 as it’s not needed. Did you ever use/run it in spite of that ?
In your case, I’d make a full backup -> new/fresh install -> restore backup, to solve this problem.
HK logo is used across all OS images, Petitboot, Ubuntu, Android…, and I’m glad that it found it’s way to CE. If you don’t like it you can replace it with one you like, or remove it…
Thanks, how can I remove that splash screen (yeah I really don’t like it)?
Any way to stop that inject_bl301 log from appearing in the root of my storage directory?. I’d be happy it there was a way to put into the logs subdirectory. I put my own stuff in the root of storage and I don’t want any junk in there, especially a log file that provides no information other than to say, “sorry, I can’t run.”
I told you already…
Several ways; replace “boot-logo-1080.bmp.gz” from 9.2.2 with the one from 9.1.1, or make your own 1080.bmp compress it to .gz, or put an empty file for “boot-logo-1080.bmp.gz” or simply delete it…
The splash screens are locked down to prevent pirates repackaging CE.
HardKernel splash screen (the first one shown) is NOT locked. Only CE splash is hardcoded.
This is my N2 background:
boot-logo-1080.bmp.gz (1.5 MB)
It is very hard to see…
Will use yours for background for present HK logo to see how it looks
Something like this:
boot-logo-1080_1.bmp (5.9 MB)