yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] 12paq:
Funny.. the Vibrant gps has always sucked and always a drama. At least its not your main phone, lol.

Seriously tho, there are a few good Vibrant devs here, Birgertime is a straight shooter and works hard for us, give him a little guidance and he'll work hard and play it right. He just wants to help us out like you.

Thanks!

via my Nook Color tablet with CM7
[Vibrant Android Development] atinm:
Like I said, I have no opinion on birgertime, the only things I know he's worked on are the Phone.apk hack which we need to find a better way to fix before it can get incorporated into CM (I already tried the fix back when we found the mute/unmute solution but it couldn't get merged into CM due to its hackiness, so I never pushed it into the repositories), and the GPS init.aries.rc change, that we tried before and it didn't help and left it out also. Now that a lot more people think that the GPS init change works, and I'd rather not deal with people thinking I've left it out because of some underhand reason, I've put it back in so that you all can try it and if it works, I will be happy and I can finally forget about GPS. The Phone hack cannot get in, and needs a kernel level solution - and I've pointed out the files to anyone who cares to ask, but I am not going to look for the fix because I have other stuff on my plate I'd rather work on. If one of the 'good' Vibrant developers can actually fix this cleanly, I'd be very very happy to merge the fix to CM.
[Vibrant Android Development] Poser:
Roman's contributions speak for themselves.

Atin's contributions speak for themselves.

I think all that needs to be said is that Teamhacksung, and the CM team in general, would prefer that any upstream development that occurs that can result in a better CM ... result in the proper pull request. Furthermore, "developers" (see: MIUI) that benefit from CM code, do not hide behind a screen of impropriety and embrace open source as it is meant to be: community developed, community maintained, community enjoyed.

Lets worry about vibrant development and leave trolling... ummmmm, well... to the trolls.

Sweet, now I shall drink good beer
[Vibrant Android Development] 12paq:
lol.

..and Atinm and crew,

I don't anyone thinks any of that stuff, just ignore it.

thanks for everything.
[Vibrant Android Development] Gen00:
Just a question.. Wondering if CM was going to change the camera apk.. Becuz im not going to lie i like the new style that they have in like the MIUI ROM or in the stock Vibrant.. The one in CM is like having a MyTouch or sorry i feel like its a old CM or something.. I do hope they upgrade the camera apk.. Just saying..
[Vibrant Android Development] Gen00:
Sorry i do wanna say i like the feel of CM on the Vibrant n i cannot wait for a more stable ROM.. Thanks everyone thats working on CM its going great.. ( Just the camera apk bugs me.. lol.. )
[Vibrant Android Development] ewidtfeldt:
It's Google's aosp camera. It won't change because this is an aosp based rom. Sorry dude.
[Vibrant Android Development] Gen00:
Thanks man.. Maybe they'll have something i can flash or install so it can be like the new style after CM7 is done..
[Vibrant Android Development] Poser:
Wow... I was going to flame the #$%& out of you, cause I am inebriated... but then I clicked on your shameless plug of your art...

... and damn, that is solid macro. Period. Nicely done.

[/OT]
[Vibrant Android Development] :
That's a good point. Did you (Apollo) type "su" in the terminal and grant superuser permissions before trying to logcat?
[Vibrant Android Development] Cesarp 24:
Ho do we turn off shutter sound on camara? Pre thanks.

Sent By My CM7 Monster
[Vibrant Android Development] Poser:
There is no setting, I believe you have to delete the actual sound file. It was posted a couple of pages back... (which exact file that is).
[Vibrant Android Development] apollo15rover:
No.. and THANK YOU...works perfectly now!!
[Vibrant Android Development] mk262:
I'm pretty confident there's something about cm7 that changes the amount of audio buffered in certain mp3 stream players.

In every 2.2 rom I've ever used my player (streamfurious, but xiia live works identical) buffers about 7 seconds of audio. Since I moved to CM7 it now buffers about 2 minutes. This is on wifi, it's not a connection problem.

Does this sound familiar to anyone? I tried it on my wife's HTC G2, also on CM7, and noticed it buffers about 2 minutes as well.

Here's a link to the stream I'm using if anyone wants to try it. I've tried it on other streams as well, same result. The bitrate doesn't matter either.

http://www.radioreference.com/scripts/playlists/1/7059/0-5241750832.mp3
[Vibrant Android Development] jt1134:
Hello all

