yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] newter55:
You still have to do the jg8 trick for 850. Working fine here.
[Captivate Android Development] p4ranoid4ndroid:
I feel flames but..

Is gps working? If so has it gotten any better?
[Captivate Android Development] newter55:
Thanks glitter....was just about to set my search button as home key to get by. Also, will this update include any other promised placebo effect optimizations? ;)
[Captivate Android Development] newter55:
hmmm...i will cut you some slack...:D states specifically in op of cyanogen thread that gps is not working so i have not tested. Perhaps someone else wants to be the guinea pig and see what exactly "kill" means:

from http://xdaforums.com/showthread.php?t=842159

16. Do not use GPS. It'll kill your phone.
[Captivate Android Development] sdotbrucato:
Do you mind going into detail about the"trick". I pushed jg8 but nothing got fixed..
[Captivate Android Development] p4ranoid4ndroid:
Lol I did jump the gun on this. Just read that thread ad was coming back here to edit my post that I had found my answer. /doh!
[Captivate Android Development] newter55:
Any time you want to use an i9000 modem, you need to flash to stock, boot, flash jg8 modem, boot, then proceed to whatever you want to do. This will magically enable the 850 band which cannot be done using the dialer codes to change band settings no matter what you try. The settings there seem to have no effect.

edit: in case anyone else needs it here is the modem View attachment jg8_modem.zip
[Captivate Android Development] glitterballs:
Yeah, I just want to make sure the nonspecific items are stable before I push them out, but I'm already planning some Vague Generalizations as well. :D
[Captivate Android Development] topcatcher:
Really wonderful. May it go to perfect sooner.....
[Captivate Android Development] tjsooley:
Where did you dl the rom from?
[Captivate Android Development] jhnstn00:
Is JM8 the eclair one? and Is this necessary to get to jpm?

gonna add flash jf6 then jg8 modem prior to all the above and try.
[Captivate Android Development] warri:
This looks very awesome..can't wait till we have captivate froyo source code...things will be alot easier
[Captivate Android Development] daraj:
Thata a lot of work to get this thing working!!
[Captivate Android Development] Squeak22:
Once you do it once, you can just update cyanogen builds when they are released instead of having to do it all from scratch again.
[Captivate Android Development] BL4zD:
The instructions on cyanogen forums for compiling from source are so screwy that I pretty much gave up. The files don't match the instructions, the diff patch is from the older source, the paths are bonkers, and the instructions are different from the wiki are different from anything I google, so I dunno...if anyone has tried to compile from the most recent way things are set up I could use a few pointers.
[Captivate Android Development] TechTony13:
Just curious if there is any work being done on the charging death with the OC/UV kernel. I read something in here about someone supposedly having it fixed, and i would really like the UV my phone without it dying while charging.

PS: Thanks for the work so far!
[Captivate Android Development] TheEscapist:
I read in the jl3 modem thread that gb was working on a fix. Of course, this is affecting everyone on a i9000 kernel, so I'm sure someone is working on it.

Also, just do what I do, and hit stay awake while charging in applications > development, then turn your screen down. It's ghetto as ****, but it works. :p
[Captivate Android Development] glitterballs:
I've said this roughly a bajillion times, but I'll mention once more.

It happens less frequently while charging by USB than while charging by the wall outlet. I've left it in plugged in overnight charging via USB w/o it dying. Not to say that USB is perfect because I've still seen it happen, it just happens less frequently.

No one using the code on an i9000, as far as we can tell, has the problem. Everyone using i9000 source for Captivate and Vibrant kernels has had the same issue. If anyone knows someone from Canada or anyone with an i9000m specifically, and they wouldn't mind helping us out, have them get in contact with me. (Or just have them install any of the OC/UV kernels and see if their phone crashes after a full charge and then contact me.)

