Anime Phone Wallpapers

Made a couple of these mobile wallpapers a while ago. I keep misplacing them so I'm going to post them here.

They are all 1080x1920 and the bars are consistently placed.
I recommend using a background switcher like SB Wallpaper Changer to change the backgrounds over time.

Note: Artwork is not my own. I merely added the bars on the right for icon placement on my phone.

I'll do requests if your image is 1080x1920 and I like it :3

By The End of 2012, I Will [Continued]

An update on this, as we are almost 2 months in.

1. Books read: 
The Stand, by Stephen King.
A Brief History of Time, by Stephen Hawking.

Currently reading:
Cell, by Stephen King

I'm not counting these but I'm also reading / have read a bunch of MLP fan fiction.
My Little Dashie, by ROBCakeran53.

Heonnshy, by Fenix.
And a bunch other short one chapter stories not worth mentioning.

2. Marathon Training:
Got a stationary bike and riding that on occasion. Making progress and that's the main thing.

4. Flip:
Not much done here. Doing handstands and stuff. Surely my overall fitness increase is helping this too.

5. Android Game:
Another game. This one based on Raiden.
Also have a working prototype. Doing this one straight to Android instead of coding to PC and then porting, like I tried with the last one. Once I get the prototype working, I'll post it up here.

6. Foods:
Had some Takoyaki a couple weeks ago. Pretty damn good so had some more this week again. That will do it for me, but I'm going to keep eating odd stuff where I can.

3. 7. 8. 9. 10. The rest:
Yeah, nothing. Some of these are one off things that I don't really need to prepare for, and will just happen when they happen.

On a funny note, this guy:

Cheers,
Milk

By The End of 2012, I Will

Walking down the road and I saw these on the bus stops. Pretty awesome really.

And so, here is my list.

By The End of 2012, I Will:
1. Read 12 books. (I don't read enough)
2. Run a marathon.
3. Get my full drivers licence. (Seriously, that's long overdue)
4. Do a flip.
5. Release something on the Android market.
6. Try a food I've never tried before.
7. Walk along the train tracks. (I'd walk for weeks if I had the time)
8. Catch a bird with my bare hands.
9. Experience free fall from a great height.
10. Learn all the first generation Pokemon in order.

What are you going to do?

Cheers,
Milk

IP Webcam - Android App

I had the idea of attaching my phone to our NXT robot so that we can see what it sees, as it didn't come with a camera. First thought was to write this myself, but since Android is awesome, someone has done it for me. 

Check it out here. My phone isn't the most powerful, but it runs with no problems at all. Even in the background. 

1) Click start on your phone.

2) Jump on your favourite web browser and type in the URI printed at the bottom of your phone screen.

3) ????

4) Profit!!!

Personally I found using VLC media player a far better option than using a web browser. Press Ctrl + N and enter the URL in here. e.g. http://172.24.120.167:8080/videofeed

And then BAM! Wireless spy camera. Just hope no one steals your phone.

Cheers,

Milk

NXT Robots

So you know how I did a project on swarm robotics and I said I would have some video of it all working, well I forgot and deleted the codes. Rageragerage. The only thing I can find is a screen shot of some early development in my collision avoidance, shown below. The robots are the small boxes and the blue is the line of sight. Trails are on to show the movement path. The yellow one (only one moving) was going to hit the blue one so swerved violently to the right, where he saw he was about to hit the brown so swerved left, then corrected once seeing he had passed the blue robot.

Any who, I now have a summer research project working with Lego. That's right. My summer job is playing with Lego. Jelly? I thought so.

The Lego MindStorm NXT is a robot is a small computer that can support 4 input devices and 3 output devices. Included in our pack are 3 motors (outputs) and 2 touch sensors, 1 ultrasound sensor, and 1 colour sensor. The NXT also supports Bluetooth so I am considering making a controller using my Android. Woot! Here are some existing projects.

 Find and grab a ball

 Solve a Rubik's cube. Epic.

 Fire balls at target.

 Solve a Sudoku

Follow a path.

I am part of a group of 4 people looking at doing some project with these robots. We are looking to have 3 of them and have them interact in some way. The exact specifications of the project are really vague. But we are looking at a warehouse simulation with automated forklifts. Still undecided but this is sounding most likely. This is something that has been done before but not completely autonomous with multiple robots.

We are to program it in Java using LeJOS (Lego Java OS), which is fantastic because I love Java. But terrible because no one on my team has used it before. We will see how this goes.

Epic post about a great Android app coming out soon.

That's all for now.

Cheers,
Milk

miTanks, Part 11

