yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] MINUS Stl:
This is after choosing Vibrant (mtd) and (2.x) in Rom Manager, following all the steps....

Finding update package...

Opening update package...

Installing update...

checking state of BML/MTD...

assert failed: run_program("/tmp/updater.sh") ==

0

E:Error in /sdcard/clockworkmod/download/download.cyanogenmod.com/get/cm_vibrantmtd_full-50.zip

(Status 7)

Installation aborted.

tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.

Last time I had cm7 on my phone was a few months ago (old install method), but reverting back to JFD (from cm7) caused a whole lot of issues (which I can't get rid of and I'm still dealing with).
[Vibrant Android Development] nedlog:
Not sure it would make a difference but select 3.x and say yes.
[Vibrant Android Development] CTown:
I think this is what you are looking for (use "The old CM7 install files" link):

http://xdaforums.com/showthread.php?t=1103614
[Vibrant Android Development] glenelgstudio:
I dont know too much about resolution but if you hold a Vibrant next to a Sensation the Sensation looks like crap. I also did the same with the evo 3d. The Sensation has the specs but the display can not compare with the Samsung super amoled. Dont get me wrong at certain angles the sensation looks great but the samsung is good at all angles. I'm waiting on the nexus prime or any new samsung dual core on tmobile. The sensation is a nice phone but I will pass
[Vibrant Android Development] notverycreative:
The GPS chip stays inactive and unpowered unless you're using an app that requests it (Navigation, Maps, Grindr, whatever). Our GPS chip always stays powered off because we don't have working drivers ;D Why would you want it to be active when you aren't using it?
[Vibrant Android Development] atinm:
Pick 3.x. Then if you still get the issue, do attach the recovery.log like the message is asking. Also, try just doing it from CWM directly by going into 3 button recovery.
[Vibrant Android Development] nedlog:
Atinm I read and downloaded the official Gingerbread release for the I9000 do you already have this .rar and would it help at all with the Vibrant? I may be way off on this so excuse me if I sound ignorant. Thanks

http://thetechjournal.com/electroni...-2-3-2-gingerbread-for-samsung-galaxy-s.xhtml
[Vibrant Android Development] cashyftw:
This is old.

Sent from my SGH-T959
[Vibrant Android Development] geoffcorey:
The devs are pretty much on top of things as soon as they are announced/posted.

Plus, that "official" release isn't the latest version (the i9k gb official is 2.3.4), and therefore pretty old.

PS, this post is in no way trying to sound mean/rude/sarcastic.
[Vibrant Android Development] nedlog:
Cool, thanks.
[Vibrant Android Development] zhuzf:
Birgertime has just got GPS working on his CM7 based ROM. Is it helpful to solve the GPS problem of CM7 official ROMs?
[Vibrant Android Development] hitman818:
Its a half assed gps.
[Vibrant Android Development] Kaik541:
that absolutely destroys battery life as well.
[Vibrant Android Development] disgustip8ted:
anyone getting a bootloop on the #50 nightly?
[Vibrant Android Development] larrisa12002:
CM7 nightly50 bluetooth working

Bluetooth HID mouse WORKING!

Bluetooth HID keyboard WORKING!

Great work! Thank you! Thank you!
[Vibrant Android Development] disgustip8ted:
well after removing the sdcard and reinserting it and beating on the vol up/down and power buttons it booted into a clockwork recovery with blue lettering when the normal is orange. flashed it again and it booted.

odd

this is my g/f phone, didnt want to have to odin back. stuff is so much easier on my nexus one
[Vibrant Android Development] bearsfan85:
the rom has been out for about a day...

using his rom I had no issues with insane battery drain 2.5 hrs of minimal use with only 8 percent battery drain on a completely uncalibrated battery
[Vibrant Android Development] nedlog:
I'm on the latest nightly and the changelog mentioned some about the recovery display, my text is blue now, so I don't think yours is abnormal.
[Vibrant Android Development] nedlog:
No, installed over the air and everything went smooth.
[Vibrant Android Development] Phateless:
Do a quick Google search for "mytouch 4g good screen bad screen." It took me 6 exchanges to get my good screen phone with no hardware issues.

