yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] epakrat75:
Not true. I'm on this rom - http://xdaforums.com/showthread.php?t=1131782 - The kernel it's packaged with supports working GPS (if left on) but doesn't support CM7 AFAIK. While not perfect, this state is much better than having no GPS IMO. The rom also doesn't suffer from the mute bug in my experience. Battery life also would seem to be better (again my opinion). Once these issues are corrected though, CM7 and those based upon it may become superior / my daily driver. I'm glad to see CM7 coming along so well for the Vibrant. Great work, guys!
[Vibrant Android Development] xriderx66:
Guys.

#37 is out.

Which one would be better to flash? RC1 or #37?
[Vibrant Android Development] whoamanwtf:
If anyone could PM me the answer to this it would be greatly appreciated. I have flashed a few GB roms and so far Revolution works I can install all my apps from tit backup and what not.. When I installed MIUI or CM7 however it doesn't install probably 51 of my apps, it will go through the motions but they are just not on my phone.... On Froyo or Revolution (which is GB) I have all my apps.. I come from a EVO so I really miss CM but I need my apps, is there a fix for this?
[Vibrant Android Development] thenaut:
I just read all the posts, so i know this hasn't been asked. I'm on GB revolution rom with the GB Bootloaders. do i need to go back to Froyo Bootloaders before i install RC1?
[Vibrant Android Development] epakrat75:
ODINing back to an RFS GB rom beforehand should be enough, the file systems between CM7 and that rom differ AFAIK. Going back all the way back to Froyo would work to do but is likely unnecessary / more complicated.
[Vibrant Android Development] twistkill:
As the change-log mentions there is not much difference between the RC1 and #37. If you haven't flashed RC1 yet, you might as well install #37. If you have already installed RC1, stick with it until something substantial is updated.
[Vibrant Android Development] archie53:
No you don't. I have the GB bootladers and have gone to jfd, 2.2 ka7, and on cm7 with them. In the OP for the bootloaders it states they are backwards compatible for all Roms, just remember that is a different key combo to get into either download mode or recovery.
[Vibrant Android Development] thenaut:
Thanks, to both replies. I went ahead and went back to the froyo bootloaders. then I odined to stock, re-rooted, then flashed RC1... and it's booted up no problem. thanks again guys

also, i've seen many posts about the Mute / unmute bug. and the information all seems to be inconsistent. it's gone, it isn't gone.... do we have official word on the status of this bug? in the meantime i'm gonna try to test it myself.
[Vibrant Android Development] Roc327:
So I just installed CM 37 and it says I am roaming, also notification area says "International data roaming". All the nightlies that my modem has worked in have said this. Is this a known problem? Any ideas for fixing this error?

Thanks.
[Vibrant Android Development] Paging Dr B:
I too would like to know. It's the only reason why my wife's vibrant is on stock right now. She's not very tech savvy but she's been complaining about the lag. CM7 will cure that but she didn't want to deal with the mute/unmute like I did.
[Vibrant Android Development] scrizz:
put her on trigger for the time being.

;)
[Vibrant Android Development] thenaut:
it's been reported that i sound like a robot, i hit mute and then unmute and then i was heard perfectly. the bug is still present
[Vibrant Android Development] bobbbb:
it depends, on several previous builds I would go for a few days with no issue and then it would randomly reappear/disappear... not sure what the hell the problem is.
[Vibrant Android Development] boodies:
gps still doesn't work? I thought cynongen was da ****. Werent' these the same guys asking us for donation money when the sgs 1 first came out?
[Vibrant Android Development] Paging Dr B:
Not a bad idea. I loved trigger when I was running 2.2 roms.
[Vibrant Android Development] Kaik541:
you should not use GB bootloaders with CM7. follow the wiki instructions which clearly state to flash from froyo.

it's not unnecessary. using gingerbread bootloaders breaks external SD card access (as well as other, undocumented things possibly as there is a reason we don't use them)

go ahead and fix it then if it's so easy. clearly you are more intelligent than these devs, so it should be what? five, ten minutes to fix? we'll wait for you to fix it then.

