yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] tjhart85:
Willing, LOL.

I will concede that Samsung seems to be releasing it in a timely manner vs HTC who seems to wait as long as possible.
[Vibrant Android Development] zenlakin:
Sorry guys, didn't mean to double post. Just noticed there is a post below about Froyo below by bbuchacher.

Sorry again....
[Vibrant Android Development] rjhay22:
Yo bbach are you gonna start working on the vibrant too? Loved your work on the mytouch. :-)
[Vibrant Android Development] bbuchacher:
Yup eventually once we get more of a stable base going on.
[Vibrant Android Development] Oxirane:
Awesome! Can't wait to see the roms Som and Eugene come out with!
[Vibrant Android Development] rjhay22:
Glad to hear that bro, will be looking forward to seeing another talented dev working on the vibrant.
[Vibrant Android Development] glensta:
Indeed, Indeed - thanks for the update on this. The vibrant roms keep getting better and better :D
[Vibrant Android Development] Preech2003:
Thank god its about damm time.....finally we can get this cm 6.1 vibrant **** poppin'
[Vibrant Android Development] eugene373:
Can anyone put a Mirror up? I can't even connect to download it from there site atm... :(
[Vibrant Android Development] Jayrod1980:
Someone needs to get this to eugene, jac, and sombionix stat!
[Vibrant Android Development] sombionix:
Yes ziiiir
[Vibrant Android Development] los0325:
Yes.Yes yes..........
[Vibrant Android Development] option94:
http://xdaforums.com/showthread.php?t=807644

6TH OR 7TH post has a mirror.

ftp://whitewidows.servebeer.com/Android/
[Vibrant Android Development] WhiteWidows:
Mirror

ftp://whitewidows.servebeer.com/Android/
[Vibrant Android Development] eugene373:
Thanks guys, I pulled a noob posting error... ( Didn't read all of the thread ):rolleyes:
[Vibrant Android Development] daddysays:
Looks too small to have the kernel included
[Vibrant Android Development] gthmcty1:
x1 FO SHO!!!!!
[Vibrant Android Development] flameinthefire:
does this mean that we can expect a fully working froyo rom from you?
[Vibrant Android Development] daddysays:
I think it means he is getting out of the android business.
[Vibrant Android Development] boogerburns:
Well it says I-9000, so the kernel if its included is still only for the international version of the Galaxy S series. So were probably stuck still with 2.1, unless you flash JP3 test, which is pretty awesome.

Kernels for each Galaxy S flavor are different. So things break if you use one on the other. Such as GPS, WiFi, etc.

SO CLOSE!!!!
[Vibrant Android Development] Paging Dr B:
Lol, it's sad that those two words made my morning.
[Vibrant Android Development] d01100100:
Are you referring to the fact that this is source code and uncompiled? It shouldn't be that large, although the opensource webpage is getting hammered right now and unavailable.

I think the advent of the release of Samsung Galaxy K on 2.2 is why we're seeing this being released now.
[Vibrant Android Development] daddysays:
It was actually just an observation compared to the size of releases and custom roms that flash everything, and ones that dont. Without kernel is between 150 - 180 and with everything is around 220 - 240mb.

Probably wrong since all files do not need to be included in an update. Not sure exactly how it works, but saw this file was only 177mb.

Again just a noobish observation, I really have no idea, lol
[Vibrant Android Development] djf8:
Should be interesting to hear what Eugene or Sombionix have to say about this source when they rip into it.
[Vibrant Android Development] daddysays:
Soooo I was wrong, kernel included. Still I9000 though so will still have same prob with buttons, wifi, bt, etc.
[Vibrant Android Development] WhiteWidows:
ftp://whitewidows.servebeer.com/Android/

lol You guys are hammering my FTP, so I made a torrent file. Im having some issues getting it going so let me know if you can connect. If you can use this and help seed. Thanks.
[Vibrant Android Development] blackerwater:
So what's in it? I hope something we can use. Dang it I'm on vacation!! No laptop

Sent from my vibrant
[Vibrant Android Development] daddysays:
How can you go on vacation without your laptop? You mine as well have left your phone too. :P
[Vibrant Android Development] blackerwater:
My wife said no laptop no working no no no. Im lucky I have my phone :)

