yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Jasonhunterx:
Well I'm us SupervibeCM7 an I think call audio is working
[Vibrant Android Development] hitman818:
Its based off the nightly #6.
[Vibrant Android Development] advil0:
Is there a KB5 Modem Zip that is flashable via CWM 3? I'm trying to flash one and it keeps spitting out an error about needing to use Edify Scripting.

Any ideas?
[Vibrant Android Development] wizern23:
http://xdaforums.com/showthread.php?t=1036215
[Vibrant Android Development] Jasonhunterx:
Sound don't work with that kernel cuz its made for miui T.T
[Vibrant Android Development] advil0:
Thanks

-10char
[Vibrant Android Development] hur8111:
i'm like checking download link every 5 min see if build #12 has been uploaded cant wait till see it :p
[Vibrant Android Development] jashlock001:
Im on build 4. How would I get back to my stock backup of 2.2? In cwm is says some error about switching an update.zip that isnt availible in the version of cwm...help?
[Vibrant Android Development] movieaddict:
odin back to stock
[Vibrant Android Development] atinm:
Until the nightlies are working again: http://sourceforge.net/projects/teamhacksung/files/vibrant/

The changelog is at http://cm-nightlies.appspot.com/?device=vibrantmtd

We have disabled backlight notification because of freezing problems.
[Vibrant Android Development] ugokind:
hy

I turned back to #7 because 8 is not good in calling.. (I hear very well but people tell me that my voice is compressed.. very dirtorced)

so.. I'd like to know how is so different from other roms.. I mean .. how it fill the different menu in topbar.. that is able to use a toggle data on off etc.. and how to have the setting cyanogen so rich..

