yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] studacris:
Lol that song has been looping in my brain for days now.
[Captivate Android Development] erbsmokah:
Nokia 5190, rogers... Nokia 5195 Fido... These phones were pre rogers fido merge and they are old school but its an example of rebranded phones having different model numbers.

or how about the captivate and the Giorgio Armani GT-i9010, same phone.

also they are talking about the small hole under the speaker grill, not the reset button to the left. Its there on our phones.. I took mine apart but if it is the microphone there is no way of telling since its soldered onto the mainboard. I still dont see why you would put the chip and not the microphone... that doesnt make sense at all.
[Captivate Android Development] TRusselo:
well there you go evidence in the other direction for the others who support their point.

I personally dont give a flying FU#GE. i really dont. noise cancellation or not, the call is too quiet to hear in my loud-ass van! lol
[Captivate Android Development] erbsmokah:
Why dont we just email samsung and ask them?
[Captivate Android Development] mrhaley30705:
Anyone remember what this thread is about?
[Captivate Android Development] studacris:
I think is was about Mr. Rogers making gingerbread cookies....
[Captivate Android Development] TRusselo:
effin eh it is
[Captivate Android Development] boog:
And on that point, has anyone built a working kernel from the source yet?

I have been just chasing my tail with it.

The stock kh2 kernel boots on my phone, just trying to build from the stock source bootloops, using the built in directions.

export CROSS_COMPILE="/home/boog/CodeSourcery/arm-2009q3/bin/arm-none-eabi-" && make KEPLER_ROGERS_defconfig && make
[Captivate Android Development] LNJ:
Just cause the audience chip diagram shows it could use 2 microphones does not mean that it needs it or that the i897 has it. In order for it to be significant 1 mic would have to be for voice and another just for ambient noise!

Totally unnecessary since voice and ambient sound can be separated during processing.
[Captivate Android Development] salazar44:
Check the flux capacitor
[Captivate Android Development] mrhaley30705:
Yep.Exactly.
[Captivate Android Development] TRusselo:
oh and from what i just read audience chip software support is in the modem not the kernel.

so................ NOT TIED TO THIS THREAD AT ALL!
[Captivate Android Development] geokilla:
Could this source be used to reorient I9000 kernels? I wanna try and reorient Semaphore from I9000. Talon is too laggy after a while and I'm trying ot test things for pikachu, which also indirectly helps existz.
[Captivate Android Development] nkrick:
There is a kernel driver for the Audience chip, and that is included in the Rogers source from what I have heard from Team Hacksung. While the modem also contains support for the Audience chip, that is not all that is required or you would be able to use i897/6 modems with i9000 kernels.

You are correct that whether or not the i896 uses the audience chip voice processing has no direct relation to this thread.

---------- Post added at 08:11 AM ---------- Previous post was at 08:03 AM ----------

Do some research. Read the A1026 press release, Audience themselves say that the A1026 uses "two microphones in a mobile phone to uniquely identify the primary voice in a conversation and eliminate surrounding noise." http://www.prnewswire.com/news-rele...ice-processor-for-mobile-phones-80687947.html

Also, check out the following document for more information: http://www.tmaa.com/images/Audience_dual-microphone_processor.pdf

The Nexus One used a second microphone on the back of the phone. The small round "hole" next to the rear speaker on the i897 is almost certainly a second microphone. I don't feel like tearing my phone apart to prove it.

Okay, I am done with Audience, but I had to respond to the comment since the primary feature of the A1026 is the multiple microphone support.
[Captivate Android Development] mrhaley30705:
As often said, screenshot's or it didn't happen.
[Captivate Android Development] mbc663:
Audience chip talk is taking over this thread.
[Captivate Android Development] TRusselo:
Yeah.... it is....
[Captivate Android Development] FlKTION:
Back to the OP, thanks for all you dev's who are trying to build a new kernel using the source. I moved to Fusion X from FireFly to get in on the GB action and am enjoying a faster and more responsive android I just really miss BLN lol I forgot how annoying it is to have to turn on my phone to see if I have any unread msg's.