Sent from my vibrant
[Vibrant Android Development] Kubernetes:
Well, it's certainly preferable to have your wife work your lap top...
[Vibrant Android Development] cruiserbax:
Folks, relax.....deep breath in.....and out....... Wait until some good devs get a good look into it. With the kernel souce they should be able to to a reorient kernel with the buton mapping and recovery select and rotation fixed like they did for us captivate guys on 2.1 out of the I9000 2.1 source! good luck Vibrant folks! I am hopeful for ya'll!
[Vibrant Android Development] Kryptyx:
Mirror: GT-I9000_OpenSource_Froyo_update_JPM.zip

MD5: 29400f5223d23aaf877bbc4761784d88

I just tossed it up on my dedicated box, should be more than enough bandwidth for people to download this.
[Vibrant Android Development] VICosPhi:
Additional mirror from your mirror... :)

http://www.megaupload.com/?d=DHHAOFII
[Vibrant Android Development] daddysays:
Im trying to do the same, but cannot seem to get it to work without using a password. How do you do that? lol
[Vibrant Android Development] PowSniffer0110:
Maybe we should freak out on you and rant for not reading... :rolleyes:
[Vibrant Android Development] newkirk:
I'm trying to get the torrent flowing now, so far it's been 2 mins with no peers...?

I've set my colo server up to keep seeding it at up to 44mbps for the next few days, but so far I've not gotten started even.

j

edit: success, after about 5 mins it started running, about 600kBps down
[Vibrant Android Development] gravis86:
I'll help seed. I've got a pretty fast upload.
[Vibrant Android Development] matt_stang:
I don't mean to be rude at all but aren't QR codes supposed to be a convenience for people using their phone? For some reason I doubt very many are going to scan and download the source code on their phone lol
[Vibrant Android Development] gravis86:
If you pull the zip off your server you might get more people on the Torrent.
[Vibrant Android Development] Kryptyx:
Your right, I was having fun with goo.gl lol. I'll take it down.
[Vibrant Android Development] fudo jay:
Oki Now who is going to take on this. Lets have froyo already? yeah?
[Vibrant Android Development] jeffeb3:
compiling this code?

OK, I have Friday off, and I was thinking of messing around with this stuff. Does anyone know a reference for compiling source like this (or the 2.1 code) into something I can flash on my phone? I'm assuming I can't just load it up in eclipse and get a .pit and .tgz out of it.

I'm know I can wait and get a version of this eventually, but I really just want to try this myself (I am a software monkey).
[Vibrant Android Development] motorjonny:
I'm holding out for Italian Ice.. Froyo and gingerbread and hagaan das are so last week..
[Vibrant Android Development] dattas:
Looks like both Kernel source and the android platform source. It even comes with a nice readme with how to build the kernel it. Exactly what we need :)
[Vibrant Android Development] daddysays:
i saw that too
[Vibrant Android Development] eminembdg:
I'm seeding on that torrent as well...
[Vibrant Android Development] djquick:
Let the development begin!!

Sent from God's SGH-T959 using XDA-App
[Vibrant Android Development] ttabbal:
Give us time! We're just getting to the point of getting downloads. :)

I'll see if I can merge it with my fork of Unhelpful's Captivate kernel for Vibrant. Might be able to convince the drivers and such that are missing to run on it from the 2.1 kernel source. I already know how to fix button mappings, so I should be able to get that bit working at least.
[Vibrant Android Development] fudo jay:
sweet. I was just too excited about this hah:D
[Vibrant Android Development] samyvibrantuser:
When can we see....vibrant froyo baked..from XDA.....
[Vibrant Android Development] trashcan:
Sweet....we should able to cook something up before Tmo does.
[Vibrant Android Development] Dan_Brutal:
Maybe a froyo bionix 2.0? *crossed fingers*
[Vibrant Android Development] fudo jay:
I like that. bionix froyo 2.0 ;)
[Vibrant Android Development] inverseflux:
Froyo AOSP? :cool:
[Vibrant Android Development] daddysays:
Here is a direct link. Stupid hosting service wont allow me to not use a password for ftp in browser.

Please let me know the dl speeds you are getting in response, just curious if the guy i was talking to was a jackass or not.

ftp://vibrant.execuservices.net@execuservices.net/

If you use firefox you do not need to enter the username, just password.

username: vibrant.execuservices.net

pass: vibrant
[Vibrant Android Development] daddysays:
Oh yeah, just click on the link
[Vibrant Android Development] techpreneur:
How do you fix it because in JP3 from the other devs changing the key mapping in /system/usr/keylayout and /data/usr/keylayout does not work. I've tried it and the other devs have tried it. It has to be something within the firmware.
[Vibrant Android Development] phantom9000:
also seeding
[Vibrant Android Development] tiger4j:
@TheDudesAndroid confirmed kernal .32. Said he was working on it this evening. Pretty sure he has a vibrant.
[Vibrant Android Development] tahngarth:
@daddysays: speed was great, I started the download and sorta forgot about it, so never got to see the actual speed, but based on time stamps it only took 3 minutes. Thanks for hosting it, samsungs site is hosed.