and.. last question.. probably stupid..if anyone tried to compile a 2.3 kernel with a 2.2 gps module of vibrant.
[Vibrant Android Development] ma0130:
CM 7.1.0? Can't wait to try it! Downloading!
[Vibrant Android Development] hur8111:
Thanks for the link! downloading now :)
[Vibrant Android Development] hur8111:
Just flashed 7.1.0 audio in call fixed as well as toggle mute fixed i guess? great work! best nightly build so far :)
[Vibrant Android Development] jdanisevich:
Latest kang feels very solid. Everything seems to be working properly (with the exception of the backlight notifications that atinm mentioned, and I tested the StatusBar brightness slider, but it didn't seem to work for me). Otherwise most of the bugs seem to be ironed out, not to mention improved benchmarks. Feels very solid and snappy. Quite impressed, can't wait for the buildbot to start up again. Amazing work Team Hacksung, thank you.
[Vibrant Android Development] shawn605:
Kang

What does KANG mean - and is it any different in terms of flashing?
[Vibrant Android Development] atinm:
KANG is just what the CyanogenMod builds are called if they aren't built by the buildbots. It implies that the person who built the build is copying/stealing from CyanogenMod (but given that it is me who put up the build, it was just me being lazy and not forcing it to say Nightly).
[Vibrant Android Development] Abu-7abash:
Downloading now, testing in an hour. Thanks!
[Vibrant Android Development] cojonesx:
I'm getting this over and over

yes I know the gps doesn't work, but its apparently trying

E/GPS ( 199): gen_timer_add_locked
D/libgps ( 199): deferred_gps_open_callback:
D/libgps ( 199): ril_gps_open:
D/libgps ( 199): send_ril_gps_open_req:
D/libgps ( 199): ril_request_alloc: cmd 01
D/libgps ( 199): init_ril_request: ril_request 0x18ab30
D/libgps ( 199): ril_request_alloc: alloc idx 0 cmd 01 wait 0x81c0de14
D/libgps ( 199): send_ril_gps_request: cmd 0x01 plen 0
D/libgps ( 199): ril_gps_wait_for_ril: req 0x18ab30 status 1 timeout 1000
D/libgps ( 199): ril_gps_wait_for_ril: +++entering
D/libgps ( 199): onError: error 24
E/libgps ( 199): RIL Request: ERROR. idx 0 cmd 0x01
E/libgps ( 199): RIL Request: Timeout
D/libgps ( 199): ril_gps_wait_for_ril: ---leaving
D/libgps ( 199): ril_request_free: idx 0 cmd 01
D/libgps ( 199): ril_gps_open: oem_gps_open request failed.
D/libgps ( 199): deferred_gps_open_callback: GPS open failed (-1). Retrying in 3 sec...
E/GPS ( 199): gen_timer_add_locked
D/libgps ( 199): deferred_gps_open_callback:
D/libgps ( 199): ril_gps_open:
D/libgps ( 199): send_ril_gps_open_req:
D/libgps ( 199): ril_request_alloc: cmd 01
D/libgps ( 199): init_ril_request: ril_request 0x18ab30
D/libgps ( 199): ril_request_alloc: alloc idx 0 cmd 01 wait 0x81c0de14
D/libgps ( 199): send_ril_gps_request: cmd 0x01 plen 0
D/libgps ( 199): ril_gps_wait_for_ril: req 0x18ab30 status 1 timeout 1000
D/libgps ( 199): ril_gps_wait_for_ril: +++entering
D/libgps ( 199): onError: error 24
E/libgps ( 199): RIL Request: ERROR. idx 0 cmd 0x01
E/libgps ( 199): RIL Request: Timeout
D/libgps ( 199): ril_gps_wait_for_ril: ---leaving
D/libgps ( 199): ril_request_free: idx 0 cmd 01
D/libgps ( 199): ril_gps_open: oem_gps_open request failed.
D/libgps ( 199): deferred_gps_open_callback: GPS open failed (-1). Retrying in 3 sec...
E/GPS ( 199): gen_timer_add_locked
D/libgps ( 199): deferred_gps_open_callback:
D/libgps ( 199): ril_gps_open:
D/libgps ( 199): send_ril_gps_open_req:
D/libgps ( 199): ril_request_alloc: cmd 01
D/libgps ( 199): init_ril_request: ril_request 0x18ab30
D/libgps ( 199): ril_request_alloc: alloc idx 0 cmd 01 wait 0x81c0de14
D/libgps ( 199): send_ril_gps_request: cmd 0x01 plen 0
D/libgps ( 199): ril_gps_wait_for_ril: req 0x18ab30 status 1 timeout 1000
D/libgps ( 199): ril_gps_wait_for_ril: +++entering
D/libgps ( 199): onError: error 24
E/libgps ( 199): RIL Request: ERROR. idx 0 cmd 0x01
E/libgps ( 199): RIL Request: Timeout
D/libgps ( 199): ril_gps_wait_for_ril: ---leaving
D/libgps ( 199): ril_request_free: idx 0 cmd 01
D/libgps ( 199): ril_gps_open: oem_gps_open request failed.
D/libgps ( 199): deferred_gps_open_callback: GPS open failed (-1). Retrying in 3 sec...
E/GPS ( 199): gen_timer_add_locked
[Vibrant Android Development] romitkin:
I upgraded from nightly #8 to 7.1.0 KANG. The phone booted up after a long time and I see "Safe Mode" on the buttom left corner. My launcher failed (Go launcher) and I've got the initial one instead, but all my apps have disappeared.

Any ideas?
[Vibrant Android Development] parmijo11:
Going good so far.

Sent from my Vibrant with CM7...
[Vibrant Android Development] atinm:
Try reflashing from here. Some modem partitions have a bad block and it requires flashing twice to get around this. Just flash again - don't go back to stock or anything.
[Vibrant Android Development] lunatikv:
So far, it is running great! Great job team
[Vibrant Android Development] Monk4Life:
Try rebooting. That seems to help the safe mode issue.
[Vibrant Android Development] Argusi:
If GPS is enabled, it does that even if you turn it off. I turned off GPS and rebooted and it was fine until GPS was toggled again. No need for it to be on at this point. Thanks for putting this build out early. Working as advertised so far.
[Vibrant Android Development] g1flasher:
flashed, all good so far, thank you atinm.

One question, I noticed I'm back on ka7 modern so I flashed my kb1, maybe it is a different deal due to 7.0.0 and 7.1.0 but upon reboot base band was unavailable and no signal. So reflashed 7.1.0. Maybe it's the modern, so il track down another to try after church. I didn't try the kb5 I have that is of cm flavor, no time at the moment.
[Vibrant Android Development] Argusi:
Also, if one of the keys are pressed at the right time during boot, it will do that. Don't remember which or when though. I do it once and a while by accident. Reboot should work.
[Vibrant Android Development] sil3ncer7:
Great build, very smooth and snappy as normal. Great work Team, Android wouldnt be where it is now without yall. Thank you for eveyones hard work.

Just outa curiosity, would flashing the 2.3.4 CM7 kernel from "theexel" bring back LEDNotification? Or would it still cause major issues?
[Vibrant Android Development] jonathanhuerta4:
Atinm, if the mute/mute off bug is fixed, I was wondering how did you guys go around fixing this issue?. thnx
[Vibrant Android Development] m2zomb1e:
really amazing rom, faster than the builds before , but I still cannot get any signal here..
[Vibrant Android Development] asatnik11:
I'm having the same problem with the CM7 KB5 modem.
[Vibrant Android Development] mulcahyd:
Anyone having data issues on build 8. The 3g would drop and switch to wifi and drop and switch to 3g etc. Ie there a fix?
[Vibrant Android Development] dxtrlabs:
Flashed latest kang works great status bar brightness works great nice touch. Also wifi downloads are completing no longer failing at the end. Thanks for the update.... Will continue testing
[Vibrant Android Development] hitman818:
Mind my posts. Didnt know tyere were bew instructions.
[Vibrant Android Development] skater4690:
So no more need for the eds backup? Its not in the files nor instructions anymore
[Vibrant Android Development] Nowaysout:
Why's that a deal breaker first off. And also, I'm pretty sure that even on other roms, battery can't be charged to 100%. it just displays 100%.
[Vibrant Android Development] Jasonhunterx:
Its a Deal breaker cuz that makes battery life even worst than wat it is an sometime it stop at 95 -___-
[Vibrant Android Development] atinm:
Yeah, not being able to charge to 100% sucks. I'll do that next, add an option to CM Settings that says "lie to user and say 100% when battery is at highest charge" for the Samsung pill eaters. For the rest, it will still only show what the Li battery charges up to of course. But why stop at 100% - I could just say 110%, that good?
[Vibrant Android Development] Jasonhunterx:
But what about charging when of that is wat i want to see the most be changed
[Vibrant Android Development] DontJoinTheDarkSide:
Using the volume rockers works but the labeling seems to be missing. Anyone else getting that issue?

+10char
[Vibrant Android Development] atinm:
It'll happen when we have a way to pass bootmode 3 to the kernel. Since this is a development thread, I am open to suggestions.
[Vibrant Android Development] gehzumteufel:
100% was always fake. Samsung made some bull**** code that made you think it was 100% charged. It never technically was though, and as such, it was just a fudging of the numbers. So to make that a "deal breaker" is just pure idiocy.

As for charging when it's off, why does it matter?

It's all integrated now, but as atinm said earlier, you can still do so if you choose.
[Vibrant Android Development] Jasonhunterx:
Charging while off matter because it charge faster when off an sometime when on it dont charge at all battery and drains
[Vibrant Android Development] cashyftw:
Put your phone in airplane mode, and charge it, whats the big deal? :D
[Vibrant Android Development] Jasonhunterx:
I know but still would be nice to have option but don't matter really still best rom out there
[Vibrant Android Development] geoffcorey:
Two things i noticed with the newest build, my ril reset, asking me to re enter my similar pin, (I don't have a logcat for this), and playing back music keeps causing a slight skip in the song, regardless of the song, and even when it's only the music player running.
[Vibrant Android Development] cal4877:
Have any of you tries the new lightsensor update
[Vibrant Android Development] gehzumteufel:
I haven't, but it's the same light sensor update that happened previously. Some commits happened that reverted it to the Samsung binary for whatever reason. The newest update reverts it back to the open source libsensors to allow for compass and light sensor to work the way it was intended.

If your phone is draining while charging, there is an issue.
[Vibrant Android Development] cal4877:
What you guys think is the best kernel for this?
[Vibrant Android Development] Soldi3rxx:
Swype

Is there anyway to get the swype keyboard working with CM7?
[Vibrant Android Development] Jasonhunterx:
There is a problem but I don't know wat it is I just got thus phone thrusday second vibrant
[Vibrant Android Development] baderfgt:
you are going to need the swype beta installer to do this.
[Vibrant Android Development] cal4877:
Nope the new update light sensor didn't work for me can't use camera
[Vibrant Android Development] apollo15rover:
Seems like so far neither Platypus or Kernel du Jour will work.. broken baseband .. tried both..
[Vibrant Android Development] darksonic:
I don't know if it's just me, but the screen temperature seems completely different on 7.1. I'm going to flash back to Nightly #8 to check.
[Vibrant Android Development] apollo15rover:
I think you're right.. not as crisp as I can get with Voodoo Color but not as smoggy as prior versions..
[Vibrant Android Development] darksonic:
For me it looks overly blue.
[Vibrant Android Development] numberoneoppa:
This ROM Is bloody fantastic so far.

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] atinm:
This might be the first vibrant build that has the color changes that were put into the other phones earlier. We basically went to stock colors. And I doubt we'll change them again, you will hear complaints about "too red" soon too - we will just ignore them because we cannot satisfy everyone and these colors are baked into the kernel.
[Vibrant Android Development] darksonic:
Ah crap, really? I thoroughly enjoy the way build 8 looks. Oh well.
[Vibrant Android Development] tsnow247:
Just use a theme.

Sent from cm7
[Vibrant Android Development] apollo15rover:
I think it's a big improvement
[Vibrant Android Development] parmijo11:
Looks just fine to me but then again my Vibrant never had issues with yellow or blue tint. Guess I'm one of the lucky ones.
[Vibrant Android Development] Devin5277:
I am having trouble with my back lights staying on while the screen Is on. Is there a way to turn it off? Using 7.1.0
[Vibrant Android Development] apollo15rover:
Hadn't noticed b4 but I have the same issue
[Vibrant Android Development] gonintendo:
can someone link me to the google apps? (or are they included in the kanged version?)
[Vibrant Android Development] pegasus912:
I'm having the same issue and am also curious if there is a way to turn it off. Everything else seems to be working great.
[Vibrant Android Development] nirogu325:
^ Another one who does not know how to use Google search nor this thread's search function. SMH.
[Vibrant Android Development] shreddintyres:
Everything running perfectly so far tho I have had issues with trying to change the modem, flashing.the cm7 modems from scrizz's post have worked in the past but I am now having issues where the phone will not get network reception when changing to any.modem, has anyone else had this issue? I might need to redownload the modems

I am running the latest Lang atimn posted earlier
[Vibrant Android Development] krazie1:
Their using different partitions so the old modems created wont work no more. I guess we wait til the modems are updated to work with the new Nightlys.
[Vibrant Android Development] :
don't change the modems for now. most of the zips in the web will break your modem. Then you have to reflash the hole rom.
[Vibrant Android Development] gonintendo:
Wasn't sure if the gapps are universally compatible or if there was supposed to be a specific version for this build.
[Vibrant Android Development] TR88:
Mute/Unmute audio issue is still there but the call audio problem itself has been fixed.
[Vibrant Android Development] shreddintyres:
Thank you for the quick response I will stick to the ka7 modem then
[Vibrant Android Development] Pmasonfirth:
What version is this ?
[Vibrant Android Development] ZeroIsntTheHero:
Woke up to a dead phone this morning. I had it on the charger and when I went to wake it up, the screen was on and it was illuminating a few pixels in the middle of the screen, but completely unresponsive. Restarting seemed to have resolved the issue; however, I went ahead and flashed 7.1.0.

7.1.0 seems pretty solid though.
[Vibrant Android Development] ZeroIsntTheHero:
Is this what version? I'm pretty sure the version is relatively obvious... 7.1.0.
[Vibrant Android Development] bigtom624:
I had an incoming call a little while ago and the person on the other end said it sounded like their was a scanner coming through. I hit mute/unmute and it cleared it up. It looks like the problem is still their. No big deal for me, I'm just glad its back working again.
[Vibrant Android Development] numberoneoppa:
Odd. Seemed to work for me. I Will double check.

Edit: seems to work fine, calling from my home phone.

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] numberoneoppa:
Edit: double post. My bad.
[Vibrant Android Development] phantomzer0:
Newest update running very stable for about 5 hours now. Mute/Unmute bug still present as reported by others. Also not getting the bightness status bar tweak to work unless there is some option to enable it that I can't find.
[Vibrant Android Development] TR88:
Really? Hm. I know the issue doesn't arise when calling someone but when receiving it's there.
[Vibrant Android Development] Pmasonfirth:
Ok let me re-word this...

