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

Search This thread
J

jscott30

Guest
This is a full of bug rom. Went back to jt's build2. Force close.... freeze....yup I went back to stock and also his karnel. His kernel is the reason to try his firmwire but disappointed.

Someone didn't follow the installation instructions properly. When almost no other users are encountering the problems you describe, the problem is YOU, not the firmware.

Exactly. The majority of things that weren't working when this ICS kernel became available for the Infuse, have been fixed by Entropy. I've run this for a couple of weeks now, checking out each new release, and haven't seen any of these problems. I've been impressed with how stable this is so early on, and am glad that we have a dev on xda working so hard to get it working even better.

Anytime a rom isn't running well, it's always a good idea to go back and clean up old user data and cache before trying again to get a clean install. Better yet, clean it up before the first flash, and things will work right the first time.
 
Last edited:

Axiomkid

Senior Member
Jan 6, 2009
875
308
Exactly. The majority of things that weren't working when this ICS kernel became available for the Infuse, have been fixed by Entropy. I've run this for a couple of weeks now, checking out each new release, and haven't seen any of these problems. I've been impressed with how stable this is so early on, and am glad that we have a dev on xda working so hard to get it working even better.

Anytime a rom isn't running well, it's always a good idea to go back and clean up old user data and cache before trying again to get a clean install. Better yet, clean it up before the first flash, and things will work right the first time.

Agreed not seeing any of these issues at all as I said before, if you are UV you may be causing the phone to reboot and lose function. Overheating issues I hear, nope none of those either. I will never go back to GB again. The touch screen and scrolling is F'n ridiculous and I love it.

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

ierdna

Member
Sep 21, 2010
32
1
Wow, no issues off the bat. Let me know if I can help with any testing .
All seems to be functioning

Sent from my SGH-I997 using XDA
 

PVD04

Member
Jan 5, 2010
42
13
Madison, WI
I've had several of the issues reported regarding the Menu/Home keys not working and wifi bugging out that have been reported. I can do a completely clean install, not set anything up (accounts, apps, etc) and still have the problems show up. They seem to be related to the new wifi drivers in the 4/22 and 4/23 build. When my Menu/Home etc keys stop working, they start working as soon as wifi finishes crashing. After it finishes I am unable to turn wifi on without rebooting but everything else seems to work. Flashing back to the 4/19 build gets rid of all the issues. If I have some time today I'll try to get back on 4/23 and post a logcat.
 

PVD04

Member
Jan 5, 2010
42
13
Madison, WI
Here is a logcat from my wifi resetting. During the time it was resetting the touch screen was working, but the Menu, Home, Back, and Search buttons were all unresponsive. As soon as wifi shut off completely the buttons started working again. This happened within an hour of flashing the 4/23 build over 4/19. The same happens if I do a clean install of 4/23.
 

nghia3d

Senior Member
Feb 12, 2012
232
23
I have an issue with wifi.Sometimes!When i open wifi it not responding so long.Wifi display content is finding wifi,at this time I can not touch wifi icon to turn off or doing anything with wifi.I must be reboot my phone then wifi is good.:confused:
 

Ljdd

Senior Member
Jan 23, 2011
239
40
31
Huntsville
Well I flashed when I was riding with my dad in a car with no computer and my touch buttons haven't went crazy yet, and this my third time going back to CM9

Sent from my SGH-I997 using XDA
 

ierdna

Member
Sep 21, 2010
32
1
... ,at this time I can not touch wifi icon to turn off or doing anything with wifi.I must be reboot my phone then wifi is good.:confused:

This occurs to me too. Tethering also. With reboot wifi ends up being on and working. I turn wifi off then on, and wifi off/on becomes grayed out. No wifi result returned
I will look into providing some logs, but I have yet to learn to do it right on android...


Sent from my SGH-I997 using XDA
 

fleadog99

Senior Member
Jun 10, 2007
385
94
Google Pixel 6 Pro
On the wi-fi issue. If you have the issue of it greying out after it is turned off manually, I found that if you let it sit for a while (2-3 minutes) then go into settings and select wi-fi (not the on switch), then select the on switch inside this panel, it turns on. It is probably a MAC address issue I am guessing though.
 
  • Like
Reactions: nghia3d

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
On the wi-fi issue. If you have the issue of it greying out after it is turned off manually, I found that if you let it sit for a while (2-3 minutes) then go into settings and select wi-fi (not the on switch), then select the on switch inside this panel, it turns on. It is probably a MAC address issue I am guessing though.
Not a MAC problem, as 4/23 fixed that.

A few people occasionally had similar problems in the I9100 kernel sources. I need to bring in some patches from gokhanmoral's tree.
 

theROMinator

Senior Member
Nov 23, 2010
1,134
296
Entropy, I've attempted to catch the "sod" and "unresponsive cap keys" issue with a logcat but nothing relevant shows up. It only use to happen every so often but it happens nearly every hour now. I believe it's related to wifi service, but I can't be too sure. The next time it happens when I'm @ my computer I'll logcat it during its course.

Sent from my SGH-I997 using Tapatalk 2 Beta-5
 

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.