It seems as though it might be due to a minor hardware difference. Newer Captivates also reportedly don't have this problem. And when the phone dies, it briefly completely loses power. It's not an issue of undervolting too much and getting a system freeze. The phone behaves as if you completely pulled the battery and then put it right back in. Obviously no one has had a problem with their phone dying while on battery power right? (At least that wasn't attributable to undervolting too much.) So everything is working except for when we use these kernels and our batteries are full or very close to full. I have a couple theories on why this might be happening. DG is working on some fixes. The code is out there if anyone wants to have a look at it and see what's going wrong. Eugene decided to just undervolt all frequencies, which is one solution. We're able to undervolt very aggresively when everything is working, so there is a lot of room for potential battery savings.

That said, I have two kernels compiled that I'm testing....well, I'm testing one and hoping I won't have to test the second. So it shouldn't be too long, hopefully sometime tomorrow. We all do this in our spare time, so when we get around to it is when we get around to it.

@blazed - There are really only like six or seven files to patch, so you can always do it by hand. That patch has been up there for days, it would take five or then minutes to patch all those files by hand. I should probably post everything on github, but I'm not by any means being closed about this, on top of other things I'm working on. If you've cloned the repository, don't point to the initramfs in ~/system, pull initramfs from github and point your config to that initramfs.
[Captivate Android Development] BL4zD:
Yeah I started to patch them all by hand when you first posted the diff, but the SGS files are all over the place and it got to the point where it wasn't worth the hassle to track what they were trying to do.

It's not your patch that's the issue, it's the fact that the devs working on source aren't being consistent in how they handle their pathing and files. So it's pointless to open up the other files and figure out what is what since the files between the Vibrant/Galaxy/Captivate are all different. It's a mess...imo.
[Captivate Android Development] Smallsmx3:
I'm glad to see that some progress is being made on the ocuv kernel to fix the sleep death.......on another note the jl3 modem has really helped improve battery life drastically. My cell standby is still high but the battery drain is not as bad. Also I'm getting an H icon in data where I wasn't getting it before with jk3...odd?
[Captivate Android Development] Sebring5:
I'm using JK3 and I have the H icon.
[Captivate Android Development] Smallsmx3:
Everytime I try to install the 12-8 kernels it fails at line four...anyone have any ideas?
[Captivate Android Development] gtg465x:
Anyone try using this kernel to throw together a Nexus S 2.3 port? I know devs in other sections were using CM kernels to successfully boot the 2.3 emulator image last week. I threw together a package by basically copying over all of the apps/framework/libs/drivers/etc. from a Nexus S system dump on top of the CyanogenMod SGS BETA3 system package, but I didn't try flashing yet because I need my phone right now and don't feel like having to set everything up again.
[Captivate Android Development] darkfalz:
If you were to provide a link to your package, I'd be more than willing to flash it. Axura is absolutely devouring my battery for whatever reason, so I had planned on flashing something new today anyways. :-)
[Captivate Android Development] gtg465x:
Cool, I can post it up when I get home around 6 today. There's a 95% chance it won't boot, but if you plan on flashing something else anyways I guess that won't matter to you.
[Captivate Android Development] TheEscapist:
You get a symlink error, right? Delete the two bln libs in /system/lib/hw. Should be something like liblights.s5pc110.so and lights.s5pc110.so. Worked for me.
[Captivate Android Development] ademejia:
count me in to flash too.
[Captivate Android Development] gtg465x:
PMed you guys.
[Captivate Android Development] darkfalz:
Ok. I'll try it out in a little while. I'm entertaining my 2 year old at the moment.

To avoid others trying, perhaps pm me the instructions?
[Captivate Android Development] ademejia:
ill try it asap connection at work blows:mad:
[Captivate Android Development] aqtrans:
http://forum.cyanogenmod.com/topic/...-version-beta3/page__view__findpost__p__92081

Looks like we got a new Nightly Build to try out! No idea if this requires a new kernel or not, but nice to see a new build :D
[Captivate Android Development] ademejia:
oh wow i guess i'll be busy flashing
[Captivate Android Development] TheEscapist:
Just an idea, but instead of using this kernel, couldn't we use the nexus s kernel with a modified version of codeworkx's patch? Obviously it'll be different in some ways, but it'll give us some guifance, at least.
[Captivate Android Development] fatttire:
I really want to know how well that nexus s GPS config file swap works (12-17-2010 build).

RE: escapist

Since Cyanogen mod is based on a froyo ROM, no way a nexus s kernel could be added currently
[Captivate Android Development] Athailias:
I see GB is on the forum... and I just finished my finals so I am sure he is done too... I wonder if he is making a new kernel ;)
[Captivate Android Development] gtg465x:
Supercurio and others are working on a proper port with the Nexus S kernel. I'm sure they will post something if they get it working.
[Captivate Android Development] glitterballs:
You guys should be able to d/l the new beta w/o a new kernel. I'll put one out, but in the mean time, not much has changed with the kernel...couple lines in the initramfs is all I think. I suppose I could do it now while I'm waiting for repo sync to finish...

