[Vibrant Android Development] dcchristopher:
Thanks, Eugene ... it's nice to have a stable phone again, despite the bugs. 2.1 was just an anathema. I'm tentatively willing to trade some of these issues for Froyo. I mean, I was ready to throw the phone out the window. Getting a data connection to send/receive a 2K packet across had become quite the ceremony. All those "fixes" the community has been putting out eventually crippled the phone.

The install went without a hitch. I just followed your instructions and it took me like 5 minutes (why would anyone not simply use "adb reboot download", I will never understand). This was also my first Odin install (was a little wary of learning a new trick after all the update.zip flashing I had been doing for the last year and a half). Now that I am comfortable with Odin, it's good to know I can restore back to stock UVJFD if need be.

So far I have found the following issues with this release:

- swapped volume keys

- home button acts as back button

- proximity sensor inop (power/lock button works well for the purposes of turning the screen on/off during calls)

- no media sounds (incoming call and alarm volumes work ... the rest don't); ouch, this is a little worrisome

- avatar reports it's locked and won't unlock; I will just miss using this movie to show off the screen

- GPS inoperative

- corrolary of the above, *#*#1472365#*#* doesn't work on this build so we can't even mess with the SUPL settings

- Search touch button doesn't vibrate like the rest (but it does work)

- Swype isn't aware of any installed languages so it won't work (someone else wrote there was a licensing issue ... perhaps that's the root of the problem I am seeing)

- date format (dd/mm/yyyy) in notification area is not indicative of chosen Locale (English-US); this being a Euro release, that's apparently all it knows

Seriously, having a stable, responsive phone (especially the data connection) is enough of a positive change to warrant putting up with all of the above. I just hope I can get sound to work over A2DP. My phone is my preferred entertainment center in my car. :(

For people looking at linpack, quadrant, neocore scores to gauge performance, please understand that the "butt dyno" is a lot more indicative of performance in phones than the best 0-60 time. What people have done with some of the partition tricks is good old Texas sharpshooting. They moved the target around their best grouping and yelled bullseye. Quadrant, for example, values the database reads/writes. So, moving dbdata to a faster, less controlled memory location "seeminly" sends the performance through the roof. Meanwhile the ALU and GPU test scores are identical. The overall score however is double. Anyone who thinks the phone just got faster across the board or that the areas that did improve will help with more than just a sliver of one's phone usage, is kidding oneself.

Again, great work Eugene. Your contributions are greatly appreciated. Any plans to iron out some of the show-stoppers? I would be willing to do the leg work if you could point me in the right direction. I am not a phone dev but I have been writing software (4GL mostly) for the last 10+ years. I totally understand if you don't have the spare cycles to do so. The official update is just around the corner.

Best,

Demetrios