Regarding the mute/unmute bug that seems to plague Vibrant users, I have some code and suggestions that I hope might help. I have passed this info along to atinm, but he was quite busy at that time, so I doubt he has investigated. If you are into building CM yourself, please give this a try :)

Some background :

The libaudio code used in these builds depends on a few functions exported from libsecril-client.so. If you look through the commit history, you can see where coolya pulled that file from the i9000 in order to fix in-call audio, since the Vibrant's library does not export these functions. This caused a few bugs in my builds for the Fascinate, so I redid libaudio to pass everything directly through the kernel instead of relying on libsecril-client.so. This fixed mic issues for my builds, hopefully it can do the same for you folks with minimal hackery. If you look through the libaudio code, you can see that the mute function is dependent on the RIL, which could very well explain why it happens to users on certain networks.

If you would like to give it a shot, clone my latest code from my fascinatemtd tree @ http://www.github.com/jt1134/android_device_samsung_fascinatemtd (the trees on CM and teamhacksung githubs are currently stale). Replace libaudio in device/samsung/aries-common with the libaudio code from my tree, and edit libaudio/Android.mk to remove the ifdef ($(TARGET_DEVICE),fascinatemtd) part. Then replace libsecril-client.so in vendor/samsung/vibrantmtd/proprietary with a libsecril-client.so file from the latest stock Vibrant ROM. Then build as usual.

Today in attempting to fix some other issues, I did introduce an issue where earpiece volume on calls does not work until to you toggle speakerphone. If this helps with your mute/unmute bug, perhaps someone would be so kind as to assist me with that one ;)

Let me know if anyone tries this and what the outcome is. Thanks
[Vibrant Android Development] jwleonhart:
Is it possible to put a different camera on this? This camera app by default kinda stinks
[Vibrant Android Development] zmattmanz:
I'm too ignorant to know all the significance of how CM7 and the development process works but I wanted to say a sincere "Thanks" to atinm who has help create the best experience on my Vibrant hence far. These roms have been far faster and more stable than anything I've used before. People who care about producing quality work based on their standards are awesome. Thanks man.
[Vibrant Android Development] notverycreative:
Already been asked. No. This is AOSP, not TouchWiz. If you want a different camera, there are plenty on the market.
[Vibrant Android Development] roffee:
The video recorder can't auto focus?
[Vibrant Android Development] Joy2DaWurld:
Currently on #48 with modified lib files for FFC + build.prop speed/data mod leading to INSANE amount of drain. Never seen anything like this but I was charged full, wifi off, data off, gps off, no games/apps even open and I'm at 13% after 2 hours. Make that 12% by the end of this sentence.

No idea what's going on but even with this same background I was up to 24+ hours one point with moderate usage, data/wifi/gps off. Nothing has changed and yet the drain is oh so hurtful. Down to 11%...

Edit#2. Even more head-scratching is that SMS, Facebook and all other apps are suddenly slowwww as Eclair (yuck). Non-responsive and incompetent. 10%...
[Vibrant Android Development] numberoneoppa:
I'm on 49. The drain seems very good (I also have the i9000 libcamera.so). I do, however, notice some of that lag you're talking about that I never have seen in previous builds. Not sure what that's about but I assumed it would probably go away on the next flash.
[Vibrant Android Development] Joy2DaWurld:
All I can say is I hope so. I can live with a minor lag but the battery draining makes it literally impossible for me to continue using CM or any other rom with this short of a battery span. Most likely I'll wake up in the morning and ODIN to stock then give this another shot. Any drain more than 10% an hour and I have no choice but to switch back to Froyo. :(

I've always managed to turn off data/wifi when not using but even when everything is off, no apps are open...something else is wrong if I'm still facing the same issue. Blah, just the worst feeling trying to decide between roms other than CM7.

I tend to listen to music as I fall asleep...but I'm actually noticing that my battery life declines even while being plugged in. That's definitely a new one for me.

A screenshot at 2:13am was taken, for an unrelated reason, when I initially unplugged after a full charge. I'm at 3% at 5:22am...3 hours and 9 minutes later. 189 minutes to take up 97% is roughly 2 minutes for 1%. :confused:
[Vibrant Android Development] atinm:
birgertime - please try these if you can, this is the much better way of fixing the Phone mute/unmute if it actually works for Vibrant.
[Vibrant Android Development] michaelh99:
So... Nobody?
[Vibrant Android Development] apollo15rover:
Doesn't look like the robot update went through last night.
[Vibrant Android Development] djf8:
Everyone should be jumping in their seat waiting on biger to log on and try out the audio libs from the fascinate git.

