yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Br1cK'd:
When flashing different kernels I would disable any type of boot settings for OC/UV applications just to be safe. That could theoretically cause issues if the values in the kernels are different for OC/UV, and a setting is trying to be forced that another kernel doesn't jive with.
[Vibrant Android Development] ddanc1984:
Thanks. I thought about that after I restored the old nandroid and I'm usually careful to be sure the new kernels support the same speeds (I don't UV...my phone blows chunks when I try that). You're correct that it's probably a good idea to take those out and just let the kernel fire up with it's stock defaults then add any OC apps back after the fact. Will try that here in a second. My concern is that when I first installed Eugene's kernel, I think it installs a GPS fix so I'm wondering if maybe why you're still having issues with GPS after installing. I'll try it again and see what happens with my phone becuase I seem to have at least decent luck with the GPS.
[Vibrant Android Development] Br1cK'd:
The only issue is that its not locking after deep sleep. Its not a big one for me, I'm just trying to help test things out.
[Vibrant Android Development] eugene373:
yeah it might be hardware issue? odd. I see 50% working and 50% not working posts.

and we all know they used multi hardware in the phone's :(
[Vibrant Android Development] lapdog101:
The percentage holds true.. my wife gets no locks after deep sleep and i lock indoors even after disabling / enabling
[Vibrant Android Development] Danielpc:
I'm not sure that it does hold true. I bought the vibrant the day it came out and it had GPS problems. After doing one of the hardware fixes that came out, most of the issues I once had subsided. I’ve had great success with GPS on ROMs until now with ICS. I've never had problems with it not turning on after a deep sleep before.
[Vibrant Android Development] eugene373:
this is an ICS related Problem only atm.
[Vibrant Android Development] Br1cK'd:
Our GPS in the Vibrant has always been hit or miss from device to device as we all know.

I performed the hardware fix on mine some months back, and it made it marginally better.

I chalk it up to either hardware, or not having a full gps driver for ICS for the Vibrant maybe, or a combo of both.

Dunno, but I'll be happy to test **** out whenever you need it man.
[Vibrant Android Development] ddanc1984:
I tried the kernel again with CPU Master uninstalled and could not get a lock. Reloading the Passion9/GPS files to see if I can get it back again.

Just wish I was more knowledgeable on this stuff and had the time to jack with it myself but I'll just have to rely on those in the know and just test stuff. :D
[Vibrant Android Development] Br1cK'd:
You know me I'm impatient, but I have the tools to not complain about it and handle my business. :p

I went ahead and hacked the i9000 version of RC3 up for ol' Betsy here, and its flyin. Using Eugene's kernel without a problem, I haven't done deep testing, but on an intial look at it, it boots, its responsive, and haven't had a single FC. Its SMOOTH. When it feels like this, I know why I still rock this phone.

Some people in the i9000 thread mentioned an FC when you open the Gallery for the first time, I didn't get that one either.

EDIT - Forgot this part a mintue ago. Copying files from the phone to pc is faster, but from pc to phone is slower, about half the speed it was in RC2.11. (That could be just me, need confirmation) Still can't buy anything from the market, but that a minor inconvenience. - END EDIT

Oh, and my accurate battery mod thats rolling around here somewhere still works, I'm sure (maybe :rolleyes:) other sysui edits (accurate battery, date, and clock mods) will work as they are.

Muchas Gracias to Onecos, msnuser, PaulFord, and the rest that are getting ICS out here in a more than stable version for us.
[Vibrant Android Development] RobZarzecki:
good to hear the rc3 i9000 runs well with Eugenes kernel. Thanks Br1ck'd For being the Vibrant tester :cool:
[Vibrant Android Development] mr_psycho:
Yer gettin' me impatient, too. :D

Other than replacing the modem, kernel, and build.prop edits, what other hacks did you have to make to the i9000 cwm zip?

Thanks,

MP
[Vibrant Android Development] Br1cK'd:
Really not much.

I rip a lot of apps out, put some in with the associated libs if needed, facelock goes bye bye and that huge pittpatt folder in /system/vendor/, you will need the kernel module files, and any other supporting files for the kernel you are using. If using Eugene's kernel you need the glitch keymapping files.

I do more that won't effect how it works, replacing some sensor files for testing purposes after the first flash, and a handful of tweaks that I use across the board.
[Vibrant Android Development] mr_psycho:
Cool beans. It does sound like you tweak a lot more than I would. I may flash this later tonight. I'm really waiting on the next version of Eugene's kernel (3.0.16 plus fixes).

