Android SDK v1.1 - changes / bug fixes or lack of

by thesquib » Tue, 10 Feb 2009 05:20:05 GMT


Sponsored Links
 This thread is for reporting changes and bug fixes (or the lack of
fixes) to the new 1.1 SDK.

So far I have found:

Bug: android.graphics.Bitmap.getPixels and
android.graphics.Bitmap.getPixel  still do not correctly function
(information is lost).

Feature missing: Playing sounds from input streams is not available.
This is very useful when playing from a single resource that contains
multiple sounds.

Documentation is still a bit thin. It is very hard to know how to
write an optimised application, especially when using the 2D graphics
API's which have very little explained.



Thanks,
Sam
--~--~---------~--~----~------------~-------~--~----~



Android SDK v1.1 - changes / bug fixes or lack of

by Mark Murphy » Tue, 10 Feb 2009 05:25:15 GMT


 


What "new 1.1 SDK"?

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com 
_The Busy Coder's Guide to Android Development_ Version 2.0 Published!

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


Sponsored Links


Android SDK v1.1 - changes / bug fixes or lack of

by Mark Murphy » Tue, 10 Feb 2009 05:30:36 GMT


 




Never mind...

 http://developer.android.com/sdk/1.1_r1/index.html 

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com 
_The Busy Coder's Guide to Android Development_ Version 2.0 Published!

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



Android SDK v1.1 - changes / bug fixes or lack of

by Justin (Google Employee) » Tue, 10 Feb 2009 06:37:00 GMT


 If you find *new* bugs the right thing to do is file them,
 http://source.android.com/report-bugs . Remember to search for 
existing bugs that match your issues before filing new ones.

To echo Dianne, 1.1 was not a major platform release and many of the
bugs in 1.0 will still exist in 1.1.

Cheers,
Justin
Android Team @ Google




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



Android SDK v1.1 - changes / bug fixes or lack of

by thesquib » Tue, 10 Feb 2009 06:58:17 GMT


 Right! I missed that, thank you for the clarification. The bug
mentioned has been raised source.android.com.

On Feb 10, 11:36am, "Justin (Google Employee)" <j...@google.com>




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



Other Threads

1. to get/generate nonce. error in random, getBytes Options

The author meant to say 'nextBytes(byte[])' instead of
'getBytes(byte[])'

It's called nextBytes instead of getBytes because you can call it
repeatedly, getting additional random bytes each time.








-- 

2. android rfkill problems - again

Android when it wants to turn BT on, write's 1 onto the rfkill entry (which
has type bluetooth),
and up until now this is the reason we had wl127x_rfkill.c on OMAP or
board-*-rfkill.c on MSM.

However a hci_register_dev from 2.6.32 also creates and rfkill entry by the
same type - bluetooth.

Now both or any of these rfkill entries may be used, unfortunately we have
to manually change the permissions of either of them.
This can be put in the init.rc if BT driver exists in kernel by default, but
by this we cannot have it as a module and hotplug it into the kernel as and
when required.

So my question is - why is this turning on of rfkill entry so very
desperately required in android.
As Dmitry Torokhov quoted "Well, this just indicates that this portion of
Android code is sploppy"
-- 
--Pavan Savoy

-- 
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: 

3. request: Tutor install NDRIVE n link files required

4. Matrix broadband(pejing yopie)

5. update 3 [BajuDroid]

6. again [WTA] Spica vs Huawei & salam kenal

7. Re(1): ayo serbu global teleshop beli spica