yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] adobrakic:
Sweet baby Jesus, I cannot wait until this is stable enough for daily use. Thank you to all who have been contributing to this.
[Samsung Galaxy S (4G Model)] bhundven:
So far at 3 hours. No reboots. When actually using the phone, I see the battery usage go very fast. But when off and in my pocket, it doesn't eat the battery as much as I'd expect.

I can't wait to see some logs...
[Samsung Galaxy S (4G Model)] elmejor183:
first time opening camera app on release 6 it was pitch black. Changed the camera to front and switched back and the camera worked.

May just be a cyanogenmod source issue.
[Samsung Galaxy S (4G Model)] hampsterblade:
I'll give an update on battery life and reboots tomorrow.

Wifi calling does not work. I'll be troubleshooting that tomorrow and see if I can make a hack for it. It installs fine and connects, but immediately drops any attempted phone calls.
[Samsung Galaxy S (4G Model)] bhundven:
wifi works perfect for me.
[Samsung Galaxy S (4G Model)] hampsterblade:
T-Mobile wifi calling app. Wifi is fine.

After some research I've found wifi calling requires a kernel module, I'll figure out which one and build a wifi calling kernel. Kernel module is there, just not working. I guess I'll have to work at it.
[Samsung Galaxy S (4G Model)] Theraze:
Battery use still has Cell standby and Phone idle as the top two battery usage entries. 4h7m in and down 35%. Wifi is 2% of usage, since I manually turned it off after I left my home wifi.

Spare parts Other usage since unplugged reports:

100% running (Time spent without sleeping)

20.4% screen on

3.8% wifi on

3.8% wifi running
[Samsung Galaxy S (4G Model)] mituzora:
Reboot to recovery is broken--at least on my phone. it just reboots. I have to manually reboot to recovery to do so. also the KJ6 modem is having some connection issues--of course that doesn't go without saying my signal sucks in the dorms, as well as the wifi. I may try the KG4 modem posted earlier in this thread
[Samsung Galaxy S (4G Model)] Juls317:
I may be wrong, but i believe the reboot to recovery thing is a known problem
[Samsung Galaxy S (4G Model)] bhundven:
in recovery, fix permissions and try again.
[Samsung Galaxy S (4G Model)] bhundven:
known problem.
[Samsung Galaxy S (4G Model)] mituzora:
ahh, my apoligies, didn't see it.
[Samsung Galaxy S (4G Model)] bhundven:
No worries. I still haven't figured out how to fix it.
[Samsung Galaxy S (4G Model)] Theraze:
Yep, that seemed to fix it! Currently showing 9.5% running time in spare parts, and battery has gone down 1% (from 76% to 75%) in the last 30 minutes.

