On 22/04/2012 04:26, Jeremy Nicoll - news posts wrote:
> Yes, but we're probably not going to be told the (original) vendor so can't
> judge what those apps might be. Do we think R-Comp have written some
> Android apps?
Possibly not, but on the other hand, I've yet to see two email clients
the same. Things get fiddled with, either for the sake of doing so, or
in some attempt to "add value" over some rather basic stock software.
It seems the Android philosophy is "we'll do the minimum necessary,
everything else you'll need is on the app store" (now known by the
annoying name "Google Play").
>> I don't think it is is about how open Google is, but more how open
>> Android is. Or maybe how not-open other options are.
> Well how open IS Android? I mean, outwith the SDK, APIs etc that the apps
> use?
As far as I know, the GPU and device-specific ASIC tend to be closed
source (it's the supplier's call, some STILL don't bother with viable
datasheets) and the security module/SIM in a phone are also closed
source. I think the browser and Google Market^WPlay are also closed.
Much of the rest is open. Unless you're thinking of rolling your own
port, this isn't important to you.
http://source.android.com/
As for the SDK/API, it might have helped if you did a bit of Googling
before writing the above. It would have pointed the way to developer
tools:
http://developer.android.com/index.html
You can download a complete SDK to use within Eclipse (or not, with a
little more pain), you can develop and push files to your phone. It's a
flavour of Java known as "Dalvik". How close it is to Java is the
subject of endless pointless patent charades.
Sounds like too much pain? You can apparently pointy-clicky apps on a
web-based interface:
http://www.appinventor.mit.edu/
If you'd rather design apps *on* the hardware itself (akin to OPL
programming on a Psion/PocketBook), you have the option to do that too.
I'm not much beyond "hello world" but it is surprisingly functional:
https://play.google.com/store/apps/details?id=com.aide.ui&hl=en
>> Normally Android is closed (for your safety), but (on most devices) you
>> can choose to install non-market apps.
> How is that different from MS being secretive about Windows internals but
> everyone else writings Windows apps?
Extremely. We aren't even talking about the same thing.
YOUR ANDROID ON YOUR DEVICE is normally locked to only download from
Google's Market (aka Google Play). You can, if you are willing to take
the risks associated with apps-from-who-knows-where tick a box in your
setup to allow the device to install from other places.
The same on a PC would be a default option only allowing the
installation of Microsoft products or Microsoft approved products... or
installing everything.
Google is fairly open with Android; however some stuff isn't open. This
is due to being a value-added-component, a security issue, an encryption
issue (ie DRM stuff), or simply because the entity that owns the IPR
says "eff off" (and given how f'd up American law is, most of them take
this sort of attitude).
This doesn't make Google perfect by any means. If you think the big
important question is how open the platform is for developing stuff, you
really shouldn't go anywere near any mobile technology invented in the
last five years.
Hint: Nobody gives a crap about source codes and such these days. It is
all about turning YOU into a commodity. You will probably find the
level of advertising and activity tracking to be scary. And
currently there is little that can be done about it. The EU has
rules, but few care about those and the little guy can't afford to
argue.
To help you get a clue about the new conflict, let me quote you
word for word what my Sony Ericsson Xperia Mini Pro says when I
turn on the GPS:
Will collect anonymous data
while using GPS. Data
transmission charges may
apply.
[ Agree ] [ Disagree ]
If you agree, you can use GPS. If you disagree, you can't. This is
likely to contravene several EU directives, and I've written a
lengthy blog post (not yet uploaded) blowing apart the charade of
calling me "anonymous".
> If I buy one I'll mainly be lying in bed with it;
Perfect for WiFi! :-)
> have the WiFi functions in the router turned off, for security.
Paranoid much?
Set WPA2/AES and a long password (at least 20 characters) and you'll be
fine. Nobody will hack you as it is far easier to get into WEP routers
(by far easier, it apparently runs in the order of 5-30 *minutes*), or
those numpties that don't bother to use any security at all.
So, set up:
Encryption type: WPA2/AES
WiFi pairing: Needs button.
Here, you have two levels of security. The first, obviously, is the
WPA2/AES on your communications. The second, the initial pairing process
should require some sort of physical action on the router itself, such
as pushing a button. This means a device with the correct key still
won't be able to gain access without a physical presence at the router.
It isn't perfect, but it is a help.
However, given the widespread use of cheap routers supplied by numpty
companies to clueless users, setting WPA2/AES will be sufficient for you
to be left alone. There are many easier targets if you want to get
online piggybacking somebody else's connection. Been there, done that.
> I suppose what I'm asking is if one can use an USB/ethernet adapter.
Possibly not. Most USB on these sorts of things works in device mode,
although *some* manufacturers have a special cable for using in host
mode. Even if you could plug in the adaptor, are suitable drivers
installed? Can they be installed?
It is important to understand that you, the user, has very limited
administrative access to an Android device. That is what "rooting" is
all about. The majority of devices can be rooted in one way or another,
but since Android is a fiddled-with Linux, you really don't want to mess
around inside unless you know the system well enough to be able to fix
problems; or to be able to download a replacement firmware and reflash
the device. I speak from (bitter!) experience that the SonyEricsson
updater requires a PC clocking around 2GHz with some 2Gb of RAM. It
worked on mom's eeePC (with harddisc and swap) but habitually failed on
my eeePC (no swap).
That an update program that basically pushes data and instructions down
a USB connection (the actual update is performed by the phone), that it
can't operate on a 1Gb machine clocking 1.6GHz...the dev team should be
taken outside and beaten guantanamo style. There's being wasteful with
resources, then there's taking the p!$$, then there's the SE updater...
In case you haven't guessed, RISC OS won't cut it for updates; not
unless all it involves is placing a file someplace. Which is pretty much
all it ought to involve, but manufacturers like to make it seem more
'difficult' to give you a reason to install their rubbish.
Best wishes,
Rick.