guys i just flashed the newest built and didn't do anything, turn my data on and choose my apn ( it was already in ) and then send a picture, took 10 seconds per pic with full 5 bars, so the story is there are no issues with mms
[Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012)
- Thread starter Entropy512
- Start date
-
- Tags
- development
Several random reboot since installing this new release.
Phone was just sitting on the table doing nothing each time.
Sent from my SGH-I997 using xda premium
Phone was just sitting on the table doing nothing each time.
Sent from my SGH-I997 using xda premium
Hey just wanted to say THANKS A TON!!!! ur rootswiki link really helped!http://rootzwiki.com/topic/22877-rom-ics-imm76d-cm9-ics-alpha-port-for-infuse4g-build2-0414/what i did was i used odin and put phone in download mode then i flashed this rom here http://xdaforums.com/showthread.php?t=1507658 and i got my boot loaders i needed then i put phone back in to download mode and flashed the ICS recovery tar from here http://rootzwiki.com/topic/22877-rom-ics-imm76d-cm9-ics-alpha-port-for-infuse4g-build2-0414/ after that you should see the blue ics recovery then you should be good to go on flashing this rom in CWM that's what i did and i have no rainbow recovery and rom works like a charm i have seen other ways but not sure how to use the other tool lol
I followed instructions using the old ICS build and it worked then updated it to newest one!
Hey just wanted to say THANKS A TON!!!! ur rootswiki link really helped!http://rootzwiki.com/topic/22877-rom-ics-imm76d-cm9-ics-alpha-port-for-infuse4g-build2-0414/
I followed instructions using the old ICS build and it worked then updated it to newest one!
your welcome glad to hear it worked for you
I think that is because you didn't really brick. A true brick means the screen won't even come on so I've been told. I've seen the screen you are referring to. I think that just means bad flash.
Anyway...back to development. Still haven't flashed your build but thanks again E.
Sent from my Galaxy Nexus using Tapatalk 2
Same problem but I haven't seen it happen yet when using a wall charger but now that I think about it the few times it happened I had been using a computer usb port
Sent from my SGH-I997 using Tapatalk 2
Ok, after a day using my self-compiled 'with wifi fix' build from 5/1, and then a day on entropy's 5/2 build, I got the wifi bug both days. I am no longer seeing the kernel panic in dmesg, so the memory alloc fail that was getting reported is no longer happening, but I'm still seeing wifi fail to turn back on after my day.
Once again, how I reproduce it on a daily basis:
Phone is rebooted in the evening (So I can connect to wifi at home).
Wifi is left on until I leave for work the next morning, at which point I turn it off.
When I arrive at work, I turn on airplane mode since I have 0 signal 60% of the time there anyways.
When I go to lunch I (usually) turn airplane mode back off to get messages/emails/etc.
When I go back to work I turn airplane mode back on
when I leave work I turn airplane back off..
and when I get home, I turn wifi back on, and it fails to turn on. I grab a logcat, and reboot.
Logcat attached. This is a short one. Had phone plugged into my computer, cleared logcat, hit wifi button, waited a minute, grabbed the logcat.
Once again, how I reproduce it on a daily basis:
Phone is rebooted in the evening (So I can connect to wifi at home).
Wifi is left on until I leave for work the next morning, at which point I turn it off.
When I arrive at work, I turn on airplane mode since I have 0 signal 60% of the time there anyways.
When I go to lunch I (usually) turn airplane mode back off to get messages/emails/etc.
When I go back to work I turn airplane mode back on
when I leave work I turn airplane back off..
and when I get home, I turn wifi back on, and it fails to turn on. I grab a logcat, and reboot.
Logcat attached. This is a short one. Had phone plugged into my computer, cleared logcat, hit wifi button, waited a minute, grabbed the logcat.
LOL thats a form of the download screen. Sorry for pretty much useless post of mine, just want to clear the confusion up.
Hey guys, just dropping to say, whats up! Hope all is good here. Peace
Sent from my SAMSUNG-SGH-I717 using XDA
Sent from my SAMSUNG-SGH-I717 using XDA
Here's the issues I've came across. I came from Zeus so I don't have gb boot loaders im kinda iffy on flashing. I've had the wifi issue after charging but all I had to do was turn it off then on from the status bar. Next issue is sometimes when I turn the screen on from stand by it won't turn on and I have to reboot. I've had that since the last 2 updates. Last one is sometimes the clock in the status bar gets stuck it usually fixes itself after a while but it throws me off. Oh and I can send pics but couldn't receive them.
Sent from my SGH-I997 using XDA
Sent from my SGH-I997 using XDA
And? The build is alpha, help the dev out and try and lock down the issue, try a odin back to stock, get the correct GB BL's, grab a logcat of the issue.
Although the answer is easily found, it is far from a stupid question.
What is stupid is continuing the dogpile because of one simple question (regardless of the fact that it's been asked a billion times)
What is stupid is continuing the dogpile because of one simple question (regardless of the fact that it's been asked a billion times)
It's a stupid question... Bluetooth on AOSP firmwares has to be one of the most well known issues with the Infuse. It never fully worked on CM7, it will never fully work on CM9 unless someone with a higher tolerance for ****ing around with ALSA than myself or LinuxBozo comes along.
It may be possible to get it to CM7 levels, but that's mostly a matter of luck.
If its nonfunctionality bothers you that much - try fixing it yourself. That's the nice thing about open source firmware.
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.
New posts
-
Development [ROM][14][OFFICIAL][STABLE] [ProjectBLaze] [raven][15-04-2024]
- Latest: dmecae11@gmail.com
-
General AI Art Creator / General AI News and Chat- Latest: furrioustorrus
-
[App][Beta] Stinger News - News and RSS feeds your way. [FREE] [NO ADS]
- Latest: Stephen.k.spear
