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

Search This thread

tripartist1

Senior Member
Jan 15, 2012
124
18
Atlanta, GA
I did that. That's why
I
freaking
said
any
damn
setting.
You should learn to read before you reply.

well if you want to get all ****ty then maybe you should read the OP before posting supposed "bugs" it clearly states:

"Known issues:

Settings->Advanced will FC until I port over the relevant parts of the GalaxyS settings app from the GalaxySII
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."
can you read that...?
im trying to help a fellow forum member, im sorry if you dont think to reflash a rom when your having issues. thats what the normal person would do, just to make sure it was a clean flash... i have no issues with the player.
 
  • Like
Reactions: Clark Joseph Kent

NunHugger

Inactive Recognized Developer
Dec 18, 2009
3,842
8,914
Des Moines, IA
someone-on-the-internet-is-wrong2.jpg
 

zelendel

Senior Member
Aug 11, 2008
23,360
20,609
OnePlus 6T
OnePlus 9
Ok I am only gonna say this once. This is not baseball so there is no 3 strikes. One warning only.


The rudness ends NOW from everyone. Follow the rules. And that means Searching, Reading and then repeat till you understand what you are doing. If you cant say something nice then dont post. This site is for learning and that is what everyone is here to do. Remember when you didnt know a damn thing?


I hope I made myself crystal clear
.
 

deathblade

Senior Member
Dec 19, 2011
1,552
406
Nexus 7 (2013)
OnePlus One
I thought it unlikely that you(or anyone for that matter) would have gone through those different threads/posts in the exact order that I typed them(or pasted them) - my mistake.

However, I've NEVER had issues with that process... and I of all people had a TON of issues with Zeus until I went through that method. That's not to say Entropy has the same issues with his ROMs as Zeus does, but regardless... if you were to have a ROM issue due to a bad flash(unbeknownst to us or not), then those steps would fix it. ;)

Not to add fuel to the fire but I have seen instructions, maybe not exact but just about else where, can't remember which thread its in just rememeber this guy was having problems and he was trying to get the cleanest flash possible, maybe in one of the Zeus threads a while back, any way my point is that yes you may have just typed them up right then but that does not by any means mean that they are not out there already, and there is no need to get defensive over it, instead just make a tut/guide somewhere to help others find the answer quicker, keep in mind this is a forum for people to learn and "show off" what they know

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

jgruberman

Senior Member
Dec 6, 2011
423
79
Dallas
Really genious??? What issues would those be?

I already said that it was issues due to bad flashes in that same post you quoted. That's not me talking bad about your ROM, just about the actual flashes that I had with it lol

---------- Post added at 02:11 PM ---------- Previous post was at 02:08 PM ----------

Not to add fuel to the fire but I have seen instructions, maybe not exact but just about else where, can't remember which thread its in just rememeber this guy was having problems and he was trying to get the cleanest flash possible, maybe in one of the Zeus threads a while back, any way my point is that yes you may have just typed them up right then but that does not by any means mean that they are not out there already, and there is no need to get defensive over it, instead just make a tut/guide somewhere to help others find the answer quicker, keep in mind this is a forum for people to learn and "show off" what they know

Sent from my SGH-I997 using xda premium

I agree completely. I'm not hiding that I had bad flashes when trying to install Zeus.. but that was due to my own faults and I've never said otherwise. Everyone is seeming to think that my comment above is me being negative about Zeus - it's not.. Zeus is great. And my attempts to make a tut/guide is actually what started this whole debacle. I copied and pasted different pieces from different peoples guides, that when I followed these particular steps, it ended up finally getting a clean install for me(due to my own lack of knowledge).

Not sure where the defensiveness is coming in, I have no problems with this ROM, Zeus, or any of the others I've installed since then.
 

tamelion1117

Senior Member
Oct 14, 2011
857
593
Nampa, ID
Someone may have already asked this. I didn't read every post in this thread, so if someone has please, accept my apologies.

Now, to get to the question.. What are the chances that we'll see a version of this Rom with working bluetooth? Working better than it does with CM7. :D
 
Last edited:

jananan

Senior Member
Sep 10, 2011
193
53
Considering its a recognized issue, I wouldn't post anymore about what aspects of the LED does and doesn't work.... we got it - LED is flaky in all aspects... different app won't change that fact

Sent from my SGH-I997 using XDA

i know there is an issue with lighting up the LED under CM9. the app was only a suggestion to JeremyE77's post.
 

threi_

Senior Member
Dec 18, 2011
487
198
Alliston
grats on the front page mention. Defenitely deserved, considering the work that was put in for this tragically forgotten phone.

Samsung really could use a kick in the rear, GS3 be damned.
 

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.