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

Search This thread

alwayslookingforanswers

Senior Member
Dec 20, 2011
333
118
Houston Tx.
img15.imageshack.us
I would have to agree with you there. As stated in the op this is BETA and there is going to be problems. I understand if you are explaining what is happening with your device so the developer can see what is going on to improve it, but to just complain about something and then throw your phone down and YELL that I'm going back to my ex.. Then whatever keep it to yourself. Get on your hands and knees and beg her back. (Her being old rom) The developers work their A** off at this stuff to improve OUR devices and you want to piss them off? Give them a thanks and a smile for what they do. And move on if it isn't for you! :p
 

enochpc

Senior Member
Jan 23, 2012
159
76
Enoch
***** ***** whine whine about reboots without posting a last_kmsg

useless post...

Would gladly post last_kmsg if I had a clue how. Only trying to mention an issue that I hadn't seen mentioned, not intending to whom

Edit think I get the idea now will attempt to get log next time it happens.
 
Last edited:

jpcdeux

Senior Member
Mar 26, 2010
3,662
885
Laporte, IN
I like the useless post to call yours useless. Some people here just live to ***** cause nobody in real life cares what they say either.

Sent from my SAMSUNG-SGH-I997 using XDA
 

alwayslookingforanswers

Senior Member
Dec 20, 2011
333
118
Houston Tx.
img15.imageshack.us
And to add to it.... Entropy512 doesn't have to be doing this. I read in this thread somewhere that this isn't his main project and he is taking time from that to do us Infuse owners a favor. The developers have to take lots of time out of their lives to be doing this. Many of us Infuse owners have been waiting for someone with his knowledge to come and give us something like this for our devices. We are lucky to have him doing this for us and every time he does an update we should thank God that he is there and all the other developers also. So please don't piss him off where he says screw the Infuse and do it ourselves. Because most likely we would be left behind with all the other devices that have been forgotten about. So with that said THANKS A MILLION TIMES OVER AND OVER for this and future projects to come... :D
 

wayzata

Senior Member
Mar 21, 2012
107
23
If people keep *****ing without helping and Entropy leaves, there's going to be a witch hunt...

He's doing a better job than anyone else ever has for the Infuse, let him get to things when he can.
 
  • Like
Reactions: slipudatung
T

tmease1

Guest
With the purchase of a 2012 Kia Rio , I will need Bluetooth capabilities ... soo I'll be going back to GB .
Curse u cm9 and **** Bluetooth.

Sent from my SGH-I997 using XDA

Take the car back and keep cm9. Who would buy a kia anyway?:)

Sent from my MB865 using xda premium
 

ierdna

Member
Sep 21, 2010
32
1
No chance I'm taking it back. Its awesome as a first car. Better than ford anyway.

Anyhow, $10 to the person that gets Bluetooth working and STABLE, plus fix flaky wifi/tethering. Will need to test myself. Customer satisfaction first. pm me or reply to this post.

Sent from my SGH-I997 using XDA
 

alwayslookingforanswers

Senior Member
Dec 20, 2011
333
118
Houston Tx.
img15.imageshack.us
No chance I'm taking it back. Its awesome as a first car. Better than ford anyway.

Anyhow, $10 to the person that gets Bluetooth working and STABLE, plus fix flaky wifi/tethering. Will need to test myself. Customer satisfaction first. pm me or reply to this post.

Sent from my SGH-I997 using XDA

Ok your right about the Ford issue. Would never buy on myself ever. I am for Chevy all the way. And you know what sorry for that to each their own. Glad your getting yourself a new ride. Anyhow enough BS>>> going to get into trouble for all this useless chit chat...:)
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
If people keep *****ing without helping and Entropy leaves, there's going to be a witch hunt...

He's doing a better job than anyone else ever has for the Infuse, let him get to things when he can.

I wouldn't say that... LinuxBozo >>>>> me. gtg also did a lot of great groundwork.

I just happen to be the only one insane enough to keep screwing with this device.

I have some possible lines on improvements for wifi, but they're going to take some time. (yet again - pershoot to the rescue, he's reworking the wifi drivers on Tab 10.1 and I'll try those if they prove stable on the Tab.) - I'm not going to mess with them on Infuse until they prove stable on the Tab. These drivers seem to have a bad habit of taking what are minor annoyances on other devices and becoming evil on Infuse.
 

elliot.newnham

Senior Member
Mar 21, 2011
693
309
Atlanta
Hey Entropy anycard over in the infuse general forums just released AOKP and he managed to get 100mhz working somehow.

Maybe shoot him a PM and see if he has any input if you'd like. I'm sure he'd be happy to help

Again thanks and your latest build is awesome.



Sent from my SGH-I997 using xda premium
 

Attachments

  • uploadfromtaptalk1336355586054.jpg
    uploadfromtaptalk1336355586054.jpg
    53.4 KB · Views: 422

jblparisi

Senior Member
Jun 12, 2007
572
508

Attachments

  • screen_20120506_2252.jpg
    screen_20120506_2252.jpg
    32.5 KB · Views: 356
Last edited:

Boxerboy213

Member
Sep 14, 2010
37
1
Los Angeles
Vibration??

Anyone else having problems with Vibration Notifications?? :(
Whenever I put my phone to vibrate, it doesn't vibrate at all. Any way to fix..?? :confused:
 

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.