yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] hurtz777:
Makelegs cm-9-20120711.1945-vibrantmtd build is working great with no bugs so far with SubZero #159 VC or Devil 0.99d VC kernels. It is amazing how fast our Vibrant runs CM9 and it keeps getting smoother! Theandroid the latest build of this CM9 kang should work fine without a datawipe since it is just CM9 nightly with some cherry picks added on. If you don't need the cherry picks then you might as well stick with CM9 nightly. Makelegs lets us have the new features\cherry picks that haven't been added or may never be added to the official CM9 nightly. If you don't like this kang then you should be able flash the latest CM9 nightly afterwards without datawipe without any issues.
[Vibrant Android Development] makelegs:
Glad it's still running great for folks. Starting to dabble in cm10, today. Be interesting to see how quickly and which devices get transitioned over.
[Vibrant Android Development] Richcar:
Hope to see a kang cm10 and thanks for your continue support and all those great skankwish cm 9 much love your work is applicated.
[Vibrant Android Development] makelegs:
JELLYBRO, anyone??

who wants to try an experimental JELLYBRO build??

seriously.....I have no idea if it will even boot. So take the necessary precautions, as usual.
[Vibrant Android Development] mohamobo:
I'm ready all the necessary precautions. Count me in. :good:
[Vibrant Android Development] makelegs:
*deleted*

got another tester as we speak. just lemme know quickly if its no good so I can kill the link, if need be.

Thanks! :cowboy:

edit: removed link
[Vibrant Android Development] mohamobo:
Running JELLYBRO build

Successful flash cm-10-20120728-SKANKY-vibrantmtd + gapps-jb-20120726-signed. :good:
[Vibrant Android Development] makelegs:
How did it "work"???

Other guy said it just rebooted during install and then got stuck in a CWM bootloop.

Weird....but GREAT!!! (I think?)
[Vibrant Android Development] mohamobo:
Steps for flashing (from CM9)

Steps for flashing (from stock CM9)

Wipe data/factory reset

Wipe cache

Wipe dalvik cache

Format system

Flash cm-10-20120728-SKANKY-vibrantmtd

Flash gapps-jb-20120726-signed

Reboot

That's all..
[Vibrant Android Development] hurtz777:
Makelegs I would like to test some experimental Jelly Bro love! Where can I get it?
[Vibrant Android Development] makelegs:
http://db.tt/0BUJf13o :)

If the consensus becomes that it works, we'll make it official
[Vibrant Android Development] mohamobo:
Already running about 3H+ now and everything look good so far.. :good:
[Vibrant Android Development] hurtz777:
makelegs the only bug with it is that the kernel causes Galaxy S Settings to display a blank screen. FE's official CM10 V8 had the same issue and it is definitely an issue with the kernel because Devil3 1.0.4 Test3 actually has working GPS and has fixed the delayed Froyo RIL issue that caused unknown baseband as well as working Galaxy S Settings. Now if you could find a fix for the external sd card not mounting on USB mount and fix the stock kernel so Galaxy S Setting won't crash I would say we have no major issues. I would say make it official and I can't wait to see what you can bring us in this CM10 kang since FE won't be making official CM10 any longer right now you are our only hope for a true built from source CM10 build for the Vibrant!
[Vibrant Android Development] makelegs:
I'll get a skanky directory set up. :)

Thanks for testing!
[Vibrant Android Development] hurtz777:
Best CM10 Combination

