[Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012)

Search This thread

Axiomkid

Senior Member
Jan 6, 2009
875
308
I wouldn't be surprised. There are a few wifi fixes I need to patch in (maybe this weekend), but one of the suspected causes of issues was memory allocation - supercharger v6, of course, dicks around with memory allocations.

I'm going to say it now: If you flashed ANY mods or installed any scripts after flashing CM9 + gapps, do NOT post bug reports here. I will not accept bug reports from people running scripts like that. I've seen it cause too many problems with too many devices.

I will let everyone know this in my ICS Mod Thread. Thanks!
 

araemo

Senior Member
Jun 23, 2011
515
620
I think I have found a bug in the 4/23/2012 rom..

Logcats are attached.

Problem: Wifi won't turn on sometimes.. reproduce steps:
Turn off wifi.
Turn on airplane mode.
Wait a bit
turn off airplane mode.
wait a bit
turn on airplane mode.
turn off airplane mode.
turn on wifi.
Wifi never finishes turning on, I need to reboot the phone.

The error I spotted in logcat:
Code:
E/WifiStateMachine(  217): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}

Problem with those repro steps: they didn't work for me just now. This has happened 2 days in a row(at least):
Leave for work, turn off wifi
Get to work, turn on airplane mode (due to no signal)
Go to lunch, turn off airplane mode..

go back to work, turn on airplane mode..
Leave work eventually, turn off airplane mode..

get home, turn on wifi, and wifi fails to turn on. So, there may be a 'trigger' in there I'm missing.. I grabbed the logcat attached within about 3 minutes of it failing to turn on wifi today.

