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

Search This thread
By:
Advanced…
A

Axiomkid

Senior Member
Jan 6, 2009
875
308
Made a new working ICS Battery Mod for Entropy's latest build 4/19/2012, This mod only works for Entropy's latest Build 4/19/2012, You flash this on a different build you will bootloop. 2 to pick from, Flash in CWM: Thanks Dman and mlkjuggalo

Different Color Dying Changing Battery Mod (Blue-Green-Yellow-Red)
https://hotfile.com/dl/153538977/4ee2524/ICS_Battery_Mod.zip.html

All ICS Blue Non Color Dying Changing Battery Mod (Always Blue Until it starts dying at 14% batt left then it turns red)
https://hotfile.com/dl/153543198/79c2e22/ICS_Battery_Mod_-_Always_Blue.zip.html
 
Last edited by a moderator:
  • Like
Reactions: garbagedump481, Zen Arcade, z3rowrk and 1 other person
F

FlyingIsFun1217

Senior Member
Oct 1, 2011
90
9
I've noticed in the new build that swiping along the notification bar on top of the screen can only dim the screen brightness, and not all the way down. But it definitely cannot bring it back up.

Seems more like a problem with CM9 than anything Entropy did, but nonetheless, is an issue for me.

Can anyone confirm?

FlyingIsFun1217
 
J

jz3

Senior Member
Jun 22, 2010
120
50
@Entropy, is there any possibility of BLN being implemented in your ICS kernel after the major bugs are squished? This is a must have for me and I'm stuck on froyo as a result until my contract is up.:(
 
E

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
jz3 said:
@Entropy, is there any possibility of BLN being implemented in your ICS kernel after the major bugs are squished? This is a must have for me and I'm stuck on froyo as a result until my contract is up.:(
Click to expand...
Click to collapse

No. BLN on Froyo was janky **** that never quite worked correctly, BLN on Gingerbread was a crashfest. If someone else implements a reliable working implementation I'll consider patching it in, but I won't spend time on this myself. BLN just isn't that beneficial especially considering that to date, any reliable implementations have required a wakelock to be held while the notification was active.

It's not that hard to click the screen on and off as a quick check.
 
  • Like
Reactions: papu4ara, Clark Joseph Kent and Yuma75
A

Axiomkid

Senior Member
Jan 6, 2009
875
308
Entropy512 said:
No. BLN on Froyo was janky **** that never quite worked correctly, BLN on Gingerbread was a crashfest. If someone else implements a reliable working implementation I'll consider patching it in, but I won't spend time on this myself. BLN just isn't that beneficial especially considering that to date, any reliable implementations have required a wakelock to be held while the notification was active.

It's not that hard to click the screen on and off as a quick check.
Click to expand...
Click to collapse

BLN is quite useless, unless your 1 of those ppl that stare at your phone constantly in pure silence. Either way don't you have to click the screen on and off anyways if you missed the BLN?
 
J

jz3

Senior Member
Jun 22, 2010
120
50
Axiomkid said:
BLN is quite useless, unless your 1 of those ppl that stare at your phone constantly in pure silence. Either way don't you have to click the screen on and off anyways if you missed the BLN?
Click to expand...
Click to collapse

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.
 
A

Axiomkid

Senior Member
Jan 6, 2009
875
308
jz3 said:
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.
Click to expand...
Click to collapse

Eh! I see where your at. And I agree lockscreens are starting to become a pain. Especially when the phone times out and locks me out each and every time. I rather not set my screen to sleep after more than 30 seconds, but the lockscreen keeps the lil sister outta my phone.
 
G

garbagedump481

Senior Member
Dec 12, 2011
171
86
I live on the internet and vacation in the USA
jz3 said:
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.
Click to expand...
Click to collapse

But as dearest Entropy said, the only reliable implementations keep your phone out of deep sleep, causing you to lose much more than you'd save. If what Entropy meant was for custom firmwares, then Stock or Based-On-Stock ROMs are your best bet.
 
Last edited:
J

jz3

