JP wrote: > Hmmm, I would suggest moto has been around the block enough to be > familiar with the issue tracker...
I realize that. I'm not quite sure what Moto is expecting to happen given the posts to date. > With that said, uhm, rhetorically asking, hasn't Android outgrown the > goto b.android.com approach a while back? Right now, we have a six-line stack trace, no sample code, and no media file. If that is all Moto wishes to supply, that is up to Moto, but Moto will likely be disappointed with the results. What would materially improve the odds of getting answers would be a project (with all necessary files) that reproduces the problem. b.android.com not only is a fine central place to stick such a project (or a link to a project hosted elsewhere), but it increases the odds that it will get some amount of Googly attention. It'd be a good idea to cross-post the issue link here as well, a point I thought of about two seconds after pressing [Send] on my previous post. If you have better advice for how to get Moto's problem solved, please post it here. Better yet, if you have a solution to Moto's problem, please post it here. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 2.x Programming Books: http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
