yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] djf8:
Interesting....it says he did.
[Vibrant Android Development] bobshute:
renardk764, who is Captain Renard with Austin/Travis County EMS has also tested/confirmed that 911 works ICS Passion v7 which is a AOSP 4.0.1 rom
[Vibrant Android Development] manjish:
ya neobuddys ics passion v7 claims in big letters that 911 works......i see a bit of hope for ics cm9 now...im not in USA to test 911...sorry for that...and atinm we respect u and im still running ur work on my vibrant and it is amazing....
[Vibrant Android Development] atinm:
That fix is already in the Vibrant and no, it does not fix E911. It was a partial fix, but that isn't enough. renardk764 confirmed this - 911 will work, but E911 will not. The Vibrant ICS port is also using our source, and therefore E911 will not work there either (I confirmed with the developer that he is using our source - and it is very specifically mentioned in his OP so it isn't like this information is not available to everyone).

I am glad someone is continuing with our code base - even though I have stopped working on it, I still want Vibrant developers who actually have Vibrants to continue so that if they can find a fix, CyanogenMod can be resurrected. We've been looking for Vibrant developers to take it over for a while, and am happy that ICS is available for it now so hopefully the developers will find a fix for the E911 issues as well.
[Vibrant Android Development] RaptorFB:
Where would I find instructions on installing a non cm7 rom from this point? I am on nightly 182, and there were instructions on the old cm7 thread but I cannot find them anymore.
[Vibrant Android Development] ali1276:
Atinm,

Here renardk764 confirms both e911 and 911 work and transmit location data to the police station!

http://xdaforums.com/showthread.php?p=20649759#post20649759
[Vibrant Android Development] jzero88:
Interesting. Would like to see things pan out :D
[Vibrant Android Development] ferhanmm:
Hope that was enough for atinm to begin work again. With his help to get cyanogen running the vibrant was really brought back to life.
[Vibrant Android Development] kcshmo:
What's wrong with you? The developer doesn't owe you anything. He doesn't even need one reason if he decided not do work on it anymore. He certainly doesn't need any excuses. If anything, Samsung/Tmobile might owe you something since they took your money. I have a Vibrant myself, and I certain would like some help to get the latest and greatest. If it doesn't happened, then it's time to move on, dude.
[Vibrant Android Development] Genesis3:
http://www.mediafire.com/?czo03t36py5sai4

CM7 7.2.0-RC, private KANG, working 911 (with and without SIM, transmits GPS location too) and the GPS both works and is VERY fast.

A bit of cooperation (like documenting where certain things in the Vibrant tree came from eh?) would have made this much quicker. As it was it was a kludge-together.

I'm not going to support this until and unless someone tells me where the source to the library that got replaced came from, and the CM7 people know damn well what I'm talking about too.

But if you want it, there it is.
[Vibrant Android Development] karimsaud21:
Is their no way you could submit the patches upstream then?
[Vibrant Android Development] Exel:
I'm not going to support this until and unless someone tells me where the source to the library that got replaced came from, and the CM7 people know damn well what I'm talking about too.

Hm, doubt it, unless.. they can come to an agreement and forget about the past.
[Vibrant Android Development] sixstringsg:
Is there source for this so that we can work on it for ICS? We've fixed GPS for ICS, but not 911.
[Vibrant Android Development] djf8:
Thanks for this man....running cm again feels so smooth. Everything is working great also....GPS is has worked every time so far.
[Vibrant Android Development] makelegs:
Don't look now....

http://review.cyanogenmod.com/#change,11492
[Vibrant Android Development] karimsaud21:
hehehe, didnt see the above post
[Vibrant Android Development] djf8:
Holy crap!
[Vibrant Android Development] Genesis3:
Yep.

And if the provenance of that libaudio code had been documented up front (where did it come from?), it would have been found oh, two or three months ago.

Further, we still don't know where the OTHER library came from. I have the link to the bugtracker thread where it is, but the origin of that file is not disclosed.

The file that I grabbed and am using is here:

http://code.google.com/p/cyanogenmod/issues/detail?id=4681

("Here, swallow this pill and see if you explode!")

In this case the answer is "no, you do not explode", but we still don't know where that file came from.
[Vibrant Android Development] makelegs:
It remains to be seen when official support might be resumed. As of now, it does not compile via the "normal" method.
[Vibrant Android Development] Dougfresh:
The announcement does or doesn't mean we're going to be supported again for cm9?
[Vibrant Android Development] Genesis3:
I would not expect "official" support to be resumed.