Maybe the "Fix Permissions" should be added to OP CM upgrade directions?
[Samsung Galaxy S (4G Model)] Juls317:
Will you report back on battery life later cuz (as I have been) im wanting to flash but need a fair amount of battery (like 10-12hours)
[Samsung Galaxy S (4G Model)] mituzora:
Well, my phone since flashing this has ran for over 10 hours and is at 68 percent--though don't go by this because i'm running a 3000 mAh battery. I think this ROM can survive a 12 hour run--i'm even in a bad signal area, so my battery life takes another hit thanks to this. as well as WiFi--again bad signal, so i don't get my 4g very easily(that and i'm running the 100mb prepaid plan >.<)

I'm going to try the fix permissions trick, and then get back--probably tomorrow though so I can report on a full charge.
[Samsung Galaxy S (4G Model)] bhundven:
Ok,

I was getting frustrated with this reboot issue, and turned on function tracing in the kernel. I started noticing this wakeup routine constantly getting running this pid that was rild.

I started watching the radio with the usb unplugged, and rild was keeping the phone from suspending. WTF

So I made this change to use the radio like all the other phones:

diff --git a/system.prop b/system.prop
index 00e8374..2bbb3ed 100644
--- a/system.prop
+++ b/system.prop
@@ -2,9 +2,7 @@
# system.prop for smdkc110
#

-rild.libpath=/system/lib/librilswitch.so
-rilswitch.vendorlibpath=/system/lib/libsec-ril.so
-rilswitch.ganlibpath=/system/lib/libganril.so
+rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0

ro.sf.lcd_density=240

Flashed and started the trace again. Modem came up... turned off the screen... started to enter suspend, no more wakups... phone reboots.

:sigh:

So something is seriously wrong with power management or wakelocks on this phone and I'm starting to compare the froyo kernel sources (KD1) vs gb sources (KJ6), because even stock kj6 source has this problem.

I was hoping this was an issue with rild or libril-sec.so so I could get the evidence over to samsung support, but now it's back to comparing source.
[Samsung Galaxy S (4G Model)] bhundven:
Alrighty... I started all over from the kj6 source drop and cherry-pick'ed mtd, wifi, and aries-vibrator.

running this on my phone now. no reboots. suspend is working everything else seems happy. check out the initial branch on my github: https://github.com/bhundven

I'll have a new build up in a half hour.
[Samsung Galaxy S (4G Model)] bhundven:
Taking a little longer then I thought.

I decided to cleanly add in each feature that was already enabled, so that if we have problems, you can always checkout(revert) to a specific change.

This should help out with the community effort a bit. But everything that is in the branch now, will get renamed to gingerbread. The current gingerbread will be moved to gingerbread-mtd-old. In case we want other things from that branch to test.

A little trim here. A tiny cut there. pull the edges together and you get 33 commits verses the 94 commits in the old gingerbread branch (on this day, at this time of writing). On the other hand... you get all the crappy compiler warnings and original samsung code.

Well clean up that cruft later. For now, the goal is stability. So far, so good (from my initial once over). My phone is much cooler (not as hot). But I don't see the phone going into suspend in spare parts (battery history ->

CPU Usage

->

Since last unplugged

- suspend - Starts: 0)

If you want to provide logs, lets make this easier.

If you can reproduce something, press vol+ and vol-, then press the power button and let go of all the keys (if the phone did not reboot). Wait 10-15 minutes. If the phone did reboot, no need to do the three button salute. Just send the stuff in /data/system/dropbox. Otherwise, try wiping the dropbox clean "rm -rf /data/system/dropbox/*" then try reproducing the problem again, so we don't get your old logs. Also, I don't want your IMEI or IMSI or other personal information (like txt messages or your xda username and password that gets sent by a notify process in the logs in CLEAR TEXT(!?!?)).

If you can not reproduce a problem, try rebooting and fixing permissions in the recovery's advanced menu, then just reboot. Then try again. If it goes away, it was probably a permissions issue (everyone should try this before trying to reproduce a problem).

OP will update after I get some more testing done.
[Samsung Galaxy S (4G Model)] Beastmode:
Thanks for the work and update on what's going on bhund :)

if you ain't first you're last :)
[Samsung Galaxy S (4G Model)] bhundven:
yw.

fyi... the branch moving is done. (meaning: gingerbread on teamacid is the 'reset' kernel.)
[Samsung Galaxy S (4G Model)] Fluidification:
does the suspend issue mean that the phone isn't sleeping even though the screen is off?
[Samsung Galaxy S (4G Model)] Theraze:
With R6, after the fix permissions, with Wifi and data on, overnight (screen off, phone in idle state, but still set to autosync email/gmail), battery went down 9% in 11 hours 17 minutes. Stock battery. So R6 should at least have the battery life needed for basic use.

Since the overnight got R7 released though, time to download, flash, and fix permissions. :)
[Samsung Galaxy S (4G Model)] Juls317:
Has anyone else had issues using the quick boot app? I know that the “reboot to recovery” option doesn't work, but the app doesn't seem to either
[Samsung Galaxy S (4G Model)] turtlepa:
This was answered a few posts/pages back
[Samsung Galaxy S (4G Model)] Juls317:
I'll double check then

By the way, no reboots and not too bad of battery life either on R5 as long as I have data off when not using it
[Samsung Galaxy S (4G Model)] bhundven:
Awh... come-on... you don't remember my motto... and you hang out in irc?!?

