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
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
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
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
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
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 rich.frie...@gmail.com wrote:
Yeah I am starting to think it's
You could alway option your present location first, then destination
to.
On Aug 12, 12:21 am, Nick Risaro nris...@gmail.com 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 spicaneb...@gmail.com wrote:
I am
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 spicaneb...@gmail.com 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
Can't you incorporate Google maps to your app for judging your location ?
On Fri, Aug 12, 2011 at 12:40 AM, Spica spicaneb...@gmail.com 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 nris...@gmail.com wrote:
That's so
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 djse.internatio...@gmail.com wrote:
You could mange that fix by having the app locate you (the user)
first, then input destination
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
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 spicaneb...@gmail.com wrote:
Here is the log and at this point i do not have any idea what it
means;
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 mmur...@commonsware.com wrote:
None of that shows a crash. A Force Close dialog will have a Java
stack trace
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 spicaneb...@gmail.com wrote:
I grabbed
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 sumed...@gmail.com wrote:
The log is generally what you what you seen in logcat console while
debugging. But here
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,
This my first android application so i am not sure what log i need to
attach...
On Aug 12, 12:21 am, Nick Risaro nris...@gmail.com 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 spicaneb...@gmail.com
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
18 matches
Mail list logo