Btw my recovery on the Vibrant is also blue now.
[Vibrant Android Development] geoffcorey:
But birgirtime's gps fix is one that atinm m added a bit ago with no luck + horrible battery drain for the majority of vibrant CM7 users, hence the removal of it from r CM7 baseline code.
[Vibrant Android Development] vahdyx:
So I have a question, I'm currently at JFD rooted, I have rom manager premium and when I try to flash recovery Vibrant MTD it does it, but I can't get into clockwork recovery at all. It stays the stock recovery. I'm not sure if I should proceed or if I should install the original recovery then try to get MTD going afterwards
[Vibrant Android Development] numberoneoppa:
No updates in the changelog since yesterday? That's unusual. :(
[Vibrant Android Development] Phateless:
Revert to 2.1 (I'm bad with the letters) and do what you just did. In recovery choose reinstall packages. You may have to reinstall packages two or three times in a row to get into clockwork.
[Vibrant Android Development] vahdyx:
I don't quite know what your telling me, but what I did was I flashed CWM but instead of choosing Vibrant MTD, I choose Galaxy S Vibrant and it flashed and then I tried rebooting to recovery from the app and it worked. Then I flashed Vibrant MTD after that and proceeded as instructed. It worked. I'm running CM7 Nightlies.

I hope this is a better suited daily driver than Revolutionrom, Asgard and SimplyHoney.

Well the only prob I had with those other GB roms was phone and FC's
[Vibrant Android Development] a2296455:
I REALLY don't understand why there are 10 other developers stealing CM's work and just repackacking it without contributing ANYTHING to the gitgub and even more shameful are those mods out there (and there are SEVERAL) who actually have fixed GPS/Mute/unmute and aren't contributing with atinm to github and coding with them.

what a travesty.....especially considering atinm doesn't look to be developing anymore for SGS1
[Vibrant Android Development] Binary100100:
I'm certain that atinm has looked into the GPS fixes that you mentioned very carefully. He had even mentioned that they are concentrating mostly on SGS2 for the time being until the code is released for the GPS from Samsung. Since it is closed source there isn't a whole lot that anyone can do. So when the source becomes available (or a reliable fix) I'm sure we will see some advancement. But in the meanwhile just enjoy what you have now and be patient. If you can't then you're welcome to move onto something that will make you happy. It's your choice really and no one is going to sweat it if you decide to use CM7 as your daily driver or not. I constantly bounce back and forth to Bionix Roms and CM7. It's a bit of a hassle having to ODIN each time but I don't complain about it. I don't even complain that there hasn't been an up date to Bionix NG2 is several weeks. Why? Because I don't feel that it's necessary to try to rush to fix that what isn't broken. In the case of CM7 we just can't simply fix what is known to be broken not because of the lack of time, effort or knowledge but because of the lack of resources which cannot be helped.
[Vibrant Android Development] movieaddict:
+1 to that binary

Theres also nothing new added to #51 if anyone is curious, just to let u know!
[Vibrant Android Development] michaelh99:
Sorry if this has been covered. I did a thread search but only came up with the mute/unmute problem posts.

I've just discovered that I'm not receiving vmail notifications. Most of the time I get a call I'm near my phone and answer it. At least two times this week I've been left vmail and didn't know it until one of the callers reached me and asked why I hadn't replied.

Anyone else have this problem? I'm on 43 now but I think I was using 32 when the vmails came in. I'm also on tmo if that matters.
[Vibrant Android Development] gatorbob:
birgertime phone.apk

When I try to install birgertime's phone.apk from page 572, I get a FC during install, and then the message app not installed. What is the correct way to install it, and is the version on 572 the best one? Thanks.
[Vibrant Android Development] xplanowestx:
These so called "fixes" have been looked at by Atinm and he's stated the reason he has not included them is due to the fact that he does no agree with the hackish methods they have been using to implement them. Read through the forum a bit and you'd notice there has been plenty of conversations regarding this.
[Vibrant Android Development] bigtom624:
What I did was use Root Explorer to move it to system app. As soon as I do that I got a f/c then I rebooted and in recovery I fix permissions and it worked for me after that.
[Vibrant Android Development] vahdyx:
So I have been playing with this for about 10 mins now and noticed, I can't access my external SD card. Is it something I did or the ROM itself?
[Vibrant Android Development] Romanbb:
Before you call anyone out on anything, please try and understand what is actually going on.
[Vibrant Android Development] notverycreative:
I'm using Google Voice for my voicemail and it goes through fine.
[Vibrant Android Development] atinm:
The GPS "fix": I'm going to leave put up for people to run with in the next nightly and see for themselves if it fixes anything (mostly because I want more people to test it). If your phone starts to misbehave, please pastebin your logcat. If it works, let us know also.
[Vibrant Android Development] effy_t:
Thanks,

I've finally upgraded to CM7 rom (Trigger Redux based on build #49 I guess) as I'm using my phone GPS on a daily basis.

Today I've used the GPS for ~2 hours (~1 hour each direction), got a lock in <5 minutes and lock was kept all along just fine (with navigation using Waze fully functional).
[Vibrant Android Development] Phateless:
Fwiw I tried trigger this morning and couldn't lock a single satellite.
[Vibrant Android Development] vahdyx:
Figured it out. Lol I should learn to read FAQs more.
[Vibrant Android Development] codeworkx:
It's fixed and ready for flashing now. Have fun.

btw... hello vibrant forums. :-P
[Vibrant Android Development] cashyftw:
Thanks! :D Hello to you sir!
[Vibrant Android Development] core123:
thanks for such a quick fix!
[Vibrant Android Development] codeworkx:
last minute fix

upload finished in 7 mins :-P
[Vibrant Android Development] atinm:
It is up! Come and get it! And this time we even tested it ;)
[Vibrant Android Development] }{Alienz}{:
Should I discontinue updating the CM7 Vibrant topic I had earlier now that the CM team is officially updating this topic?
[Vibrant Android Development] atinm:
Yes please, you can request it closed like we did the Galaxy S thread.
[Vibrant Android Development] }{Alienz}{:
Sounds good. That being the case though, you guys will now have the endless questions endeavor :)
[Vibrant Android Development] d33dvb:
First of all thank you guys, without you I would have sold my vibrant long ago.

