yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] SamsungVibrant:
Let's all just get along, and lets fix these issues so I can come back to Cm7!

Ok all the fighting is lame. Let's just all get along, stop calling names. Let the devs develop as long as they follow whatever rules they are suppose to.

With that said, I want to come back to CM7, but there are a few bugs that need to be worked out.

1) 911 must work, I live in a metropolitan area with tons of different cities. Los Angeles is not Los Angeles, and LAPD doesn't serve the entire county. Driving on the Freeway one minute I'm in noho, next minute I'm in sherman oaks, then van nuys, then weho, then beverly hills. All served by different emergency response teams, so I can't store every imaginable emergency response number in my phone. I NEED 911 for safety. THIS SHOULD BE TOP PRIORITY. Someone please get it working. According to cyanogenMod forums it still doesn't work.

2) GPS needing reboot, is just annoying. Please someone fix this. Or scream at both T-mobile and Samsung to give us a driver for GB.

3) During Calls. Hello? Hello? Ya I have to say hello twice, the first hello when I pick up the phone never registers. Same issue with MiUi. There is like a brief muted silence at the start of calls, I can hear the other side but they can't here me when I pick up and say "hello," I have to say it twice.

4) Recording feature. I use my phone as a digital recorder all the time. With stock roms the recording is loud and crisp. With both MiUi and CM7 the recording quality upon playback was of horrible sound quality. Doesn't matter what recording app I use, same issue with all.

5) LOW LOW in call speakerphone volume. Way too low.
[Vibrant Android Development] Kaik541:
while I'm at it, since the diff's already been run, let's go through the changes to the source he's posted (assuming that's the full source):

Hardcoded directories for building (you will build on eugene's computer only! :P)

More or less took captivatemtd defconfig and renamed it to vibrantmtd

Lowering stock voltages by about 25 mV

Adding a slew of new CPU governors

Incomplete, but mostly functional, deep idle support (which only works on gingerbread bootloaders iirc, which is why we haven't implemented it)

New modem drivers (which doesn't actually affect the vibrant if you look at the ifdef's, and could potentially break the other devices--especially CDMA ones)

Added an mmc change that could accommodate for crappier microSD cards (this is actually a useful change)

Reverted the wireless broadcom driver to an older version (why?)

Some differences in the way battery charge is read/written

Some mDNIe changes

Removal of preliminary car audio dock support (again, why?)

From the looks of things, he more or less took some samsung source code drop, poured it on top of the teamhacksung source selectively... the copied/pasted the governors and deep idle stuff. Not necessarily anything bad, but as for how this fixes GPS, please point me to those changes because I saw nothing that would lead me to believe this happened.
[Vibrant Android Development] mobilebone:
Agreed. Feature-wise the ROM is great, but there are some rough spots that need to be fixed.
[Vibrant Android Development] jewishmafia:
Thanks for the help, again after more futzing around I managed to figure it out before coming back here again... lol :rolleyes:
[Vibrant Android Development] eugene373:
wow, After all that your eye sight sucks & you can't Diff worth ****....

Seriously, I think everyone is over your BS
[Vibrant Android Development] Kaik541:
http://pastebin.com/bSpAi1Vs

show me.
[Vibrant Android Development] xalucardx:
.

Yeah but i doesn't say you have to release it immediately , stop *****ing for a source just to kang it , its out there so stfu , instead of *****ing got make your own kernel and stop relying on other people work , you just sound like a annoying 12 y/o ginger kid.
[Vibrant Android Development] beren28:
So you think that *all* galaxy S devices are the same? Then why don't we do what you suggested with the existing official galaxy gingerbread that has been out for months? Or the captivate leaks?
[Vibrant Android Development] eugene373:
show you?

Can you not understand " - " & " + "

What more do you want? You cry over Source & once you Get it, You cry over what was Changed.... LMAO!!

You Uber Win!

~Eugene
[Vibrant Android Development] Kaik541:
actually, go ahead and read the GPLv2, it actually does state you must either have it immediately available or "upon request." HTC has made up some bull**** about having up to 30 days to do it, which is wording from the GPLv3 (which the linux kernel is not licensed under).

no, I understand it just fine, I'm pointing that if you fixed GPS, it certainly isn't in this kernel source. and besides adding a few governors and the mildest of undervolting, I'm not sure what you've done at all.
[Vibrant Android Development] eugene373:
Take you GPL and Shove it stright up you A**

Second.. You think a Diff would be that big if I changed a few things...

Never said GPS was Fixed in the Source... Once again.. Your Words not mine...

the SVNET Modem Control does what? Oh that's right, talks to the Modem... Is the Vibrant a CDMA Phone? Oh that's right it's not!

Like I said, You UBER Win!

Regarding GPS!

It's a Binary issue...

Even though you've been nothing but a Jerk, Here's what I found regarding the GPS >

agpsd needs to be in bin ( Same File ) Named gpsd needs to be in vendor with a nice gps.conf for CM7 & GPS to work nice everytime without it locking up or it to stop working..

The Best Binary I have found that works the best is the one in the Kernel packed for download..
[Vibrant Android Development] Jackdog89:
It's obvious that you have a personal grudge against Eugene, you're entitled to your opinion. But I don't care for it and I certainly didn't come to this thread to hear about it.

I was agreeing with the previous poster, I don't care about your feelings on something that allegedly happened 6 or more months ago, it doesn't apply to me. Eugene released his source, so let it go.....

.... Really? the source "he wasn't going to release" wasn't good enough for you? :rolleyes:
[Vibrant Android Development] SamsungVibrant:
Ok back to the issues with cm-7, no more fighting please.

1) no 911

2) gps needs reboot

3) low in-call speakerphone volume

