G1 treated as disk... All the time

by Alvin Yates » Tue, 04 Nov 2008 02:37:18 GMT


Sponsored Links
 I downloaded the driver for the G1 and attached it to my PC so I could
resume development after my MacBook decided off was better than on.
Was test driving the phone via USB and attached it as a storage
device.

The problem now is, Windows won't stop treating the phone as a USB
drive, even when the USB option is unchecked (It treats it as having
no capacity).

Has anyone else run into this problem?  Is there a way to fix it?
--~--~---------~--~----~------------~-------~--~----~



G1 treated as disk... All the time

by ecompositor » Tue, 04 Nov 2008 03:01:07 GMT


 What happends when you type in adb devices



--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


G1 treated as disk... All the time

by Alvin Yates » Tue, 04 Nov 2008 03:17:40 GMT


 Nothing.  ADB doesn't detect the phone as being attached.  Does
Windows typically let ADB respond while using it as a disk drive?  If
so, then I probably have something wrong with the drivers, and that's
probably not going to resolve nicely.




--~--~---------~--~----~------------~-------~--~----~



G1 treated as disk... All the time

by Stephen Chambers » Tue, 04 Nov 2008 11:34:11 GMT


 I don't where you are supposed to find this out, but this URL saved me. Your
set up is not complete.
 http://androidcommunity.com/forums/f4/how-to-install-apps-using-adb-4482/ 

Steve







--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. HTC Wildfire Home Screen Widgets issue?

Hello, multiple users reported that my widget does not surviver
restart of Htc Wildfire. They said (I have not access to wildfire to
test it) that widget works fine but after phone turn off and then on
it does not appear (it says loading only).

On my phones ADP1 and Galaxy S it work with no problem.

Does anybody met the same issue with home screen widgets?

Thank
Tom

-- 

2. Method called after release()

Hi, I'm getting this error ( in the end of this post)... which I guess
I understand it's because I'm calling something after releasing it..
but I can't find a wy to work it around... Here is the method:

public void surfaceDestroyed(SurfaceHolder holder) {
                mPreviewRunning = false;
                mCamera.stopPreview();
                mCamera.release();
        }

I've tried all combinations.. I've tried:
mCamera.setPreviewCallback(null);
This class, where the surfaceview is implemented can be accessed by 2
different classes.. one that doesnt implement surfaceview and other
that does.. the error just shows me when I go from the activity that
uses the camera to the activity that also uses camera.. I don't know
what else to do.. I've google it and can't find any answer. any
suggestion?


09-22 19:55:57.475: ERROR/AndroidRuntime(900):     Uncaught handler:
thread main exiting due to uncaught exception
09-22 19:55:57.605: ERROR/AndroidRuntime(900):
java.lang.RuntimeException: Method called after release()
09-22 19:55:57.605: ERROR/AndroidRuntime(900):     at
android.hardware.Camera.stopPreview(Native Method)
09-22 19:55:57.605: ERROR/AndroidRuntime(900):     at
com.pedroteixeira.thennnow.cameraView.surfaceDestroyed(cameraView.java:
184)
09-22 19:55:57.605: ERROR/AndroidRuntime(900):     at
android.view.SurfaceView.reportSurfaceDestroyed(SurfaceView.java:426)
09-22 19:55:57.605: ERROR/AndroidRuntime(900):     at
android.view.SurfaceView.updateWindow(SurfaceView.java:351)
09-22 19:55:57.605: ERROR/AndroidRuntime(900):     at
android.view.SurfaceView.onWindowVisibilityChanged(SurfaceView.java:
182)

-- 

3. How to make children of TableRow selectable

4. AutoCompleteTextView performance

5. How to access system MP3 / AAC decoder?

6. Content Delivery (Ringtones, Wallpaper, Games, etc)

7. App working but GoogleMap not coming (proxy settings working)