I was a bit more impatient, so in September 2011 I started on my plan with a Huawei Slim S7. Honestly, the story is a bit different and I need to take another short detour. The absolute right timing for my plan! Amazon, how did you know that I would need.? The summary of this: the Kindle Fire is just open enough to be an attractive hacking platform, while the Blackberry Playbook is just closed enough not to be! So, finally my passion went with the Kindle Fire. releases! They obviously don't care about us hackers and developers (who should we blame to not include a proper nfig?). That's true! But then what about the operating system? 3) Amazon releases at least the source code. Ok, talking about pure hardware-mods here, you could argue now: simply ignore that locked Blackberry bootloader and set the OMAP4 SYS_BOOT bits right and you'll get around it. But the Fire is 1) way cheaper and 2) (more) open!
The hardware was very right and I would still prefer it over the Kindle Fire. rocket to enter the tablet market! And very much because they got the price wrong. But that was not as open as the Kindle Fire. I had known the Pandaboard and Blaze from Texas Instruments before, so I was familar and happy with that basic TI platform.Īt that time my passion had almost gone with the Blackberry Playbook already.
KINDLE FIRE HACK ANDROID MOD
The rest I could hack and mod myself, learn something by doing so and have some fun at the same time. Actually less, but it's good at what it offers and that counts most for me. The Kindle Fire had a lot, not more than I needed. My plan needed a powerful dual-core embedded platform with a good and bright display and a capacitive touchscreen. Every now and then I'll drop a few more details about that plan here, too, but now I want to tell you more about how I got my 2 Kindle Fire(s).Įver since the Kindle Fire came out in November 2011 I wanted to have it. My passion for the Kindle Fire started shortly after developing a plan for my project in mid 2011.
0 kommentar(er)