4) when using phone as a digital recorder, the recorded sound quality is horrible.

5) when picking up a phone for the first time there is a brief muted pause, Hello hello
[Vibrant Android Development] sublimnl:
kaik, shut it down man. despite all your whining about his source doesnt really do anything, i have to say that without a doubt his new kernel has given me the best battery life I have had on any GB based ROM with any other kernel, and I've just about tried them all.
[Vibrant Android Development] nirogu325:
Really guys, this is tiresome. I've seen that Kaik guy start fights so many times in XDA...tiresome indeed. Let's focus on driving this ROM the right way please, and thanks Eugene, because you've taken this ROM a little bit further. I'd love to use this ROM again someday, but I'm afraid it doesn't deserve the word "stable" IMO yet, so any progress will be thanked.
[Vibrant Android Development] creeve4:
Not with Eugene's test kernel...
[Vibrant Android Development] apicia:
Is Eugene's kernel CM7 only, or CM7 based (like MIUI, etc)?
[Vibrant Android Development] atinm:
Actually, what it says is you have to release source if you release a binary, with all your changes. You have to make it available as soon as you release the binary that includes the GPL code - which a linux kernel is doing. Always.

And "*****ing for source just to kang it"? You're saying that to teamhacksung here? On the CM7 thread? Seriously? When *everyone* basically bases their kernels on work we did? Go away.

What we want is what we give to the community - GPL source. We actually release more than just GPL source - CyanogenMod has all the framework code we use released as well, not just the kernel source. So stop with the licking of Eugene's nether regions. If he actually releases source, we're good. Otherwise he's just stealing.

We see that Kaik's pushing actually got him to post something on github. Asking him privately (which I've done before) just gets him to say "Oops, I deleted the source because it isn't fun anymore".

I haven't run a diff against his source yet, because it seems he doesn't actually know how to use Git and so all he has is one big dump which is a pain for anyone else to use. Unlike what we do as teamhacksung where you see every commit we make. Each one. *That* is how you work with the community. But hey, keep dumping on teamhacksung and see how quickly Vibrant specific issues get fixed . . .

And "stable" designation is mostly there to give you a target to file bugs against. But heck, it's very tempting to ignore them now.
[Vibrant Android Development] eugene373:
Well, all I know is this got blown way out of the box. Yes, I am grateful for the work that teamhacksung has done, as it's light year from when I last used it..

With that being said, yeah we last spoke on bad terms, & the "Oops" did happen.. Regardless, I had every intent on posting it from the start with or without people acting like total douche bags..

I just don't understand why it was so urgent when I already said I would post it..

Regardless, Thanks for all the work you & the rest of the team put into making CM7 usable for everyone.