I was reading your IRC logs, and noticed that you were trying to get the GPS working the other day, and while I know other bugs take precedence, I would truly run this as a daily driver if it werent for the gps. Are we all waiting on a leak from samsung and if so, any ideas on when such a leak may happen, I hate to speculate, but I have been waiting to go back to cm since i left my mytouch a year ago. Cant wait guys, if some donations would help reverse engineer the thing, I think the vibrant community should start a Donation Bucket pledge for it.
[Vibrant Android Development] cashyftw:
Wait woah woah woah, my phone says 99% I thought it stopped at 97% lol
[Vibrant Android Development] jeph36:
In the leaked-from-China thread that originally claimed to have working GPS on 2.3.3 (later proven to be false), eugene claimed he had successfully got GPS to work on a 2.3.3 ROM (not sure which one). I have been on vacation since Wednesday and away from my normal computers so I have not tried to reproduce his work. Has anyone else tried to make that work for GPS? Certainly not a deal-breaker for me (CM7 since early March), but it would be nice.

Edit: This thread and post, as an example.
[Vibrant Android Development] needslipo:
sweeeet.. reboot to recovery finally works!

by proxy the rom manager app now works too!!! just hit 'flash clockwork recovery' select vibrant (mtd). it will say not supported yet, i just hit yes to 'installed manually', and then '3.x' and its set!
[Vibrant Android Development] atinm:
That person has not open sourced anything so the links are useless to us. If we find open source code for GPS, or just get around to debugging it ourselves, it'll be fixed. Hasn't been a priority because none of the developers actually own a Vibrant.
[Vibrant Android Development] jonathanhuerta4:
I'm sorry if this was explained but, didn't "Kolja" (dumdidum), have a Vibrant?.:)
[Vibrant Android Development] gehzumteufel:
While he does have a device, he hasn't been working on CM for the Vibrant for a few weeks now. Atinm has been so kind to work with a few of us to get this stuff tested and working. Sadly, he doesn't have the device.
[Vibrant Android Development] dbacchus:
I wonder if Eugene will ever clarify that claim...
[Vibrant Android Development] Magum p.i.:
I just tried flashing this and got error assert failed get prop or something installation aborted
[Vibrant Android Development] cashyftw:
Are you on a custom kernel?
[Vibrant Android Development] BuLLeT_PrOOf_wAlleTz:
Can the bettery ever get good as stock roms? Or do we need more open source from Samsung
[Vibrant Android Development] charkey:
I'm glad there is now a new separate thread maintained by our very own CM7 Vibrant developer himself! Thank you!
[Vibrant Android Development] ^Fs:
Battery life has improved for me.

