Android 2.1 backward Compatability? Urgent Question

by Vassilios Kirellous » Sat, 23 Jan 2010 08:31:19 GMT


Sponsored Links
 Hi,

My app is on the ANdroid Market. I built it on version 1.6 Android.

Today, I just received a comment from someone who said he liked the icon,
but the app doesn't work on Android 2.1

Is Android 2.1. OS backward compatible with Android 1.6 Apps?

What do I need to do to make my app forward compliant? This is tricky,
because it would mean creating an app (through refactoring) for each Android
Release.

Has anyone actually played around with the Nexus One? I heard its not
selling at all, so is it really worth doing any work on it for a few people
who would probably uninstall it anyway??

Thanks for any advice,
Vaz

--



Android 2.1 backward Compatability? Urgent Question

by Greg Donald » Sat, 23 Jan 2010 08:39:43 GMT


 


2.1 is still less than 1% for my apps.  It's climbing, but very slowly.

If you can possibly add a webview to your app, you can get all sorts
of Android version info about your users via Google Analytics.


-- 
Greg Donald
destiney.com | gregdonald.com

--


Sponsored Links


Android 2.1 backward Compatability? Urgent Question

by Vassilio » Sat, 23 Jan 2010 09:46:54 GMT


 Thanks

But what do I need to do to make sure my app works on android 2.1?

Sent from my iPhone




On Fri, Jan 22, 2010 at 6:30 PM, Vassilios Kirellous <vassi...@gmail.com
Has anyone actually played around with the Nexus One? I heard its not selling at all, so is it really worth doing any work on it for a few people who would probably uninstall it anyway?? Thanks for any advice,
2.1 is still less than 1% for my apps. It's climbing, but very slowly. If you can possibly add a webview to your app, you can get all sorts of Android version info about your users via Google Analytics. -- Greg Donald destiney.com | gregdonald.com --



Android 2.1 backward Compatability? Urgent Question

by Dianne Hackborn » Sat, 23 Jan 2010 10:02:38 GMT


 Newer Android versions are intended to be backwards compatible with older
