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

Search This thread

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
No, Don't need the entire Logcat as it would take Entropy time to look thru, But yea if you only post the lines with the Error's and everything else, it would help Entropy better to understand whats wrong.

Actually, too often people don't understand what is relevant and what isn't - so never try to censor it yourself. However don't post the whole thing as a code block, zip it up or attach as a text file.

IF it is something you can reliably reproduce, clear the logcat before you trigger the issue:
Code:
logcat -c
logcat -v time > blah.txt
then reproduce the bug
 

gatoraid84

Senior Member
Jan 12, 2012
450
162
Jacksonville
Well I had those similar issues with other ROMs.... so I wasn't even thinking it related to CM9, just thinking that it was a bad flash... or something didn't get wiped.

Like my issues were IDENTICAL to that. It was having issues waking up sometimes to where I had to hard reboot... sometimes it'd come on then reboot right after.

I had this problem on ZEUS build 6

Sent from my SGH-I997 using XDA
 

pdtp

Senior Member
Jul 22, 2006
210
55
Samsung Galaxy S22 Ultra
I have seen this error posted but no real response to it.
I'm on the 4/23 build with the build.prop mod of heapzize=64m and the wifi scan set to 120. This error happened before the mod as well. I had no issues flashing the rom.
My soft keys will stop responding for a short period of time, longest being 15 sec or so. The rest of the phone works including the the touch screen, i can put the phone to sleep and rewake it and they still wont work. After the a few seconds they will light up and start to work without issue. I cannot reproduce it on command. This happens once or twice a day.

On a side note, I was wondering if there has been any progress on getting bluetooth up and running?
 

cline2

Senior Member
Jun 2, 2011
802
99
Sorry if I miss something, I am on 4/23. Tethering not working??? I don't see list mention If it works or not.


Sent from my SGH-I997 using xda premium
 

MythicBlue

Senior Member
Jun 23, 2010
64
9
Hi there guys, i found a bug in the camera when you are recording in 720p with flash activated and you proceed to focus something the image gets bouncing a lot... it's kind of weird.

By the way sorry about my poor english.

yeah i am getting the same thing... when i record in 720p the image just bounces all over the place... you can see it happen while recording and then wile playing the file back... quite jittery... any known fixes for this? also not that the 480 res works fine... its just the 720 res
 
Last edited:

GuyIncognito721

Senior Member
Mar 1, 2011
424
226
Oswego
I have seen this error posted but no real response to it.
I'm on the 4/23 build with the build.prop mod of heapzize=64m and the wifi scan set to 120. This error happened before the mod as well. I had no issues flashing the rom.
My soft keys will stop responding for a short period of time, longest being 15 sec or so. The rest of the phone works including the the touch screen, i can put the phone to sleep and rewake it and they still wont work. After the a few seconds they will light up and start to work without issue. I cannot reproduce it on command. This happens once or twice a day.

On a side note, I was wondering if there has been any progress on getting bluetooth up and running?

Have had similar issues, without any build.prop tweaks.

Also, please stop asking about bluetooth. It's already been discussed ad nauseum.
 

EscapeE

Member
Jan 2, 2011
27
1
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

Sent from my SGH-I997 using Tapatalk
 

jgruberman

Senior Member
Dec 6, 2011
423
79
Dallas
I had this problem on ZEUS build 6

Ditto. But after a GOOD flash, Zeus was working well for me regardless.

---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------

For some reason mms' wont download. dont know if its the ROM, APN settings or what. any ideas?

Check my sig for MMS fix.

---------- Post added at 02:35 PM ---------- Previous post was at 02:35 PM ----------

Sorry if I miss something, I am on 4/23. Tethering not working??? I don't see list mention If it works or not.

Check my sig for the Unofficial FAQ, which includes a link to the changelog - Look at the 3rd line on 4/22 regarding tethering.

---------- Post added at 02:37 PM ---------- Previous post was at 02:35 PM ----------

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

You need to do a Super Clean Install before claiming the ROM is full of bugs. I use the ROM daily as do many others without problem.

If you want to give the ROM a fair chance before writing it off as bug-ridden, then click the link in my sig for instructions on a Super Clean Install. It will work, and you will be happy... assuming you know how to follow directions ;)
 

rxnelson

Senior Member
Aug 30, 2011
676
76
I guess this is where I'm having a hard time. I've not changed my habits of usage at all vs other ROMS. While I completely understand that this is a work in progress and not meant to be a daily-driver ROM, i see people saying the battery is good for them.

GPS is always off unless I absolutely NEED to use it. I tried the task-killer idea but it hasn't made a bit of difference in battery life. The heat issue is really what concerns me. I can feel it heating up in my pocket sometimes.