Ah here we go.. kernel panic from dmesg:
Code:
<4>[ 3462.966849] ---- mook table_num[70]
<4>[ 3463.101696]
<4>[ 3463.101702] Dongle Host Driver, version 1.6.1
<4>[ 3463.101707] Compiled in drivers/net/wireless/bcmdhd/src on Apr 23 2012 at 19:32:00
<4>[ 3463.101830] ## wifi_probe
<4>[ 3463.101840] wifi_set_power = 1
<4>[ 3463.452885] wifi_set_carddetect = 1
<7>[ 3463.452914] sdhci_s3c_force_presence_change : Enter
<7>[ 3463.654938] *** DEBUG : start mmc_rescan (mmc2)***
<7>[ 3463.691475] sdhci_cmd_irq(1525) intmask = 0x10001.
<7>[ 3463.696989] sdhci_cmd_irq(1525) intmask = 0x10001.
<7>[ 3463.702103] sdhci_cmd_irq(1525) intmask = 0x10001.
<7>[ 3463.702595] *** DEBUG : First we search for SDIO...(2)***
<4>[ 3463.718899] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
<4>[ 3463.775546] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
<6>[ 3463.783331] mmc2: new high speed SDIO card at address 0001
<4>[ 3463.808576] alloc static buf at c4e00000!
<4>[ 3463.812337] F1 signature read @0x18000000=0x16834330
<4>[ 3463.827128] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 3463.924729] kmmcd: page allocation failure. order:5, mode:0xc0d0
<4>[ 3463.924782] Backtrace:
<4>[ 3463.924888] [<c0132fe4>] (dump_backtrace+0x0/0x110) from [<c054db18>] (dump_stack+0x18/0x1c)
<4>[ 3463.924947]  r7:c09f7058 r6:00000001 r5:00000005 r4:0000c0d0
<4>[ 3463.925166] [<c054db00>] (dump_stack+0x0/0x1c) from [<c019ac98>] (__alloc_pages_nodemask+0x534/0x580)
<4>[ 3463.925254] [<c019a764>] (__alloc_pages_nodemask+0x0/0x580) from [<c019acfc>] (__get_free_pages+0x18/0x58)
<4>[ 3463.925353] [<c019ace4>] (__get_free_pages+0x0/0x58) from [<c01b88f8>] (__kmalloc+0x40/0x110)
<4>[ 3463.925446] [<c01b88b8>] (__kmalloc+0x0/0x110) from [<c052a938>] (wiphy_new+0x168/0x36c)
<4>[ 3463.925501]  r8:bf200908 r7:e168e400 r6:bf201880 r5:dca53000 r4:00010f48
<4>[ 3463.925801] [<c052a7d0>] (wiphy_new+0x0/0x36c) from [<bf1ea60c>] (wl_cfg80211_attach+0xe8/0xb70 [dhd])
<4>[ 3463.925862]  r6:e6f51000 r5:dca53000 r4:e9bfbc08
<4>[ 3463.926189] [<bf1ea524>] (wl_cfg80211_attach+0x0/0xb70 [dhd]) from [<bf1c6d48>] (dhd_attach+0x35c/0x864 [dhd])
<4>[ 3463.926498] [<bf1c69ec>] (dhd_attach+0x0/0x864 [dhd]) from [<bf1ccae4>] (dhdsdio_probe+0x36c/0xe84 [dhd])
<4>[ 3463.926784] [<bf1cc778>] (dhdsdio_probe+0x0/0xe84 [dhd]) from [<bf1bae94>] (bcmsdh_probe+0x100/0x158 [dhd])
<4>[ 3463.926844]  r8:e3263400 r7:ee729e80 r6:bf202144 r5:00000000 r4:e3263700
<4>[ 3463.927212] [<bf1bad94>] (bcmsdh_probe+0x0/0x158 [dhd]) from [<bf1bc6b0>] (bcmsdh_sdmmc_probe+0x98/0xa0 [dhd])
<4>[ 3463.927306]  r8:00000000 r7:00000000 r6:bf2005ac r5:e9bfbc00 r4:e9bfbc08
<4>[ 3463.927556] [<bf1bc618>] (bcmsdh_sdmmc_probe+0x0/0xa0 [dhd]) from [<c03d7bd0>] (sdio_bus_probe+0xdc/0xf0)
<4>[ 3463.927616]  r5:e9bfbc00 r4:bf1f3734
<4>[ 3463.927724] [<c03d7af4>] (sdio_bus_probe+0x0/0xf0) from [<c02f7c84>] (driver_probe_device+0xb0/0x160)
<4>[ 3463.927782]  r7:bf2005ac r6:c02f7dc0 r5:e9bfbc08 r4:bf2005ac
<4>[ 3463.927911] [<c02f7bd4>] (driver_probe_device+0x0/0x160) from [<c02f7e04>] (__device_attach+0x44/0x48)
<4>[ 3463.927968]  r7:00000000 r6:c02f7dc0 r5:e9bfbc08 r4:bf2005ac
<4>[ 3463.928095] [<c02f7dc0>] (__device_attach+0x0/0x48) from [<c02f7174>] (bus_for_each_drv+0x54/0x94)
<4>[ 3463.928171]  r5:c4e5de48 r4:e9bfbc08
<4>[ 3463.928349] [<c02f7120>] (bus_for_each_drv+0x0/0x94) from [<c02f7e8c>] (device_attach+0x58/0x70)
<4>[ 3463.928408]  r7:e9bfba00 r6:00000000 r5:e9bfbc08 r4:e9bfbc3c
<4>[ 3463.928535] [<c02f7e34>] (device_attach+0x0/0x70) from [<c02f6fa4>] (bus_probe_device+0x2c/0x48)
<4>[ 3463.928591]  r5:e9bfbc10 r4:e9bfbc08
<4>[ 3463.928685] [<c02f6f78>] (bus_probe_device+0x0/0x48) from [<c02f596c>] (device_add+0x350/0x4c8)
<4>[ 3463.928776] [<c02f561c>] (device_add+0x0/0x4c8) from [<c03d79c4>] (sdio_add_func+0x3c/0x54)
<4>[ 3463.928869] [<c03d7988>] (sdio_add_func+0x0/0x54) from [<c03d7348>] (mmc_attach_sdio+0x4b4/0x560)
<4>[ 3463.928924]  r5:00000000 r4:c48c8000
<4>[ 3463.929015] [<c03d6e94>] (mmc_attach_sdio+0x0/0x560) from [<c03d3534>] (mmc_rescan+0x30c/0x444)
<4>[ 3463.929108] [<c03d3228>] (mmc_rescan+0x0/0x444) from [<c016910c>] (worker_thread+0x17c/0x208)
<4>[ 3463.929164]  r6:c03d3228 r5:c4e5c000 r4:c4e58980
<4>[ 3463.929274] [<c0168f90>] (worker_thread+0x0/0x208) from [<c016cc50>] (kthread+0x84/0x8c)
<4>[ 3463.929361] [<c016cbcc>] (kthread+0x0/0x8c) from [<c0159d78>] (do_exit+0x0/0x5f4)
<4>[ 3463.929411]  r7:00000013 r6:c0159d78 r5:c016cbcc r4:c4c21ed8

