Making a distributed system

by ThemePark » Sun, 02 Nov 2008 23:22:11 GMT

Sponsored Links
 I've been reading through a bit of the Android documentation, and this
seems to be perfect for developing one of my projects. But in order to
make sure, I need to get some things straight.

Android has processes (background processes being especially
interesting), life cycles, and as far as I can tell, the ability to
connect to networks. So as far as I can tell, I should be able to
build a distributed system, by having a server with my program and
some data, and then any number of G1  phones, that have downloaded and
installed another program for downloading some of the data, running
calculations on it, and uploading it back to the server.

Am I right about being able to do that, and how should I go about with
it? What things should I be careful of/look out for?


Making a distributed system

by Al Sutton » Sun, 02 Nov 2008 23:25:51 GMT

 Your app will most either kill battery life or spend most of it's time 
suspended, making it either unpopular or very slow.

Most battery powered devices (such as the G1) try to increase battery 
life by reducing processing load, so when you whack up the lock the 
battery suffers.


Al Sutton



Sponsored Links

Making a distributed system

by ThemePark » Sun, 02 Nov 2008 23:51:20 GMT

 I saw a YouTube video from the Android team about running multiple
processes, showing how the phone is looking for new pictures on a
Flickr account, while doing something else.

With that in mind, wouldn't it be possible for me to run it as a
background process, possibly only running when the phone is not being
used (if at all possible), and that way not use a whole lot of battery
time and not making it slow either? Think of the way SETI works.


Making a distributed system

by Mark Murphy » Mon, 03 Nov 2008 00:02:40 GMT


[EMAIL PROTECTED] is usually used on machines plugged into AC power. Mobile 
devices are infrequently plugged into AC power.

On a mobile device, every executed instruction eats a tiny bit of 
battery power. What you're suggesting is to execute a whole lot of 
instructions while users are thinking their phone is asleep and 
therefore is not using (much) power.

If Android starts getting used for devices more frequently connected to 
power, using it for a distributed computation cloud might make sense.

Mark Murphy (a Commons Guy) 

Android Training on the Ranch! -- Mar 16-20, 2009 


Making a distributed system

by ThemePark » Mon, 03 Nov 2008 01:21:42 GMT

 Point taken. I didn't think it would use up a lot of battery power,
but you're right, a lot of little bits certain would.

Let's say that Android does get used more on AC powered devices (it
will take me a couple of years to fully make the app anyway, so it's
entirely possible). Then back to my original question. How would I go
about doing that? I'm not so concerned with how to upload and download
data through networks, but more how I would go about with sending data
from one application to another, and how to receive it in an
application as well. I've been reading about using stuff like messages
and threads in general, but I am unsure of what I should use
specifically in Android.


Making a distributed system

by David Given » Mon, 03 Nov 2008 01:51:36 GMT


It would be entirely possible to have the app only run when the device
is charging; given that most people with smartphones leave them on
charge overnight, this would still get you reasonable run time. There's
an ACTION_BATTERY_CHANGED intent that you can register for to get
notified when the AC power status changes, but I don't know offhand how
you'd poll for the current status.

You probably want to read up on this: 

Note that you only really need to do this for IPC between different apps
on the same device. The most common use for this is to allow one app to
communicate with a library that's actually part of another app ---
ContentProviders, for example. For a distributed processing app, the
most likely scenario is to have the actual calculator running as a
background service, with a separate app communicating with it via IPC to
show the results to the user, that only runs when the user actually
wants to watch things happening.

€€  €€€€€  €€€€€
--- Conway's Game Of Life, in one line of APL

Making a distributed system

by Jean-Baptiste Queru » Mon, 03 Nov 2008 07:57:41 GMT

 -Running the CPU at full speed on a G1 will drain the battery in a few hours.

-Running the CPU at full speed on a G1 while the device is charging
will slow down the speed at which the device recharges.

-Running the CPU at full speed on a G1 for any extended period of time
will make the device hot to the touch.


PS: pushing to the extreme, which doesn't seem to be the case here,
it's possible to make a G1 draw so much power that the battery almost
stops charging or even discharges while the device is plugged in,
especially when charging over USB which provides less power than a
wall charger. The CPU alone isn't enough for this, but if you start to
add up enough power-draining peripherals (network, screen, GPS,
accelerometer) you could be consuming several watts.


Other Threads

1. Issue with using fill_parent on Donut

Here is the XML of a camera test application that worked on the
branch. The preview size spans the entire screen on cupcake. However
same app does not work on the Donut branch without explicitly setting
the width and height to 800 and 400 dp respectively?

Why doesn't fill_parent work on the Donut branch?

Example XML

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="
   <SurfaceView android:id="@+id/preview_surface"
           android:layout_width="800dp"                --------------
These lines HAVE to be added for donut
           android:layout_height="480dp"               --------------
but not for cupcake to get full screen preview



2. Writing raw data on a partition.


I want to write raw data on a available partition. I can view that
partition under /dev/block dir.

I am using following command on 'adb shell' and getting error:

echo hi | dd of=/dev/block/mtdblock0
/dev/block/mtdblock0: write error: I/O error
0+1 records in
0+0 records out
0 bytes transferred in 0.002 secs (0 bytes/sec)

I guess I need some special permission inorder to write on the
partition. Can someone please point me to a way by which i can do



3. is it ok to use key store for release as the key store for debugging android application?

4. Blog Tabs not working

5. Samsung Galaxy fullscreen performance

6. android-x86 project home is moving to google sites

7. ADC2 Guidelines