Does the download link refer to a build after the nightly version of #11 ?
[Vibrant Android Development] Jackdog89:
Here you go. Click here.

The universal link at the top of the page should be the correct version.
[Vibrant Android Development] bigtom624:
You have to enable the status bar brightness in CM settings status bar tweaks.
[Vibrant Android Development] ZeroIsntTheHero:
Indeed. The 7.1.0 was just released today and includes fixes for a few different things. I was just messing with you, by the way. =P

So, that being said, it is a build generated after the #11 nightly.
[Vibrant Android Development] Pmasonfirth:
Thanks Zero' I was a little confused with the prefix 7 ;)
[Vibrant Android Development] TR88:
Video recording is very jittery, don't know if it's just HD recording but whenever I record the video is very jumpy, seems to backtrack...see it for yourself. Also doesn't appear when you're recording only after in playback.
[Vibrant Android Development] Vizone-:
So I'm a little confused. I've been following this thread for about a little over a month now. I've flashed over several updates, and experienced all the reported problems. I know about the modems using different partitions....and that kernel de jour had it's OWN nightly release to work with the partitions of the latest nightly builds.

My question is this:

I know that Build #11 was release on 05.25.11, I've been following the change log and reading people's replies on Build #12 but nobody specifically mentions Build #12. So is everyone talking about how Update Build #11 (that had all the same issues as Previous Builds #9, and #10) is now miraculously Build #12? Or am I just not seeing the DL link for this awesome update?

