yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] mobilebone:
It is in the Vibrant section, it boots and runs. That is a pretty good indicator of compatibility. Relying that much on the community is what I was do not understand. A lot of users upgraded in the mean time, not only developers.
[Vibrant Android Development] renardk764:
I work in the 911 call center in Austin Texas. I own a vibrant and have been usning CM7 for a while.

I've attached a logcat taken while attempting a 911 call. Result was a busy signal.

BTW, I'll personnally test any solutions that are developed. I'm in a position where testing 911 phone calls won't cause a stir.

It's important and many of you giving out alternative numbers really don't understand the complexity of modern 911 systems.

Let me know ASAP if this logcat is informative or if I need to do something different.

KenR
[Vibrant Android Development] apicia:
Thanks reynardk764, I hope that helps developers.
[Vibrant Android Development] RoxAbout:
Force Close Fix?!?

Rom Cm7.1.0.1

currently on bali kernal

tried eugenes testrrr1 sucks battery life like nothing i've ever tried

tried glitch broke my ext mem card [unable to read it]

bali is giving good battery levels after full charge..at least it dont nose dive in discharge like eugenes!

ok after having a sudden case of fc's after days of no problems [at least in that dept], and searching on xda for help on a fix for them.

I have FINALLY got them to stop!

from the different threads regarding them they all say "wipe dalvik clear cache and fix permissions"

Yes Yes And Yes ! except also use rom managers fix permissions! that works! i do not believe that the one ran from recovery works at least it wont stop the fc's thats for sure.

enclosed are some battery spy pics

note on the eugene one it shows the full discharge done for battery calibration but the steady decline between charges over night was where my comments were pointed at. and as you can see on the bali rom nothing of the same sort was/is going on...same phone just changed kernels and let it watch over night.
[Vibrant Android Development] KWKSLVR:
It won't last. Trust me. You didn't install the ROM correctly. Wiping Dalvik and fixing permissions might work for an hour, maybe 8, maybe a day or two. But eventually, the ROM is going to slow to a crawl and the everything related to the Framework is going to FC.

As mentioned in several threads: Odin to stock > update.zip to get into recovery > wipe data/factory reset > format /system > install CM7 to load blue recovery > install CM7 again > install gapps > wipe data/factory reset > boot into CM7 > leave it along for 10 minutes > don't restore system apps or any data from titanium > enjoy CM7.

Anything other than this will most likely result in problems on down the road.
[Vibrant Android Development] apicia:
Another that likes it fresh ;)
[Vibrant Android Development] Kaik541:
so close! we need adb logcat -b radio for this to be of any use

<pawitp> Kaik541: ask him to use "logcat -b radio" ran before the call and keep it running throughout the call
[Vibrant Android Development] pawitp:
BTW, try the latest nightly and those contain some fixes which might not be present here. (Busy tone was before emergency call code was merged). The nightly should no longer have the busy tone bug but rather the "no audio" bug where the call goes through but there's no audio being routed. It'd also be interesting to see what happens if you choose AT&T as your network and attempt emergency call there.
[Vibrant Android Development] KWKSLVR:
What can I say, I've been running CM7 since #4X, it's NEVER been stable for me until I started doing the above. I always knew it had to be something I was doing wrong, but it took a while to pin it down.
[Vibrant Android Development] atinm:
Thanks - now you can go back to stock or whatever other ROM you want. We will not force you to stay on CyanogenMod and I'm sorry if we bullied you into installing it before. We are going to drop Vibrant support once ICS drops - not worth the hassle.

To the person who works in the 911 call center - I have sent you a PM with a build I want you to try with my email address. Please let me know how it goes. I might have other things for you before I drop this. Also, please try setting your network to AT&T and trying 911 from that instead and see if it works.

To the person who asked what phones we've moved to - the current team has never been on tmobile, and we've always had other phones than Vibrant. We were developing for the Vibrant because it was similar enough to other Galaxy S devices and the developers before us had dropped the Vibrant and we felt somewhat obligated to support Vibrant. Not so much anymore . . . we've gone above and beyond the call of duty and dislike taking crap from users. The main developers of teamhacksung are on SGS2, Captivate and Galaxy S. TMobile will have the SGS2 variant and already has many HTCs that run CM. The Vibrant is a crappy phone to support for CM and I'll be happy to drop it.
[Vibrant Android Development] idiosyncrisia:
I for one thank you and the cyanogen mod team for all the work you've done. Ever since my g1 died, I've been wanting cm on my vibrant. We were teased with wes garner, but in the end we got the support we've desired. I have donated when I used my g1 and have donated now for my vibrant. It's a shame to hear you'll drop support of the device, but this stable cm7 will tide me over until the phone dies, or I get something else.
[Vibrant Android Development] Stevethegreat:
I'm sorry if I seem to be repeating old querries but I feel the need to try anyway:

