Hello CinemaGo and CinemaTube Mini owners,
CinemaGo = CinemaTube Mini + Wifi Adapter
We are happy to announce that the first official firmware update is now available. This time we added the MUZEE internet video (BETA version) so you can enjoy thousands of online video channels without any subscription fees.
To activate your MUZEE Internet TV channels, please perform the through “online update”. You can find that option by going to:
Home –> Setup –> System –> Software –> Online Update
We strongly suggest you using a wired Ethernet connection when performing the online update.
If that is not an option, please see this page for a step-by-step tutorial on how to perform a “USB update”.
Here is the release note for firmware version IPB15107151:
- Muzee Internet radio support
- Muzee Internet TV support (BETA)
- Improved eSATA compatibility
- Resolved photo thumbnail display issue via UPnP
- Resolved rebooting issue caused by “File Copy”
- Enhanced HFS+ compatibility
If you have any questions, please do not hesitate email us at service@brite-view.com.
***Please note the CinemaGo/CinemaTube Mini and the CinemaTube DO NOT share firmware. Forcing the firmware of the CinemaGo on the CinemaTube will cause the damage of the CinemaTube, and vice versa.***
CinemaTube Mini
« New brite-View LinkE Review from “TechyDad” CinemaTube’s 100th Review Available on Amazon! »
So where is the new firmware? I’m still seeing version IPB10106251when I click on the link.
Hi Kiet, this firmware is for the CinemaGo and CinemaTube Mini, and is available on the support page. The new firmware for CinemaTube with the new UI (also available for CinemaGo and CinemaTube Mini) will hopefully be available in September. Thank you for your patience with us!
The links for the CinemaGo firmware update from the support page are broken. For example, the link for the sig file is:
http://www.brite-view.com/firmware-5005HDMiniCG/07042810/install.img-sig.txt
It should be 07282010 instead of 07042810. The actual .img file has the same issue. If you replace that, you can download the file. However, when I do that, I get this for the the SHA1 hash for the sig file:
ad1bdbe4def59cf3966636a225f7f886e7c68aaf
which, obviously, is not what is on the support page. The SHA1 hash for the .img file is correct (except that you have an extra “1″ at the end, making 41 characters in a SHA1 hash signature).
@James: it certainly was broken. We are going to fix that today. Thank you for taking the time to let us know.