Is face recognition and tagging of faces possible through API?

by prachi » Mon, 19 Jul 2010 20:54:52 GMT


Sponsored Links
 Hii

Im  looking for some help to detect faces in group photograph and then
add some comments to each face as we do in picasa.

As pere as detecting faces is concerned i found the API in android but
to tag each face with some comments i could not find any API.

Please help me.....

Is it possible in android??

Are there any APIs for it???

If not then can u tell me if picasa has exposed this feature in its
API?? Any idea???

Any help would be appreciated:)

--



Other Threads

1. How to modify NAND device blocks size from 4096 to 2048 at run-time

Hi,
       I am having a problem where at run-time, android starts using a
4096 block size, whereas the on-board NAND device is 2048.

When I try to run df command after booting from NAND, just after
android init executes, I get the following output:

# df
/dev: 110764K total, 0K used, 110764K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block
size 4096)
/system: 163840K total, 41612K used, 122228K available (block size
4096)
/data: 32768K total, 1972K used, 30796K available (block size 4096)
/cache: 32768K total, 1412K used, 31356K available (block size 4096)

As you can see, the block size being use is 4096 instead of 2048,
which is the block size of my Micron NAND memory used on the gumstix
overo.

As as result, I get a D/dalvikvm(  902): DexOpt: incorrect opt magic
number (0xff ff ff ff) error, as soon as it starts to access the /
system partition and starts to process and optimize the dex files.

When I boot the system from MMC and write the data to the NAND, and
when the android linux kernel uses the ramdisk at boot up from NAND,
it uses a block size of 2048.

However, the moment  android init takes over and the /system partition
is accessed, the block size changes to 4096.

Would anyone happen to know which source file I need to look at to
change this to 2048 ?

I am using a TI OMAP 3503 device, which has a Micron NAND device.

Running

# mtd_debug info /dev/mtd0

reports the following:

mtd.type = MTD_NANDFLASH
mtd.flags = MTD_CAP_ROM
mtd.size = 524288 (512K)
mtd.erasesize = 131072 (128K)
mtd.writesize = 2048 (2K)
mtd.oobsize = 64
regions = 0

So this corresponds to a blocksize (aka erasesize) of 128K which is
made up of 64 x 2K pages (aka writesize).

So, I think the NAND settings are correct at the moment, since the
block / erasesize match up (hex values)

Creating 7 MTD partitions on "omap2-nand":
0x000000000000-0x000000080000 : "xloader"
0x000000080000-0x000000240000 : "uboot"
0x000000240000-0x000000280000 : "uboot environment"
0x000000280000-0x000000680000 : "linux"
0x000000680000-0x00000a680000 : "system"
0x00000a680000-0x00000c680000 : "userdata"
0x00000c680000-0x00000e680000 : "cache"

r...@overo:/# cat /proc/mtd
dev:  offset          size     erasesize  name
mtd0: 0x000000000000  00080000 00020000   "xloader"
mtd1: 0x000000080000  001c0000 00020000   "uboot"
mtd2: 0x000000240000  00040000 00020000   "uboot environment"
mtd3: 0x000000280000  00400000 00020000   "linux"
mtd4: 0x000000680000  0a000000 00020000   "system"
mtd5: 0x00000a680000  02000000 00020000   "userdata"
mtd6: 0x00000c680000  02000000 00020000   "cache"


best regards,

Elvis

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

2. Non Ascii characters are Displayed as ? and squares and some junk characters

Hi,

 I am displaying a set of non ascii characters which are displayed as
some junk characters. What I Do is in one activity take a set of ascii
characters  store it in Sqlite and and in other activity it is
displayed as junk characters. The set of non ascii characters i am
using are
  '', '', '', '', '', '', '', '', '', '', '', '', '',
'', '', '', '', '', '', '', '', '', '', '', '', '', '',
'', '', '', ''


Another problem is Once i store this non ascii characters in database,
I have a feature to send it to another Andorid where the database will
be replaced with the new database. but when i do this the database is
getting corrupted; then happens only if it contains non ascii
characters.

The code for receiving the database is as follows

                                BufferedInputStream is = new
BufferedInputStream(socket.getInputStream());
                                FileOutputStream fos = null;
                                fos = new FileOutputStream(tempPath, true);
                                BufferedOutputStream bos = new 
BufferedOutputStream(fos);
                                int bytesRead = 0, totalBytesReceived = 0;
                                // Read the file from the socket and save it.

                                while (fileSize > 0)
                                {
                                        byte[] buffer = new byte[4096];
                                        if (fileSize >= 4096)
                                        {
                                                bytesRead = readBuffer(is, 
buffer, 4096, bos);
                                        }
                                        else
                                        {

                                                bytesRead = readBuffer(is, 
buffer, fileSize, bos);;

                                        }
                                        fileSize -= bytesRead;
                                }
                                fos.close();

-- 

3. Test speed

4. "unable to open database file" after OS upgrade

5. Paket Data untuk Android

6. Short review Milestone Seidio 2600

7. How to save a file to res/raw ?