[Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012)
- Thread starter Entropy512
- Start date
-
- Tags
- development
Yeah, you probably need to back-port this into your tree:
http://review.cyanogenmod.com/#/c/22437/
Not sure if there was a similar one done in CM9.
CM9 has been real buttery smooth for me. I can't wait to try out CM10 with butta. Thks for this great ROM, I am loving it
Sent from my SGH-I997 using xda premium
Sent from my SGH-I997 using xda premium
battery performance test
hi guys, just wanted to share with you an interesting behavior i found on cm9 with OC kernel:
scenario was: my phone was idle for aproximately 5 hours, no turning screen on, neither taking or making calls, no messaging whatsoever. when i looked into the battery stats: it turned out that Android OS was responsible for draining most of the battery during that idle time.
i would like to know if any dev can tell me if these is a normal behavior, because as i interpret this behavior, every idle hour takes aproximately 10% of the battery, would you guys consider this normal?. I would sincerely like your opinion in this, and if theres a problem what would you recommend to do to avoid whats happening.
PS. no wifi, gps was running during the idle time, just mobile data. i only missed calls (2 only) and probably 4 whatsapp messages during that time.
hi guys, just wanted to share with you an interesting behavior i found on cm9 with OC kernel:
scenario was: my phone was idle for aproximately 5 hours, no turning screen on, neither taking or making calls, no messaging whatsoever. when i looked into the battery stats: it turned out that Android OS was responsible for draining most of the battery during that idle time.
i would like to know if any dev can tell me if these is a normal behavior, because as i interpret this behavior, every idle hour takes aproximately 10% of the battery, would you guys consider this normal?. I would sincerely like your opinion in this, and if theres a problem what would you recommend to do to avoid whats happening.
PS. no wifi, gps was running during the idle time, just mobile data. i only missed calls (2 only) and probably 4 whatsapp messages during that time.
Attachments
Its a random hit and miss bug with any ROM...gb-ics-jb...they all have it...just about everyone experiences it at least once...some say it is caused by media scanner malfunctioning
A fix would be to go to recovery and wipe cache and dalvic, then boot it up and leave your screen on for like 10 minutes to let all the scans finish while its awake...if that doesn't work then a full wipe and reflash should work
Sent from my SGH-I997 using Tapatalk 2
Ringer issues-
I was using google play music to listen to some music for a while today. I left it plugged in after the music stopped.
I had some desktop speakers plugged in to the headphone jack.
While i was listening I received a phone call, but the phone never rang.
I thought maybe i'd been out of ear shot, so i tried calling the phone with my landline.
The screen displayed just like it would when receiving a phone call, but there was no sound.
I'm not sure if this is normal. I couldn't find anything in settings that would make a difference. I checked system, play music and DSP manager.
There's also nothing in the Q&A thread.
I was using google play music to listen to some music for a while today. I left it plugged in after the music stopped.
I had some desktop speakers plugged in to the headphone jack.
While i was listening I received a phone call, but the phone never rang.
I thought maybe i'd been out of ear shot, so i tried calling the phone with my landline.
The screen displayed just like it would when receiving a phone call, but there was no sound.
I'm not sure if this is normal. I couldn't find anything in settings that would make a difference. I checked system, play music and DSP manager.
There's also nothing in the Q&A thread.
GoSooners345
Senior Member
Thank you!
Hi Guys,
I just want to thank Entropy 512 and so many other developers for your continuous effort to help us. I installed CM9 on my Samsung Infuse and it is running like a charm. So far it has been awesome. I never thought I would see ICS running on my Infuse but thanks to you guys, I now have it. You guys are simply superb!
Thanks again.
Krantiredeyes
Hi Guys,
I just want to thank Entropy 512 and so many other developers for your continuous effort to help us. I installed CM9 on my Samsung Infuse and it is running like a charm. So far it has been awesome. I never thought I would see ICS running on my Infuse but thanks to you guys, I now have it. You guys are simply superb!
Thanks again.
Krantiredeyes
you just reminded me I need to upload one last CM9 build, that I compiled over a month ago...
At some point I need to restart with CM10, but the whole Exynos disaster on my other devices has been consuming my time, my brain, and my will to hack.
If the Xperia TL on AT&T has an unlockable bootloader, I think I might buy that and then focus on that and the Infuse.
**** Exynos4.
At some point I need to restart with CM10, but the whole Exynos disaster on my other devices has been consuming my time, my brain, and my will to hack.
If the Xperia TL on AT&T has an unlockable bootloader, I think I might buy that and then focus on that and the Infuse.
**** Exynos4.
Looking forward for this next build
Sent from my SGH-I997 using xda app-developers app
I think CM10 is coming along pretty well. The remaining stuff I think is minor, other than the camera mess... though I had some ideas on that while poking around the aries kernel. (I'm insane enough to try booting an aries kernel on my infuse.. we'll see how that goes... I haven't finished looking for what I NEED to make sure I pull over.. I have the onenand stuff pulled over, and I'm considering just inheriting the captivate stuff otherwise except where I know we're different, rather than going through each and every config_samsung_captivate/fascinate/etc ifdef.).
Then again, you might not like the way I decided to handle onenand/etc when cm10 (Plus gapps) got too big for the 350MB /system. It seems to be back under 350 now that rommanager has been removed, but I don't like how close it is/was. Technically we didn't need to go through the same level of mess as aries, and doing it their way splits /data and /datadata again, but it seems like a workable solution to me, and more future-proof than stealing a few MB at a time from /cache.
Last edited:
Hello all,
I am having an issue here. I am a bit new with flashing so not sure what to do at this point. I flashed the CM9 zip in CMW. Then rebooted and got stuck at the Samsung logo. Now I try to reboot into CMW again to re-flash the CM9 zip but I can't get in. I only see some distorted image. I am not sure if this is what Rainbows are. Please help!
Thanks!
I am having an issue here. I am a bit new with flashing so not sure what to do at this point. I flashed the CM9 zip in CMW. Then rebooted and got stuck at the Samsung logo. Now I try to reboot into CMW again to re-flash the CM9 zip but I can't get in. I only see some distorted image. I am not sure if this is what Rainbows are. Please help!
Thanks!
First it is know that this user is less than 10 posts, with a join date of 2007, seems miss the cut off for the 10 post rule, So NO need to keep reporting it, Thank You.
http://xdaforums.com/showpost.php?p=24901128&postcount=3
Addtionally the below user has provided assistance for you...
Now Sir, please refer back to the OP, since you are not familiar with flashing read the OP and this post to help in your issues of the "Famous Rainbow" effect:
http://xdaforums.com/showpost.php?p=24901128&postcount=3
Addtionally the below user has provided assistance for you...
I don't know what OP means in here but where I come from OP means other people.
Sent from my X10 using xda app-developers app
A Google search of forum terminology would have revealed that it means Original Post or Original Poster, with the former being appropriate in this instance.
Inadequate searching is the leading cause of irritated internet syndrome (IIS). Microsoft is the second most common cause of that.
Sent from my SGH-I997 using xda app-developers app
Last edited:
I have the infuse 4g running stock GB 2.3.6/rooted running "red CWM"
in order to install the JB4.2.2 I need to install this ROM ICS
my question i out the last built on the SD card but when i reboot in to recovery i am not able to access the SDCard, i never notice this,
Is this normal for "red CWM"
can i just put the rom in to the internal memory and install it from there?
any suggestions will be greatly appreciated.
in order to install the JB4.2.2 I need to install this ROM ICS
my question i out the last built on the SD card but when i reboot in to recovery i am not able to access the SDCard, i never notice this,
Is this normal for "red CWM"
can i just put the rom in to the internal memory and install it from there?
any suggestions will be greatly appreciated.
D
Deleted member 804010
Guest
Was normal for me - I saved to internal SD and it was fine
Good luck
Sent from my SGH-I897 using Tapatalk 2
Good luck
Sent from my SGH-I897 using Tapatalk 2
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
215DO 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.63Building - 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 infuse4g51FAQ
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.49Change 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 changes36I'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.