Is there a chance for TV-out support to ever be included in CM7 (or MIUI)?
[Vibrant Android Development] sebastianwfh:
atinm....i really thank you and your team for the support you have done.... CM7 nightly is the first ROM i ever flashed and happy with it although i am testing other rom. nonetheless, you guys are amazing!
[Vibrant Android Development] flipper2006:
They could always dial 411 and have information transfer them to 911.:eek:
[Vibrant Android Development] bigtom624:
Don't let a few jerks ruin it for the ones of us who really appreciate all that you do for our phones. If you look back it is always the same people complaining about the same **** over and over. I really hope you reconsider and keep supporting the Vibrant.
[Vibrant Android Development] :
who ever said shame on CM is a fool! i really hope you guys still support the vibrant. Because no cm7 = no miui = death of vibrant.
[Vibrant Android Development] swa2k4:
The reality is... Life is not worth loosing on not upgrading your phone for one that is supported by CM. If someone gets hurt and only one phone is nearby..., vibrant on cm7 there is a chance that the person who knows how to dial 911 could have saved a life if not their own. please run stock if you are not willing to deal with this danger. Or else in the small difference in price that it is....minimally spending, Pick up a nexus one on Ebay and sell your vibrant

good luck and be safe all
[Vibrant Android Development] androidcee123:
I too am an older user of CyanogenMod from the G1, and have tried many other ROMs, with the hope that we would get a stable ROM for Vibrant.

Personally, I appreciate the work that you and your team has put forth for US ALL. I agree that you shouldn't have to be subjected to this foolishness, and I respect you for pulling out. I can honestly say that I will miss you guys.

Just know that not everyone here has gripes about different things that not to our individual liking. The bottom line is that we have a very stable and workable QUALITY ROM.

Thanks again bro.
[Vibrant Android Development] strictlyrude27:
The sense of entitlement and overall bratiness from the Vibrant community is astounding.

We know 911 is not working properly, and we know it's a major, potentially life-threatening issue. There's an open bug on it. Lots of people love to ***** and moan to get it fixed, but nobody has submitted a logcat against the radio running stock, as requested in the bug report as requested.

How about making contributions rather than complain and drive our developers away? "Making contributions" doesn't mean writing code or anything, but it means being a good member of the community: filing reports, getting logcats for the developers, etc.

I can't blame atinm or any of the other CM7 developers for pushing to drop support of our phone.
[Vibrant Android Development] Jdom58:
Strictly, I'm another one who has been here since the very early days of the G1 and I have seen quite a few great developers just simply get fed up and leave. There's always the few that think they are entitled to something around here with their *****ing and moaning and complaining because something isn't working right on their phone or the update is not coming fast enough, or the sun ain't shinning on their part of town.

It's too bad it has to happen but schmucks like this are everywhere and come in all ages. I'm sure they do realize these guys working on the ROMs do it for free and on their own time but they don't give a ****.
[Vibrant Android Development] CM Wave:
Whoa, no ICS on the Vibrant? I hope that was a joke.
[Vibrant Android Development] geoffcorey:
If there's no one working on cm code for the vibrant, then no updates, which means no ics.
[Vibrant Android Development] Ningcube89:
I wholeheartedly agree. If you can't deal with the lack of 911. Run stock, but don't complain and moan about certain things when you should know what you're dealing with when you use CM7 on the Vibrant.

I do want to thank the developers for doing everything they have so far. It's not an easy task at all. But as usual, we always have to have the "entitled" ones who don't do anything at all and should just leave XDA.
[Vibrant Android Development] :
Hopefully it was. I just can't understand how someone can bash cyannogen mod for a bug, forgetting that the rom is 100% free!!! I know 911 is important, but thank God I have never dialed it and don't plan on. I'm sure there are other emergency numbers per city you live in.

I would like to apologize on behalf of all the good vibrant community members, this is the same reason Nick from miui us and 360 productions posts less on xda, too much knuckle heads...Smh.