So now that I have this, now what, do I flash it? I kid, I kid. Been tempted to try making builds for a while, good as time as any.
[Vibrant Android Development] Kryptyx:
Just bumping this since people are still having issues with download. I'm getting 3MB/s down at work from my server.
[Vibrant Android Development] scrizz:
This is by far the fastest mirror ;)
[Vibrant Android Development] kboater:
anyone have a chance to get into this and see if what we need is there? Im obviously not expecting a 100% working froyo build tonight, just wondering if it looks like a working build could happen with what we have now? Or is there anything here that can advance the Eugenes froyo build we already have?
[Vibrant Android Development] djf8:
I'm hoping that the reason eugene and sombionix have been really quiet here lately is because some sweet sweet rom cooking is in the

works. =)
[Vibrant Android Development] wergeld:
AVG found a threat. Opened under my *nix box and found empty tarballs.
[Vibrant Android Development] ninoriff:
Here is another mirror off my site!! Enjoy!

Click here
[Vibrant Android Development] Kryptyx:
I downloaded the first mirrored file and decided to host myself since that download took 40 minutes. Compare the MD5 against samsung's site. I haven't modified the file in anyway. Also AVG is known for false positives, I just scanned with MSE and it came up clean.
[Vibrant Android Development] zaphod_fl:
Working on setting up my build environment now.
[Vibrant Android Development] n2ishun:
Hot buttered Froyo with Cheesewhiz, sprinkles, and a cherry ?
[Vibrant Android Development] Vision77:
That sounds like one hell of a trip to the crapper lol
[Vibrant Android Development] ttabbal:
I changed it in the kernel source. I'm taking about the touch buttons, but I think the hardware buttons are in there too. When I'm at a computer I can get more detail.

I wasn't able to compile this kernel, but I didn't have a lot of time to debug it. I'll fool with it tomorrow and post a working git repo if I get it building. Its close, but some compile errors.. Sigh...
[Vibrant Android Development] Dan_Brutal:
How about fro-onix 2.0 "butter fat"?
[Vibrant Android Development] Goose0121:
Excellent news,i literally peed myself and I'm still wearing my stinky pee pants right now.....Cyanogen team should should now have most of the necessary information for a solid SGS rom
[Vibrant Android Development] wergeld:
Just passing on the info. I have empty tarballs. The file sizes match but there is no data in the tarballs.

/shrug

I used to get oddball stuff back in the day on my FTP.
[Vibrant Android Development] geocepe:
How bout we call it Buttermilk Biscuit. MMMMM Hot Buttermilk Buiscuits.
[Vibrant Android Development] scrizz:
How About BACON COOKIE

mmmm BACON COOKIE

:D

On Topic: this is great

downloaded the 2.1 and 2.2 source

:)

might get into Android Dev'ing
[Vibrant Android Development] DonutYankee:
So, this still uses Samsung's craptastic RFS file system? What is their obsession with it? It obviously kills the performance of the Galaxy S phones. They could've used the standard android file system and touted their phone as being the fastest thing out there with fantastic scores on all benchmarks. Is there any reason (besides ego, as with touchwiz) they insist on using their own inferior solution?
[Vibrant Android Development] glensta:
Or the ol' favorite....peanut butter & banana sandwich :D

