[android-developers] Re: Force Close Issue
guys, you were correct. My phone's usb port went bad. I tested my app on my new HTC Aria today and no "Force Close" error coming up. But still i am get that error on Samsung Captivate. Looks like nothing is wrong in my code. Its the hardware or else, i'm not sure. My app is running fine on Aria so at this point i would consider it as resovled :)) Thanks for your support Cheers On Aug 13, 4:46 pm, Spica wrote: > It looks like i will have to buy another android phone... any > suggestion which one is good low cost phone for android development? > Obviously other than Samsung Captivate :)) How about HTC Aria > > On Aug 13, 1:19 pm, rich friedel wrote: > > > > > Yeah I am starting to think it's the port on the mobo... :-/- Hide quoted > > text - > > - Show quoted text - -- 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: Force Close Issue
It looks like i will have to buy another android phone... any suggestion which one is good low cost phone for android development? Obviously other than Samsung Captivate :)) How about HTC Aria On Aug 13, 1:19 pm, rich friedel wrote: > Yeah I am starting to think it's the port on the mobo... :-/ -- 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: Force Close Issue
Yeah I am starting to think it's the port on the mobo... :-/ -- 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: Force Close Issue
Sounds like a malfunctioning USB cable or hub... 13.08.2011 20:47, rich friedel пишет: I can't speak for Samsung but I have had that issue with the Motorola drivers on Win7. It sometimes says that I should use USB 2.0 as well. (which I am) To correct it I simply unplug it and plug it back it and it will usually take the first or second time. Hope that helps -- Kostya Vasilyev -- 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: Force Close Issue
I can't speak for Samsung but I have had that issue with the Motorola drivers on Win7. It sometimes says that I should use USB 2.0 as well. (which I am) To correct it I simply unplug it and plug it back it and it will usually take the first or second time. Hope that helps -- 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: Force Close Issue
Guys, I am still trying to get logs using logcat by connecting my device to my laptop. But, suddenly i started running into another issue. My device stopped connecting to my laptop. It was connecting fine before but now i am getting two type of errors; either a- Device driver was not successfuly installed or b- USB device not recognized I have tried almost everything available in blogs but no fate. Any idea why is it started happening suddenly and how i can make it work again? I am using Samsung Captivate On Aug 12, 7:25 pm, Indicator Veritatis wrote: > your log extract looks like the same kind of log produced by logcat. > Well and good. But there is no evidence of a "force close" in there. > When you capture the log for that, you will see a Java Exception in > the log. Exceptions produce stack traces. That is what we need to see. > > On Aug 12, 9:18 am, Spica wrote: > > > > > I grabbed this log using app "Log Report". Could you suggest how i can > > capture log so it grabs the Java stack trace? > > Or suggest better app to capture log. > > > On Aug 12, 11:31 am, Mark Murphy wrote:> None of > > that shows a crash. A "Force Close" dialog will have a Java > > > stack trace associated with it. > > > > On Fri, Aug 12, 2011 at 11:29 AM, Spica wrote: > > > > Here is the log and at this point i do not have any idea what it > > > > means; > > > > == > > > > CRASH LOG: > > > > 0.00) > > > > 08-12 10:54:08.908 D/gps_BRCM( 2479): on_location_cb() : location is > > > > missed. flags is 0! > > > > 08-12 10:54:08.908 D/GpsLocationProvider( 2479): send an intent to > > > > notify that the GPS is receiving fixes > > > > 08-12 10:54:08.943 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > > > used_in_fix_mask : 0x) > > > > 08-12 10:54:08.943 D/GpsLocationProvider( 2479): send an intent to > > > > notify that the GPS is no longer receiving fixes > > > > 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : > > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > > accuracy(100.00) > > > > 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : location is > > > > missed. flags is 0! > > > > 08-12 10:54:09.904 D/GpsLocationProvider( 2479): send an intent to > > > > notify that the GPS is receiving fixes > > > > 08-12 10:54:09.979 I/wpa_supplicant( 2555): CTRL-EVENT-NO-CONNECTION > > > > 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [ SCAN-RESULTS ] > > > > 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [CTRL-EVENT-NO- > > > > CONNECTION] > > > > 08-12 10:54:10.010 I/NetworkStatusReceiver( 3662): action: > > > > android.net.wifi.SCAN_RESULTS > > > > 08-12 10:54:10.022 I/NetworkStatusReceiver( 3662): action: > > > > android.net.wifi.SHOW_AP_LIST_DIALOG > > > > 08-12 10:54:10.022 E/WifiManager( 3662): showApDialog > > > > 08-12 10:54:10.025 I/WifiService( 2479): > > > > isShowingAccessPointListDialog():false > > > > 08-12 10:54:10.025 I/WifiService( 2479): > > > > setShowAccessPointListDialog():false > > > > 08-12 10:54:10.041 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > > > used_in_fix_mask : 0x) > > > > 08-12 10:54:10.041 D/GpsLocationProvider( 2479): send an intent to > > > > notify that the GPS is no longer receiving fixes > > > > 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : > > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > > accuracy(100.00) > > > > 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : location is > > > > missed. flags is 0! > > > > 08-12 10:54:10.900 D/GpsLocationProvider( 2479): send an intent to > > > > notify that the GPS is receiving fixes > > > > 08-12 10:54:10.939 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > > > used_in_fix_mask : 0x) > > > > 08-12 10:54:10.939 D/GpsLocationProvider( 2479): send an intent to > > > > notify that the GPS is no longer receiving fixes > > > > 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : > > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > > accuracy(1500.00) > > > > 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : location is > > > > missed. flags is 0! > > > > 08-12 10:54:11.893 D/GpsLocationProvider( 2479): send an intent to > > > > notify that the GPS is receiving fixes > > > > 08-12 10:54:11.908 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > > > used_in_fix_mask : 0x) > > > > 08-12 10:54:11.908 D/GpsLocationProvider( 2479): send an intent to > > > > notify that the GPS is no longer receiving fixes > > > > 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : > > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > > accuracy(1500.00) > > > > 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : location is > > > > missed. flags is 0! > > > > 08-12 10:54:12.908 D/GpsLocationProvider( 2479): send an intent to > > > > notify that the GPS is receiving fixes > > > > 08-12 10:54:12.994 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > > > used_in
[android-developers] Re: Force Close Issue
your log extract looks like the same kind of log produced by logcat. Well and good. But there is no evidence of a "force close" in there. When you capture the log for that, you will see a Java Exception in the log. Exceptions produce stack traces. That is what we need to see. On Aug 12, 9:18 am, Spica wrote: > I grabbed this log using app "Log Report". Could you suggest how i can > capture log so it grabs the Java stack trace? > Or suggest better app to capture log. > > On Aug 12, 11:31 am, Mark Murphy wrote:> None of > that shows a crash. A "Force Close" dialog will have a Java > > stack trace associated with it. > > > On Fri, Aug 12, 2011 at 11:29 AM, Spica wrote: > > > Here is the log and at this point i do not have any idea what it > > > means; > > > == > > > CRASH LOG: > > > 0.00) > > > 08-12 10:54:08.908 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:08.908 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:08.943 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:08.943 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > accuracy(100.00) > > > 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:09.904 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:09.979 I/wpa_supplicant( 2555): CTRL-EVENT-NO-CONNECTION > > > 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [ SCAN-RESULTS ] > > > 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [CTRL-EVENT-NO- > > > CONNECTION] > > > 08-12 10:54:10.010 I/NetworkStatusReceiver( 3662): action: > > > android.net.wifi.SCAN_RESULTS > > > 08-12 10:54:10.022 I/NetworkStatusReceiver( 3662): action: > > > android.net.wifi.SHOW_AP_LIST_DIALOG > > > 08-12 10:54:10.022 E/WifiManager( 3662): showApDialog > > > 08-12 10:54:10.025 I/WifiService( 2479): > > > isShowingAccessPointListDialog():false > > > 08-12 10:54:10.025 I/WifiService( 2479): > > > setShowAccessPointListDialog():false > > > 08-12 10:54:10.041 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:10.041 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > accuracy(100.00) > > > 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:10.900 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:10.939 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:10.939 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > accuracy(1500.00) > > > 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:11.893 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:11.908 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:11.908 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > accuracy(1500.00) > > > 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:12.908 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:12.994 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:12.994 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08-12 10:54:13.908 D/gps_BRCM( 2479): on_location_cb() : > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > accuracy(1500.00) > > > 08-12 10:54:13.908 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:13.912 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:13.951 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:13.951 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS
[android-developers] Re: Force Close Issue
And why can't he debug it while moving? He can run the SDK on a laptop and carry it with him connected to the phone while he moves both together. On Aug 11, 10:13 pm, Sumedh Jiwane wrote: > The log is generally what you what you seen in logcat console while > debugging. But here is the catch since it happens when you are moving and > you can't debug at that time, you can you Logger application available from > market. It requires SD/micro SD card to save the logs. You can also choose > to email if you have synched the account.On Fri, Aug 12, 2011 at 10:10 AM, > Spica wrote: > > This my first android application so i am not sure what log i need to > > attach... > > > On Aug 12, 12:21 am, Nick Risaro wrote: > > > That's so sad :( > > > > Maybe if you attach some logs we can help you and stop being sad. > > > > On Fri, Aug 12, 2011 at 1:15 AM, Spica wrote: > > > > I am developing location based application which uses phone's gps. It > > > > works fine on my android device when i am not moving but as soon as i > > > > start moving my application either freezes or error out with option of > > > > "Force close". This application is also consuming web service to send > > > > location to the server. > > > > > -- > > > > 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 -- 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: Force Close Issue
Run a "logcat" after you force close while you have the device plugged in (or hooked up in some other way to your debug bridge.) Logcat can give you some good helpful hints, you can read a bit more about it. Kris On Fri, Aug 12, 2011 at 12:18 PM, Spica wrote: > I grabbed this log using app "Log Report". Could you suggest how i can > capture log so it grabs the Java stack trace? > Or suggest better app to capture log. > > On Aug 12, 11:31 am, Mark Murphy wrote: > > None of that shows a crash. A "Force Close" dialog will have a Java > > stack trace associated with it. > > > > > > > > On Fri, Aug 12, 2011 at 11:29 AM, Spica wrote: > > > Here is the log and at this point i do not have any idea what it > > > means; > > > == > > > CRASH LOG: > > > 0.00) > > > 08-12 10:54:08.908 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:08.908 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:08.943 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:08.943 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > accuracy(100.00) > > > 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:09.904 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:09.979 I/wpa_supplicant( 2555): CTRL-EVENT-NO-CONNECTION > > > 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [ SCAN-RESULTS ] > > > 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [CTRL-EVENT-NO- > > > CONNECTION] > > > 08-12 10:54:10.010 I/NetworkStatusReceiver( 3662): action: > > > android.net.wifi.SCAN_RESULTS > > > 08-12 10:54:10.022 I/NetworkStatusReceiver( 3662): action: > > > android.net.wifi.SHOW_AP_LIST_DIALOG > > > 08-12 10:54:10.022 E/WifiManager( 3662): showApDialog > > > 08-12 10:54:10.025 I/WifiService( 2479): > > > isShowingAccessPointListDialog():false > > > 08-12 10:54:10.025 I/WifiService( 2479): > > > setShowAccessPointListDialog():false > > > 08-12 10:54:10.041 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:10.041 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > accuracy(100.00) > > > 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:10.900 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:10.939 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:10.939 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > accuracy(1500.00) > > > 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:11.893 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:11.908 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:11.908 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > accuracy(1500.00) > > > 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:12.908 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:12.994 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:12.994 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08-12 10:54:13.908 D/gps_BRCM( 2479): on_location_cb() : > > > lat(40.734275), lon(-73.596664), flags(0x000c), > > > accuracy(1500.00) > > > 08-12 10:54:13.908 D/gps_BRCM( 2479): on_location_cb() : location is > > > missed. flags is 0! > > > 08-12 10:54:13.912 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is receiving fixes > > > 08-12 10:54:13.951 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > > used_in_fix_mask : 0x) > > > 08-12 10:54:13.951 D/GpsLocationProvider( 2479): send an intent to > > > notify that the GPS is no longer receiving fixes > > > 08
[android-developers] Re: Force Close Issue
I grabbed this log using app "Log Report". Could you suggest how i can capture log so it grabs the Java stack trace? Or suggest better app to capture log. On Aug 12, 11:31 am, Mark Murphy wrote: > None of that shows a crash. A "Force Close" dialog will have a Java > stack trace associated with it. > > > > On Fri, Aug 12, 2011 at 11:29 AM, Spica wrote: > > Here is the log and at this point i do not have any idea what it > > means; > > == > > CRASH LOG: > > 0.00) > > 08-12 10:54:08.908 D/gps_BRCM( 2479): on_location_cb() : location is > > missed. flags is 0! > > 08-12 10:54:08.908 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is receiving fixes > > 08-12 10:54:08.943 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > used_in_fix_mask : 0x) > > 08-12 10:54:08.943 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is no longer receiving fixes > > 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : > > lat(40.734275), lon(-73.596664), flags(0x000c), > > accuracy(100.00) > > 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : location is > > missed. flags is 0! > > 08-12 10:54:09.904 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is receiving fixes > > 08-12 10:54:09.979 I/wpa_supplicant( 2555): CTRL-EVENT-NO-CONNECTION > > 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [ SCAN-RESULTS ] > > 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [CTRL-EVENT-NO- > > CONNECTION] > > 08-12 10:54:10.010 I/NetworkStatusReceiver( 3662): action: > > android.net.wifi.SCAN_RESULTS > > 08-12 10:54:10.022 I/NetworkStatusReceiver( 3662): action: > > android.net.wifi.SHOW_AP_LIST_DIALOG > > 08-12 10:54:10.022 E/WifiManager( 3662): showApDialog > > 08-12 10:54:10.025 I/WifiService( 2479): > > isShowingAccessPointListDialog():false > > 08-12 10:54:10.025 I/WifiService( 2479): > > setShowAccessPointListDialog():false > > 08-12 10:54:10.041 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > used_in_fix_mask : 0x) > > 08-12 10:54:10.041 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is no longer receiving fixes > > 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : > > lat(40.734275), lon(-73.596664), flags(0x000c), > > accuracy(100.00) > > 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : location is > > missed. flags is 0! > > 08-12 10:54:10.900 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is receiving fixes > > 08-12 10:54:10.939 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > used_in_fix_mask : 0x) > > 08-12 10:54:10.939 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is no longer receiving fixes > > 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : > > lat(40.734275), lon(-73.596664), flags(0x000c), > > accuracy(1500.00) > > 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : location is > > missed. flags is 0! > > 08-12 10:54:11.893 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is receiving fixes > > 08-12 10:54:11.908 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > > used_in_fix_mask : 0x) > > 08-12 10:54:11.908 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is no longer receiving fixes > > 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : > > lat(40.734275), lon(-73.596664), flags(0x000c), > > accuracy(1500.00) > > 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : location is > > missed. flags is 0! > > 08-12 10:54:12.908 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is receiving fixes > > 08-12 10:54:12.994 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > used_in_fix_mask : 0x) > > 08-12 10:54:12.994 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is no longer receiving fixes > > 08-12 10:54:13.908 D/gps_BRCM( 2479): on_location_cb() : > > lat(40.734275), lon(-73.596664), flags(0x000c), > > accuracy(1500.00) > > 08-12 10:54:13.908 D/gps_BRCM( 2479): on_location_cb() : location is > > missed. flags is 0! > > 08-12 10:54:13.912 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is receiving fixes > > 08-12 10:54:13.951 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > > used_in_fix_mask : 0x) > > 08-12 10:54:13.951 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is no longer receiving fixes > > 08-12 10:54:14.936 I/GpsLocationProvider( 2479): requestRefLocation: > > gsm_cell = [11940,156182206] > > 08-12 10:54:14.940 I/GpsLocationProvider( 2479): requestRefLocation: > > mcc = 310 mnc = 410 > > 08-12 10:54:14.943 D/gps_BRCM( 2479): on_location_cb() : > > lat(40.733659), lon(-73.597838), flags(0x001f), > > accuracy(100.00) > > 08-12 10:54:14.947 D/GpsLocationProvider( 2479): send an intent to > > notify that the GPS is receiving fix
Re: [android-developers] Re: Force Close Issue
None of that shows a crash. A "Force Close" dialog will have a Java stack trace associated with it. On Fri, Aug 12, 2011 at 11:29 AM, Spica wrote: > Here is the log and at this point i do not have any idea what it > means; > == > CRASH LOG: > 0.00) > 08-12 10:54:08.908 D/gps_BRCM( 2479): on_location_cb() : location is > missed. flags is 0! > 08-12 10:54:08.908 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is receiving fixes > 08-12 10:54:08.943 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > used_in_fix_mask : 0x) > 08-12 10:54:08.943 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is no longer receiving fixes > 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : > lat(40.734275), lon(-73.596664), flags(0x000c), > accuracy(100.00) > 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : location is > missed. flags is 0! > 08-12 10:54:09.904 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is receiving fixes > 08-12 10:54:09.979 I/wpa_supplicant( 2555): CTRL-EVENT-NO-CONNECTION > 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [ SCAN-RESULTS ] > 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [CTRL-EVENT-NO- > CONNECTION] > 08-12 10:54:10.010 I/NetworkStatusReceiver( 3662): action: > android.net.wifi.SCAN_RESULTS > 08-12 10:54:10.022 I/NetworkStatusReceiver( 3662): action: > android.net.wifi.SHOW_AP_LIST_DIALOG > 08-12 10:54:10.022 E/WifiManager( 3662): showApDialog > 08-12 10:54:10.025 I/WifiService( 2479): > isShowingAccessPointListDialog():false > 08-12 10:54:10.025 I/WifiService( 2479): > setShowAccessPointListDialog():false > 08-12 10:54:10.041 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > used_in_fix_mask : 0x) > 08-12 10:54:10.041 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is no longer receiving fixes > 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : > lat(40.734275), lon(-73.596664), flags(0x000c), > accuracy(100.00) > 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : location is > missed. flags is 0! > 08-12 10:54:10.900 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is receiving fixes > 08-12 10:54:10.939 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > used_in_fix_mask : 0x) > 08-12 10:54:10.939 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is no longer receiving fixes > 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : > lat(40.734275), lon(-73.596664), flags(0x000c), > accuracy(1500.00) > 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : location is > missed. flags is 0! > 08-12 10:54:11.893 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is receiving fixes > 08-12 10:54:11.908 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 > used_in_fix_mask : 0x) > 08-12 10:54:11.908 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is no longer receiving fixes > 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : > lat(40.734275), lon(-73.596664), flags(0x000c), > accuracy(1500.00) > 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : location is > missed. flags is 0! > 08-12 10:54:12.908 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is receiving fixes > 08-12 10:54:12.994 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > used_in_fix_mask : 0x) > 08-12 10:54:12.994 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is no longer receiving fixes > 08-12 10:54:13.908 D/gps_BRCM( 2479): on_location_cb() : > lat(40.734275), lon(-73.596664), flags(0x000c), > accuracy(1500.00) > 08-12 10:54:13.908 D/gps_BRCM( 2479): on_location_cb() : location is > missed. flags is 0! > 08-12 10:54:13.912 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is receiving fixes > 08-12 10:54:13.951 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > used_in_fix_mask : 0x) > 08-12 10:54:13.951 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is no longer receiving fixes > 08-12 10:54:14.936 I/GpsLocationProvider( 2479): requestRefLocation: > gsm_cell = [11940,156182206] > 08-12 10:54:14.940 I/GpsLocationProvider( 2479): requestRefLocation: > mcc = 310 mnc = 410 > 08-12 10:54:14.943 D/gps_BRCM( 2479): on_location_cb() : > lat(40.733659), lon(-73.597838), flags(0x001f), > accuracy(100.00) > 08-12 10:54:14.947 D/GpsLocationProvider( 2479): send an intent to > notify that the GPS is receiving fixes > 08-12 10:54:15.022 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 > used_in_fix_mask : 0x50001000) > 08-12 10:54:15.904 I/GpsLocationProvider( 2479): requestRefLocation: > gsm_cell = [11940,156182206] > 08-12 10:54:15.904 I/GpsLocationProvider( 2479): requestRefLocation: > mcc = 310 mnc = 410 > 08-12 10:54:15.912 D/gps_BRCM( 2479): on_location_cb() : > lat(40.733659), lon(-73.5978
[android-developers] Re: Force Close Issue
Here is the log and at this point i do not have any idea what it means; == CRASH LOG: 0.00) 08-12 10:54:08.908 D/gps_BRCM( 2479): on_location_cb() : location is missed. flags is 0! 08-12 10:54:08.908 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is receiving fixes 08-12 10:54:08.943 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 used_in_fix_mask : 0x) 08-12 10:54:08.943 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is no longer receiving fixes 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : lat(40.734275), lon(-73.596664), flags(0x000c), accuracy(100.00) 08-12 10:54:09.900 D/gps_BRCM( 2479): on_location_cb() : location is missed. flags is 0! 08-12 10:54:09.904 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is receiving fixes 08-12 10:54:09.979 I/wpa_supplicant( 2555): CTRL-EVENT-NO-CONNECTION 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [ SCAN-RESULTS ] 08-12 10:54:09.979 I/WifiMonitor( 2479): Event [CTRL-EVENT-NO- CONNECTION] 08-12 10:54:10.010 I/NetworkStatusReceiver( 3662): action: android.net.wifi.SCAN_RESULTS 08-12 10:54:10.022 I/NetworkStatusReceiver( 3662): action: android.net.wifi.SHOW_AP_LIST_DIALOG 08-12 10:54:10.022 E/WifiManager( 3662): showApDialog 08-12 10:54:10.025 I/WifiService( 2479): isShowingAccessPointListDialog():false 08-12 10:54:10.025 I/WifiService( 2479): setShowAccessPointListDialog():false 08-12 10:54:10.041 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 used_in_fix_mask : 0x) 08-12 10:54:10.041 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is no longer receiving fixes 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : lat(40.734275), lon(-73.596664), flags(0x000c), accuracy(100.00) 08-12 10:54:10.900 D/gps_BRCM( 2479): on_location_cb() : location is missed. flags is 0! 08-12 10:54:10.900 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is receiving fixes 08-12 10:54:10.939 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 used_in_fix_mask : 0x) 08-12 10:54:10.939 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is no longer receiving fixes 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : lat(40.734275), lon(-73.596664), flags(0x000c), accuracy(1500.00) 08-12 10:54:11.893 D/gps_BRCM( 2479): on_location_cb() : location is missed. flags is 0! 08-12 10:54:11.893 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is receiving fixes 08-12 10:54:11.908 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 8 used_in_fix_mask : 0x) 08-12 10:54:11.908 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is no longer receiving fixes 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : lat(40.734275), lon(-73.596664), flags(0x000c), accuracy(1500.00) 08-12 10:54:12.908 D/gps_BRCM( 2479): on_location_cb() : location is missed. flags is 0! 08-12 10:54:12.908 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is receiving fixes 08-12 10:54:12.994 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 used_in_fix_mask : 0x) 08-12 10:54:12.994 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is no longer receiving fixes 08-12 10:54:13.908 D/gps_BRCM( 2479): on_location_cb() : lat(40.734275), lon(-73.596664), flags(0x000c), accuracy(1500.00) 08-12 10:54:13.908 D/gps_BRCM( 2479): on_location_cb() : location is missed. flags is 0! 08-12 10:54:13.912 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is receiving fixes 08-12 10:54:13.951 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 used_in_fix_mask : 0x) 08-12 10:54:13.951 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is no longer receiving fixes 08-12 10:54:14.936 I/GpsLocationProvider( 2479): requestRefLocation: gsm_cell = [11940,156182206] 08-12 10:54:14.940 I/GpsLocationProvider( 2479): requestRefLocation: mcc = 310 mnc = 410 08-12 10:54:14.943 D/gps_BRCM( 2479): on_location_cb() : lat(40.733659), lon(-73.597838), flags(0x001f), accuracy(100.00) 08-12 10:54:14.947 D/GpsLocationProvider( 2479): send an intent to notify that the GPS is receiving fixes 08-12 10:54:15.022 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 used_in_fix_mask : 0x50001000) 08-12 10:54:15.904 I/GpsLocationProvider( 2479): requestRefLocation: gsm_cell = [11940,156182206] 08-12 10:54:15.904 I/GpsLocationProvider( 2479): requestRefLocation: mcc = 310 mnc = 410 08-12 10:54:15.912 D/gps_BRCM( 2479): on_location_cb() : lat(40.733659), lon(-73.597838), flags(0x001f), accuracy(100.00) 08-12 10:54:15.916 D/gps_BRCM( 2479): on_satellite_cb(num_svs : 7 used_in_fix_mask : 0x50001000) 08-12 10:54:16.912 I/WifiMonitor( 2479): Event [ SCAN-RESULTS ] 08-12 10:54:16.916 I/wpa_supplicant( 2555): CTRL-EVENT-NO-CONNECTION 08-12 10:54:16.916 I/WifiMonitor( 2479): Event [CTRL-EVENT-NO- CONNECT
[android-developers] Re: Force Close Issue
Guys, functionality is fine but issue is that it crashes when device moves. I will install looger app and upload the log here today. On Aug 12, 12:32 am, Usef Ali wrote: > You could mange that fix by having the app locate you (the user) > first, then input destination 2nd. > > On Aug 12, 12:15 am, Spica wrote: > > > > > I am developing location based application which uses phone's gps. It > > works fine on my android device when i am not moving but as soon as i > > start moving my application either freezes or error out with option of > > "Force close". This application is also consuming web service to send > > location to the server.- Hide quoted text - > > - Show quoted text - -- 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: Force Close Issue
You could mange that fix by having the app locate you (the user) first, then input destination 2nd. On Aug 12, 12:15 am, Spica wrote: > I am developing location based application which uses phone's gps. It > works fine on my android device when i am not moving but as soon as i > start moving my application either freezes or error out with option of > "Force close". This application is also consuming web service to send > location to the server. -- 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: Force Close Issue
Can't you incorporate Google maps to your app for judging your location ? On Fri, Aug 12, 2011 at 12:40 AM, Spica wrote: > This my first android application so i am not sure what log i need to > attach... > > On Aug 12, 12:21 am, Nick Risaro wrote: > > That's so sad :( > > > > Maybe if you attach some logs we can help you and stop being sad. > > > > > > > > > > > > > > > > On Fri, Aug 12, 2011 at 1:15 AM, Spica wrote: > > > I am developing location based application which uses phone's gps. It > > > works fine on my android device when i am not moving but as soon as i > > > start moving my application either freezes or error out with option of > > > "Force close". This application is also consuming web service to send > > > location to the server. > > > > > -- > > > 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 -- -- 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: Force Close Issue
You could alway option your present location first, then destination to. On Aug 12, 12:21 am, Nick Risaro wrote: > That's so sad :( > > Maybe if you attach some logs we can help you and stop being sad. > > > > On Fri, Aug 12, 2011 at 1:15 AM, Spica wrote: > > I am developing location based application which uses phone's gps. It > > works fine on my android device when i am not moving but as soon as i > > start moving my application either freezes or error out with option of > > "Force close". This application is also consuming web service to send > > location to the server. > > > -- > > 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- Hide quoted text - > > - Show quoted text - -- 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: Force Close Issue
The log is generally what you what you seen in logcat console while debugging. But here is the catch since it happens when you are moving and you can't debug at that time, you can you Logger application available from market. It requires SD/micro SD card to save the logs. You can also choose to email if you have synched the account. On Fri, Aug 12, 2011 at 10:10 AM, Spica wrote: > This my first android application so i am not sure what log i need to > attach... > > On Aug 12, 12:21 am, Nick Risaro wrote: > > That's so sad :( > > > > Maybe if you attach some logs we can help you and stop being sad. > > > > > > > > > > > > > > > > On Fri, Aug 12, 2011 at 1:15 AM, Spica wrote: > > > I am developing location based application which uses phone's gps. It > > > works fine on my android device when i am not moving but as soon as i > > > start moving my application either freezes or error out with option of > > > "Force close". This application is also consuming web service to send > > > location to the server. > > > > > -- > > > 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 > -- 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: Force Close Issue
This my first android application so i am not sure what log i need to attach... On Aug 12, 12:21 am, Nick Risaro wrote: > That's so sad :( > > Maybe if you attach some logs we can help you and stop being sad. > > > > > > > > On Fri, Aug 12, 2011 at 1:15 AM, Spica wrote: > > I am developing location based application which uses phone's gps. It > > works fine on my android device when i am not moving but as soon as i > > start moving my application either freezes or error out with option of > > "Force close". This application is also consuming web service to send > > location to the server. > > > -- > > 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
