[Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012)
- Thread starter Entropy512
- Start date
-
- Tags
- development
Can you really say that though? It is for anyone who has flashed or tried to flash a non-samsung rom, sure, but outside of that it can be entirely possible that they wouldn't know at all.
Say for example someone has an infuse, has never flashed anything on it but saw or heard somewhere that an ICS port and jumped straight to this thread. They wouldn't know that it is a known problem, or a feature soon-to-be restored in a W.I.P. ROM (unless of course they read the OP like they should have
)I'm not trying to defend the guy or anything, but I do understand if it continually gets brought up again by random people, regardless of how many times you state it in the OP.
I just don't see the need to jump down people's throats. It, in the end, is just a simple question. I see no problem with simply ignoring the question, or giving a short, blunt answer. In my view it's simple, and you said it yourself:
"It won't work. If you want it to, either do it yourself or flash a different rom." <- That right there is good enough for me and i'm sure everyone else. I reeealy don't see why that has continually been blown up to be such a big issue. Android is about choice, they are free to flash whatever else they feel makes them happy. You just keep doing your thing, there are many that are appreciative of your work and will state such.
Last edited:
Can you really say that though? It is for anyone who has flashed or tried to flash a non-samsung rom, sure, but outside of that it can be entirely possible that they wouldn't know at all.
Say for example someone has an infuse, has never flashed anything on it but saw or heard somewhere that an ICS port and jumped straight to this thread. They wouldn't know that it is a known problem, or a feature soon-to-be restored in a W.I.P. ROM (unless of course they read the OP like they should have
I'm not trying to defend the guy or anything, but I do understand if it continually gets brought up again by random people, regardless of how many times you state it in the OP.
I just don't see the need to jump down people's throats. It, in the end, is just a simple question. I see no problem with simply ignoring the question, or giving a short, blunt answer. In my view it's simple, and you said it yourself:
"It won't work. If you want it to, either do it yourself or flash a different rom." <- That right there is good enough for me and i'm sure everyone else. I reeealy don't see why that has continually been blown up to be such a big issue. Android is about choice, they are free to flash whatever else they feel makes them happy. You just keep doing your thing, there are many that are appreciative of your work and will state such.
There maybe a simple expectation for any user to be informed enough to read the op and then read the thread to understand what has been addressed.
^^^ All to often, unfortunately, that's the problem right there ^^^
(and usually a recipe for disaster)
XDA is intended to be a learning (as well as sharing) community. People who simply "jump in" to flashing a custom/developmental ROM without thoroughly reading and understanding what they're getting into are not only going to have issues, but they're also going to annoy the hell out of the developer (and the other educated users) by asking questions already answered many times over.
Of course it would be kinder/gentler to simply ignore them -- but this is one of the few things that really irritates many of us. (It is also clearly stated in the XDA forum rules).
Let's have a nice day
and Entropy, thanks a million for all your hard work!
Ran the whole day on wifi, streaming music at work using the 5/2 update. No dropouts, which surprised me because every ROM I've ever used lost connection at least 3 times during a day. I always assumed it was just our crappy corporate wifi. Great job, Entropy!
Go have a pizza - Confirmation #3MK35894KT050273B
Go have a pizza - Confirmation #3MK35894KT050273B
It was a simple question and the answer was just two letters
I dont deserve all that attack
I dont have to read 750 posts most of them people thanking or complaining
I have never flash CM before and as stated in the first post bluetooth worked "partially in cm7" so I thought you might consider it
Im not a new member and I know how some developers acting like they are cutting from their flesh when answering a "noobi,repeated,stupid" questions
So please stop doing that
I dont deserve all that attack
I dont have to read 750 posts most of them people thanking or complaining
I have never flash CM before and as stated in the first post bluetooth worked "partially in cm7" so I thought you might consider it
Im not a new member and I know how some developers acting like they are cutting from their flesh when answering a "noobi,repeated,stupid" questions
So please stop doing that
Of course there is a chance, but you have to admit it is a silly question that has been asked many times in the last few days/weeks.
What answer did you expect otherwise?
Last edited:
Don't think so, possibly just miscellaneous cleaning of code and stuff.
But definitely try out 5.02 amazing rom. Thanks Entropy!
Sent from my SGH-I997 using xda premium
Ya mofo's, need to get with the program...see my blue tooth is bang'n...**** is tight and works great....
my keys are funnier than you
dont try to be funny while you aren't
ha ha...take it easy...trying to lighten the mood in here...but as I can see...not working with you...so just...take it....
, I am sure Communications Engineers have some humor....?When I did radio the COMS Engineers I knew just argued about whose tower was bigger.
Sent from my SGH-I997 using xda premium
Sent from my SGH-I997 using xda premium
I'd be happy too its on my list to do just busy with work figured I'd put in as much input as I could atm.
Sent from my SGH-I997 using XDA
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.