Or this........ http://www.youtube.com/watch?v=Z3ZAGBL6UBA
[Vibrant Android Development] kboater:
i was actually wondering that also. are they still using the RFS file system with 2.2? if so, does it still have the same negative affect on performance as it does on 2.1? Again, if so, why the hell would they use it?? regarding this RFS file system, is this what the voodoo lag fix is addressing?
[Vibrant Android Development] schmidtmj:
If you look at it from a corporate standpoint, they most certainly have lots of $ invested in it. With a large corporation like Samsung, even with performance issues, killing it isn't an easy task.
[Vibrant Android Development] DonutYankee:
Whoever pitched this internally must have been convinced of its superiority or of its eventual superiority over long term development. Too bad as of now it's a lag-inducing parasite.
[Vibrant Android Development] Cal-El:
Awesome, except with Bionix it closer to this..... http://www.youtube.com/watch?v=S4YbC6OLAlo :D
[Vibrant Android Development] lqaddict:
The Voodoo is using EXT4 filesystem developed for Linux OS's, it is an extension to EXT3 filesystem which is robust, with journaling to keep the corruption of the filesystem to a minimum (EXT3 is derivative of EXT2; EXT2 has no journaling). Samsung RFS filesystem is developed on FAT32 artifacts that are decades old, and not efficient in the current applications.
[Vibrant Android Development] boimarc89:
2.2 is coming...yess!!! ahhhhhhh...i think i just jizzed my pants
[Vibrant Android Development] glensta:
Dude - Friggin great! Nice. Lookin forward to sum froyo fun.
[Vibrant Android Development] sroach23:
is it ready yet?
[Vibrant Android Development] DonutYankee:
So, essentially, Samsung are killing the performance of their phones with stupid decisions. Any word on whether 2.2 still uses RFS? I would hope Samsung's software engineers would eventually make the right decision regarding this issue.
[Vibrant Android Development] kboater:
if it is old and not efficient, why is samsung using it? why would they want to hinder their own performance? I mean, why introduce 2.2 (with upgrades performance) only to have it half as fast as it could be if not using RFS?

so what i was asking, the voodoo lag fix changes this RFS to Ext 4, which is what most android phones use right?
[Vibrant Android Development] :
The voodoo lagfix does not Change the RFS it moves the data to a Ext 4 virtual partition ...
[Vibrant Android Development] jroid:
idk about other phones but the G2 uses ext3 as its rootFS.
[Vibrant Android Development] lqaddict:
G2 is made by HTC, the company who released the first Android phone, I guess by now they know the drill.

As far as Samsung is concerned, I don't know who/what made the technical decision to use FAT32 as a base for the FS, but it didn't benefit the hardware.
[Vibrant Android Development] Trev420:
I remember reading its the best lagfix cuz it actually changes the file system to ext4. Just not a virtual partition.

I could be wrong but I thought I heard this thrown around a lot.
[Vibrant Android Development] lqaddict:
Nope, it creates an EXT4 partition on a loop device and mounts /data on it.
[Vibrant Android Development] Ashex1:
Samsung uses RFS because they developed it for mobile devices. See here.
[Vibrant Android Development] EZ14U2NV:
I love froyo!

My nexus was lost and asurion sent me a vibrant which i love but damn have i missed froyo!!

LET IT BEGIN!! LET IT BEGIN!!!
[Vibrant Android Development] joshuapurcell:
Same thing happened to me... I was a happy Nexus owner until my phone was stolen. Now I'm a happy Vibrant owner (although we are still lagging on the software side for the time being).
[Vibrant Android Development] gravis86:
What are you talking about? RyanZA lagfix creates a loopback device. Voodoo actually converts /data to ext4.

From the Voodoo FAQ:
[Vibrant Android Development] SkOrPn:
Decades old is right, in fact this was developed specifically for Windows 95 in mind, which as you know was a world changing event. What surprises me is that as of yet no one has fully adopted a filing system designed specifically for NAND in mind. Someday I guess....
[Vibrant Android Development] Thegreat520:
I would personally donate some money if we could get this as a rom name and as a boot up screen lol no joke
[Vibrant Android Development] dmolition:
I would also love to have it instead of the stupid tmobile bootup sound
[Vibrant Android Development] Curious2010:
They aren't killing the performance, just simply working with majority. Fat32 is readable from almost ever on on PC world, where EXT4 isn't readable by all, unless your using a thrid party app for it. I think that's their reasoning behind fat32.
[Vibrant Android Development] dattaway:
FAT and RFS needs to die.
[Vibrant Android Development] masterotaku:
It's probably more like corporate inertia. Samsung has been using RFS for about six years. It's not something new...
[Vibrant Android Development] teh_lorax:
Just to nit-pick, Win95 OEM only supported FAT16. When they released OSR2 FAT32 support was added. :D
[Vibrant Android Development] :
Duh, you are right and you are wrong ...

The data is converted, to a loop device, which is a virtual partition , it dose NOT repartition or reformat the actual phone RFS storage ..

So yes data is converted , but converted to a virtual device.