Although not sure why Google Voice is eating my battery. I haven't used it at all or received any messages.
[Vibrant Android Development] iynfynity:
I can still use the old method of flashing right?
[Vibrant Android Development] gehzumteufel:
If you still have the files, yes. Otherwise, no.
[Vibrant Android Development] atinm:
Wrong. Click on the links in my signature.
[Vibrant Android Development] iynfynity:
even with the old files? the method I know is the one that requires Odin, then after the initial CM7 I'll just flash the latest nightly.
[Vibrant Android Development] gehzumteufel:
It's best to use the new, currently supported process.
[Vibrant Android Development] }{Alienz}{:
You made the new instructions actually easier! Shame! What happened to making it harder with ODIN. :)
[Vibrant Android Development] boothten:
That's exactly what I was thinking!

The one thing keeping me from from flashing CM7 any earlier was I was kind of scared to use ODIN, as I never used it before.

When I found out you can just flash it using CWM now, I did one of these, lol:

Just a quick question to the OP, do you only recommend/support we use the modems available on your sourceforge download page?

Could we use one from the CM7 flashable modem threads somewhere in the Vibrant Development section, or is that not suggested...?
[Vibrant Android Development] atinm:
Whatever man, pick whatever method you want. But if you want one that works, I'd say use what we tell you to. But we're going to stop telling people to do anything now, you're on your own.
[Vibrant Android Development] :
I instailed this b4 the new way of doing it, so i have to go to recovery flash kernel, reboot and then the update cm7 will flash by its self or what?
[Vibrant Android Development] cojonesx:
follow the "UPGRADING FROM EARLIER CM7-RELEASE:" instructions
[Vibrant Android Development] GreenDroidX:
I have seriously look at http://goo-inside.me/gapps/ Could NOT find the lastest gapp with the May gapp the latest was from March
[Vibrant Android Development] javacody:
It was there, I downloaded it yesterday. Looks like they pulled it...
[Vibrant Android Development] boothten:
That's too odd, it was on there just yesterday when I downloaded it...

:confused:
[Vibrant Android Development] gehzumteufel:
It was formerly there, but here it is. http://www.multiupload.com/CGOAV122GQ
[Vibrant Android Development] boothten:
Maybe something was wrong with it, and that's why they pulled it...?
[Vibrant Android Development] gehzumteufel:
Maybe, but it seems to work for me. This is the same one I am running.
[Vibrant Android Development] boothten:
Same here, I have yet to encounter a problem with it, but they had to have pulled it for a reason right?

Either way, it works for me lol.

And, even though I already have it, thanks for re uploading it again for others!
[Vibrant Android Development] cojonesx:
my understanding is too many people were using it for other then 2.3.4

its only change was to gtalk and that only seems to work on the nexus s anyway (as seen by the problems with gtalk in this thread)
[Vibrant Android Development] :
Reboot. Your Phone should automatically start flashing "update-cm-7-INITIAL-DEVICE-signed.zip". If it doesn't, simply reboot again.

This is what in kinda confused about , so after flashing the kernel (say if i was flashing via clockwork mod) will the update cm7 flash by its self or would i have to reboot my phone get back into cwm and flash the update?
[Vibrant Android Development] notverycreative:
Will it still suck up battery when it's off like it used to with gpsd?
[Vibrant Android Development] atinm:
That's the question :) - I am told not, but we shall see. My Vibrant is acting flaky (the USB jack is loose and so doesn't make a decent connection to charge . . .) so I can't charge it. Will try again tonight - but figured you guys could test it better :D
[Vibrant Android Development] notverycreative:
Alright, I'll give it a shot tomorrow and report back. My GPS was barely usable with stock 2.1/2.2, so I'm not really expecting much xD
[Vibrant Android Development] GreenDroidX:
I too have no data no problem with Linksys router or my cooperate one at work
[Vibrant Android Development] beren28:
Does the captivate use the same battery?
[Vibrant Android Development] notverycreative:
I don't think so. Regardless, the Captivate GPS driver is totally different and fully functional.
[Vibrant Android Development] mk262:
Is this change just committed or is it in the 7-12 file?
[Vibrant Android Development] atinm:
I think you misunderstood what he was saying -- he thinks it is shameful that there are so many other developers basically using our work, but not contributing anything back. Almost *every* 3rd party kernel is pulling our changes into their kernel, but I only know one person who ever sends us pull requests. *That* is what he is calling shameful, and we agree. If someone is going to use CM7 repositories to create basically copies of CM+mods, if the mods are things that would help CM, they should be sending us pull requests. Not doing so is low, and goes against the spirit of open source development. MIUI is the most egregious example, but the kernel developers, even though they have their github repositories public, aren't doing their part because pull requests are supposed to flow upstream, and our repositories are upstream from the 3rd party kernels.
[Vibrant Android Development] gbakabg:
Yes it uses the same
[Vibrant Android Development] apollo15rover:
Willing but NooB Question re: Logcat