Doh, didn't see that others reported it.. well, here's good debugging info. :p
 

Attachments

  • logcat1.zip
    70.9 KB · Views: 2

Axiomkid

Senior Member
Jan 6, 2009
875
308
I think I have found a bug in the 4/23/2012 rom..

Logcats are attached.

Problem: Wifi won't turn on sometimes.. reproduce steps:
Turn off wifi.
Turn on airplane mode.
Wait a bit
turn off airplane mode.
wait a bit
turn on airplane mode.
turn off airplane mode.
turn on wifi.
Wifi never finishes turning on, I need to reboot the phone.

The error I spotted in logcat:
Code:
E/WifiStateMachine(  217): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}

Problem with those repro steps: they didn't work for me just now. This has happened 2 days in a row(at least):
Leave for work, turn off wifi
Get to work, turn on airplane mode (due to no signal)
Go to lunch, turn off airplane mode..

go back to work, turn on airplane mode..
Leave work eventually, turn off airplane mode..

get home, turn on wifi, and wifi fails to turn on. So, there may be a 'trigger' in there I'm missing.. I grabbed the logcat attached within about 3 minutes of it failing to turn on wifi today.

Ah here we go.. kernel panic from dmesg:
Code:
<4>[ 3462.966849] ---- mook table_num[70]
<4>[ 3463.101696]
<4>[ 3463.101702] Dongle Host Driver, version 1.6.1
<4>[ 3463.101707] Compiled in drivers/net/wireless/bcmdhd/src on Apr 23 2012 at 19:32:00
<4>[ 3463.101830] ## wifi_probe
<4>[ 3463.101840] wifi_set_power = 1
<4>[ 3463.452885] wifi_set_carddetect = 1
<7>[ 3463.452914] sdhci_s3c_force_presence_change : Enter
<7>[ 3463.654938] *** DEBUG : start mmc_rescan (mmc2)***
<7>[ 3463.691475] sdhci_cmd_irq(1525) intmask = 0x10001.
<7>[ 3463.696989] sdhci_cmd_irq(1525) intmask = 0x10001.
<7>[ 3463.702103] sdhci_cmd_irq(1525) intmask = 0x10001.
<7>[ 3463.702595] *** DEBUG : First we search for SDIO...(2)***
<4>[ 3463.718899] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
<4>[ 3463.775546] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
<6>[ 3463.783331] mmc2: new high speed SDIO card at address 0001
<4>[ 3463.808576] alloc static buf at c4e00000!
<4>[ 3463.812337] F1 signature read @0x18000000=0x16834330
<4>[ 3463.827128] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 3463.924729] kmmcd: page allocation failure. order:5, mode:0xc0d0
<4>[ 3463.924782] Backtrace:
<4>[ 3463.924888] [<c0132fe4>] (dump_backtrace+0x0/0x110) from [<c054db18>] (dump_stack+0x18/0x1c)
<4>[ 3463.924947]  r7:c09f7058 r6:00000001 r5:00000005 r4:0000c0d0
<4>[ 3463.925166] [<c054db00>] (dump_stack+0x0/0x1c) from [<c019ac98>] (__alloc_pages_nodemask+0x534/0x580)
<4>[ 3463.925254] [<c019a764>] (__alloc_pages_nodemask+0x0/0x580) from [<c019acfc>] (__get_free_pages+0x18/0x58)
<4>[ 3463.925353] [<c019ace4>] (__get_free_pages+0x0/0x58) from [<c01b88f8>] (__kmalloc+0x40/0x110)
<4>[ 3463.925446] [<c01b88b8>] (__kmalloc+0x0/0x110) from [<c052a938>] (wiphy_new+0x168/0x36c)
<4>[ 3463.925501]  r8:bf200908 r7:e168e400 r6:bf201880 r5:dca53000 r4:00010f48
<4>[ 3463.925801] [<c052a7d0>] (wiphy_new+0x0/0x36c) from [<bf1ea60c>] (wl_cfg80211_attach+0xe8/0xb70 [dhd])
<4>[ 3463.925862]  r6:e6f51000 r5:dca53000 r4:e9bfbc08
<4>[ 3463.926189] [<bf1ea524>] (wl_cfg80211_attach+0x0/0xb70 [dhd]) from [<bf1c6d48>] (dhd_attach+0x35c/0x864 [dhd])
<4>[ 3463.926498] [<bf1c69ec>] (dhd_attach+0x0/0x864 [dhd]) from [<bf1ccae4>] (dhdsdio_probe+0x36c/0xe84 [dhd])
<4>[ 3463.926784] [<bf1cc778>] (dhdsdio_probe+0x0/0xe84 [dhd]) from [<bf1bae94>] (bcmsdh_probe+0x100/0x158 [dhd])
<4>[ 3463.926844]  r8:e3263400 r7:ee729e80 r6:bf202144 r5:00000000 r4:e3263700
<4>[ 3463.927212] [<bf1bad94>] (bcmsdh_probe+0x0/0x158 [dhd]) from [<bf1bc6b0>] (bcmsdh_sdmmc_probe+0x98/0xa0 [dhd])
<4>[ 3463.927306]  r8:00000000 r7:00000000 r6:bf2005ac r5:e9bfbc00 r4:e9bfbc08
<4>[ 3463.927556] [<bf1bc618>] (bcmsdh_sdmmc_probe+0x0/0xa0 [dhd]) from [<c03d7bd0>] (sdio_bus_probe+0xdc/0xf0)
<4>[ 3463.927616]  r5:e9bfbc00 r4:bf1f3734
<4>[ 3463.927724] [<c03d7af4>] (sdio_bus_probe+0x0/0xf0) from [<c02f7c84>] (driver_probe_device+0xb0/0x160)
<4>[ 3463.927782]  r7:bf2005ac r6:c02f7dc0 r5:e9bfbc08 r4:bf2005ac
<4>[ 3463.927911] [<c02f7bd4>] (driver_probe_device+0x0/0x160) from [<c02f7e04>] (__device_attach+0x44/0x48)
<4>[ 3463.927968]  r7:00000000 r6:c02f7dc0 r5:e9bfbc08 r4:bf2005ac
<4>[ 3463.928095] [<c02f7dc0>] (__device_attach+0x0/0x48) from [<c02f7174>] (bus_for_each_drv+0x54/0x94)
<4>[ 3463.928171]  r5:c4e5de48 r4:e9bfbc08
<4>[ 3463.928349] [<c02f7120>] (bus_for_each_drv+0x0/0x94) from [<c02f7e8c>] (device_attach+0x58/0x70)
<4>[ 3463.928408]  r7:e9bfba00 r6:00000000 r5:e9bfbc08 r4:e9bfbc3c
<4>[ 3463.928535] [<c02f7e34>] (device_attach+0x0/0x70) from [<c02f6fa4>] (bus_probe_device+0x2c/0x48)
<4>[ 3463.928591]  r5:e9bfbc10 r4:e9bfbc08
<4>[ 3463.928685] [<c02f6f78>] (bus_probe_device+0x0/0x48) from [<c02f596c>] (device_add+0x350/0x4c8)
<4>[ 3463.928776] [<c02f561c>] (device_add+0x0/0x4c8) from [<c03d79c4>] (sdio_add_func+0x3c/0x54)
<4>[ 3463.928869] [<c03d7988>] (sdio_add_func+0x0/0x54) from [<c03d7348>] (mmc_attach_sdio+0x4b4/0x560)
<4>[ 3463.928924]  r5:00000000 r4:c48c8000
<4>[ 3463.929015] [<c03d6e94>] (mmc_attach_sdio+0x0/0x560) from [<c03d3534>] (mmc_rescan+0x30c/0x444)
<4>[ 3463.929108] [<c03d3228>] (mmc_rescan+0x0/0x444) from [<c016910c>] (worker_thread+0x17c/0x208)
<4>[ 3463.929164]  r6:c03d3228 r5:c4e5c000 r4:c4e58980
<4>[ 3463.929274] [<c0168f90>] (worker_thread+0x0/0x208) from [<c016cc50>] (kthread+0x84/0x8c)
<4>[ 3463.929361] [<c016cbcc>] (kthread+0x0/0x8c) from [<c0159d78>] (do_exit+0x0/0x5f4)
<4>[ 3463.929411]  r7:00000013 r6:c0159d78 r5:c016cbcc r4:c4c21ed8

