did the op get updated? what version did u install Cody?
Sent from my HTC Glacier using xda premium
Sent from my HTC Glacier using xda premium
[ROM][24 Feb] IceCreamSandwich Development/Discussion Thread
- Thread starter bl1nkk
- Start date
Dude just so you know Task Killers aren't needed by Android anymore. The in house memory management works just fine since 2.2. By constantly freeing up memory those task killers just put a drain on battery life.
Just a few quick questions...
- I haven't seen anyone else say anything about this, but I mentioned it earlier: Viewing Storage or App settings crashes the OS. Has anyone else seen this?
- Can someone get me the stock bootanimation.zip from this, I kind of messed mine up and would like to not have to flash the OS again...
- What's the latest development? We haven't seen many bug fixes or anything for a day or two now.
The current state of my latest build is:
Video still is broken and sound is borked
Wifi battery drain is fixed and sdcard issue is fixed. Apps cannot be moved to the sdcard as there is no sdcard so the one present is almost a "virtual" thing for storing stuff
I've taken out some bits and everything seems more fluid but there are still a few hesitations but they are few and far between. Battery of pure web browsing as I was doing last night for more than an hour drops about 1% every four minutes giving us ~400 minutes of pure web browsing with the screen on which is about 6 hours and 40 minutes of nothing but web browsing with the screen on its lowest setting
Sent from my Galaxy Nexus using XDA App
Video still is broken and sound is borked
Wifi battery drain is fixed and sdcard issue is fixed. Apps cannot be moved to the sdcard as there is no sdcard so the one present is almost a "virtual" thing for storing stuff
I've taken out some bits and everything seems more fluid but there are still a few hesitations but they are few and far between. Battery of pure web browsing as I was doing last night for more than an hour drops about 1% every four minutes giving us ~400 minutes of pure web browsing with the screen on which is about 6 hours and 40 minutes of nothing but web browsing with the screen on its lowest setting
Sent from my Galaxy Nexus using XDA App
Nice, so do the settings still cause it to crash, or does the virtual sdcard fix that? And does the wifi battery drain fix also fix the 1008 cpu issue?
I never has that problem of it crashing, but I just checked and it didn't so I guess we're in business
Sent from my Galaxy Nexus using XDA App
Sent from my Galaxy Nexus using XDA App
Disable notifications on your Fire, and it will freak out. The only way to fix the problem is by wiping, because it causes the UI to crash - so make sure you backup first
Disable notifications on your Fire, and it will freak out. The only way to fix the problem is by wiping, because it causes the UI to crash - so make sure you backup first
Good find, I know for sure that's something I would've overlooked, and I bet the devs would've too.
Last edited:
The one in the OP, downloaded it last night.
Some noticeable things are video and audio of course.
I haven't tried much, also I just installed Advanced Task Killer to see if it actually worked.
Ignore the messy bedroom in the back, been changing my bedroom around and moving furniture.
Can't embed video for some reason.
But here it is: http://www.youtube.com/watch?v=H7v9BDR5EM0&hd=1
Video showing Ice Cream Sandwich on the Kindle Fire.
Some noticeable things are video and audio of course.
I haven't tried much, also I just installed Advanced Task Killer to see if it actually worked.
Ignore the messy bedroom in the back, been changing my bedroom around and moving furniture.
Can't embed video for some reason.
But here it is: http://www.youtube.com/watch?v=H7v9BDR5EM0&hd=1
Video showing Ice Cream Sandwich on the Kindle Fire.
Last edited:
My build is up on Github currently under KFire-Android. It's using the hwcomposer.default right now. It's buildable.
Edit: it's buggy too. Need a day or 2 to sort stuff out.
Sent from my XT862 using XDA App
Edit: it's buggy too. Need a day or 2 to sort stuff out.
Sent from my XT862 using XDA App
Last edited:
Flash the Gapps.zip included in the OP.
http://api.viglink.com/api/click?fo...v8.koush.zip&jsonp=vglnk_jsonp_13251954600861
What he said. Just to clarify because I made this mistake: Flash it through TWRP, don't extract the zip and try to install that way. It won't work. You have to do it through TWRP.
Thanks for the update...
Would it be possible to silently post your updated build for all us impatient fools, uhh "early adopters"?
Anyway, I've been running this as my daily driver and now that I have a ICS rom on my phone I don't want to go back to Gingerbread...
Thanks for the update...
Would it be possible to silently post your updated build for all us impatient fools, uhh "early adopters"?
Anyway, I've been running this as my daily driver and now that I have a ICS rom on my phone I don't want to go back to Gingerbread...
I think the problem with this is that it takes forever to compile, so they hold off till they make a major step forward. Although I would like to see this too. I've been using it as my main ROM even though I really need audio and video to work to use the thing how I want to (as a media consumption device). I keep recovering back to CM7, and just can't stand it after ICS.
I'll think about it ;-)
Our builds are almost identical
The one I'm running now is going very well. You'd have to do some reconfiguring as you may lose your launcher preferences as a bunch of stuff has changed since your build
I warn you that videos won't play and that sound is almost useless
Sent from my Galaxy Nexus using XDA App
Our builds are almost identical
The one I'm running now is going very well. You'd have to do some reconfiguring as you may lose your launcher preferences as a bunch of stuff has changed since your build
I warn you that videos won't play and that sound is almost useless
Sent from my Galaxy Nexus using XDA App
My max build time is about 1 hour.... If github (KFire-Android) is updated, I can build it. If my ccache is reasonably up to date, it's more like 30min. I'm happy to post builds if the devs don't mind. I've been meaning to help in a more meaningful way, but the current issues aren't areas I'm as familiar with. I'm keeping an eye on things though.
So if it's desired, I don't mind doing daily builds when there are changes, etc.. It's up to them though, I don't want to be causing them more headaches than they already have.
My max build time is about 1 hour.... If github (KFire-Android) is updated, I can build it. If my ccache is reasonably up to date, it's more like 30min. I'm happy to post builds if the devs don't mind. I've been meaning to help in a more meaningful way, but the current issues aren't areas I'm as familiar with. I'm keeping an eye on things though.
So if it's desired, I don't mind doing daily builds when there are changes, etc.. It's up to them though, I don't want to be causing them more headaches than they already have.
I think us pre-alpha testers would love that. It sounds like the latest build is up on that github, and I don't see what'd it'd hurt to compile it for us. I'd love to see what works in the latest update
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
243IceCreamSandwich 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
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
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
None needed.
The devs do all of this for free, remember that. Buy them a drink! ♥36Here 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
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).35here'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 ones31Sound = 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!30
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
Code:While(whine==true) do repost this.post end
