USB driver not working on Windows 7 64 bits

by Salva Maine » Thu, 23 Sep 2010 23:09:49 GMT


Sponsored Links
 For some reason my windows 7 64 don't recognize the driver r3. Does
anybady have this problem? Found any solution?

--



USB driver not working on Windows 7 64 bits

by Kostya Vasilyev » Fri, 24 Sep 2010 04:40:52 GMT


 This depends on the phone - unfortunately, adb drivers are device specific.
You could try downloading the manufacturer's drivers, or tweak the PnP
device information in the driver's .inf file. There is also some kind of
magic having to do with installing a "composite" device.

All of this came up before, use The Search, Luke :)

--
Kostya Vasilyev --  http://kmansoft.wordpress.com 

23.09.2010 19:10  "Salva Maine" <salvama...@gmail.com> :

For some reason my windows 7 64 don't recognize the driver r3. Does
anybady have this problem? Found any solution?

--


Sponsored Links


USB driver not working on Windows 7 64 bits

by Morrison Chang » Sat, 25 Sep 2010 10:09:47 GMT


 I'm running win7 x64 without problems.
What device are you trying to connect to?
A number of the newer HTC devices need their driver or a hack.




--



USB driver not working on Windows 7 64 bits

by Bob » Tue, 28 Sep 2010 06:20:55 GMT


 I'm having trouble too.
I'm using Windows 7 64 bit and have an LG GT540.
I've written my app, and it works on the virtual phone, now I want to
test it on my phone, but I can't get windows to connect to it.

--



USB driver not working on Windows 7 64 bits

by FrankG » Tue, 28 Sep 2010 19:20:25 GMT


 


Hello Bob,

you need a special USB driver from LG as the GT 540 comes with a
composite usb interface.

You didn't say whether you already installed the PC Sync App from LG
and before the driver from LG ?

 http://tinyurl.com/2do4po5 

Good luck !
   Frank

--



Other Threads

1. Local communication with a service from another APK that runs in the same process

In case it would help, here is the relevant code:

The two classes (LocalServiceBinder and LocalService) used to bind to
the service and obtain a reference to it:

-----------------------------------------------------------------
package localservice;

import android.os.Binder;

public abstract class LocalServiceBinder extends Binder{
        public abstract LocalService getLocalService();
}

-----------------------------------------------------------------

package localservice;

public interface LocalService{
        public String getPid();
}

-----------------------------------------------------------------

A sample activity in APK #1 that binds with the service and also
implements the ServiceConnection interface
-----------------------------------------------------------------

package kanonov.t1;

import localservice.LocalService;
import localservice.LocalServiceBinder;
import android.app.Activity;
import android.content.ComponentName;
import android.content.Intent;
import android.content.ServiceConnection;
import android.os.Bundle;
import android.os.IBinder;
import android.util.Log;

public class T1 extends Activity implements ServiceConnection{
        public static final String TAG = "Test";

        @Override
        public void onCreate(Bundle savedInstanceState){
                super.onCreate(savedInstanceState);
                setContentView(R.layout.main);

                Log.d(TAG, "T1 onCreate");
                bindService(new Intent("kanonov.localservice"), this,
BIND_AUTO_CREATE);
        }

        @Override
        public void onServiceConnected(ComponentName name, IBinder service){
                Log.d(TAG, "T1 onServiceConnected " + 
android.os.Process.myPid());
                if (service == null){
                        try{
                                LocalServiceBinder lsb = 
(LocalServiceBinder)service;
                                LocalService ls = lsb.getLocalService();
                                Log.i(TAG, "My PID is: " + 
android.os.Process.myPid());
                                Log.i(TAG, "LocalService Process' PID is: " + 
ls.getPid());
                        }catch(Exception e){
                                Log.e(TAG, "Error in connection: " + 
e.getMessage(), e);
                        }
                        unbindService(this);
                }else{
                        Log.e(TAG, "Binder is null!");
                }

        }
        @Override
        public void onServiceDisconnected(ComponentName name){}
}


The actual service in APK #2
-----------------------------------------------------------------
package kanonov.t2;

import localservice.LocalService;
import localservice.LocalServiceBinder;
import android.app.Service;
import android.content.Intent;
import android.util.Log;

public class LS extends Service implements LocalService{
        public static final String TAG = "Test";

        @Override
        public LocalServiceBinder onBind(Intent intent){
                Log.d(TAG, "LocalService onBind " + android.os.Process.myPid());
                return new LocalServiceBinder(){

                        @Override
                        public LocalService getLocalService(){
                                Log.d(TAG, "T2LS getLocalService");
                                return LS.this;
                        }

                };

        }

        @Override
        public String getPid(){
                Log.d(TAG, "LocalService getPid");
                return "" + android.os.Process.myPid();
        }
}


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

2. Central service scheduler

Would it make sense to create a central scheduler for services that
need to run periodically?

There are a lot of application that want to run at periodic intervals,
require network access and need to keep the device awake during their
work. Instead of each app having to use an AlarmManager, a WakeLock
and its own network availability checking / auto-retry, wouldn't it
make sense to provide an API that would do that work?

Also, if you have a lot of apps on your device with background checks,
they run on different schedules and wake the device up more frequently
than if they'd run on a synchronized schedule.

Ideally, I'd imagine this service scheduler to provide the following:
* Application can register and unregister service intents for a
certain schedule.
* Provide schedules an app can register for. These could be constant
such as a frequent schedule (every 10mins) and a less frequent one
(every 60mins), or maybe user configurable.
* Apps can specify a network filter, i.e. only run when connected via
wifi, 3g, 2g...
* Services would signal to the scheduler when they're done, possibly
with an error code such that the scheduler could retry automatically
out of the ordinary schedule.
* Provide a UI for users to change schedules, unregister services, etc.
* Define and require permissions for schedules such that users could
see how much "battery drainage" an app is causing.

I really think this would be quite useful for developers and users
likewise. This central service scheduler could be part of the
platform/SDK or it could be a user APK, much like some of the OI
components already available.

Any thoughts?

Christoph

P.S.: Not sure whether android-developers is the right mailinglist,
but it does not quite fit into any of the others, either.

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

3. Need help in writing unit test for parcelable object

4. PhoneStateListener state transitions

5. Bring up active dialer or send dial tone

6. Weekly Nascar Pocket Guide

7. If i use the internet in my app, how long does it stay connected?