ones (I won't say always, because bugs happen, but that is the intention).

Have you tried running your app under 2.1 in the emulator?

2.1 is not very different from 2.0.1 (currently on Droid), so if you work on
2.0.1 I think your problem is most likely something specific to the Nexus
One (how the camera works, etc) or a result of using private APIs.






>>



Android 2.1 backward Compatability? Urgent Question

by Jonas Petersson » Sat, 23 Jan 2010 17:35:49 GMT


 

Newer Android versions are intended to be backwards compatible with older ones (I won't say always, because bugs happen, but that is the intention). Have you tried running your app under 2.1 in the emulator? 2.1 is not very different from 2.0.1 (currently on Droid), so if you work on 2.0.1 I think your problem is most likely something specific to the Nexus One (how the camera works, etc) or a result of using private APIs.
In general I would tend to agree that backwards compatibility has been pretty good. This one appears to be the only significant problem I've found in 2.1 compared to 2.0.1: http://code.google.com/p/android/issues/detail?id=6191 If anyone has an idea for a workaround, please elaborate (see comment #2). Best / Jonas
On Fri, Jan 22, 2010 at 5:45 PM, Vassilio <vassi...@gmail.com Thanks But what do I need to do to make sure my app works on android 2.1? Sent from my iPhone On 23 Jan 2010, at 00:39, Greg Donald <gdon...@gmail.com On Fri, Jan 22, 2010 at 6:30 PM, Vassilios Kirellous Has anyone actually played around with the Nexus One? I heard its not selling at all, so is it really worth doing any work on it for a few people who would probably uninstall it anyway?? Thanks for any advice, 2.1 is still less than 1% for my apps. It's climbing, but very slowly. If you can possibly add a webview to your app, you can get all sorts of Android version info about your users via Google Analytics. -- Greg Donald destiney.com < http://destiney.com > | gregdonald.com < http://gregdonald.com > --



Android 2.1 backward Compatability? Urgent Question

by Romain Guy » Sun, 24 Jan 2010 11:24:37 GMT


 The bug reported below was fixed the day it was reported to us. I took
care of it personally. Android is unfortunately a *very* complex piece
of software (several millions of lines of code) and despite our
extensive testing and dogfooding, problems like this might occur in
new releases. We are very sorry about this.








>>>    --



Android 2.1 backward Compatability? Urgent Question

by Jonas Petersson » Sun, 24 Jan 2010 19:39:21 GMT


 

The bug reported below was fixed the day it was reported to us. I took care of it personally.
That is very good to know. Still, it would be very good to know either: a) A rough estimate when to expect 2.1 phones to have this fixed or b) Some kind of workaround (in particular for the seemingly very simple case in comment #2). If (a) is very soon, then (b) is not an issue, but if (a) is more like April or so, then any application using something like the code in comment #2 on a 2.1 device will keep crashing on rotation unless they are rewritten in some way. I assume the 2.1 emulator will stay broken for verification purposes, just like the 2.0 still has the search issues fixed in 2.0.1. Best / Jonas
[...] This one appears to be the only significant problem I've found in 2.1 compared to 2.0.1: http://code.google.com/p/android/issues/detail?id=6191 If anyone has an idea for a workaround, please elaborate (see comment #2).
--



Android 2.1 backward Compatability? Urgent Question

by Juan Delgado » Sun, 24 Jan 2010 19:48:10 GMT


 Hi,


Not that it concerns me too much, but it's been said a billion times
that Google cannnot / will not be responsible for updating specific
phones, that is up to manufacturers. Google can only be accountant for
release dates of Android itself, then it's up to, let's say HTC, to
pick that release, run their tests, apply any modifications (ie Sense
UI) and make the release available to their users.

Basically, there's no coordinated date for any given Android release
to make it to ALL phones available, you just cannot count on that.

J



>



Android 2.1 backward Compatability? Urgent Question

by Jonas Petersson » Sun, 24 Jan 2010 20:21:10 GMT


 

a) A rough estimate when to expect 2.1 phones to have this fixed or
Not that it concerns me too much, but it's been said a billion times that Google cannnot / will not be responsible for updating specific phones, that is up to manufacturers. Google can only be accountant for release dates of Android itself, then it's up to, let's say HTC, to pick that release, run their tests, apply any modifications (ie Sense UI) and make the release available to their users.
Very true in general, but in this particular case, the RELEASED 2.1 phones are pretty much Googles own Nexus One phones and therefore they *DO* have rather good control over updates, right? Or did is miss anything obvious? (I would assume that any prereleased 2.1 phones will have this bug fixed before actual release.) Speaking of updates, when I ask my Milestone to check for system updates I always get an "Unable to connect. The device is unable to connet to the server. Try again later." dialog. I fully understand that there IS no update available, but the message appears to indicate that there is actually not even a server to host any future updates at the moment. Is this normal or should I dig deeper? (I live in Sweden and the phone was bought from Expansys local web show - which is really UK based.) Best / Jonas --



Other Threads

1. Getting 'OutOfMemoryException' while trying to download a 14mb mp3 file from webserver

Hi Friends,

I want to play an mp3 file as soon as my application starts. The mp3 file is
really large in size(approx 14 mb).

So I am trying to download it from a webserver and than I want to store it
on sdcard.

While doing so I am getting OutOfMemoryException. Can anybody please help
me?

My code is as follows:


public MainClass() throws Exception
{

URL u = new URL("http://----------");
URLConnection uc = u.openConnection();
String contentType = uc.getContentType();
int contentLength = uc.getContentLength();

if(contentLength < Integer.MAX_VALUE)
{

}

if (contentType.startsWith("text/") || contentLength == -1)
{
     throw new IOException("This is not a binary file.");
}

InputStream raw = uc.getInputStream();

InputStream in = new BufferedInputStream(raw);


*// Getting OutOfMemoryException here

**byte [] data=new byte[(int)contentLength];*


int bytesRead = 0;

int offset = 0;

while (offset < contentLength)
{

    bytesRead = in.read(data, offset, data.length - offset);
    if (bytesRead == -1)
    break;
    offset += bytesRead;
}

in.close();

/*

if (offset != contentLength)
{
  throw new IOException("Only read " + offset + " bytes; Expected " +
contentLength + "   bytes");
}

*/


// String filename = u.getFile().substring(filename.lastIndexOf('/') + 1);

FileOutputStream out = new FileOutputStream("/sdcard/music.mp3");

out.write(data);

out.flush();

out.close();

}


Mahesh

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

2. How to Win Features and Influence Developers (Was: Future of Android)

Wise and needed words of Wisdom.

- Juan






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

3. Can the manfifest name be different than AndroidManifest.xml

4. Rotating SurfaceView

5. Identifying pictures taken on 'this' device

6. Recording audio stream

7. MediaRecorder docs fix