[Commotion-dev] batphone/olsr GUI dev sync

[Jeremy Lakeman]

> git submodule init
> git submodule update

?


On Tue, Mar 13, 2012 at 9:21 AM, Hans-Christoph Steiner
<hans at guardianproject.info> wrote:
>
> It should be possible to make a Remote Service that runs in the
> background and is only killed as a last resort.  It has to be a Remote
> Service, because that is the only way that I know to make the Service
> run in its own process.  We use this in our Gibberbot app to maintain
> the connections to the XMPP server even if the app is killed, and we
> run it a lot on Samsungs.  I checked the AndroidManifest.xml and it
> seems like there is no Remote Service, only standard Services.
>
> Also, I just tried to build the head of 'development', and got the
> errors below:
>
> ndk-build:
>        [exec] jni/Android.mk:65: jni/serval-dna/Android.mk: No such
> file or directory
>        [exec] make: *** No rule to make target
> `jni/serval-dna/Android.mk'.  Stop.
>
> Here's what I did before:
>
> - android update project --path .
> - set sdk.dir and env.NDK_ROOT in local.properties
>
> .hc
>
>
> On 03/12/2012 05:37 PM, Jeremy Lakeman wrote:
>> Actually, I've just reworked the way batphone executes shell commands
>> pretty much exactly like that in the development branch, though I'm
>> not keeping the shell open. These changes also make it easier to tell
>> the different between su permission errors and errors from executing
>> other commands, simplifying a fair amount of code and giving better
>> error messages.
>>
>> We've had one phone that was impossible to root permanently, so the
>> software would always check for root permission when it was started.
>> But some other phones are very aggressive at killing background
>> processes (eg samsung's), which would cause the root test to pop up
>> quite frequently.
>>
>> So we now run a foreground service when the software is "on" which
>> prevents us being killed, and we remember if we had root permission in
>> a setting that is only cleared on boot. As well as tweaking a couple
>> of other places where running commands as root could be avoided.
>>
>> 0.08 is feature complete, and we've pretty much run out of blocking
>> issues. So you can expect to see a release candidate build soon.
>>
>> On Tue, Mar 13, 2012 at 6:26 AM, Hans-Christoph Steiner
>> <hans at guardianproject.info> wrote:
>>>
>>> Hey Jeremy and all,
>>>
>>> I would like to try to keep the OLSR Android GUI app that I'm working on
>>> as in sync as possible with batphone, since all of the adhoc/edify/olsrd
>>> infrastructure will be exactly the same.  So far I've been working with
>>> batphone 0.0.7, which seems to be the head of master in git.  But there
>>> is a lot of work in the 'development' branch, some of which looks
>>> related.  Does it make sense for me to switch over to syncing with your
>>> development branch?
>>>
>>> Also, some feedback on the command line stuff: currently, in the setup
>>> wizard in 0.0.7 asks for root permission on each step.  I generally do
>>> not grant apps permanent root perms, so that means I have to confirm
>>> granting root perms on each step of the wizard, and probably each step
>>> of the app running.  I propose that this app instead launch a root
>>> shell, then execute commands as root by sending them to this shell.
>>>
>>> This way, batphone will only ever ask once for root permission when it
>>> needs it.  We've done this in Lil' Debi and some other apps and it works
>>> well.
>>>
>>> .hc
>>>
>>> _______________________________________________
>>> Commotion-dev mailing list
>>> Commotion-dev at lists.chambana.net
>>> http://lists.chambana.net/mailman/listinfo/commotion-dev
>>>