Only good thing for us is if we sadly don't get official CM ICS then maybe we get a i9000 port.
[Vibrant Android Development] Genesis3:
I loaded this and get no phone service at all.

The base Froyo load works; I know the phone is ok ;-)

Here's what I'm getting out of an "adb logcat -b radio"

E/RIL ( 2118): check_nv_data_size:

E/RIL ( 2118): check_md5:

E/RIL ( 2118): compute_md5: path /efs/.nv_data.bak

E/RIL ( 2118): compute_md5: open(/efs/.nv_data.bak) fail. No such file or directory.

E/RIL ( 2118): No valid backup data. Create default nv data.

E/RIL ( 2118): create_default_nv_data:

E/RIL ( 2118): => create new nv_data file(/efs/nv_data.bin).

E/RIL ( 2118): create_default_nv_data: write -1 byte to /efs/nv_data.bin

E/RIL ( 2118): refresh_md5_file: /efs/nv_data.bin

E/RIL ( 2118): __refresh_md5_file: md5_path /efs/nv_data.bin.md5

E/RIL ( 2118): compute_md5: path /efs/nv_data.bin

E/RIL ( 2118): refresh_md5_file: done

E/RIL ( 2118): compute_md5: path /efs/nv_data.bin

E/RIL ( 2118): /efs/nv_data.bin md5 : 35345d8af8f0283b1e0d339e24997781

E/RIL ( 2118): make_md5_file: (/efs/nv_data.bin.md5)

E/RIL ( 2118): make_md5_file: fd 15

E/RIL ( 2118): make_md5_file: write failed with 28

E/RIL ( 2118): check_md5:

E/RIL ( 2118): compute_md5: path /efs/nv_data.bin

E/RIL ( 2118): check_md5: MD5 fail. orignal md5 '' computed md5 '35345d8af8f0283b1e0d339e24997781' (rild)

E/RIL ( 2118): NV data tainted! Restoring...

E/RIL ( 2118): check_md5:

E/RIL ( 2118): compute_md5: path /efs/.nv_data.bak

E/RIL ( 2118): compute_md5: open(/efs/.nv_data.bak) fail. No such file or directory.

E/RIL ( 2118): No valid backup data. Create default nv data.

E/RIL ( 2118): create_default_nv_data:

E/RIL ( 2118): => create new nv_data file(/efs/nv_data.bin).

E/RIL ( 2118): create_default_nv_data: write -1 byte to /efs/nv_data.bin

E/RIL ( 2118): refresh_md5_file: /efs/nv_data.bin

E/RIL ( 2118): __refresh_md5_file: md5_path /efs/nv_data.bin.md5

E/RIL ( 2118): compute_md5: path /efs/nv_data.bin

E/RIL ( 2118): refresh_md5_file: done

... and then a bunch more.

Nevermind... I think I know why... and if I'm right I can fix it ;-)
[Vibrant Android Development] 12paq:
I like CM7 on my Vibrant very much. Considering that the port was done without Vibrant Gingerbread source is astonishing and team Hackung should be damn proud they got it this far.

Putting up with XDA Vibrant forum brats has been team Hacksung's biggest challenge and I thank you guys greatly for your tolerance and patience.

The Vibrant was and still is an amazing device, but with carrier branding and a crappy mount system and a terrible GPS and no 2.3 source, the writing has been on the wall for a long time. The Vibrant's dev support is all but gone. But what a ride!
[Vibrant Android Development] gunks:
I hope you devs don't stop on the vibrant just for a couple bad apples. Realistically, xda is filled with those kinds of people, not just the vibrant section. Of course you guys put in tons of free time and effort into this project which all of us appreciate. Please reconsider abandoning development on our device. I find this ROM to be one of the best I've ever used on the vibrant and I've had the phone since day 1. Like previous posts have mentioned, if you don't like the little bugs that have been mentioned OVER and OVER then go develop yourself or find another rom. Thanks again devs.
[Vibrant Android Development] nirogu325:
Please just focus on what you have been focusing. I came back to CM7 days ago and the last nightly I tried was #25 many months ago. Your team has improved this ROM a lot over time. Please don't let ignorance win by getting the best of you, teamhacksung. In the end it is your choice, a choice we will all be looking forward to.
[Vibrant Android Development] KWKSLVR:
I really wonder why so many Developers bother in the first place. Between the Vibrant Forums and the Galaxy Nexus forums, what's the point? All I see are people whine and moan. Don't get me wrong, I've had complaints with the way my device performance, but also admitted it was most likely user error (and it was).

