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

Search This thread
By:
Advanced…
Radiotsar

Radiotsar

Senior Member
Jan 7, 2012
200
39
Elgin, IL
Axiomkid said:
I'm saying in General any bugs your gonna report don't whine about it, Post a logcat.
Click to expand...
Click to collapse

Forgive me for asking, but is the preferred method for posting a logcat to only post the lines that state "Error", "Exception", "Fatal" & "Failure"? Should we avoid such lines if they are app related or could those provide additional information?

I figure you don't need the entire logcat if some things are listed as doing what they should have.
 
Q

qkster

Retired Recognized Developer
Apr 5, 2011
3,276
4,422
USA
RoryB said:
Excuse my ignorance. Don't kill them? Just let them run in the background?

I have noticed some "kill" themselves after a period of time, but it seems not all the time or not all of them.

Do they eventually stop on their own?
Click to expand...
Click to collapse

Rory,
There are a few schools of thoughts on this. Some will say that unused memory is wasted memory. Supposedly GB and ICS has better memory management that will allocate each programs accordingly. You don't necessarily have to end or kill programs as you did when froyo or eclair was introduced. Idk if while some programs are loaded they will consume battery or not. Some apps running in the background certainly can as they actively pull and push data. Ex: email, facebook, skype, fring)
There are some strong opinions in both camps...
Some ROMs however, have reduced avail cache or mem allocation to free up more memory to allow more cpu/gpu and mem hog games to run "faster".
idk.
I'm pretty simple minded and poor at multitasking. As a habit, I kill all apps I see on my phone that I'm not using actively. I've seen arguments that re-starting the app anew can also use up battery as well. Who knows. I have not seen any harmful effects.
I guess in this way, I'm like a dictator - lol..absolute iron fist - no apps do anything unless i allow it. :) ymmv

edit: oldbbman: I was nominated. but power corrupts absolutely. So I'm corrupted. I need to be repartitioned.
 
Last edited:
  • Like
Reactions: Zen Arcade, FlyingIsFun1217, jgruberman and 1 other person
RoryB

RoryB

Inactive Recognized Developer
Sep 4, 2008
2,921
766
Lexington
I am doing the same thing. I would run the calculator and after a while I would see it still running in task manager so I'd kill it. Now I usually go kill it right after I use it. About the only program I do not kill right after using is email since I am in it the most throughout the day.
 
A

Axiomkid

Senior Member
Jan 6, 2009
875
308
Radiotsar said:
Forgive me for asking, but is the preferred method for posting a logcat to only post the lines that state "Error", "Exception", "Fatal" & "Failure"? Should we avoid such lines if they are app related or could those provide additional information?

I figure you don't need the entire logcat if some things are listed as doing what they should have.
Click to expand...
Click to collapse

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

blackwrx02

Senior Member
May 3, 2006
276
39
jgruberman said:
If you want to know what percentage of the battery is being drained and how quickly, get My Battery Drain Analyzer

If you want to know what's running, get Better Battery Stats

The original posting with a lot of information about Better Battery Stats is HERE

Even further detailed information and about how to interpret the program is HERE

If you only use your WiFi or GPS at certain times throughout the day, then you may want an app that is good at setting profiles for your phone based on time. I wake up, go to work, come home and go to sleep at the same time every day... so this app is great for me - PhoneWeaver.
The above is a trial, if you like it, buy the full... it's VERY worth it.

DON'T kill apps with "Startup Manager" and "AutoKill" programs... they do more harm than good... HERE'S WHY. Use Better Battery Stats and review the Wakelocks and see what is running and not letting your phone chill(no pun intended). The Battery Drain Analyzer will tell you how much is being drained in percentage format... use this before and after every time you make changes that could affect the battery to see how much improvement or harm you've done.

I use all of the above, and recommend it all highly. Let me know if you have questions on how to use them. Also, if you don't use your GPS, leave it off - big battery hog. And remember... keep your brightness AS LOW AS YOU CAN COMFORTABLY HAVE IT!!! (Also a setting in PhoneWeaver) :D
Click to expand...
Click to collapse

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.

Also, watching battery stats with the built in monitor shows its mostly screen and google account sync.

Maybe a fresh install will cure things?
 
jgruberman

jgruberman

Senior Member
Dec 6, 2011
423
79
Dallas
blackwrx02 said:
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.

Also, watching battery stats with the built in monitor shows its mostly screen and google account sync.

Maybe a fresh install will cure things?
Click to expand...
Click to collapse

