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

Search This thread

TheKid2

Member
Dec 23, 2011
35
45
Shepherdsville
I believe this CPU wifi thing isn't kernel related. I flashed cm7 and used the kernel in the ics builds and the wifi modules and it didn't continuously flip flop between 300 to 1008 so it seems like it's something else doing it but it's software related so there's definitely a fix.. I just have to find it :)

Sent from my Galaxy Nexus using XDA App
Have you looked into the wlan calibration utility built into the driver. You can also customize the MAC Address.

Original source of info

http://www.omappedia.org/wiki/Porting_MCP_WLAN_to_Android#TxBiP_Calibration
http://processors.wiki.ti.com/index...ce_(CLI)_User's_Guide#Editing_the_MAC_Address


I have used the calibartion utility once and copied the nvs_map.bin to all four of my kindles, only changing the mac address.

Manufacturer indicates that customer(amazon) should run uitility on each device.
We can probably find the original file by restoring to factory. I have looked in the factory update files and could not locate it. Of course it would be a custom file to each device (mac address unique).

My four kindles connected to secure wireless do not appear to have any problem.
http://xdaforums.com/showthread.php?t=1406845

I have also used my nvs_map.bin while running your ics build to retain my mac address.

edit:

I have reports from other cm7 users that running the calibaration routine and using resulting nvs_map.bin file fixes cpu scaling issue for them also

edit:

Thanks for your continued effort on this great platform.
 
Last edited:

dragossh

Member
Dec 1, 2009
5
0
Didn't see this posted already, but when you disable notifications the bottom bar goes into a crash frenzy. As far as I recall, it's either a missing file or a missing string. Don't want to wipe all the data again so no logcat output.
 

enkode

Senior Member
Apr 22, 2010
119
20
Jersey
So, why am I getting keyboard feedback sounds and unlock sounds, and no sounds from notifications or media?

Sent from my PC36100 using xda premium
 

HeWhoWas

Senior Member
Oct 17, 2007
53
66
So, why am I getting keyboard feedback sounds and unlock sounds, and no sounds from notifications or media?

Sent from my PC36100 using xda premium

Read the OP. Sound is sketchy.

---------- Post added at 07:44 AM ---------- Previous post was at 06:56 AM ----------

Didn't see this posted already, but when you disable notifications the bottom bar goes into a crash frenzy. As far as I recall, it's either a missing file or a missing string. Don't want to wipe all the data again so no logcat output.

I read this, less than an hour later was playing around with the quick settings having just discovered them. Turned notifications off, and it died :-( Any way to re-enable them without wiping? I keep getting sent to the UMS app by default, and then UI crashes, so I can't go back :-(
 

dragossh

Member
Dec 1, 2009
5
0
I have no idea. The only way to get it to work was to wipe the data and set it up again.

Do we have any idea why sound doesn't work all the time? It seems to start working every time something crashes...
 

bl1nkk

Senior Member
Jun 16, 2010
176
390
Baunatal
mrks.me
Ok cool, thanks for the heads up. One question... What is the status of the hwcomposer bug, only its a bit difficult to look into logcats when they are full of android_wait_for_fb_sleep messages. I was hoping to look into a few of the smaller bugs, I'm no Dev but I know my way arround a logcat.

Try `adb lolcat | grep -v "android_wait_for_fb_sleep"`

It should do the trick until there's a new zip. :)

Sent from my Nexus S using Tapatalk
 
  • Like
Reactions: monho and icebuck

zone23

Senior Member
Feb 16, 2009
5,437
2,309
Hay guys whats up? Just wanted to stop by the house.

Made a version of this ROM its very similar to my Xoom ICS but uses this base. Its looking good but not ready to hit the streets just yet. Plus I haven't ask the OP so keep that quite.

Got all the same problems nothing new but I give OP the NICE JOB OP.

---------- Post added at 08:42 AM ---------- Previous post was at 08:36 AM ----------

Forgot couple things:

OP when flashed I didn't have root was wondering if you are just going to include it.

Also the ROM did not have /data/apps for user apps, plans to add that?

I have both working in the version of your ROM I did. If you want or would like I can give the script line I used. Actually here I'll just post it incase someone else wants it.

and this to updater script:

Code:
ui_print("Extracting user data....");
mount("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/userdata", "/data");
package_extract_dir("data", "/data");
set_perm_recursive(0, 0, 0755, 0644, "/data");

create /data/app inside ROM zip add your apps to app folder.

Superuser

Copy SU binary to /system/bin

and this to updater script:

Code:
symlink("/system/bin/su", "/system/xbin/su");

Actually I over right the one in xbin as well..
 
Last edited:

zone23

Senior Member
Feb 16, 2009
5,437
2,309
What do you mean it didn't have user data?

Sent from my Galaxy Nexus using XDA App

User data is sometimes included in the downloaded ROM. Its a folder that contains apps that get installed when you flash the ROM. Apps in /data/app can be uninstalled. So he can put say GMail.apk in there and then if someone didn't want it, it would be unistall it. Thats all.
 

JackpotClavin

Inactive Recognized Developer
Feb 27, 2011
1,024
3,814
New York
Oh I gotcha. I think there's a legal issue if CM were to include Google apps within the zip so we have to flash gapps separately

Sent from my Galaxy Nexus using XDA App
 

zone23

Senior Member
Feb 16, 2009
5,437
2,309
Got some pictures attached. I removed some off the GAPPS stuff and this seems pretty solid now.
 

Attachments

  • device-2011-12-28-095552.jpg
    device-2011-12-28-095552.jpg
    31.6 KB · Views: 324
  • device-2011-12-28-095603.jpg
    device-2011-12-28-095603.jpg
    21.6 KB · Views: 268
  • device-2011-12-28-095618.jpg
    device-2011-12-28-095618.jpg
    25 KB · Views: 274

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.

    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!
    36
    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).
    35
    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 :)
    31
    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!
    30
    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 :)

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