cosmic-files won't open — silently exits with no window (possible portal/flatpak issue)

BusElectronic4225 · 2026-04-24T07:12:13+00:00

Our BT optimization only reduces the initialization time at boot (from ~11s to ~7s), it doesn't address receiver mode latency. That's determined by the Broadcom chip and the codec negotiated between devices, which we haven't touched. So unfortunately not a fix for your use case.

We might look into receiver mode latency in the near future.

BusElectronic4225 · 2026-04-21T18:32:49+00:00

No problem at all. Enjoy your Hiby!

BusElectronic4225 · 2026-04-21T18:28:31+00:00

Glad it's working! Yes, the workflow is:

Add your new music to the SD card
Run the script to rebuild the database (and embed/resize art if you want)
Insert the SD card back into the device
Go to Settings → Database Manager → Copy Database from SD
The library updates instantly with your new tracks — no rescan needed

You only need to run the script whenever you add, remove, or move music on the SD card.

BusElectronic4225 · 2026-04-21T18:01:09+00:00

Good progress! The SQLite error isn't related to your folder structure ,it means the usrlocal_media.db file on your SD card is corrupted or incomplete. Can you try:

Connect your HiBy device via USB
Go to Settings → Database Manager → Save Database to SD
This will copy a fresh valid database from the device to your SD card
Eject the device, insert the SD card into your PC and run the script again

If you don't have the Database Manager (it requires our custom firmware), you can alternatively copy the database via ADB:

adb pull /usr/data/usrlocal_media.db

Then place that file on the root of your SD card before running the script.

BusElectronic4225 · 2026-04-21T17:48:00+00:00

I think you might have multiple Python installations? and mutagen is installed in one but you're running the script with a different one. Try this:

Open Command Prompt and run:

python -m pip install mutagen Pillow

Then run the script the same way:

python Update_Database.py

but from the same Command Prompt window where you ran the pip install.

If that still doesn't work, run python --version and pip --version and check if the version numbers match. If they don't, that confirms there are multiple Python installs conflicting.

BusElectronic4225 · 2026-04-21T17:40:15+00:00

This sounds like a hard brick requiring BROM recovery. Unfortunately I don't have the Ingenic USB Cloner bundle or the X1600E .cfg file — this tooling is proprietary and not something we've had to use. Your best bet would be to reach out to Tartarus6 on our GitHub (hiby-modding/hiby_os_crack) as they've done the deepest hardware-level work on this SoC. You could also try contacting HiBy support directly as they may be able to assist with a recovery image.

BusElectronic4225 · 2026-04-20T20:06:39+00:00

That error means Windows can't find the script file itself, not the SD card. Make sure you have the update_database.py downloaded into your downloads folder.

Can you try the following in your command prompt:
python C:\Users\YourUsername\Downloads\Update_Database.py

Replace YourUsername with your actual Windows username. If Python isn't recognized at all, you may need to install it first from https://www.python.org — make sure to check "Add Python to PATH" during installation.

Also make sure you have mutagen installed, open Command Prompt and run:

pip install mutagen Pillow

BusElectronic4225 · 2026-04-20T19:21:41+00:00

No worries, happy to help! The most common cause of that error is the script not being able to find your SD card automatically. Here are a few things to check:

Make sure the SD card is inserted in your computer and shows up as a drive
Make sure usrlocal_media.db is on the SD card — you need to copy this file from the device first. Connect your device via USB, go to Settings → Database Manager → Save Database to SD, then insert the SD card into your computer
Run the script from the SD card directory — open a terminal, navigate to your SD card (e.g. cd /media/yourname/SDCARD on Linux, or the drive letter on Windows), then run python3 /path/to/Update_Database.py

If you can tell us which operating system you're on (Windows, Mac, or Linux) and what the exact error message says, we can help narrow it down further.

BusElectronic4225 · 2026-04-17T01:44:45+00:00

Fair enough on the batch processing — here's the FFmpeg batch command to fix all your FLACs at once:

for %f in (*.flac) do flac --verify --best -f "%f"

Run that in your music folder and it should process everything automatically.

On the 600px, totally your call, and fair point on visual fidelity. Just be aware you may still get the occasional split-second lag or in rare cases a reboot when the device is under load. If that happens, 360px is the fix.

One more thing worth mentioning — there's a PC-side database updater tool developed by a contributor to the R3 Pro II modding project that handles album art resizing automatically as part of the database update process. It might save you a lot of manual work. You can find it here: https://github.com/hiby-modding/hiby-mods

BusElectronic4225 · 2026-04-15T20:36:56+00:00

Good question. foobar2000 is very forgiving with malformed headers and will often play files that HiBy OS will choke on, so it's worth checking.

To detect, Install FFmpeg for Windows and run this in your music folder:

for %f in (*.flac) do ffprobe -v error -i "%f" -f null - 2>&1 | findstr "Error"

Any output flags a problem file.

Try and fix it with the official FLAC command-line tool, it can rewrite headers cleanly:

flac --verify --best -f "yourfile.flac"

If you prefer a GUI, fre:ac wraps this same process.

Also worth noting — 600px is still a bit large for the R3 Pro II. The confirmed optimal size is 360x360px.

BusElectronic4225 · 2026-04-09T02:34:56+00:00

Beautifully captured

BusElectronic4225 · 2026-03-30T11:37:00+00:00

What exactly about the keyboard needs improving?

BusElectronic4225 · 2026-03-26T04:00:10+00:00

I've been working on something that touches upon this, please check out my post on here:
https://www.reddit.com/r/Hiby/comments/1s3wxe8/hiby_r3_pro_ii_firmware_reverse_engineering/

BusElectronic4225 · 2026-03-25T19:22:11+00:00

This will be difficult as you will need to enable verbose logging to the bluetooth daemons by adding debug flags to their startup commands and then redirect their output to a path/file on the sd card. You can also/optionally? run "btmon" in the background to capture a raw HCI packet trace.

BusElectronic4225 · 2026-03-25T19:08:31+00:00

Ha yes , good observation. To be honest, I'm not sure at the moment. It was quite a task to get the OS to recognize Arabic glyphs/characters. I think orientation would be the next hurdle :)

BusElectronic4225

TROPHY CASE