Did...um...whathisface get that thing with the zip straightened out? Smallsx3 or something like that..
[Captivate Android Development] TheEscapist:
You misunderstand. They are saying to use this kernel with the Nexus S rom just in case it happens to boot. I'm saying to use the Nexus S kernel, patched similarly to this kernel, with the Nexus S rom, just to see if it boots. That way, we actually have a 2.3 kernel with a 2.3 rom.

Awesome, gonna be flashing tonight. If I'm going to be charging my phone tonight any way, do I really have to wait for a full charge? :rolleyes:

As long as he follows my instructions, probably. It worked for me, I was having the same issue, flashing the OC/UV kernel over the non OC/UV. I just chmod'd and deleted them, and it fixed it.
[Captivate Android Development] Smallsmx3:
I actually had flashed another rom.......but ill prob flash the new nightly build tomorrow....I wanted to use a cappy 2.2 kernel modem and rom (jj4 w voodoo) to see how my signal was...im having issues at work where I get crappy service......I've been thinking its the i9000 modem and roms im using and today just proved it.....I was losing about 10% an hour on cm but only at work. On jj4 im only losing about 4. And I can actually access the internet and send messages where I couldn't on cm w 6.1. Is anyone else having these issues in bad service areas?
[Captivate Android Development] TheEscapist:
Not at all. With uv, I lose 1-2% an hour, in my cinderblock high school.:rolleyes: What modem are you using? I'm finding the TL3(?) modem fantastic.
[Captivate Android Development] Smallsmx3:
Im using tl3 as well....I've used quite a few different i9000 roms and its always the same. Cell standby is at 60% and I hardly get service.... I switch to a captivate rom and no issues.....I knew something was wrong when all my customers are using their iphones in the dead spots in the building. Don't get me wrong I was getting about 3% drain outside of work with tl3 and cm6 but once I got in the building I couldn't get through a shift.
[Captivate Android Development] aqtrans:
Don't know if anyone else experienced this issue with the new Nightly build, but I had the same Superuser issue that came up before. /system was mounted with nosuid for me, had to run the remount command to get Superuser working at all.
[Captivate Android Development] TheEscapist:
No issues here. You using the beta3 kernel? Maybe it's an issue in their new kernel that's not in the b3.

Or maybe you just got unlucky and need to reflash.:rolleyes:
[Captivate Android Development] aqtrans:
Yeah I was using the reoriented kernel, I usually strip the kernel out of any builds before flashing. Guess it was a product of the hit-or-miss Nandroid restore functionality.Or maybe my phone just really hates me...I was trying to go back and forth between my Beta3 backup and the nightly, so I somehow got a mish-mash of them, with a bugged system mount :(

I had to install the Nightly, wipe data, then restore only my /data and /cache from a previous backup. Seems to be going good now.
[Captivate Android Development] Smallsmx3:
Anyone using this with the jj4 modem? If so any issues? Hows battery life? I stopped using this rom because of the battery life
[Captivate Android Development] zerojay:
Anyone else having a problem with Bluetooth when the screen turns off? If I'm using a music or podcasting app and listening to a podcast or music through Bluetooth to my wireless headphones, if the screen turns off the sound stops completely between 1 and 5 seconds after. As soon as I hit the power key to bring up the lock screen, the sound kicks back in through the headphones.

Maybe there's some option that I'm missing here.
[Captivate Android Development] spiritssight:
CMW without overclocking

Hello All,

I was wondering if there will be a CMW bundle instead of all the different files needing to be done at different times? I ask this as I don't use windows system and I would like to update my CM verison to the latest files and modem but I don't have a windows system in my house any more as my gf system is not linux also.

I am loving what has been done so far and look forward to having 2.3 on our devices :-)

Have your self a wonderful holiday!

