Is there any doc exist for porting android 1.5 into x86

by GrainWang » Sat, 23 May 2009 12:50:20 GMT


Sponsored Links
 Dear friends:
        I'm a fresh guy on Android system. And have the following
questions:
1.       Is there any stable release that fit x86 net book? I heard
the name upcake but it semed to be a float branch?
2.       Is the sus eee701project in "cupcake" only fit for asus
net books? Or it fit for any x86 based net books?
3.       The latest stable version that fit for x86 is?
4.       The OpenCore's version in "cupcake" now is very old, in
"android-sdk-1.5r1" which is also a stable release, the OpenCore's
version is much newer(V2.02), so I doubt that if there is possibilty
that I put the eee701 project into "android-sdk-1.5r1" and without
mofication it'll work on x86 net books, or should I port V2.02's
version into "cupcake" branch,I completely have no idea which way is
better, as I have little knowledge in eee701 project, and does not
know what this project acturally  do and how to do.
5.       Is any version that fit for x86 and contain OpenCore newer
versions (V2.01 or V2.02)?
6.       Is there any doc exist for port "android-sdk-1.5r1" into x86?

        Thanks in advance!

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

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



Is there any doc exist for porting android 1.5 into x86

by GrainWang » Sat, 23 May 2009 12:50:27 GMT


 Dear friends:
        I'm a fresh guy on Android system. And have the following
questions:
1.       Is there any stable release that fit x86 net book? I heard
the name upcake but it semed to be a float branch?
2.       Is the sus eee701project in "cupcake" only fit for
asus
net books? Or it fit for any x86 based net books?
3.       The latest stable version that fit for x86 is?
4.       The OpenCore's version in "cupcake" now is very old, in
"android-sdk-1.5r1" which is also a stable release, the OpenCore's
version is much newer(V2.02), so I doubt that if there is possibilty
that I put the eee701 project into "android-sdk-1.5r1" and without
mofication it'll work on x86 net books, or should I port V2.02's
version into "cupcake" branch,I completely have no idea which way is
better, as I have little knowledge in eee701 project, and does not
know what this project do acturally and how to do.
5.       Is any version that fit for x86 and contain OpenCore newer
versions (V2.01 or V2.02)?
6.   Is there any doc exist for porting android 1.5 into x86?

        Thanks in advance!



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

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


Sponsored Links


Other Threads

1. How does a "held" wakelock impact if the service dies with out releasing it?

Wake locks should be released when the object is garbage collected.
See the finalize() method in the WakeLock subclass here:

http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=core/java/android/os/PowerManager.java

You will get a thrown exception in your logs if this occurs.

So, as long as your Service is no longer referenced in memory (e.g. it
has been destroyed), the wakelock should be released. Obviously this
should not be the behaviour by design :)


On Fri, Jun 4, 2010 at 3:36 PM, Satya Komatineni


> 

2. MSM72xx AOSP port missing hardware audio acceleration

Hi, I've just been having a poke about in the MSM7201 code (for my HTC
Hero). I noticed there's code in the AOSP msm kernel which uses the
audio DSP to accelerate mp3, aac, etc audio decoding. I was trying to
figure out how that was hooked into the audio subsystem.

project's libaudio is here:
http://android.git.kernel.org/?p=platform/hardware/msm7k.git;a=tree

The code in there only uses the /dev/msm_pcm devices. However, running
strings over the libaudio.so from the binaries that came with the
phone shows it refers to /dev/msm_mp3, /dev/msm_aac. This kinda
implies that AOSP builds will be doing audio decoding entirely in
software.

Is there a good reason the audio acceleration code is missing from the
AOSP libaudio? I mean, the hardware support code is all there in the
kernel, and it /appears/ it wouldn't exactly be hard to modify the
libaudio source to add the missing glue in.

Am I missing something, or is this just HTC/Qualcomm trying to annoy
me again? :)

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

3. findViewbyId returns null --- called in a custom CursorAdapter -- bindView() method. Codes in body.

4. Rumor: HTC Scorpion and all of its 1.5 Ghz, Android 2.2 goodness headed for Verizon?

5. How does a "held" wakelock impact if the service dies with out releasing it?

6. Acer Ferrari Androi

7. USB On-The-Go on Nexus One!!