Thanks for all the work
[Captivate Android Development] ln100:
Don't know if anyone will find any use from this, but...

Found the 2.3.4 GB source for the Galaxy S Mesmerize. Mesmerize is the only US Galaxy S (US Cellular) I have heard of getting an official GB ROM.

Go to the Samsung open source page - https://opensource.samsung.com

Search for i500 - EH09 is 2.3.4 GB

Don't know if any of this is of use to any of the devs, but if it is - great!
[Captivate Android Development] TRusselo:
its not. its not for the captivate hardware.

and thats where this source came from, but for our device.
[Captivate Android Development] Yuna:
Please, stop any talk about Audience etc.

Here is a proof of even that motherboard of i896 called i897

and there is a audience chip.

http://4pda.ru/forum/index.php?s=&showtopic=258585&view=findpost&p=9705447

Might require signup
[Captivate Android Development] TRusselo:
i love you, and google translate!
[Captivate Android Development] Wdustin1:
Thank you so much finally the audience chip argument is done!

Currently Fusionized
[Captivate Android Development] TRusselo:
i wish i had my dev status approved so I could clean it all up... awaiting approval... again...
[Captivate Android Development] erbsmokah:
Hey, think of it this way... your thread finally helped end the long lasting and often times mentally retarded audience chip debate. I'm not sure what or why you would clean up the thread considering its for a link to kh2 source. Its better the debate happened here than in somebodys ROM thread.
[Captivate Android Development] TRusselo:
i would clean everything between the first question and the final answer, and my other threads...
[Captivate Android Development] erbsmokah:
What you should have said was..

"I would have locked the thread after creating it because it was only meant to provide a link for the uxkh2 source code"

:P

There was nothing to discuss so I guess we got carried away with the chip argument. Thanks for the link.
[Captivate Android Development] FlKTION:
Any updates from devs on progress with this source? I have patience but i am just curious if there has been progress :D

BLN and Voodoo withdrawals made me ask :O
[Captivate Android Development] Yuna:
Hmm, me too asking just for even a testing kernel for this source.
[Captivate Android Development] Squeaner:
Boog has been able to create a sucessful build. It unfotunately will not boot though.

He has a couple ideas, but has been spending time with his family.
[Captivate Android Development] studacris:
Well then I wouldn't exactly call that a "successful" build lol.
[Captivate Android Development] boog:
Just a technicality :p

There has to be just a little something evading me :)
[Captivate Android Development] TRusselo:
i did notice when i unpacked the files to an empty folder using 7zip (i think) it came up and asked if i wanted to over-write files... found that odd since it was an empty folder to begin with... there were more than 3 as after that i clicked rename all... never found them after now i think of it.
[Captivate Android Development] Yuna:
It's just cos for windows file and filE are the one file. but for linux filE and FilE are the different ones.
[Captivate Android Development] parnz:
Hmm... case sensitive.

So, If unpack on windows box you'll lose some file that overwritten(?)
[Captivate Android Development] nfs_phone:
<SNIP>...

but also that round hole on the back is on ours (896) too but its not a mic. and not a reset button, (its not a calculator!)

[/QUOTE]

What reason do you have for claiming that it's not a mic?

You make a statement that tries to sound authoritative but doesn't, because it seems that you don't really know what that hole is for.

Sent from wherever I was when I sent it.
[Captivate Android Development] TRusselo:
I read it in multiple posts that it is not a mic. if that information is incorrect go find people to posted it on xda.

I was wondering when you would show back up to this fight... Again.. looks like I'm going to have to block you again. you have nothing ever nice to say to me or about anything I have to say.

you don't have an i896, how do you have any authority in what you say?

once again this thread is not about the audience chip it is about source. go find a different forum!
[Captivate Android Development] jlsesler:
That statement struck me as funny...lol

I couldn't resist poking fun.
[Captivate Android Development] TRusselo:
this is a Development thread about source!

this is a Development thread about source!

this is a Development thread about source!

this is a Development thread about source!