I have found the most stable and best performance with all major functions working CM10 combination on our Vibrant so far. SkankyJellyBro072812 + Devil 1.04 Test 3 CMC JB kernel + gapps-jb072612. Just wipe and flash SkankyJellyBro072812 rom and then gapps-jb072612 and then reboot in to the rom completely(Should take no longer then 3-4minutes to boot the first time). Now reboot in to recovery and flash Devil3 1.0.4Test3 JB kernel and reboot and Galaxy S settings will now work perfect as well as the delayed Froyo RIL and GPS will lock 3-4 satellites for the first time in about 5 minutes. I can also confirm that the Devil Kernel Config finally will hold the settings even after reboot. Unfortunately the kill app feature and Background Processes settings won't hold after a reboot and that needs fixed in the CM10 source. I have found for best performance and decent battery to run at 1200mhz with SmartassV2 governor and VR scheduler with Ultra KSM enabled and Devil Idle set to permanent. I would also recommend setting Background Processes to 2.
[Vibrant Android Development] makelegs:
It's OFFICIAL...

Skanky directory is skanky!
[Vibrant Android Development] mohamobo:
Running JELLYBRO build cm-10-20120729.0706-SKANKY-vibrantmtd

Wow downloads hits 100+
[Vibrant Android Development] makelegs:
I know, right??.....that was fast as F#*K!!!

:cool:
[Vibrant Android Development] nedlog:
Would not recommend flashing the Devil 104 kernel; my phone boot looped. Just FYI.
[Vibrant Android Development] romitkin:
Boot loops with Devil 1.03 as well.
[Vibrant Android Development] hurtz777:
Devil 1.0.4 Test3 works perfect. You have to follow my instructions above to avoid boot loop. It must be flashed after booting in to rom with stock kernel.
[Vibrant Android Development] romitkin:
That's what I did but with 1.03. Can you please link to 1.04 Test3?
[Vibrant Android Development] makelegs:
Just in case....

Since I've sorta neglected this thread for a few weeks...It's worth mentioning that skanky builds are now additionally supported via the GooManager app as well as RomManager.

The euroskank server has been getting nailed since Jellybean, so sometimes DL's have been painfully slow. The only drawback with Goo is that it doesn't necessarily refresh the ROM list immediately, but it's really good about letting you know that an update is available, once it refreshes.
[Vibrant Android Development] hurtz777:
The link to the Devil 1.0.4 Test3 kernel is below:

http://xdaforums.com/showthread.php?p=29421577
[Vibrant Android Development] nedlog:
Yeah I was on stock kernel for a couple hours. I think the 104 kernel I flashed wasn't the test kernel. At lest the file didn't say test. Will try again later. Thanks.
[Vibrant Android Development] maelstromm:
Flashed the rom based on your instructions and it worked like a charm. However, I got an issue that was also posted on the kernel thread - reboot when you toggle the GPS on if you turn it off. Do you keep gps on or off all the time? Did you get the same issue?
[Vibrant Android Development] makelegs:
Just leave GPS on. It only shows up in status bar when it's actually being used.
[Vibrant Android Development] maelstromm:
Thank you makelegs !! :good: Liking the feel of the ROM already. Will play around some more and provide feedback :)
[Vibrant Android Development] Guitar100:
I would really love to try this rom.....is there a procedure on flashing it? rom,kernel,gapps,add-ons,salt and pepper etc.?
[Vibrant Android Development] maelstromm:
Instructions in post 532 by Hurtz777
[Vibrant Android Development] awolbrin:
i'm currently on MIUI V4.

will it be easy to go back to MIUI? will i just need to reflush my old rom?

thanks!
[Vibrant Android Development] xriderx66:
derp herp.

Nandroid backup.

---------- Post added at 10:13 PM ---------- Previous post was at 10:00 PM ----------

Ok, maybe this is just me being stupid or curious but when you first flash the ROM and the "WELCOME" screen comes up, why does it say MOTHER at the bottom? call mother?

