yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] cicada:
ZenInsight,

Without kernel source for Froyo you're going to hit a wall - you can't simply copy the sources into the phone, they need to be compiled modules. Without the sources, we can't compile the modules properly for the Epic.

You *can* compile the i9000 Froyo kernel, but the modules you get out of it won't be compatible - they'll simply fail to insert into the running kernel and that hardware won't be initialized ( in desktop linux, this is what insmod errors are )

In order for it to work, the modules need to be compiled alongside the kernel, and the i9000's kernel will certainly break almost everything else.
[Epic 4G Android Development] ZenInsight:
Well, here is the answer. Doesn't Samsung eventually release the source for the kernel like they did the i9000 after it's gone gold? Or would that be a kernel that has the files removed? Why does the TV out option show up in the Launcher Pro menu if TV out wasn't in there at some point?
[Epic 4G Android Development] cicada:
They do indeed, and it should be out for froyo shortly after public release if the past is any indication.

That said we have the full sources for 2.1 available now. The missng peice is the application layer to actually turn it on. That's where noobnl was headed before the froyo distraction.
[Epic 4G Android Development] bitbang3r:
Question: does anybody know *what* hardware physically lies between the headphone jack & Cpu inside the phone?

I'm seriously starting to think there's no video hardware per se, and the whole concept involved bitbanging raw NTSC/PAL with a gpio pin and brute CPU force alone. This isn't totally off-the-wall... far lesser CPUs than a gigahertz ARM cortex have pulled it off before (google AVR NTSC PONG). The hardest part (on a Linux system) would be the need to *literally* "own" the cpu during each scanline. Then again, Lucent & IBM both had working "linmodems" 10 years ago, so it IS apparently possible with a kernel module.

check this out to see how raw ntsc can be bitbanged by a cpu:

http://www.avrfreaks.net/index.php?name=PNphpBB2&file=printview&t=64452&start=0
[Epic 4G Android Development] cicada:
We *do* have a pretty robust graphics core on the platform that could handle that task and keep the cpu fairly idle - pretty sure that's how its being done on other devices. I doubt there's a discrete video output chip otherwise.

Hell, if DLNA can work there's no reason not involvng the radios would make it worse. And that can 'stream' 720p.
[Epic 4G Android Development] ZenInsight:
I wanted to let anyone knows that cares that I have *****ed about this enough that I would be willing to take on any task required to find a solution.

Besides that point as far as between the headphone jack and the CPU I wasn't aware of any other hardware. The CPU is the same that is in the Vibrant and Captivate as well as the Galaxy Tab (?). I believe that they all can output video via 3.5 jack. Why would this be any different?
[Epic 4G Android Development] bitbang3r:
Actually, having the headphone jack contacts wired directly to gpio pins on the CPU would be just about the greatest thing that we could hope for, because that opens the door to literally being able to use the headphone jack for raw bitbanged GPIO of any kind within the limits of the CPU itself. It would more or less GUARANTEE that we can generate video, even if Samsung and/or Sprint never make it happen officially.

In fact, we could actually go a step beyond composite video, and do s-video using the pins normally allocated to left and right headphone audio. God forbid, if the pin normally used as an input with the mic is fully bidirectional and can be used as an output by setting a bit in a data direction register somewhere, we could even bitbang YPbPr component video. In fact, component video would be EASIER to bitbang than composite, because we could largely ignore gamut and wouldn't have to worry about getting the phase timing right (there are colors that are theoretically possible, but can't actually be output as composite video because they'd cause interference and artifacts). Limited bit-depth HD is a definite possibility (via component video, or maybe monochrome by just connecting one pin to the TV's Y component input).

Remember, generation of an analog video signal is not the same thing as graphics capabilities. Believe it or not, HDMI is one of the easiest things you can output (as long as you can rely on external components to turn the data lines into proper balanced TMDS signals) because it's literally just a bunch of really, really fast serial ports operating in parallel. In contrast, analog RGB is a little harder, because you need at least a few resistors to make a rudimentary DAC. Component video is a little more complicated than analog RGB to calculate, but has more or less the same primitive hardware needs ( a few resistors to kludge a cheesy DAC). In contrast, composite video is absolutely the hardest thing you can try to generate in realtime, because SO MUCH nontrivial math has to be done in (more or less) realtime to make it happen.
[Epic 4G Android Development] ZenInsight:
Before I get into the following information I've found please remember that I'm beyond noob at this but I'm trying really hard.

