Mobile capabilities from AJAX

by Jose Mar铆a Gonz谩lez » Wed, 25 Jun 2008 23:51:22 GMT


Sponsored Links
 Hello,
I am interested in develop web pages specials for Android.
I know that the web browser is based on WebKit:
Does this means that the webpages are seen in Safari in the same way
they are seen in Android?

I would like to make a webpage which allows a user to click in some
button or link and launch a call.
Is it possible to access to some mobile expecific capabilities (such
call dialing, messaging, battery status...)  from a web?

Thanks.
--~--~---------~--~----~------------~-------~--~----~



Mobile capabilities from AJAX

by Hong » Thu, 26 Jun 2008 02:20:57 GMT


 the webkit supporst full ajax.

as for dialing call, sms, and battery status, it's not supported out of the
box, but u can have an application running with a bridge to the webkit that
provides the system information.

to natively support from ajax, they need to provide something like the
intel's javascript web 2.0 kit, which has battery info. support.

On Wed, Jun 25, 2008 at 11:51 AM, Jose Mara Gonzlez <[EMAIL PROTECTED]>




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


Sponsored Links


Mobile capabilities from AJAX

by Jose Mar铆a Gonz谩lez » Thu, 26 Jun 2008 20:51:01 GMT


 Thanks Hong, that sounds great.
Could you please provide me with more info. I have no idea hoy to
implement the bridge between my application and the webkit.
Some links will be very helpfull.






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



Mobile capabilities from AJAX

by Gene Vayngrib » Fri, 27 Jun 2008 13:06:10 GMT


 Jose,

Take a look at  http://bhoost.com  which aims to provide exactly what
you are looking for.
Bhoost is an open source wrapper around Android's WebKit browser. It
offers JavaScript API to native Android capabilities.
To launch native dialer it follows a common technique used on iPhone
and s60 phones - all you need is to have an href starting with tel:
and Bhoost will launch the native dialer.
It also can launch camera to shoot and upload photos, has GPS api,
sensors api and more.
At this moment it does not have battery power and network status APIs,
but you can easily add them yourself.
If you have a problem with this - let me know and we will put this in
our Bhoost project plan.

Gene





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



Other Threads

1. how to debug engine layer crash without stack information?

Dear all,
    I'm debugging opencore related app & engine. Normally, when met
engine layer crash issue, we will get the stack info printed in the
log as below.

I/DEBUG   (   33):          #00  pc 00111dac  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #01  pc 00112c66  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #02  pc 00105ff0  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #03  pc 00082b98  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #04  pc 00042fe2  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #05  pc 0004346c  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #06  pc 00043088  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #07  pc 00040e18  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #08  pc 000ede86  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #09  pc 000edf48  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #10  pc 000f56b6  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #11  pc 000f50f4  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #12  pc 00032a50  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #13  pc 00032c7c  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #14  pc 00032e44  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #15  pc 001109ec  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #16  pc 00110b40  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #17  pc 0002affe  /system/lib/
libandroid_runtime.so
I/DEBUG   (   33):          #18  pc 000285d4  /system/lib/libutils.so
I/DEBUG   (   33):          #19  pc 0000f8cc  /system/lib/libc.so
I/DEBUG   (   33):          #20  pc 0000f438  /system/lib/libc.so




    But sometimes, we can not get these info. So it's very hard to fix
the bug at that time. Does anyone know some method to solve this
problem? Thanks!

Best Regards,
Kevin
--~--~---------~--~----~------------~-------~--~----~

2. about "parent mmc0 is sleeping, will not add" error when wakeup

Hi everybody:
    I met a trouble and it confuse me a fews days,that is when my
android wake up,sometimes occours some error aboutT flash card ,here
is the log:
sd 0:0:0:0: [sda] Starting disk
mmc0: new SD card at address 5a61
mmc mmc0:5a61: parent mmc0 is sleeping, will not add
[ cut here ]
WARNING: at drivers/base/power/main.c:78 device_pm_add+0x6c/0xf0()

here is the trace:
Call Trace:
[warn_on_slowpath+95/144] warn_on_slowpath+0x5f/0x90
[device_pm_add+24/240] ? device_pm_add+0x18/0xf0
[device_pm_add+108/240] device_pm_add+0x6c/0xf0
[device_add+1092/1376] device_add+0x444/0x560
[_end+510110570/2109230024] :mmc_core:mmc_add_card+0xa2/0x140
[_end+510117927/2109230024] :mmc_core:mmc_attach_sd+0x17f/0x860
[_end+510109176/2109230024] ? :mmc_core:mmc_rescan+0x0/0x1c0
[_end+510109545/2109230024] :mmc_core:mmc_rescan+0x171/0x1c0
[run_workqueue+246/560] run_workqueue+0xf6/0x230
[worker_thread+167/288] worker_thread+0xa7/0x120
[autoremove_wake_function+0/64] ? autoremove_wake_function+0x0/0x40
[worker_thread+0/288] ? worker_thread+0x0/0x120
[kthread+73/144] kthread+0x49/0x90
[child_rip+10/18] child_rip+0xa/0x12
[restore_args+0/48] ? restore_args+0x0/0x30
[kthread+0/144] ? kthread+0x0/0x90
[child_rip+0/18] ? child_rip+0x0/0x12

I found some conclusion about this:
It's a result of the way the MMC core is written. There's an
upper-level controller device, and below that is a host device, and
below that is the card itself. The code that adds and removes children
of the host device runs as part of the controller driver.
Hence the problem: The driver adds children below the _host_ as soon
as
the _controller_ is resumed, even though the host is still suspended.
It's not as big an error as it sounds -- the host was originally a
class_device and then got converted over to a regular device. It
doesn't have a driver of its own.
This is one of the things that needs to be fixed up as part of the
reworking of the system-sleep API. I simply haven't had any time to
work on it (and I'm not likely to in the near future).

but I still don't know how to do,is there anyone show me a easy way to
fix it ?givng source code and patch is better hanks all
   PSy linux kernel version.6.28
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. Automatic Scrolling view

4. How to open or register a new file extension in Android?

5. pppd stuck in TIOCSETD ioctl call

6. VideoView inside ScrollView

7. Anybody can tell me where is the source code for software mp4 decoder in android?