• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][24 Feb] IceCreamSandwich Development/Discussion Thread

Search This thread


Senior Member
Mar 15, 2007

Top Liked Posts

  • There are no posts matching your filters.
  • 243
    IceCreamSandwich Development/Discussion Thread
    Hello everyone! This thread is dedicated to Hashcode's and JackpotClavin's work.
    This is an Android 4.0.3 ROM not meant for daily use! It is based on CyanogenMod 9.

    I will not post any instructions how to flash this to your kindle until it is considered to be ready for daily use. If you know how, feel free to do it.

    If you want to join us on IRC:
    irc.freenode.net #kindlefire-dev

    What works? What doesn't?
    revxx14 created a Google Spreadsheet to collect known bugs. You can find it right here.
    Please take a look at it before reporting any bugs!

    A rough list what does not work:
    • Hardware Video Decoding
    • Light sensor
    There is a SOD bug and no, there is no bluetooth.

    2012-02-24 cm9-02-24.zip
    ff4e0ea9c27d28b18226e230e2bf2994 by sitic

    +init.d support
    +fix default.prop
    +Test: Apps use now xlarge layout instead of large
    More information here

    Google Apps:

    None needed. :)

    The devs do all of this for free, remember that. Buy them a drink!
    Here is a new build:


    +init.d support
    +fix default.prop
    +Test: Apps use now xlarge layout instead of large

    * I'm not sure if init.d is working as it should, to my impression it's executing too early. I've tried to set it such that it executes init.d when the sdcard is ready but convinced that that worked. Could someone test it properly for me?

    * I'm breaking with Google's guideline for display sizes here, if you look at that graphic

    you'll note that the Fire is on the edge between the large and xlarge layout for apps. However from the code you see that it is using large layout for apps as it has less then 720 Pixel on the short side. In this build it force apps to go with xlarge layouts, i did that to test if apps looks better and use tablet features. Comments on this are welcome, in particular if there are apps which work significant better with this release. However with next build i think i'll go back to the stock large layout.

    This build does not include the new boot animation, as that one is not in the cm sources yet. if you really want it, someone used the image from the youtube video to get the boot animation, follow the instructions on this thread. For the battery percentage display: that are changes from cm, i think they'll make a setting for this soon.

    I was working on otg (usb host mode) support, the kernel loads it now, but it fails at loading USB 2.0/1.1 drivers (working on this, it's not included in this build).
    here's the .zip with working video. I've also implemented XDA user Chiggins' better volume slider which is much better than my uglier icon

    everybody give Chiggins a big thanks! he's the reason we can have nice things

    i also cherry-picked a change that hasn't been officially approved that cleans up and fixes some of the touch input code which fixes a lot of the touch events not doing anything. i saw a difference with touch input, hopefully you guys will too :)

    md5sum: 43879eaacc0104af2f935c366cbc0244

    this wipes your /system and /cache so you'll have to reflash gapps which can be done consecutively. HD videos do not play with the youtube app, if you come across an hd video that you'd like to watch, just hit the little HD button and it will drop down to normal resolution and will begin playing after that. the little HD button i'm talking about is here

    enjoy folks. i think that's it for the major bugs and missing functionality since we've upgraded to ics, now on to the tinier ones :)
    Sound = Working!! Update probably tonight for everybody! Sorry I had been away for quite some time; I had a string of family emergencies and the death of a loved one earlier this week :( Now just video and we should be set!
    I think what would shutting most people up regarding hardware acceleration is if the developers actually discussed it instead of saying a damn goat died, or a kitten, or a puppy.

    Right now there is so much debate on Windows 8's Start Screen and if you EVER checked the Building Windows 8 blog, their blog entries seriously are life stories...so much is explained that it gives little reason to nag about.

    If we had any kind of information regarding hardware acceleration, I think a lot of us would shutup including me. BUT because the developers refuse to release an update, we're stuck in the dark with people saying we killed kittens. Seriously grow up, I don't need to shutup and a door slammed in my face.

    Release an update regarding hardware acceleration, I have some very big doubts that anybody is working on it...maybe once-a-month effort is put into it, not even. I'd like to know that work is being done on it, then MAYBE I wouldn't be so damn doubtful and MAYBE people would stfu already about it.

    I'm sorry and I love the development of ICS for the Kindle Fire, but it has a long way to go. Nothing is quite fluid and from what I hear, hardware video decoding is apparently the same thing as hardware acceleration, and apparently none of that works. I want some fluidity on my Kindle Fire running ICS. I could care less for HD video playback, all of my stuff plays fine in standard definition via MX Player.

    It sounds like you need a little insight. Let's see if I can bring you some.

    ICS (or Android 4.0.3) is based on the Linux 3.0.x kernel. This kernel (opposed to the previous 2.6.x) has a few new bells and whistles which makes some parts of ICS (HW acceleration for example) dependent on the 3.0.x kernel.

    The KF is OMAP based (Texas Instrument platform) and has yet to receive the 3.0.x kernel from Amazon. Without the 3.0.x kernel, we have to back-port (i.e reconstruct the new bells and whistles) to the 2.6.x kernel. This is very tedious and time-consuming.

    Today, there are basically two paths on this;
    • Back-port everything necessary to the 2.6.x kernel. This is what Hashcode set up to do initially.
    • Get the 3.0.x kernel booting. TI has a working 3.0.x kernel on their OMAP devices named Blaze. The KF has the Otter board in it. Thus, to get it booting we have to customize the config to match the Otter board and be able to debug why our current one isn't.

    Right now, most of the work is poured into getting the new 3.0.x working. Unfortunately, the USB interface is initialized quite late in the kernel boot, which makes it really difficult to debug (we're basically blind). That's why I started a thread in finding the UART pins on the KF, to be able to debug properly.

    I hope this gave you some well needed information. And hopefully I didn't just encourage you to keep whining.

    Ps. I bet pressing the Donate-button will speed things up a little :)

    While(whine==true) do
       repost this.post