FINALLY!!! After 5 days searching the net and testing heaps of different custom views, I've drawn a circle. That's right. 5 days of work and all I've done is draw a circle. This must sound rediculous but this is the biggest break though. Look! Here it is:

It's amazing. Now I simply had to copy over the view handling bits of code to miTanks and BAM!

We get an ugly, badly drawn game of tanks. It's nice. So now I'm working on tweeking the look so that it, well, works. For those of you using the code snippets I'm putting on here, the main bits are:

In the main class:

public class miTanks extends Activity {

private GameView gv;

/** Called when the activity is first created. */
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
GameView gv = new GameView(this);
setContentView(gv);
}

In the GameView:

public class GameView extends View{

private final Paint PAINT;
private static final Bitmap[] TANK_IMAGES = new Bitmap[8];
private static final int[] TANK_COLOURS = new int[8];
private final GradientDrawable BACKGROUND_GRADIENT;
private static GameView INSTANCE;

/**
 * Initialises the GameView.
 * @param context
 */
public GameView(Context context) {
super(context);
setFocusable(true);
setFocusableInTouchMode(true);
...
/**
 * Draws the game onto the canvas.
 */
protected void onDraw(Canvas canvas){
drawBackground(canvas);
drawGround(canvas);
drawTanks(canvas);
}

In the main.xml:

<?xml version="1.0" encoding="utf-8" ?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
 android:orientation="vertical"
 android:layout_width="fill_parent"
 android:layout_height="fill_parent">
 <com.miTanks.game.GameView
  android:id="@+id/View01"
  android:layout_width="wrap_content"
  android:layout_height="wrap_content"
  android:maxHeight="40dip" />
 </LinearLayout>

miTanks, Part 10

It's not working... I've been trying different ways to get the game to draw to screen though I just don't have it working yet. Fixed a couple minor bugs, as I hadn't moved everything across from the PC version.

When running I follow the debug and step through the program. Turns out the game runs perfectly, that is the game constructs and plays out completely with two random computer players, except it never draws to the screen. Thought the onDraw(Canvas canvas) method would be called automatically every couple of milliseconds. Turns out no. So, I need a way to get the canvas (i.e. the screen) so that I can call the method myself. Working on it...

If anyone knows how android views work, let me know...

As for sounds, I have this site that generates old school game noises. So I'll probably use that for my sounds. Means I don't have to search for people to make decent sounds. Lol. Sorry to those of you that did help with that. There just weren't enough to continue with them.

So the site looks like this:

Here is the link. Will probably be my one stop shop for sounds in the future. Check it out.

My roommate made me a little icon for the game as well. His tanks looks better than the little ones I made in the last post. So may end up replacing them with copies of his. I'll post the icon when I have my computer again.

Cheers,
Milk

miTanks, Part 9

That's right! miTanks is back. After a very very long break I've got motivated to finish it. Or at least get it on the platform it was originally for. Haven't really had much commitment from Foo, which is both our faults really. I'm not the best teacher and he has little / no coding experience. And lobbing him with graphics was not the best move.

Sorry to everyone that doesn't have an Android, but you can still enjoy my struggle with xml and the Android graphics classes... And the PC version will still have the same look and feel as the Android version, with the obvious touch-screen exception.

Can't remember if I've said already or not but this is a fantastic, simple example of how to make a game on Android. The game is open source so I'm basing the majority of figuring out how to do graphics on this. For those of you know don't know software programming is basically: "Learn the basics; google the rest."

Image courtesy of xkcd.

I think I have a pretty good idea of what I need to do now. The tanks are going to look something like this:
 

And the turrets are just going to be a black smooth edged square, pointing at whatever angle they need to. The ground is either going to be a solid colour or each pixel will be 1 of three colours. This will depend on how much time it takes up to search and utilise a very very large 2D colour array.

I'll be using the sky square (not a box, it's 2D) Foo created earlier, because it is awesome. This will be the background of most of the levels. Might end up overlaying some objects like a building or something.

What else? Damage isn't quite right. The tank only takes damage if the very centre is hit. Not a major flaw but not very ascetically pleasing.

I'll get to work on this all tonight and post something on Monday(?) about what I have done.

Links to the other miTanks posts:
Part 1, The Plan
Part 2, Initial Concept
Part 3, Object Oriented Design + Update
Part 4, Sound Request + Update
Part 5, First Screenshots
Part 6, Ground Types
Part 7, Weapons + Ground Dynamics
Part 8, Initial Release

The last one contains the initial release for PC. Have a look at that if you haven't already. Just renamed all my posts... I had two part 4's AND 2 part 6's. That's just bad...

And as always suggestions are always appreciated.

Cheers,
Milk

miAlchemy

So Foo showed me this free game on Android called Alchemy. It's pretty simple. You start off with the four basic elements; earth, fire, water, and air. Then you drag one on another and make something else. e.g. earth + water = swamp, fire + air = energy, energy + swamp = life. There are 360 elements to unlock in the free version.

Being a coder I thought that it seemed pretty simple to make. So, I made miAlchemy (original, I know). Now it doesn't look as awesome as the Android one, and it's for computer instead. It's written in Python; like the last few projects I've put up here.

The way it figures out which elements exist allows for drop in add-ons. That way you can simply add a file into the elements folder and BAM! it's in the game. Images can be changed just as easily.

Mine also allows more then 2 things to be combined at a time. So something like: earth + air + fire + water = life, is possible.

My version has:
Earth
Air
Water
Fire
Alcohol

Put some suggestions in the comments and I'll add it to the game. If it's not obvious, let me know how to make it.

When I get some more elements into the game I'll package it up and release it for you guys.
If you want to do some 40x40 images would be good too.

miTanks, Part 3

As neither me or Foo know how to successfully draw to the screen, we thought we'd make it as easy as we could. Firstly the game will be the size of the screen. This will remove the need for scrolling. The battlefield size will be in relation to some fixed variables, so can be easily changed at will. The game will be completely in landscape view.

Foo agreed to do the visual side of the application. Considering the amount of lower-level coding Foo has actually done, and the combined skills we possess for graphics, this looks like the hardest part. Seemingly working from scratch, the progress on this is slow. So far there is nothing to show.

Done so far:
Did a quick class diagram for the actual game.

Most of the inner workings are completed for in game.
The game physics work, (untested).
Simple flat terrain completed.
Support for differing gravity, wind and landscape.
Support for random terrain generator.
Support for multiple weapons, including weapon movement and collision calculations.
One weapon implemented.
Multiple matches in a game.

Still to do:
Getting input. Once input can be received the usage is already implemented.
Tank movement.
Display. Location calculations implemented. Just need to know how to put an image on the screen.
The game cycle. This will be very easy. Just need to actually do it.
AI calculations, of differing skill levels.
Perfect AI, should be easy to do.
Absolutely useless AI, is even easier.
Realistic AI is somewhat harder. Shouldn't take too long. I'd just fudge some numbers from the perfect AI.
Defensive weaponry support. Shields and such.

Things YOU think I should add:
Leave a comment. Tell me what you would like to see.

Hello, Android!

Well so far Android is hard to program to. Considering I've only ever done to a screen of whatever size I decide, this is very new. Also being an app leaves me with alot of other things to consider. Layout is a huge issue.

Eclipse handles the vast majority of the initial set-up so managed to do this with 2 lines of code changed.

Good start I believe.

miTanks, Part 1

So now that I have an Android phone my next plan is to create an app. I could port some of my CLI games across very easily, but that's no fun. I'm going to remake Tanks, with the help of a friend, herein refered to as Foo.

Tanks is a simple turn-based game. Each player has a tank. On your turn you select the angle to shoot and the power, and then fire. Some minor physics determine travel of the shot. Then there is collision and damage calculations. Rince and repeat until there is only one tank left standing.

I'll get Foo to post an about Foo thing here aswell. Foo has an LG p500 (Optimus One), that runs Android 2.2. Slightly better specs than the Galaxy 580 for a similar price. Galaxy 580 runs Android 2.1, so will use that as the minimum version.

Android

Situation:
I just found out that Dick Smiths Electronics is having a 20% off sales for all their phones, thats ending at 5.30pm today. I've wanted an android for a while now. So I've got 1.5 hours to do some research and see which one to get.

Must be:

• Vodafone
• Keyboard
• Android
• Good
• Preferably cheap

Option 1: Vodafone 845

Main point of difference are the price NZD$199.00. Although there is a lack of not having a keyboard. Resolution is acceptable. The main issue for me is ease of use. I don't particularly like touch screens.
Review from techradar:

The touchscreen itself is resistive rather than capacitive, and it does it's best to resist your commands a large part of the time. Swiping and moving around apps is relatively responsive, but getting the desired response from simply pressing the touchscreen can be difficult. Typing? Again, not so easy.

Review from expertreviews:

As a budget Android phone, the 845 stands out for having the latest version of the operating system, but despite a host of great features, it's no match for the Samsung Galaxy Portal with its 3.2in AMOLED capacitive touchscreen.

Final thought:
Main concern here is the ease of use.


Option 2: Samsung Galaxy 580

Coming in at twice the price of NZD$399.00, the Samsung Galaxy 580 better be good. Again no keyboard. Think I'll only have a quick look at this one.

Review from random customer at DSE:

I've finally found a phone I can use with ease. I never liked the touch screens before but the Samsung Galaxy is really easy to use,
Pro's - 3 instant brightness settings, Good volume control, Clear Icons, WiFi connectivity plus the usual extras. Con's... some apps drain the battery if you don't turn them off, but once you learn what's what, it's a great phone, and really good value for money.

Not really sure if I should be trusting this review for anything.

Final thought:
The only other phone here with Andriod OS 2.1. Will have a look in store.


Option 3: Sony Ericsson X10 Mini Pro

At the same price of the above Samsung Galaxy 580 of NZD$399.00, with a keyboard, the Sony Ericsson X10 Mini Pro seems a more likely option.
Review from cnet:

The addition of a keyboard makes the X10 Mini Pro surprisingly usable, as long as you don't mind its little screen. It's not a phone for media lovers or Web junkies, but, if you're seeking smart-phone prowess in a ridiculously small package, the X10 Mini Pro could be worth a look.

Review from techradar:

The phone itself is much more powerful and responsive than any of the other phones in its entry-level price bracket, so much so that comparing this with the similarly price Vodafone 845 feels quite wrong. The X10 Mini Pro is streets ahead of it.

With such a lack of competing Android QWERTY phones out there on the market, the Sony Ericsson Xperia X10 Mini Pro is going to have the whole sector to itself, we suspect.

In fact, the Mini Pro feels as fast in use as many of the top-spec phones of today like the HTC Desire, so we can imagine it'll also win over quite a few of the 'enthusiasts' out there as well. It's quite an achievement.

And don't fear the small screen – Sony Ericsson has made a smartphone so user friendly you're in no way hindered.In short, the Sony Ericsson Xperia X10 Mini is quite an impressively powerful and polished phone

Final thought:

Definatly on my high list. Wonder how much of a difference this 1.6 Android OS is going to be.

Option 4: LG Optimus GT540

Same price as the above two at NZD$399.00. Again no keyboard. Also using the outdated 1.6 Android OS.

Review from techradar:

The screen is clear and bright, but sadly it's resistive, and far from being the best of its type to come our way. We didn't have to press too hard to make a connection (although it is annoying having to remember to over-press, although we guess that will become second nature eventually).

Final thought:

Another not so user friendly out of date Android mobile. This is starting to look depressing.

Option 5: Sony Ericsson Xperia X8

Another Android at the familar price of NZD$399.00. Again without a keyboard. Let's check the reviews.

Review from techradar:

The good news is the X8's touchscreen uses capacitive technology, so it's immediately more usable than other entry-level Android phones like the LG GT540 and Vodafone 845, which use the cheaper, less sensitive resistive technology. And don't work.

Ok, this looks promising. Again this is using the 1.6 old Android OS. Keep reading.

As a result, the X8 finds itself in a bit of a bad place where it's outsmarted on all fronts by other models – even Sony Ericsson's own X10 Mini is a better option. If you're not concerned about having the latest (or even a particularly recent) version of Android, the X8 will do, but it's hobbled by an unresponsive touchscreen and the many difficulties that brings.

Final thought:

From that last line alone, I'm crossing this off my list.


Option 6: LG Optimus One p500

Recommended by a friend a little too late. Thought I'd add it here anyway. Same price of NZD$399.00.
Review from techradar:

The Optimus One is a solid phone, but there's little in the way of outstanding features to get excited about. The main selling point here is your chance to get Android 2.2 on a budget. That's it.

But in the crowded 3.2-inch smartphone scene, it deserves a second look. There really is no cheaper way to get Android 2.2 out there right now. The way LG has left Android relatively untouched means a basic but functional experience, and it's a refreshing change compared to the overly customised manufacturer skins out there that add needless layers of complexity to the user experience.

Final thought:

Aside from the Android OS 2.2, it seems this phone doesn't have much going for it. And from what I've seen with the actual OS the difference between 2.1 and 2.2 is very minor. The other point of difference is the price. Unfortunatly, the others here are all the same price or cheaper.

In conclusion:

I'm heading down to the store to have a look at options 2 and 3, Samsung Galaxy 580 and Sony Ericsson X10 Mini Pro. Will edit this when I get back.

Cheers,

FINAL THOUGHT:
Went down to the shop. Asked Vodafone, DSE and the warehouse to test some working models of the Galaxy 580 and the X10 Mini Pro. No-one had any, although at every store the assistants had one of their own Galaxys. They all gave amazing reviews and said from what they have tried the X10 is terrible. So I got the Galaxy 580. Also found an even better deal at The Warehouse. Bonus.

Any and all comments welcome.
And if I do get to have a go with any of the others I'll update this accordingly.