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

Search This thread
By:
Advanced…
Takenover83

Takenover83

Senior Member
Nov 6, 2009
907
427
YouTube works fine as reported, as long as you unclick the HD button as mentioned. I did gets some weird graphic corruption in the youtube interface before I click a video. But rotating the screen by tilting the tablet seem to clear it up.

NetFlix does not work for me. Just a black screen. I tried setting Video Quality (Netflix website options) to Good or Better. Disabling, Best "which if available can do HD". But none the less. Just a black screen.
 
Last edited:
  • Like
Reactions: DeerSteak and icebuck
Chiggins

Chiggins

Senior Member
Jul 22, 2010
99
25
blog.chigstuff.com
revxx14 said:
Nice! Download the video ROM now :)

For Chiggins, or someone who knows how to do this...Can someone replace the icon from Chiggin's volume slider with this one?

http://dl.dropbox.com/u/12147973/ic_sysbar_volume.png

It's the same dimensions and should be ready to go, but I can't figure out how to properly repackage the SystemUI.apk. The icon that I just linked to is taken from the Settings menu, resized, and coloredd to match the rest. Not a big deal, but I'd really appreciate if someone could at least make me a tweaked SystemUI.apk with that icon instead.
Click to expand...
Click to collapse

Yeah I'll do that, I gotta fix this one problem though because I can't build anything :|
 
  • Like
Reactions: lman00, powercrim, danij3l and 1 other person
rukin5197

rukin5197

Senior Member
Jul 26, 2011
838
797
Flashing now, reporting later. Great job!

Sent from my Amazon Kindle Fire using Tapatalk
 
Takenover83

Takenover83

Senior Member
Nov 6, 2009
907
427
Qloud Media Player also does not work. It's a app similar to Plex. So I am guessing Plex will also not work. Just a black screen (with audio).
Qloud/Plex are media players that use a server on your pc to transcode media on the fly to your device.
 
Last edited:
lovejoy777

lovejoy777

Inactive Recognized Developer
Dec 30, 2011
3,725
4,541
Nottingham
been hanging on black screen for about 5 mins after reboot i flashed new rom and gapps then rebooted

---------- Post added at 11:39 PM ---------- Previous post was at 11:34 PM ----------

sorted just reflashed rom and gapps again.
(it allways makes your ass twitch when these things happen)
 
D

DeerSteak

Senior Member
Jul 25, 2011
383
59
The touch screen is definitely more responsive, and as others have reported Youtube in SD works for me. This is truly a herculean feat. :D

Also, assuming 3 hours is long enough for the device to fall into deep sleep for the previous SOD issue, the 1/19 build was fine once I set my CPU to 600MHz.

So when I look at the Cyanogenmod stats page, is this device an otter or a blaze? The build says otter, but the CM7 builds all say the device is a blaze.
 
Last edited:
B

biglama

Senior Member
Sep 23, 2008
77
23
Detroit
Any fix or work around for screen taps registering as a flick/drag? I'm using apex launcher and have Widgets that I want to resize and move that are 'stuck' because long pressing always moves work space to the right.

The screen does feel more responsive on the newest update and I had this issue on the previous release (Jan. 19), if its not already in the bug tracker let me know to add it.

Overall I am very impressed with the progress, a million thanks and a donation on the way.


Edit: The default launcher does not exhibit this issue, seems to be application related. DEVS please disregard.

Sent from my Amazon Kindle Fire using XDA Premium App
 
Last edited:
D

DesDr0id

Senior Member
Jan 9, 2012
79
16
First off, a HUGE THANKS to Jackpot and all the other devs working on this. I just gave this ROM a shot after hearing video and sound were for the most part, working. Amazing work!!

I've gone back and re-flashed back to CM7 however :)

There is no USB mounting in this latest version, which in my case was a deal-breaker, I'm sure it will eventually get addressed.

I would also like to point out that the development of the ICS port for the NOOK COLOR is quite far along, (they have USB mounting amongst other things), which I suspect that code (at least portions of it) would be re-usable for adding such functionality or simply for a comparison of how things are implemented from the coding perspective.

http://xdaforums.com/showthread.php?t=1370873

Looking forward to seeing what will come over the next few months! Keep up the great work!
 
f2

f2

