Picture Application Conflicts? (may be duplicate, third attempt to post)

by dsurround » Mon, 13 Apr 2009 12:08:21 GMT


Sponsored Links
 Any idea why a picture taking application works on some phones and not
on others?  The app was tested with the 1.1 emulator and the 1.0
developer phone.  Some customers reported that they could not find the
resulting pictures using the Picture application after they powered
off the phone and powered it back on to cause a new media scan.
Others find them just fine (in the dcim/camera directory).  Are there
any known conflicts for applications taking pictures?  The only other
thing I can think of is that the developer phone, currently at 1.0,
will function differently at 1.1, however,  the app works on the 1.1
version of the emulator.

Any ideas would be appreciated.

Thanks,

App is ear cam 1.1.


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



Other Threads

1. Get a GPS location :: Need to open "Maps" to get the getLastKnownLocation return a correct value.

Dear all,

I am facing a strange issue and I'm certainly doing something
wrong ...

Here is the scenario :
I open my emulator
I send a geo fix via telnet
I open my app and try to be geolocated... getLastKnownLocation return
null (the first time, or the last position after opening "Map"), my
code is below
I open the "Maps" included app from Google.
I click on menu > My  Location and I am located to the position I sent
via the geo fix
I reopen my app and try to be geolocated ... and it works !

I read the doc and I don't understand what I am doing wrong :

Here is my code :
 public static LocationProvider getLocationProviderToUse(Context act)
{
        LocationManager locMgr = MapUtility.getBuiltLocationManager
(act);

        String name = locMgr.getBestProvider(new Criteria(), true);

        Log.d("MAP", "The best location provider is " + name);

        return locMgr.getProvider(name);
    }

    public static GeoPoint geoLocalize(Activity act)
        throws SecurityException {

        LocationProvider toUse = getLocationProviderToUse(act);

        LocationManager locMgr = MapUtility.getBuiltLocationManager
(act);

// Test but change nothing
// LocationListener listener = new LocationListener() {
//                public void onLocationChanged(Location location) {
//                }
//                public void onProviderDisabled(String provider) {
//                }
//                public void onProviderEnabled(String provider) {
//                }
//                public void onStatusChanged(String provider, int
status,
//                                Bundle extras) {
//                }
//        };

//        locMgr.requestLocationUpdates(toUse.getName(), 0, 0,
listener);

        Location current = locMgr.getLastKnownLocation(toUse.getName
());

        if (current != null) {
            Log.d("MAP", "Location : " + current.getLatitude() + ", "
+ current.getLongitude());
            GeoPoint p = new GeoPoint((int) (current.getLatitude() *
1000000), (int) (current.getLongitude() * 1000000));
            return p;
        } else{
                 Log.e("MAP", "Unable to get the last known position");
            return null;
        }
    }

   public static LocationManager getBuiltLocationManager(Context ctx)
{
        LocationManager mgr = (LocationManager) ctx.getSystemService
(Context.LOCATION_SERVICE);

        return mgr;
    }

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

Coud you please help me in finding what is wrong or sending me a code
snippet ? By reading the Google reference documentation, a single call
to getlastknownlocation might be sufficient.... The best provider
returned is always "gps".

Thanks a lot for your help

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

2. GsmCellLocation.getCid() returns very large numbers.

For the most part, when we call GsmCellLocation.getCid, we get normal
looking numbers:


public synchronized static int GetCellId() {

        GsmCellLocation location = (GsmCellLocation) phoneMan.getCellLocation
();
        return (location.getCid());

}


This method often times returns small numbers under 10000 which seem
in line with other phones:
        -1 (unknown, but expected per the documentation
        3151
        4252
        8251

etc ... all these look fine.  But, recently we're noticing some rather
large numbers come back:

        21267748
        21267756
        27821304

Has anyone seen this?  And, does anyone know what accounts for such a
dramatic change in numbers?  Do the larger numbers contain other bits
about the tower that I need to extract using bitwise flags?

Thanks

Richard Schilling
Root Wireless

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

3. error executing aapt. Please check aapt is present at .......eclipse

4. pricing model on a service based android application/game?

5. Gallery pain

6. Touch screen slowdown

7. Problem loading KML in DDMS view of Eclipse