Shouldn't this page be removed and just redirected to [[Android on Freerunner]]? Or am I missing something? --[[User:JohnSullivan|JohnSullivan]] 16:51, 26 January 2009 (UTC)

+

Q: Shouldn't this page be removed and just redirected to [[Android on Freerunner]]? Or am I missing something? --[[User:JohnSullivan|JohnSullivan]] 16:51, 26 January 2009 (UTC)

+

+

A: I refactored thos pages and separated the content between installation ([[Android on Freerunner]]), development ([[Android porting]]) and usage ([[Android usage]]). I think it's more clear than before where there was duplicate content and content for different audiances mixed. --[[User:Jernst|jernst]] 17:09, 26 January 2009 (UTC)

+

+

Can we rename the [[Android on Freerunner]] page then? The name doesn't say anything about installation... How about, [[Android Installation]], if that's what you are aiming for. There's plenty of info on that page that isn't directly related to installation, and now that I'm actually playing with Android I'm finding the separation confusing.--[[User:JohnSullivan|JohnSullivan]] 18:20, 16 May 2009 (UTC)

As a layman (ie. non-Hacker) I would personally love to see an indepth comparison between the Android OS and the OpenMoko OS, from the point of view of the user / consumer, as of the moment.

+

+

In other words, I would love to see (for example) what I would be getting if I installed Android on the Freerunner, ''feature-wise'', as opposed to keeping the already installed OS. I think I would ''also'' be interested if it would be a good idea, ''feature-wise'', to ditch the T-Mobile G1's (aka. HTC Dream's) native Android installation for OpenMoko OS.

+

+

You know, just to get the competitive spirit going ;)

+

+

(Btw, right now an unlocked HTC Dream and a Freeruner both cost US$399...) --[[User:Lemi4|Lemi4]] 01:22, 18 February 2009 (UTC)

+

+

== Running speed? ==

+

+

Does Android really run this slow or is my Freerunner in bad shape? There is a half second delay between clicking and anything happening on screen. The API finger-painting demo is also laughably slow. On the other hand, the SurfaceView Overlay runs at (what I consider) a reasonable speed for the hardware.

+

+

==Suspend==

+

+

I have the latest Panicking image, with that my FR goes into suspend mode even if plugged-in and when I click the power button to wake it up, it appears immediately the unlock screen in which you have to enter your unlock movement.

+

+

It's like power was pressed two times at once: one for waking up and the other to show the unlock screen.

+

+

It's quite annoying because you can't see the charging percentage when you wake it up or other notifications because you immediately go further than that screen.

+

+

It's just my problem?

+

+

[[User:Dareus|Dareus]] - 2010-01-16-T-11:27

+

+

I don't know what do you mean by "Panicking image", but images from [http://code.google.com/p/android-on-freerunner/] work well.

+

Looks like your problem is addressed in [http://code.google.com/p/android-on-freerunner/issues/detail?id=23]

+

+

[[User:Skliarie|Skliarie]] - 2010-01-16-T-19:03

+

+

With panicking images I mean images from Micheal Trimarchi [http://panicking.kicks-ass.org/download/].

+

+

[[User:Dareus|Dareus]] - 2010-01-18-T-14:29

+

+

Which versions are we talking about? The only usable one for me is the RC which is very slow and exhibits the annoying behaviour described by Dareus.

A: I refactored thos pages and separated the content between installation (Android on Freerunner), development (Android porting) and usage (Android usage). I think it's more clear than before where there was duplicate content and content for different audiances mixed. --jernst 17:09, 26 January 2009 (UTC)

Can we rename the Android on Freerunner page then? The name doesn't say anything about installation... How about, Android Installation, if that's what you are aiming for. There's plenty of info on that page that isn't directly related to installation, and now that I'm actually playing with Android I'm finding the separation confusing.--JohnSullivan 18:20, 16 May 2009 (UTC)

As a layman (ie. non-Hacker) I would personally love to see an indepth comparison between the Android OS and the OpenMoko OS, from the point of view of the user / consumer, as of the moment.

In other words, I would love to see (for example) what I would be getting if I installed Android on the Freerunner, feature-wise, as opposed to keeping the already installed OS. I think I would also be interested if it would be a good idea, feature-wise, to ditch the T-Mobile G1's (aka. HTC Dream's) native Android installation for OpenMoko OS.

You know, just to get the competitive spirit going ;)

(Btw, right now an unlocked HTC Dream and a Freeruner both cost US$399...) --Lemi4 01:22, 18 February 2009 (UTC)

Does Android really run this slow or is my Freerunner in bad shape? There is a half second delay between clicking and anything happening on screen. The API finger-painting demo is also laughably slow. On the other hand, the SurfaceView Overlay runs at (what I consider) a reasonable speed for the hardware.

I have the latest Panicking image, with that my FR goes into suspend mode even if plugged-in and when I click the power button to wake it up, it appears immediately the unlock screen in which you have to enter your unlock movement.

It's like power was pressed two times at once: one for waking up and the other to show the unlock screen.

It's quite annoying because you can't see the charging percentage when you wake it up or other notifications because you immediately go further than that screen.