I'd think a fresh install would at leas determine that it wasn't ROM related. and FWIW... it's my daily driver, no issues at all.

There's a link in my sig for how to do a clean install - you can try to follow that and get a fresh, brand new install if that's the route you want to take.
 
  • Like
Reactions: blackwrx02
B

blackwrx02

Senior Member
May 3, 2006
276
39
jgruberman said:
I'd think a fresh install would at leas determine that it wasn't ROM related. and FWIW... it's my daily driver, no issues at all.

There's a link in my sig for how to do a clean install - you can try to follow that and get a fresh, brand new install if that's the route you want to take.
Click to expand...
Click to collapse

Thanks. Fresh install it is. If I could the battery working normally, and figure out the MMS issue (had it working breifly) I'd be using this as a DD for sure.
 
tekgurl

tekgurl

Senior Member
Feb 23, 2010
121
14
Anyone having issues with waking phone on 4/23 build? I did not overclock or alter anything. This was my 4th install. 2 builds from jt and 2 from Entropy. Never had any problems before. Wiped before install.

Sent from my SGH-I997 using xda premium
 
C

cline2

Senior Member
Jun 2, 2011
802
99
Worked great i could live with rainbow in cwm for now keep it up

Sent from my SAMSUNG-SGH-I997 using xda premium
 
Demonic240

Demonic240

Senior Member
Mar 18, 2009
1,007
122
Plano
blackwrx02 said:
I'm having a REALLY hard time with the battery on this ROM. I see everyone saying how good it is. I can normally make it all day on other ROMS (off charger at 7am, back on the charger at 11:30-ish). No out of the norm usage (and no phone calls during my work day), its just on my desk most of the day. With ICS i'm having to charge it when I get home around 5:00pm

I've changed the build.prop to reduce wifi scanning which has helped, but only a little.

Also getting quite a bit of heat sometimes off the phone, so something is running but I'm just not able to tell what it is...would appreciate some input on where to start looking.
Click to expand...
Click to collapse

What have you installed? I'm running as-is with only a couple of random apps installed, but I can make it more than 24 hours on one charge.
 
jgruberman

jgruberman

Senior Member
Dec 6, 2011
423
79
Dallas
blackwrx02 said:
Thanks. Fresh install it is. If I could the battery working normally, and figure out the MMS issue (had it working breifly) I'd be using this as a DD for sure.
Click to expand...
Click to collapse

Check one of the links in my sig for the MMS. After you replace that file, don't forget to reset your APNs to default.

---------- Post added at 08:27 AM ---------- Previous post was at 08:26 AM ----------
Demonic240 said:
What have you installed? I'm running as-is with only a couple of random apps installed, but I can make it more than 24 hours on one charge.
Click to expand...
Click to collapse

I think if he is having heat issues from his phone, then it's more than an app. I'd almost question hardware if there is substantial heat. But I know mine in the past got toasty, and it was attributed to a bad flash.

---------- Post added at 08:28 AM ---------- Previous post was at 08:27 AM ----------
cline2 said:
Worked great i could live with rainbow in cwm for now keep it up
Click to expand...
Click to collapse

and if you can't, just do a Super Clean Install from the link in my sig ;)

---------- Post added at 08:31 AM ---------- Previous post was at 08:28 AM ----------
wayzata said:
The script called thunderbolt...
Click to expand...
Click to collapse

THIS is what he is talking about..... but not sure of the answer. Entropy would be better suited to answer that.
 
gatoraid84

gatoraid84

Senior Member
Jan 12, 2012
450
162
Jacksonville
Twice yesterday I went to wake my phone...screen came on briefly then phone shutdown..rebooted it is fine and hasn't happened since

Sent from my SGH-I997 using XDA
 
jgruberman

jgruberman

Senior Member
Dec 6, 2011
423
79
Dallas
gatoraid84 said:
Twice yesterday I went to wake my phone...screen came on briefly then phone shutdown..rebooted it is fine and hasn't happened since
Click to expand...
Click to collapse

That screams "bad flash" to me. It will happen again(sorry for the pessimism). I had the same issues previously and a good, clean flash fixed it. If you want to go through the steps, check the link in my sig.
 
jgruberman

jgruberman

Senior Member
Dec 6, 2011
423
79
Dallas
Axiomkid said:
Odd! I haven't seen this issue yet, No wake issues yet so far.
Click to expand...
Click to collapse

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.
 
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
LinuxBozo
[SOURCE] [UNOFFICIAL] CM7 for Infuse (Updated: 2011-09-29)
Replies
990
Views
201K
H
Hobbbez

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