I am willing to test tomorrow's release because on Stock Eclair, Stock Froyo, then ROMs like Trigger, Bionix etc I always was able to get a strong and reliable GPS signal.

In preparation, I find I have no idea how to logcat. I can do dmesg just fine on my phone's terminal program, but can someone either tell me ..

1) How to do logcat on the phone (I am getting "unable to open log device '/dev/log/main': Permission denied" )

2) How to do logcat otherwise - or give me a link to the instruction?

3) Or can I simply submit a dmesg?

Thanks
[Vibrant Android Development] Romanbb:
I can't tell if any of that was subtly directed towards me or not, but I hope it wasn't.
[Vibrant Android Development] geoffcorey:
What kernel are you running? It sounds like your logging module isn't loaded.
[Vibrant Android Development] Cesarp 24:
Pretty sure it wasn't.

Sent from My CM7 Monster
[Vibrant Android Development] :
If you have ADB set up and working, then you can "adb shell" to get in, and then do a logcat from there. That's the way I do it.
[Vibrant Android Development] 12paq:
Agreed, absolutely.

The community here is in your dept, without you and your team, the orphaned SGS devices might never have gotten CM7. We can't thank you enough.

Then why when someone does it correctly do you lable the commit "bull**** as usual"? I'm kind of hoping that was a joke, and not a snarky turf ego thing. No biggie, I geuss.
[Vibrant Android Development] gamikzone:
i think there is a new relase for gps for build 52
[Vibrant Android Development] beren28:
Good thing the GPS drivers are not needed to charge a battery then, right?
[Vibrant Android Development] Kaik541:
it wasn't, you admit yourself your code is a hack (which, as a general rule, device-specific hacks aren't included in CM) and that means it won't ever get approved, even though it would fix an annoying bug. it's the same reason we don't disable the 2g/3g toggle entirely even though it can trash the phone (the nexus s still suffers from this problem, as well).

if there is a way to fix it at a device-specific level, then it'll be included. jt1134 from the fascinate has even offered several attempts to fix it as he had a similar (but not the same) issue on the fascinate. we'd love to incorporate *any* fix, but hacks just aren't fixes.

because we keep getting reports of "this works this works!" and then we have people test it and it results in more brokenness than before. there was a similar issue with didle earlier in development and the whole bootloader drama and blah blah blah... basically, we've never gotten a consistent report on any of the "fixes" that have been tossed our way... and the ones that have are hacks (like the above mute/unmute issue).

the anger is mostly directed to "kernel developers" who just constantly pull in changes from upstream thinking they have any idea what it's doing (usually seems they don't) and completely rely on the team to do anything of serious improvement. I'm not gonna say OC/UV is pointless, but that's about the only *real* feature any third party kernel has added (unless you want to argue for voodoo color, which I still say is a preference thing) and still they constantly introduce new things that are most likely gibberish to 98% of the people reading the thread and they're touted as amazing new features.
[Vibrant Android Development] atinm:
It is directed at anyone who is pulling from CM repositories, adding stuff that could be useful for CM (meaning not OC/UV, but other fixes, enhancements that should/could be merged into CM), but doesn't send back pull requests when they've got things fixed. I have no opinion on your contributions because unless you have sent us pull requests, I have no idea what you have done. I do know that you've engaged with me on phone.apk and gps, so you're actually way better than many others. Only Zach actually sends us pull requests though - it should be everyone who pulls from us.
[Vibrant Android Development] atinm:
It was me getting pissed because I f'ing *HATE* GPS on Vibrant and the init.aries.rc change seemed like it was another of the placebo fixes that keep showing up on Vibrant forums. I've actually reverted that commit - I'm going to let you guys see for yourselves if it fixes GPS for you.
[Vibrant Android Development] atinm:
The "unable to open" message is when you're not rooted, which is weird . . . you can also run logcat from your host computer with your phone connected. Just run

$ adb logcat

on your host machine.