Sorry about the reporting, reading this on the train going to work and
my fat fingers hit it by mistake
:/ sorry about that

On Apr 17, 3:03 am, Michael Cheselka <[email protected]> wrote:
> Hello,
>
> I just installed android 2.1 on Fedora 12 x86_64 and it's working for me.
>
> 1st step, I followed other peoples advice and installed the following rpms:
>
>     yum install glibc.i686 glibc-devel.i686 libstdc++.i686
> zlib-devel.i686 ncurses-devel.i686 libX11-devel.i686 libXrandr.i686
>
> 2nd step, I installed the latest Sun Microsystems JDK and JRE for
> x86_64 RPM based Linuxes:
>
>     yum install jdk-6u20-linux-amd64.rpm jre-6u20-linux-amd64.rpm
> sun-javadb-common-10.5.3-0.2.i386.rpm
> sun-javadb-core-10.5.3-0.2.i386.rpm
> sun-javadb-client-10.5.3-0.2.i386.rpm
> sun-javadb-demo-10.5.3-0.2.i386.rpm
> sun-javadb-docs-10.5.3-0.2.i386.rpm
> sun-javadb-javadoc-10.5.3-0.2.i386.rpm --nogpgcheck
>
> 3rd step, I twiddled the permissions on my Android dir:
>
>     [ ! -d /opt ] && sudo mkdir -m 0755 /opt
>     sudo tar zxvf
> /home/"${USER}"/Downloads/android-sdk_r05-linux_86.tgz -C /opt/.
>
>     sudo chown -Rf "${USER}":"${USER}" /opt/android-sdk-linux_86/.
>     chcon -R -u system_u /opt/android-sdk-linux_86/.
>     chmod -Rf o-wx /opt/android-sdk-linux_86/.
>     chmod -Rf a+r /opt/android-sdk-linux_86/.
>     find /opt/android-sdk-linux_86 -type d -exec chmod a+x '{}' \;
>
>     cd /opt/android-sdk-linux_86/tools
>     chmod a+x adb android apkbuilder ddms dmtracedump draw9patch
> emulator etc1tool hierarchyviewer hprof-conv layoutopt mksdcard
> sqlite3 traceview zipalign
>     chcon -t bin_t adb android apkbuilder ddms dmtracedump draw9patch
> emulator etc1tool hierarchyviewer hprof-conv layoutopt mksdcard
> sqlite3 traceview zipalign
>
> Details:
> * Name: "droid"
> * Target: Android 2.1 - API Level 7
> * Size: 512MiB
> * Skin: HVGA
>
> Result: works fine.
>
> Finally:
> # rpm -qa --qf '%{name}-%{version}-%{release}.%{arch}\n' | egrep
> '\.i686$' | egrep 'audio|arts|alsa|sound|glibc|gcc|\+\+' | sort
> alsa-lib-1.0.22-2.fc12.i686
> alsa-lib-devel-1.0.22-2.fc12.i686
> alsa-plugins-pulseaudio-1.0.22-1.fc12.i686
> arts-1.5.10-12.fc12.i686
> audiofile-0.2.6-11.fc12.i686
> audiofile-devel-0.2.6-11.fc12.i686
> compat-libstdc++-296-2.96-143.i686
> compat-libstdc++-33-3.2.3-68.i686
> esound-devel-0.2.41-3.fc12.i686
> esound-libs-0.2.41-3.fc12.i686
> glibc-2.11.1-4.i686
> glibc-devel-2.11.1-4.i686
> jack-audio-connection-kit-0.118.0-1.fc12.i686
> libgcc-4.4.3-4.fc12.i686
> libstdc++-4.4.3-4.fc12.i686
> libstdc++-devel-4.4.3-4.fc12.i686
> pulseaudio-libs-0.9.21-5.fc12.i686
> pulseaudio-libs-devel-0.9.21-5.fc12.i686
> pulseaudio-libs-glib2-0.9.21-5.fc12.i686
> pulseaudio-libs-zeroconf-0.9.21-5.fc12.i686
> wine-pulseaudio-1.1.38-1.fc12.i686
>
> Regards,
> Michael Cheselka
> 650-488-4820
>
>
>
>
>
> On Fri, Apr 16, 2010 at 19:28, Michael Cheselka <[email protected]> wrote:
> > Hello,
>
> > This is wrong!  Pulse Audio is new, not old.  People are using it more
> > and more not less and less.
>
> > It is working better all the time on Fedora 12.  Originally I had
> > problems now and then with Pulse Audio but  not in the last few
> > months.  In fact, my bluetooth headphones work best under Fedora 12
> > than under Vista 64 Ultimate or XP Pro.
>
> > It is used now with Gnome, MS Windows, and the Palm Pre.
>
> > Try to fix the problem rather than strip down the OS.
>
> > Read about Pulse Audio here:
>
> >http://en.wikipedia.org/wiki/PulseAudio
>
> > Regards,
> > Michael Cheselka
> > 650-488-4820
>
> > On Fri, Apr 16, 2010 at 15:37, Indicator Veritatis <[email protected]> 
> > wrote:
> >> You should not have to disable audio to run the emulator.
>
> >> I wish I could be sure my proposal would work for this problem, but I
> >> don't: since it is a good idea anyway, I will go ahead and say you
> >> should try removing pulse-audio from your Fedora installation, since
> >> nobody uses it anymore anyway, yet it causes lots of weird problems.
>
> >> I have a lot fewer audio problems ever since removing pulse about a
> >> month ago. Unfortunately, I can't remember exactly how it is done: try
> >> "yum info pulse-audio" as superuser to see if that gives you the exact
> >> package name to remove. Then remove it with "yum remove <pacakge-
> >> name>"
>
> >> On Apr 14, 1:34 pm, yodaa <[email protected]> wrote:
> >>> I hopefully found a workaround
> >>> see:http://forums.fedoraforum.org/showthread.php?p=1350997&posted=1#post1...
>
> >>> That's weird but audio is involved is this issue, arguments must
> >>> passed in the run configuration to disable audio:
>
> >>> In Eclipse, "Run" > "Run Configuration" > "Android Application" > "my
> >>> android app" tab > "target tab > "Additionnal Emulator Command Line
> >>> Options" type "-no-audio" + "Apply"
>
> >>> Running the application is now a success:
>
> >>> [2010-04-14 22:16:36 - HelloDroid] Android Launch!
> >>> [2010-04-14 22:16:36 - HelloDroid] adb is running normally.
> >>> [2010-04-14 22:16:36 - HelloDroid] Performing
> >>> com.tests.HelloDroid.HelloDroid activity launch
> >>> [2010-04-14 22:16:36 - HelloDroid] Automatic Target Mode: launching
> >>> new emulator with compatible AVD 'FakePhone_2_1'
> >>> [2010-04-14 22:16:36 - HelloDroid] Launching a new emulator with
> >>> Virtual Device 'FakePhone_2_1'
> >>> [2010-04-14 22:16:37 - HelloDroid] New emulator found: emulator-5554
> >>> [2010-04-14 22:16:37 - HelloDroid] Waiting for HOME
> >>> ('android.process.acore') to be launched...
> >>> [2010-04-14 22:17:32 - HelloDroid] WARNING: Application does not
> >>> specify an API level requirement!
> >>> [2010-04-14 22:17:32 - HelloDroid] Device API version is 7 (Android
> >>> 2.1)
> >>> [2010-04-14 22:17:32 - HelloDroid] HOME is up on device
> >>> 'emulator-5554'
> >>> [2010-04-14 22:17:32 - HelloDroid] Uploading HelloDroid.apk onto
> >>> device 'emulator-5554'
> >>> [2010-04-14 22:17:32 - HelloDroid] Installing HelloDroid.apk...
> >>> [2010-04-14 22:17:45 - HelloDroid] Success!
> >>> [2010-04-14 22:17:45 - HelloDroid] Starting activity
> >>> com.tests.HelloDroid.HelloDroid on device
> >>> [2010-04-14 22:17:58 - HelloDroid] ActivityManager: Starting: Intent
> >>> { act=android.intent.action.MAIN
> >>> cat=[android.intent.category.LAUNCHER]
> >>> cmp=com.tests.HelloDroid/.HelloDroid }
>
> >>> On 26 mar, 21:37, yodaa <[email protected]> wrote:> Hello,
>
> >>> > I decided to install my Android development environment on my second
> >>> > OS: Fedora 12 x_86_64 (KDE)
> >>> > with proprietary NVIDIA Drivers. My distribution is up to date.
>
> >>> > SUN Java JRE, JDK and Eclipse Galileo EE are installed, Android SDK
> >>> > 2.1, ADT eclipse plugin
> >>> > , android SDK tools, Google APIs... are up to date. I also set up the
> >>> > ~bashrc file for my current user.
>
> >>> > I tried to create a new Android project (Hello World flavour) and get
> >>> > the following error:
>
> >>> > Failed to parse the out of 'adb version'
> >>> > ....android-sdk/tools/adb: error while loading shared libraries:
> >>> > libncurses.so.5:
> >>> > cannot open shared object file
>
> >>> > I figured out that the 32bits libs were missing. So I followed
> >>> > instructions about 32bits needed 
> >>> > packages:http://www.crashcourse.ca/wiki/index.php/The_Android_SDK_on_64-bit_Fe...
> >>> > and installed them:
>
> >>> > ######################################
> >>> > # yum install glibc.i686
> >>> > # yum install glibc-devel.i686
> >>> > # yum install libstdc++.i686
> >>> > # yum install zlib-devel.i686
> >>> > # yum install ncurses-devel.i686
> >>> > # yum install libX11-devel.i686
> >>> > ######################################
>
> >>> > I restarted Eclipse, the previous error message disappeared.
> >>> > I created a virtual device called "fake_phone_2_1" and target my
> >>> > "Hello World" project to Android 2.1.
> >>> > So created my project (HelloDroid), and ran it.
> >>> > The emulator didn't showed up, even after a few minutes.
> >>> > I got no error or warning... I'm missing something here.
>
> >>> > Console output within Eclipse:
> >>> > --------------------------------
> >>> > [2010-03-26 20:09:07 - HelloDroid] Android Launch!
> >>> > [2010-03-26 20:09:08 - HelloDroid] adb is running normally.
> >>> > [2010-03-26 20:09:08 - HelloDroid] Performing
> >>> > com.tests.HelloDroid.HelloDroid activity launch
> >>> > [2010-03-26 20:09:08 - HelloDroid] Automatic Target Mode: launching
> >>> > new emulator with compatible AVD 'FakePhone_2_1'
> >>> > [2010-03-26 20:09:08 - HelloDroid] Launching a new emulator with
> >>> > Virtual Device 'FakePhone_2_1'
>
> >>> > Please find below somemore information about my environement setup:
>
> >>> > 1 ) JRE and JDK location
> >>> > ----------------------
> >>> > /opt/jdk1.6.0_18
> >>> > /opt/jre1.6.0_18
>
> >>> > 2 ) SUN JAVA version
> >>> > --------------------
> >>> > Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
> >>> > Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)
>
> >>> > 3 ) Eclipse Galileo IDE for Java EE Developers
> >>> > -----------------------------------------------
> >>> > /opt/eclipse
>
> >>> > 4 ) Android SDK: android-sdk_r05-linux_86
> >>> > ---------------------------------------
> >>> > /home/johndoe/android-sdk
>
> >>> > 5 ) ".bashrc" file (/home/johndoe/.bashrc)
> >>> > ----------------------------------------
> >>> > # .bashrc
> >>> > # Source global definitions
> >>> > if [ -f /etc/bashrc ]; then
> >>> >         . /etc/bashrc
> >>> > fi
>
> >>> > # User specific aliases and functions
> >>> > export PATH=${PATH}:/home/johndoe/android-sdk/tools
>
> >>> > Help would be appreciated...
>
> >> --
> >> You received this message because you are subscribed to the Google
> >> Groups "Android Beginners" group.
>
> >> NEW! Try asking and tagging your question on Stack Overflow at
> >>http://stackoverflow.com/questions/tagged/android
>
> >> To unsubscribe from this group, send email to
> >> [email protected]
> >> For more options, visit this group at
> >>http://groups.google.com/group/android-beginners?hl=en
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Beginners" group.
>
> NEW! Try asking and tagging your question on Stack Overflow at ...
>
> read more »

-- 
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.

NEW! Try asking and tagging your question on Stack Overflow at
http://stackoverflow.com/questions/tagged/android

To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en

Reply via email to