However, once I have the changes I commented out of the SamsungRIL file put back in and verified as working (that piece of code, as in CM7, throws exceptions upstream under certain cases and can blow up the radio) I'll spend some time getting a manifest up where everyone can get at it. That will allow anyone who wants to do so to be able to build.
[Vibrant Android Development] sixstringsg:
CM7 hasn't had kernel changes since quite a while, so you should be good in that regard, and we have the ICS changes adapted to Vibrant already.
[Vibrant Android Development] Genesis3:
Yep.

The SamsungRIL.java changes I made may be useful for ICS as well, although the perusal I did of the ICS source divulged that there has been some fairly significant organizational changes in some of the code under that general part of the framework, so whether it's a "drop in" is unknown to me. They're not monstrous but they do stop exceptions from being thrown where they shouldn't be.
[Vibrant Android Development] atinm:
We have e911 and 911 working in CyangenMod now, but as I said - we're now looking for a maintainer for the Vibrant who is actually able to work with us as part of the team. If you are a developer and willing to work with us (there is at least one person who is disqualified due to being someone I refuse to work with again), you can PM me or Pawitp here and we'd love to have support for Vibrant again. Just not from the two of us directly as we are not going to work on it without actually having a phone and being overworked as it is (though work we do that is common will of course still be used on the Vibrant). We'd really rather have another developer or five join teamhacksung for Vibrant support of CM7, CM9 and beyond.
[Vibrant Android Development] bigtom624:
Thanks Atinm, this is great news. Hopefully it will all work out.
[Vibrant Android Development] makelegs:
Wish I had the skillz or the time....or the device =-O
[Vibrant Android Development] jrafael:
@Genesis3

I see you also commented out some lines in the build.prop, is that also part of getting this lib working correctly ?

# ro.ril.ecclist=911/0,112/0,911,112
# ril.ecclist=911/0,112/0,911,112
# ro.telephony.gsm.ecclist=911/0,112/0,911,112
# ro.telephony.ecclist=911/0,112/0,911,112
# ro.telephony.call_ring.delay=3000

Removed:
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2

Another question, besides using this lib is there anything else that needs to be implemented into the rom (ie MIUI/CM9) to get 911 properly working ?
[Vibrant Android Development] bearsfan85:
nevermind

--10 char
[Vibrant Android Development] pawitp:
FYI, crespo and aries is the exception rather than the norm. And maybe you'd understand more of the build tree and the situation if you spend time reading code rather than writing these long complaints.
[Vibrant Android Development] bearsfan85:
just out of curiosity what all would a vibrant maintainer have to do, I feel like most of the things would just be modified from the I9000, correct me if I'm wrong, I dont want to belittle the work that you have done but I do have a friend who is knowledgeable in this area but he is in school and cannot take on too heavy of a work load is all.
[Vibrant Android Development] pawitp:
No. The maintainer for Vibrant fixes Vibrant-specific bugs and test things to make sure common changes don't break them. There are quite a few Vibrant-specific bugs (I think) we still have (such as GPS, earsel and other stuff).
[Vibrant Android Development] bearsfan85:
thanks for the quick response I will forward this to him, he doesnt have a vibrant but I have no problems letting him use mine
[Vibrant Android Development] makelegs:
Santa came late!

Ok guys...I have a fresh, vanilla, kang for you to test. Please nandroid, first! This would not have been possible without some

critical

help from pawitp. Gimme some feedback, and if this is looking good, then I will build a skanky kang with the typical cherry picks for it tomorrow.

Edit: New link to euroskank

PLEASE BRICK MY PHONE

Build has UI tweaks only. Everything else is current vanilla.
[Vibrant Android Development] duboi97:
Downloading. Does it require you to wipe?
[Vibrant Android Development] Mjharns:
Do you have change log?
[Vibrant Android Development] makelegs:
If you are running cm7, the you shouldn't have to wipe. If not, then it may or may not be advisable to.
[Vibrant Android Development] makelegs:
There hasn't been a vibrant build in weeks. Refer to gerrit for all the changes that have been merged in that time frame.

The real question that needs answering is does this build work? If so, then we're in good shape to add the same cherry picks I add to captivate and fascinate.

And if someone wanted to test TV-out, that would really be helpful, too!!
[Vibrant Android Development] es7241:
I've been running this for about an hour and it's been good so far.

