Re: [android-developers] Re: Send bug report from 4.1
On Thu, Dec 20, 2012 at 4:06 AM, Latimerius l4t1m3r...@gmail.com wrote: GOOD ADVICE QFE. This. Seriously. - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Send bug report from 4.1
I introduced logging into an app-private file a while ago for different reasons (partly because the system log on some devices is spammed beyond belief) and I'm happy for having done that. Access to the private log is uniform across platform versions, everything's fully automatic (no need to ask users to perform ridiculous exercises with their device's buttons). I've been attaching the last 100 (IIRC) lines of the log to my ACRA reports which has been unbelievably useful to me, and is hassle-free with a private log file. I believe that unless you often need to see a broader system-wide context to solve your bugs, this is the superior solution. And it' s not even hard to do, I deployed it very late into the dev cycle, in a code base of 35000-4 lines of Java teeming with Log.xxx() calls. This is actually part of a more general strategy of avoiding to rely on platform services as much as possible because they tend to break. There might even be good reasons for that, I don't mean this to bash Google. The platform's still under rapid development, breakages are probably unavoidable and all that. I don't actually care as at any rate, the fact remains that breakages are frequent and that's what matters. And you don't need to tell me how this is a terrible engineering decision - I know I should reuse stuff, but stuff that breaks under you is *not* reusable, I'm sorry. On Thu, Dec 20, 2012 at 8:17 AM, Pent supp...@apps.dinglisch.net wrote: Other than POWER + VOLUME UP + VOLUME DOWN, I am unaware of a way to collect the bug report on 4.1 without a copy of the Android SDK installed. If anyone from Google is reading: for the love of God, please put a toast or audible notation or similar in when this key combination is registered. Since it takes about 10 seconds to do anything you have no idea if you've hit the right key combination or not. You've just made debugging super-hard by reducing the system logging access, please at least make the workarounds usable. Trying to get the users to use this key combo or attempt to unlock the secret developer options (after you've found out if they're on 4.2 or not) is just embarrassing. Pent -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Send bug report from 4.1
I tell users to install alogcat and send me a snapshot. This seems to work even on non-rooted devices. On Wednesday, December 19, 2012 7:45:23 PM UTC-5, Nathan wrote: Hi From discussions previously here, I am aware that Android 4.1 has rendered tools such as Sendlog worthless for collecting log cat logs. There was also mention of some secret keystrokes that might produce an error log. Something like power + volume up+ volume down. On Galaxy Nexus. I can't really push both volume up and volume down at the same time sine they are on a rocker type switch. I think I got it right once but I was lucky, and I think the method will be . There was also talk of making a more user friendly way in settings to do this. Is there any procedure that will work on, say, Razr Maxx HD, or ASUS Transformer TF700T. I of course know that the real solution is to write my own log collection dialog which will read from my own apps log only on 4.1 and above. But I am not inclined to tell a customer Just wait till next month's release if there are some alternate ways of diagnosing the problem. Nathan -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Send bug report from 4.1
On Wed, Dec 19, 2012 at 7:58 PM, lbendlin l...@bendlin.us wrote: I tell users to install alogcat and send me a snapshot. This seems to work even on non-rooted devices. However, it will not work on Android 4.1 and higher. aLogCat can only report its own LogCat messages, not ones from other processes. That's because READ_LOGS can no longer be held by normal SDK apps (it is signatureOrSystem now). On Wednesday, December 19, 2012 7:45:23 PM UTC-5, Nathan wrote: There was also talk of making a more user friendly way in settings to do this. The hidden Developer Options on a 4.2+ device has a Take bug report option that emits the same report as does the magic key combination. Is there any procedure that will work on, say, Razr Maxx HD, or ASUS Transformer TF700T. Other than POWER + VOLUME UP + VOLUME DOWN, I am unaware of a way to collect the bug report on 4.1 without a copy of the Android SDK installed. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 4.4 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Send bug report from 4.1
On Thu, Dec 20, 2012 at 10:07 AM, Mark Murphy mmur...@commonsware.com wrote: On Wed, Dec 19, 2012 at 7:58 PM, lbendlin l...@bendlin.us wrote: I tell users to install alogcat and send me a snapshot. This seems to work even on non-rooted devices. However, it will not work on Android 4.1 and higher. aLogCat can only report its own LogCat messages, not ones from other processes. That's because READ_LOGS can no longer be held by normal SDK apps (it is signatureOrSystem now). An alternative is integrate ACRA in your app which can use the logcat command to read you app's log entries, no need for adding permissions. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Send bug report from 4.1
I just uninstalled 4.2.1 because I couldn't find the developer options any more in the settings, and thus was unable to use adb. Why do they make that so difficult? On Wednesday, December 19, 2012 8:07:29 PM UTC-5, Mark Murphy (a Commons Guy) wrote: On Wed, Dec 19, 2012 at 7:58 PM, lbendlin lu...@bendlin.us javascript: wrote: I tell users to install alogcat and send me a snapshot. This seems to work even on non-rooted devices. However, it will not work on Android 4.1 and higher. aLogCat can only report its own LogCat messages, not ones from other processes. That's because READ_LOGS can no longer be held by normal SDK apps (it is signatureOrSystem now). On Wednesday, December 19, 2012 7:45:23 PM UTC-5, Nathan wrote: There was also talk of making a more user friendly way in settings to do this. The hidden Developer Options on a 4.2+ device has a Take bug report option that emits the same report as does the magic key combination. Is there any procedure that will work on, say, Razr Maxx HD, or ASUS Transformer TF700T. Other than POWER + VOLUME UP + VOLUME DOWN, I am unaware of a way to collect the bug report on 4.1 without a copy of the Android SDK installed. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 4.4 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Send bug report from 4.1
it is hidden. http://howto.cnet.com/8301-11310_39-57549207-285/restore-the-developer-options-menu-in-android-4.2/ On Wednesday, December 19, 2012 9:18:56 PM UTC-5, lbendlin wrote: I just uninstalled 4.2.1 because I couldn't find the developer options any more in the settings, and thus was unable to use adb. Why do they make that so difficult? On Wednesday, December 19, 2012 8:07:29 PM UTC-5, Mark Murphy (a Commons Guy) wrote: On Wed, Dec 19, 2012 at 7:58 PM, lbendlin lu...@bendlin.us wrote: I tell users to install alogcat and send me a snapshot. This seems to work even on non-rooted devices. However, it will not work on Android 4.1 and higher. aLogCat can only report its own LogCat messages, not ones from other processes. That's because READ_LOGS can no longer be held by normal SDK apps (it is signatureOrSystem now). On Wednesday, December 19, 2012 7:45:23 PM UTC-5, Nathan wrote: There was also talk of making a more user friendly way in settings to do this. The hidden Developer Options on a 4.2+ device has a Take bug report option that emits the same report as does the magic key combination. Is there any procedure that will work on, say, Razr Maxx HD, or ASUS Transformer TF700T. Other than POWER + VOLUME UP + VOLUME DOWN, I am unaware of a way to collect the bug report on 4.1 without a copy of the Android SDK installed. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 4.4 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Send bug report from 4.1
Other than POWER + VOLUME UP + VOLUME DOWN, I am unaware of a way to collect the bug report on 4.1 without a copy of the Android SDK installed. If anyone from Google is reading: for the love of God, please put a toast or audible notation or similar in when this key combination is registered. Since it takes about 10 seconds to do anything you have no idea if you've hit the right key combination or not. You've just made debugging super-hard by reducing the system logging access, please at least make the workarounds usable. Trying to get the users to use this key combo or attempt to unlock the secret developer options (after you've found out if they're on 4.2 or not) is just embarrassing. Pent -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
