Learning to Program in Android So Far

My main source for learn to program has been to follow Ed Burnete's book "Hello, Android."  It is a nice book.  However, it is for 1.5/1.6 and the Android is currently at 2.2.

Following this link:  http://stackoverflow.com/questions/949818/how-can-i-learn-android

Recommends the Developer's Guide on the Android site.

Also recommends several books.  

I think I will go through the Android site Developer's Guide first.

Get My First Appplication on my Nexus One Phone

I have Java, Eclipse and the Android SDK installed.  Also the computer is seeing my phone.

Working from the following link:

http://developer.android.com/resources/tutorials/hello-world.html

Everything seemed fine till I got to the point to look at the code.  The code window doesn't show up.  I have seen it before, but I don't remember what I did.

Had to double click on the HelloAndroid.java name in the tree HelloAndroid ==> src ==> com.example.helloandroid ==> HelloAndroid.java

Now I am unable to edit the code.  Now I can edit the file.  I am now sure what changed.  Was it just way behind?  Don't thing so, other options where working.

My old portable my not be powerful enough to run Eclipse.

Running the app ran it on my HTC that was connected.

Connecting Nexus One to Ubuntu 10.04

This is my guide:  http://ubuntuforums.org/showthread.php?t=1441466

Trying a straight connect with no modification first.

The Nexus One see the connection.

Turned on the debug option on the phone.

Created the USB rules file with the following rules.

SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666", GROUP="plugdev"

Verify the my user is a member of the 'plugdev' group.

Restart the 'udev' process.

$ sudo restart udev

The 'lsusb' command showes the device as present.

$ lsusb

Bus 003 Device 002: ID 18d1:4e12 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Having the same problem that I had before:

$ ./adb devices
List of devices attached
????????????    no permissions

Trying to reboot the PC with the device connected.

The reboot did the trick!

$ ./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9CYP804076    device

I am so close to loading a test program on to my phone, but I am out of time for now.

Android over IPhone for Army

http://gcn.com/articles/2010/06/14/dod-smartphone-unlikely-to-be-iphone.aspx?s=gcndaily_150610

Army leaning towards Android OS for smart phones.

File Sharing with Pogoplug NAS

http://www.crunchgear.com/2009/12/21/review-second-generation-pogoplug-nas/

Looks pretty nice.  Actually transcodes video files automatically.  This lets you display it on your IPOD.  Also has a Android app.  Is is build upon Linux which they don't hide.  The Linux platform is OpenPogo.  You share everything through their server.

There is also TonidoPlug based on Ubuntu.  This seems to support sharing applications which is cool.  It is based on SheevaPlug.  Is PogoPlug based on SheevaPlug?  Lets you share using your own static IP or through DynDNS.com.

Is available from buy.com for $98.00.

The Ubuntu 9.10 Karmic Koala with Linux 2.6.31-generic

I am having trouble getting Linux to see my Google phone so I can test Android applications.

Getting the information in the title.

Get the Linux info

uname -a

Get the Ubunto info

lsb_release -a

LSB stands for Linux Standard Base

Root Kit for Android

http://www.computerworld.com/s/article/9177576/Android_rootkit_is_just_a_phone_call_away?taxonomyId=15&pageNumber=1

This root kit was created by a security consultant working for Chicago's Trustwave. The demo root kit is for a demo in the up coming Defcon hacking conference in LA.  Basically once the root kit is installed it can be activated with a message or phone call.  It can reroute 911 calls or reroute web addresses.  This is only a prof of concept.  The risk currently is low for this type of attack.  One of the things that help reduce the risk is getting apps through the store.  This way if there is a problem, Android can contact those who download the malices app.

It would seem like you want to make darn sure that your browser doesn't have holes in it what would let someone install a root kit from the Internet.

What might be the avenue of attack?  Web, messages, USB, and Bluetooth.  Are there any others?