Maybe a fresh install will cure things?

I can't speak to this build as I'm on jts build 2 but use CPU spy to check for deep sleep. Also on both of jts builds my wifi and/or data will randomly be "stuck" with arrows on as if it is trying to connect when I'm not using data. I can't duplicate it on purpose so haven't reported it. Airplane mode toggle fixes this.

Sent from my Galaxy Nexus using Tapatalk 2
 

porksoda02

Member
Oct 12, 2011
42
2
I guess ... There are so many threads about CM9 here...
I'll just put this here.


The menu/home keys sometimes don't work/respond when i unlock the screen.
 

Radiotsar

Senior Member
Jan 7, 2012
200
39
Elgin, IL
Actually, too often people don't understand what is relevant and what isn't - so never try to censor it yourself. However don't post the whole thing as a code block, zip it up or attach as a text file.

I've tried to clean this up & make it less a wall of text - hope it helps somewhat. The only reason I asked about editing is that it appears some of the repetition in the attached are the same processes/apps trying to connect numerous times and failing.

What I ran into this morning was the wifi was turned off (despite being left on) and not being able to turn it on. Initially both the wifi toggle and the switch under System Settings>Wireless & Networks were unresponsive. With repeated attempts, the wifi under System Settings finally went to search for my router, but could not locate it despite it being about 2 ft away. I pulled the logcat and then rebooted, after which the wifi came back and located my router automatically.
 

Attachments

  • 2012-04-27-05-31-32-746.zip
    17.7 KB · Views: 13
  • Like
Reactions: threi_

jblparisi

Senior Member
Jun 12, 2007
572
508
Rom runs fairly stable for a beta/alpha release other than the listed known bugs, in fact it runs perfect for what it is. You need to start over and go from there. Try Heindall or Odin.
 
Last edited by a moderator:

Radiotsar

Senior Member
Jan 7, 2012
200
39
Elgin, IL
My soft keys will stop responding for a short period of time, longest being 15 sec or so. The rest of the phone works including the the touch screen, i can put the phone to sleep and rewake it and they still wont work. After the a few seconds they will light up and start to work without issue. I cannot reproduce it on command. This happens once or twice a day.

Somewhat same here, except when it happens the screen is also unresponsive.
 

dagunshooow

Senior Member
Oct 6, 2011
59
18
I have seen this error posted but no real response to it.
I'm on the 4/23 build with the build.prop mod of heapzize=64m and the wifi scan set to 120. This error happened before the mod as well. I had no issues flashing the rom.
My soft keys will stop responding for a short period of time, longest being 15 sec or so. The rest of the phone works including the the touch screen, i can put the phone to sleep and rewake it and they still wont work. After the a few seconds they will light up and start to work without issue. I cannot reproduce it on command. This happens once or twice a day.

On a side note, I was wondering if there has been any progress on getting bluetooth up and running?

Had the same issue. Re-downloaded and re-flashed per OP. Made sure to be EXACT, and resolved the issue. I originally posted abt this way back. Don't want to thumb through 60 pages to find it. It is almost definitely a bad flash, I'd say. I am still on 4/19 due to reports of issues on 4/23. Things have been running more or less flawlessly. My MMS is broken, and I have seen some fixes for it, but I haven't had a chance to research it yet.

Sent from my SGH-I997 using XDA
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
Sorry if I miss something, I am on 4/23. Tethering not working??? I don't see list mention If it works or not.


Sent from my SGH-I997 using xda premium
What do the BOLD LETTERS AT THE TOP OF THE FIRST POST SAY?

You CLEARLY DID NOT READ.

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

Sent from my SGH-I997 using Tapatalk
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.

I have seen this error posted but no real response to it.
I'm on the 4/23 build with the build.prop mod of heapzize=64m and the wifi scan set to 120. This error happened before the mod as well. I had no issues flashing the rom.
My soft keys will stop responding for a short period of time, longest being 15 sec or so. The rest of the phone works including the the touch screen, i can put the phone to sleep and rewake it and they still wont work. After the a few seconds they will light up and start to work without issue. I cannot reproduce it on command. This happens once or twice a day.

On a side note, I was wondering if there has been any progress on getting bluetooth up and running?

Bug reports are not accepted from anyone running modifications. I am not encountering any such issues.
 

wyattjo

Member
May 9, 2011
27
4
Calgary, Alberta
Awesome rom... been running it 2 days now without issue I won't be using anything but ics on my phone now! Thanks for the hard work entropy and all other devs associated with this rom

Sent from my SGH-I997 using Tapatalk 2
 

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.