lol
[Vibrant Android Development] mryounghc:
i noticed that too. i thought it was trying to call my mother
[Vibrant Android Development] hurtz777:
It's amazing how fast and lag free this rom and FE's V8 rom is considering they are running off of the slower NAND and not the faster datadata like Devil CM10 port.
[Vibrant Android Development] Linkmeup82:
I also noticed my phone said "Mother" but I don't have a "Mother" Contact. I was playing around and wiped everything and when the phone went to first use setup the second time, I noticed it said "Friend" instead of "Mother" at the bottom that time. I've only ever noticed this on happen on this ROM. I could be wrong. It doesn't really bother me, just strange. I wonder why this could be? I really like this ROM with the Devil3 test kernel. It's really fast even without datadata in my opinion.

---------- Post added at 05:59 PM ---------- Previous post was at 05:47 PM ----------

I agree. This ROM is amazingly faster than i thought it would be. I used it with the stock kernel for a short time a experienced some notable lag but was not surprised. I then flashed the Devil3 1.0.4 test3 kernel and this ROM flies. It's insane. I was using the ported ROM that uses datadata, that thread is a mess btw, and I love how fast the ported ROM is. After using this ROM and how stable it appears to be so far, I'm going to start using this one. Much thanks to the dev. Awesome ROM.
[Vibrant Android Development] mryounghc:
"mother"it has done it to me on some ICS roms too. i am going to wait a few days before i flash this one. JB's are flying out like crazy now and so far they seem to have little to no issues when flashed correctly. i have done 3 roms in the past 4 days lol.
[Vibrant Android Development] xriderx66:
Yep. The MOTHER thing was in ICS too :)

Anyways, 3 roms in 4 days? LUCKY

I've flashed over 10 roms yesterday alone...

It was mostly just trying to fix all the issues from the cm10 port, screw that, really that thread is just bunch of BS now, this thing is amazingly fast!

Thanks to hurtz for recommending.

If you guys haven't tried it, go buy the Touchwiz 5.0 theme, it looks AMAZING, and the black exodus (free) looks amazing as well.
[Vibrant Android Development] samsgun357:
@x first off, you are a flash-a-holic! Second, how is this compared to Fe cm10? I looked at the port thread..... its a freakin wreck. I guess if nobody picks up official cm10 thread I'm going skank.
[Vibrant Android Development] xriderx66:
Well, I'm guessing you've tried the CM10 port with the /datadata?

Then you prob went back to FE's CM10 with no /datadata and found the small bits of lag?

Well this has no /datadata and doesn't lag a single bit. Use it with Devil kernel and it flies bro.
[Vibrant Android Development] mryounghc:
That is exactly what i did, i was on the cm10 port, then tried the v9 that someone threw in there and screwed everything up when i tried to revert since its actually i9000. there has to be about 3 different roms in that thread

had to odin. just went back to FE's a few hours ago. but i guess i will try this one now
[Vibrant Android Development] Drjjones426:
What's the difference between the file with 1330 and the one with 0706.
[Vibrant Android Development] xriderx66:
It's the new version (not sure whats new)

Just curious to people who have been on this ROM for a bit more than me, the update process works the same as any other CM rom, correct?
[Vibrant Android Development] Waldos:
This rom+gapps+devil test 3+ is near perfect. I have NOT lag! :D
[Vibrant Android Development] makelegs:
Nice to see everyone enjoying some jellybro!
[Vibrant Android Development] Drjjones426:
Couldn't get to boot sat at cm9 boot animation screen for 10+ mins
[Vibrant Android Development] makelegs:
Follow the directions from hurtz, posted earlier. Or re-d/l first and then follow the directions from hurtz. I think we can safely say that this build has been confirmed, at the very least, to successfully boot.