MD5 checksums show that SystemUI.apk has not changed since RC1. So, all the battery mods, and other tweaks to the status bar should work just fine. :D

MP
[Vibrant Android Development] RobZarzecki:
Thanks for the info on the pittpatt folder.gladly removed
[Vibrant Android Development] Br1cK'd:
For sure. Those are all facelock files, so if you're not using facelock, you don't need that entire directory.
[Vibrant Android Development] shinglers:
I jumped over to this rom from passion to check it out and see how it is! So far really smooth! Is the incoming call problem with passion happening with this rom( mute unmute)?
[Vibrant Android Development] RobZarzecki:
Yes. I experience the bug re: mute /unmute using this ROM
[Vibrant Android Development] Richcar:
Hey Br1ck'd i was waiting and checking all day to see if onecosmic's team would put up the vibrant port of RC3 but no luck ,can we have a copy of what you put together.thanks.............
[Vibrant Android Development] krackers:
Can this be used with froyo bootloader/
[Vibrant Android Development] ddanc1984:
I'm using 2.11 on Froyo bootloaders with no problem.
[Vibrant Android Development] DreamcastDC:
RC3 is smooth like butter.
[Vibrant Android Development] Br1cK'd:
Well, I was putting a more complete one together for you guys when I popped into their IRC channel to ask if they minded if I put out a KANG for the Vibrant community as a sneak peak until they can get their build out.

Nobody said no, but nobody said yes either, and one of their team members seemed to reply in an offended manner and not like the idea of me putting out a kang ahead of them.

So to avoid stepping on anyone's toes or hurting anyone's feelings, I won't be making my kang public. Sorry guys.
[Vibrant Android Development] Richcar:
thanks for the effort Br1ck'd really appreciated it ,we just have to wait until they are ready to put it up.
[Vibrant Android Development] RobZarzecki:
Thanks anyhow.Br1ckd. you posted directions we can follow ,I think in Eugene's thread or here..
[Vibrant Android Development] lapdog101:
@Br1ck'd

Very cool and respectful of you . Hopefully we will see it soon. On a side note have had zero issues since my double soft brick....just a freak incident i guess
[Vibrant Android Development] mohamobo:
Thanks for trying suporting us

Waiting RC3 for Vibrant......
[Vibrant Android Development] Br1cK'd:
They did assure me that they will be putting it out as soon as possible, and there was a mention of the GPS in the kernel is whats causing the hold up. So its coming, let them do their thing.

I do think they've probably had more than a few requests for it, which I know can be bothersome after the 100th time or so, and my request probably fell under that hat with them.. No worries, and yeah, the instructions I posted on how to kang it yourself are in Eugene's kernel thread for those that are interested.

And as scrizz also pointed out, you can flash the i9000 rom, then your kernel and modem, and basically you'll have it. You might need to flash one of the keymapping fixes if home and back are reversed, and edit your build.prop to reflect SGH-T959 instead of GT-i9000, if you wish to do so.

@ lapdog - Glad to hear you haven't experienced that crash again, I haven't either, so I'm with ya, just a freak incident.
[Vibrant Android Development] tvargas5248:
Ended up downloading the i9000b version flashed it with the modem and kernel and everything is working perfctly. I did get a force close on the gallery like u mentioned before (don't remember where tho lol) but everything seems to be working fine for me. Thanks for always helping with questions and fixes and everything u do, always appreciate it!!
[Vibrant Android Development] viralbug:
You're instructions were very helpful and I got RC3 working on my phone. :D

I'd like to add, you might also have to edit the update script where it checks for i9000 before flashing. I had to remove that bit to be able to flash it on my phone. And keymapping fix will be required if you're going to flash Eugene's Streamline.

Will still wait for them to release RC3 officially for Vibrant though.

The gallery FCs everytime when you go into settings. Haven't faced any other problems as such I guess.
[Vibrant Android Development] Br1cK'd:
Good call about the script, that might need to be fixed on pc's if it stops people from flashing, I forgot about that part.

I'm not getting an FC when going into the gallery settings. Did you do the factory format after flashing everything? They stated in the i9000 OP might need to happen. Just go into recovery and do a wipe now and see if that helps you with the FC.
[Vibrant Android Development] jzero88:
**** it, do it!!!

Na jp B ;)

