From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark Elston <m_elston@comcast.net>
Subject: Re: MobileOrg and Voice Capturing (Android)
Date: Thu, 02 Dec 2010 11:14:28 -0800
Message-ID: <4CF7F014.7080203@comcast.net>
References: <87fwul463g.fsf@gmx.ch>
	<4CF46B08.2020200@comcast.net>	<87d3plotiv.fsf@gmx.ch>
	<4CF6FBF0.1090707@comcast.net> <874oawppqa.fsf@gmx.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=34526 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1POEcF-00085C-Ku
	for emacs-orgmode@gnu.org; Thu, 02 Dec 2010 14:14:56 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <m_elston@comcast.net>) id 1POEc5-0007zv-1E
	for emacs-orgmode@gnu.org; Thu, 02 Dec 2010 14:14:51 -0500
Received: from qmta13.emeryville.ca.mail.comcast.net ([76.96.27.243]:36471)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m_elston@comcast.net>) id 1POEc4-0007zd-NN
	for emacs-orgmode@gnu.org; Thu, 02 Dec 2010 14:14:40 -0500
In-Reply-To: <874oawppqa.fsf@gmx.ch>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

On 12/2/2010 12:02 AM, Sven Bretfeld wrote:
> Mark Elston<m_elston@comcast.net>  writes:
>
>> I don't know about the current state of MobileOrg and its
>> implementation details but I would look at the two sl4a
>> methods:
>>
>>    startActivity, and
>>    startActivityForResult.
>
> Yea, I've tried that already.
>
> droid.startActivity(com.matburt.mobileorg.Capture);
>
> looks right to me, as far as I understand the syntax but the script
> starts and finishes without anything happening. :-(
>
> Sven
>

Sven,

Matthew said in an earlier email that he has some work to do
on the Capture activity to make this work.  I am not sure what
that work is - it *could* be that there is no Intent filter
for that Activity in the manifest for it to respond to.  That
would have the effect you noticed as (I think) both of the
above methods create Intents and send them to the app to start
the Activity.

But whatever it is you will likely have to wait for him to finish
before this will work.

Mark