Thank you so much for this insight. I don't think this SDK has any
future in the first place. In any case I would not want to work with
it in the future.
On May 21, 1:36 pm, Dianne Hackborn hack...@android.com wrote:
Also don't count on being able to do that in the future. Note that even
On May 23, 12:44 pm, chcat vlyamt...@gmail.com wrote:
Thank you so much for this insight. I don't think this SDK has any
future in the first place. In any case I would not want to work with
it in the future.
And developers who would rather not scrub potentially identifiable
data from a private
On Friday, May 20, 2011 6:16:39 PM UTC-4, TreKing wrote:
On Fri, May 20, 2011 at 4:43 PM, chcat vlya...@gmail.com wrote:
OK. Asynchronous notification, like exception handler in application code
to receive that warning from OS.
The warning in the logcat just indicate that the app / system
Also don't count on being able to do that in the future. Note that even
though there is a permission, there is not actually a public API to read the
logs, so any attempt to do so requires the use of private APIs that may not
be supported in the future. Also since there have been continual issues
OK. Asynchronous notification, like exception handler in application
code to receive that warning from OS.
Note that I implemented MediaRecorder.OnError and MediaRecorder.OnInfo
handlers in my app. Neither seems to catch anything useful.
On May 20, 1:59 pm, TreKing treking...@gmail.com wrote:
On Fri, May 20, 2011 at 4:43 PM, chcat vlyamt...@gmail.com wrote:
OK. Asynchronous notification, like exception handler in application code
to receive that warning from OS.
The warning in the logcat just indicate that the app / system decided to log
something for that case. It does not imply
6 matches
Mail list logo
