the camera provide yuv422 data,but openGL "just show the Y plane of
YUV buffers"(frameworks\base\libs\surfaceflinger\LayerBase.cpp
624),must convert yuv422 to rgb565,camera preview is ok,a little
slow,why,thanks
--~--~-~--~~~---~--~~
unsubscribe: [EMAIL PROTECTED]
w
Hi Shivanand,
Thanx for the info. But i am not getting how to create the soft link (to teh
complete directory ) mentioned by you :(
Secondly I have checked out the complete source code from git & build it
which has given me three images system.img, userdata.img & ramdisk.img.
These images only i
etc folder is in system/bin/etc.
create a softlink at root to etc
Are you trying to build android filesystem from git or trying to
extract from the running emulator.
--Shiv
On Wed, Nov 19, 2008 at 10:42 AM, nimit <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am trying to port android on TI Omap. I
I had an email exchange with our partner support group and updated
documents are in the works. I can't give you a timeframe yet.
In the meantime, if you have specific questions, this is the right
place to ask. There are a number of different porting efforts in
various stages, so there's a good ch
Hi,
I am trying to port android on TI Omap. I am following teh
instructions from the following link :-
http://elinux.org/Android_on_OMAP
But i am facing some issues with ramdisk.img. According to it when we
unzip this CPIO archive ( cpio -iv < ../ramdisk) it should give us teh
following root fi
it will be my pleasure to update the porting guide, but i am still
stuck at some point and moreover i am not clear about the whole
porting steps itself. But i f i get a start up i will surely update
the Porting guide.
On Nov 18, 10:11 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> If it's
If you boot from the SD card, do you have the files /dev/block/mmcblk0
and /dev/block/mmcblk0p1? If those files are missing, then mountd
will not attempt to mount the SD card.
You might want to turn on:
#define ENABLE_LOG_MOUNT
#define ENABLE_LOG_SERVER
in system/core/mountd/mountd.h to enable
In my experience, using any part of the SD card makes /sdcard not work.
Example: if, after the system has already booted up and /sdcard is mounted,
I mount a second partition off the SD card, everything is fine until I next
need /sdcard to mount. Specifically, if I plug in the USB cable it work
hello all
When driver register rtc_alarm_interface by class_interface_register
(),it wil call below code:
if (class_intf->add_dev) {
list_for_each_entry(dev, &parent->devices, node)
class_intf->add_dev(dev, class_intf);
}
Then rtc_alarm_ad
Hi Pulkit,
thank you! Can you also see, which file system the rootfs uses?
bye
Markus
On 18 Nov., 19:55, pulkitbisen <[EMAIL PROTECTED]> wrote:
> Hi Markus
>
> This is what it looks like on my G1, and its yaffs2 for the
> system,cache and data partitions.
> rootfs / rootfs ro 0 0
> tmpfs /dev t
I may have a similar problem here. I'm trying to run Android entirely
off the SD card (actually, microSD, on the Zoom). I made three
partitions :
- /dev/mmcblk0p1, vfat, 1G, to be mounted as /sdcard for media data
- /dev/mmcblk0p2, msdos, 10M, to host the uImage for U-Boot (i could
have put it on
Ok, Thanks, It worked, now I am running hciattach as root and without
logwrapper, but the problem..
# I/bluedroid( 665): Starting hciattach daemon
I/bluetooth_ScoSocket.cpp( 705): Listening SCO socket...
E/bluetooth_common.cpp( 665): dbus_func_args_timeout_valist: D-Bus error in
GetName: org.fr
On Tue, Nov 18, 2008 at 2:04 PM, pavan savoy <[EMAIL PROTECTED]> wrote:
> Ok, Looking into it.. Still not solved,
> a #start hciattach on command line returns me just a character "C", whereas
> the same command with or without
> logwrapper runs smoothly even registers with the hcid.
>
Just for ki
Ok, Looking into it.. Still not solved,
a #start hciattach on command line returns me just a character "C", whereas
the same command with or without
logwrapper runs smoothly even registers with the hcid.
Also was the build error valid, or something wrong with my local version?
Thanks & Regards,
P
On Tue, Nov 18, 2008 at 1:48 PM, pavan savoy <[EMAIL PROTECTED]> wrote:
> Yeah, couple of silly mistakes, the hcid, said /system/etc/bluez/hcid.conf
> where it should have said /system/etc/hcid.conf,
> Ok now the hcid is running,
>
> However I still get the error, because I dont think the hciattac
Yeah, couple of silly mistakes, the hcid, said /system/etc/bluez/hcid.conf
where it should have said /system/etc/hcid.conf,
Ok now the hcid is running,
However I still get the error, because I dont think the hciattach is able to
start, although If I run the same command through command line /conso
Sounds like hcid is not running.
To diagnose why, try changing running hcid with -d and via logwrapper to
pipe its output into logcat. For example, in init.rc:
service hcid /system/bin/logwrapper /system/bin/hcid -d ...
Another tip, to quickly turn on some verbose logging of the bluetooth JNI
tr
Hi,
# E/BluetoothDevice( 784): BT_DBG: enable Called
E/BluetoothDeviceService( 656): enableNative will be called now...
E/BluetoothDeviceService.cpp( 656): BT_DBG bt_enable will be called now...
E/BluetoothDeviceService.cpp( 656): BT_DBG bt_enable will be called now...
I/bluedroid( 656): Star
Hi Dmitry,
Thanks that worked!
Best regards,
Mikkel
On Nov 18, 12:56 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Hi,
> You may want to try from shell prompt:
> echo keyguard.no_require_sim=1 >> /data/local.prop"
> setprop keyguard.no_require_sim 1
>
> Thans,
> Dmitry
>
> On Nov 18, 10:
Hi,
You may want to try from shell prompt:
echo keyguard.no_require_sim=1 >> /data/local.prop"
setprop keyguard.no_require_sim 1
Thans,
Dmitry
On Nov 18, 10:43 am, Mikkel Christensen <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I am porting Android to OMAP Zoom board (omapzoom.org) and working on
>
Hi Markus
This is what it looks like on my G1, and its yaffs2 for the
system,cache and data partitions.
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
Hi all,
I am porting Android to OMAP Zoom board (omapzoom.org) and working on
the RIL. I found that if a SIM is not inserted there will only be an
emergency call dialog and it is not possible to get pass this to use
other phone functionality like Music/Video player etc.
In RIL, GET_SIM_STATUS re
If it's important to you, perhaps you might volunteer to update the
porting guide.
On Nov 17, 8:29 pm, Pivotian <[EMAIL PROTECTED]> wrote:
> The Porting Guide is out of date now because google has released the
> entire source code itself. Since its been long time that google
> released the source
On 18 nov, 04:05, Sean McNeil <[EMAIL PROTECTED]> wrote:
> As of 12 hours ago, I broke the rootfs for Freerunner when I disabled
> Packet Video (there are license issues with the codecs). I've now
> deleted this bad rootfs and will place a new one up when I have it fixed.
>
> One way to debug is t
Hi,
I got a bluetooth build error. The bluedroid library doesn't find
bluetooth.h which is inside include/bluedroid/ so the LOCAL_C_INCLUDES for
bluedroid should also include the line..
$(LOCAL_PATH)/include/
Thanks & Regards,
Pavan Savoy.
--~--~-~--~~~---~--~~
I think that this is a question for the android-porting mailing list.
Android-developers is for people having questions related to
developing applications with the SDK.
Thanks,
JBQ
2008/11/18 伊泽 <[EMAIL PROTECTED]>:
> hello all
>
> When driver register rtc_alarm_interface by class_interface_regi
Yes, the kernel linux-2.6.25-android-1.0_r1 has already included the
kobj patch. I have checked it and found it has theses codes.
On Nov 18, 4:23 pm, "sungjun.lee" <[EMAIL PROTECTED]> wrote:
> Hi edwardlee!
>
> Did you apply "kobj" patch exactly?
>
> See following
> patch:http://groups.google.co
Hi,
during the process of finding an optimal filesystem for Android on
real hardware (see
http://groups.google.com/group/android-porting/t/a67cbe36603d429a
), we have started to wonder, which filesystem organisation is used on
a G1 (which directory uses which file system)?
At the moment, our sys
hello world
first i want to trace android linux kernel
i try to do this by using qemu + gdb
but in the end i found qemu can not take -S (freeze CPU at startup)
and usually i got SIGTRAP (i set breakpoints on binder driver)
so i would like to ask how you guys trace android kernel and
framework
Hi edwardlee!
Did you apply "kobj" patch exactly?
See following patch:
http://groups.google.com/group/android-internals/tree/browse_frm/thread/5dd7cc07f256ac15/f875919379234f04?rnum=11&q=Android+Patch+for+i.MX31&_done=%2Fgroup%2Fandroid-internals%2Fbrowse_frm%2Fthread%2F5dd7cc07f256ac15%2Ff2958d
30 matches
Mail list logo