Senior Member
Jan 9, 2008
138
15
Gute Arbeit bl1nkk! Well done Jackpot ... :)

Local streaming clients like Qloud don't seem to work too at the moment. But ICS on the Kindle Fire is still fantastic!

Did anyone test other versions of gapps? I'm really missing Gtalk ... Thanks!
 
Last edited:
dcaplinger76

dcaplinger76

Senior Member
Sep 23, 2010
1,259
212
Oklahoma City
I got stuck at the touch the Android screen, as soon as I touch it, it says unfortunately setup wizard has stopped. Gonna try and reflash but curious if anybody else had this

Update : Must have been the version of gapps I was flashing... Tried not flashing any and it started right up.

Sent from my HTC EVO 3D using xda premium

---------- Post added at 06:56 PM ---------- Previous post was at 06:25 PM ----------
DesDr0id said:
First off, a HUGE THANKS to Jackpot and all the other devs working on this. I just gave this ROM a shot after hearing video and sound were for the most part, working. Amazing work!!

I've gone back and re-flashed back to CM7 however :)

There is no USB mounting in this latest version, which in my case was a deal-breaker, I'm sure it will eventually get addressed.

I would also like to point out that the development of the ICS port for the NOOK COLOR is quite far along, (they have USB mounting amongst other things), which I suspect that code (at least portions of it) would be re-usable for adding such functionality or simply for a comparison of how things are implemented from the coding perspective.

http://xdaforums.com/showthread.php?t=1370873

Looking forward to seeing what will come over the next few months! Keep up the great work!
Click to expand...
Click to collapse

I use wifi explorer pro... that way I don't even have to touch the usb
 
Last edited:
  • Like
Reactions: emelie and DeerSteak
You must log in or register to reply here.

Similar threads

twa_priv
[ROM] CM10/SGT7 for the Kindle Fire [20130117]
Replies
4K
Views
1M
sd_shadow
sd_shadow
Hashcode
[ROM/KERNEL] OFFICIAL CM11.0 + 3.0.72 Kernel for Kindle Fire [NIGHTLIES]
Replies
3K
Views
1M
M
mikeataol
NRGZ28
[ROM][ICS] |July 31| Energy™ -.¸¸.·´¯ ICS CM9 3.0 Kernel / Lightly Themed ¯´·.¸¸. -
Replies
1K
Views
501K
S
samreh
Hashcode
[ROM-AOSP] [OLD] Stock Jelly Bean 4.1.2_r1 for the Kindle Fire [10-10]
Replies
887
Views
646K
S
spartan77
twa_priv
[ROM] [JB 4.2.2] CM10.1/SGT7 for the Kindle Fire [20130724]
Replies
2K
Views
632K
t3chwizard
t3chwizard

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 243
    bl1nkk
    bl1nkk
    IceCreamSandwich Development/Discussion Thread
    What is this?
    Click to expand...
    Click to collapse
    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?
    Click to expand...
    Click to collapse
    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.

    Downloads
    Click to expand...
    Click to collapse
    ROM:
    2012-02-24 cm9-02-24.zip
    ff4e0ea9c27d28b18226e230e2bf2994 by sitic

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

    Google Apps:
    gapps-ics-20120224-signed.zip
    11b5763810edb732379d39b6df9ccbcf

    Workarounds / Fixes
    Click to expand...
    Click to collapse

    None needed. :)

    Last words
    Click to expand...
    Click to collapse
    The devs do all of this for free, remember that. Buy them a drink! ♥
    View
    36
    N
    nind
    Here is a new build:

    cm9-02-24.zip
    ff4e0ea9c27d28b18226e230e2bf2994

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

    Remarks:
    * 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
    screens-ranges.png

    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).
    View
    35
    JackpotClavin
    JackpotClavin
    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
    http://www.mediafire.com/?y8eocgddv569mdc

    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 :)
    View
    31
    JackpotClavin
    JackpotClavin
    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!
    View
    30
    C
    csholmq
    sionicion said:
    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.
    Click to expand...
    Click to collapse

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

    Background
    Click to expand...
    Click to collapse
    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.

    Development
    Click to expand...
    Click to collapse
    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 :)

    Code: 
    While(whine==true) do
   repost this.post
end
    View

New posts