So like limited as in 16-bit rather than 32? Question if the specs on the board of the Captivate and Vibrant have the same hardware as the Epic, would knowing what that PCB was laid out like and specifics on the chipset assist anyone in completing this task? As I understand it either the hardware can do it or it can't. Assuming that it can we need the source for the drivers that are Epic specific. Another poster mentioned this above. That means that the actually functionality of the chip can't be called to for the API to function. Unless someone reverse engineers the s5pc110.

I have no idea what I'm doing but I know how to search the net for conversations about this.

Take a look at this conversation:

Discussion about TV out driver

http://odroid.foros-phpbb.com/software-development-f19/is-the-analog-tv-out-driver-working-t226.htm

ODROID seems to use the exact same chip although of course I guess they write their own drivers.

Odroid's site:

http://www.hardkernel.com/

I also found this site in South Korea.

Translate it with Google (automatically asks you if you surf with Chrome).

Click on (Samsung s5PC110 family of processors) on left

[ODROID-T & S] Android 2.2 Froyo 3 Car Update (11/10)

http://www.aesop.or.kr/?mid=Board_Download_S5PC110&document_srl=351957

Driver download:

Kernel:

http://www.megaupload.com/?d=K7IW8RQ6

Android:

http://www.megaupload.com/?d=76W5YLT8

This looked interesting to me but may not be relavent whatsoever-

http://www.aesop.or.kr/?document_sr...3C64X0&sort_index=readed_count&order_type=asc

s3c-tvenc.c

and

s3c-tvenc.h

s3c-tvenc.ko is floating around too....

Where I found all this from:

Discussion about TV out driver

http://odroid.foros-phpbb.com/software-development-f19/is-the-analog-tv-out-driver-working-t226.htm

This is hilarious to me...it's like fighting Mike Tyson in the dark and he's wearing night vision goggles.
[Epic 4G Android Development] cicada:
I'd almost have to assume that's the case, I don't believe there's any discrete audio processing chip either - hummingbird is a SOC, not just a cpu. All of the drivers are availablein the kernel source, so perhaps the audio driver would shed some light on this.

Are there any datasheets on the platform that detail pinouts?
[Epic 4G Android Development] ZenInsight:
Researching:

WHOA--- I just think I found something interesting.

Apparently most places think this is true:

32bit Samsung-Intrinsity S5PC110, 1000MHz

All devices made with this chip

http://pdadb.net/index.php?m=pdamaster&posted=1&cpu=a10010

Fully ARM Cortex-A8 compatible, 13-stage pipeline, 64/32-bit Multi-layer AHB/AXI bus, ARM TrustZone, NEON SIMD engine, OneDRAM, mobile DDR, LP DDR2 interface, PowerVR SGX 540 3D graphics coprocessor, vector floating point coprocessor (VPU), 32-channel DMA, 1080p full HD codec engine, HDMI 1.3 interface

Right?

Not accordind to Samsung it isn't.

Found here:

http://ars.samsung.com/customer/usa..._ID=2&PROD_SUB_ID=557&PROD_ID=559&AT_ID=32581

What The Specifications & Features For The Processor Located In My Sprint SPH-d700 Epic 4G Phone?

The SPH-d700 packs a powerful Samsung S5PC111 (Hummingbird) mobile application processor, CPU, built on a ARM Cortex A8 Core that can operate up to 1GHz. The System On a Chip (SOC), enables intergration of gaming, navigation, media player, camera, multiple radios, and more while offering lower power and high performance in a mobile device.

The S5PC111 has an incorporated multi-format codec engine capable of recording up to 720p using the handset's camcorder.

TA - DA

NOT a 110. It's a S5PC111 !!!!!

I also found this a huge FAQ list page:

http://ars.samsung.com/customer/usa...ID=2&PROD_SUB_ID=557&PROD_ID=559&AT_ID=315927

What's really funny is this one:

http://ars.samsung.com/customer/usa...ID=2&PROD_SUB_ID=557&PROD_ID=559&AT_ID=316007

Hmmmm...so asking how to connect the phone for TV out gets an answer same as the question? Interesting.

