Archive for the ‘Nexus One’ Category.

Cyanogen

Upgraded to Cyanogen 6 today and found the make-everything-work rebuild permissions option. Now working great with all my apps, root and busybox. Great bit of software.

Froyo, Ubuntu and Busybox

Tried to boot my Ubuntu build on the Nexus and got the shock of my life when it failed to boot. I initially got 2 error messages, the second of which was complaining about a lack of chroot.

The problem was a lack of BusyBox. Since the Froyo build was a stock + root only it is lacking some of the nice toys we are used to.

BusyBox can be downloaded from here. The busybox-armv6l works fine on my Nexus.

Instructions to install it can be found here and here.

Ubuntu now boots just fine.

Froyo + battery

On my first day out with Froyo it seems to be tanking the battery massively. Down to under 50% charge in half a day and needed a mid-day charge. It’s also getting a lot hotter around the base.

I’m going to keep an eye on it and possibly back the radio firmware down to an earlier release if this continues.

Nexus, Froyo and Flash

Or, why Steve Jobs can kiss my ring.

After many unsuccessful attempts to get a Cyanogen build to remain stable on the Nexus (*cries* so many good features) I have opted for the rooted Froyo build, available from here:

FRF50

Some goods, some bads. beebPlayer and Skype seem to be unavailable from the market for this build for the time being. On the up side, the new release appears to be a lot faster and I now have access to the official Flash app from Adobe. While there are many reasons to hate Flash, Jobs seems to have picked the wrong ones as it works perfectly on the Nexus.

Sound is exceedingly quiet in the video. Video quality is down to use of the G1 as a capture device.

Coming soon (when I can be bothered): Open Office on the Ubuntu build.

Flash on the Nexus

I was put off at first for a long time by trying to get a flash player running on the Gnome build. I eventually stumbled on this thread and found out about Gnash. A simple apt-get install gnash was all that was needed on my build to install it.

Adobe now report:

Sadly, the Nexus went chunky under the load from albinoblacksheep and almost crashed like it did last time. I managed to save the Android by killing the VNC server from the ADB shell. It took a couple of minutes of sitting and thinking to recover but after that the UI was as normal and the VNC server came back up quickly. This is the best I have from that run:

Guessing that the load came from the double whammy of both the JavaScript and the Flash I turned to a lighter weight old favourite:

It worked perfectly, without the sound of course.

A half crash

Nothing major new to report. While I was downloading and extracting a large source archive Android was becoming sluggish and throwing up a lot of Force Close/Wait dialogs for standard services.

I kept hitting Wait but suddenly the Nexus rebooted, going to its shiny graphical X intro. Obviously my VNC died as the wireless rebooted but as soon as it was back up I could re-connect and my session was still live.

Back from the (wifi) dead

The importance of nandroid backups cannot be stressed enough.

Installed the 3G patch (early, impatient) and killed wifi by also installing the optional high memory kernel. The radio patch itself works amazingly, pushing the Nexus to slightly better than the G1 in overall terms. Still hit the blackspots where 2G and 3G are passing the buck, but that is exactly the same for my other radio devices.

Keyboard hack

It’s not pretty, but it works.

The bug seems to be with the way that Gnome interfaces with the VNC server. There are a lot of different suggestions over the net to fix it. I have found one that works for me, but I will be trying the vnc4server one at some point.

Hugues Fournier posted a reply to Scrambled Keys in feisty ubuntu desktop which saves a working good keymap and then runs it in the Gnome session.

To do this you need to VNC in to your LXDE environment and run the command:

xmodmap -pke -display :1 > ~/xmodmap.map ( if your VNC display is :1 )

Then create a shell script in your filesystem containing:

#!/bin/bash
cat ~/xmodmap.map | xmodmap -

and chmod u+x it.

This is where I differ from Hughes’ instructions. You need to run this script while within the Gnome environment. For now, I have managed to use mouse control to edit the Menu. You can browse to the script and then enter anything as a name (you can tidy this later). Run the script from the menu and test. I will be looking at ways to auto-boot it later.

Hats off to HTC and Google

Throughout all of this work I am hammering the Nexus and it barely gets warm. It can get to enough above ambient so that you can feel it, but only just.

Admittedly I haven’t tried to increase the clock speed as cyanogen suggests.

Good work on the unit though, compared to the G1 the Nexus runs cold.

Nexus and 3G

http://www.theregister.co.uk/2010/01/26/nexus_one_3g_patch/

Google have confirmed a radio patch for the Nexus to come soon. I can confirm that the trouble is real, the Nexus performance is currently poor compared to the G1 with the HTC radio firmware applied on T-Mobile’s network in the UK.

Once the patch is applied I expect the Nexus to perform well as the difference to the G1 was amazing.

The Nexus is solidly outperforming my other devices in standard 2G use though. It is a rare luxury to have this much signal.