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

Search This thread

qkster

Retired Recognized Developer
Apr 5, 2011
3,276
4,422
USA
Last edited:
Changed heap size to 128, runs really nicely. Looks like wifi doesn't go to sleep on any policy, using juice defender again for now. Panoramic photos are very low resolution. Still great to have and can always go back to CM7 while this ROM fleshes out.

Also noticed that the screen selection nose is very quiet.

Sent from my SGH-I997 using xda premium
 
  • Like
Reactions: FlyingIsFun1217

Ryanscool

Senior Member
Aug 30, 2011
1,151
194
Denver
I feel posting this here will have more benifit then anywhere else. Anyway, tv out (not hdmi) doesnt work, BUT since i did a log of what happened, maybe someone will be able to figure it out (link removed) It says d/tv out or something, and it says void? I think. Its towards the end.
 
Last edited:
Take care when posting these kinds of logs; I can see one of your email accounts in plain text as well as the last 2 songs you were listening to. That was in 3 minutes of browsing. Thankfully the little I can read is tame information.

Sent from my Transformer Prime TF201 using XDA Premium HD app
 
Last edited:

Ryanscool

Senior Member
Aug 30, 2011
1,151
194
Denver
Take care when posting these kinds of logs; I can see one of your email accounts in plain text as well as the last 2 songs you were listening to. That was in 3 minutes of browsing. Thankfully the little I can read is tame information.

Sent from my Transformer Prime TF201 using XDA Premium HD app

Lol thanke bro. Took it down, if anyone wants to see pm me. Or i may post it with that edited out. And lol i didnt do anything people could get (unless what u said) but ill promote my music lol.
 

popi09

Senior Member
Sep 17, 2011
151
11
Well gonna give this ROM a shot and hopefully I don't brick my infuse lol. If I dont ill report back after flashing. Wish me luck!

Sent from my SAMSUNG-SGH-I997 using XDA
 

jananan

Senior Member
Sep 10, 2011
193
53
At my job I am constantly running back and forth between my office and the warehouse. It is nice not having to check my screen every time I sit down to see if I missed a call or text. Plus I hate lockscreens. BTW you can set BLN to blink as long as you want after a missed event. And... actually increases my battery life by not having to fire up the screen as much.

i used to use this tiny app that repeats the message tone like every 1 or 2 or 5 minutes until you check it.

it also applies to missed calls and other notifications.

you can choose any tones you want, short and softer sounding ones that keep bugging you until you check the notification. you can also set it up to stop notifying you like after 30 minutes or so.

pretty useful if you ask me. better than BLN.
 

nolawhodat

Senior Member
May 13, 2011
74
5
Laplace, LA
i used to use this tiny app that repeats the message tone like every 1 or 2 or 5 minutes until you check it.

it also applies to missed calls and other notifications.

you can choose any tones you want, short and softer sounding ones that keep bugging you until you check the notification. you can also set it up to stop notifying you like after 30 minutes or so.

pretty useful if you ask me. better than BLN.

What app?

Sent from my SGH-I997 using xda premium
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
At my job I am constantly running back and forth between my office and the warehouse. It is nice not having to check my screen every time I sit down to see if I missed a call or text. Plus I hate lockscreens. BTW you can set BLN to blink as long as you want after a missed event. And... actually increases my battery life by not having to fire up the screen as much.

Dude you don't have to unlock your screen to see notifications.
 
  • Like
Reactions: Clark Joseph Kent

qkster

Retired Recognized Developer
Apr 5, 2011
3,276
4,422
USA
OK, Kids.

Let's see if we can move

NON DEVELOPMENTAL TALKs and TWEAKS

to this thread started by AxiomKid:


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

thanks.

For example: If you hacked into broadcom's chipset and fix the Bluetooth, post it here.
If you had no clue on how to flash this rom or had some other questions, go to Q/A.
If you had a tweak or some ways of this rom better, let talk in AxiomKids thread.

Let keep this thread for development.

Thanks.
 

tripartist1

Senior Member
Jan 15, 2012
124
18
Atlanta, GA
Just out of curiosity, does / has anyone had some time to flash zues build 6 (with / with out ics theme) and try to flash this rom from it... i need to know if im the only one having this issue here it would be greatly appreciated. TY :)

and 1 quik question. I dont have a modded 3e recovery, only cwm (pushed it).
is the blue recovery still cwm, or is it a modded stock ICS recovery, or what...
 

berryman13

Senior Member
Mar 30, 2011
1,988
1,239
San Francisco
Just out of curiosity, does / has anyone had some time to flash zues build 6 (with / with out ics theme) and try to flash this rom from it... i need to know if im the only one having this issue here it would be greatly appreciated. TY :)

and 1 quik question. I dont have a modded 3e recovery, only cwm (pushed it).
is the blue recovery still cwm, or is it a modded stock ICS recovery, or what...

it's still CWM
 
  • Like
Reactions: tripartist1

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.