Doh, didn't see that others reported it.. well, here's good debugging info. :p

Everyone is having this issue, Thanks for the logcat bro, helps Entropy a lot compared to just whining about it.
 

jgruberman

Senior Member
Dec 6, 2011
423
79
Dallas
I am on Heimdall and i don't really use it cuz iv never gotten it to work before... what do i do to flash bootloaders_UCKJ2.7z? What do i do? srry ima noobie on Heimdall stuff. Heimdall Suite 1.3.2 wut im using.
And my phone wont boot, it goes to recovery every time.

Follow the third link in my sig.

---------- Post added at 11:24 PM ---------- Previous post was at 11:22 PM ----------

yes, thats what i meant, just didnt know exactly what you called it

Thanks to you, I think that's what I WILL call it ;) At least until someone finds fault in it lol
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY

AJerman

Inactive Recognized Developer
Jul 18, 2007
933
123
Colorado
Damn, we get ICS and I break my phone. SGS3 needs to hurry!

Good post with the logcat btw. It did it to me again this morning, but I needed wifi at the moment, so I just rebooted and didn't get a log again.
 

jblparisi

Senior Member
Jun 12, 2007
572
508
Was the last time you built before the new wifi driver?

Often when BoardConfig.mk changes, you need to clobber the whole output tree and rebuild from scratch - remove out/target/product/infuse4g/