God Bless,

Christopher
[Captivate Android Development] zerojay:
You can install beta 3 using just CWM right now. The files are in the OP.
[Captivate Android Development] TheEscapist:
You can do it all through Clockwork, just not all at once. Flash the initkernel, then either Beta3 or the latest nightly, then your choice of Beta3 kernel from the OP. Reboot, flash gapps, and enjoy. :)
[Captivate Android Development] NiXXeD:
I saw a post in the CM forums seeming to indicate they were running without a reorient kernel. Is their "universal kernel" working partially?
[Captivate Android Development] glitterballs:
I tried it out. JJ4 does work, but the battery drain was redic. Although, different people experience different things with the modems (as was evidenced in my JL3 post), so, by all means, try it out and see if it works better for you.

There won't be, and there are a few reasons for that. For one, I want it to be clear to everyone that codeworkx and others are the geniuses behind all this. People around here have a tendency not to read much, and if I had a post with a full ROM, people might start to credit me instead of them. Secondly, some people like the OC/UV kernels, some don't; some like one modem, some like another. It's much easier to let people decide what modem & kernel they want to use than it would be to package up every possible combination of modem and kernel. Third, it takes probably all of 30 seconds to flash this stuff with CWM. You don't have to have any specific OS to load these onto your phone, just mount as USB, copy, and reboot to recovery. If thirty seconds, or hell, even if it was five minutes which I'm pretty sure it isn't, is too much time, either flash less or become more patient. :)
[Captivate Android Development] Sebring5:
Yes, it was my post you saw and I am running CM6.1 nightly builds without the reorient kernel. Here is a list of what I have to do to run without the reorient kernel:

1-turn screen rotation off and use portrait only

2-select speaker to hear when I am using the phone

3-selecting always play on speaker option in CyanogenMod settings/sound to hear to ringtones, alerts and notifications

4-home button does not work, use the back button to get home
[Captivate Android Development] glitterballs:
Just bumping this so anyone else still running CM6.1 sees there is an updated kernel with the charge-death fixes (and a couple other minor things).
[Captivate Android Development] TheEscapist:
Hasn't it been dropped though? I'd be running it if I knew it was still being updated, and if I didn't have Gingerbread.
[Captivate Android Development] ademejia:
new nightly build

nightly build avalible 1/5/2011 just wanna share the info.
[Captivate Android Development] glitterballs:
Doesn't look like anything kernel related changed, so the 12/27 kernel should still be good.
[Captivate Android Development] tjsooley:
What works now that we have 3.5?
[Captivate Android Development] Kaik541:
Using it right now and the only "issue" I've noticed is that the latest nightly zip doesn't actually work (you have to push the files manually) and you need to modify vold.fstab if you don't have an external micro sd card. Besides that, almost all of the functionality is there. Look at the google code bug tracker to see what doesn't work.
[Captivate Android Development] tjsooley:
does voice recording and 2g3g toggle work now?
[Captivate Android Development] TheEscapist:
Latest beta is just an update to CM 6.1.1. A bunch of stuff from the nexus s got put in.
[Captivate Android Development] tjsooley:
but does voice recording and 2g3g toggle work.

i would love to run this rom but need the above features to work.

I have looked at the bug reporting but have not found any information.
[Captivate Android Development] Kaik541:
like I said, you should read the google code issue tracker page. the 12/17 nightly I'm running doesn't have 2G/3G toggle working (hitting it just causes data to cut out entirely, tapping it again restores it to auto) and voice recording turns my voice into the predator's.

seeing how both of these issues are still not marked as "solved" or "fixed" on the tracker, there's really no need to ask. Issue Tracker and the specific 2G/3G Toggle and, lastly, the audio recording bug. Most likely these won't be fixed in 6.1 because they've moved on to 7.0 with the Nexus S sources
[Captivate Android Development] tjsooley:
is there a issue tracker for cm 7?
[Captivate Android Development] Kaik541:
http://twitter.com/codeworkx/status/23163619977990144

right now, their focus is just making sure things are stable. for example, they don't know the long term effects of using the MTD driver supplied with the Nexus S sources. your best bet is to find a channel on IRC that codeworkx and coolya are in OR just follow them on twitter. until there's an alpha, there likely won't be a bug tracker.

