Hi guys,
Anyone else having difficulties compiling libcameraservice.so ? I am trying
to compile it on a ARM5 against prop. libcamera.so and prop. liboemcamera.so
Compiler:
prebuilt/$(HOST_PREBUILT_TAG)/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Whatever I try I get:
target SharedLib:
Hi guys,
Can it be you guys disabled a lot of animation effects for the MDPI devices?
If so, there is a way to enable them for MDPI builds?
Also why are the graphics for MDPI all messed up. They do not seem to be
nicely rendered.
If anyone could explain.
Thanks in advance,
--
unsubscribe:
Open the hardware/alsa_sound/Android.mk and add LOCAL_MODULE_TAGS :=
optional on the correct module.
On Fri, Dec 24, 2010 at 1:39 PM, deepak singal deesin...@gmail.com wrote:
Hi All,
I'm working on porting gingerbread to EVM3550 using the froyo alsa lib
since their are no gingerbread alsa
There is no source code yet guys.. Only SDK with system.img for the
emulator.
On Tue, Dec 7, 2010 at 1:39 PM, Thiru thirumalai.andr...@gmail.com wrote:
How could you say this is gingerbread branch. i couldn't see and 2.3
version
On Tue, Dec 7, 2010 at 5:30 PM, Deva R r.deva...@gmail.com
Anyone?
On Mon, Sep 13, 2010 at 1:16 PM, Mali Laurent i.m.laur...@gmail.com wrote:
I applied the patch but now am getting a very messed up preview on Froyo
Cam. Something like this:
http://blackfin.uclinux.org/gf/download/forummessage/91534/7924/bad2.png
http://blackfin.uclinux.org/gf
I applied the patch but now am getting a very messed up preview on Froyo
Cam. Something like this:
http://blackfin.uclinux.org/gf/download/forummessage/91534/7924/bad2.png
http://blackfin.uclinux.org/gf/download/forummessage/90003/7809/image_30.05.jpg
Recording and taking pictures does work but
:
You should not list softap as an upstream connection. Those should be your
connections to the internet, typically client mode wifi and cellular ifaces.
On Sep 1, 2010 5:52 AM, Mali Laurent i.m.laur...@gmail.com wrote:
That does not make any sense as the foo* interfaces are not even being used
Hello,
!-- List of regexpressions describing the interface (if any) that
represent tetherable
USB interfaces. If the device doesn't want to support tething over
USB this should
be empty. An example would be usb.* --
string-array translatable=false
Hi,e
1. No we do not need a seperate interface.
2. You will need to use eth0 as the tethering config device.
3. This is for me the same question. Or do we need the kernel to have some
other configs enabled?
On Wed, Sep 1, 2010 at 12:17 PM, guru guru.nav...@gmail.com wrote:
Hi Irfan,
I tried
That does not make any sense as the foo* interfaces are not even being used
with this config.
Should be:
string-array translatable=false
name=config_tether_upstream_
regexs
itemusb\\d/item
itemsoftap\\d/item
/string-array
On Wed, Sep 1, 2010 at 10:41 AM, yogesh
Hi list,
I have created a new working device profile to build Froyo AOSP on.
All the propitiatory bins/libs and so on are being pulled in from my
phone like I have always done with the 2.1 AOSP.
The build completed and I have Froyo running almost perfectly. Only 2
issues I have at the moment and
11 matches
Mail list logo