Is there any hope on cm9, seeing the 911 fix, or is it already in the code and we just need to compile it?
[Vibrant Android Development] makelegs:
I would think that the answer for CM7 bodes well for E911 in CM9, too. Until they find a maintainer for Vibrant, I would expect development to slow to a crawl. Universal stuff in gerrit should still apply, though.
[Vibrant Android Development] Genesis3:
The ICS builds are predicated on CM9 and don't have this bug as the people doing it never picked up the bad libaudio code. The libaudio in the ICS builds here is different than the one that builds from the aeries source, however, which implies (rather strongly) that they lifted a libaudio.so from somewhere else rather than build it.
[Vibrant Android Development] hurtz777:
Makelegs your Lang runs great with no bugs and it seems a little zippier then nightly #182. Do you have 911 fix integrated in it? I can't wait to try your skanky kang with cherry picks. Thanks for the work man! This is definitely the fastest rom for the Vibrant to date with Glitch 13.1 kernel using smartass v2.
[Vibrant Android Development] makelegs:
good to hear.

Skanky version may be delayed. Experiencing technical difficulties.
[Vibrant Android Development] hurtz777:
No rush. Just keep it stable and fast.
[Vibrant Android Development] makelegs:
Semi-Skank build

Fortunately...I ran a build with the ICS font and custom rings before I ran into technical problems that are preventing a full on skanky build.

I updated the OP link and the link from last night to link to euroskank for that build. Should be exactly the same build other than the UI tweaks.
[Vibrant Android Development] VeryCoolAlan:
I can confirm that TV out doesn't work only sound.

Sent from my Titan
[Vibrant Android Development] makelegs:
is the sound at least in stereo?
[Vibrant Android Development] VeryCoolAlan:
Yes. Not mono

Sent from my Titan
[Vibrant Android Development] hurtz777:
So this new build has all the cherry picks?
[Vibrant Android Development] jvpde:
Not yet. OP hit some problems when he was trying to compile.
[Vibrant Android Development] makelegs:
Only a couple of UI tweaks. No cherries whatsoever.
[Vibrant Android Development] duboi97:
When are we going to expect some cherries ;)

I just noticed you live in Kansas City, same here :D
[Vibrant Android Development] makelegs:
As soon as I can make it compile again. I hit a wall.
[Vibrant Android Development] pawitp:
Try plugging the red or white cable into the yellow slot. Some cables have it swapped.

(Or there might be a bug in the kernel micbias handling preventing tv out from working)
[Vibrant Android Development] jrafael:
Also, TV's itself can be very picky, for example my 32" lcd (dynex) doesn't pickup my phone's tv out signal, however in my 10+ year old CRT (Sharp) works just perfect, this was tested with stock unrooted froyo as well with custom roms (froyo, GB, ICS) with the same results.

So I really don't know if the phone signal it's not "strong" (voltage) enough for the new TV or that my LCD it's not 100% compliant with composite standards ? :confused::confused::confused:
[Vibrant Android Development] VeryCoolAlan:
Yup I tried and just sound.
[Vibrant Android Development] makelegs:
Have you actually tried with this kang?
[Vibrant Android Development] ew:
Does anyone know if the current build includes the BT GPS drivers?
[Vibrant Android Development] makelegs:
They might have been merged before I built it. It's possible that I missed them by a short amount of time. I think what your talking about applies to external gps devices, though. Does anyone really use those with their phone?
[Vibrant Android Development] ew:
It looks like the BT GPS did not make it.

I actually use it. Because of all the GPS issues with the Vibrant, I purchased a external BT GPS receiver. Now that I have it, it is great to be able to use. I get a quick lock and accuracy below 10ft with no drift.

Hopefully it will make it into the next build.

Thanks,
[Vibrant Android Development] makelegs:
Need tester!

I'm gonna need to test a potentially skanky build before I even think about posting publicly...

Any volunteers?

It should be uploaded in about 10 minutes...it should either be a typical skanky build with new boot animation, or it might just blow up ur phone. I'd test it myself if I could.
[Vibrant Android Development] jrafael:
Is this the new rom ?

http://fitsnugly.euroskank.com/gigglebread/vibrantmtd/

update-cm-7.2.0-RC0-Vibrant-KANG-signed.01072012-0318.zip

md5: e167bf39fbc0b919fd4ea67409adf9a9
[Vibrant Android Development] hurtz777:
Makelegs does it have the cherry picks? I would be willing to test it. Please send me a pm with link.
[Vibrant Android Development] makelegs:
Nope.

but if ur volunteering, say so, and I'll pm a link
[Vibrant Android Development] jrafael:
Hit me with a brick !!!! :D