read the op? :D :cool:
[Samsung Galaxy S (4G Model)] Juls317:
Haha sorry! I did but I suppose my CM7 excitement overcame my reading ability
[Samsung Galaxy S (4G Model)] bhundven:
OP updated with simpler instructions for upgrading cm7 from cm7.

Enjoy :)
[Samsung Galaxy S (4G Model)] xaocon:
All of the OP correct? Specify the GPS not working?
[Samsung Galaxy S (4G Model)] Theraze:
Yes, GPS still doesn't work. It hasn't worked for any of the builds yet. Brian will update when it does.

Update on R7... the wakelock bug fixed in R6 (before the source reset) is back.

Details for 4h49m on battery:

Settings->Battery Use:

37% cell standby

24% phone idle

15% display

11% wi-fi

5% game

4% gps test app

2% android os

Spare parts->Battery history->Other usage->Since last unplugged:

Running: 93.2%

Screen on: 34.4%

Wifi On: 29.3%

Wifi Running: 29.3%

Clicking on Running for time: 4h30m not sleeping.

Basically, something makes it sleep, so that's better than R5, but it wasn't running anywhere near as efficiently as R6 did.

Edit: Oh, and since I forgot to say it earlier, yes, I did Fix permissions after flashing. As per the (now) official directions, I did that after installing the zip, but before the reboot to OS. I guess I'll fix permissions again and see if that fixes it... if so, we might need to let it soak, THEN fix permissions. I'll post in several hours if that seems to have fixed it.
[Samsung Galaxy S (4G Model)] hechoen:
Bryan, Fb, m4x, and everyone else working on this

Nice work guys. I finally folded like an accordian and flashed this. I told myself I was gonna wait for a final, but you know how that goes. Everything so far is running great except for that quote from the OP. Yes I actually read it over and over and over. When I place a call as soon as the other person picks up I can't here them and they can't here me. Is that the call volume issue? So far I've wiped cache, dalvik and fixed perms. Still doing it. Am I missing something here? Any help would be great. Also I quick question about nands. Has anyone tried to nand back to this from cwm? What I was thinking is flash kernel, reboot recovery, wipe and restore? Thanks again guys. This thing is pretty sweet.
[Samsung Galaxy S (4G Model)] bhundven:
hampsterblade said he turned the volume all the way down then all the way back up. But maybe try muting then unmuting?
[Samsung Galaxy S (4G Model)] hechoen:
Volume all the way down then back up does the trick.
[Samsung Galaxy S (4G Model)] eollie:
That was also a issue on my old phone. Its a CM7 bug it was hit and miss on the phone it affected.
[Samsung Galaxy S (4G Model)] Juls317:
told you they weren't working
[Samsung Galaxy S (4G Model)] bhundven:
Thank you for letting me know.

I think it's because the OTA name is not SGH-T959V or galaxys4g it think's it's not supported (it's galaxys4gmtd). Or there is a problem with the version magic.

It's not that high on the priority scale, so hang out a while ;)

DSP is keeping me happy, and if my phone stayed stable, we could just start adding dvfs tuning controls (which may prove interesting).
[Samsung Galaxy S (4G Model)] Juls317:
i just wanted to make sure seeing as you said they should be working. it kinda sucks that tegrak isn't working, cuz that's what i use to uv for battery life
[Samsung Galaxy S (4G Model)] Theraze:
After running another Fix permissions, 4 hours after following OP directions... same basic (fast drain) behaviour on R7.

Details for 4h55m on battery. From 67% to 35% with:

Settings->Battery use:

Cell standby - 32%

Wi-Fi - 31%

Phone idle - 27%

Display - 5% (turned it back down to minimum from the default settings)

Android OS - 2%

Android System - 2%

Spare parts->Battery history->Other usage since last unplugged:

Running - 23.9%

Screen on - 14.6%

Wifi On - 97.2%

Wifi Running - 97.2%