But do you know the post number for the kanged GPS files?
[Vibrant Android Development] tvargas5248:
I only got a force close one time for the gallery it was the very first time I opened it after flashing other then that it has been perfect and I didn't have to change anything to flash the i9000b version. I did do a complete wipe before flashing if that makes a difference
[Vibrant Android Development] Br1cK'd:
Nope, I was using Eugene's kernel with the GPS files he includes, but I haven't even tested it, GPS has never been my focus on these devices, and mine has been sketched out from day one.
[Vibrant Android Development] RobZarzecki:
re Good call about the script, that might need to be fixed on pc's if it stops people from flashing, I forgot about that part

Can we simply edit the build.prop to show GT-i9000? before flashing the RC3 i9000 rom
[Vibrant Android Development] Br1cK'd:
Now that's thinking outside the box right there. Yeah I think that would work, because the script is checking the existing build.prop for the phone version, so in theory that should work.

Sent from my ICS'd Vibrant, melting all over XDA Premium
[Vibrant Android Development] RobZarzecki:
Thanks.I'll give the build prop change a shot
[Vibrant Android Development] mr_psycho:
Usually, when I install these Roms, even via the "no wipe" method, I always format /system at a minimum. If you format /system, then wouldn't the 'build.prop" file be missing? How does the script handle that, even for real i9000 users? Would the installation bomb, requiring you to restore a nandroid? I haven't looked too deeply at the script myself.

MP

Sent from my Transformer TF101 running Android Revolution HD 2.3.0.
[Vibrant Android Development] ameedi600:
how is this rom, I'm on ics passion and I want to know if this one has better battery life and faster. I basically want to know what works and what doesn't. Thank you
[Vibrant Android Development] scrizz:
I prefer this over CM9 and CM9 over neobuddy, but that is just me.

:p
[Vibrant Android Development] Glirhuin:
Any news about the RC3, guys????

Inviato dal mio Droide di fiducia!
[Vibrant Android Development] DAKIDD236:
I think they forgot about us. =/
[Vibrant Android Development] jamez243:
They just released a .1 maybe they wanted to wait for this before packaging a vibrant one?
[Vibrant Android Development] mr_psycho:
It's finally out! Onecosmic RC3.1 for the Vibrant. Just got posted about 3 minutes ago.

http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list

MP
[Vibrant Android Development] jamez243:
And I was just about to go to bed... Good thing I checked first.
[Vibrant Android Development] mr_psycho:
Btw, I just looked at the build.prop, and it's still identified as i9000. My guess is it's using the Glitch kernel, too.

Also, the modem wasn't changed. The zip still contains the i9000 modem, so don't forget to flash a Vibrant modem once the Rom installation completes.

And lastly, the SystemUI.apk is still the same as releases RC1-RC3, so any battery mods will still work.

MP
[Vibrant Android Development] SuperJMN:
What steps should I take to fix the build.prop in order to flash it? Thanks!
[Vibrant Android Development] jpelagio11:
Flashed rc3 and home and back buttons backwards
[Vibrant Android Development] paranoia_gu:
flash the r3, can not login the google account.
[Vibrant Android Development] alexdemonumber3:
Too all of those who complained about them forgetting us, seriously, thaws guys are working on their own personal free time. Be thankful for what you have and don't bag on the devs. I knew they'd get around to us :)
[Vibrant Android Development] greeneyes513:
I hope its the glitch kernal, I got 2.11 running like butter. Live oc to 105% overclocked to 1260. Using medium leakage levels. Use scrizz key map zip for the reversed keys. Gonna wait for more reports.
[Vibrant Android Development] Smartassassin:
OK, I am feeling like a noob. What am I missing. I am trying to flash this but I am having issues. I tried changing the build prop but getting same error. Then was told I need to change a script in the meta file but not sure which one.

Sent from my phone, not yours.
[Vibrant Android Development] Br1cK'd:
It looks like the build.prop was not edited for the Vibrant 3.1, so your device model will show as GT-i9000 if you flash this, simple to fix, and if you don't know how, use the search its been diuscussed numerous times in this thread.

They also left in the assert getprop in the install script. You might be able to format the system in mounts and storage through recovery and bypass this check, but if you don't want to, do the following. Download the rom to your pc, using 7zip, open the archive and browse to the META-INF\com\google\android\ folder inside the zip, and drag the updater-script to your desktop.

Use notepad++ to open it, and delete the following lines from the top of the installation script:

assert(getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" ||

getprop("ro.product.device") == "galaxysmtd" || getprop("ro.build.product") == "galaxysmtd" ||

getprop("ro.product.device") == "GT-I9000" || getprop("ro.build.product") == "GT-I9000" ||

getprop("ro.product.device") == "GT-I9000M" || getprop("ro.build.product") == "GT-I9000M" ||

getprop("ro.product.device") == "GT-I9000T" || getprop("ro.build.product") == "GT-I9000T");

Save and close notepad++, and drag the newly edited script back into the zipped up rom (7zip window). Put that zip on your phone and flash away.

Disclaimer - I have not flashed this, but I know it worked for RC3, but if you mess up, its on you to know how to recover.

******************

EDIT - Or, you could inject these files I edited for you into the proper place in the zip file. Extract them from the attached zip, place the build.prop into the system folder, and the updater-script into the META-INF\com\google\android\ folder, then copy the rom to your phone and it should be happy flashing time.
[Vibrant Android Development] Smartassassin:
I have used the search. I had no point of reference for what all to change or delete. This will help me. Sorry I wasnt as specific before

Sent from my phone, not yours.
[Vibrant Android Development] Smartassassin:
Thank you brickd. I will look at what you changed in these so I will know for future reference

Sent from my phone, not yours.
[Vibrant Android Development] Br1cK'd:
No worries, I wasn't near a pc most of the day yesterday so I couldn't get you the files you were asking for. I edited my previous post with the edited build.prop and updater-script for 3.1, hope those help.
[Vibrant Android Development] Smartassassin:
yeah, I will still look at what you did, otherwise I feel like I cheated

Thanks again. I am the type that if I see it done, I can duplicate.

Sent from my phone, not yours.
[Vibrant Android Development] Br1cK'd:
Giggitty. The changes are real basic. If you do use Notepadd++, use the compare plugin, its super!
[Vibrant Android Development] Jarmezrocks:
Hey everyone I just wanted to announce that I have made a ROM based off OneCosmics ROM 3.1 ready for download.

Basically been refining it and has been stable on 3.0 with the following additions:

Working SNS account and facebook synching - can log into the standard interface just like a normal Samsung ROM. I have the embedded Touchwiz4.x framework and jarva files all working.

Permissions XML for touchwiz 4

Updated build.prop

Infact ALL SNS accounts - Yet to test them all as I don't have twitter and or a sever and alt email accounts to synch with in the SNS interface like facebook? Anyone care to try for me?

MTP and cable USB with no crashing

Samsung Apps

Nova Launcher

Platypus Kernel

PerkasMOD coloured % battery

Samsung Music Hub

Polaris Office

and most other Samsung apps I just don't use them so didn't install them?

Has updated .OGG ringtones as well.

Can download as extra app packs if you guys are interested?

My dropbox is taking forever to upload 4 ROMS

GTi9000 Optus Aust SRJV1

GTi9000 Telstra Aust DTJV5 850mz modem

GTi9000B.JVU.EU

SGH-T959 T Mobile KB5 versions

Have made some nice custom OneCosmic wallpapers if everyone is interested?

Will post links up in the morning. I am wrecked! I did all of this in less than a day yesterday and also updated to RC3.1 this afternoon. Sleepy time for me I think

I will start a thread and Github sometime soon as I have some cool ideas to deal with FCs and low storage errors that I would like to discuss with people at some stage.
[Vibrant Android Development] greeneyes513:
Anybody figure out what kernal this is using?
[Vibrant Android Development] Drjjones426:
Platypus

sent from my deranged vibrant
[Vibrant Android Development] greeneyes513:
Thanks. Any feedback on 3.1
[Vibrant Android Development] mr_psycho:
+1 to what Br1cK'd says. He gives great advice on this point. Having a great editor (Notepad++, PsPad, UltraEdit, etc) and a comparison tool (eg. WinMerge) is just as good as gold. When comparing two files, it clearly shows you the differences or changes.

I run Linux, so I use Gedit and a comparison tool called "Meld". It's uber awesome. This is exactly what I do whenever a new release comes out to quickly see what changed (if anything) in the basic files (eg. build.prop, updater-script, etc.).

MP
[Vibrant Android Development] mr_psycho:
RC3.1 Buggy?

Well, I flashed OC rc3.1 this morning, and it seems kinda buggy for me.

Observations:

1. Lost my lockscreen.

2. WiFI and Data drops (similar reports in i9K forums).

3. Home key doesn't work.

Otherwise, it's fast and snappy. Unfortunately, #2 and #3 are gonna force me back to a different version for the time-being.

Anyone else notice any of these issues?