#LifeOfACrackflasher :cool:
[Vibrant Android Development] Drjjones426:
Thanks! Up and running now. I didn't reboot originally between flashing ROM and devil kernel. I think I've flashed my phone about ten times today.
[Vibrant Android Development] hurtz777:
I have found the most stable and best performance with all major functions working CM10 combination on our Vibrant so far. The latest SkankyJellyBroVibrant Build + Devil 1.04 Test 3 CMC JB kernel + gapps-jb072612. Just wipe and flash the latest SkankyJellyBroVibrant Build rom and then gapps-jb072612 and then reboot in to the rom completely(Should take no longer then 3-4minutes to boot the first time). Now reboot in to recovery and flash Devil3 1.0.4Test3 JB kernel and reboot and Galaxy S settings will now work perfect as well as the delayed Froyo RIL and GPS will lock 3-4 satellites for the first time in about 5 minutes. I can also confirm that the Devil Kernel Config finally will hold the settings even after reboot. Unfortunately the kill app feature and Background Processes settings won't hold after a reboot and that needs fixed in the CM10 source. I have found for best performance and decent battery to download Devil Kernel Config app from the market and run at 1200mhz with SmartassV2 governor and VR scheduler with Ultra KSM enabled and Devil Idle set to permanent. I would also recommend setting Background Processes to 2. I have attached the Devil3 1.0.4 Test3 kernel.
[Vibrant Android Development] skinzy98:
Could someone please pull the stock jellybean wallpapers from one of the other ROMs? Mine only has two wallpapers and one of them I've never even seen before
[Vibrant Android Development] samsgun357:
Download Fe's CM10 and extract wallpaper apk's with root explorer or whatever root file app, move to /system/app, fix permission and reboot.
[Vibrant Android Development] zeusakatkm:
I followed these instructions, it's running like a dream, Thanks!
[Vibrant Android Development] henkohan:
Finally enjoying JellyBro!

Coming from Slim ICS+Sub Zero kernel, I got boot loop too when I try to flash this ROM. I tried restore nandroid backup back to Slim ICS, flash CM9 hoping to be able to follow hurtz's instruction with no luck, still got bootloop at CM9 installation.

Slightly frustrated, I plugged out the battery in the middle of boot loop sequence (um... is it wise to do that?), plugged it in again, boot to CWM, re-flash JellyBro + gapps, and voila! It worked!!! Yay!!!

Everything is buttery smooth and I love it very very much. GPS is still a problem, (never seem to be able to get it working properly except at stock JFD/Froyo) but I can live with that. Many thanks to makelegs for this wonderful ROM.
[Vibrant Android Development] Martezgarki:
I got error trying to dl form playstore.

"App name" could not be download due to an error. Error retrieving information from serer
[Vibrant Android Development] Linkmeup82:
No problems here. Try going to settings and apps and clearing Google Play's cache and data and then select force stop. If that doesn't work, I would reboot and see if that works.
[Vibrant Android Development] Waldos:
After clearing Google Play's data, you can delete the Google Services Framework data too.

I have the same proble with other ROMs and that steps solved my problem
[Vibrant Android Development] iTz KeeFy:
Screenshots anyone?
[Vibrant Android Development] Waldos:
Is the same as CM10 for i9000 but ported tu us :highfive:
[Vibrant Android Development] chadhoard:
I take it that it is good to go and flash??
[Vibrant Android Development] samsgun357:
Yea it is OK to pull battery on boot loop. Boot loop happens often and a batt pull, recovery, reboot usually fixes it. Keep in mind sometimes first boot takes a little longer. If it boot loops again after those steps, reflashing is a good idea. I always try this before going back to a nandroid.
[Vibrant Android Development] iTz KeeFy:
Cool thanks, probably won't flash until I know what bugs to expect. I'm guessing JB has the EU Bug like ICS does?
[Vibrant Android Development] junglerumble:
Just did this and holy ****ing crap Batman! This is the fastest, smoothest, best performing my vibrant has ever been.
[Vibrant Android Development] samsgun357:
Yea good question, has anybody seen EU with jellybean?
[Vibrant Android Development] xriderx66:
Not that I know of, but tell all the noobs yes that you have.

It saves you, him, and everyone else much trouble if it actually does happen.
[Vibrant Android Development] Exel:
Uploading now. :)
[Vibrant Android Development] serendipityguy:
I am very grateful and god bless your broadband :D