So it does get to sleep sometimes, but drain is still fast. I think I'm going to flash the R6 kernel for now and see if that gets it minimal again.
[Samsung Galaxy S (4G Model)] 7TimesCursed:
Bryan, I'm on the April 19th build. Its been 23 hours since I flashed and I have not had ANY reboots.

The battery is at 40% using juice defender.

Looking in spare parts, suspend is working ok. "Running 20%"
[Samsung Galaxy S (4G Model)] bhundven:
Hmm

That is interesting. On that same battery history page, you see a screen like this(?):

CPU usage details for suspend:

User time:0s
System time:13s
Total time:13s
Starts:0

I'm curious to know if starts means how many times 'suspend was successful' or 'how many times it's left suspend'? I guess the question is rhetorical, as we could just look at SpareParts and find out.

When I look at dmesg:

adb shell
dmesg > /data/dmesg
exit
adb pull /data/dmesg
adb shell rm /data/dmesg
$EDITOR dmesg

I see timing information on the left in a medium resolution. then on the right I'm looking at how quickly the phone has been flipping between suspend and resume. Not always making it into suspend. Either by unsuccessfully suspending power.0 (which isn't always reproduceable) or just instantly returning to resume for no apparent reason.

The major change to make the phone cooler running was I switched the ril library paths. Less errors about "unknown broadcast" cruft in 'logcat -b radio'. Less radio chatter, more chance of sleeping... (which sounds good right now ;) )

So as much as I think the kernel has some problem (no doubt) so does the cm rom and file permissions/ownership problems that make some things not work correctly. Or just being named wrong or whatever. So take issues with a grain of salt.

If you figure something out; I like help!
[Samsung Galaxy S (4G Model)] hampsterblade:
Oh God. So f***ing amazing. Last night I was down because data wasn't working at all. Finally did a fix permissions through rom manager. Not only did it fix that, but like most nights my phone fell off the charger. But unlike most nights it didn't even fall 1% over the hour! The phone suspended!!!

Using R7.
[Samsung Galaxy S (4G Model)] hechoen:
Got voodoo to work by editing the build.prop to show SGH-T959V. Tegrak is still returning the same error that juls originally posted. Battery life seems fine. And the phone does appear to be sleeping properly. No complaints.
[Samsung Galaxy S (4G Model)] Juls317:
Thanks for the tip! It worked for me so my voodoo sound goodness is back! Although, same result with tegrak
[Samsung Galaxy S (4G Model)] Fluidification:
My performance report.

R7 is too buggy.

R6 is very stable.

Battery lasts 15+ hours,moderate use.

No in call issues with volume.

When moving app to SD in manage apps, it fails the first time, then it works.
[Samsung Galaxy S (4G Model)] mecha2012:
Thank you so much for this man keep up the good work!!!
[Samsung Galaxy S (4G Model)] Juls317:
What about R7 is buggy? I haven't had any issues
[Samsung Galaxy S (4G Model)] Fluidification:
I just didn't keep it on long enough. I saw too many bad reports.

But is battery life better?

And what's the sustain issue?
[Samsung Galaxy S (4G Model)] bhundven:
So instead of saying you tried it and giving a bad report... then asking what the problems are. Why not just try it. If you have problems, post logs.

I dont want "it doesn't work" or "it has battery issues" kinds of comments. Just logs.

If you cant do that. Don't post.
[Samsung Galaxy S (4G Model)] astaccz:
Ive had no serious issues with R7. Two minor things I have noticed. The Data indicators switch from 3g to H. 3g when Data is inactive but lets say if it is loading a webpage. It goes to H then when webpage finishes loading it goes back to 3g. Any ideas? Also in the Browser, with default User Agent, I can't load any webpages on data. It says this User Agent is not allowed. But when I switch to iPhone user agent, they load fine on data.
[Samsung Galaxy S (4G Model)] Fluidification:
Bryan, you could have said that nicer, other than that, I´ll trust you and flash r7. But still, you posted that the system doesn't suspend. So what´s that?

