I've had fun messing with the datapack, fixing bugs and altering loot tables, but I've been wanting to do more.

I think it could be fun to make a datapack (or several perhaps) that serve as add-ons to matcha. Adding additional features and such.

I have been thinking about a major fishing content add-on, adding new fishing rods, food, lures, maybe even lava and void fishing if I can figure it out.

A much smaller idea I've had is adding a compass that points north (so I can finally stop using f3 constantly with maps), and maybe messing with the compasses, so that we have different compasses that work in different dimensions.

Does anyone else have ideas for add-ons? I think a good addon should be something that Klei probably wouldn't add to the base datapack, so then it makes sense to have it as an optional add-on.

In the current version of the datapack, the fishing loot is bugged.

The Cause

Some recent patch notes include "Fishing outside of pre-designated biomes no longer gives insane loot (junk pool at 85 weight as fallback)"

He modified the fishing loot table to add an entry at a weight of 85 that's just garbage, but he forgot to make it only apply "outside of pre-designated biomes". So it ALWAYS applies.

This means that, each time you fish (assuming you have no luck of the sea, for simplicity), you're getting the following:

• (wieght: 10) Trash
• (weight: 5 ) Treasure
• (weight: 85) Biome-dependant fish
• (weight: 85) Trash

So it ends up as about 51% trash, when the intended is 10%

The Fix

The fix for this is just a simple change to the fishing loot tables.