~Eugene
[Vibrant Android Development] sublimnl:
End scene. We now return you to your regularly scheduled programming.
[Vibrant Android Development] iynfynity:
You'll love the vibrant section.
[Vibrant Android Development] getnbzy:
So i have been running this rom for a few days now and it is fast. And love the way it looks BUT battery life is bad...even with 3G shut off. Any ideas as i have already performed the recondition battery task? Thanks.
[Vibrant Android Development] SamsungVibrant:
Try turning off your GPS, then rebooting the phone and leaving it off.

If you need your GPS, after you are done with it, if you turn it off, and you don't see the icon anymore, still reboot your phone again and leave it off.

Not sure if that will help, but I noticed it did for me. Like GPS was secretly still on in the background.
[Vibrant Android Development] burgon:
I can confirm all of these
[Vibrant Android Development] ajamils:
Last night I installe CM7 for the first time (coming from MIUI) and have some SERIOUS issues. First, the battery is disharging like crazy. I took the phone of charger this morning at 100% and in 1 hour 15 mins the batter is at 51%. Secondly, phone is getting VERY hot, even though its not in use and screen is turned off.

Any suggestion?
[Vibrant Android Development] tbrar:
Seems like there is a rogue process running which is causing high cpu utilization. Couple of things you can try. Install Cpu Spy from market to make sure that your phone is sleeping properly. Also after charging phone try rebooting. There is a known bug where the phone sometimes doesn't sleep after disconnecting from charger this doesn't occur all the time but occurs occasionally.
[Vibrant Android Development] ajamils:
According to CPU spy, phone is in deep sleep 54% time still the battery is draining like crazy.
[Vibrant Android Development] Jackdog89:
Look at the battery usage and see if AndroidOS has a high usage percentage.

Also, the link in my signature has a thorough walk thru on how to rule out any rogue apps.
[Vibrant Android Development] MizSxxyBych:
UGH

I want to pull my hair out right now....

My APN is disappearing everytime I reboot and APN restore doesnt seem to be helping.... I got it back somehow (dont ask how..lol)...but I'm sure when I reboot it will be gone... Any ideas?
[Vibrant Android Development] getnbzy:
Ill give this a shot. Thanks for the tip
[Vibrant Android Development] t1h5ta3:
you got some thing set up wrong...

i get 30+hours
[Vibrant Android Development] Emama:
but u charged your phone:rolleyes:
[Vibrant Android Development] ChristoA1:
Dammit Facebook! lol
[Vibrant Android Development] swa2k4:
Anyone who flashes this rom using this device better save their emergency contact number in their phone as 911 does not work still right? They need to prioritize this pleaseeeee I hope you all take this as a responsibility that everyone should do, save the number!!!
[Vibrant Android Development] CTown:
About fixing the 911 bug...

From the 911 bug listed on Google code http://code.google.com/p/cyanogenmod/issues/detail?id=4365

I'm guessing no one has seen this bug posting as only one person has given the developer I quoted a radio log. The last post on the bug is from about 2 weeks ago! Most likely we all have a Gmail, which is the only requirement to post on GoogleCode. For those who say the 911 bug should be a priority, just hand this developer your "lolcats".
[Vibrant Android Development] SamsungVibrant:
Cyanogenmod should put in large letters in the OP that 911 doesn't work

It amazes me that this rom was released as stable when 911 supposedly still doesn't work. At the VERY LEAST it should be in BOLD red letters at the top of the original post that 911 does not work and you may put your life at risk.

Imagine someone flashing this and not knowing about 911 not working. Then during an emergency or accident nervously dialing 911 to no avail and dying.

This really is a big deal and it seems like many people are over looking the scope of it.
[Vibrant Android Development] jt1134:
And how many people that have complained about it have provided useful information in fixing the issue? I still haven't seen any. NOBODY working on cm even has a vibrant.
[Vibrant Android Development] KWKSLVR:
Here's mine. In the past, crappy battery life was because CM7 wasn't set up right. Odin to stock, update.zip to get into recovery, wipe data/factory reset, format /system, flash CM7 (to load the proper recovery for CM7 install), flash CM7 again, flash GAPPS, wipe data/factory reset, reboot, when CM7 loads don't touch ANY FREAKING THING. Leave it alone for 10 minutes. Do not restore system apps from Titanium. Do not restore system data from Titanium. Do not let Google restore your settings. Start fresh, enjoy battery life.