and no, teamhacksung never asked for money to start work on the ROM... on top of that, even if they *did* it's still a DONATION, as in, it's a request not a demand. if you feel like donating, go ahead... if you don't, don't donate. cyanogenmod has and always will be free.
[Vibrant Android Development] dbacchus:
Well, if that's true, the use of 'RC' in the title seems unjustified. That is, if the 'release' is planned to be free of the bugs/limitations above, of course.
[Vibrant Android Development] atinm:
No, we never ask for donations. Ever. Donations are a voluntary thing that users do - we don't care, that is not why we work on this.

And we are da ****. But if we don't have source code for proprietary hardware, nor any way to reverse engineer it, we can't do **** either.
[Vibrant Android Development] atinm:
All releases are planned to be free of all bugs. Reality forces us to accept what we can do and our hands are tied on things that we don't have code for, nor documentation for and so no, it will not be free of all bugs/limitations. If the code is stable, if the release is usable as a daily driver for most people, it will get the "stable" designation. We will continue to fix bugs that we can fix.

*BUT*, if you feel so inclined, all the code is available on github. Have at it and fix the bugs that are problems for you. Thanks.
[Vibrant Android Development] djjeesh:
people told me this while i was miui .. bad modems?
[Vibrant Android Development] boodies:
Dude.. FU. With an attitude like that I want nothing to do with your roms. Dip ****s like you with anger issues are the reasons why people will instantly switch to Bionix if they ever release it. As for me, no thanks. Keep your cyan roms.
[Vibrant Android Development] hitman818:
Its not really kaik's rom, it atinm's.
[Vibrant Android Development] epakrat75:
Indeed. Ignorant ingrates (especially those that say FU) don't make for happy devs. :rolleyes:
[Vibrant Android Development] master.peterm:
couple of Questions (OP preferred :) )

1. Is it safe to install this (after wiping of course) over a froyo rom.

2. Any chance of losing my IMEI or /efs folder????
[Vibrant Android Development] shreddintyres:
i installed with out any problems to the /efs folder, however that said it would not be a bad idea to go ahead and make a copy of your efs folder on your desktop just in case. something does happen. i copied and zipped it and put it up on dropbox in online storage just incase something happens to my hdd, that way you have redundancy incase something goes wrong.
[Vibrant Android Development] Kaik541:
1. the only "official" upgrade path is documented on the wiki (wiki.cyanogenmod.com), but it should be fine flashing from most (any?) 2.2 based ROM

2. CM7 does not actually write to your real /efs partition so even if something goes tragically wrong, flashing back to stock should fix it. the process merely copies and pastes the /efs partition into a folder backed up onto your sd card (and then maps it into a new /efs partition). but it's always considered a good idea to make a backup of your efs and have it stored in multiple locations just in case

you'll be sorely missed. deeply. I gave attitude because you started with the attitude.
[Vibrant Android Development] rogerchew:
easy fix....grab a voodoo enabled kernel, and just flash that over a stock KB5 ROM. you get stability and a boost in speed
[Vibrant Android Development] cashyftw:
He didn't give you attitude, your just an asshole.
[Vibrant Android Development] master.peterm:
alright thanks guys, btw just asking for a friend..... back to G2 land :)
[Vibrant Android Development] cpittman:
@atinm and @kaik541

i know it means nothing but let me apologize on behalf of the vibrant community for all of the disrespect and the gross sense of entitlement you guys face from users on our forums. many of us understand and greatly appreciate the time and effort you guys put forth in order to support a phone that means absolutely nothing to anyone on your team. you have far more patience than i and for that i commend you.

@everyone else

if you don't have anything constructive to contribute LEAVE. if you're not contributing to the development process you don't belong here to begin with. post your opinions in the general forum and questions in the q&a section so those of us who understand the enormous undertaking these guys have taken on can contribute useful information to the process.
[Vibrant Android Development] suchavibrantthang:
+1 the greater good...
[Vibrant Android Development] s1lenz:
sorry to ask another gps question, but is gps functioning on cyanogen in any way tied to getting gps working on gingerbread? or because it is not a vibrant rom, does that make it irrelevant and gps will never function on CM7?

