[ROM][24 Feb] IceCreamSandwich Development/Discussion Thread
- Thread starter bl1nkk
- Start date
Can't fully comment on battery life by the browser works great.
Sent from my Kindle Fire using xda premium
Could you put in ES File explorer instead? I find it much more intuitive, and you can enable root access in the settings.
Sent from my Kindle Fire using Tapatalk
Sent from my Kindle Fire using Tapatalk
Browser is great, battery life will suffer because of the wakelock, and haveing the cpu stick around 1ghz contently...
Yea. I just got this today and found out my boot loop-type problem was from selecting reboot to recovery in the utility prog. Fixed it up now tho and running smooth. This is nice!
I am trying to flash this to test it out, and I seem to be stuck in a boot loop. I have the .zip on the kindle, and I flashed it, but I get the same message as bl1nkk. I then reboot, and it boots back into recovery. What do you suggest I try?
You need to change the bootmode back to 4000. Use fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
should then say <waiting for device>
Reboot your tablet, bootmode will be updated and you should be good to go. In future, don't use "Reboot to Recovery"
browser has worked great for me as well, not sure about battery life yet.
Things I noticed so far that don't work:
(of course it is not an everyday rom to use yet and of course things are not going to work all the time, but i thought I would share what i have come across)
Youtube video playback
Google Talk (as I read before because of the no camera issue)
Touch screen sensitivity is hit or miss, mainly with app icons and menu buttons (except for with the keyboard, that works beautifully)
Email would not sync (wifi working fine)
Every once in awhile the launcher crashes
Flash Video Play back
No Sound
I cannot get USB mass storage to work with my computer, but i may just be doing something wrong.
Otherwise this rom is beautiful, smooth and i am excited to see it evolve!
Thanks again to those that donate their time to do all of this work!
Last edited:
Flashed this, because I couldn't resist. I am using Trebuchet as the launcher, but it's not rotating. It pushed fine, and I can pick either com.android.launcher or com.cyanogenmod.trebuchet, and neither allows rotation. Did I miss something?
Otherwise, looks totally friggin sweet.
Otherwise, looks totally friggin sweet.
In com.cyanogenmod.trebuchet launcher hit the app drawer and in the upper right hand corner hit the settings button, it will be three squares. Go to general and check the auto rotate box. That's it
I had this same issue and just shut it down and reflashed both .zips with a full wipe, worked fine after that.
In com.cyanogenmod.trebuchet launcher hit the app drawer and in the upper right hand corner hit the settings button, it will be three squares. Go to general and check the auto rotate box. That's it
Oh, durr. That little 3 dot thing INSIDE the app drawer needs an explanation. that's my defense, anyway...lol
Well If you choose com.trebuchet launcher instead of the com.cyanogenmod.trebuchet launcher it gives a link to the market as apposed to the settings. I am not sure which launcher is better to use overall.
I will give that a shot. Does leave me with one question. What is safe to wipe from twrp? Any cache resets between zip installs or anything?
well there's definitely something wrong with the cpu scaling when the wifi is on. when it's off, the cpu is totally normal. when it's on however, it's almost always at 1.008 ghz so those who pointed this out were right. was it not like this on cm7? i didn't ever look at the cpu
Yeah i did a full wipe and cache between each install, not sure if it was needed but it seemed to work fine then
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