I would pull it and try it if I had any clue what I was doing; unfortunately I know just enough to realize I don't know enough haha. So I'll wait for someone with more experience to give it a go first.

Plus I need my phone for work.
[Vibrant Android Development] Romanbb:
I meant to try this last night but I got caught up in trying to get my formatting right on what I was submitting to gerrit, took longer to get it formatted than to add it to CM.

Anyways, thank you so much jt1134 for helping (and Atin). Currently doing a clean build with all the changes you suggested. My Linux machine takes like an hour to build so I won't know how it goes until later today, gotta get to class soon.

I'll keep everyone posted.
[Vibrant Android Development] nirogu325:
I understand where you're coming from. I switched back to Bionix-v. Oh and if you're focusing on battery, remove the 3G speed/signal entries from the build.prop. They drained my battery like crazy both in Bionix-v 1.3.1 and in Bionix NextGen2. I noticed the difference when I removed them.
[Vibrant Android Development] nedlog:
No ones answered because I believe not many have had this particular issue. The only times I've had this issue was with my network having problems, not my phone. However, you might want to wipe/data and Dalvik and reflash the ROM to see if that helps; that's what I would do...if that didn't work then I'd ODIN back to stock and start over. Sorry I don't have a clearer answer. :cool:
[Vibrant Android Development] Romanbb:
Uploading now, actually, it'll be at http://goo-inside.me/roms/edt/vibrant when it's done, if you so happen to be reading this now, make sure you give it at least 10m before downloading or you'll be sorry :)
[Vibrant Android Development] atinm:
If/when you submit something to gerrit for Samsung specific stuff, add me to the people who should review it because otherwise no one else will look at it and if I am not added, I won't see it unless I remember to look at *all* the submissions. I see that you put in stuff for Signal bars/dbm, and as that isn't specific to Samsung, someone else will have to look at it.
[Vibrant Android Development] Romanbb:
Gotcha. Will do.

Anyone who wants to try the new libaudio can dl it(it's a whole rom) from the link above (the last one in the list). Running it right now, everything seems to work.
[Vibrant Android Development] jt1134:
Awesome. So no more mute bug? What about the speakerphone toggle issue I mentioned?
[Vibrant Android Development] metalman3797:
Since last night after disconnecting from my wifi i dont get 3g. Its stuck on E.

I rebooted multiple times, reflashed, formatted system etc...

When i go into the access points i see SIMPLE and t-mobile US.

proxy, port, username, password, server, mms proxy, mms port authentication type and all not set or just a "*"

any ideas at all?
[Vibrant Android Development] Romanbb:
Preliminary testing (one call from gtalk, LOL) showed no bugs. But I had to go so haven't gotten a chance to test anything thoroughly.
[Vibrant Android Development] Jackdog89:
Try setting up your APN manually.

Name: T-Mobile US

APN: epc.tmobile.com

Proxy: Not Set

Port: Not Set

Username: Not Set

Password: Not Set

Server: Not Set

MMSC: http://mms.msg.english.t-mobile.com/mms/wapenc

MMS Proxy:

MMS Port:

MCC: 310

MNC: 260

Authentication Type: None

APN Type: Internet + MMS
[Vibrant Android Development] jt1134:
Thanks
[Vibrant Android Development] metalman3797:
Now it doesnt have any internet at all :(

any other ideas?
[Vibrant Android Development] Romanbb:
Mute/Unmute Potential Solution

Here, instead of a whole ROM, this is a flashable that includes only the changed files (I believe, Atin, JT correct me if I'm wrong)

I've included

baseline phone.apk from cm7 (to remove my hacked one for testing)

new libaudio.so

libsecril from kb5

just did a test flash and it seems to be working fine

please test and report your results

This is a potential solution for the mute/unmute bug
[Vibrant Android Development] 12paq:
testing now.

thanks for all your work and time! :)

Edit: tested on incoming calls, all good so far. If I have an issue I'll.report back with a log.
[Vibrant Android Development] beren28:
Pay your bill? :)
[Vibrant Android Development] metalman3797:
LOL yeah its not due for 3 more weeks! haha
[Vibrant Android Development] Relikk356:
I called my self from work; seemed to work for me. I will update as i receive more calls.
[Vibrant Android Development] Relikk356:
Did you hit your download cap?
[Vibrant Android Development] }{Alienz}{:
And with this...we bid farewell to the mute/unmute bug. Honestly this ROM is just about ready for prime time now. Just a bit more work on the battery perhaps and it's done. Amazing.
[Vibrant Android Development] Joy2DaWurld:
It's weird I had the build.prop mod for a week and I just started feeling some backlash towards the battery, so I overlooked this. Whatever the case I just flashed a stock version of #48 and we'll see how it goes.
[Vibrant Android Development] notverycreative:
I wonder if this was what was stopping the buildbot from working?
[Vibrant Android Development] djscamper:
gps fix working

The GPS fix is working on my Vibrant with the Birg CM7. My phone always had perfect GPS with all other ROMS as well.

Nice work Team CM7.

Battery drain seems about normal for CM7 for me.

Let me know know if you need me to run any tests on gps stuff.

-Hank
[Vibrant Android Development] notverycreative:
How long did it take you to get your first satellites?
[Vibrant Android Development] djscamper:
Seconds in my car.
[Vibrant Android Development] notverycreative:
Huh. I just sat by my window for five minutes and nothing. But my GPS never really worked to begin with soooooo... :)
[Vibrant Android Development] djf8:
This made me laugh....
[Vibrant Android Development] wyvernwaddell:
No mute/unmute for me...