Yes I believe that last time I compiled successfully was before the new wifi driver.

Thanks for the input, I will try that and report back.

Update: Yup, happy to report back that it worked. :)

I could not have done it without that tip, thanks again.


Sent from my SAMSUNG-SGH-I997 using XDA
 
Last edited:

brazcub

Senior Member
Oct 1, 2008
130
54
Winthrop, WA
My Infuse was delivered yesterday after being repaired by Samsung (I bricked it). It came back with stock 2.3.6 but the first thing I did was root it and install this ROM. Been using it for about 20 hours and I can say I love it. I haven't had any force closes, everything works great, wifi, both cameras, flash, etc. Battery life has been awesome!

Donation is on its way.

Thanks a lot!!!
 
Last edited:

tankmorph

Senior Member
Jun 28, 2007
853
343
St. Petersburg, FL
My Infuse was delivered yesterday after being repaired by Samsung (I bricked it). It came back with stock 2.3.6 but the first thing I did was root it and install this ROM. Been using it for about 20 hours and I can say I love it. I haven't had any force closes, everything works great, wifi, both cameras, flash, etc. Battery life has been awesome!

Donation is on its way.

Thanks a lot!!!

I concur. This ROM rocks. I have no clue why I wasting time with GB.

Sent from my Amazon Kindle Fire using Tapatalk 2
 