I still looking for the Pinout diagram for the Epic.
[Epic 4G Android Development] m5james:
I've tried this on LauncherPro and I don't see an ADD and ACTIVITIES screen :confused:
[Epic 4G Android Development] biscojams:
Sorry it's long press , shortcuts, activities, settings, then scroll down to tv out
[Epic 4G Android Development] m5james:
I can't find TV-Out, but I did notice that the next submenu is misspelled with one too many S's ;)
[Epic 4G Android Development] tmillar07:
UPDATE

Progress updated. Please see OP.
[Epic 4G Android Development] ZenInsight:
"TVout service is running, TVout settings starts up, does not force close, but does not list any settings. Phone screen goes black, and it does recognize when a 3 RCA cord is plugged in. I am getting a couple errors, which I dumped to logcat. I need somebody who can read, and analyze the log, and help explain what its calling for, and what exactly it is doing. Like I said, this is pretty much my first whack at anything development wise with android. I am running leaked froyo beta 4.2, from a fresh wipe and install, with launcher pro plus v.0.8.1.0, and terminal emulator installed, and one or two other mods..."

I'm on Froyo 4.1 right now....but what cable are you using? I have the Nokia CA-75u which is SUPPOSED to work and HAS in other Galaxy S models.
[Epic 4G Android Development] cicada:
Awesome!

I suggest putting your logcat up on pastebin so anyone can peek at it.
[Epic 4G Android Development] Eazail70x7:
Keep it up!
[Epic 4G Android Development] bitbang3r:
Quick update. Bitbanged video is still a possibility if the guys can't get the current strategy to work, but my color/resolution predictions from last night were *wildly* optimistic. Full-color composite NTSC might still be do-able, but anything higher-res would be a crapshoot.

The problem is that bitbanging video is *very* time-consuming, and the dotclock for hd modes is so fast... ~55mhz. Simplifying a bit, you'd need ~200-300mhz just to modulate a single gpio with single-bit resolution using assembly. If you added an external YPbPr encoder (~$5) & interfaced it through a latching shift register (~$2, using 3 "headphone" gpio lines as clock, data, & latch and hardwiring the low bits to 0 ) , you *might* pull off 2/2/2 rgb. *maybe*.
[Epic 4G Android Development] m5james:
Every time I read your posts, it throws me off since it sounds like you've got it running. I've already got the cable, so hopefully something comes of this by the time I return home Thanksiving weekend. I don't see why the cable would matter as it works on other phones and it's not like that cable is some high tech piece of equipment that cares what it's plugged into. Once TV-Out starts working, my next order will be a 3.5mm to 3.5mm cable to I can go one-to-one in my truck :)
[Epic 4G Android Development] m5james:
You're so far above my head when you write :D
[Epic 4G Android Development] KitsunePaws:
I agree, this would be helpful.
[Epic 4G Android Development] ZenInsight:
Sorry. No I'm not running it....YET.

Agreed. lol
[Epic 4G Android Development] m5james:
Why was the title of this thread changed to a bold update with a date when ti's still not working? I almost shat myself w/ excitement.
[Epic 4G Android Development] Poryhack:
It's so people know the update was today and not a week ago. Chill. ;)
[Epic 4G Android Development] m5james:
As long as I reply to this thread, or anyone else for that matter, I get updates automatically emailed to me. I just don't see why it was renamed when it's still at the same point. I'm "chill" as is, so no need to tell me what do. I want this to happen just like the next person, so I got excited when it was changed...for no reason.
[Epic 4G Android Development] muyoso:
I guess the OP didn't know that you were getting automatic updates emailed to you. He will be sure to change his posting and editing behavior post haste so as not to rouse any more unwarranted excitement.

Or, you know, he just wanted to inform others that there was a development and to draw attention from other developers to his recent discoveries so that together they may be able to make your phone more awesome. I am sure he is VERY sorry he disturbed you.

Edit: Also, not sure if you know this, but most people don't get emails every time someone replies to a thread.
[Epic 4G Android Development] m5james:
I'm sorry, but why are you guys being asses and ganging up on me? I simply asked why the title was changed. I get email updates when I reply to threads, and for ANYONE who is on these forums, once the a reply is made on a thread, it bumps the entire thread back to the top. Point is, I just asked why it was changed. I'm not all ***** hurt about it, so lay off.

EDIT reply - If you haven't made the necessary changes in your preferences, thats' your personal choice. As I said though, replies on the thread still bumps it to the top anyways.
[Epic 4G Android Development] KitsunePaws:
Nah, they're being asses to OP. Stop whining about the update...
[Epic 4G Android Development] scriz:
By default, users do not get email updates just from replying in a thread. Thats something you've set up. You can't expect everyone to do that.