where is my dev status so i can clean and mod my threads?
[Captivate Android Development] Nick0703:
Lol!!! Have you got any word from Boog about the Kernal?
[Captivate Android Development] boog:
I haven't had any luck, or much time.
[Captivate Android Development] Nick0703:
Alright then. Thanks for the reply
[Captivate Android Development] kimchi0400:
Does anyone know if this will affect CM7/MiUI builds in any way?
[Captivate Android Development] TRusselo:
read the thread please. it was answered 2nd or 3rd page.
[Captivate Android Development] Nick0703:
How long?

How long do we have to wait for the kernel to be done???:(
[Captivate Android Development] studacris:
As long as it takes
[Captivate Android Development] TRusselo:
I did this just for

you

buddy!

[youtube]TPJlKv-7_3s[/youtube]
[Captivate Android Development] studacris:
LOL thanks bro :D
[Captivate Android Development] Nick0703:
I'll guess that it will be months then.
[Captivate Android Development] studacris:
Really dude?

Where's your kernel?

How long is gonna take YOU to compile one?

Don't be rude and demanding to people doing this as a hobby in their free time. Unpaid.

If you want it done faster do it yourself otherwise wait patiently like the rest of us.
[Captivate Android Development] TRusselo:
the 1 time I show restraint n just say nothing....
[Captivate Android Development] Wdustin1:
+1

Currently Fusionized
[Captivate Android Development] boog:
I can't get it to build properly. It must be missing something that I can't find.

You are more than welcome to grab the source and help find the issue. All of the experienced devs are moving to other devices and we have to figure this stuff out to have new builds, and samsung appears to like to release not quite what they must have built upon.
[Captivate Android Development] TRusselo:
may not be fair to blame samsung, might be fault of rogers, as it is their build..
[Captivate Android Development] popfan:
I know this might be a stupid question, but have you been able to build kernal without any mods at all?
[Captivate Android Development] TRusselo:
That's always what they try to do first...

so, you called it...
[Captivate Android Development] Jsmokey:
Finally got a chance to pull the source boog going to give a go tonight and see if I can't get a bastardized voodoo color and sound version of red nebula together and working. Anyways getting ready to go to work but I'll post back what happens once I get home and get a chance to play with it some.
[Captivate Android Development] TRusselo:
i was going to email samsung source tonight and see if they can verrify the integrity/completeness/accuracy of the files, as just a stock kernel will fail to boot.

boog i know this is an extremely dumb question.... but you did disable lagfix first right? (stuck at kernel boot right?)
[Captivate Android Development] mattern1974:
Is anyone working with this source to bring additional features such as voodoo color?

Does it even match up with newer, KH3, KJ3 or KK2?

I imagine the answer to the 2nd question is yes...but maybe I missed the answer to the first somewhere.

EDIT: Sorry all!! I see there might be a problem with files. Forget I asked. Good luck...your work is much appreciated.
[Captivate Android Development] boog:
Yup, have had all lagfix disabled, have thrown all the tricks I know at it. Must be overlooking something.

Just to make sure, I put my initramfs into the talon source, and pulled a few files from the kh2 source, and got a successful port of talon. It, just has the typical bluetooth problems, and no audience support as running a i9000 kernel on i897 does.
[Captivate Android Development] 1tontomato:
If this boots I'd like to give this a try for kicks.
[Captivate Android Development] Jsmokey:
I get it to build fine but I do think something isn't quite right with the source itself. I tried unpacking the zImage so I could have a look through init.rc and it throws some weird messages I've never got unpacking before, says success and then there's jack in the initramfs directory in zimage_unpacked other than two empty folders.

Haven't tried flashing it due to the fact I really don't feel like having to go through booting up my other pc and getting it ready to use odin to flash something else when it doesn't boot cause I'm highly doubting it will. Maybe tomorrow I'll give it a go and see if it'll flash and boot.

For tonight I'm off to play around with the ICS source that dropped today and see if I can't get this to work better than the ICS sdk port I was working on. Shouldn't be terribly difficult to get booting but fully functioning is most likely going to be a royal pain.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] studacris:
Why don't you just use heimdall in Linux, instead of having to boot your other PC with windows for Odin?
[Captivate Android Development] Jsmokey:
Because usb voltage on my main machine and even my backup machine is too low to correctly recognize it in dl mode, pretty much the same issue quite a few apple machines have, and yes I'm talking about the rear ports, that's trying with windows, osx, and linux on both machines. So I really have no choice but to use my old server tower.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] boog:
Here it is, it also has a bug with it leaving the usb and the fully charged icons in the top bar, but everything seems to work.