Senior Member
Jun 22, 2010
120
50
Axiomkid said:
Eh! I see where your at. And I agree lockscreens are starting to become a pain. Especially when the phone times out and locks me out each and every time. I rather not set my screen to sleep after more than 30 seconds, but the lockscreen keeps the lil sister outta my phone.
Click to expand...
Click to collapse

lol I don't have to worry about that, my lil sister is 46!
 
Wilkij

Wilkij

Senior Member
Nov 16, 2011
153
111
Knoxville
OnePlus 8
Samsung Galaxy S21+
Portability

A search found a similar question, but not the answer. Do I need to disable voodoo lagfix if moving from a costom lb3 ROM to this one? Or does this ROM use voodoo?

Also, if I flash this ROM will I have problems retuning to my current one using nandroid recovery?

If these question have been asked/answered earlier, I apologize and would appreciate someone pointing me to the posts.

Thanks
 
J

jason4962

Senior Member
Dec 18, 2011
1,031
161
NEW JERSEY
Wilkij said:
A search found a similar question, but not the answer. Do I need to disable voodoo lagfix if moving from a costom lb3 ROM to this one? Or does this ROM use voodoo?

Also, if I flash this ROM will I have problems retuning to my current one using nandroid recovery?

If these question have been asked/answered earlier, I apologize and would appreciate someone pointing me to the posts.

Thanks
Click to expand...
Click to collapse

when you flash ics(cm9) it givces you blue cmw, and your old GB rom is using red cmw , i try to restore an old GB rom ( back up with red cmw ) and after having blue cmw it did not restore it only gave error

this is what happen when i got miui last time which uses blue cmw v5
 
  • Like
Reactions: Wilkij
The_Zodiac

The_Zodiac

Senior Member
Aug 28, 2010
1,956
260
Unknown
Bjray said:
Use the V6 SuperCharger like I did...

Link 1: http://xdaforums.com/showthread.php?t=991276
Link 2: http://xdaforums.com/attachment.php?attachmentid=993904&d=1334036191
Link 3: http://android.mimic.ca/

1. Download a script (I used RC8.2)
2. Install BusyBox (Google Play)
3. Install Script Manager (Browse as Root in Config) (If you can't download it from the market use my attachment)
4. Load script into Script Manager (Run As Root - the skull and crossbones icon which turns green when selected)
5. Follow instructions/user prompts & select what you want

Then do the ICS steps:
1. Install V6 SuperCharger script as always.
....Note: You will probably get Segmentation Fault errors running the V6 SuperCharger script on ICS due to a flakey su (superuser) binary.
2. Patch and install services.jar as explained below by whichever method you like best (online with ICS OOM Priority Charger webapp or manually)
3. SuperClean & ReStart! (ie. Wipe Dalvik Cache & Reboot)
Click to expand...
Click to collapse

we may want to consider adding this to the op, it definitely really really increases speed.

and the instructions arent too difficult to follow.
 
You must log in or register to reply here.

Similar threads

scott.hart.bti
[ROM][JellyBean][4.3]Unofficial CM10.2 - 10/27/2013 - Butter - MTD - OC Kernel
Replies
8K
Views
2M
G
GerardSamija
P
[REF] Infuse 4G Super Everything Thread -(updated APRIL 14, 2012)
Replies
199
Views
281K
meanhacker
meanhacker
L
  • Sticky
[ HowTo ] Samsung Infuse 4g Free Unlock and Root on all O/S's
Replies
523
Views
463K
D
dchobo
uberamd
[ROM][UNOFFICIAL] Compiled CM 7 for Infuse 4G - Automated Nightly Builds
Replies
870
Views
224K
R
reactorcooler
J
[ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g
Replies
335
Views
327K
J
jerryspring

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 215
    E
    Entropy512
    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.
    View
    63
    E
    Entropy512
    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
    View
    51
    E
    Entropy512
    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.
    View
    49
    E
    Entropy512
    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
    View
    36
    E
    Entropy512
    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.
    View

New posts