And it was updated to let people who DO NOT have email updates that progress has been made ;)
[Epic 4G Android Development] jacktownlane:
Off topic guys. Start a new thread if you want to ***** about this one.
[Epic 4G Android Development] tmillar07:
UPDATE! I'll make sure every time from now on that I do anything on this forum that it complies with your personal preferences. Thank you so much for letting us all know that you are a whiny brat. When it is finaly enabled, I will be sure to send a pm to everyone BUT you. As a matter of fact, I might even start a thread with a list for those who would like to be updated about progress, and I'll create a specific one just for you, and in full compliance with your personal needs. And it's not like you got 5000 emails about one update. Are you that bored that you busted one in your shorts when you read the title? I bet you also send money to Svetlana from russia, in hopes of one day finally meeting her when she comes from another country thousands of miles away, just to see you.

Everyone else who is patient and understands that software development takes time and effort: Thank you for your continued support, understanding, and help no matter how small, and mostly, not being a jackass.
[Epic 4G Android Development] m5james:
Jesus christ, I asked a ****ing question...it wasn't whining, so if you guys all want to perceive it that way, so then clearly that's your mentality. Even the OP can't move on, and you guys are calling me whiney while it takes like 5 guys humping this thread to tell me their opinions...hypocrits.

PM me if you jackwagons feel the need to vent more, in the mean time, get back to the damn topic already...for the SECOND TIME.
[Epic 4G Android Development] tmillar07:
Either I'm a complete idiot, and I clearly don't know my @ss from a whole in the ground, or certain people with their attitudes just happen to annoy the crap out of others, and heaven forbid somebody makes a comment about it.

Back to the subject, which I started, and I will UPDATE, or deviate from as much as I please:

Will post log tonight, who is experienced with compiling kernels for the epic? Should we wait for the 2.2 kernel's source to be released, or backtrack a little with 2.1?
[Epic 4G Android Development] Poryhack:
We still don't have official word from Samsung about 2.2 (not that it would mean much more then pure speculation does if we did). If everything else is in place, I see no reason to sit and twiddle thumbs until 2.2 is official.

$.02
[Epic 4G Android Development] ZenInsight:
I thought that without the 2.2 kernel source we couldn't do anything that affected tv out driver functionality. In fact, shouldn't you be more concerned witht the unrelased leaks kernel...not even the one we have now?
[Epic 4G Android Development] cicada:
The trouble in 2.1 is we have source/drivers but no obvious way to actually turn on tvout, in 2.2 it appears we have the option, but no source to modify.

We've got opposite issues on either side of the wall.
[Epic 4G Android Development] :
could there be a chance that some of the other Galaxy s phones could have what we are looking for in there 2.2 updates.
[Epic 4G Android Development] ZenInsight:
I asked this in another post and they said that you get errors trying to use the i9000 kernel drivers in the Epic because they aren't written for the Epic specifically. I don't know enough to argue against that logic.
[Epic 4G Android Development] latinmaxima:
I am simply glad it has gotten this far and hopefully once the 2.2 source is released we can get what we need. I realy don't see the need for it to be put on 2.1 as I truly doubt anyone will stay on 2.1 for tv out if it isn't on 2.2 right away. Thank you though to everyone helping in this process.
[Epic 4G Android Development] m5james:
I'm pretty sure that's why Noobnl and some others aren't concentrating on this as much as we like.
[Epic 4G Android Development] k0nane:
There's an awful lot of hate and general squabbling in the Epic forums...

Folks, can we all just get along? Or try? Please? :)
[Epic 4G Android Development] cicada:
Pssst.. the best way is to not feed the trolls ;)
[Epic 4G Android Development] dwallersv:
rofl

rofl

rofl
[Epic 4G Android Development] a454nova:
What about the tab? It has everything 2.2 and its out with TV options. Right?

Plus, and I may be wrong. I thought I read it was the same hardware. Most of our leak 2.2 came from the tab I think.

Sent from my SPH-D700
[Epic 4G Android Development] cicada:
Our leak came from - get this - the Epic!

The leak is the Epic's own 2.2 beta.

