[Vibrant Android Development] Genesis3:
Just the library for 911.

The library is confirmed to be from aries_common, including the recent commit; I built from scratch and verified checksums.

The list of emergency numbers is commented out because it is unnecessary. In point of fact if you try to stick an ordinary 10-digit number in there as an "emergency" number (I tried this in a failed attempt to get a configuration I could pound on with a call to my house that would exhibit the problem) the phone will pass it down as an emergency number exactly as you declared but the modem in the phone will ignore your claimed emergency number and happily turn around and call 911 instead. Guess how I found that out? (This is not, incidentally, recommended.)

Oh, for those who are interested, the Hercules (SGS-II T-Mobile) has a similar problem with audio routing on CM7. Since the Hercules could be faulted with ordinary calls, and I happen to own one, I would have likely been able to run this down. This was the reason that I put forward the request for access to that repo - I couldn't fault the Vibrant EXCEPT on 911 calls, which I (of course) can't make freely, which kinda sucks when you're trying to debug something. I don't own a crespo-based phone, unfortunately.

But, I was assured by those who denied my request that manufacturers would never, ever use similar APIs and hardware and thus what was found for one phone made by them would never apply to the other(s) made by the same company.

Of course in light of the truth now being out there on the crespo and aries it would be rather interesting to look at the libaudio code for the Hercules and see if there might be a state machine problem there too that's amenable to a similar fix.

But I still can't do that because the repos are not available. Don't be surprised, however, if the Hercules is "magically" fixed here shortly.

Oh, and if you look at the root of that commit on the aries library and then follow it back to the crespo one, please note the date of the diff, where it came from (a real corporate email address! That might be a real developer!) and that unlike the one-liners found in other places there's a real comment on what's changed and why too, which along with the commit itself (all of a couple of lines) is more than sufficient to explain what's going on and what was found. That's called "documentation" and it helps a lot when you're trying to figure things out.

The bottom line: If wee-wee waving was less important than actually resolving problems the Vibrant would have had the 911 issue resolved several months ago and the Hercules probably would have been fixed as well.

PS: If you detect plenty of sarcasm in this post, that would be a correct interpretation as well. I'll be posting up a manifest and overlay directories as soon as I can get the time to verify that it pulls and builds from zero, so if anyone wants to grab and work (or just compile) they can. You might enjoy the GPS performance improvements in that load as well. There is only one warning on the GPS -- the first time you use it after a cold boot Wifi has to be off or it will take forever to init, and if you abort the init it will lock out until you reboot again. The assist data is supposed to come over the cell connection and the link it IS brought up properly to retrieve it, but something's getting trashed in the process. Just start it once on a cell connection and it will lock within ~10 seconds or so -- from that point on it's fine. I'm looking for that problem and there's a decent chance I'll be able to resolve it.