Mute/unmute not working for me..rebooted and ran fix permissions..no audio at all now..tried speaker button also,no help

(edit) worked on the very first call, but after that, there was no audio at all, couldn't hear the other person and they couldn't hear me either.

Running totally stock Nightly 51.
[Vibrant Android Development] Cesarp 24:
Not working all sorts of radio problems.

Sent By My CM7 Monster
[Vibrant Android Development] 12paq:
First calls worked, but now all audio incoming or outgoing is gone.

I'm on the road but I ran a dmesg, I'll try to post the log as soon as can. Thanks.
[Vibrant Android Development] Romanbb:
Strange, I called myself twice and audio is still working for me.

Maybe there was another dependent file I missed in the flashable that I have in the fully compiled ROM...
[Vibrant Android Development] krazie1:
I'm going to flash the rom that you posted earlier. I'll get back to you with some results.
[Vibrant Android Development] Cesarp 24:
Same for me. I called myself twice and it was good. then after about 30 mins it broke all audio.

Sent By My CM7 Monster
[Vibrant Android Development] metalman3797:
i am not at a cap, i signed up when there was no cap :)
[Vibrant Android Development] krazie1:
So i flashed the Rom that you posted 2 pages back Birgertime. The fist call was all good (perfect). But on the second call they could hear me but i couldn't hear anything from them. The vibrants speaker wasn't working nor was the speaker on the back when i put on the speaker. But the mic was working because they heard me. And thats how all the calls are, they can hear me but i cant hear them.

EDIT: I rebooted the phone to see if it fixes, but now there is no sound at all. I can't hear them and they can't hear me.

EDIT 2: Nvm they can hear me again, i still can't hear them though.
[Vibrant Android Development] ewidtfeldt:
Same here no audio.
[Vibrant Android Development] barribow:
This is a post from a few days ago. I tried both and I was not successful on deleting the file. By the way the filename is "batterystats.bin".

Edit: it says permission denied
[Vibrant Android Development] Relikk356:
Worked great on the first phone call, but not after that. No sound.
[Vibrant Android Development] movieaddict:
easiest way to do this!! make sure u have root then download SGS TOOLS! go into sgs tools and click on apply script. Then click on wipe battery stats and ur done, its that easy. BUT make sure u charge to 100% first before doing it and it may take a few charges to see effects from it.
[Vibrant Android Development] numberoneoppa:
Personally, I think all of this "batterystats" nonsense is... nonsense. ;)
[Vibrant Android Development] moonfire711:
I applied the mute fix flashable without flashing a whole new rom. I had a good first phone call like the rest, but now my phone gets no audio on my end while it works fine for the person to hear me on the other end. I even tried mute/unmute with no dice. ;)
[Vibrant Android Development] jt1134:
What about toggling speakerphone?
[Vibrant Android Development] Romanbb:
No audio here now as well. I shall investigate
[Vibrant Android Development] krazie1:
Toggling the speakerphone button does nothing, there is still no audio coming out the speakers.
[Vibrant Android Development] barribow:
We will see, my phone is not working for more than 2 hours now. When I reset the batt stats I let you know how much it will be improved, without changing the ROM or course.