EDIT:

And then I scrolled up to the few latest posts and figured it out.

No need to search, I used a mouse wheel =)
[Vibrant Android Development] amwilliams9:
I have downloaded the Kang version numerous times and have not been able to install successfully. I'm a little confused. It appears that the total download size is only 74 bytes. I have continued to get error upon installing every time either via CWM and via ROM Manager......a lil' help guys!?!?!? I have tried this with two different Vibrants with no success.
[Vibrant Android Development] gamikzone:
check the file u downloaded u may have downloaded the md5sum check go to the sourceforge site and download the first file there
[Vibrant Android Development] amwilliams9:
WOW I must have caught a serious case of SOS (Stuck On Stupid)....I can't believe I overlooked that so many times LOL Thanks!!
[Vibrant Android Development] ginzberg:
I have been following the cyanogenmod work for the sgs, and vibrant specifically, since I first got the phone all the way back in July. Not until today, after all the positive reviews on the latest nightly 11+ kang, did I finally install. I had been holding off for a true release, particularly with GPS, but I just could not wait. I just want to thank all those that have been so dedicated in bringing this amazing release to our phone. Thank you to cyanogen for making this alternative asop rom a reality, thank you to codeworkx and coolya for really pushing through many obstacles on the galaxy s front, thank you to atinm for your continued work on the vibrant specifically. Thank you to the rest of the hacksung team. Thank you to koush for making the installation process stupid easy. Thank you all :)
[Vibrant Android Development] gamikzone:
lol its ok i noticed that the md5 file was 74 bytes since i downloaded the new version of this rom becuause i might switch over from miui, and your welcome :D
[Vibrant Android Development] jnagar:
Sorry for my lack of understanding, but I had thought this just meant not to try and change modems once 7.1 had been flashed. So, I went and stupidly installed 7.1 over my #8/KB5 build, and this seems to have broken the baseband/modem. I tried restoring, but that didn't fix it, nor did applying the KA7 modem to my restored #8 installation.