Thanks.
[Vibrant Android Development] cpittman:
no it is not functioning. samsung tied gps to the modem & ril which means it is tied to proprietary framework. without source for their gps driver these guys have to reverse engineer everything. it's sort of like buying a 10,000 piece model with no instructions and then trying to build it.
[Vibrant Android Development] flipper2006:
I was using RC1 today and had a new issue pop up that nevre happend before. I was in car and using bluetooth (built into car) and my telephone call was disconnected and phone rebooted. I tried this 3 times in a row (after 1 minute the call would disconnect and phone would reboot). I'm able to stream BT audio without any issue in car so it's something new added in the phone routines???

I been using nightly's for months..
[Vibrant Android Development] CTown:
I understand that GPS does not have to work in order for this to go stable. But, will the compass point in the correct direction before CM7 for the Vibrant is complete?
[Vibrant Android Development] movieaddict:
As Cpittman already said this Ty @atinm and @kaik541 so much for all ur hard work! Some people can be rude and we know u do this on ur free time. Some developers have left XDa due to peoples rudeness so I applaud u for ur dedication and work for cm7!
[Vibrant Android Development] atinm:
This is not "attitude"? An outright false accusation about us asking for donations when sgs 1 came out, on top an insult about our competence?

teamhacksung has *never* asked for donations and never will. Take your attitude elsewhere - we do not do this for people who give us attitude, the work is hard enough, and we do it for nothing, but expect plain civility. If you want to give us attitude, show us what you can do. Otherwise shut up, and go elsewhere.
[Vibrant Android Development] atinm:
Try doing figure eights in the air with the phone before you turn on compass. It takes a little dancing to calibrate the stupid thing.
[Vibrant Android Development] atinm:
Pull off the /proc/last_kmsg whenever you hit a reboot please - or as I am bound to say "/proc/last_kmsg or it didn't happen".
[Vibrant Android Development] Kaik541:
all thanks belong to atinm and coolya (as they're the devs with vibrants), I'm merely trying to keep things on track and keep up to date with potential bugs to update the FAQ's with and try to address and help issues when I can.

the only thing I really can't stand is just people being rude toward the people who make this ROM selflessly and try their hardest to fix things, yet just respond with callousness. if the ROM doesn't meet your needs, we're sorry and suggest you go to one that does until we can provide the functionality you need (of which the devs are sincerely trying to get working). we gladly listen for constructive criticism and input, but hearing "GPS is still broken" 100 posts in a row followed by 100 more posts of "mute/unmute issue" doesn't provide anything useful to us. open a bug report on the issue tracker now if you must, but only if you're running the RC1 build--NOT a nightly.
[Vibrant Android Development] Phateless:
Hear, hear!
[Vibrant Android Development] HeadOfMax:
I had been waiting for quite some time to update to CM7 and am very happy that I finally did.

I came from eugines gingerclone RC2 which was also awesome btw and when I tried to update through rom manager it would not verify the image before flashing. I toggled image verification and it went through the motions of flashing and said it was successful however it booted into my old rom. The flashing process took all of 5 seconds so I figured it really did nothing. I ended up using Odin to go back to stock and updating the phone through kies before the new rom would take. I followed the instructions on cyanogenmods website and all is now well.

I must say I thought eugines rom was fast this is out of this world. I am not having any problems receiving calls. My download speeds seem to be faster now somehow and I am getting an h sometimes instead of 3G. I know the modems in these do not support 4G or hdspa+ and really wonder why this is. I am in Chicago where T-Mobile has 4g coverage.

One other thing that bothers me. I can not get ad free to update. It keeps saying that it is too old of a version and needs to be updated but will not update. I have uninstalled and reinstalled to no avail. Anyone else have this problem?

Sent from my Vibrant running CM7 with the XDA premium app
[Vibrant Android Development] d33dvb:
Kaik, I am not one to complain, but I wonder, is it bugging you guys or helping if we pastebin and send you logcats on the issue. If we can teach this disfunctional group to be helpful maybe it would be to our advantage.

That being said, here is a pastebin of the logcat for GPS from Build #31, the last time I ran one, Im not a dev, but just reading it seems like its not decoding the data correctly. I wish I could help, someone else should take a look. We need some developer from the vibrant community to step up and help out the CMSGS team.

http://t.co/DBHkN6E

Specifically this data:

D/gpsinterface( 193): year:0, month:0, day:0, hours:0, minutes:0, seconds:0, millis:0, Timestamp:2029929088000

This data shows I think that it defaulted to 0's because it is not decoding the timestamp correctly? Wish I knew more to be able to look at the code as to why. How would I look at the source for the gps stuff on the vibrant, should I go to github and look through what exactly? I would just like to know, just in case my annoyances become too great that I decide to learn something new to help out.

Now on the other hand, and I am not even sure that it is that useful. But here is a pastebin of a functional GPS from Project V.

http://pastebin.com/b2uVcpHC
[Vibrant Android Development] atinm:
If you notice, there are user space binaries talking directly to RIL for GPS (a wtf if there was ever one). That's the part we're missing.
[Vibrant Android Development] ironlood:
Would it be possible for us to all petition samsung for a dump of the source for the vibrant.

I mean there was a dump of the T-959v source not too long ago, whats stopping them from dropping the T-959.

Maybe if we all asked nicely on the samsung official twitters as well as customer service lines they may dump.
[Vibrant Android Development] Cesarp 24:
@ atinm why with build #25 the battery is so good meanwhile with RC1 its drains much faster. I left it untouched fully charged last night and when I woke up I was at 35%.

Or am I bugging out?

Either way thanks for cm7 still the best for my vibrant.

Sent from My CM7 Monster
[Vibrant Android Development] Kaik541:
give rc1 a day or two to calibrate the battery. I always find the first drain to be amazingly fast and then back to normal after charging back to full
[Vibrant Android Development] Cesarp 24:
I guess you are right I probably need to be more patient. Lets see what happens.

Sent from My CM7 Monster
[Vibrant Android Development] hoott:
Just would like to chime in with my appreciation for what you guys provide. Thank you! And I think it would be easier if you just ignore any irrational posts, they'll go away once no one is responding to their childish games.
[Vibrant Android Development] krntehknik303:
**** riders and haters.. kind of getting old don't you think?
[Vibrant Android Development] atinm:
No one dumps the closed parts - ever. Android is in two parts, kernel and android framework. Kernel is under GPL and so the manufacturers are bound to release the source (but some parts are moved into user space which aren't, and some of that has happened on SGS phones). The Android framework is under the Apache license, which allows people to close any mods they make, and that no one releases (TouchWiz for example, or Sense).

Samsung did say that they cannot release some of the source because they are bound by NDAs with their partners who provide the chips we're missing - like Audience for Captivate, the GPS chip for Vibrant, etc and it is clear that there are multiple restrictions such that effectively the only source that gets released is source that they are contractually bound to release under GPL.
[Vibrant Android Development] d33dvb:
Thanks for replying atinm, just trying to understand and ultimately get to a point where I can contribute.

Can you point out a "diff" of where it is talking to those parts and where it is not in the cm7 log?

Just trying to understand what Im looking at, if you dont have time, i understand, any place you can point to where I can learn fairly quickly?
[Vibrant Android Development] flipper2006:
Atinm, That is chinese to me. explain better please.. What do you need for me to do? I have since loaded 37 and i didnt have a chance4 to duplicate it in my car but im able to make a phone call and it doesnt reboot. I will try tommorow in car. Also.. unfortunately, tin can is still there, once i mute, and its much better.. I called my house phone from cell phone and vise versa, only when i answer the cell phone does it have the problem, when i initiate from cell, its ok sound.
[Vibrant Android Development] ironlood:
Thanks that clears up a lot. This is probably why Google is pushing towards cleaning up fragmentation and getting plenty of uniform standards on both hardware and sowtware.
[Vibrant Android Development] Demetris:
Phone was on flight mode + sim out + screen switched off+no external sd card.

After aprox. 24 hours of full baterry i have 46%.

See Uploaded picture.
[Vibrant Android Development] ironlood:
Now that's some horrific drain ... i had a vibrant with its sim pulled out and on... idling for almost 48 hours and was only on 72% battery ... id say 48 hours for 28% battery loss is pretty dam good
[Vibrant Android Development] movieaddict:
+ 1 to that
[Vibrant Android Development] kevinngu:
love cm7! i can't wait for gps support. then im on it! :D
[Vibrant Android Development] _-..zKiLLA..-_:
Cant flash this :( get some weird error
[Vibrant Android Development] te_quiero_forever_girl:
This rom is not for the GT-I9000 (international version of samsung galaxy S). It's for the Vibrant Samsung galaxy S (T959)
[Vibrant Android Development] normi2k5:
The only thing keeping me from this is lack of MKV support !
[Vibrant Android Development] Cistoran:
I followed the instructions in the wiki

When I selected Delete User Data, Cache etc.. and then hit OK to reboot into recovery. It rebooted into recovery but it just sits there. Should I select something or should it have done something?
[Vibrant Android Development] Droidicus:
At this point I would just install via recovery. Go to "install zip from sd card", toggle down to "downloads", it should be there. Be sure to write dalvik cache at a minimum as well.
[Vibrant Android Development] Cistoran:
It won't let me, I try to go to reinstall packages and it says something to the effect of unable to verify full signature or something.
[Vibrant Android Development] Droidicus:
ITry downloading again. Seems you have a corrupt file. Once it downloads you can reflash via recovery again if it doesn't work in rom manager.

The full path is as follows when in CW recovery:

install zip from sd card

choose zip from sd card

clockwork mod

download

download.cyanogenmod.com

That should be the latest rom you downloaded.
[Vibrant Android Development] _-..zKiLLA..-_:
But on the side of my box it says T959 and its definitely for t-mobile in the us. :confused:
[Vibrant Android Development] Cistoran:
How am I supposed to get into CW Recovery? I know Recovery you boot up with Vol Up & Vol Down held down. The only options I see are like Reboot phone, install package, wipe user data, wipe cache and one other I forget.
[Vibrant Android Development] Kaik541:
your phone is identifying itself as an i9000 (see how your xda signature says i9000?). this is why the wiki instructions are the only official ones. if you're going to install the ROM, please follow those instructions.
[Vibrant Android Development] Droidicus:
So, wait, do you have clockwork mod installed on your phone? Sound like your are getting into samsung recovery when you do the 3 buttona, is that correct?

if so you need to install clockwork mod first...
[Vibrant Android Development] Cistoran:
I have ROM Manager installed, I go in, click Flash ClockworkMod Recovery, select Vibrant (MTD) and hit Yes and select ClockworkMod 2.x. It says "ROM Manager has been setup to use your existing recovery installation."

I then click Reboot into Recovery, and it reboots and just goes into the default samsung recovery screen.
[Vibrant Android Development] Phateless:
Try reinstall packages two or three times. If that doesn't work, odin back to 2.1 and try it again. That's	what I had to do.
[Vibrant Android Development] Cistoran:
I uninstalled and reinstalled ROM Manager, flashed Clockwork Mod, and clicked boot into recovery. I went to reinstall packages and it says this.

Then it just goes back to the recovery screen settings.
[Vibrant Android Development] droidfan77:
You want to select ClockworkMod 3.x and then it should work fine.
[Vibrant Android Development] Cistoran:
This doesn't work either, does the same thing as above post.
[Vibrant Android Development] laylovj:
Just flash it with the green CWM. worked for me.
[Vibrant Android Development] atinm:
It really won't kill you to follow the instructions. The OP has the instructions that actually work. Follow http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide

You need to be starting from a Froyo 2.2 that has CWM already installed on it. The Samsung recovery in froyo does signature checking and that is what is failing.
[Vibrant Android Development] droidfan77:
I had this problem as well. The way I fixed it was to log in to the market through my laptop and installed adfree that way even though I already had it installed on my phone. It pushed an updated version to my phone and everything seems to work fine now.
[Vibrant Android Development] Cistoran:
I fixed my issue with a lot of googling. Apparently Samsung Recovery 3e does Signature Verification, found a program that disabled it. Flashed CWM Recovery onto it and am now flashing Cyanogen.
[Vibrant Android Development] Nabeel10:
So is nightly #36 RC1 or is RC1 something else? I can't find this answer so please don't scold me

Edit: Nevermind figured it out, but. OP just state it
[Vibrant Android Development] movieaddict:
This version is a release candidate, but you will find it stable for everyday use, thats wht they say about rc1.

All releases are planned to be free of all bugs. Reality forces us to accept what we can do and our hands are tied on things that we don't have code for, nor documentation for and so no, it will not be free of all bugs/limitations. If the code is stable, if the release is usable as a daily driver for most people, it will get the "stable" designation. We will continue to fix bugs that we can fix.