Edit: my phone battery lasts for about 2 hours if I use it good
[Vibrant Android Development] compuguy1088:
I've been running the full Rom with no issues. I guess I haven't gotten enough calls.
[Vibrant Android Development] hitman818:
Try fixing the permissions in recovery mode and check if that fixes the no audio problem.
[Vibrant Android Development] iynfynity:
Are there any bugs on the latest release other than gps and mute/unmute?
[Vibrant Android Development] atinm:
Explore the voice call and SPK paths - make sure they match up with what's in wm8994_samsung.c. I looked and it looks fine, but that's where it ought to be.
[Vibrant Android Development] 12paq:
Hey jt1134,

Thanks. :)
[Vibrant Android Development] Cesarp 24:
Thanks for your effort. I also want to thank atinm and the cm7 team

Sent By My CM7 Monster
[Vibrant Android Development] Phateless:
Try a data wipe. You probably have some app or widget draining your battery.
[Vibrant Android Development] shreddintyres:
just a thought but if it is dealing with the wm8994_samsung.c it might have to do with users running Voodoo Control app which i believe affects that path, tho i may be mistaken
[Vibrant Android Development] konigswagger:
New Android Marketplace that's compatible with this rom here:

http://www.redmondpie.com/android-market-3.0.26-apk-download/
[Vibrant Android Development] notverycreative:
The new Market is really nice and my GPS works now! (Works being defined as getting a lock *eventually*.)
[Vibrant Android Development] barribow:
What does exactly data wipe do? I only use it when I want to install a new ROM. and then when I restore my stuff through ti back up everything is the same as before.
[Vibrant Android Development] Phateless:
It restores the rom back to original settings and clears all your apps, settings, etc. On first boot after wipe let it sit for 10 mins. Then don't restore data with titanium and see if you still have the problem. If you still do you can always nandroid back.

I've never encountered any of these weird bugs that others are having except for GPS, but that's not a bug.
[Vibrant Android Development] cashyftw:
Which nightly are you using to test your gps?

Sent from my SGH-T959
[Vibrant Android Development] atinm:
birgertime, if you haven't seen yet (you must have), jt1134 made some more mods in https://github.com/jt1134/android_d...mmit/8fd923efcd3c54aec050854ceee225b4fae77d08 last night (he'd taken out too *much* code :-) ), and you should try them too. Make sure the pathnames and control names match what is in wm8994_samsung.c (in the kernel's sound/soc/codecs directory). I think they're the same - it looks right, but need someone who is concentrating on Vibrant to test it.

Actually, I'll just upload something for people to test in a few.
[Vibrant Android Development] atinm:
Ok, uploaded a nightly KANG build that has both the GPS and libaudio fixes - or at least, what we think are fixes - but want people to try it before I commit these changes. The build is what would be the next nightly if I commit these changes, and is a full build. Install like you install a nightly. Remember, this could be quite broken - like any other nightly.

Link: http://www.megaupload.com/?d=QW2RLYLZ
[Vibrant Android Development] djf8:
Can't test until after work today at 4 pm cst.

Hopefully someone has a chance to get in here and test this bad boy out.
[Vibrant Android Development] kelmerp:
So far it's working great. Tested 3 calls with no bug, rebooted and tried another call, and again no bug.
[Vibrant Android Development] gbakabg:
Downloading now
[Vibrant Android Development] sublimnl:
What about gps?
[Vibrant Android Development] Romanbb:
I was studying yesterday, so I didn't have time to do any Android stuff. Looks like you got it covered, though :). Downloading the test build to test it out.

Thanks for your work
[Vibrant Android Development] notverycreative:
I was using the Kang build a few pages back.
[Vibrant Android Development] atinm:
If I get enough confirmations for both mute/unmute and gps - I'll commit my changes (it requires some modifications to common Makefiles too) so that it is available in the next nightlies.
[Vibrant Android Development] nedlog:
Tested good for me so far, only had one call and no problems; don't really use gps but will test later. Thanks for looking into this for us!:)
[Vibrant Android Development] livbean:
Works great for me.

Sent from my SGH-T959
[Vibrant Android Development] roffee:
My phone can find Satellites, but very slow, looks like it don't download Satellites data to speed lock.
[Vibrant Android Development] kelmerp:
Mine seems to be doing the same. It can see that there are satellites but none of them lock.