I've always appreciated our Vibrant's developer support. But with so many vocal people complaining, I'd walk away too.
[Vibrant Android Development] nirogu325:
Easy answer: goodwill. Yep, the one that's being abused.
[Vibrant Android Development] Zdidge:
Sorry to see you go. I think CM7 on the Vibrant is amazing. I appreciate all the hard work you guys do. I am bummed we won't be getting ICS. I hope you reconsider. Thank you.
[Vibrant Android Development] getnbzy:
Hello all,

I know the mood in here is a little ...tense to say the least but can someone help me please. I flashed from stock 2.2 to CM 7.1 using the guide from this page http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide

All was well for almost a week now but today i am getting framework and gapps FC's and when getting calls my ringtones change. Also the wifi and another icon is white now instead of green and i cant check my gmail. I'm thinking of reflashing but i didn't make a nandroid backup. Am i screwed? Can i just reflash without the nandroid backup following the guide again or do i need to go another route. I was loving this rom before things got sideways. Thanks
[Vibrant Android Development] Alex9090:
Recovery> wipe cache partition

Sent from samsung vibrant
[Vibrant Android Development] getnbzy:
Thanks. Trying it now

---------- Post added at 10:42 PM ---------- Previous post was at 10:17 PM ----------

No luck. It was in the cyan arrow circle startup for like 10 minutes and finally i held down power button trying to get it to finish boot and it did. Unfortunately problems still there. Any other suggestions?
[Vibrant Android Development] creeve4:
Is this "Stable" release any more stable than the newest nightly?

