yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] .Candy:
So that means I can successfully install the Firebird kernel over CM7?

I'm in school now, in my comp sci class so I get to use my computer ;)

Anyway, I just got Gapps installed... for some reason it wasn't already installed even though I used the ./get_google_apps.sh or whatever the script is before I built...

Edit: Uhm... I just tried replacing the fonts in the /system/fonts directory, and now the bootanimation just repeats itself and never stops.
[Captivate Android Development] atinm:
Firebird: No, first you'll have to go back to stock using Odin One-Click. CM7 converts the filesystem to yaffs2 and the easiest way to get back to froyo is to flash back to stock and do whatever else you do. Firebird is just what I use, but froyo is your business - pick what you want.

Fonts: look in the dmesg output and/or logcat to figure out what is wrong and see if you can fix it. If you don't know what dmesg or logcat are, then you really shouldn't be using CM7 yet.
[Captivate Android Development] slifer315:
I used font changer from the market to change the system font and that worked just fine.
[Captivate Android Development] smokestack76:
I agree but with your instructions it will shed light on alot of the users that want to learn. You did a good job with those. I am sure we will see alot more users wanting to be a dev or even becoming a dev. So again. Nice one :D
[Captivate Android Development] .Candy:
Oh okay. Sorry, just got a little confused. And yaffs2? I thought one of the biggest things about Gingerbread was that it natively used EXT4.

I know what both dmesg and logcat are. Though tbh, I can't figure out what the issue was. I used Root Explorer to copy the files, so that could've been the issue... I'll try with ADB next time.
[Captivate Android Development] .Candy:
Okay bad news.

I've been trying to reboot into recovery or download using the key combos, and they worked before but not now. I wasn't too worried because I knew ADB worked and that the commands should work, right?

Well, when I use adb reboot download or recovery, it just reboots like normal without going into either recovery or download mode. So now there's no way for me to get into either.