---------- Post added at 06:58 PM ---------- Previous post was at 06:56 PM ----------

by the way, here is a good report.

e internet is faster than e on KJ6 stock.
[Samsung Galaxy S (4G Model)] FBis251:
You know, I finally decided to remove you from my ignore list on XDA but after this post, you're going back on it.
[Samsung Galaxy S (4G Model)] Fluidification:
Dude, I don't want to be the bad guy around here. Plz forgive me if i offended Bryan.

But, here is another thing. After 2 reboots, my battery starts draining fasts, and i need to fix permissions, but it seems to stick better if i do it through Rom Manager.
[Samsung Galaxy S (4G Model)] FBis251:
bhundven, finally got finished customizing my cm7 install. So far I'm loving it. Even got some custom lockscreens set up.

Thanks for the work, and also huge thanks to Max and hampster.
[Samsung Galaxy S (4G Model)] m4xm4n:
oh sweet! I did something, apparently.
[Samsung Galaxy S (4G Model)] Fluidification:
You are the one who keeps making changes many changes in github.

Of course you did something!
[Samsung Galaxy S (4G Model)] Kyndig66:
@FBis251 I'm having trouble getting CM7 on my phone so I wasn't able to try out your zip. There are a lot of things involved that I have no experience with so I have a lot more reading/searching to do to get it going. Just wanted to give you a heads-up. Working on installing a Linux VM right now to see if that will make it easier. :)
[Samsung Galaxy S (4G Model)] FBis251:
EDIT

Removed. The CWM zips aren't ready for prime time yet apparently. I'll post them once I have verified a good, working method.
[Samsung Galaxy S (4G Model)] hechoen:
FB

You just made a whole bunch of people real happy. Be prepared for the onslaught. lol Nice work and thanks.
[Samsung Galaxy S (4G Model)] FBis251:
It ain't isn't not no working yet!!! Don't flash them. I went into a reboot to recovery loop. I think I know how to fix it, but I'll repost everything once I make sure it works 100% of the time.
[Samsung Galaxy S (4G Model)] Beastmode:
damn the time i forget to refresh and see what's new u put links n take em down :P
[Samsung Galaxy S (4G Model)] FBis251:
Okay, finally got around to making the CWM zips for making the installs easier on the users.

INSTRUCTIONS

Download both zip files, plus the latest update.zip and boot.img from the downloads post on this thread

Transfer all 3 zips to your phone

Reboot to recovery (RED CWM)

Do a nandroid backup of your current ROM

Flash cm7-efs-backup.zip

Put your phone into download mode

Flash the latest boot.img from bryan's OP using HEIMDALL

You should now be in the BLUE CWM menu