http://dl.dropbox.com/u/33609688/talon_port/Talon-port_0.0.1.tar

it isn't going to be a release, it is beta beta beta! lol Proof of concept only!

---------- Post added at 07:12 AM ---------- Previous post was at 06:50 AM ----------

You have to specify your intitramfs folder eg: CONFIG_INITRAMFS_SOURCE="usr/initrd_files"
[Captivate Android Development] Jsmokey:
I did I just think something went wrong during the build. Going to give it another go sometime this week.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] boog:
Man, I hope you can figure it out. I am stumped! Moved to a different project for just a bit, going to come back to the kernel later, give it some time to rest lol
[Captivate Android Development] Wdustin1:
Lol don't stress over it boog, next November we will get Samsung sources!

Currently Fusionized
[Captivate Android Development] boog:
Technically these are Samsung sources :D

I'm not stressing, just ticked that I am better at taking something apart and putting it back together than starting from scratch (that actually applies to more things in my life than kernels lol).

But, I think if we could figure out what is wrong/missing then the other features could be implemented easily.

Or if the audience chip (and possibly bluetooth) could be ported over to other kernels, then kernels could be brought over from the i9000. The files for audience are in the i896 source, if someone could sort it out.
[Captivate Android Development] TRusselo:
what is the audience chips to be in the att and Rogers froyo sources as well? you could always trying building a fro yo colonel to see if you are doing anything wrong and to see what else you can find neat in there

XDA NEW USER GUIDE

WHY YOU GET SHORT/ONE WORD ANSWERS (The Long Answer)

Rogers Captivate Stock ROMS 2.1-2.3 | 3e Fix | Setup ADB

Fix your Screen Protector | Neon Clock | Docks! | Null Keyboard for BT Keyboards

Help me out. Get a Drop box account!

Captivate Bootscreen Replacement

Next Phone: Something Samsung!
[Captivate Android Development] Jsmokey:
Me too even tried building the source using the kj3 initramfs and everything built and flashed fine but it just won't get past the i896 boot screen which I believe is because its failing to mount the partitions, the reason I'm thinking that's the issue is because it won't let me mount anything but sdcard in recovery.

I think I need to take a more thorough look through the source and see if the mount points are different on the i896.... I can't really see them being different but who knows, I really just need to search real quick and see what I can find out.
[Captivate Android Development] TRusselo:
well all the i897 mount points work just fine on my i896 with i897 kernels/software.
[Captivate Android Development] Jsmokey:
Yeah that's what I figured, man this thing is driving me nuts.... I got a few more things to try but I'm running out of ideas and fast.
[Captivate Android Development] TRusselo:
like i said build a froyo source kernel to see if you are the problem or the GB kernel source.
[Captivate Android Development] Jsmokey:
I have many times, I modify and build linux kernel from source every few weeks to try out new patches and tweaks, I've built the aosp kernel, it compiles fine, I even run all my builds with the -d option so I can watch for anything out of the ordinary. This just won't boot past the I896 screen no matter what I do to it. Like I said even in recovery it simply won't let me mount the partitions so I guarantee they aren't mounting when its trying to boot.

I've tried building with just the default options, tried changing some of the config options around, tried building using other captivate gb initramfs.cpio by adding the path of the one I wanted to use in make menuconfig. None of them make it further than the I896 boot logo.

So no I'm not the problem, or what I believe you meant, no my set up on my system isn't the problem. When I have more time I need to run a diff between the source for i897 froyo and this and see if there are any major differences that could attribute to this not booting. I know that some of the code is going to be different regardless because of the firmware difference but its really all I have to work off other than maybe comparing an i9000's source.