Help? :(
[Captivate Android Development] atinm:
/data is ext4, system, cache, efs and datadata are yaffs2 in CM7. Samsung will most probably ship with RFS for non-Nexus S devices . . .
[Captivate Android Development] AJerman:
Well, forgive me if I'm wrong about any of this, I'm just now getting into the CM7 development (been busy with work and haven't done much Android development since when the Captivate first came out). From what I saw neither reboot recovery nor reboot download work, and I couldn't get into download mode manually either. I think I remember hearing that as a current issue, but recovery mode should work. Turn you phone off completely, then try to do the 3 button startup for recovery. You should be able to flash a different ROM from recovery if you need to fall back, then you'll get download mode back as well.
[Captivate Android Development] atinm:
adb reboot recovery and download will not work. The usual 3-button stuff should work though, that's what we use all the time.

For me:

Download mode - leave USB plugged in, hold the power and volume keys, let the phone light up and go dark two times while holding the keys, then after the second time it goes dark, just before it would light up again (its takes practice to get the timing right ;) ), let go the power button and it should be in download mode.

Recovery mode - unplug from USB, hold the power and volume keys, let the phone light up and go dark two times while holding the keys, then when it just starts to light up the third time (again, timing!), let go of all the buttons and it should go into Clockworkmod recovery after showing you the cyanogenmod bootlogo.
[Captivate Android Development] bobbylx:
I agree with this completely. I have been building this and installing for about 3 weeks now and loving it. I have worked with and taught Unix/Linux for the last 10 years or so, but never played with any Dev work. I have enough knowledge to build and do that stuff, and am using this experience to understand the Android OS in more depth.

Of course, I'm still a bit slow. Every time I start working on a known issue, someone on IRC announces they've fixed it. Still a good learning experience.

Most important thing. Have more than a beginner knowledge of your phone! And also, have and know about Linux. Try to solve problems yourself before asking in IRC, unless it's a really good one of course. Enjoy.
[Captivate Android Development] TheEscapist:
I find it's WAY easier just to turn your phone off, then hold down both volume buttons and plug in the usb. Throws you straight into download mode, and none of these timing difficulties. :p
[Captivate Android Development] atinm:
Wow! Did not know about this method - cool!
[Captivate Android Development] Scarchunk:
Synced and compiled last night. Flashed early this morning before work. I'm very impressed. I've been using all day without a single FC/reboot. Everything I've tried works.

I'm a network tech, but I tinker with code. I'm learning as I go, but maybe I'll get lucky and stumble across something useful...
[Captivate Android Development] nrgaway:
Do you need a 64 bit processor to compile sources?
[Captivate Android Development] Billabong81:
From everything I have read: yes. 95% certain on this, but that always means 5% chance I'm wrong (or 100% if you look at it that way!).
[Captivate Android Development] smithisize:
Yes, you need x64, I tried on x32 by mistake and it didn't work.

Downloaded all files from the repo, finally.

Kernel: Check

CM7: Nearly... Java problems. Checking Java integrity... Coming along nicely...

EDIT: Nearly compiles. Java issue SEEMS to be alleviated, however, here's what's up:

make: *** [out/target/common/obj/APPS/Tag_intermediates/classes-full-debug.jar] Error 41
[Captivate Android Development] SweetwaterBurns:
If you are using Ubuntu, make sure all the Java alternatives are set to the sun JDK and not icedtea. You could just uninstall all the open source Java stuff, as well. That fixed things for me.
[Captivate Android Development] AJerman:
I'm not so sure 64 bit is required myself. I have a 64 bit processor, but a 32 bit version of Linux, and it gave me the warning at the beginning about how 32 bit isn't supported, but it compiled everything just fine, so your mileage may vary I suppose.
[Captivate Android Development] Kaik541:
just so everyone knows, cyanogen is currently merging in 2.3.3 changes into mainline... which means a lot of stuff is possibly going to break (though how much is hard to say). any errors in building can likely be attributed to this for the next day or so
[Captivate Android Development] smithisize:
Well, I re-installed all the Java stuff. Then, I re-synced, and re-downloaded google apps. Not done compiling yet, but looking promising lol
[Captivate Android Development] vvaffles:
no its fine, i just did a re-sync and build as of 11:30, it seems OK. im on 2.3.3 now
[Captivate Android Development] Aztecbandit:
Hey guys. Just wanted to say thansk for all the work you guys are putting in. So how are your builds coming along?

Sent from my iDon"t care what u say its not an iPhone or a Droid, phone
[Captivate Android Development] Kaik541:
I was saying "if they try to build while everything is still being merged"... merge seems to be over as of now, so everything should be good (to be honest, they merged all that in much faster than I expected). and as said above, many people can confirm 2.3.3 works fine
[Captivate Android Development] vvaffles:
ah sorry, i misunderstood.
[Captivate Android Development] gandalf21502:
This has been said...but...a big THANKS to everyone here working hard on this!
[Captivate Android Development] smithisize:
Got it! It's beautiful:-)
[Captivate Android Development] SSMI:
SO I'm building this and the kernel compiles fine and the tar works fine but I get an error in the section about building the whole package. When I run the command lunch cyanogen_captivate-eng I get an error about device/htc/supersonic/supersonic.mk not existing which I think is weird because I don't care about that device. Everything synced to 100% earlier too.
[Captivate Android Development] smithisize:
Try re-syncing. I had to do that a few times before the files and work tree synced properly.
[Captivate Android Development] SSMI:
I just resynced it a number of times. It counts straight to 100% and says done. I still get the same error. I did notice something though. hen I run the envsetup command it lists a bunch of devices and the supersonic isn't on that list. Then when I run the lunch command it says it can't find the supersonic.mk file. Maybe thats why. I tried reopening the console and syncing again as well and it still doesn't work.
[Captivate Android Development] smithisize:
Can you paste envsetup output here please? As well as lunch
[Captivate Android Development] SSMI:
Here they are.

The file the error refers to isn't there.
[Captivate Android Development] smithisize:
Hmm... and you're doing the following:

repo sync -j40

?

If not, try repo sync -q -j40

All it does is supress most output so only important stuff is displayed. Helped me a lot
[Captivate Android Development] SSMI:
Ya that is how I am syncing. I did it again and it pulled something like it missed but I had run it a number of times where it went straight to 100. Still doesn't work. should I delete it all and try again? I would hate to.
[Captivate Android Development] smithisize:
I would. I did that like 3 times before it worked >.<
[Captivate Android Development] SSMI:
It takes so long >.< Is that file even necessary for the captivate? Could I maybe make a blank one just to get it to work? Or is there a way just to sync the captivate stuff?
[Captivate Android Development] smithisize:
I honestly don't know ://
[Captivate Android Development] atinm:
No, but you will see a warning if you do. Ignore it . . . I use an old 32-bit machine I have as my build box.
[Captivate Android Development] atinm:
It is actually lunch that is complaining - an upstream change that wants supersonic. You can go into vendor/cyanogen and grep supersonic and comment it out if you want to compile, but better to try sync'ing again, it is sync'ing a lot of new stuff due to upstread 2.3.3 merge.
[Captivate Android Development] atinm:
2.3.3 is merged upstream to CM7 so you will need to resync and build. You might see issues due to the large commit this entailed.
[Captivate Android Development] AJerman:
Dammit, I opened SSH to my home computer so I could work on getting the sync and compile and a few others things while I was bored at work today, and of course it promptly starts acting up (telling me my entire file system was read only), so I reboot it and it never comes back up. I hate computers, haha.

Maybe I could spare a few blades here at work..... :D
[Captivate Android Development] zielins1:
Having problems compiling the initial kernel. Running into some errors in /kernel/samsung/2.6.35/arch/arm/mach-s5pv210/mach-aries.c. Compilation output is such:

Any suggestions?
[Captivate Android Development] zielins1:
nevermind, either a fix got checked in or my compiler decided it didn't mind.
[Captivate Android Development] AJerman:
https://github.com/teamhacksung/and...mmit/7517f0ad121cc1f08928acd814257b4240dc3d74

They are clearing up a few issues with the 2.3.3 merge still.
[Captivate Android Development] SnakeHaveYou:
Yes!! Because 2 things:

1- Unified Repo!

2- Finally i could sync and compile correctly!! (bad checksums and java!)
[Captivate Android Development] mcord11758:
Ok, here is my question. The thread says it is for devs only to develop, but it appears it is only being compiled by users with the know how, for personal use. Is there a realistic time line where average users like myself could expect a beta, or is it safe to say I should either learn how to compile or move on?

Please, no disrespect meant at all, just an honest question.
[Captivate Android Development] rizzo1001:
6 months is probably realistic.

[edit] I've only been reading this forum for 6 months and even I'm tired of people asking for release dates for software that folks work on in their spare time. Ridiculous. Sorry for the derail. Back to lurking.
[Captivate Android Development] Kaik541:
it is up to atinm for when a public release will be available to the general community, and as of last night he is not 100% satisfied with it's state to provide this release.

I don't know where you're getting this date, it is (mostly) feature complete at this time and is just optimization and bugfixes. captivate builds are in-line with the i9000 builds for the most part. Here are the known issues:

2G/3G toggle broken when you have an active data connection

wifi hotspot doesn't work (USB tether does work though)

camera pictures taken in portrait mode get rotated 90 degrees, but not landscape

polling problem when phone turns on (put it to sleep and wake it up to fix)

orientation can get "locked" after using some apps (Google Navigation)

wifi sleep can cause soft reboots (set to never sleep or don't use wifi)

no sharing of external sd card to computer (take it out and use it)

there may be one or two more things that I can't recall all the top of my head
[Captivate Android Development] slifer315:
none of the above issues are even major either. codeworkx did say last week that he might release both a captivate and a fascinate build this week.

Sent from a phone, playing a phone, disguised as another phone.
[Captivate Android Development] i have a leg:
I can confirm wifi hotspot DOES work
[Captivate Android Development] Kaik541:
whenever I attempt to use the wifi hotspot feature, I receive an "Error" comment instead of activating and then the phone soft reboots. (I'll try again with WPA disabled and just an open connection)

just tried, still errors out for me running a build made from about 2 AM last night
[Captivate Android Development] DrCruelty:
My luck he will do so right after I finally figure out how to build this. In the mean time, I continue trying.
[Captivate Android Development] SnakeHaveYou:
LOL!!!!

The weirdest bug i've seen on my Captivate!!

The capacitive buttons are located inside the Screen area!!!! :D
[Captivate Android Development] Kaik541:
you must have built very recently, https://github.com/teamhacksung/and...mmit/6d54eb99f060e7e7ef0f187e668c426d0c804b45

codeworkx has acknowledged the issue, will be resolved
[Captivate Android Development] SnakeHaveYou:
Yep, it's easily seen in Pointer Location.. In bottom area, the pointer goes faster than your finger (my english is bad :P)
[Captivate Android Development] Scarchunk:
Hotspot is working here on a 2.3.2 build compiled night before last. 2.3.3 seems to have broken quite a bit. I compiled a 2.3.3 ota zip last night but kinda glad I held off.
[Captivate Android Development] atinm:
Do not pass go - repo is quite broken right now while we merge 2.3.3 stuff from upstream. Just cease and desist until the all clear. :)
[Captivate Android Development] Kaik541:
DO NOT FLASH A BUILD MADE ANYTIME WITHIN THE PAST TWO HOURS PLEASE

http://twitter.com/#!/codeworkx/status/42695695869808640

it's possible the controller firmware for the touchkeys may BREAK backward compatibility and will not be able to use samsung firmwares again (2.1/2.2)
[Captivate Android Development] zerojay:
See above.
[Captivate Android Development] bobbylx:
1 more for the warning list. If your phone does not have working button recovery/download or if you have flash the button fix, be very careful!
[Captivate Android Development] bpodz34:
Hate to be this guy but any word on progress and when it might be released for public use? :)
[Captivate Android Development] atinm:
The only rule of CyanogenMod is that you don't ask for ETAs :)

And we're quite broken right now anyway . . . latest kernel source drop upstream screwed us with touchkey firmware install that had never been part of Samsung kernels before so caught us unawares.
[Captivate Android Development] zelendel:
Ok guys Even though the thread says it is for Devs only it seems that alot of people are trying to do this. So instead of this thread filling up with questions from people who honestly should not be attempting this I will say this. Try this at your own risk and while you might get a little bit of help on some issues, you are on your own. Let the Devs work and not bother them with questions about ETAs and issues that they already know about.
[Captivate Android Development] smithisize:
Once I got it downloaded, nothing else has been a problem honestly. Downloading was 90% of the battle lol.

A slight hangup with java, but anyone somewhat knowlegable (or, in my case, willing to research while awaiting a response) could figure it out.

Now everything is running, I hope I can contribute.

Regards

Smith
[Captivate Android Development] pvr:
Good luck to all of you. I'm one of those that do not have the time to go and compile from source so I'm rooting for the success of your volunteer work!
[Captivate Android Development] dudyk:
After seeing the initial flash instructions (which I missed before) I finally know how to flash this thing.

Are there any plans to clean up the build process to make it use the "CM7 standard"? Need help with that?

From what I know, all block devices in the SGS line are managed flash, why use yaffs2? do you access the raw flash some way?
[Captivate Android Development] AJerman:
So, if you remember me saying I rebooted my home box from work yesterday and it never came back. I got home to a dead Linux install sitting at the initramfs prompt! :(

So that's a bit of a set back for me. I haven't been home for more than a few minutes (except to sleep) for the last few days, but I've been needing a fresh install of Linux for a while on a bigger partition, so tonight I'll have to do that and hopefully I can get everything rebuilt and start messing with this more.

I will say though, I've had incredible battery life with my current build of CM7 (built on the 26th I think?). I left my charger at someone's house last night and my other at work, and went to bed with 25% or so and woke up with a good 17% still, even made it all the way to work playing music without dying. And that's with all my apps like Lookout reinstalled and running, so that's a great sign. I think I'm going to charge it to 100% now that I'm at work and see how long I can make it last. It was at 22 hours this morning and that was with playing Gun Bros for a while and not trying to make the battery last.

Everything will be cleaned up eventually, but right now getting the ROM working is the priority first.
[Captivate Android Development] cumanzor:
So, I take it from this that flashing your own CM7 binary doesn't touch the bootloader?
[Captivate Android Development] smithisize:
I'm working on fixing a small issue but am a little stuck...

From the messaging app when you click the contact's icon then call them, the screen and buttons go black and are unresponsive until you cover the proximity sensor and uncover it.

Can someone help me fix this, or work with me, I think I'm close but I'm not sure...
[Captivate Android Development] atinm:
No, we do not touch the bootloader. Only Samsung does that. So the GB leak from Samsung did touch it but we would never do it ourselves.

Again, please - unless you are a relatively experienced developer, do not try this yourself.
[Captivate Android Development] slifer315:
when you place the call, the phone assumes you're going to put it up to your face to hear the person you called, so it shuts the screen off to avoid unwanted operations by your face. it's working as intended.

Sent from a phone, playing a phone, disguised as another phone.
[Captivate Android Development] SSMI:
Is the repo back to a working state? Are there still a bunch or errors in it?
[Captivate Android Development] cumanzor:
I haven't seen this behavior in any ROM I've used (all Samsung of course, 2.1 or 2.2.1). If this the default behavior in CM? Does it happen in other phones? Does it happen outside of the messaging app?

Normally, you still see the screen after placing the call, and it won't get "locked" until you cover the proximity sensor. Think of any occasion in which you will need to toggle the speaker or the dialpad right after placing the call.
[Captivate Android Development] bubbinator91:
Just wanted to make sure that the touchkey firmware was indeed reverted and that it is safe to compile and flash now.
[Captivate Android Development] DirtyRasa:
Since the OP was edited. Does that mean we can re-sync and compile again?
[Captivate Android Development] atinm:
It should be fine now - no longer touching the touchkey firmware . . .
[Captivate Android Development] vvaffles:
i did a build at 12:30 today after sync and it works fine, i think coolya tweeted that they reverted to the old driver this morning.

the colour temp changed tho, its a bit more...yellowish.
[Captivate Android Development] TheEscapist:
Google changed the samoled driver in 2.3.3.
[Captivate Android Development] Kaik541:
this is from an upstream change related to crespo (nexus s) I believe. it's not life or death, just something to be aware of. Engadget recently compared the two color temperature differences on the nexus s and it should look fairly similar on ours: http://www.engadget.com/2011/02/27/...campaign=Feed:+weblogsinc/engadget+(Engadget)
[Captivate Android Development] Kaik541:
To anyone who updated their touchkey firmwares (keys inside the screen/not working on 2.2 or 2.1) and wants to fix it, the solution was found thanks to evaluate (tested and confirmed by codeworkx here).

It requires flashing back to a COMPLETELY STOCK firmware (JF6/JH7/KB1) and typing in the information found on this thread here. Should restore functionality.
[Captivate Android Development] smithisize:
Yes, I know, but it's inconvenient because I often switch to speakerphone immediately. I'm trying to remove that check, or delay it rather, a second or two.
[Captivate Android Development] slifer315:
it's actually not happening anymore in the build I made earlier today.

Sent from a phone, playing a phone, disguised as another phone.
[Captivate Android Development] squishy5:
how is the new build 2.3.3 running
[Captivate Android Development] Baltix:
keeping thread clean for dev talk
[Captivate Android Development] slifer315:
I did have this problem yesterday, but not with today's new build.

Sent from a phone, playing a phone, disguised as another phone.
[Captivate Android Development] ytt3r:
This is a Dec thread, not intended to answer questions but to be informative about how to build for yourself. If you need help you can get it on the cm forums (not in the Dec thread(s)) or on freenode at #cmsgs.
[Captivate Android Development] Kaik541:
This. Let's try to keep the thread clean of non-dev talk. If you are having any issues building or an issue WITH a build, please come to #cmsgs on freenode and we'll help (it's also a much faster way to communicate with the developers)
[Captivate Android Development] coderunner:
I was thinking about compiling this. How big is the repo?
[Captivate Android Development] ytt3r:
7.7 GB when all's said and done, and you've compiled. That's not including the packages required to install.
[Captivate Android Development] coderunner:
I was just wondering I started syncing an hour ago and was wondering how long to expect.
[Captivate Android Development] ronandi:
From atinm's twitter: "Working on putting up a CM7 build for #captivate - compiling now"
[Captivate Android Development] Kaik541:
build possibly on hold, stuff got pushed upstream (seems the ENTIRE sdk got pushed in somehow) and is messing up a lot of things
[Captivate Android Development] coderunner:
That would be nice I was going to compile it but I had to put it on hold because it was eating up all my bandwidth syncing and I am using my internet for other stuff right now. What is the twitter username I can follow for progress?
[Captivate Android Development] Billabong81:
http://twitter.com/#!/atinm