We have more in common with the i9000 than the tab, and the i9000 has tv options as well. Unfortunately its not that simple. The tv-out is baked into 'settings', not just a standalone app we can borrow.
[Epic 4G Android Development] a454nova:
Makes sense, I only thought the 2.2 we have was a vision that started from the tab and samsung used it to make ours. I've come across a few thing playing around that thinks my phone is the Galaxy Tab.
[Epic 4G Android Development] jacktownlane:
I for one would stay on 2.1 if video-out was finally solved for it but not 2.2.

I need standard-def video-out + Android + Sprint.
[Epic 4G Android Development] cicada:
I wouldn't consider the 2.2 beta to be fully indicative of what we'll see in the official release - all indications seem to be that dk05 is more stable, official should only improve on that.
[Epic 4G Android Development] cicada:
This info may be useful to anyone working on this.

Our audio subsystem is the WM8994 from Wolfson Microelectronics, full specifications here:

http://www.wolfsonmicro.com/products/audio_hubs/WM8994/
[Epic 4G Android Development] sinman02:
So is this project dead? Postponed? Can someone provide an update? I know BThomas is working on this on his rom. Has everyone else given up?
[Epic 4G Android Development] ZenInsight:
As said before, we are waiting for the kernel source before any further work will be done. If BT figures it out before then, hopefully it will still work with the new source.
[Epic 4G Android Development] sndtubes:
Shouldn't the Andromeda kernel with prototype TV out help? I haven't tried it myself. Don't have a cable.

Frankly I'm really PISSED at SPrint for this. They keep releasing DELUXE phones with DELUXE prices that are CRIPPLED. They deleted the FM radio on the Touch Pro and Touch Pro II and now the Epic has the TV out feature deleted. The Epic probably should have had the FM radio, too. That's just bullcrap. I'm just about ready to switch to AT&T. At least they don't disable features on their phones.
[Epic 4G Android Development] onilink67:
They disable loading application from outside sources on their android phones
[Epic 4G Android Development] ZenInsight:
It's true, just as with every carrier in America, there are features disabled OR the phone itself is lacking something important. Like the other version without keyboards, LED flash, and front facing cameras.

There should be functioning radio but TuneIn Radio really solves that problem and more for me. Check it out, it's amazing and free (there is a paid version but I don't know what else it offers).

The Andromeda kernel doesn't work for Froyo and also doesn't work for TV Out. I have tested it thoroughly (as far as I could) and it's not working. BThomas is working on it for Froyo apparently but without the source kernel as of yet.

Honestly, once this is cracked the only thing I can tell that will be missing from this phone is USB Host and the ability to view NTFS hard drives (google "Android Paragon NTFS driver").

Let's be patient, the phone has been out for 90 days and devs have already hacked the crap out of it. We are moving in the right direction.
[Epic 4G Android Development] Djinn23:
Have you ever checked to sere how locked down att android phones are?
[Epic 4G Android Development] Electrofreak:
I've not read through all the pages in this thread so forgive me if it's been mentioned, but I've heard (from dev Whosdaman) that TV-Out was actually in the DG17 build of 2.1, and if we were to get a dump of that build we may be able to find further details necessary to solve the TV-Out problem.

When I originally received my Epic, it had DG17 loaded and would not update OTA (as it's apparently a pre-release build). I flashed to DG27 to update to a release build and from there received my updates OTA as they should. Only later did I hear that I may have been able to provide a dump to assist the TV-Out effort.

If this is the case, if anyone's got an Epic that still has DG17, lets grab a dump and see if we can pick any TV-Out functionality out of it.
[Epic 4G Android Development] ZenInsight:
dg17 never had it. A Samsung rep has been said to have had a release earlier than dg17 that had it...but no one has ever seen it, that's just heresay.
[Epic 4G Android Development] Electrofreak:
Interesting, thank you.
[Epic 4G Android Development] ZenInsight:
BT is asking for beta testers for TV out now IF...you have a cable. Either 3.5mm to composite OR the micro usb to HDMI.

http://xdaforums.com/showpost.php?p=9556314&postcount=2307
[Epic 4G Android Development] art3mis-nyc:
Theres an SMB version of ghost commander in the market that should let you view NTFS via samba.
[Epic 4G Android Development] tmillar07:
I am still working on this, for those of you who lost hope, there are also several more groups and individuals working to get this solved. A little group effort can go a long way! Thanks everybody for help and continued support and optimism. Will be more involved with this again once the holidays have passed.