Is it going to last 36 hours with the screen on while you play angry birds all day, NO, stop expecting it to. And people, the term "battery life" is completely subjective. Everyone's use is different, everyone's sync is different, everyone's signal is different. You can buy new OEM batteries for well under $10 each, shipped. I recommend them. I carry 3 spares. It's SAMOLED, nothing is going to make the thing run like a it's a clamshell prepaid phone. Me posting up the attached screen shot of my battery life should mean NOTHING since no two devices are set up and used the same.
[Vibrant Android Development] SamsungVibrant:
I wouldn't know how to fix it, I don't know any code.

Speaking of phones and devs, which phones do most devs own besides the Nexus line?

I want to get a new phone but I want to make sure I get one with lots of dev support.
[Vibrant Android Development] beren28:
While I agree in general with your main point you loose some credibility by posting that pick proving you never turn your screen on :)
[Vibrant Android Development] beren28:
You missed the part where I said I agreed with you.

still, I got much much better life on bionic worth the same usage. Not complaining, but battery life is worse on cm, and denying it its silly.
[Vibrant Android Development] beowolf:
This is totally irresponsible to develop for a phone that you dont even use or have access to. And we just readily allow this, with 911 not working and the lame excuse for it is just wrong. Shame on you cyanogen.
[Vibrant Android Development] KWKSLVR:
It's not intended to be directed at you, it's directed at the shear number of battery life posts in this thread. Battery life complaints are a HUGE personal pet peeve. Now processes running wild or other weird things, hey I'm right there with everyone else.

Battery life on CM7 SHOULDN'T be as good as it is on Bionix. We're essentially running a hacked and chopped OS with missing drivers developed by people that don't even have a phone to test on.

There is a loud minority of people that somehow think that their phone should last 3 days on a charge. These people are tiresome and annoying. Chances are, if someone is dissatisfied with their battery life, they probably need to start with the person staring at the screen the most. ;)

---------- Post added at 12:42 AM ---------- Previous post was at 12:39 AM ----------

Whatever, people asked for it, begged for it, then demanded it and now they've gotten it. The 911 issue has been documented for months. No one is forcing you or anyone else to flash it and use it. We shouldn't allow it? Yeah, YEAH! Let's go arrest them!!! YEAH!!!!

If someone lacks the common sense to expect ANYTHING in an experimental ROM to work right, then I pity them. That's the type of person that should NOT be flashing ROM's, much less CM7 that barely has RC1 out. Every time I flash something I flash it knowing it might brick my device. For those truly panicked about 911 that still voluntarily choose to use CM7, I recommend a small prepaid cell phone to keep in your other pocket. If that's a ludicrous suggestion for you, then don't flash CM7 and stay out of the thread.

And for the record, there have been plenty of "stable" CM7 releases that lack certain features due to driver incompatibility as one example. If someone is truly worried about everything working as the manufacturer intended, I recommend staying on the factory ROM.
[Vibrant Android Development] Kaik541:
so I'm sure a lot of you guys are aware that once ICS source is made available, CM9 will be rebased off this work. With the release of CM9, some devices will be dropped from the support tree (mostly old devices).

But comments like the above? It's why teamhacksung is genuinely considering dropping the vibrant. There are quite a few users who are grateful for what we can give and realize we are *not* forcing you to use this ROM, and if it's not up to par that you don't have to use it. Those are the users we want to support and are grateful for. The ones that can provide logcats and dmesgs. But you are few and far between.

I challenge you guys to look at the I9000 or Captivate sections and see just how much more POLITE and CONSIDERATE the average user is there. Arguments erupt from and discussions get heated from time to time, but that's daily life here on the vibrant section compared to the "very infrequent" other boards. Quite simply, the vibrant community should be ashamed of the "average user" in their group, it makes you all look bad.
[Vibrant Android Development] jt1134:
I heartily laugh at you, and your unsupported device :)
[Vibrant Android Development] KWKSLVR:
I couldn't agree more and over the past year and half it's made me start despising the Vibrant Forums. It's tiresome, especially complaints about GPS on every device and every ROM after so many of us have taken the time to figure out what's up and how to make it the best it can be and bring realistic expectations to the table.