edit: and if there is, it probably isn't public just yet
[Captivate Android Development] ronandi:
Anyway a reoriented kernel can be made for CM7? Right now theres no initramfs for the captivate and the i9000 one is being used.

A user that tried it said:

Captivate kernel + Captivate CM7 = Broken SD cards & no screen rotation.

Captivate kernel + i9000 CM7 = Working SD cards & no screen rotation.

i9000 kernel + i9000 CM7 = Working SD cards & screen rotation, but with the standard rotation problems with i9000 kernels.

So it sounds like a reoriented + i9000 CM7 would work perfectly.

http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/

https://github.com/coolya/android/
[Captivate Android Development] TheEscapist:
Sent GB a PM about it, hopefully he does it. :D

Either way, I'm downloading the source, gonna compile it and just run the i9000 kernel. Orientation can just be turned off, and I'm pretty sure Captivate button support was baked in from the original tech demo by xcaliburinhand.
[Captivate Android Development] cchant:
I was able to compile the i9000 source and kernel for CM7 but I am having issues flashing them to my captivate. I was able to output to a OTA package and a ROM but have not been able to flash by Clockwork recovery. Any pointers on what I am doing wrong?
[Captivate Android Development] TheEscapist:
Supposedly, OTA has been broken since early CM6 releases. There is instructions somewhere on the cyanogenmod forums. You got to do something like tar up the kernel, and use nandroid to restore the system.img. There is also issues with the different partitions, so look out for that.
[Captivate Android Development] cchant:
Thanks. I have the kernel tar'd for flashing. I tried to restore the system.img via nandroid but keep getting MD5 checksum not matching errors. This is where I have been stuck and am unsure what I am missing.
[Captivate Android Development] TheEscapist:
Yeah, I have no idea. Good luck though, I'd like to be able to install this as well.
[Captivate Android Development] TheEscapist:
Okay, so how did you compile the kernel? I have the i9000 build, but i don't have the kernel-aries directory from the CM6.1 instructions, and I'm not sure how to build the kernel. Is it the scripts under kernel/samsung/2.6.35?
[Captivate Android Development] cchant:
Try the following:

copy device/samsung/galaxys/initramfs to device/samsung/captivate/initramfs

Compile the kernel with following commands in terminal:

cd ~/android/system/kernel/samsung/2.6.35

./build_captivate.sh clean

./build_captivate.sh

You can find the compiled zImage kernel in arch/arm/boot. I still haven't been able to figure out the md5 check sum issues but I have an idea I'm going to try tomorrow.

If you happen to figure out how to flash it before I do feel free to share :-)
[Captivate Android Development] TheEscapist:
To restore the system.img, did you just put it in a folder in the clockworkmod folder? Cause every other folder in there has a nadroid.md5 file, plus the *.img files. I'm betting you need to make that md5 file some how before it will flash. Also, to create the flashable tar, you just did tar -cf <archive> zImage?

PS: I'm scared as **** to flash this, so I'll probably wait until someone else has some sucess. Damn being a 16year old on minimum income. :(
[Captivate Android Development] cchant:
I created a nandroid.md5 file in terminal so I'm going to try to recover it in a minute. I'll let you know what happens.

EDIT

restoring the back up didn't work. Had to flash back to stock via ODIN. Going to try something else

As long as you have the 3 button combo to get in to recovery then you should be fine. There's always risk of course but that comes with the territory.
[Captivate Android Development] TheEscapist:
What happened, what kind of errors did you get?

And yeah I know. I just don't have the money right now to replace the phone. Once I get my Nexus in a few months, I'll be a lot more okay with experimenting. :rolleyes: I can at least help debug.
[Captivate Android Development] cchant:
I didn't get any errors. The phone just froze during the restore process. I let it sit for a few minutes but no progress was made so I just ODIN to stock.

The MD5 sums pass the check, it restores the boot image, and during restoring the system img is where it hangs.
[Captivate Android Development] TheEscapist:
Okay, well, thanks for trying. Maybe one of those guys who have had success will come in and help.
[Captivate Android Development] cchant:
Maybe. I've got a few hours to tinker with it so I'm going to research and try some other things