Do a factory reset (Main Menu > wipe data/factory reset, you might get a format volume error. It's normal, continue)

Format and mount /system (Main Menu > format /system & mount /system)

Flash cm7-efs-restore.zip

Flash the cm7 rom zip you downloaded, and the gapps zip if you want

Reboot and enjoy CM7.

DOWNLOADS

cm7-efs-backup.zip

cm7-efs-restore.zip

EXPLANATION

The problem was that the phone won't like it if you flash the kernel via CWM, so you have to do it via heimdall or it won't work for you.

For the curious ones. I just made a few scripts that get run through CWM that do a lot of the steps in Bryan's OP for you. It'll do all the efs backup and restore for you, which will make flashing CM7 a little more trivial
[Samsung Galaxy S (4G Model)] TunedFish:
Where's the link to the gapps? The OP says it's at the bottom of the first page but I don't see them.
[Samsung Galaxy S (4G Model)] hechoen:
Here you go.

http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
[Samsung Galaxy S (4G Model)] cybok0:
Sorry wrong place
[Samsung Galaxy S (4G Model)] 7TimesCursed:
I can't get FB's padded modems to stick. It seems like they flash correctly in CWM but when I boot, I'm still on KJ6.

This is on the 4/19/12 build.

Any clues?
[Samsung Galaxy S (4G Model)] hechoen:
Team

I am running the latest build and kernel. Woke up this morning to a very unresponsive phone. Laggy as I've ever seen it. It was running fine when I plugged it into to go to bed. I ran the old quad to check and it's not even hitting 1000. I know I can clear and fix perms and it will most likely fix the issue but I would like to get you some logs. Do you want a whole system dump or do you want it narrowed down? I'll be using ABD to get the logs.
[Samsung Galaxy S (4G Model)] bhundven:
No, just fix permissions. If you still have problems, then send logs.
[Samsung Galaxy S (4G Model)] bhundven:
The modems just get copied to /radio. try just adb pushing the file to /radio. make sure /radio is mounted.
[Samsung Galaxy S (4G Model)] Fluidification:
Like I said, permissions seem to break after a few reboots.
[Samsung Galaxy S (4G Model)] adobrakic:
@ FB -- I'm confused about your instructions. I got to step 7; have heimdall open and under "utilities," it says "Device detected," but I'm not sure where to go from here. Everything but the browse button under the 'Flash' tab is grayed out. Any help?
[Samsung Galaxy S (4G Model)] TunedFish:
From the Heimdall README.txt :

5. Before you can chose which partitions you want to flash with particular

files you MUST first select a PIT file. To do this click the "Browse"

button in the "PIT" section. This will open a dialogue allowing you to

navigate to and select a valid PIT (.pit) file.

If you do not already have a valid PIT file stored on your computer you

can download your device's PIT file from the "Utilities" tab.

after that, you should be able to flash the Kernel to the Kernel Partition from the img file.
[Samsung Galaxy S (4G Model)] Juls317:
I've talked to bryan about downloading the pit from the phone and he suggested just using the one in the KG4 leak. I uploaded it to media fire so you don't have to download the whole leak. Link is in the guide in my sig
[Samsung Galaxy S (4G Model)] Fluidification:
honestly, using the command line heimdall is easier because it doesn't require you to add another pit thus saving a step.

(Mac)

cd /users/yourusername/Applications

heimdall flash --kernel draganddropboot.imghere

(Windows)

cd pathtoyourheimdall.exe(not heimdall-frontend)

heimdall flash --kernel draganddropboot.imghere
[Samsung Galaxy S (4G Model)] hechoen:
Holy crap you can drag and drop in command prompt. Amazing. I never new that. Thanks
[Samsung Galaxy S (4G Model)] Juls317:
You don't have to cd into it
[Samsung Galaxy S (4G Model)] adobrakic:
Worked like a charm. Thank you.
[Samsung Galaxy S (4G Model)] Fluidification:
I know, but it saves a drag and drop step. And if you make a mistake once, you don't have to enter it again(or hit the up key)! :P
[Samsung Galaxy S (4G Model)] braski:
Hey bryan finally got the balls flash this. Wanted to say thanx also I noticed in the OP you said you have issues with 3g vs 4g. I don't think you do cyanogenmod views umts as 3g where as stock views it as 4g. Most of the time we are on umts unless we need hspa+ during downloads or high data transfers. Thanx again love the ROM :)
[Samsung Galaxy S (4G Model)] bhundven:
btw, I'm broke as hell. I added my donation link to paypal.

I'm not gonna force anything, but if you want to help me eat and drink coffee to keep this progress going, any help would be very appreciated!
[Samsung Galaxy S (4G Model)] bhundven:
Sure! PM me!
[Samsung Galaxy S (4G Model)] vgcraze:
When you say that we can Heimdall back to BML, can I assume this works for Odin as well?

Btw, congrats on the progress and thanks for ask the hard work!
[Samsung Galaxy S (4G Model)] g4ry12:
Donated $10. Hope it helps. Thank you for your work!

On a side note, you may want to copy that quote above into the OP. Next to the download link, when that will be up. That would probably get you more donations than a post on a 3rd page. Just trying to help. Keep it up!
[Samsung Galaxy S (4G Model)] hechoen:
Bryan,

Can't have you going without coffee. Donation sent.
[Samsung Galaxy S (4G Model)] bhundven:
Yes, if you flash the pit.