1. unzip the datapack (if you haven't already). You should get a folder called Matcha_Flavoured_1_12, or something along those lines. In that folder is all of the datapack and texturepack stuff.
2. Navigate through the folders data > minecraft > loot_table > gameplay > fishing
3. Create a file called fish_selector.json and put the text from this pastebin in it: https://pastebin.com/WLqyN7TN
4. Go back one folder (so that you're in data > minecraft > loot_table > gameplay)
5. Open fishing.json and replace it's contents with the text from this pastebin: https://pastebin.com/wp2zXgMp

Sorry if this is confusing, just reply if you don't understand something.

You just create one file, paste some stuff in it, then you open another file, and paste some stuff in that. That's it.

(This post mirrors a discussion post that I made on the HiBy OS Modding discord. Feel free to respond on here though, I'll still be actively reading and responding.)

The batteries in the HiBy OS devices seem to be prone to failure. There are many reports of HiBy R1 and Tempotec V1 devices having their cells pillow, which is a serious safety hazard. So we've been looking into ways to protect the batteries the devices come with and ways that we might be able to replace the batteries with safer ones (or even just replace them at all, once they go bad).

The HiBy R1 uses a 423554 3.85V 1150mAh cell. It's a similar cell in the variations V1, and I think it's similar across all of the HiBy OS devices (though I'd be very happy if someone proved me wrong).

We do have CFWs that set a charging cap, to extend the lifespan of these cells, but it can only do so much. The cells will degrade eventually, and we should be able to replace them when that happens.

Rare Cells

The issue is that 3.85V cells seem to be quite rare. I have a lot of experience finding data sheets for obscure batteries, and I haven't managed to find a single product/sheet that matches the specs of the R1 battery.

So I'm not sure if it's reasonably possible to source direct replacements for the batteries. It could be a good idea to contact HiBy, to see if they'll tell us where they source their batteries.

3.7V Replacements

There's a ton of cells we could get in the exact same form-factor that use the much more standard 3.7V chemistry. These batteries are way easier to get, last many more cycles, and should be a lot safer.

The issue is that the charge controller in the devices is (of course) built for the 3.85V cells, which cap out at 4.4V. Charging a standard 3.7V lithium cell all the way to 4.4V would kill it, since they cap out at only 4.2V.

The devices (at least the R1, and i think the R3Pro II) use the axp2101 charge controller. We have made user-level scripts that allow us to set charge limits, but these scripts only apply while the device is on. If the device is fully powered down, it would still charge the batteries all the way up to 4.4V.

I think by messing with the xImage in the .upt we may be able to set hardware-level limits that stay active when powered down.

Here's a picture someone else posted on the Reddit of the battery in the R1:

https://preview.redd.it/kuuuk2mwglfh1.png?width=1080&format=png&auto=webp&s=22e016a97a714fee382f39633ef8297b9f7a8103

We have a discord for sharing, talking about, and developing mods for HiBy OS devices. This includes all of the non-android portable DAPs in the current generation of devices (R1, R3 II 2025, R3Pro II, Tempotec V1, etc.)

This is the best place to see what mods exist, and to talk with the people making them. You don't have to be a developer to join, though developers are obviously very welcome.

https://discord.gg/22vhTYK3Y

Some of the projects we're working on:

• HiBy R1 Mod (By Bidhata/Krish) - The most comprehensive custom firmware (CFW) for the R1, combining many added features and fixes
• SpotUI - A spotify client for HiBy devices (currently just targeting the R3Pro II)
• Open HiBy Player - A project I have been working on for a while, writing a full replacement for the stock hiby_player program. (currently this project resides in the hiby-os-crack github repo, but i do plan to move it to its own repo soon)
• hiby-os-crack - A repo I've put together with some help from others that is all of the documentation and tools that you might need for modding the HiBy OS devices. I'm still adding new documentation, guides, and tools as they get found/created. It includes detailed hardware documentation for the CPUs, guides for installing/creating firmware, tools to easily unpack and repack firmwares, and a lot more!

As the modding community has been working on reverse engineering HiBy OS, we've found quite a few hidden features.

A couple days ago I found this developer easter egg page. It's pretty cool.

Crazy that this is hidden in the OS, haha. It's even animated, the fire moves!

A detailed guide on how to access this page can be viewed on the hiby_os_crack repo: https://github.com/hiby-modding/hiby_os_crack/blob/main/guides/EASTER_EGG.md

In short, you go to the "About" page at the bottom of the settings and press the HiBy logo a bunch of times.

Do be warned though, I'm not sure how to exit the screen other than restarting the device. It's not harmful or anything, just annoying to have to wait like 20 seconds for it to shut off and turn back on.

If any of you guys can figure out how to leave the screen, that'd be helpful.

https://preview.redd.it/dt0by1kzozch1.png?width=1240&format=png&auto=webp&s=f9b8145c0e22749578f042ff56c829c7be5c6db8

This is a repost from the discord server: https://discord.gg/f8uPd23pF

In my efforts to build a replacement for `hiby_player`, I've got to build a lot of features.

The core feature of a Digital Audio Player is playing digital audio (I know, right?).

But I can't figure out how to play sound without just using the original UI and hitting the play button.

The firmware has `aplay` built in. But whenever I run it, the device just restarts for some reason? Every time I try to play sound, it restarts. I have an R3Pro II. Endgame4 on the discord server has `aplay` working just fine on their system, but they have an R1. So we currently only have 2 conflicting data points.

So if anyone can figure out how to play an audio file through the command line on an R3Pro II (messing around through ADB shell should be the easiest way), that'd be really, really helpful.

Also if you have an R1, checking to see if it works as well for you or not will also provide useful information.

For anyone who doesn't know how to connect to the device's cli:

>Go into settings, then the about page at the bottom of the settings, tap the "about" text in the top left a bunch of times until the notification that test mode is enabled shows up. Then you plug the device into your computer, and on your computer run adb shell, and you should be connected to the device's cli.

This is a copy of a discussion post I made on the discord.

Hi all! I have a copy of all documentation, development tools, and the SDK for the Ingenic x1600 platform (which is the cpu that the HiBy OS devices use) I'm working on moving the documentation into the hiby-os-crack repo, but i'm not sure what to do with the dev tools and sdk

What I Have

• the dev tools i think are for flashing the devices. so i think that could allow us to fully replace the bootloader
• the sdk includes buildroot, so that's the full source for Ingenic's linux as well as a tool to build a cross-compiler
• the sdk i have includes kernel + cross-compiler for ingenic linux 4.4.94, 5.10, and 6.6. The current HiBy OS firmware uses 4.4.94, so it could be worth considering upgrading. i'm not sure what the benefits and drawbacks would be with upgrading though

i dont have a good way of sharing these tools, since the total disk space is over 13GB. I think i can cut that down by removing duplicate files and compressing it. but still

Question

does anyone know a good place for me to post these so that they can be shared with the community and preserved?

https://preview.redd.it/pubv26xmcl9h1.png?width=2260&format=png&auto=webp&s=41963f86ab182d0ba0bf18caccd37b20c9e8adcc

Hi! I've been helping to develop custom firmwares for the HiBy OS devices.

Currently, firmwares are kind of scattered across different GitHub accounts and Reddit posts. So I made a Discord server to help keep everything organized, and to let us chat in real time.

Both technical and non-technical people are welcome to join. It will be a place to share/showcase firmwares that have been developed as well as a place to collaborate on making the firmwares.

As it states in the rules, any inappropriate behavior will not be tolerated. No spamming, no hate speech, etc.

https://discord.gg/5BdZ4WEZR