I've been running nightly 157 since it came out and have not experienced any problems until this morning. I charged my phone to 100% with the phone off, booted to recovery, and wiped battery stats. Now my phone won't boot past the CM logo screen (Yes, I've tried all methods of wiping).

I'm not looking for help with the "no boot" problem, just wondering if the "Stable" release is any more stable than the newest nightly?
[Vibrant Android Development] getnbzy:
Update. I Odin'd back to stock and am going to try this again. Wish me luck:)
[Vibrant Android Development] a2296455:
I can no longer install a LOT of the apps from the market. It is saying that "your device is not compatible with this item" even though it's already installed. This was for multiple apps, including Google+!!!! What's going on?
[Vibrant Android Development] MizSxxyBych:
wow

I would also like to add my two cents and ask that you not let a bunch of unappreciative idiots ruin it for us all. I am fairly new here and have flashed only a few roms, but I have always loved CM the best despite the minor bugs that were CLEARLY listed. No one is forcing ANYONE to install ANY rom, so to install it anyway then ***** about the developers is the dumbest **** I have ever seen. I myself have posted once or twice about an issue I had, but only to ask what I may have done wrong, never to flame the developers for something they have provided for us for FREE!!! Shame on the people with that type of attitude!!

Again, thanks for all of your help and hard work!!
[Vibrant Android Development] archie53:
I second this.
[Vibrant Android Development] creeve4:
Disable call end tone

How do you disable the tone that plays when you press "End Call" ?
[Vibrant Android Development] aznhybrid:
I third this!!

Thank you guys so much for your hard work, many of us (if not most) are very grateful!

I switched from Trigger to this and I love it!! I was having problems with all my process's force crashing and now everything is in the clear. Although I will probably upgrade to SGSII soon, but nevertheless I appreciate all of your hard work!
[Vibrant Android Development] Genesis3:
OK, I've got it loaded and have been running it for a day.

My only complaint: Battery life

sucks

.

I mean really sucks. Even with Juice Defender killing data when the screen is off I'm burning ~150ma while idle which turns into ~10%/hour! EEEK!

It looks like the phone is not going all the way down into S3 (fully asleep); I don't see anything in the usage list that appears abnormal, nor anything in the System Monitor top apps list. Whatever is doing it is not showing up in the logs..... but it's quite bad.

To put this in perspective I ported CM7 (same release) to the Motorola Triumph on Virgin and with Wifi off and Juice Defender (same as the Vibrant) I'm getting

2%

battery consumption per-hour while idle - or one

fifth

the power consumption with identical use profiles (phones literally sitting next to each other on my desk!)

I'll chase this if I can get the kernel being used in source form and a reasonably-documented way to push new copies on the device - is it available?
[Vibrant Android Development] creeve4:
Use Streamline and Calibrate your battery.
[Vibrant Android Development] Genesis3:
Thanks - I'll give that a shot..... it's definitely not dropping to S3; I was able to determine that poking around. Looks like that kernel addressed the particular issue in question.
[Vibrant Android Development] faceless:
it's sad to hear someone representing CM7 sound as arrogant and retarded as the people who steal their work. maybe there isn't much difference between the two after all.
[Vibrant Android Development] :
*face palm*
[Vibrant Android Development] CM Wave:
I think we're just getting trolled now. Let's hope the Vibrant devs don't take this stuff too seriously.
[Vibrant Android Development] :
I did the research, and this is the first time you are posting in the vibrant forum ever, you have no life to come in here and try to add insult upon injury. Stick to your epic 4g forums you troll!

if i was a moderator i would ban your ass.
[Vibrant Android Development] jt1134:
Goddamn you're dumb.

Never been on the developing end, have ya?
[Vibrant Android Development] a2296455:
I have this same problem...
[Vibrant Android Development] blazinn831:
i am having signal and data problems. i get one bar of signal and have a hspa data signal (simply honey about4bars)....then my hspa will cut to edge and then my signal will go up to 4bars. flashed different modems and all have the same result. never had this problem before. any help would be much appreciated.
[Vibrant Android Development] Genesis3:
Here's a treat for you folks... this is out of my Triumph CM7 build.

Stick this in /system/etc/init.d/99memory

#!/system/bin/sh
#
# Write memory management parameters
#
if test "$RESP" != "OK"
then
export RESP="OK"
/system/xbin/nohup /system/etc/init.d/99memory >/dev/null 2>&1 </dev/null &
exit 0
fi
#
# OK, we executed ourself (yea, I know) and effectively detached. Now
# wait 2 minutes and then write the memory parameters
#
sleep 120
L="log -p i -t cm"

$L "99memory: TG-CM7 Setting memory management parameters"
echo "1536,3072,4096,10000,25000,32000" >/sys/module/lowmemorykiller/parameters/minfree
exit 0

What this does:

1. Detaches itself immediately.

2. Waits 2 minutes (so the boot can complete; the boot sets the minfree parameters later)

3. Sets the minfree grouping parameters as above.

Those sizes are in PAGES (4kb each) not bytes. What this does is tell the kernel's internal memory management that you want to kill off things in the lowest three sets of process groupings more aggressively than the default. This will tend to run your free RAM in the ~80MB range instead of in the ~50-60mb ramge, which in turn will make for a significant increase in perceived performance.

The cost? Less multitasking - there is no free lunch. The Vibrant is relatively RAM constrained (as is the Triumph) so you have to give to get.
[Vibrant Android Development] jay661972:
Had the same problem, bcuz i change the density to 220. Change it back to default, 240 and everything works fine now.
[Vibrant Android Development] pault949:
Battery Issues (solution)

To all the people having battery issues with CM 7:

1. When installing the ROM, follow instructions on the CM wiki to the letter.

http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide

2. After initial install, let the phone boot and sit for 10 minutes. Go get a coffee.

3. Do whatever you need to do with the phone. Install apps, etc.

4. Charge phone to 100%.

5. Reboot to recovery, wipe battery stats.

And here's what really helps with the battery life...

6. When not using the GPS, disable it. Reboot phone.

http://forum.cyanogenmod.com/topic/33150-battery-life/

It seems that the 'Android System' process that is killing everyone's battery may be because the GPS isn't truly off when an application that is using it, like Google Maps, is closed (even though the GPS icon in the status bar is gone).

I had serious battery issues when I first installed the ROM and now that I have taken these steps, everything is fine. I am getting over 20 hours of battery life with moderate use (Bluetooth, media player, etc.) and the 'Android System' process is no longer taking double digit percentages of the battery life.

This is definitely a bug that the CM group probably knows about and is probably working on.

On a side note...

I, personally, would like to thank the CM team for all the hard work that they put not only into the Vibrant development, but also for the development on all the other supported devices. Thanks, guys. Keep up the good work.
[Vibrant Android Development] Raistline:
Word of warning to all using this ROM.

Emergency Calling, i.e. 911 in the US does not work with this ROM. I can confirm this as I have tried. In fact, dialing 911 had soft-bricked my phone. I was not too happy about this, of course.
[Vibrant Android Development] pault949:
C'mon, man. Really?

We know that there is a problem with 911. No need to troll.