blackwrx02

Senior Member
May 3, 2006
276
39
I'm having a REALLY hard time with the battery on this ROM. I see everyone saying how good it is. I can normally make it all day on other ROMS (off charger at 7am, back on the charger at 11:30-ish). No out of the norm usage (and no phone calls during my work day), its just on my desk most of the day. With ICS i'm having to charge it when I get home around 5:00pm

I've changed the build.prop to reduce wifi scanning which has helped, but only a little.

Also getting quite a bit of heat sometimes off the phone, so something is running but I'm just not able to tell what it is...would appreciate some input on where to start looking.
 

ejness

Senior Member
Dec 1, 2011
88
30
Also getting quite a bit of heat sometimes off the phone, so something is running but I'm just not able to tell what it is...would appreciate some input on where to start looking.

Try OS Monitor. That will show you what processes are running and how much resources they're using.

Sent from my SAMSUNG-SGH-I997 using XDA
 

jgruberman

Senior Member
Dec 6, 2011
423
79
Dallas
If you want to know what percentage of the battery is being drained and how quickly, get My Battery Drain Analyzer

If you want to know what's running, get Better Battery Stats

The original posting with a lot of information about Better Battery Stats is HERE

Even further detailed information and about how to interpret the program is HERE

If you only use your WiFi or GPS at certain times throughout the day, then you may want an app that is good at setting profiles for your phone based on time. I wake up, go to work, come home and go to sleep at the same time every day... so this app is great for me - PhoneWeaver.
The above is a trial, if you like it, buy the full... it's VERY worth it.

DON'T kill apps with "Startup Manager" and "AutoKill" programs... they do more harm than good... HERE'S WHY. Use Better Battery Stats and review the Wakelocks and see what is running and not letting your phone chill(no pun intended). The Battery Drain Analyzer will tell you how much is being drained in percentage format... use this before and after every time you make changes that could affect the battery to see how much improvement or harm you've done.

I use all of the above, and recommend it all highly. Let me know if you have questions on how to use them. Also, if you don't use your GPS, leave it off - big battery hog. And remember... keep your brightness AS LOW AS YOU CAN COMFORTABLY HAVE IT!!! (Also a setting in PhoneWeaver) :D
 
Last edited:
  • Like
Reactions: seekyo and ejness

RoryB

Inactive Recognized Developer
Sep 4, 2008
2,921
766
Lexington
... DON'T kill apps with Task Managers... they do more harm than good...
Excuse my ignorance. Don't kill them? Just let them run in the background?

I have noticed some "kill" themselves after a period of time, but it seems not all the time or not all of them.

