Most people are now aware that the gps driver for the NEO 1973 is available once you’ve accepted the EULA, although strangely you can’t look in the docs folder to get at the GPL/LGPL notices or the readme until you’ve agreed to it. I can’t see a specific reason for this and it’s probably just a configuration error.
Aside from all the shouting at the end of the EULA, there is one sentence that did catch my eye and it was fairly early on.
“…removal of the Software from a country in which it is licensed shall automatically terminate this license.”
Notwithstanding the fact that I could pretty much guarentee that neither you or I would happen to know in which countries it is licensed in, apparently if you happen to wander into a country that is not on this list you just lost the right to use the software. I think it’s only fair to know the boundaries, can we have the list please.
Since the EULA doesn’t allow the distribution of the binary .ipk file I’m afraid that you aren’t going to see this in any non-official images either. I’m not even sure that it’s practical for the official images to contain it. What would be useful, however, is if the ‘firstboot’ scripts checked your SD card for the .ipk and automatically installed it for you. I’m fairly certain that I’ll start putting this into my images shortly.
Although it’s a binary only .ipk it is at least a step in the right direction and at least GTA01 owners can now legally use their gps.
Lorn Potter from Trolltech dropped a note into the Openmoko community list to let everyone know that Qtopia can now use the fully GPL’d Cruxus media engine in their Qtopia builds. This is another step forward and away from Helix, which was basically holding Qtopia back in terms of a GPL phone stack. Now all I have to do is get it working properly, once it is I’ll be adding it to my builds. Stay tuned.
Some time ago I wrote what I called the “Ramius” edition of my tracker application for the TomTom Go. The limitations of the Go SDK caused more than its fair share of grief and I shelved the project, hoping to revive it later. Now I’m thinking that it’s time to bring it back to life.
At the moment I’m selling my house in The Netherlands and moving back to the UK. Until the house sells I flit between the UK and Holland every couple of weeks. I’ve taken to using the Chunnel for this because it means I can drive through the night rather than have to bend to the ferry or flight schedules. The trouble is, my wife gets worried that I’m going to crash and burn. She does this every time I do the trip, in either direction. She wont go to bed until she knows that I’ve at least got to the Tunnel.
I brought the original code out of my archive and started looking at it, removing anything that was TomTom specific. I’m pretty sure that I’ll have a workable solution fairly soon, I may butcher the openmoko-agpsui2 application a bit too, just to add a face to the tracker application code. Obviously, it will need a network connection of some sort so I’ll be looking at starting and stopping a gprs connection, or using wifi when the GTA02 arrives.
On the topic of gprs and network connections, I was mulling over some points in my mind about this. Nobody wants their Neo to pull an iPhone, and give us all large bills because of roaming, so there needs to be some mechanism where the user can deny or allow access to things like gprs connections. These could be based on dates, times, even locations with the built in gps. The problem is not that it is difficult to do, the problem is that we need to be able to force applications to use an API to open gprs and wifi conections, and possibly even access the gps. There’s a whole kettle of fish here. Openmoko is opensource, not the Google kind of ‘opensouce’, the real kind. That in itself poses a few questions and perhaps some not so nice answers.
If we want to force people to use an API, then we have to make sure that they can only use the API and not bypass it. If they can bypass it, it’s useless because the malicious ‘l33t h4x0r’ is going to abuse your connection. The problem is, since we are opensource, the same abuser can simply replace the API. Sure you still have to install the application, but just think about it. Right now how many places do you update your Neo from with ipkg? If any one of those gets compromised or the owner deliberately alters packages, the first you’ll know of it is when you bill hits the mat with a thud rather than the usual ‘ftht’.
We can think about signed images or signed packages etc but that is not really going to help, this is opensource. As an application developer I’m going to want to publish applications, I don’t really want to have to get them certified or signed by someone else just so other people can use them. If you alert the user that an application or package is not signed, you know that they’ll just click ‘ok install it anyway’ and ignore it.
I think I’m going to have to ponder this one a little longer.
Some people have been seeing things. Faces. Faces in their Neo’s. Don’t worry, it’s not your imagination it’s me, and I mean that literally, peering at you from under the clock. It’s not some vanity thing, it simply means you’re running one of my builds and allows you to quickly identify that fact.
If you ssh into your Neo and you are running one of my builds, then you will also find a file called
with the release date and time of the image, for example
ScaredyCat release qtopia-image-200711181035
The file appears in both my Qtopia and ScaredyCat builds but, as always, the standard Openmoko builds I do are unaltered so do not contain anything other than what is normally there – at this point that’s nothing, but may change in the future.
If you want to change the picture it’s a fairly simple procedure, either replace the file
with the file you want or change the gconf entry
and make it point to the file you want to use. For example,
gconftool-2 –config-source=xml::/etc/gconf/gconf.xml.defaults –direct –type string –set /desktop/poky/interface/wallpaper /media/card/mypicture.png
You will need to restart the Openmoko-Today application which, for most people, will mean a reboot of ther Neo.
After getting a little frantic over my Neo battery life it appears that it has magically cured itself. I had decided that I’d try to eliminate the software side of thing as a cause for my charging issue. Rolling back to a 20071109 version of one of my own builds showed that the Neo was charging perfectly, rolling forward again and it was still happily charging.
Having left it running all night sampling the battery voltage once a second with no failure or reboot, I’m convinced that it was just a freak failure.
Hopefully other people monitoring their battery using the same method will report their findings so we can see if there is any sort of pattern in this.
keep looking »
Current Electricity Use (15min)
- automated home
- Automated It Technology News
- My Acer page
- My Asterisk pages
- My Work in progress (old)
- Noble Race Car
- openmoko / neo 1973 wiki
- planet openmoko
- Spadgecock Cumpants