Has anyone with the i896 even tried building this to see if it will even boot on the device/firmware it was made for? I know it's almost identical to the i897 but at this point I'm pretty much at the end of my rope trying to get this to boot, it honestly took me less time to get the ics sdk to a point where it would boot and if no one can confirm this source to be working at all then I'm just going to go back to devoting my time to working on porting ICS now that I have source to work from.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] erbsmokah:
Stupid question but did you try running the kernel with the rogers 2.3.3 firmware?

Also, If you send me a copy I can try it on one of my i896's
[Captivate Android Development] TRusselo:
i think they have tried that.wait "one of" your i896's??

wanna sell one? or at least the LCD of one? mine is cracked to SH!AT but still works.. 75$ (can) to trade lcd's?
[Captivate Android Development] boog:
That is exactly what I ran into. I tried swapping the fs from i9000, and still no boot.

I tried kh2, kh3, kj*, kk1 initramfs, and all of them would do the same thing. (Just have to use different "version magic" with each initramfs eg: export LOCALVERSION="-I897UCKK1-CL614489" just in case anyone didn't know).

And you can't pull kmsg or dmsg without the filesystem mounted lol
[Captivate Android Development] Jsmokey:
I know its driving me nuts there literally isn't anything left I can think to try to get this to boot and without any logs its next to impossible to find exactly what/where the problem is.

At above about trying it on i896, give me a day or so to rebuild it I've got a ton going on right now and I cleaned a lot out of my pc to make room for working with ics and one of the first things to go was the kernels I had built since they weren't working.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] erbsmokah:
Yeah i have two, one of them I broke the headphone jack off inside the phone... so im waiting for a part to arrive to repair it. When it happened I just ran out and bought another cappy outright to replace it. I'm going to hold on to the second cappy as a spare for now.. I work construction an destroy phones on the regular... Although I have to say I'm using the otterbox commuter and my phone is still in great condition. Some dust gets in because its not a complete seal like the defender but its doing its job quite well.

As for your screen I think digitizers go on ebay for about 100. You might have to get an i897 one though. If its just the glass thats broken they sell that too for around 20 bucks.. I have no idea how to separate the actual LCD digitizer from the glass lens without destroying it though.

Edit: Apparently you have to warm up the digitizer/lens assembly with a blow dryer or something to get the adhesive to let go. Sounds pretty ballsy
[Captivate Android Development] Nick0703:
Any word on the progress of the kernel?
[Captivate Android Development] TRusselo:
ICS took attention away
[Captivate Android Development] erbsmokah:
For good reason too!.. ICS SDK source is working pretty well considering how new it is.
[Captivate Android Development] TRusselo:
it would still be nice to have a source build gingerbread kernel
[Captivate Android Development] Wdustin1:
yes it would. at least get gingerbread to where froyo was before moving on lol. oh well
[Captivate Android Development] Nick0703:
Yep, it looks like it definitely did that.
[Captivate Android Development] sepherian:
Maybe if we just bump the thread a few times...
[Captivate Android Development] Jsmokey:
Well if we could get source that would build properly it wouldn't be a problem but for the life of me I can't get it to build and boot. When att finally gets gb for the captivate and the source for it comes out I'm going to work on it but to me this is a lost cause.

This past week I've literally built 3 different kernels from source and they've all booted up no problem but regardless of how me and boog tried to build this it wouldn't boot.
[Captivate Android Development] TRusselo:
js go to https://opensource.samsung.com/top right corner "web mail"

tell them what you know, how it wont build.

ask them to check for corruption, completeness, correctness of the file they have for download.

be clear and concise as the guy reading the emails.... well english isnt his first language.

make sure to include model i896 and the build kh2
[Captivate Android Development] Jsmokey:
I've already done that, sent it when I started running into all the problems with it, still waiting on a reply back.

I've been a member of the samsung open source site for quite some time now and have never had to wait so long for a response about anything which is another thing that has me fed up with working on this build.

I don't know I may give sending them another message a try when I get some spare time today.
[Captivate Android Development] :
Even though you guys can't get a working kernel, I would like to thank all of you for your effort and dedication. I too would love to see a working source built kernel, and maybe get some voodoo color love ;)