Do they eventually stop on their own?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 215
    DO NOT POST IN THIS THREAD UNTIL YOU HAVE COMPLETELY READ THIS POST AND THE FAQ.

    Since jt1134 is no longer supporting his CM9 releases here on XDA and asking people to go elsewhere for support, I have decided to start building CM9 for the Infuse.

    Much of the credit goes to him for doing the initial ICS bringup for Infuse, I'm working on fixing some of the things that are not yet working. Even more goes to LinuxBozo - without his CM7 work we would be nowhere.

    http://d-h.st/vN1 - 06/20/2012 build
    http://d-h.st/ahW - 06/27/2012 build
    http://d-h.st/Pfr - 07/28/2012 build

    Installation instructions-from a Gingerbread firmware with "red CWM":
    Place this release and an ICS gapps release on your SD card.
    Flash this ZIP in CWM
    Reboot - you will get stuck at the Samsung screen
    Reboot to recovery again using the three-finger salute - hold down VolUp+VolDn+Power until the device reboots, release Power after the reboot, continue holding VolUp+VolDn
    Go to Mounts and Storage and format: system, data, cache
    Flash this ZIP a second time, then flash gapps
    Reboot and enjoy

    Coming from any AOSP-based firmware with "blue CWM":
    Flash this, flash gapps, wipe. That should be all you need.

    What is working:
    Calls
    GPS
    Sound
    Video playback

    What is partially working:
    Camera (minor flakiness, but mostly working)
    Car dock audio (possibly desk dock too, untested) - Some issues with ringtone playback when docked - This is native dock audio, not using the Car Dock Redirector app workaround. Thanks go to StevenHarperUK of the GT-I9100 community for reworking CM9's dock audio code to permit this to work.
    Wifi - It frequently loses connection when the device is asleep. Most likely needs some SDHCI driver tweaks to match the N7000 wifi driver.
    Wifi Direct - A little glitchy but mostly working with I777/N7000. Won't talk to a P7510 (Tab 10.1) though.
    Bluetooth - A2DP (music) and SCO (call audio) now works. However BT power management (LPM) is currently disabled, so BT may eat your battery when on.

    Not working:
    TV Output - No one has gotten MHL fully working on any Samsung device yet to my knowledge. There's some promising results from the I9100 community but it's not there yet.

    Known issues:
    SetCPU seems to be unable to set the minimum frequency to 100 MHz. This is one of the main reasons for holding off on OC - even stock clock code isn't working quite right
    Facebook contact sync has been blocked by Google in ICS - this is universal to ICS on all devices I'm aware of. Facebook got what they deserved here.
    63
    Building - Use the Source, Luke

    Kernel source is at: https://github.com/teamhacksung/android_kernel_samsung_dempsey

    Device repo at: https://github.com/teamhacksung/android_device_samsung_infuse4g

    To build, first prep your system for a Cyanogenmod build by following the instructions at:
    http://wiki.cyanogenmod.com/wiki/Building_from_source

    Once you have done the first "repo sync", at the two following lines to .repo/local_manifest.xml
    Code:
      <project path="device/samsung/infuse4g" name="teamhacksung/android_device_samsung_infuse4g" remote="github"/>
      <project path="kernel/samsung/dempsey" name="teamhacksung/android_kernel_samsung_dempsey" remote="github" />

    Run "repo sync" again

    Sync https://github.com/TheMuppets/proprietary_vendor_samsung/ into vendor/samsung

    Drop the contents of the attached tarball into vendor/samsung

    (I really need to clean that process up...)

    Run:
    Code:
    . build/envsetup.sh && brunch infuse4g
    51
    FAQ

    Q: I get weird rainbows in recovery and when my device boots? What gives?
    A: This is what happens when a Gingerbread or ICS kernel is booted on a device with Froyo bootloaders. You will need to either live with the rainbows (recovery is at least partially usable with the rainbows now) or flash Gingerbread bootloaders. Stay tuned for more info on bootloader flashing.

    Unfortunately, the classic "rainbow fix" we used for Gingerbread is not compatible with how video acceleration is set up in ICS. The rainbowfix will just cause the device to crash immediately on boot. (I think this is why jt was not successful with LinuxBozo's CM7 source.)

    Q: I'm getting rainbows, how do I flash Gingerbread bootloaders?
    Flash the bootloaders from the file attached to this post using Heimdall as follows:
    Code:
    heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin

    DO NOT do this unless you are experiencing rainbows, and DO NOT do this until you have confirmed you can flash less dangerous stuff (like kernels) with Heimdall. If the flash fails you will hardbrick!

    Thanks to LinuxBozo for confirming, way back in the days of UCKJ2, that Heimdall can safely flash bootloaders from leaks. http://xdaforums.com/showthread.php?p=18539754#post18539754 - Be warned, once you do this step there is no going back. For whatever reason the Infuse won't flash dumped bootloaders, so there is no known way to return to Froyo and Rogers Gingerbread bootloaders.
    49
    Change Log

    7/28/2012:
    Removed 1000 MHz cpufreq step - the extra frequency step was causing all sorts of weird derpage.
    Fixed 1200 MHz step (it was using the wrong PLL settings)
    Moved to open source sensor HAL

    7/22/2012:
    Major improvements to camera flash functionality - torch is still broken but most other flash functions work
    EXIF info (including rotation) is now saved. However I had to disable JPEG thumbnail generation, which slows down viewing of images in gallery
    Structural changes to the repos to make things cleaner - Once two patches get merged by CM I plan on submitting Infuse for official nightlies
    CPU clock handling for GPU bus frequency was changed from a policy change (min freq bumped to 200 MHz in policy, which would cause some apps to "stick" the min at 200) to a DVFS lock. Min no longer bumps up to 200 - however any time the GPU is active it'll still lock to 200 MHz.

    6/27/2012:
    Discovered our device has a Broadcom BT chipset - the CG2900 is NOT used for Bluetooth. BT is now fully functional other than possible power management issues

    6/20/2012:
    Various upstream stuff
    Wifi Direct support added - partially glitchy (see OP)
    Bluetooth support brought up to CM7 levels (Audio stuff is still broken)

    5/27/2012:
    New wifi driver from GT-N7000 Update3 source drop: Hopefully will improve wifi for those with issues
    New LPM (charging while off) code from I9100
    All upstream changes since last build, including lockscreen weather

    5/19/2012:
    Lots of upstream CM9 changes, including theme engine and customizable lockscreen
    Settings->Advanced now works. mDNIE settings (tested) and HSPA+ control (untested)
    A small patch that might help wifi driver loading issues, but not guaranteed (gokhanmoral reverted it within a day in his case...)

    5/2/2012:
    Pulled in a few wifi fixes from gokhanmoral's I9100 SiyahKernel tree. May help those who are having wifi issues.

    4/23:
    Fixed wifi MAC address getting set randomly on every boot

    4/22:
    Misc stuff from CM9 upstream
    New wifi driver backported from the I9100 update4 sources and pershoot's Tab 10.1 kernel - Fixes wifi tethering!
    USB tethering removed until I can make the RNDIS driver play with the new net/wireless code - not even sure if it was working to begin with.

    4/19:
    No more banding in recovery (thank codeworkx for this one, exact same fix as for I9100)
    FFC is no longer cropped to one corner of the sensor. Full resolution support for FFC still not implemented
    Various upstream changes
    36
    I'm going to push out a build that hopefully fixes some of the wifi driver issues tonight, it pulls a few patches in from gokhanmoral's I9100 tree. (I9100 users have had occasional issues with wifi reliability too.)

    Since I can't reproduce the issues I don't know if it will help things or not.

    I do plan on staying with this wifi driver. The benefits of working tethering and (hopefully) eliminating the BT-AMP wakeup bug (as it did when backported to the Tab 10.1) outweight the small issues it has.

    Currently on my list, time permitting:
    Try to identify why the broadcast/ARP packet filters don't enable when the screen is off. This seems to be a common issue to all devices using the I9100 wifi drivers and CM9 - It can hurt battery life for those on "dirty" networks with lots of broadcast spam. It's not a problem for most developers as we run clean networks, which might explain the unusual discrepancies in battery life between the developers and some users.
    Attempt to see if there's a way to shoehorn the I9100 camera HAL onto the Infuse, which seems to use the exact same cameras. If possible it will provide a much more robust camera experience. If not - I've lost enough sleep to the damn camera HAL, I welcome someone else trying to fix it. I hate going from an open-source HAL to a blob - but the open source HAL isn't working too well.

    I'm probably not going to be doing too much over the next few days on any device, I'm generally exhausted.