PS: I have an unbrickable moded vibrant
[Vibrant Android Development] makelegs:
Ok....so build prop is is for captivate. That's my bad. Can someone send me a copy of vibrant build.prop so that I can try to fix it?

nevermind....I should have it!
[Vibrant Android Development] makelegs:
I think I just fixed it! Running another build, now, for testing
[Vibrant Android Development] Dougfresh:
Yeah I want to brink my phone!pm me:D
[Vibrant Android Development] makelegs:
test build status

A couple of brave testers are currently doing the dirty work. About to send another test build, in a few minutes. If they tell me everything is golden, then I will broadcast an official skanky version over twitter, here, shortly.

I've been banging my head against the wall for 2 days on this. JT1134 was kind enough to help point me in the right direction, so that it would finally compile, again. I owe him some serious kudos!
[Vibrant Android Development] makelegs:
GIGGITY!!!

All systems appear to be "GO!!!"

OP updated :cool:
[Vibrant Android Development] makelegs:
Duplicate build uploading now...

Just to avoid some confusion....another build is uploading right now, but it should be exactly the same as the one that just uploaded a few minutes ago.

I was having some trouble with my build script acting correctly, but it appears to be fixed now. Didn't want anyone worrying about what might be wrong with the previous version, or different in the "new" version.

THEY BE THE SAME :D
[Vibrant Android Development] makelegs:
Special thanks to hurtz777 and jrafael for testing my funky build and helping me to avoid freaking a bunch of folks out.

:D:D:D
[Vibrant Android Development] sixstringsg:
Is there a possibility of pushing your work to github so more can play?
[Vibrant Android Development] makelegs:
I honestly haven't "created" anything to add to github. In fact, the final piece to my puzzle was found on github. I was actually minutes away from asking you for help, earlier, but JT was kind enough to point me in the right direction. That dude is salt of the earth!
[Vibrant Android Development] sixstringsg:
Well if you get a minute, I would like to be pointed in the right direction as well :)
[Vibrant Android Development] hurtz777:
Makelegs can you explain to me what cm7.2 RC0 source this is kanging? Was it the last nightly that never made it to the vibrant buildbot or is it some kind of up to date generic nightly build that you added cherry picks to? With this kang are we Vibrant owners up to date with all that CM7.2 has to offer as of today? Sorry for the newb question but I just want a better understanding of where this build comes from. All I know is that it is slightly zippier all around including data then CM 7.1 Nightly #182 for Vibrant. Nightly #182 was CM7.1 still wasn't it? Or was it CM 7.2 RC0? I am using NeoR18 12-03 Voodoo Color + LED Notifications +didle and it runs lightning fast @ 1.3ghz using Smartass V2 governor and undervolted from -25mv to -150mv. Thanks again for this bad ass build! This is without a doubt the fastest from available for the Vibrant! I would be happy to test any future builds and I hope you continue CM support for our Vibrant since nobody else has stepped yo the plate yet.
[Vibrant Android Development] makelegs:
Short answer: you are as current as my repo sync from Sunday morning.

This should include any commits since vibrant was axed, including the most recent E911 fix and libtvout (both merged; not cherries). All cherries are listed in the DL directory, and OP list is up to date, too.

Additionally:

Buildbots stopped, but cm7 development continued. The Kang must go on!!! I haven't flashed an "official nightly" in over a year ;-)
[Vibrant Android Development] mohamobo:
makelegs, i got this message when pressed the thanks button.

"Sorry, you are limited to 8 thanks per day"

BTW, thanks for SKANG-A-LANG-A-LANG!!!!
[Vibrant Android Development] Richcar:
Any body have a working vending app for this rom. Thanks
[Vibrant Android Development] hurtz777:
The latest gapps should work fine. I just added the latest 3.44 market apk to gapps zip and flashed. Search for 3.44 market in forums.
[Samsung Galaxy Nexus] TheEdge65:
Very weirdly I noticed tonight that my notifications weren't making a sound. When I dug a little deeper I found I had no sound right across the board, ringtones, notifications. music, youtube, ANYWHERE !

I have looked through all the settings and nothing is set to mute and all volume levels are up. Factory reset has not cured this.

Anyone have any ideas ?