I am very grateful and god bless your broadband :D
[Vibrant Android Development] makelegs:
My last build should have been from Sunday. It was auto-deleted, so I don't have a copy anywhere. Seems like a copy was shared already, though. I'm assuming that anyone else's existing repo is probably older than what I synced for that build, so I'm not certain what the point of compiling it would be. I guess the bright side is that we got that last build off just in in the nick of time before getting the axe :(

What pisses me off is that we literally only banged out 2 builds, and you Vibrant folks were downloading it at a pretty rowdy pace! The guru is using language along the lines of "dead to me" to describe Vibrant, though, so it's not looking good at all. And the E911 commit was only for CDMA phones, so that didn't help, either.

SON OF A.....:confused:
[Vibrant Android Development] robertd0619:
Still waiting for this....
[Vibrant Android Development] Exel:
Should be done, will post as soon as I get back home. :)

Mutiupload link, by the way.
[Vibrant Android Development] Moped_Ryder:
I have one that ends with:

.12112011-1323.zip

Was that the last build?
[Vibrant Android Development] Exel:
Yes, I have the update-cm-7.2.0-RC0-Vibrant-KANG-signed.12102011-1245.zip one, but.. I had it tweaked to the max with an ICS-look.
[Vibrant Android Development] Moped_Ryder:
OK - mines untouched. Ill be home in 8 hours.

Ive never uploaded any large file to share. What is the easiest service for it?
[Vibrant Android Development] Exel:
Multiupload, Mediafire, uhm.. those are the only two I upload to.
[Vibrant Android Development] Moped_Ryder:
No biggie - so long as its free - lol

If its not posted by the time I get home Ill get it up then.
[Vibrant Android Development] crazy25000:
I checked the main website of the download link in the OP, but there isn't even a folder for our phone. Am I missing something?
[Vibrant Android Development] Moped_Ryder:
Start on page four...
[Vibrant Android Development] crazy25000:
I know about the dropped support from Cyanogenmod, but I thought there was continued support through this ROM.
[Vibrant Android Development] Moped_Ryder:
http://xdaforums.com/showpost.php?p=20224468&postcount=32

CM has dropped support for Vibrant, as evidenced HERE and HERE.

As such, the EUROSKANK decision was to remove the directory in it's entirety.

Once CM dropped support EUROSKANK did as well
[Vibrant Android Development] makelegs:
Op updated

OP now updated to reflect the current status of builds. I shoulda done that to begin with, guys. Oops! :eek:
[Vibrant Android Development] Exel:
update-cm-7.2.0-RC0-Vibrant-KANG-signed.12102011-1245.zip (99.45 MB)	http://www.multiupload.com/CTF0CGUN38
[Vibrant Android Development] crazy25000:
Thank you sir.
[Vibrant Android Development] robertd0619:
Thanks for this. Just downloaded straight to my phone. My dl speed is fast tonight only took 4min. Thanks again.
[Vibrant Android Development] serendipityguy:
There is a Santa Claus early in December!!!
[Vibrant Android Development] atinm:
Just do a git rebase and remove my last Vibrant commits from vendor/cyanogenmod where we got rid of Vibrant, rebuild the kernel and then build the device. You'll get the last "nightly" that should have gone out if buildbot had been alive.

Vibrant is dead to me because I don't own one, haven't had one for months (someone had sent me a broken one so I could at least test, but that died) and don't intend to get one nor develop for this phone again for other reasons. That shouldn't stop anyone else from building this for themselves using the repositories that are there, but there will not be an official or unofficial CyanogenMod from the actual CyanogenMod team for Vibrant until E911 is fixed (by someone other than me). I removed the auto-building stuff so that Vibrant wouldn't get built again by buildbot and removed the kernel executables from device/samsung/vibrant because those were built by me and I don't want that committed to the repository anymore. http://github.com/teamhacksung/kernel-samsung-aries still has the Vibrant kernel source for whoever wants to build it for themselves.
[Vibrant Android Development] maelstromm:
Noticed that the GPS toggle being on drains battery faster than if turned off - as is obvious. Toggling the GPS on restarts the phone and I can use GPS again which his rare. Other than that, it has been smooth so far and the battery also lasts a long time on a single charge with Wi-Fi using the settings Hurtz provided earlier for the Devil Config.
[Vibrant Android Development] imilleson:
lawl xactly