SO, I'm screwed and need to start from scratch?

Or is there a way to recover without needing to go through the hassle of a complete wipe/reinstall?

Thank you all, and if you didn't pick up on the earlier warnings, as I hadn't, let this serve as another warning...

Edit: Recovered from this mess. Don't know exactly what fixed it, but booted to recovery, applied KA7 modem zip, restored from nano to my working #8 build, and then applied the 7.1 KANG again. Rebooted, and voila: baseband at KA7, and I have a signal!
[Vibrant Android Development] numberoneoppa:
Alternatively, you could have just reflashed the latest KANG.

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] Pmasonfirth:
Just updated to 7.1.0 and it seems to have fixed the four front buttons remaining lit when screen is off.

However the mute / unmute bug still remains :(

Being a phone, I would presume that this bug would be top of the list :/
[Vibrant Android Development] inrelief:
I would presume you're smart enough to read -- this thread and twitter come to mind.

Radio Interface Layer and black boxed binaries.

Two topics I'd suggest getting familiar with before criticizing a well documented nightly build with condescending, passive aggressive language.
[Vibrant Android Development] Abu-7abash:
After flashing 7.1 since 5 hours now, My impretions are it's great. But to be honest this and Nightly 8 are quite the same to me. Same mute/unmute issue and quite the same handling of the battery (which is great for a GB rom). But what Nightly has and this lacks is the ability to flash a different OCed kernel and modem which I honestly have to bearing in mind my data plan addiction and the fact that well, I have to OC :D

Back to Nightly 8 for me, but still great as always HackSung!
[Vibrant Android Development] antonio91282:
this rom is nice and all but i want to get my old auxora back. im stuck and i cant get into bootloader mode. can anyone help?
[Vibrant Android Development] notverycreative:
Hold the volume buttons, take out the battery, plug the phone into USB, and put the battery back in. Odin away.
[Vibrant Android Development] djluis48:
Add this to the OP please?
[Vibrant Android Development] CM Wave:
So is 7.1.0 build #12? Just making sure before I flash it.
[Vibrant Android Development] numberoneoppa:
No, but is the newest build. It's not a sequential nightly as it's not built by the Cyanogenmod nightly bot.

Flash away.
[Vibrant Android Development] apollo15rover:
Just noticed camera zoom's back!
[Vibrant Android Development] mulcahyd:
How stable is this latest release? Im gonna flash it later possibly.
[Vibrant Android Development] amwilliams9:
Anyone else have a non-working home button?
[Vibrant Android Development] parmijo11:
How do I start the ffc on this rom, not seeing the option in this build. Was there on previous build.

Sent from my Vibrant with CM7...
[Vibrant Android Development] skarayala:
No FFC Support with the lattest kang

Enviado desde mi SGH-T959 usando XDA Premium App
[Vibrant Android Development] geoffcorey:
They said they would stop making ffc support standard and that you'd have to push a lib from the galaxy s zip to get ffc working on vibrant phones.