Thanks
[Samsung Galaxy Nexus] santacruzdz:
I got my phone today...sound worked once then all sounds are gone??? No solution found?!!!! Is it a hardware issue?? Should we return it?
[Samsung Galaxy Nexus] Luxferro:
Try plugging in the headphones. Maybe something is wrong with your headphone socket and it thinks headphones are plugged in.
[Samsung Galaxy Nexus] RTContent:
I agree, this has happened to make with previous phones on a few occasions. I think it can happen if you get a little dirt in the headphone socket.
[Samsung Galaxy Nexus] TheEdge65:
Gave up and returned mine. I couldn't get the sounds back. Hopefully a replacement will be with me in a couple of days.
[Samsung Galaxy Nexus] rokfor2000:
Did any of you use any software like Volume+, Volume control etc... ?
[Samsung Galaxy Nexus] santacruzdz:
it has nothing to do with the socket or the headphone, the phone doesnt ring or produce any sound in "normal profile". it just vibrate in all profils . i returned mine too today !
[Samsung Infuse 4G] Kevinr678:
So it's been a little while since we've seen a new leak. I'm thinking Gingerbread is now done and in the hands of AT&T. What do you guys think? please, discuss.
[Samsung Infuse 4G] abacona:
Tbh I don't think at&t gives a **** about infuse owners. It didn't sell too well. They're focusing on marketing the skyrocket and attain sgs2 models.
[Samsung Infuse 4G] Kevinr678:
Gingerbread's clearly coming... Look at all the leaks. They aren't just made to tease.
[Samsung Infuse 4G] Kevinr678:
And the Infuse actually sold extremely well. I worked at an AT&T store.
[Samsung Infuse 4G] jpapa1086:
The infuse was #2 selling phone all summer
[Samsung Infuse 4G] Dani897:
I've met some ignorant people but some of these posts are mind boggling. Like they manage to ignore the entire forum just to respond to a single post and give their opinion about att.. We only have about 6 or 8 leaks for new firmware on a pretty regular release schedule and an att announcement that we get GB in 2011 and several threads showing the infuse as a top seller but we get responses like these.
[Samsung Infuse 4G] JLR9914:
So, we are 99% sure that we will get it. LOL At least by early to mid January, right.

But seriously, I hear you Dani, I love my phone and can't understand why since the SG2 and Nexus and Atrix are out suddenly people call ours ****e? It is annoying. Our phone is top quality.

Besides, after reading the discussion in the leak threads about how the video issue came up with all of the modded kernels and most importantly the assumption that AT&T developers care about what we do here at the forums so much that they use us as guinea pigs(in a good way) they stopped releasing leaks until they were ready for the official, I just took those words for GOLD and decided we are waiting. Was I wrong?
[Samsung Infuse 4G] CheesyNutz:
I think the OP thinks to much :-P

E3D
[Samsung Infuse 4G] JLR9914:
LMBO@ Cheesy

But seriously, can you think too much when software development is involved?
[Samsung Infuse 4G] Kevinr678:
Maybe I do, but it seems pretty probable to me, Cheesy :p
[Samsung Infuse 4G] apallohadas:
1) Yes, AT&T Doesn't give a damn about firmware updates.

2) The Infuse sold extremely well.

3) I've seen very little advertising on the Skyrocket, yet continue to see ads for the Infuse (as recently as this past week on TV and yesterday in a target flyer.)

I've decided I can live with the ROMS in our forums here and AT&T can kiss my shiny metal arse.
[Samsung Infuse 4G] shiftylock:
Well, not sure if this is any indication, but my local Walmart is selling infuse cases, as well as screen protectors, while there is nothing on the SGSII or Skyrocket. Honestly I think Samsung is spewing out more expensive versions of practically the same phone, and the Infuse is the OG in this siuation. *thinks of carbon copying phones, and sees a conspiracy theory!*

Since I follow these forums as well as the Xperia Play forums, my hypothesis is:

-They were testing GB

-They LOLragequit and decided to make all newer android phones upgradeable to ICS

-they plan on releasing ICS in January or February.

I know these are some out-there speculations, but AT&T tends to send firmware updates in batches, and it has been confirmed by Sony Ericsson that they are planning on ICS for the Play by February 2012.

Just my 2 cents on the matter.
[Samsung Infuse 4G] Dani897:
What I think is that as usual att is behind schedule. Maybe Samsung put us off while developing a whole new line. Either way I doubt we will see official this month. but the idea we will never see it is just ignoring the evidence. They wouldn't be working on it so aggressively if they didn't intend to release it. Also since att probably only wanted one update the wait is kinda a good thing since we'll get at least 2.3.6 and not 2.3.3 like Rogers got.
[Samsung Infuse 4G] CheesyNutz:
I honestly don't think we will see gb officially. Bit I have had gingerbread on my phone for a while now

E3D