---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------

Rumble is this faster than the port from the i9000?
[Vibrant Android Development] samsgun357:
Dude you're are brutal, I saw your post where you told someone his phone was bricked etc. Lol.....hilarious!
[Vibrant Android Development] lloydb9382:
" VR scheduler with Ultra KSM enabled and Devil Idle set to permanent" where ang how do i set this? Noob here Thanx ...
[Vibrant Android Development] hurtz777:
Download the Devil Kernel Config app from the the market to change all devil kernel options.
[Vibrant Android Development] xriderx66:
Don't worry I'm copying his setup and I could not find the VR Scheduler..

I did however set the Devil idle to perm.
[Vibrant Android Development] lloydb9382:
also anybody change the devil kernel setting to smooth ? would this affect performance and drain battery extensively ?

---------- Post added at 02:49 AM ---------- Previous post was at 02:47 AM ----------

where to i set the devil idle to perm ? ist on the CWM ? or in the performance setting ? could not find it guys ....:confused: thanx for the help

---------- Post added at 02:55 AM ---------- Previous post was at 02:49 AM ----------

so i went to cwm n under the devil setting i change the performance to smooth .. all i got to say is Wow ! super fast i feel like im holding a Gnex , i just hope it does not super drain my battery :o
[Vibrant Android Development] hurtz777:
I find SIO and VR scheduler to be the best performance and VR gives slightly better battery on Devil 1.0.4 Test3 kernel.
[Vibrant Android Development] xriderx66:
On the kernel config app, go towards the bottom, its above bluetooth kill

@hurtz do you have your LIVEOC target high at 1200mhz?
[Vibrant Android Development] samsgun357:
What does the devil idle perm do?
[Vibrant Android Development] Dougfresh:
I like to keep ultra ksm off in the most part but I do agree with (V)r and sio as the quickest I/O schedulers . Sio, smartass v2 100-1000 has been my favorite so far on ics/jb
[Vibrant Android Development] xriderx66:
Ey doug, what exactly does KSM do?
[Vibrant Android Development] Dougfresh:
I'll find it for ya soon but with my experience, I keep ksm and Uksm off and go with sio/s.assV2 and keep background process at two for my best performance..
[Vibrant Android Development] imilleson:
This thread talks about the devil kernel config app http://www.xda-developers.com/android/devil-kernel-config-gives-galaxy-s-users-kernel-control/
[Vibrant Android Development] xriderx66:
Where is the background process option? Can't find it. Do i need to check something before one of the greyed out buttons is available or something?

P.S. try out the TEAMWIN recovery guys, its pretty cool, a bit confusing at first but quite cool.
[Vibrant Android Development] imilleson:
Cool will do
[Vibrant Android Development] Fictional Reality:
process limit is under the dev options in your rom....
[Vibrant Android Development] Xenoism:
Hey guys :]

I was wondering if anyone experienced a...choppy cm10 boot animation? For me, it keeps freezing and then going, then freezing and going lol...it boots up just fine, but It does look rather odd lol any thoughts?
[Vibrant Android Development] makelegs:
That's not unusual at all in my experience.
[Vibrant Android Development] Xenoism:
I've never seen it either myself lol That's why I thought to ask ^^;;

At first, I thought it was boot looping, but then I noticed it was just pausing and unpausing....not actually looping. So I let it run through, and sure enough...it booted up just fine. But it boots up like that every time....very weird.