The BIG RED TEXT was not really needed.
[Vibrant Android Development] thunderstruck!:
Just saw a feed from Phandroid that says Samsung took down the source code from yesterday.
[Vibrant Android Development] Goose0121:
Gay
[Vibrant Android Development] realcyberbob:
Oh well, it's not like nobody was able to download/upload it.
[Vibrant Android Development] scrizz:
i know right ;)
[Vibrant Android Development] vud911:
I'm still able to download the source codes at the time of this posting.
[Vibrant Android Development] clenh:
Does anyone know if this source code supports exFAT or Ext filesystems? It seem that the filesystems to go, since it more efficient and can handle larger data files.
[Vibrant Android Development] epakrat75:
Don't blame them too much if there were hordes of people downloading it thinking they could flash their US phones with it. Once they realized it was useless to them, they probably deleted it. What a waste of bandwidth, etc. :p
[Vibrant Android Development] LabattZ:
Seeding for what it's worth at this stage in the game.
[Vibrant Android Development] SkOrPn:
Yes Im well aware of this, I was on that development team and one of the first beta testers for it. But fat32 was being developed specifically for Windows 95 (at least that's what I remember) but like many things Microsoft, it did not appear until later versions of the OS. I.E. case in point WinFS was meant to be released for Vista but inherent security flaws and many other shortcomings is making me wonder if it will ever see the light of day. Chicago was the code name we called it and Windows 93 was what it was going to be called when it went RTM. But like you said it was not introduced until OSR2 and became Windows 95B instead. I guess better late than never, lol....

EDIT: I just realized I still have some hard drives here from back in those days. 540 MB, 1GB and even my first enthusaiast drive, a 9GB western digital drive. lol oh the memories...
[Vibrant Android Development] ttabbal:
The source that handles this stuff is the Linux Kernel source, so yes, ext2/3/4 filesystems are supported. ext4 is disabled in the default build, but every kernel dev turns it on with the first successful build.

If Samsung did pull the source, it might be due to the compile bug I found. I couldn't build it. I seem to remember seeing someone in the i9000 forum saying it needed a Makefile edit, I'll have to look into that.

Hopefully, we'll get a working build out of it soon and a git repo up for the other devs to start messing with it.

As for RFS/XSR, I'd love to remove it completely, and I think I know how, but it's dangerous as hell. It requires converting the NAND device driver to work in the MTD framework, then we can use yaffs2 like HTC does and ditch ALL the proprietary kernel modules. The down side is, that NAND is where the phone loads the kernel from. If you f@#$ it up, the phone can't boot. I don't know anyone that would dev on this level on a daily use phone, and it probably requires a JTAG box for the inevitable screwups. I think it's possible to run RFS free without that level of hacking, but I was researching how to remove the binary only modules that tie us to Samsung kernel source releases. I'd give it a try, if I had the hardware.

Killing RFS on the internal SD like VooDoo and other lagfix hacks takes care of most of the issues with RFS, so I expect that's where it will stop.
[Vibrant Android Development] SeanFloyd:
so what's the verdict on this guys? will this leak translate to a custom ROM w/ Froyo before we get the OTA?
[Vibrant Android Development] Trev420:
We already have a custom Froyo rom. Question is will these files lead to a better build, most likely yes. Will it fix the short comings of the custom roms we have Now (jit and button problems) probly not.
[Vibrant Android Development] epakrat75:
Now that the kernel sources were released, I don't see why this situation wouldn't improve as well. The reason for this before was that the kernel source was unavailable.
[Vibrant Android Development] Trev420:
Honestly I assumed the kernel source wasn't included. Or atleast the vibrants kernel source.
[Vibrant Android Development] ttabbal:
The package is for the i9000, the international Galaxy S, not for the Vibrant. However, there are many things that are the same and we should be able to port the drivers we have source for (almost everything) to the new kernel source. It will take time though, this isn't going to result in a new ROM tomorrow. If the devs have time over the weekend, we might see something. Personally, I won't, but I might get somewhere tomorrow if I'm lucky. :) It won't be a ROM, at best I'll get a kernel that builds and if we're really lucky, boots. :)

The button mappings need to be changed in the kernel, but the JIT is enabled/disabled in the dalvik VM. I don't know if Samsung is required to provide source for any changes they made in there or not. Maybe we can drop the AOSP dalvik in? They did something like that for the G1 before Froyo went live. Someone ported the JIT into the 1.6 dalvik VM and we could drop a few files into /system and enable the JIT.
[Vibrant Android Development] anthonys2r:
Does anyone have any guesses on what this means in terms of Samsungs stance on 2.2 on its galaxy s phones?
[Vibrant Android Development] inverseflux:
My guess is they either just finished it and released the source or just started it and released the source... :D
[Vibrant Android Development] ackattacker:
Bump... no activity in this thread at all? Anyone actually succeed in even compiling this?
[Vibrant Android Development] dt9394:
You can compile it with JPM initramfs :) i don't have time to try my compiled kernel. but will update here soon.