MP
[Vibrant Android Development] Drjjones426:
I can't say I've had any issues at all so far. Before flashing I switched the files with the ones br1ck'd posted earlier and also flashed the ka7 modem.

sent from my deranged vibrant
[Vibrant Android Development] mr_psycho:
Yeah. I already patched my files like what Br1cK'd posted. That was easy enough. I also did a Wip/Factory Default. Not sure at what point it happened, but I lost my lockscreen. When I first flashed, I had it, but restoring some of my apps in Titanium Backup, might have done it. I'll have to test more later.

I've seen others in the i9K forums also make references to some of the issues I had. *shrug*

MP
[Vibrant Android Development] DAKIDD236:
So far so good, this ROM is running great. Thanks for the files Br1ckD
[Vibrant Android Development] jamez243:
I've always had signal issues. Since the first one. It just drops completely sometimes. Sucks.
[Vibrant Android Development] Drjjones426:
Have u tried switching modems

sent from my deranged vibrant
[Vibrant Android Development] jamez243:
I've tried at least 5
[Vibrant Android Development] jpelagio11:
Can someone point me to the button mapping fix?
[Vibrant Android Development] lapdog101:
Button mapping fix.

http://www.multiupload.com/48S2EGPIWX
[Vibrant Android Development] erick3000:
is this the best ics rom for vibrant?
[Vibrant Android Development] salazar.r1:
I tried flashing the latest vibrant kernel ffrom the OP and still don't have the correct button mapping. Any suggestions?

That and the market FC is really pushing me back to NB (stripped version).
[Vibrant Android Development] gemstocks:
WIFI Hotspot is not working, cannot run Barnacle Wifi techering either, is there a fix for wifi hotspot?
[Vibrant Android Development] ykram:
ICS port ftw!
[Vibrant Android Development] DAKIDD236:
Same for me.. It sucks having to press the back button 100 times =/
[Vibrant Android Development] Br1cK'd:
File Removed
[Vibrant Android Development] DAKIDD236:
Didn't work. Thanks for the try!

It's weird that the vibrant kernel fixes the button mapping for some phones and doesn't for others.
[Vibrant Android Development] Br1cK'd:
Its akin to our GPS's being vastly different from handset to handset. I put up a new zip with different scripting, its worth a shot if you are so inclined.
[Vibrant Android Development] jereader:
I've been running it for a few days now, and I'm loving it. It's not perfect, no by far, but it is usuable as a daily driver for most.
[Vibrant Android Development] DAKIDD236:
Yeah i'll take a shot at it. It's not only the home button, the search button also isn't mapped correctly. The back button, menu button and volume rockers are all working fine.

Edit - Maybe 2 is a no go.
[Vibrant Android Development] Br1cK'd:
I took the file down, thanks for trying it, sorry it didn't work.
[Vibrant Android Development] themoose:
hey msnuser111

I think the reason GPS works in Neos ROM and not onecosmics is that Neo is still using a 2.x kernel while onecosmic is using a 3.x kernel which, among other things, killed init.d support which is making things harder.
[Vibrant Android Development] thepatman:
Yay maps, boo market - wait, where's voice search?

Great work again by all concerned!

Finding the following issues:

- Market FCs with latest version, have to Uninstall Updates to use it (yes, I have done a factory reset)

- GPS still not working (known issue, providing feedback!)

- No Voice Search, and checking Language & Input - Speech - Text-to-Speech output causes the TTS Engine to FC

- Camera looks like I'm riding a suspension-less vehicle down a rutted track. Takes a decent picture, but gives me a headache to look at. Also FFC is still screwed. Might try putting the original, rear-only, camera component back in, see how that looks...

I do have maps back, they are essential for me, so thanks for fixing that!!

Cheers

PatMan
[Vibrant Android Development] Br1cK'd:
See if pushing the file I posted in this link fixes your camera, it definitely stopped mine from doing the jitterbug.

http://xdaforums.com/showpost.php?p=20470293&postcount=195
[Vibrant Android Development] bobshute:
Was just over at the onecosmic page in the I9000 section. They (not onecosmic) are saying onecomsic is just about ready to drop RC1 with fixed video, camera, recording etc.
[Vibrant Android Development] thepatman:
Thanks! Will see if Onecosmic has an RC1 when I get home, if not I will try your fix - just to keep me occupied, you understand :)

---------- Post added at 02:53 PM ---------- Previous post was at 02:53 PM ----------

Will keep an eye on it, thanks!