People don't realize the sheer volume of support this device has compared to other Android devices and how much work DOZEN'S of solid developers have put into this thing. The fact that there are people on the CyanogenMod Team developing for a device that they don't even OWN or POSSESS is something that people should be grateful for.
[Vibrant Android Development] mryounghc:
isnt that the truth! i just flashed to CM7 a week ago knowing of all the problems. started at 160 to the current nightly hoping each one would solve some of the previous issues. yea some did but it seems like another issue would replace it. i really like CM but im very picky about having everything functioning the way it should. and yea, the battery drain...

from 100% to 84% in 15 to 20 min of NO use and then it would stay there for a while. i listen to music alot and when i pop my earphones in around 10 am every morning at work i would hit 60's% by 1ish. im not a big texter but if i started texting i swear it seem like it would drop 1 percent for each text lol. but anyways i never complained. these people here put alot of effort and personal time into these things without demanding a dime and i really appreciate it. we could be still sitting on stock, Problems? move onto another rom until it is fixed.

btw i went to miui and everything from my ffc to gps is working great
[Vibrant Android Development] mobilebone:
Developing for a phone you don't have is like making performance parts for an engine you don't have. Should have been mentioned in the initial post.
[Vibrant Android Development] beren28:
Using a ROM when you didn't read the thread is like installing an engine without checking if it is compatible with your car.

You should should have mentioned your stupidity in your first post.
[Vibrant Android Development] Kaik541:
except at one point we had two people with the phone. but atinm's was on it's last legs when someone donated it and I'm not even sure what happened to coolya's. we felt we could keep the vibrant development at least up to par with the other devices (except for GPS), but maybe we're wrong. we looked to the community for developers that still had functioning phones on more than one occasion and no one stepped forward. we can't test the 911 issue as literally no one here was ever on tmobile to begin with.

if you have such an issue with this ROM and it's method of development, then take it upon yourself to do something about it instead of just whining like a five year old. yeah, we've tried fixing what we can, it doesn't mean we're going to get it right every time, but at least we're doing something. we've been almost BEGGING for logcats of 911 attempted phone calls... we've gotten, what, one? if this is such an issue for you guys, why do you do absolutely nothing about it?
[Vibrant Android Development] Demetris:
Well said!

Please continue your excellent work, and thank you very much for it.
[Vibrant Android Development] apicia:
1) no 911

2) gps needs reboot

3) low in-call speakerphone volume

4) when using phone as a digital recorder, the recorded sound quality is horrible.

5) when picking up a phone for the first time there is a brief muted pause, Hello hello

I can confirm these. The #5 is so irritating. Hello, hello..... hello?
[Vibrant Android Development] geoffcorey:
It was released stable partly so that 911 dialing COULD be reported and fixed, but NO ONE is going about helping to fix the damn thing. You can't fix what you don't know isn't working...

Edit: and if someone flashed this not knowing something isn't working, it's their own damn fault for not knowing what they are doing because AJY custom roms explicitly states that the maintainer is not responsible for anything that comes from you using their rom. It's called being responsible for your own actions...
[Vibrant Android Development] Jackdog89:
Possible solutions..

1)Look up your local emergency (dispatch) number, there's a standard 10 digit number for every city as well as 911. If 911 doesn't work, program your phone with the other emergency number.

2)GPS has never worked well on this phone and without having source code, it's miracle that they've gotten it to work this well on GB based ROMs.

3)Use dsp manager, if that doesn't work you can try flashing a different kernel. Glitch seems to have resolved this issue.

4)I haven't encountered this issue, but I also don't use the digital recorder.

5)I have the same issue. It's not present for me if I use bluetooth, I'm not sure about using the wired headset. It is annoying, but I don't think every vibrant user is affected by this.
[Vibrant Android Development] mobilebone:
Compatible alright, but running rough.
[Vibrant Android Development] mobilebone:
Fortunately it is not that hard to flash something else. I love CM7, but I need the basic phone functionality. How would programming the dispatch number work with a screen lock?