Revue and Accessories

[ericnhitterdal]

(Insert Signature Here)

[veeeee]

I would love to see this. I would buy more units if they did it.

[modder420]

i agree and since i feel riped off paying 300 its the least they can do just saying.

[ericnhitterdal]

I paid 300 also... even pre-ordered it...

so this is a long awaited update, and freeing up the bootloader etc would help out all the guys at gtvhacker!

[Craysh]

I completely support this suggestion.

I understand that certain proprietary parts of the system may need to be protected.  That's simple enough to alleviate:

Make the relevant pieces into apps.

Opening the bootloader will make it a community affair.  In one fell swoop Logitech would be in the good graces of the Revue community.

[Bostwickenator]

I vote for this too.

[jim729]

Logitech owes those of us that have been lied to.  The Logitech APP is a terrific idea.

[note4shawn]

Since I own four Revues then I +4 this petition!

[Aqualung]

I take it, there's no way to attempt to install either of Chromium OS or ICS-x86 on the Revue without an open bootloader, right? How did those that installed the leaked Honeycomb do it though?

[Eferzz]

---

Aqualung wrote:

I take it, there's no way to attempt to install either of Chromium OS or ICS-x86 on the Revue without an open bootloader, right? How did those that installed the leaked Honeycomb do it though?

---

All the developer leaks were fully signed Android update packages from Logitech. That's why there's not much in the way of "underground development" for the Google TV. In the second developer leak, they even removed the ability for user input while in recovery. Therefore, holding down the power button while the Revue is booting up will no longer initiate the USB update process.

There are probably contractual agreements with Intel and Google which prevent Logitech from releasing it. After all, the boot loader for the Revue is built into the CE4150 processor. That's why they have to use the Intel's Consumer Electronics Firmware Development Kit (CEFDK) whenever they build finalize a patch.

Google still needs to prove to the content owners that Google TV is a safe platform. Otherwise there's nothing to stop someone from overriding the HDCP copy protections if they have full access to the kernel. This is one of the main reasons that the Native Developer Kit (NDK) is still not compatible with Google TV; not even the x86 NDK.

Remember, Google is still trying to smooze the content providers to embrace Google TV as a tool to enhance their product offerings. So, leaving a security hole that will prove that they do not have control over the platform will be seen as a threat to content owners and distributors. This is why "security updates" continued to be pushed by Google even after Logitech appeared to cease development for the 2.1 platform at the beginning of March.