[9fans] Announcing Inferno for Android phones

[9fans] Announcing Inferno for Android phones

[John Floren]

We would like to announce the availability of Inferno for Android
phones. Because our slogan is "If it ain't broke, break it", we
decided to replace the Java stack on Android phones with
Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
to keep with the Inferno theme, but then we realized we're in Northern
California and the change was obvious.

The Hellaphone runs Inferno directly on top of the basic Linux layer
provided by Android. We do not even allow the Java system to
start. Instead, emu draws directly to the Linux framebuffer (thanks,
Andrey, for the initial code!) and treats the touchscreen like a
one-button mouse. Because the Java environment doesn't start, it only
takes about 10 seconds to go from power off to a fully-booted Inferno
environment.

As of today, we have Inferno running on the Nexus S and the Nook
Color. It should also run on the Android emulator, but we haven't
tested that in a long time. The cell radio is supported, at least on
the Nexus S (the only actual phone we've had), so you can make phone
calls, send texts, and use the data network.

The Inferno window manager has been re-worked with cell phone use in
mind. Windows are automatically sized to fill the whole screen. The
menu has been moved to the top and the menu items have been made
significantly larger. Physical buttons on the phone are now used to do
many common tasks:

    (these keys are for the Nexus S, different bindings are used for
the Nook, which has different keys available)
    * Back: Close the current window
    * Menu: Toggle the onscreen keyboard
    * Home: Minimize the current window
    * Power: Turn off the screen
    * Power+Volume Up: Open the screen brightness widget
    * Power+Volume Down: Turn off the phone
    * Power+Home: Restart Inferno

Installation is reasonably simple. You'll need the Android SDK
(http://developer.android.com/sdk/index.html), with the platform-tools
package installed for the adb and fastboot utilities. We also strongly
recommend installing CyanogenMod on your phone before
proceeding--that's what we use to test.

First, make absolutely sure you have the "adb" and "fastboot"
commands in your path--see the previous paragraph regarding the
SDK and try running "adb" to be sure. Download the tarball from
http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
unpack it in your root. You should end up with a /data/inferno
directory (we put it there because of the Inferno build
process). Then, go to the /data/inferno/android directory and run
the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
Reflash-Nook-Color.sh if you have a Nook). This will
automatically set up the phone to boot into either Inferno or the
regular Java environment--during bootup, the screen will go solid
white; if you touch the screen at this point, it will boot into
the regular Android environment, otherwise it will timeout and go
to Inferno. However, at this point you're not yet ready to boot
into Inferno, so reboot the phone and touch the screen to go into
the regular Android UI. The final task is to run the command "cd
/data/inferno; ./parallel-push.sh". Reboot, let it boot into
Inferno, and you're ready to go.

You can also clone the repository
(http://bitbucket.org/floren/inferno/) and build it yourself, but this
is a significant effort. I do not recommend it if you wish to simply
try the system, but if you want to do development you should get the
repository.

Disclaimer: If you break your phone, it's not our fault. Don't email
us, don't come knocking on our door, and don't call us--oh wait, you
won't be able to do that anyway, your phone is broken!

Credit where credit is due: Ron Minnich came up with the initial
idea--we've been kicking the idea of a Plan 9/Inferno phone around for
years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
lion's share of the work of making Inferno into a usable cell phone
OS--no small feat, considering that neither had any Limbo or Inferno
experience before the start of the summer! They re-wrote the UI,
puzzled out the undocumented cell radio interface, figured out audio,
worked to make Inferno more portable across phones, and generally
figured out how to make Inferno and the Android kernel coexist
peacefully. Andy Jones, another intern, also did some very early work
with Android that helped us figure out the Android init process and
how to build for Android. I took care of getting Inferno running on
the phone in the first place and have been adding things occasionally
since then. We would also like to thank Andrey Mirtchovski for
providing the OLPC framebuffer code (which ported to the Android
phones relatively easily), and of course Charles Forsyth for keeping
the Inferno torch lit all these years (and helping me figure out some
puzzling problems throughout the summer)!

Re: [9fans] Announcing Inferno for Android phones

[Nemo]

impressive :)

On Sep 17, 2011, at 12:23 AM, John Floren <john@jfloren.net> wrote:

> We would like to announce the availability of Inferno for Android
> phones. Because our slogan is "If it ain't broke, break it", we
> decided to replace the Java stack on Android phones with
> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
> to keep with the Inferno theme, but then we realized we're in Northern
> California and the change was obvious.
>
> The Hellaphone runs Inferno directly on top of the basic Linux layer
> provided by Android. We do not even allow the Java system to
> start. Instead, emu draws directly to the Linux framebuffer (thanks,
> Andrey, for the initial code!) and treats the touchscreen like a
> one-button mouse. Because the Java environment doesn't start, it only
> takes about 10 seconds to go from power off to a fully-booted Inferno
> environment.
>
> As of today, we have Inferno running on the Nexus S and the Nook
> Color. It should also run on the Android emulator, but we haven't
> tested that in a long time. The cell radio is supported, at least on
> the Nexus S (the only actual phone we've had), so you can make phone
> calls, send texts, and use the data network.
>
> The Inferno window manager has been re-worked with cell phone use in
> mind. Windows are automatically sized to fill the whole screen. The
> menu has been moved to the top and the menu items have been made
> significantly larger. Physical buttons on the phone are now used to do
> many common tasks:
>
>    (these keys are for the Nexus S, different bindings are used for
> the Nook, which has different keys available)
>    * Back: Close the current window
>    * Menu: Toggle the onscreen keyboard
>    * Home: Minimize the current window
>    * Power: Turn off the screen
>    * Power+Volume Up: Open the screen brightness widget
>    * Power+Volume Down: Turn off the phone
>    * Power+Home: Restart Inferno
>
> Installation is reasonably simple. You'll need the Android SDK
> (http://developer.android.com/sdk/index.html), with the platform-tools
> package installed for the adb and fastboot utilities. We also strongly
> recommend installing CyanogenMod on your phone before
> proceeding--that's what we use to test.
>
> First, make absolutely sure you have the "adb" and "fastboot"
> commands in your path--see the previous paragraph regarding the
> SDK and try running "adb" to be sure. Download the tarball from
> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
> unpack it in your root. You should end up with a /data/inferno
> directory (we put it there because of the Inferno build
> process). Then, go to the /data/inferno/android directory and run
> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
> Reflash-Nook-Color.sh if you have a Nook). This will
> automatically set up the phone to boot into either Inferno or the
> regular Java environment--during bootup, the screen will go solid
> white; if you touch the screen at this point, it will boot into
> the regular Android environment, otherwise it will timeout and go
> to Inferno. However, at this point you're not yet ready to boot
> into Inferno, so reboot the phone and touch the screen to go into
> the regular Android UI. The final task is to run the command "cd
> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
> Inferno, and you're ready to go.
>
> You can also clone the repository
> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
> is a significant effort. I do not recommend it if you wish to simply
> try the system, but if you want to do development you should get the
> repository.
>
> Disclaimer: If you break your phone, it's not our fault. Don't email
> us, don't come knocking on our door, and don't call us--oh wait, you
> won't be able to do that anyway, your phone is broken!
>
> Credit where credit is due: Ron Minnich came up with the initial
> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
> lion's share of the work of making Inferno into a usable cell phone
> OS--no small feat, considering that neither had any Limbo or Inferno
> experience before the start of the summer! They re-wrote the UI,
> puzzled out the undocumented cell radio interface, figured out audio,
> worked to make Inferno more portable across phones, and generally
> figured out how to make Inferno and the Android kernel coexist
> peacefully. Andy Jones, another intern, also did some very early work
> with Android that helped us figure out the Android init process and
> how to build for Android. I took care of getting Inferno running on
> the phone in the first place and have been adding things occasionally
> since then. We would also like to thank Andrey Mirtchovski for
> providing the OLPC framebuffer code (which ported to the Android
> phones relatively easily), and of course Charles Forsyth for keeping
> the Inferno torch lit all these years (and helping me figure out some
> puzzling problems throughout the summer)!
>

Re: [9fans] Announcing Inferno for Android phones

[andrey mirtchovski]

this is cool!

On Fri, Sep 16, 2011 at 4:23 PM, John Floren <john@jfloren.net> wrote:
> We would like to announce the availability of Inferno for Android
> phones. Because our slogan is "If it ain't broke, break it", we
> decided to replace the Java stack on Android phones with
> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
> to keep with the Inferno theme, but then we realized we're in Northern
> California and the change was obvious.
>
> The Hellaphone runs Inferno directly on top of the basic Linux layer
> provided by Android. We do not even allow the Java system to
> start. Instead, emu draws directly to the Linux framebuffer (thanks,
> Andrey, for the initial code!) and treats the touchscreen like a
> one-button mouse. Because the Java environment doesn't start, it only
> takes about 10 seconds to go from power off to a fully-booted Inferno
> environment.
>
> As of today, we have Inferno running on the Nexus S and the Nook
> Color. It should also run on the Android emulator, but we haven't
> tested that in a long time. The cell radio is supported, at least on
> the Nexus S (the only actual phone we've had), so you can make phone
> calls, send texts, and use the data network.
>
> The Inferno window manager has been re-worked with cell phone use in
> mind. Windows are automatically sized to fill the whole screen. The
> menu has been moved to the top and the menu items have been made
> significantly larger. Physical buttons on the phone are now used to do
> many common tasks:
>
>    (these keys are for the Nexus S, different bindings are used for
> the Nook, which has different keys available)
>    * Back: Close the current window
>    * Menu: Toggle the onscreen keyboard
>    * Home: Minimize the current window
>    * Power: Turn off the screen
>    * Power+Volume Up: Open the screen brightness widget
>    * Power+Volume Down: Turn off the phone
>    * Power+Home: Restart Inferno
>
> Installation is reasonably simple. You'll need the Android SDK
> (http://developer.android.com/sdk/index.html), with the platform-tools
> package installed for the adb and fastboot utilities. We also strongly
> recommend installing CyanogenMod on your phone before
> proceeding--that's what we use to test.
>
> First, make absolutely sure you have the "adb" and "fastboot"
> commands in your path--see the previous paragraph regarding the
> SDK and try running "adb" to be sure. Download the tarball from
> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
> unpack it in your root. You should end up with a /data/inferno
> directory (we put it there because of the Inferno build
> process). Then, go to the /data/inferno/android directory and run
> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
> Reflash-Nook-Color.sh if you have a Nook). This will
> automatically set up the phone to boot into either Inferno or the
> regular Java environment--during bootup, the screen will go solid
> white; if you touch the screen at this point, it will boot into
> the regular Android environment, otherwise it will timeout and go
> to Inferno. However, at this point you're not yet ready to boot
> into Inferno, so reboot the phone and touch the screen to go into
> the regular Android UI. The final task is to run the command "cd
> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
> Inferno, and you're ready to go.
>
> You can also clone the repository
> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
> is a significant effort. I do not recommend it if you wish to simply
> try the system, but if you want to do development you should get the
> repository.
>
> Disclaimer: If you break your phone, it's not our fault. Don't email
> us, don't come knocking on our door, and don't call us--oh wait, you
> won't be able to do that anyway, your phone is broken!
>
> Credit where credit is due: Ron Minnich came up with the initial
> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
> lion's share of the work of making Inferno into a usable cell phone
> OS--no small feat, considering that neither had any Limbo or Inferno
> experience before the start of the summer! They re-wrote the UI,
> puzzled out the undocumented cell radio interface, figured out audio,
> worked to make Inferno more portable across phones, and generally
> figured out how to make Inferno and the Android kernel coexist
> peacefully. Andy Jones, another intern, also did some very early work
> with Android that helped us figure out the Android init process and
> how to build for Android. I took care of getting Inferno running on
> the phone in the first place and have been adding things occasionally
> since then. We would also like to thank Andrey Mirtchovski for
> providing the OLPC framebuffer code (which ported to the Android
> phones relatively easily), and of course Charles Forsyth for keeping
> the Inferno torch lit all these years (and helping me figure out some
> puzzling problems throughout the summer)!
>
>

Re: [9fans] Announcing Inferno for Android phones

[Mathieu Lonjaret]

Brilliant.
Any idea how much work it would be to adapt that for the nokia n900?
(runs maemo linux as native OS, or an half-assed android -nitdroid-
with some hackery.)

On Sat, Sep 17, 2011 at 12:32 AM, andrey mirtchovski
<mirtchovski@gmail.com> wrote:
> this is cool!
>
> On Fri, Sep 16, 2011 at 4:23 PM, John Floren <john@jfloren.net> wrote:
>> We would like to announce the availability of Inferno for Android
>> phones. Because our slogan is "If it ain't broke, break it", we
>> decided to replace the Java stack on Android phones with
>> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
>> to keep with the Inferno theme, but then we realized we're in Northern
>> California and the change was obvious.
>>
>> The Hellaphone runs Inferno directly on top of the basic Linux layer
>> provided by Android. We do not even allow the Java system to
>> start. Instead, emu draws directly to the Linux framebuffer (thanks,
>> Andrey, for the initial code!) and treats the touchscreen like a
>> one-button mouse. Because the Java environment doesn't start, it only
>> takes about 10 seconds to go from power off to a fully-booted Inferno
>> environment.
>>
>> As of today, we have Inferno running on the Nexus S and the Nook
>> Color. It should also run on the Android emulator, but we haven't
>> tested that in a long time. The cell radio is supported, at least on
>> the Nexus S (the only actual phone we've had), so you can make phone
>> calls, send texts, and use the data network.
>>
>> The Inferno window manager has been re-worked with cell phone use in
>> mind. Windows are automatically sized to fill the whole screen. The
>> menu has been moved to the top and the menu items have been made
>> significantly larger. Physical buttons on the phone are now used to do
>> many common tasks:
>>
>>    (these keys are for the Nexus S, different bindings are used for
>> the Nook, which has different keys available)
>>    * Back: Close the current window
>>    * Menu: Toggle the onscreen keyboard
>>    * Home: Minimize the current window
>>    * Power: Turn off the screen
>>    * Power+Volume Up: Open the screen brightness widget
>>    * Power+Volume Down: Turn off the phone
>>    * Power+Home: Restart Inferno
>>
>> Installation is reasonably simple. You'll need the Android SDK
>> (http://developer.android.com/sdk/index.html), with the platform-tools
>> package installed for the adb and fastboot utilities. We also strongly
>> recommend installing CyanogenMod on your phone before
>> proceeding--that's what we use to test.
>>
>> First, make absolutely sure you have the "adb" and "fastboot"
>> commands in your path--see the previous paragraph regarding the
>> SDK and try running "adb" to be sure. Download the tarball from
>> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
>> unpack it in your root. You should end up with a /data/inferno
>> directory (we put it there because of the Inferno build
>> process). Then, go to the /data/inferno/android directory and run
>> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
>> Reflash-Nook-Color.sh if you have a Nook). This will
>> automatically set up the phone to boot into either Inferno or the
>> regular Java environment--during bootup, the screen will go solid
>> white; if you touch the screen at this point, it will boot into
>> the regular Android environment, otherwise it will timeout and go
>> to Inferno. However, at this point you're not yet ready to boot
>> into Inferno, so reboot the phone and touch the screen to go into
>> the regular Android UI. The final task is to run the command "cd
>> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
>> Inferno, and you're ready to go.
>>
>> You can also clone the repository
>> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
>> is a significant effort. I do not recommend it if you wish to simply
>> try the system, but if you want to do development you should get the
>> repository.
>>
>> Disclaimer: If you break your phone, it's not our fault. Don't email
>> us, don't come knocking on our door, and don't call us--oh wait, you
>> won't be able to do that anyway, your phone is broken!
>>
>> Credit where credit is due: Ron Minnich came up with the initial
>> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
>> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
>> lion's share of the work of making Inferno into a usable cell phone
>> OS--no small feat, considering that neither had any Limbo or Inferno
>> experience before the start of the summer! They re-wrote the UI,
>> puzzled out the undocumented cell radio interface, figured out audio,
>> worked to make Inferno more portable across phones, and generally
>> figured out how to make Inferno and the Android kernel coexist
>> peacefully. Andy Jones, another intern, also did some very early work
>> with Android that helped us figure out the Android init process and
>> how to build for Android. I took care of getting Inferno running on
>> the phone in the first place and have been adding things occasionally
>> since then. We would also like to thank Andrey Mirtchovski for
>> providing the OLPC framebuffer code (which ported to the Android
>> phones relatively easily), and of course Charles Forsyth for keeping
>> the Inferno torch lit all these years (and helping me figure out some
>> puzzling problems throughout the summer)!
>>
>>
>
>

Re: [9fans] Announcing Inferno for Android phones

[Paul Lalonde]

[-- Attachment #1: Type: text/plain, Size: 5668 bytes --]

A pretty good week for 9fans!
Grats all involved!
Paul

On Fri, Sep 16, 2011 at 3:32 PM, andrey mirtchovski
<mirtchovski@gmail.com>wrote:

> this is cool!
>
> On Fri, Sep 16, 2011 at 4:23 PM, John Floren <john@jfloren.net> wrote:
> > We would like to announce the availability of Inferno for Android
> > phones. Because our slogan is "If it ain't broke, break it", we
> > decided to replace the Java stack on Android phones with
> > Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
> > to keep with the Inferno theme, but then we realized we're in Northern
> > California and the change was obvious.
> >
> > The Hellaphone runs Inferno directly on top of the basic Linux layer
> > provided by Android. We do not even allow the Java system to
> > start. Instead, emu draws directly to the Linux framebuffer (thanks,
> > Andrey, for the initial code!) and treats the touchscreen like a
> > one-button mouse. Because the Java environment doesn't start, it only
> > takes about 10 seconds to go from power off to a fully-booted Inferno
> > environment.
> >
> > As of today, we have Inferno running on the Nexus S and the Nook
> > Color. It should also run on the Android emulator, but we haven't
> > tested that in a long time. The cell radio is supported, at least on
> > the Nexus S (the only actual phone we've had), so you can make phone
> > calls, send texts, and use the data network.
> >
> > The Inferno window manager has been re-worked with cell phone use in
> > mind. Windows are automatically sized to fill the whole screen. The
> > menu has been moved to the top and the menu items have been made
> > significantly larger. Physical buttons on the phone are now used to do
> > many common tasks:
> >
> >    (these keys are for the Nexus S, different bindings are used for
> > the Nook, which has different keys available)
> >    * Back: Close the current window
> >    * Menu: Toggle the onscreen keyboard
> >    * Home: Minimize the current window
> >    * Power: Turn off the screen
> >    * Power+Volume Up: Open the screen brightness widget
> >    * Power+Volume Down: Turn off the phone
> >    * Power+Home: Restart Inferno
> >
> > Installation is reasonably simple. You'll need the Android SDK
> > (http://developer.android.com/sdk/index.html), with the platform-tools
> > package installed for the adb and fastboot utilities. We also strongly
> > recommend installing CyanogenMod on your phone before
> > proceeding--that's what we use to test.
> >
> > First, make absolutely sure you have the "adb" and "fastboot"
> > commands in your path--see the previous paragraph regarding the
> > SDK and try running "adb" to be sure. Download the tarball from
> > http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
> > unpack it in your root. You should end up with a /data/inferno
> > directory (we put it there because of the Inferno build
> > process). Then, go to the /data/inferno/android directory and run
> > the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
> > Reflash-Nook-Color.sh if you have a Nook). This will
> > automatically set up the phone to boot into either Inferno or the
> > regular Java environment--during bootup, the screen will go solid
> > white; if you touch the screen at this point, it will boot into
> > the regular Android environment, otherwise it will timeout and go
> > to Inferno. However, at this point you're not yet ready to boot
> > into Inferno, so reboot the phone and touch the screen to go into
> > the regular Android UI. The final task is to run the command "cd
> > /data/inferno; ./parallel-push.sh". Reboot, let it boot into
> > Inferno, and you're ready to go.
> >
> > You can also clone the repository
> > (http://bitbucket.org/floren/inferno/) and build it yourself, but this
> > is a significant effort. I do not recommend it if you wish to simply
> > try the system, but if you want to do development you should get the
> > repository.
> >
> > Disclaimer: If you break your phone, it's not our fault. Don't email
> > us, don't come knocking on our door, and don't call us--oh wait, you
> > won't be able to do that anyway, your phone is broken!
> >
> > Credit where credit is due: Ron Minnich came up with the initial
> > idea--we've been kicking the idea of a Plan 9/Inferno phone around for
> > years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
> > lion's share of the work of making Inferno into a usable cell phone
> > OS--no small feat, considering that neither had any Limbo or Inferno
> > experience before the start of the summer! They re-wrote the UI,
> > puzzled out the undocumented cell radio interface, figured out audio,
> > worked to make Inferno more portable across phones, and generally
> > figured out how to make Inferno and the Android kernel coexist
> > peacefully. Andy Jones, another intern, also did some very early work
> > with Android that helped us figure out the Android init process and
> > how to build for Android. I took care of getting Inferno running on
> > the phone in the first place and have been adding things occasionally
> > since then. We would also like to thank Andrey Mirtchovski for
> > providing the OLPC framebuffer code (which ported to the Android
> > phones relatively easily), and of course Charles Forsyth for keeping
> > the Inferno torch lit all these years (and helping me figure out some
> > puzzling problems throughout the summer)!
> >
> >
>
>


--
I'm migrating my email.  plalonde@telus.net will soon be disconnected.
 Please use paul.a.lalonde@gmail.com from now on.

[-- Attachment #2: Type: text/html, Size: 7005 bytes --]

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

I know absolutely nothing about the n900, but let me take a quick look
at the wiki page.

Ok, I'm thinking that the n900 seems much more of a pure Linux device
than an Android phone--it runs a derivative of X, even. I think with
probably rather minimal hacking, you could at least get Inferno
running on it, hosted by Linux and displaying in X. The hard part
would probably be talking to the cell radio.


John

On Fri, Sep 16, 2011 at 3:39 PM, Mathieu Lonjaret
<mathieu.lonjaret@gmail.com> wrote:
> Brilliant.
> Any idea how much work it would be to adapt that for the nokia n900?
> (runs maemo linux as native OS, or an half-assed android -nitdroid-
> with some hackery.)
>
> On Sat, Sep 17, 2011 at 12:32 AM, andrey mirtchovski
> <mirtchovski@gmail.com> wrote:
>> this is cool!
>>
>> On Fri, Sep 16, 2011 at 4:23 PM, John Floren <john@jfloren.net> wrote:
>>> We would like to announce the availability of Inferno for Android
>>> phones. Because our slogan is "If it ain't broke, break it", we
>>> decided to replace the Java stack on Android phones with
>>> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
>>> to keep with the Inferno theme, but then we realized we're in Northern
>>> California and the change was obvious.
>>>
>>> The Hellaphone runs Inferno directly on top of the basic Linux layer
>>> provided by Android. We do not even allow the Java system to
>>> start. Instead, emu draws directly to the Linux framebuffer (thanks,
>>> Andrey, for the initial code!) and treats the touchscreen like a
>>> one-button mouse. Because the Java environment doesn't start, it only
>>> takes about 10 seconds to go from power off to a fully-booted Inferno
>>> environment.
>>>
>>> As of today, we have Inferno running on the Nexus S and the Nook
>>> Color. It should also run on the Android emulator, but we haven't
>>> tested that in a long time. The cell radio is supported, at least on
>>> the Nexus S (the only actual phone we've had), so you can make phone
>>> calls, send texts, and use the data network.
>>>
>>> The Inferno window manager has been re-worked with cell phone use in
>>> mind. Windows are automatically sized to fill the whole screen. The
>>> menu has been moved to the top and the menu items have been made
>>> significantly larger. Physical buttons on the phone are now used to do
>>> many common tasks:
>>>
>>>    (these keys are for the Nexus S, different bindings are used for
>>> the Nook, which has different keys available)
>>>    * Back: Close the current window
>>>    * Menu: Toggle the onscreen keyboard
>>>    * Home: Minimize the current window
>>>    * Power: Turn off the screen
>>>    * Power+Volume Up: Open the screen brightness widget
>>>    * Power+Volume Down: Turn off the phone
>>>    * Power+Home: Restart Inferno
>>>
>>> Installation is reasonably simple. You'll need the Android SDK
>>> (http://developer.android.com/sdk/index.html), with the platform-tools
>>> package installed for the adb and fastboot utilities. We also strongly
>>> recommend installing CyanogenMod on your phone before
>>> proceeding--that's what we use to test.
>>>
>>> First, make absolutely sure you have the "adb" and "fastboot"
>>> commands in your path--see the previous paragraph regarding the
>>> SDK and try running "adb" to be sure. Download the tarball from
>>> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
>>> unpack it in your root. You should end up with a /data/inferno
>>> directory (we put it there because of the Inferno build
>>> process). Then, go to the /data/inferno/android directory and run
>>> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
>>> Reflash-Nook-Color.sh if you have a Nook). This will
>>> automatically set up the phone to boot into either Inferno or the
>>> regular Java environment--during bootup, the screen will go solid
>>> white; if you touch the screen at this point, it will boot into
>>> the regular Android environment, otherwise it will timeout and go
>>> to Inferno. However, at this point you're not yet ready to boot
>>> into Inferno, so reboot the phone and touch the screen to go into
>>> the regular Android UI. The final task is to run the command "cd
>>> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
>>> Inferno, and you're ready to go.
>>>
>>> You can also clone the repository
>>> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
>>> is a significant effort. I do not recommend it if you wish to simply
>>> try the system, but if you want to do development you should get the
>>> repository.
>>>
>>> Disclaimer: If you break your phone, it's not our fault. Don't email
>>> us, don't come knocking on our door, and don't call us--oh wait, you
>>> won't be able to do that anyway, your phone is broken!
>>>
>>> Credit where credit is due: Ron Minnich came up with the initial
>>> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
>>> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
>>> lion's share of the work of making Inferno into a usable cell phone
>>> OS--no small feat, considering that neither had any Limbo or Inferno
>>> experience before the start of the summer! They re-wrote the UI,
>>> puzzled out the undocumented cell radio interface, figured out audio,
>>> worked to make Inferno more portable across phones, and generally
>>> figured out how to make Inferno and the Android kernel coexist
>>> peacefully. Andy Jones, another intern, also did some very early work
>>> with Android that helped us figure out the Android init process and
>>> how to build for Android. I took care of getting Inferno running on
>>> the phone in the first place and have been adding things occasionally
>>> since then. We would also like to thank Andrey Mirtchovski for
>>> providing the OLPC framebuffer code (which ported to the Android
>>> phones relatively easily), and of course Charles Forsyth for keeping
>>> the Inferno torch lit all these years (and helping me figure out some
>>> puzzling problems throughout the summer)!
>>>
>>>
>>
>>
>
>

Re: [9fans] Announcing Inferno for Android phones

[andrey mirtchovski]

John, turn a camera on and film the phone while using it, please!

Re: [9fans] Announcing Inferno for Android phones

[Nemo]

or some screenshots at least :)

On Sep 17, 2011, at 12:46 AM, andrey mirtchovski <mirtchovski@gmail.com> wrote:

> John, turn a camera on and film the phone while using it, please!
> 

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

On Fri, Sep 16, 2011 at 3:46 PM, andrey mirtchovski
<mirtchovski@gmail.com> wrote:
> John, turn a camera on and film the phone while using it, please!
>
>

Unfortunately we can't use just any camera here at work... I'll see if
I can get one of the officially blessed cameras, otherwise it'll have
to wait until tonight/the weekend.

We also don't have any SIM cards sitting around to test with at the
moment--so I can show how to use the phone but won't be able to
demonstrate a real phone call. I'll see what I can do, though.


John

Re: [9fans] Announcing Inferno for Android phones

[Bruce Ellis]

intense. good stuff. i have a source in china for cheap smartphones.
might be worth ordering some inferno branded phones.

brucee

On 17 September 2011 08:23, John Floren <john@jfloren.net> wrote:
> We would like to announce the availability of Inferno for Android
> phones. Because our slogan is "If it ain't broke, break it", we
> decided to replace the Java stack on Android phones with
> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
> to keep with the Inferno theme, but then we realized we're in Northern
> California and the change was obvious.
>
> The Hellaphone runs Inferno directly on top of the basic Linux layer
> provided by Android. We do not even allow the Java system to
> start. Instead, emu draws directly to the Linux framebuffer (thanks,
> Andrey, for the initial code!) and treats the touchscreen like a
> one-button mouse. Because the Java environment doesn't start, it only
> takes about 10 seconds to go from power off to a fully-booted Inferno
> environment.
>
> As of today, we have Inferno running on the Nexus S and the Nook
> Color. It should also run on the Android emulator, but we haven't
> tested that in a long time. The cell radio is supported, at least on
> the Nexus S (the only actual phone we've had), so you can make phone
> calls, send texts, and use the data network.
>
> The Inferno window manager has been re-worked with cell phone use in
> mind. Windows are automatically sized to fill the whole screen. The
> menu has been moved to the top and the menu items have been made
> significantly larger. Physical buttons on the phone are now used to do
> many common tasks:
>
>    (these keys are for the Nexus S, different bindings are used for
> the Nook, which has different keys available)
>    * Back: Close the current window
>    * Menu: Toggle the onscreen keyboard
>    * Home: Minimize the current window
>    * Power: Turn off the screen
>    * Power+Volume Up: Open the screen brightness widget
>    * Power+Volume Down: Turn off the phone
>    * Power+Home: Restart Inferno
>
> Installation is reasonably simple. You'll need the Android SDK
> (http://developer.android.com/sdk/index.html), with the platform-tools
> package installed for the adb and fastboot utilities. We also strongly
> recommend installing CyanogenMod on your phone before
> proceeding--that's what we use to test.
>
> First, make absolutely sure you have the "adb" and "fastboot"
> commands in your path--see the previous paragraph regarding the
> SDK and try running "adb" to be sure. Download the tarball from
> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
> unpack it in your root. You should end up with a /data/inferno
> directory (we put it there because of the Inferno build
> process). Then, go to the /data/inferno/android directory and run
> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
> Reflash-Nook-Color.sh if you have a Nook). This will
> automatically set up the phone to boot into either Inferno or the
> regular Java environment--during bootup, the screen will go solid
> white; if you touch the screen at this point, it will boot into
> the regular Android environment, otherwise it will timeout and go
> to Inferno. However, at this point you're not yet ready to boot
> into Inferno, so reboot the phone and touch the screen to go into
> the regular Android UI. The final task is to run the command "cd
> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
> Inferno, and you're ready to go.
>
> You can also clone the repository
> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
> is a significant effort. I do not recommend it if you wish to simply
> try the system, but if you want to do development you should get the
> repository.
>
> Disclaimer: If you break your phone, it's not our fault. Don't email
> us, don't come knocking on our door, and don't call us--oh wait, you
> won't be able to do that anyway, your phone is broken!
>
> Credit where credit is due: Ron Minnich came up with the initial
> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
> lion's share of the work of making Inferno into a usable cell phone
> OS--no small feat, considering that neither had any Limbo or Inferno
> experience before the start of the summer! They re-wrote the UI,
> puzzled out the undocumented cell radio interface, figured out audio,
> worked to make Inferno more portable across phones, and generally
> figured out how to make Inferno and the Android kernel coexist
> peacefully. Andy Jones, another intern, also did some very early work
> with Android that helped us figure out the Android init process and
> how to build for Android. I took care of getting Inferno running on
> the phone in the first place and have been adding things occasionally
> since then. We would also like to thank Andrey Mirtchovski for
> providing the OLPC framebuffer code (which ported to the Android
> phones relatively easily), and of course Charles Forsyth for keeping
> the Inferno torch lit all these years (and helping me figure out some
> puzzling problems throughout the summer)!
>
>



-- 
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

On Fri, Sep 16, 2011 at 4:34 PM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
> intense. good stuff. i have a source in china for cheap smartphones.
> might be worth ordering some inferno branded phones.

would be fun, but wow these nexus s with amoled displays are so pretty!

But yeah cheap iPhones -- the original name, but some folks took it --
would be cool.

ron

Re: [9fans] Announcing Inferno for Android phones

[Joseph Stewart]

[-- Attachment #1: Type: text/plain, Size: 5199 bytes --]

You guys rock!

On Fri, Sep 16, 2011 at 6:23 PM, John Floren <john@jfloren.net> wrote:

> We would like to announce the availability of Inferno for Android
> phones. Because our slogan is "If it ain't broke, break it", we
> decided to replace the Java stack on Android phones with
> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
> to keep with the Inferno theme, but then we realized we're in Northern
> California and the change was obvious.
>
> The Hellaphone runs Inferno directly on top of the basic Linux layer
> provided by Android. We do not even allow the Java system to
> start. Instead, emu draws directly to the Linux framebuffer (thanks,
> Andrey, for the initial code!) and treats the touchscreen like a
> one-button mouse. Because the Java environment doesn't start, it only
> takes about 10 seconds to go from power off to a fully-booted Inferno
> environment.
>
> As of today, we have Inferno running on the Nexus S and the Nook
> Color. It should also run on the Android emulator, but we haven't
> tested that in a long time. The cell radio is supported, at least on
> the Nexus S (the only actual phone we've had), so you can make phone
> calls, send texts, and use the data network.
>
> The Inferno window manager has been re-worked with cell phone use in
> mind. Windows are automatically sized to fill the whole screen. The
> menu has been moved to the top and the menu items have been made
> significantly larger. Physical buttons on the phone are now used to do
> many common tasks:
>
>    (these keys are for the Nexus S, different bindings are used for
> the Nook, which has different keys available)
>    * Back: Close the current window
>    * Menu: Toggle the onscreen keyboard
>    * Home: Minimize the current window
>    * Power: Turn off the screen
>    * Power+Volume Up: Open the screen brightness widget
>    * Power+Volume Down: Turn off the phone
>    * Power+Home: Restart Inferno
>
> Installation is reasonably simple. You'll need the Android SDK
> (http://developer.android.com/sdk/index.html), with the platform-tools
> package installed for the adb and fastboot utilities. We also strongly
> recommend installing CyanogenMod on your phone before
> proceeding--that's what we use to test.
>
> First, make absolutely sure you have the "adb" and "fastboot"
> commands in your path--see the previous paragraph regarding the
> SDK and try running "adb" to be sure. Download the tarball from
> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
> unpack it in your root. You should end up with a /data/inferno
> directory (we put it there because of the Inferno build
> process). Then, go to the /data/inferno/android directory and run
> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
> Reflash-Nook-Color.sh if you have a Nook). This will
> automatically set up the phone to boot into either Inferno or the
> regular Java environment--during bootup, the screen will go solid
> white; if you touch the screen at this point, it will boot into
> the regular Android environment, otherwise it will timeout and go
> to Inferno. However, at this point you're not yet ready to boot
> into Inferno, so reboot the phone and touch the screen to go into
> the regular Android UI. The final task is to run the command "cd
> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
> Inferno, and you're ready to go.
>
> You can also clone the repository
> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
> is a significant effort. I do not recommend it if you wish to simply
> try the system, but if you want to do development you should get the
> repository.
>
> Disclaimer: If you break your phone, it's not our fault. Don't email
> us, don't come knocking on our door, and don't call us--oh wait, you
> won't be able to do that anyway, your phone is broken!
>
> Credit where credit is due: Ron Minnich came up with the initial
> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
> lion's share of the work of making Inferno into a usable cell phone
> OS--no small feat, considering that neither had any Limbo or Inferno
> experience before the start of the summer! They re-wrote the UI,
> puzzled out the undocumented cell radio interface, figured out audio,
> worked to make Inferno more portable across phones, and generally
> figured out how to make Inferno and the Android kernel coexist
> peacefully. Andy Jones, another intern, also did some very early work
> with Android that helped us figure out the Android init process and
> how to build for Android. I took care of getting Inferno running on
> the phone in the first place and have been adding things occasionally
> since then. We would also like to thank Andrey Mirtchovski for
> providing the OLPC framebuffer code (which ported to the Android
> phones relatively easily), and of course Charles Forsyth for keeping
> the Inferno torch lit all these years (and helping me figure out some
> puzzling problems throughout the summer)!
>
>

[-- Attachment #2: Type: text/html, Size: 5972 bytes --]

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

One caveat that I just came across: If you're trying to set up your
phone from Mac OS X, it's quite possible that the case-insensitive
filesystem will bite you. We have two directories at the same level,
named "android" and "Android". If you do an adb push from OS X,
they'll both end up in a directory called "android". Here's how you
can fix it:

(run adb shell)
# mkdir /data/inferno/Android
# mv /data/inferno/android/arm /data/inferno/Android/

There may be other problems lurking, but I'm pretty sure all of the
stuff Inferno needs is all lowercase.


John

On Fri, Sep 16, 2011 at 3:23 PM, John Floren <john@jfloren.net> wrote:
> We would like to announce the availability of Inferno for Android
> phones. Because our slogan is "If it ain't broke, break it", we
> decided to replace the Java stack on Android phones with
> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
> to keep with the Inferno theme, but then we realized we're in Northern
> California and the change was obvious.
>
> The Hellaphone runs Inferno directly on top of the basic Linux layer
> provided by Android. We do not even allow the Java system to
> start. Instead, emu draws directly to the Linux framebuffer (thanks,
> Andrey, for the initial code!) and treats the touchscreen like a
> one-button mouse. Because the Java environment doesn't start, it only
> takes about 10 seconds to go from power off to a fully-booted Inferno
> environment.
>
> As of today, we have Inferno running on the Nexus S and the Nook
> Color. It should also run on the Android emulator, but we haven't
> tested that in a long time. The cell radio is supported, at least on
> the Nexus S (the only actual phone we've had), so you can make phone
> calls, send texts, and use the data network.
>
> The Inferno window manager has been re-worked with cell phone use in
> mind. Windows are automatically sized to fill the whole screen. The
> menu has been moved to the top and the menu items have been made
> significantly larger. Physical buttons on the phone are now used to do
> many common tasks:
>
>    (these keys are for the Nexus S, different bindings are used for
> the Nook, which has different keys available)
>    * Back: Close the current window
>    * Menu: Toggle the onscreen keyboard
>    * Home: Minimize the current window
>    * Power: Turn off the screen
>    * Power+Volume Up: Open the screen brightness widget
>    * Power+Volume Down: Turn off the phone
>    * Power+Home: Restart Inferno
>
> Installation is reasonably simple. You'll need the Android SDK
> (http://developer.android.com/sdk/index.html), with the platform-tools
> package installed for the adb and fastboot utilities. We also strongly
> recommend installing CyanogenMod on your phone before
> proceeding--that's what we use to test.
>
> First, make absolutely sure you have the "adb" and "fastboot"
> commands in your path--see the previous paragraph regarding the
> SDK and try running "adb" to be sure. Download the tarball from
> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
> unpack it in your root. You should end up with a /data/inferno
> directory (we put it there because of the Inferno build
> process). Then, go to the /data/inferno/android directory and run
> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
> Reflash-Nook-Color.sh if you have a Nook). This will
> automatically set up the phone to boot into either Inferno or the
> regular Java environment--during bootup, the screen will go solid
> white; if you touch the screen at this point, it will boot into
> the regular Android environment, otherwise it will timeout and go
> to Inferno. However, at this point you're not yet ready to boot
> into Inferno, so reboot the phone and touch the screen to go into
> the regular Android UI. The final task is to run the command "cd
> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
> Inferno, and you're ready to go.
>
> You can also clone the repository
> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
> is a significant effort. I do not recommend it if you wish to simply
> try the system, but if you want to do development you should get the
> repository.
>
> Disclaimer: If you break your phone, it's not our fault. Don't email
> us, don't come knocking on our door, and don't call us--oh wait, you
> won't be able to do that anyway, your phone is broken!
>
> Credit where credit is due: Ron Minnich came up with the initial
> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
> lion's share of the work of making Inferno into a usable cell phone
> OS--no small feat, considering that neither had any Limbo or Inferno
> experience before the start of the summer! They re-wrote the UI,
> puzzled out the undocumented cell radio interface, figured out audio,
> worked to make Inferno more portable across phones, and generally
> figured out how to make Inferno and the Android kernel coexist
> peacefully. Andy Jones, another intern, also did some very early work
> with Android that helped us figure out the Android init process and
> how to build for Android. I took care of getting Inferno running on
> the phone in the first place and have been adding things occasionally
> since then. We would also like to thank Andrey Mirtchovski for
> providing the OLPC framebuffer code (which ported to the Android
> phones relatively easily), and of course Charles Forsyth for keeping
> the Inferno torch lit all these years (and helping me figure out some
> puzzling problems throughout the summer)!
>

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

On Fri, Sep 16, 2011 at 3:23 PM, John Floren <john@jfloren.net> wrote:

> Installation is reasonably simple. You'll need the Android SDK
> (http://developer.android.com/sdk/index.html), with the platform-tools
> package installed for the adb and fastboot utilities.


I think things have changed since you started this work a while back
-- hey, it's android, right?

First off, my phone when turned on says 'fastboot mode'. Does this
maybe mean it's already unlocked? It certainly doesn't match what the
various sites say I should expect to see. It does indicate that it is
locked, however.

Second off, I just pulled this down:
http://developer.android.com/sdk/index.html (the mac version),
patiently waited while I did a
tools/android update sdk

and got lots and lots and lots of stuff, but ... no fastboot.

The link on this page http://wiki.cyanogenmod.com/wiki/Fastboot goes
to an HTC site -- is that really what I want for a samsung phone?

Ah, ok, went to the linux tools and it's there.

So, first step, everyone: in spite of the docs you see on many Android
pages, you may not have fastboot on OSX. Just Linux.

ron

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

On Fri, Sep 16, 2011 at 9:24 PM, ron minnich <rminnich@gmail.com> wrote:
> On Fri, Sep 16, 2011 at 3:23 PM, John Floren <john@jfloren.net> wrote:
>
>> Installation is reasonably simple. You'll need the Android SDK
>> (http://developer.android.com/sdk/index.html), with the platform-tools
>> package installed for the adb and fastboot utilities.
>
>
> I think things have changed since you started this work a while back
> -- hey, it's android, right?
>
> First off, my phone when turned on says 'fastboot mode'. Does this
> maybe mean it's already unlocked? It certainly doesn't match what the
> various sites say I should expect to see. It does indicate that it is
> locked, however.
>
> Second off, I just pulled this down:
> http://developer.android.com/sdk/index.html (the mac version),
> patiently waited while I did a
> tools/android update sdk
>
> and got lots and lots and lots of stuff, but ... no fastboot.
>
> The link on this page http://wiki.cyanogenmod.com/wiki/Fastboot goes
> to an HTC site -- is that really what I want for a samsung phone?
>
> Ah, ok, went to the linux tools and it's there.
>
> So, first step, everyone: in spite of the docs you see on many Android
> pages, you may not have fastboot on OSX. Just Linux.
>
> ron
>
>

We did all our development on Linux... had no idea fastboot doesn't
ship with the SDK for OS X. And yeah, the link on the cyanogenmod wiki
is outdated. Ugh.

Just use Linux, guys :) I've looked around a bit but have not yet been
able to find out where to download fastboot for OS X.


John

Re: [9fans] Announcing Inferno for Android phones

[Skip Tavakkolian]

Nice work!  I plan to try it on a few android devices the first chance i get.

BTW, my experience with the emulator at the api/dalvik level has given
me confidence that if i can run it on the emulator (interacting with
it using DDMS) i can run it on any device.

-Skip

On Fri, Sep 16, 2011 at 3:23 PM, John Floren <john@jfloren.net> wrote:
> We would like to announce the availability of Inferno for Android
> phones. Because our slogan is "If it ain't broke, break it", we
> decided to replace the Java stack on Android phones with
> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
> to keep with the Inferno theme, but then we realized we're in Northern
> California and the change was obvious.
>
> The Hellaphone runs Inferno directly on top of the basic Linux layer
> provided by Android. We do not even allow the Java system to
> start. Instead, emu draws directly to the Linux framebuffer (thanks,
> Andrey, for the initial code!) and treats the touchscreen like a
> one-button mouse. Because the Java environment doesn't start, it only
> takes about 10 seconds to go from power off to a fully-booted Inferno
> environment.
>
> As of today, we have Inferno running on the Nexus S and the Nook
> Color. It should also run on the Android emulator, but we haven't
> tested that in a long time. The cell radio is supported, at least on
> the Nexus S (the only actual phone we've had), so you can make phone
> calls, send texts, and use the data network.
>
> The Inferno window manager has been re-worked with cell phone use in
> mind. Windows are automatically sized to fill the whole screen. The
> menu has been moved to the top and the menu items have been made
> significantly larger. Physical buttons on the phone are now used to do
> many common tasks:
>
>    (these keys are for the Nexus S, different bindings are used for
> the Nook, which has different keys available)
>    * Back: Close the current window
>    * Menu: Toggle the onscreen keyboard
>    * Home: Minimize the current window
>    * Power: Turn off the screen
>    * Power+Volume Up: Open the screen brightness widget
>    * Power+Volume Down: Turn off the phone
>    * Power+Home: Restart Inferno
>
> Installation is reasonably simple. You'll need the Android SDK
> (http://developer.android.com/sdk/index.html), with the platform-tools
> package installed for the adb and fastboot utilities. We also strongly
> recommend installing CyanogenMod on your phone before
> proceeding--that's what we use to test.
>
> First, make absolutely sure you have the "adb" and "fastboot"
> commands in your path--see the previous paragraph regarding the
> SDK and try running "adb" to be sure. Download the tarball from
> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
> unpack it in your root. You should end up with a /data/inferno
> directory (we put it there because of the Inferno build
> process). Then, go to the /data/inferno/android directory and run
> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
> Reflash-Nook-Color.sh if you have a Nook). This will
> automatically set up the phone to boot into either Inferno or the
> regular Java environment--during bootup, the screen will go solid
> white; if you touch the screen at this point, it will boot into
> the regular Android environment, otherwise it will timeout and go
> to Inferno. However, at this point you're not yet ready to boot
> into Inferno, so reboot the phone and touch the screen to go into
> the regular Android UI. The final task is to run the command "cd
> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
> Inferno, and you're ready to go.
>
> You can also clone the repository
> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
> is a significant effort. I do not recommend it if you wish to simply
> try the system, but if you want to do development you should get the
> repository.
>
> Disclaimer: If you break your phone, it's not our fault. Don't email
> us, don't come knocking on our door, and don't call us--oh wait, you
> won't be able to do that anyway, your phone is broken!
>
> Credit where credit is due: Ron Minnich came up with the initial
> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
> lion's share of the work of making Inferno into a usable cell phone
> OS--no small feat, considering that neither had any Limbo or Inferno
> experience before the start of the summer! They re-wrote the UI,
> puzzled out the undocumented cell radio interface, figured out audio,
> worked to make Inferno more portable across phones, and generally
> figured out how to make Inferno and the Android kernel coexist
> peacefully. Andy Jones, another intern, also did some very early work
> with Android that helped us figure out the Android init process and
> how to build for Android. I took care of getting Inferno running on
> the phone in the first place and have been adding things occasionally
> since then. We would also like to thank Andrey Mirtchovski for
> providing the OLPC framebuffer code (which ported to the Android
> phones relatively easily), and of course Charles Forsyth for keeping
> the Inferno torch lit all these years (and helping me figure out some
> puzzling problems throughout the summer)!
>
>

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

OK, a little more info.

I booted a linux vm and ran the fastboot command to
unlock the phone
install clockwork mod recovery

at that point, once the phone rebooted, linux in the vm could no
longer enumerate it. Linux got usb events, but it could not, in its
own words, "enumerate the device"

So I went back to the mac, and using the adb tool, was able to find
the phone, connect to it, push a file to it, and install clockwork
mod.

Now, that clockwork mod is sitting here showing the boot screen endlessly.

So I went back to recovery screen on the phone, wiped the data and
cache again, rebooted again, and this time it came up fine.

adb shell gets a nice root shell. So, at this point, you'll own the phone.

So, tomorrow, on to inferno!

ron

Re: [9fans] Announcing Inferno for Android phones

[Richard Miller]

> Any idea how much work it would be to adapt that for the nokia n900?

No need for the android version on maemo - standard hosted
inferno "just works" on the n900.  I've been running it for
quite a while (or was until my pocket was picked in Paris last
week ☹).  I'll have to go back to my n800 (=n900 without the
phone part) which also runs standard inferno happily, after a
small mod to win-x11a (in contrib/miller/inferno/n800).

N900 is a nice device, but android phones can be a lot cheaper.

Re: [9fans] Announcing Inferno for Android phones

[Mathieu Lonjaret]

Good to know, thanks!

On Sat, Sep 17, 2011 at 12:58 PM, Richard Miller <9fans@hamnavoe.com> wrote:
>> Any idea how much work it would be to adapt that for the nokia n900?
>
> No need for the android version on maemo - standard hosted
> inferno "just works" on the n900.  I've been running it for
> quite a while (or was until my pocket was picked in Paris last
> week ☹).  I'll have to go back to my n800 (=n900 without the
> phone part) which also runs standard inferno happily, after a
> small mod to win-x11a (in contrib/miller/inferno/n800).
>
> N900 is a nice device, but android phones can be a lot cheaper.
>
>
>

Re: [9fans] Announcing Inferno for Android phones

[Ethan Grammatikidis]

On Fri, 16 Sep 2011 15:23:01 -0700
John Floren <john@jfloren.net> wrote:

> We would like to announce the availability of Inferno for Android
> phones. Because our slogan is "If it ain't broke, break it", we
> decided to replace the Java stack on Android phones with
> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
> to keep with the Inferno theme, but then we realized we're in Northern
> California and the change was obvious.

Excelent! Now where can I steal an Android phone from...

There's a tablet I might be able to get my hands on but it's got some
funky CPU; not ARM, something else. My memory is saying "Dragonball"
but I've got a feeling it's lying.

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

OK, more data this morning.

Since the cyanogen upgrade, no linux vm I have on OSX/VMWare can
enumerate the phone over USB. This is a very common problem as
revealed by any search.

On the one linux box I have, the phone is enumerated as a USB storage.
There may be some setting I need to reset ... but that box, having
been turned off since april, seems to have decided it can't do wifi
more ... so, that's not an option at present!

I did try downloading the android sdk on a clean vmware-based linux
platform. No fastboot in there. So far the only fastboot I have is the
one I built from source during android bootcamp.

You can NOT install inferno from anything but Linux. There are a few
linux tool dependencies in th scripts that can not be satisfied (yet)
on a mac. I am going to see what is possible.

I continue to be amused that all these Java "write once run
everywhere" environments always come with a huge stack of "this CPU,
this OS, this version" programs without which they can not function.
Hmm. All I need with inferno is emu. Maybe inferno can teach them some
things :-)

Finally, it's a linux phone: I keep thinking I ought to be able to do
the install scripts on the phone, not on some other box and download
them. If I can figure out where to plug in an SD card -- it claims to
have one! -- I might just give that a go.

ron

Re: [9fans] Announcing Inferno for Android phones

[Wes Kussmaul]

On Sat, 2011-09-17 at 09:29 -0700, ron minnich wrote:
> If I can figure out where to plug in an SD card -- it claims to
> have one! -- I might just give that a go.

The MicroSD slot in my Droid X is hidden under the battery fwiw.

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

On Sat, Sep 17, 2011 at 10:46 AM, Wes Kussmaul <wes@authentrus.com> wrote:
> On Sat, 2011-09-17 at 09:29 -0700, ron minnich wrote:
>> If I can figure out where to plug in an SD card -- it claims to
>> have one! -- I might just give that a go.
>
> The MicroSD slot in my Droid X is hidden under the battery fwiw.
>
>
>

There's not actually an SD card in the Nexus S, it's apparently just
onboard flash made to look like one.


John

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

On Fri, Sep 16, 2011 at 3:46 PM, andrey mirtchovski
<mirtchovski@gmail.com> wrote:
> John, turn a camera on and film the phone while using it, please!
>
>

Terrible video: http://www.youtube.com/watch?v=dF_-jQc53jw

Some screenshots are available at https://bitbucket.org/floren/inferno/wiki/Home

John

Re: [9fans] Announcing Inferno for Android phones

[Joel Armstrong]

On Sat, Sep 17, 2011 at 9:29 AM, ron minnich <rminnich@gmail.com> wrote:
>
> OK, more data this morning.
>
> Since the cyanogen upgrade, no linux vm I have on OSX/VMWare can
> enumerate the phone over USB. This is a very common problem as
> revealed by any search.
>
> On the one linux box I have, the phone is enumerated as a USB storage.
> There may be some setting I need to reset ... but that box, having
> been turned off since april, seems to have decided it can't do wifi
> more ... so, that's not an option at present!
>
> I did try downloading the android sdk on a clean vmware-based linux
> platform. No fastboot in there. So far the only fastboot I have is the
> one I built from source during android bootcamp.
>
> You can NOT install inferno from anything but Linux. There are a few
> linux tool dependencies in th scripts that can not be satisfied (yet)
> on a mac. I am going to see what is possible.
>
> I continue to be amused that all these Java "write once run
> everywhere" environments always come with a huge stack of "this CPU,
> this OS, this version" programs without which they can not function.
> Hmm. All I need with inferno is emu. Maybe inferno can teach them some
> things :-)
>
> Finally, it's a linux phone: I keep thinking I ought to be able to do
> the install scripts on the phone, not on some other box and download
> them. If I can figure out where to plug in an SD card -- it claims to
> have one! -- I might just give that a go.

If I'm understanding right, you have adb but not fastboot on Mac,
right? As long as your phone is unlocked, you can still install
inferno on the Nexus with just adb by manually flashing the boot
partition. Once you've pushed everything over to /data/inferno, run
the Reflash-Nexus-S.sh script. It should fail at the fastboot step,
but that's fine. Reboot the phone into Cyanogen. Then, from the same
folder as the Reflash-Nexus-S.sh script:
$ adb shell mount -o remount,rw /
$ adb push boot-inferno.img
$ adb shell
Now you'll be in an Android shell.
android$ cat /proc/mtd
This will hopefully give you a list of "mtd" devices and their names.
We only care about the one called "boot."
android$ cat /dev/zero > /dev/mtd/<"boot" device from above>
The zeroing step may not be necessary, but I've never tried flashing
the boot manually without it.
android$ flash_image boot /boot-inferno.img
Then reboot and it should work.
If it's broken, the good news is it's nearly impossible to screw up
the recovery partition. Boot into the bootloader by holding the power
and volume up buttons, then enter the recovery mode and reinstall
Cyanogen.

Re: [9fans] Announcing Inferno for Android phones

[Joel Armstrong]

On Sat, Sep 17, 2011 at 11:02 AM, John Floren <john@jfloren.net> wrote:
>
> Terrible video: http://www.youtube.com/watch?v=dF_-jQc53jw

Pretty good for being shot with a laptop webcam! I think incoming
calls should be working, though, unless I screwed something up between
last week and now (which is likely). The phone won't beep or anything
when a call comes in, but if you open up the dialer application the
status should say "incoming (15555555555)" and the dial button should
change to an answer button, etc.

Side note: I'm attempting to port to my HTC Inspire and by far the
biggest difficulty seems to be just getting the Android source to
compile, especially since you have to rely on mirrors since the
kernel.org attacks. I'm running into the USB enumeration errors as well.

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

joel, on osx, some scripts are not there. I was more concerned about
this than the flash failures because I'm not sure what they do.

sh: mkbootimg: command not found

Where did your version of this one come from? It's nowhere on my machine.

ron

Re: [9fans] Announcing Inferno for Android phones

[Joel Armstrong]

On Sat, Sep 17, 2011 at 1:26 PM, ron minnich <rminnich@gmail.com> wrote:
> joel, on osx, some scripts are not there. I was more concerned about
> this than the flash failures because I'm not sure what they do.
>
> sh: mkbootimg: command not found
>
> Where did your version of this one come from? It's nowhere on my machine.
It comes from the full Android source. I guess it doesn't make sense
for it to be in the SDK. The android git server is dead right now, but
you can fetch a mirror of this specific sub-project at
https://github.com/CyanogenMod/android_system_core/android_system_core.
It's in system/core if you already have an Android source tree.
The Android build system is a pain in general, but especially if you
just want to build a specific executable, so from the cloned
system_core tree:
cd libmincrypt
gcc -I../include/ -o sha.o -c sha.c
mv sha.o ../mkbootimg/
gcc -I../include/ -o mkbootimg -c mkbootimg.c
gcc -o mkbootimg mkbootimg.o sha.o
should do it.

Fastboot is in that tree too if you need a mac version.

Re: [9fans] Announcing Inferno for Android phones

[Joel Armstrong]

> It comes from the full Android source. I guess it doesn't make sense
> for it to be in the SDK. The android git server is dead right now, but
> you can fetch a mirror of this specific sub-project at
> https://github.com/CyanogenMod/android_system_core/android_system_core.
URL correction: it's https://github.com/CyanogenMod/android_system_core.

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

Slight correction:
git clone https://github.com/CyanogenMod/android_system_core
cd android_system_core/
cd libmincrypt/
gcc -I../include/ -o sha.o -c sha.c
mv sha.o ../mkbootimg/
cd ../mkbootimg/
gcc -I../include/ -c mkbootimg.c
gcc -o mkbootimg mkbootimg.o sha.o

Although most of you will get that.

ron

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

A few corrections.

> $ adb shell mount -o remount,rw /
> $ adb push boot-inferno.img

adb push work/boot-inferno.img /boot-inferno.img

> $ adb shell
> Now you'll be in an Android shell.
> android$ cat /proc/mtd
> This will hopefully give you a list of "mtd" devices and their names.
> We only care about the one called "boot."
> android$ cat /dev/zero > /dev/mtd/<"boot" device from above>
> The zeroing step may not be necessary, but I've never tried flashing
> the boot manually without it.

It is hard to believe it is needed. The reason is the erase state of
flash is all 1s, not all zeros. Cat'ing zeros onto the flash is
probably not what you want: it corresponds to an all-bits-burned
state, not an all-bits-cleared state. In this case when you the next
step:

> android$ flash_image boot /boot-inferno.img

The mtd driver will likely erase the flash (to all 1s!) and then burn it :-)


> Then reboot and it should work.

android continues to work. But no inferno at present. I get the nice
white screen, but if I touch it, well, it's blank after a bit.



The parallel_push script did not work that well for me, I had to push
dis/ by hand. I think it would be better to copy the tar file over and
untar it -- would avoid mac silliness with case in the names, as well.

Anyway, I'm booted. I've taken notes and will post them later.

I think I'm still missing lots of stuff so I may just push the tar
file and untar it.

ron

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

OK, I just adb pushed the tar file over and untar'ed and things were
more complete.

So it's up on my nexus-s too. John, would recommend putting OSX and
linux versions of fastboot and mkbootimg into the tar file or on the
web page.

I can tell it's inferno because I hit a button and get instant
response. This is somewhat unlike the java-based experience, although
of course I'm not about to stop using android for good ... just for
most of the time :-)

What would truly be interesting, since we don't need to reboot to
switch modes, would be a button to
do just that ...

All right folks, it's there. Now it's time to contribute! You can see
the limitations, and this is a very hackable system. Somebody want to
write a gps device so I can cat my GPS coords and see if that creates
a number I can dial :-)

ron

Re: [9fans] Announcing Inferno for Android phones

[andrey mirtchovski]

the video shows the OS to be pretty snappy, John. thanks!

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

On Sat, Sep 17, 2011 at 3:05 PM, ron minnich <rminnich@gmail.com> wrote:
> What would truly be interesting, since we don't need to reboot to
> switch modes, would be a button to
> do just that ...
>

It's really easy to switch modes from the shell.

To go from zygote to Inferno:

stop zygote
stop media
start media-inferno
start inferno

To go from inferno to zygote:

stop inferno
stop media-inferno
killall emu-g
start media
start zygote

Adding an appropriate menu item in Inferno would allow you to switch
back to the Java UI easily. Might be a little tougher on the Java side
to go to Inferno, without being connected to a PC.


John

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

On Mon, Sep 19, 2011 at 10:25 AM, John Floren <john@jfloren.net> wrote:
> On Sat, Sep 17, 2011 at 3:05 PM, ron minnich <rminnich@gmail.com> wrote:
>> What would truly be interesting, since we don't need to reboot to
>> switch modes, would be a button to
>> do just that ...
>>
>
> It's really easy to switch modes from the shell.
>
> To go from zygote to Inferno:
>
> stop zygote
> stop media
> start media-inferno
> start inferno
>
> To go from inferno to zygote:
>
> stop inferno
> stop media-inferno
> killall emu-g
> start media
> start zygote
>
> Adding an appropriate menu item in Inferno would allow you to switch
> back to the Java UI easily. Might be a little tougher on the Java side
> to go to Inferno, without being connected to a PC.

yeah, android is so powerful, eh? You can't just exit it.

ron

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

but showing that menu on the inferno side would be very neat.

ron

Re: [9fans] Announcing Inferno for Android phones

[Bruce Ellis]

Are there some clues about what is needed in a compatible phone?
Simply unlocked android or any other niggles? The phones available
from China are usually based on a big seller (and come off the same
hardware production line). One I have is based on the nokia E5 (and is
called the Wank E5). If I hurry I can throw around a box of new phones
at IWP9.

brucee

On 20 September 2011 03:29, ron minnich <rminnich@gmail.com> wrote:
> but showing that menu on the inferno side would be very neat.
>
> ron

--
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)

Re: [9fans] Announcing Inferno for Android phones

[Steve Simon]

"One I have is based on the nokia E5 (and is called the Wank E5)"

surely a forutune?

-Steve

Re: [9fans] Announcing Inferno for Android phones

[Joseph Stewart]

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Reminds me of some Chinese PC's we evaluated many years ago. One model was
called "My Personal Woody"...

On Mon, Sep 19, 2011 at 5:49 PM, Bruce Ellis <bruce.ellis@gmail.com> wrote:

> Are there some clues about what is needed in a compatible phone?
> Simply unlocked android or any other niggles? The phones available
> from China are usually based on a big seller (and come off the same
> hardware production line). One I have is based on the nokia E5 (and is
> called the Wank E5). If I hurry I can throw around a box of new phones
> at IWP9.
>
> brucee
>
> On 20 September 2011 03:29, ron minnich <rminnich@gmail.com> wrote:
> > but showing that menu on the inferno side would be very neat.
> >
> > ron
>
> --
> Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)
>
>

[-- Attachment #2: Type: text/html, Size: 1209 bytes --]

Re: [9fans] Announcing Inferno for Android phones

[hiro]

These high resolution displays in current mainstream smartphones are
worth their bucks in my view!.
But if the china phones are available with 800x480 and under 100 Euros
I might reconsider...

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

Unlocked android, basically, but I think it's best if you can run
Cyanogenmod on it. That's what we've used for all of our testing,
because it's available for a lot of phones and provides a reasonably
similar environment across all of them.

Since the E5 is not an Android phone, you probably won't have much
luck with that one. See if there are any other Wank-ers that can run
Android.


John

On Mon, Sep 19, 2011 at 2:49 PM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
> Are there some clues about what is needed in a compatible phone?
> Simply unlocked android or any other niggles? The phones available
> from China are usually based on a big seller (and come off the same
> hardware production line). One I have is based on the nokia E5 (and is
> called the Wank E5). If I hurry I can throw around a box of new phones
> at IWP9.
>
> brucee
>
> On 20 September 2011 03:29, ron minnich <rminnich@gmail.com> wrote:
>> but showing that menu on the inferno side would be very neat.
>>
>> ron
>
> --
> Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)
>
>

Re: [9fans] Announcing Inferno for Android phones

[Ethan Grammatikidis]

On Sat, 17 Sep 2011 11:26:49 -0700
Joel Armstrong <joelcarmstrong@gmail.com> wrote:

> The phone won't beep or anything

Does it not have audio?

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

On Wed, Sep 21, 2011 at 3:06 PM, Ethan Grammatikidis
<eekee57@fastmail.fm> wrote:
> On Sat, 17 Sep 2011 11:26:49 -0700
> Joel Armstrong <joelcarmstrong@gmail.com> wrote:
>
>> The phone won't beep or anything
>
> Does it not have audio?
>
>

I'm not sure I understand the point of your question, but I'm not sure
you understand the issues surrounding your question :-)

I mean, of course it has audio. It's a phone.

ron

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

On Wed, Sep 21, 2011 at 3:06 PM, Ethan Grammatikidis
<eekee57@fastmail.fm> wrote:
> On Sat, 17 Sep 2011 11:26:49 -0700
> Joel Armstrong <joelcarmstrong@gmail.com> wrote:
>
>> The phone won't beep or anything
>
> Does it not have audio?
>
>

I wasn't very involved in the audio side of things, but as I recall
there are separate controls for audio coming from/going to the cell
chip vs. audio that the user deals with. We have the cell audio
working so you can make a phone call and talk to someone. We haven't
built a /dev/audio yet, though, so there are no "notification" sounds.


John

Re: [9fans] Announcing Inferno for Android phones

[Bruce Ellis]

The phones that I have worked on have *INSANE* audio routing. Qudos to
he who conquers.

A phone call is a damned good start though.

brucee

On 22 September 2011 08:14, John Floren <john@jfloren.net> wrote:
> On Wed, Sep 21, 2011 at 3:06 PM, Ethan Grammatikidis
> <eekee57@fastmail.fm> wrote:
>> On Sat, 17 Sep 2011 11:26:49 -0700
>> Joel Armstrong <joelcarmstrong@gmail.com> wrote:
>>
>>> The phone won't beep or anything
>>
>> Does it not have audio?
>>
>>
>
> I wasn't very involved in the audio side of things, but as I recall
> there are separate controls for audio coming from/going to the cell
> chip vs. audio that the user deals with. We have the cell audio
> working so you can make a phone call and talk to someone. We haven't
> built a /dev/audio yet, though, so there are no "notification" sounds.
>
>
> John
>
>



--
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)

Re: [9fans] Announcing Inferno for Android phones

[Ethan Grammatikidis]

On Wed, 21 Sep 2011 15:14:43 -0700
John Floren <john@jfloren.net> wrote:

> On Wed, Sep 21, 2011 at 3:06 PM, Ethan Grammatikidis
> <eekee57@fastmail.fm> wrote:
> > On Sat, 17 Sep 2011 11:26:49 -0700
> > Joel Armstrong <joelcarmstrong@gmail.com> wrote:
> >
> >> The phone won't beep or anything
> >
> > Does it not have audio?
> >
> >
>
> I wasn't very involved in the audio side of things, but as I recall
> there are separate controls for audio coming from/going to the cell
> chip vs. audio that the user deals with. We have the cell audio
> working so you can make a phone call and talk to someone. We haven't
> built a /dev/audio yet, though, so there are no "notification" sounds.

Ah *nods* this is what I wanted to know, thanks. I hope it's not as
insane as Bruce mentions.


Also Ron: You were perfectly right.

/me intentionally fails to elaborate on that.

Re: [9fans] Announcing Inferno for Android phones

[Ethan Grammatikidis]

On Tue, 20 Sep 2011 07:49:57 +1000
Bruce Ellis <bruce.ellis@gmail.com> wrote:

> Are there some clues about what is needed in a compatible phone?
> Simply unlocked android or any other niggles? The phones available
> from China are usually based on a big seller (and come off the same
> hardware production line). One I have is based on the nokia E5 (and is
> called the Wank E5). If I hurry I can throw around a box of new phones
> at IWP9.

I probably shouldn't ask, but how much would they be? Once you've found
a suitable model of course. I won't be at Madrid, but I imagine postage
within the EU would be reasonable. (I'm in Britain.) I'm thinking I'd
much rather have a model other people are using too, rather than
attempt to port to another model which might be quite different.

Re: [9fans] Announcing Inferno for Android phones

[Bruce Ellis]

The Wank E5 was AU$50. The only disappointing thing was that they took
the Wank tagging off the case, though it is still unashamed in the
battery compartment. I'm not sure how much fun It will be at the
airport with a dozen phones - but if I check them they'll get lost at
Heathrow.

brucee

On 22 September 2011 20:11, Ethan Grammatikidis <eekee57@fastmail.fm> wrote:
> On Tue, 20 Sep 2011 07:49:57 +1000
> Bruce Ellis <bruce.ellis@gmail.com> wrote:
>
>> Are there some clues about what is needed in a compatible phone?
>> Simply unlocked android or any other niggles? The phones available
>> from China are usually based on a big seller (and come off the same
>> hardware production line). One I have is based on the nokia E5 (and is
>> called the Wank E5). If I hurry I can throw around a box of new phones
>> at IWP9.
>
> I probably shouldn't ask, but how much would they be? Once you've found
> a suitable model of course. I won't be at Madrid, but I imagine postage
> within the EU would be reasonable. (I'm in Britain.) I'm thinking I'd
> much rather have a model other people are using too, rather than
> attempt to port to another model which might be quite different.
>
>



--
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)

Re: [9fans] Announcing Inferno for Android phones

[Ethan Grammatikidis]

On Thu, 22 Sep 2011 22:30:56 +1000
Bruce Ellis <bruce.ellis@gmail.com> wrote:

> The Wank E5 was AU$50. The only disappointing thing was that they took
> the Wank tagging off the case, though it is still unashamed in the
> battery compartment. I'm not sure how much fun It will be at the
> airport with a dozen phones - but if I check them they'll get lost at
> Heathrow.

Wot? Don't want it without the label! Nah, seriously, that's a whole
lot better than the £200 I just saw for the HTC Wildfire which was
recommended to me as a cheap Android phone. I would like one if you're
all right bringing/posting it.

Re: [9fans] Announcing Inferno for Android phones

[Richard Miller]

>> The Wank E5 was AU$50.

Why is it that I can't quite summon up the courage to do a
google search for "wank phone"?

Re: [9fans] Announcing Inferno for Android phones

[erik quanstrom]

On Fri Sep 23 09:41:43 EDT 2011, 9fans@hamnavoe.com wrote:
> >> The Wank E5 was AU$50.
>
> Why is it that I can't quite summon up the courage to do a
> google search for "wank phone"?

that might be a mistake but searching for "wank e5" turned up
nothing more offensive than el reg.

http://www.mobino1.com/product-1341.html

- erik

Re: [9fans] Announcing Inferno for Android phones

[Mathieu Lonjaret]

Because deep inside you know it's just an elaborate ruse from brucee.

On Fri, Sep 23, 2011 at 3:40 PM, Richard Miller <9fans@hamnavoe.com> wrote:
>>> The Wank E5 was AU$50.
>
> Why is it that I can't quite summon up the courage to do a
> google search for "wank phone"?
>
>
>

Re: [9fans] Announcing Inferno for Android phones

[Brian L. Stuart]

> >> The Wank E5 was AU$50.
>
> Why is it that I can't quite summon up the courage to do a
> google search for "wank phone"?

Because it will cost you $4.99 a minute?

Re: [9fans] Announcing Inferno for Android phones

[Gorka Guardiola]

Turn safe search on first.

http://www.amokbuy.com/928-wank-e5-wifi-mobile-phone.html

On Fri, Sep 23, 2011 at 3:55 PM, Brian L. Stuart <blstuart@bellsouth.net> wrote:
>> >> The Wank E5 was AU$50.
>>
>> Why is it that I can't quite summon up the courage to do a
>> google search for "wank phone"?
>
> Because it will cost you $4.99 a minute?
>
>
>



--
- curiosity sKilled the cat

Re: [9fans] Announcing Inferno for Android phones

[Jeff Sickel]

On Sep 23, 2011, at 9:05 AM, Gorka Guardiola wrote:

> Turn safe search on first.

Or just go to the register's search field first.  They've got a nice little headline, "Forget the Jesus Phone, here's the Rude Phone".

Re: [9fans] Announcing Inferno for Android phones

[Bruce Ellis]

Hey!

Hold on ... I wouldn't believe me either.

On 23 September 2011 23:51, Mathieu Lonjaret <mathieu.lonjaret@gmail.com> wrote:
> Because deep inside you know it's just an elaborate ruse from brucee.
>
> On Fri, Sep 23, 2011 at 3:40 PM, Richard Miller <9fans@hamnavoe.com> wrote:
>>>> The Wank E5 was AU$50.
>>
>> Why is it that I can't quite summon up the courage to do a
>> google search for "wank phone"?
>

--
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)

Re: [9fans] Announcing Inferno for Android phones

[Tharaneedharan Vilwanathan]

Hi All,

Would this phone be able to run inferno?

"Samsung Google Nexus S I9023 Unlocked GSM Android Phone With 4"
Touchscreen, Dual-Cameras, WiFi & More!"

http://1saleaday.com/wireless/?CID=173477&AFID=178621

Its on sale today. Price $299. Does it make sense?

Thanks
dharani

On Fri, Sep 23, 2011 at 4:14 PM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
> Hey!
>
> Hold on ... I wouldn't believe me either.
>
> On 23 September 2011 23:51, Mathieu Lonjaret <mathieu.lonjaret@gmail.com> wrote:
>> Because deep inside you know it's just an elaborate ruse from brucee.
>>
>> On Fri, Sep 23, 2011 at 3:40 PM, Richard Miller <9fans@hamnavoe.com> wrote:
>>>>> The Wank E5 was AU$50.
>>>
>>> Why is it that I can't quite summon up the courage to do a
>>> google search for "wank phone"?
>>
>
> --
> Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)
>
>

Re: [9fans] Announcing Inferno for Android phones

[Ethan Grammatikidis]

On Mon, 26 Sep 2011 00:26:19 -0700
Tharaneedharan Vilwanathan <vdharani@gmail.com> wrote:

> Hi All,
>
> Would this phone be able to run inferno?
>
> "Samsung Google Nexus S I9023 Unlocked GSM Android Phone With 4"
> Touchscreen, Dual-Cameras, WiFi & More!"

It's running on at least one other Nexus S already:
http://9fans.net/archive/2011/09/356

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

That's the phone we used to develop, so yes.

On Mon, Sep 26, 2011 at 12:26 AM, Tharaneedharan Vilwanathan
<vdharani@gmail.com> wrote:
> Hi All,
>
> Would this phone be able to run inferno?
>
> "Samsung Google Nexus S I9023 Unlocked GSM Android Phone With 4"
> Touchscreen, Dual-Cameras, WiFi & More!"
>
> http://1saleaday.com/wireless/?CID=173477&AFID=178621
>
> Its on sale today. Price $299. Does it make sense?
>
> Thanks
> dharani
>
> On Fri, Sep 23, 2011 at 4:14 PM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
>> Hey!
>>
>> Hold on ... I wouldn't believe me either.
>>
>> On 23 September 2011 23:51, Mathieu Lonjaret <mathieu.lonjaret@gmail.com> wrote:
>>> Because deep inside you know it's just an elaborate ruse from brucee.
>>>
>>> On Fri, Sep 23, 2011 at 3:40 PM, Richard Miller <9fans@hamnavoe.com> wrote:
>>>>>> The Wank E5 was AU$50.
>>>>
>>>> Why is it that I can't quite summon up the courage to do a
>>>> google search for "wank phone"?
>>>
>>
>> --
>> Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)
>>
>>
>
>

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

Update: We now have a sort-of-working audio device in there. Sort of.
You can bind '#A' /dev and write to /dev/audio, 44.1KHz 16 bit PCM
audio will play fine. It'll also attempt to record 16KHZ 16 bit PCM,
but it comes out choppy. All the code is basically a crude hack from
the OpenSL ES example code.

Anyone with experience in OpenSL is encouraged to submit patches; I'm
feeling around in the dark here :-)


John

Re: [9fans] Announcing Inferno for Android phones

[Lyndon Nerenberg (VE6BBM/VE7TFX)]

> As of today, we have Inferno running on the Nexus S and the Nook
> Color.

And naturally, the Nexus S has been discontinued.  At least, I can't
get my hands on one anywhere in Canada.  Anyone have a souce for an
unlocked Nexus S (preferably from a US online dealer, for reasons too
absurd to go into).

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

https://negrielectronics.com/google-nexus-s-i9020a-white-8503g-unlocked.html

On Fri, Nov 4, 2011 at 2:45 PM, Lyndon Nerenberg (VE6BBM/VE7TFX)
<lyndon@orthanc.ca> wrote:
>> As of today, we have Inferno running on the Nexus S and the Nook
>> Color.
>
> And naturally, the Nexus S has been discontinued.  At least, I can't
> get my hands on one anywhere in Canada.  Anyone have a souce for an
> unlocked Nexus S (preferably from a US online dealer, for reasons too
> absurd to go into).
>
>
>

Re: [9fans] Announcing Inferno for Android phones

[Masen Marshall]

[-- Attachment #1: Type: text/plain, Size: 704 bytes --]

You might want to check out eBay, usually a good way to pick up cheaper dev
hardware.

On Fri, Nov 4, 2011 at 4:55 PM, John Floren <john@jfloren.net> wrote:

>
> https://negrielectronics.com/google-nexus-s-i9020a-white-8503g-unlocked.html
>
> On Fri, Nov 4, 2011 at 2:45 PM, Lyndon Nerenberg (VE6BBM/VE7TFX)
> <lyndon@orthanc.ca> wrote:
> >> As of today, we have Inferno running on the Nexus S and the Nook
> >> Color.
> >
> > And naturally, the Nexus S has been discontinued.  At least, I can't
> > get my hands on one anywhere in Canada.  Anyone have a souce for an
> > unlocked Nexus S (preferably from a US online dealer, for reasons too
> > absurd to go into).
> >
> >
> >
>
>

[-- Attachment #2: Type: text/html, Size: 1201 bytes --]

Re: [9fans] Announcing Inferno for Android phones

[Ethan Grammatikidis]

On Fri, 30 Sep 2011 09:02:52 +1000
Bruce Ellis <bruce.ellis@gmail.com> wrote:

> next target
>
> http://www.eetimes.com/electronics-news/4228591/Dick-Tracy-watch-ARM-TechCon

Got to be done! :}

Re: [9fans] Announcing Inferno for Android phones

[Bruce Ellis]

next target

http://www.eetimes.com/electronics-news/4228591/Dick-Tracy-watch-ARM-TechCon

--
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

On Wed, Sep 28, 2011 at 12:53 PM, John Floren <john@jfloren.net> wrote:
> On Wed, Sep 28, 2011 at 7:43 AM, 252608386 <252608386@qq.com> wrote:
>> i build the floren-inferno with cyanogen-mod source code(htc hero)
>> and i got the error,why?
>> agcc -c -O -I/media/sdb1/inferno/floren-inferno/Android/arm/include
>> -I/media/sdb1/inferno/floren-inferno/include -DLINUX_ARM -DINFERNO
>> -I/media/sdb1/inferno/floren-inferno/include/freetype -I. freetype.c
>> ........
>> /media/sdb1/android/bionic/libc/include/stdlib.h:169: error: expected ')'
>> before '*' token
>> /media/sdb1/android/bionic/libc/include/stdlib.h:170: error: expected ')'
>> before '*' token
>> /media/sdb1/android/bionic/libc/include/stdlib.h:173: error: expected
>> declaration specifiers or '...' before 'wchar_t'
>> /media/sdb1/android/bionic/libc/include/stdlib.h:174: error: expected ';',
>> ',' or ')' before '*' token
>> In file included from
>> /media/sdb1/inferno/floren-inferno/Android/arm/include/lib9.h:17,
>>
>
> Please check out
> https://bitbucket.org/floren/inferno/wiki/CompilingInferno,
> specifically the bit about changing stdlib.h. It's not a pretty way to
> do things, but it works. Once you make the change, if you intend to do
> a "repo sync" later, you'll need to change to the bionic directory and
> do a "git stash" to get rid of your changes, or else repo sync will
> fail. You can then change it back later.
>
>
> John
>

Anyone running Inferno on Android may also find this useful:
https://bitbucket.org/floren/inferno/wiki/HellaphoneManual


John

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

On Wed, Sep 28, 2011 at 7:43 AM, 252608386 <252608386@qq.com> wrote:
> i build the floren-inferno with cyanogen-mod source code(htc hero)
> and i got the error,why?
> agcc -c -O -I/media/sdb1/inferno/floren-inferno/Android/arm/include
> -I/media/sdb1/inferno/floren-inferno/include -DLINUX_ARM -DINFERNO
> -I/media/sdb1/inferno/floren-inferno/include/freetype -I. freetype.c
> ........
> /media/sdb1/android/bionic/libc/include/stdlib.h:169: error: expected ')'
> before '*' token
> /media/sdb1/android/bionic/libc/include/stdlib.h:170: error: expected ')'
> before '*' token
> /media/sdb1/android/bionic/libc/include/stdlib.h:173: error: expected
> declaration specifiers or '...' before 'wchar_t'
> /media/sdb1/android/bionic/libc/include/stdlib.h:174: error: expected ';',
> ',' or ')' before '*' token
> In file included from
> /media/sdb1/inferno/floren-inferno/Android/arm/include/lib9.h:17,
>

Please check out
https://bitbucket.org/floren/inferno/wiki/CompilingInferno,
specifically the bit about changing stdlib.h. It's not a pretty way to
do things, but it works. Once you make the change, if you intend to do
a "repo sync" later, you'll need to change to the bionic directory and
do a "git stash" to get rid of your changes, or else repo sync will
fail. You can then change it back later.


John

Re: [9fans] Announcing Inferno for Android phones

[JS enter]

On Sep 28, 11:13 pm, j...@jfloren.net (John Floren) wrote:
> On Wed, Sep 28, 2011 at 7:43 AM, 252608386 <252608...@qq.com> wrote:
> > i build the floren-inferno with cyanogen-mod source code(htc hero)
> > and i got the error,why?
> > agcc -c -O -I/media/sdb1/inferno/floren-inferno/Android/arm/include
> > -I/media/sdb1/inferno/floren-inferno/include -DLINUX_ARM -DINFERNO
> > -I/media/sdb1/inferno/floren-inferno/include/freetype -I. freetype.c
> > ........
> > /media/sdb1/android/bionic/libc/include/stdlib.h:169: error: expected ')'
> > before '*' token
> > /media/sdb1/android/bionic/libc/include/stdlib.h:170: error: expected ')'
> > before '*' token
> > /media/sdb1/android/bionic/libc/include/stdlib.h:173: error: expected
> > declaration specifiers or '...' before 'wchar_t'
> > /media/sdb1/android/bionic/libc/include/stdlib.h:174: error: expected ';',
> > ',' or ')' before '*' token
> > In file included from
> > /media/sdb1/inferno/floren-inferno/Android/arm/include/lib9.h:17,
>
> I think I recognize this error. I will post more complete building
> instructions when I get to work.
>
> John

thanks and wait.

I build this on BackTrack5,and build the cyanogen-mod for HTC hero
successfully.
also compile Inferno x86 tools.

this error occurs when build the Inferno-Android.

I also google the problem, somebody said "That's clearly a truecrypt
bug."

sorry for my pool English.

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

On Wed, Sep 28, 2011 at 7:43 AM, 252608386 <252608386@qq.com> wrote:
> i build the floren-inferno with cyanogen-mod source code(htc hero)
> and i got the error,why?
> agcc -c -O -I/media/sdb1/inferno/floren-inferno/Android/arm/include
> -I/media/sdb1/inferno/floren-inferno/include -DLINUX_ARM -DINFERNO
> -I/media/sdb1/inferno/floren-inferno/include/freetype -I. freetype.c
> ........
> /media/sdb1/android/bionic/libc/include/stdlib.h:169: error: expected ')'
> before '*' token
> /media/sdb1/android/bionic/libc/include/stdlib.h:170: error: expected ')'
> before '*' token
> /media/sdb1/android/bionic/libc/include/stdlib.h:173: error: expected
> declaration specifiers or '...' before 'wchar_t'
> /media/sdb1/android/bionic/libc/include/stdlib.h:174: error: expected ';',
> ',' or ')' before '*' token
> In file included from
> /media/sdb1/inferno/floren-inferno/Android/arm/include/lib9.h:17,
>

I think I recognize this error. I will post more complete building
instructions when I get to work.

John

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

you need to dig a lot more than that!

What distro? What OS? did you look in the file to see what was going on?

If something this simple stops you this much, this may not be the
right project for you to take on.

ron

[9fans] Announcing Inferno for Android phones

[252608386]

[-- Attachment #1: Type: text/plain, Size: 810 bytes --]

i build the floren-inferno with cyanogen-mod source code(htc hero)
and i got the error,why?


agcc -c -O -I/media/sdb1/inferno/floren-inferno/Android/arm/include -I/media/sdb1/inferno/floren-inferno/include -DLINUX_ARM -DINFERNO -I/media/sdb1/inferno/floren-inferno/include/freetype -I. freetype.c

........
/media/sdb1/android/bionic/libc/include/stdlib.h:169: error: expected ')' before '*' token
/media/sdb1/android/bionic/libc/include/stdlib.h:170: error: expected ')' before '*' token
/media/sdb1/android/bionic/libc/include/stdlib.h:173: error: expected declaration specifiers or '...' before 'wchar_t'
/media/sdb1/android/bionic/libc/include/stdlib.h:174: error: expected ';', ',' or ')' before '*' token
In file included from /media/sdb1/inferno/floren-inferno/Android/arm/include/lib9.h:17,

[-- Attachment #2: Type: text/html, Size: 939 bytes --]

Re: [9fans] Announcing Inferno for Android phones

[Bruce Ellis]

i enjoy working with a framebuffer. but i guess cause i have the code.
the secret phone i worked on was inferno on top of plan9 (arm based).
you could lazily run rio and grab the "framebuffer" that you get from
/dev/screen for each window. the rendering code uses that thru rio.
and the graphics manager (which they never got) ran on that. works
well except i only have two of them and hardware is adhoc and bad, and
most importantly the battery life is bad. i'm taking tiger for walkies
so call it ... i'll give away the fb code, unless someone wants to pay
for it (secret meeting in madrid).

brucee

On 17 September 2011 13:40, ron minnich <rminnich@gmail.com> wrote:
> And the docs are the usual inaccurate awful android stuff. I'm
> struggling right now just to get the fastboot step done. These tools
> are just terrible, and the iffy descriptions don't help much. I guess
> the churn in the android tools is such that consistency is not the
> most visible result.
>
> I'm taking notes which I hope will help others.
>
> ron
>
>



--
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

And the docs are the usual inaccurate awful android stuff. I'm
struggling right now just to get the fastboot step done. These tools
are just terrible, and the iffy descriptions don't help much. I guess
the churn in the android tools is such that consistency is not the
most visible result.

I'm taking notes which I hope will help others.

ron

Re: [9fans] Announcing Inferno for Android phones

[ron minnich]

On Fri, Sep 16, 2011 at 7:48 PM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
> did you stick with tk (seems so). a sad relic.

you gotta start somewhere. The goal is to get this into people's hands
and hope we make the hacking easy enough for people to do some things.

btw the control of things is as you might expect, via commands echoed
to ctl files.

ron

Re: [9fans] Announcing Inferno for Android phones

[Bruce Ellis]

did you stick with tk (seems so). a sad relic.

brucee

On 17 September 2011 12:46, John Floren <john@jfloren.net> wrote:
> By the way, it's pretty easy to try things out while the phone is
> running. Just push over /data/inferno, then you should be able to do
> something like this:
>
> % stop zygote # this kills off the java UI
> % /data/inferno/Android/arm/bin/emu-g
> ; wm/wm
>
> The README.android file should tell you all you need to know about
> managing the radio. Oh, and if you use the network, it's a good idea
> to do a "setprop net.dns1 8.8.8.8"  (at the Android prompt, not in
> Inferno) first, otherwise DNS doesn't seem to work right. When you're
> sick of testing inferno, just Ctrl-C the process and run "start
> zygote".
>
> I've found a few things that need to be fixed and will be working on
> them Monday. However, if you just want to get it running on your own
> phone, you should be able to do it. You'll need to have the full
> Android build environment set up, not just the SDK, and you'll need to
> have adb in your path. You may also need to put "agcc" (provided in
> the repo) into your path in order to actually build Inferno. I believe
> README.android has a summary of how to build Inferno yourself down at
> the bottom.
>
>
> John
>
> On Fri, Sep 16, 2011 at 7:40 PM, John Floren <john@jfloren.net> wrote:
>> We've only had one device with an actual radio in it, so we haven't
>> been able to test on anything but the Nexus S, but there's probably a
>> total of 100 lines of device-specific code. Mostly, you have to figure
>> out:
>>
>> 1. The screen dimensions and the color depth
>> 2. Which devices are for the touchscreen, which are for the buttons
>>
>> emu/port/main.c and emu/Android/screen.c contain all the
>> device-specific code, I think. If there is any justice, the radio
>> interface will be the same--we talk to "rild", the radio daemon,
>> rather than directly with the hardware.
>>
>> John
>>
>> On Fri, Sep 16, 2011 at 7:35 PM, Devon H. O'Dell <devon.odell@gmail.com> wrote:
>>> How difficult is it to get specs and port this to other android devices? I'd
>>> love to run this on my motorola droid if I could get all the radios working.
>>>
>>> --dho (via said droid)
>>>
>>> On Sep 16, 2011 10:25 PM, "paul.a.lalonde@gmail.com"
>>> <paul.a.lalonde@gmail.com> wrote:
>>>> For all these plan9ish things on OSX I run a case-sensitive file-system in
>>>> a file; just use the Disk Utility to make one and then mount it. I link mine
>>>> into my home directory and use it for all case-sensitive apps.
>>>> Paul
>>>>
>>>> Sent from my HTC Inspire™ 4G on AT&T
>>>>
>>>> ----- Reply message -----
>>>> From: "John Floren" <john@jfloren.net>
>>>> To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>,
>>>> <inferno-list@vitanuova.com>
>>>> Subject: [9fans] Announcing Inferno for Android phones
>>>> Date: Fri, Sep 16, 2011 7:01 pm
>>>>
>>>>
>>>> One caveat that I just came across: If you're trying to set up your
>>>> phone from Mac OS X, it's quite possible that the case-insensitive
>>>> filesystem will bite you. We have two directories at the same level,
>>>> named "android" and "Android". If you do an adb push from OS X,
>>>> they'll both end up in a directory called "android". Here's how you
>>>> can fix it:
>>>>
>>>> (run adb shell)
>>>> # mkdir /data/inferno/Android
>>>> # mv /data/inferno/android/arm /data/inferno/Android/
>>>>
>>>> There may be other problems lurking, but I'm pretty sure all of the
>>>> stuff Inferno needs is all lowercase.
>>>>
>>>>
>>>> John
>>>>
>>>> On Fri, Sep 16, 2011 at 3:23 PM, John Floren <john@jfloren.net> wrote:
>>>>> We would like to announce the availability of Inferno for Android
>>>>> phones. Because our slogan is "If it ain't broke, break it", we
>>>>> decided to replace the Java stack on Android phones with
>>>>> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
>>>>> to keep with the Inferno theme, but then we realized we're in Northern
>>>>> California and the change was obvious.
>>>>>
>>>>> The Hellaphone runs Inferno directly on top of the basic Linux layer
>>>>> provided by Android. We do not even allow the Java system to
>>>>> start. Instead, emu draws directly to the Linux framebuffer (thanks,
>>>>> Andrey, for the initial code!) and treats the touchscreen like a
>>>>> one-button mouse. Because the Java environment doesn't start, it only
>>>>> takes about 10 seconds to go from power off to a fully-booted Inferno
>>>>> environment.
>>>>>
>>>>> As of today, we have Inferno running on the Nexus S and the Nook
>>>>> Color. It should also run on the Android emulator, but we haven't
>>>>> tested that in a long time. The cell radio is supported, at least on
>>>>> the Nexus S (the only actual phone we've had), so you can make phone
>>>>> calls, send texts, and use the data network.
>>>>>
>>>>> The Inferno window manager has been re-worked with cell phone use in
>>>>> mind. Windows are automatically sized to fill the whole screen. The
>>>>> menu has been moved to the top and the menu items have been made
>>>>> significantly larger. Physical buttons on the phone are now used to do
>>>>> many common tasks:
>>>>>
>>>>>    (these keys are for the Nexus S, different bindings are used for
>>>>> the Nook, which has different keys available)
>>>>>    * Back: Close the current window
>>>>>    * Menu: Toggle the onscreen keyboard
>>>>>    * Home: Minimize the current window
>>>>>    * Power: Turn off the screen
>>>>>    * Power+Volume Up: Open the screen brightness widget
>>>>>    * Power+Volume Down: Turn off the phone
>>>>>    * Power+Home: Restart Inferno
>>>>>
>>>>> Installation is reasonably simple. You'll need the Android SDK
>>>>> (http://developer.android.com/sdk/index.html), with the platform-tools
>>>>> package installed for the adb and fastboot utilities. We also strongly
>>>>> recommend installing CyanogenMod on your phone before
>>>>> proceeding--that's what we use to test.
>>>>>
>>>>> First, make absolutely sure you have the "adb" and "fastboot"
>>>>> commands in your path--see the previous paragraph regarding the
>>>>> SDK and try running "adb" to be sure. Download the tarball from
>>>>> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
>>>>> unpack it in your root. You should end up with a /data/inferno
>>>>> directory (we put it there because of the Inferno build
>>>>> process). Then, go to the /data/inferno/android directory and run
>>>>> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
>>>>> Reflash-Nook-Color.sh if you have a Nook). This will
>>>>> automatically set up the phone to boot into either Inferno or the
>>>>> regular Java environment--during bootup, the screen will go solid
>>>>> white; if you touch the screen at this point, it will boot into
>>>>> the regular Android environment, otherwise it will timeout and go
>>>>> to Inferno. However, at this point you're not yet ready to boot
>>>>> into Inferno, so reboot the phone and touch the screen to go into
>>>>> the regular Android UI. The final task is to run the command "cd
>>>>> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
>>>>> Inferno, and you're ready to go.
>>>>>
>>>>> You can also clone the repository
>>>>> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
>>>>> is a significant effort. I do not recommend it if you wish to simply
>>>>> try the system, but if you want to do development you should get the
>>>>> repository.
>>>>>
>>>>> Disclaimer: If you break your phone, it's not our fault. Don't email
>>>>> us, don't come knocking on our door, and don't call us--oh wait, you
>>>>> won't be able to do that anyway, your phone is broken!
>>>>>
>>>>> Credit where credit is due: Ron Minnich came up with the initial
>>>>> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
>>>>> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
>>>>> lion's share of the work of making Inferno into a usable cell phone
>>>>> OS--no small feat, considering that neither had any Limbo or Inferno
>>>>> experience before the start of the summer! They re-wrote the UI,
>>>>> puzzled out the undocumented cell radio interface, figured out audio,
>>>>> worked to make Inferno more portable across phones, and generally
>>>>> figured out how to make Inferno and the Android kernel coexist
>>>>> peacefully. Andy Jones, another intern, also did some very early work
>>>>> with Android that helped us figure out the Android init process and
>>>>> how to build for Android. I took care of getting Inferno running on
>>>>> the phone in the first place and have been adding things occasionally
>>>>> since then. We would also like to thank Andrey Mirtchovski for
>>>>> providing the OLPC framebuffer code (which ported to the Android
>>>>> phones relatively easily), and of course Charles Forsyth for keeping
>>>>> the Inferno torch lit all these years (and helping me figure out some
>>>>> puzzling problems throughout the summer)!
>>>>>
>>>>
>>>
>>
>
>



-- 
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)

Re: [9fans] Announcing Inferno for Android phones

[Bruce Ellis]

One Inferno phone I have from China has two sims and a TV receiver.
And DIY documentation.

brucee

On 17 September 2011 12:40, John Floren <john@jfloren.net> wrote:
> We've only had one device with an actual radio in it, so we haven't
> been able to test on anything but the Nexus S, but there's probably a
> total of 100 lines of device-specific code. Mostly, you have to figure
> out:
>
> 1. The screen dimensions and the color depth
> 2. Which devices are for the touchscreen, which are for the buttons
>
> emu/port/main.c and emu/Android/screen.c contain all the
> device-specific code, I think. If there is any justice, the radio
> interface will be the same--we talk to "rild", the radio daemon,
> rather than directly with the hardware.
>
> John
>
> On Fri, Sep 16, 2011 at 7:35 PM, Devon H. O'Dell <devon.odell@gmail.com> wrote:
>> How difficult is it to get specs and port this to other android devices? I'd
>> love to run this on my motorola droid if I could get all the radios working.
>>
>> --dho (via said droid)
>>
>> On Sep 16, 2011 10:25 PM, "paul.a.lalonde@gmail.com"
>> <paul.a.lalonde@gmail.com> wrote:
>>> For all these plan9ish things on OSX I run a case-sensitive file-system in
>>> a file; just use the Disk Utility to make one and then mount it. I link mine
>>> into my home directory and use it for all case-sensitive apps.
>>> Paul
>>>
>>> Sent from my HTC Inspire™ 4G on AT&T
>>>
>>> ----- Reply message -----
>>> From: "John Floren" <john@jfloren.net>
>>> To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>,
>>> <inferno-list@vitanuova.com>
>>> Subject: [9fans] Announcing Inferno for Android phones
>>> Date: Fri, Sep 16, 2011 7:01 pm
>>>
>>>
>>> One caveat that I just came across: If you're trying to set up your
>>> phone from Mac OS X, it's quite possible that the case-insensitive
>>> filesystem will bite you. We have two directories at the same level,
>>> named "android" and "Android". If you do an adb push from OS X,
>>> they'll both end up in a directory called "android". Here's how you
>>> can fix it:
>>>
>>> (run adb shell)
>>> # mkdir /data/inferno/Android
>>> # mv /data/inferno/android/arm /data/inferno/Android/
>>>
>>> There may be other problems lurking, but I'm pretty sure all of the
>>> stuff Inferno needs is all lowercase.
>>>
>>>
>>> John
>>>
>>> On Fri, Sep 16, 2011 at 3:23 PM, John Floren <john@jfloren.net> wrote:
>>>> We would like to announce the availability of Inferno for Android
>>>> phones. Because our slogan is "If it ain't broke, break it", we
>>>> decided to replace the Java stack on Android phones with
>>>> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
>>>> to keep with the Inferno theme, but then we realized we're in Northern
>>>> California and the change was obvious.
>>>>
>>>> The Hellaphone runs Inferno directly on top of the basic Linux layer
>>>> provided by Android. We do not even allow the Java system to
>>>> start. Instead, emu draws directly to the Linux framebuffer (thanks,
>>>> Andrey, for the initial code!) and treats the touchscreen like a
>>>> one-button mouse. Because the Java environment doesn't start, it only
>>>> takes about 10 seconds to go from power off to a fully-booted Inferno
>>>> environment.
>>>>
>>>> As of today, we have Inferno running on the Nexus S and the Nook
>>>> Color. It should also run on the Android emulator, but we haven't
>>>> tested that in a long time. The cell radio is supported, at least on
>>>> the Nexus S (the only actual phone we've had), so you can make phone
>>>> calls, send texts, and use the data network.
>>>>
>>>> The Inferno window manager has been re-worked with cell phone use in
>>>> mind. Windows are automatically sized to fill the whole screen. The
>>>> menu has been moved to the top and the menu items have been made
>>>> significantly larger. Physical buttons on the phone are now used to do
>>>> many common tasks:
>>>>
>>>>    (these keys are for the Nexus S, different bindings are used for
>>>> the Nook, which has different keys available)
>>>>    * Back: Close the current window
>>>>    * Menu: Toggle the onscreen keyboard
>>>>    * Home: Minimize the current window
>>>>    * Power: Turn off the screen
>>>>    * Power+Volume Up: Open the screen brightness widget
>>>>    * Power+Volume Down: Turn off the phone
>>>>    * Power+Home: Restart Inferno
>>>>
>>>> Installation is reasonably simple. You'll need the Android SDK
>>>> (http://developer.android.com/sdk/index.html), with the platform-tools
>>>> package installed for the adb and fastboot utilities. We also strongly
>>>> recommend installing CyanogenMod on your phone before
>>>> proceeding--that's what we use to test.
>>>>
>>>> First, make absolutely sure you have the "adb" and "fastboot"
>>>> commands in your path--see the previous paragraph regarding the
>>>> SDK and try running "adb" to be sure. Download the tarball from
>>>> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
>>>> unpack it in your root. You should end up with a /data/inferno
>>>> directory (we put it there because of the Inferno build
>>>> process). Then, go to the /data/inferno/android directory and run
>>>> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
>>>> Reflash-Nook-Color.sh if you have a Nook). This will
>>>> automatically set up the phone to boot into either Inferno or the
>>>> regular Java environment--during bootup, the screen will go solid
>>>> white; if you touch the screen at this point, it will boot into
>>>> the regular Android environment, otherwise it will timeout and go
>>>> to Inferno. However, at this point you're not yet ready to boot
>>>> into Inferno, so reboot the phone and touch the screen to go into
>>>> the regular Android UI. The final task is to run the command "cd
>>>> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
>>>> Inferno, and you're ready to go.
>>>>
>>>> You can also clone the repository
>>>> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
>>>> is a significant effort. I do not recommend it if you wish to simply
>>>> try the system, but if you want to do development you should get the
>>>> repository.
>>>>
>>>> Disclaimer: If you break your phone, it's not our fault. Don't email
>>>> us, don't come knocking on our door, and don't call us--oh wait, you
>>>> won't be able to do that anyway, your phone is broken!
>>>>
>>>> Credit where credit is due: Ron Minnich came up with the initial
>>>> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
>>>> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
>>>> lion's share of the work of making Inferno into a usable cell phone
>>>> OS--no small feat, considering that neither had any Limbo or Inferno
>>>> experience before the start of the summer! They re-wrote the UI,
>>>> puzzled out the undocumented cell radio interface, figured out audio,
>>>> worked to make Inferno more portable across phones, and generally
>>>> figured out how to make Inferno and the Android kernel coexist
>>>> peacefully. Andy Jones, another intern, also did some very early work
>>>> with Android that helped us figure out the Android init process and
>>>> how to build for Android. I took care of getting Inferno running on
>>>> the phone in the first place and have been adding things occasionally
>>>> since then. We would also like to thank Andrey Mirtchovski for
>>>> providing the OLPC framebuffer code (which ported to the Android
>>>> phones relatively easily), and of course Charles Forsyth for keeping
>>>> the Inferno torch lit all these years (and helping me figure out some
>>>> puzzling problems throughout the summer)!
>>>>
>>>
>>
>
>



-- 
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

By the way, it's pretty easy to try things out while the phone is
running. Just push over /data/inferno, then you should be able to do
something like this:

% stop zygote # this kills off the java UI
% /data/inferno/Android/arm/bin/emu-g
; wm/wm

The README.android file should tell you all you need to know about
managing the radio. Oh, and if you use the network, it's a good idea
to do a "setprop net.dns1 8.8.8.8"  (at the Android prompt, not in
Inferno) first, otherwise DNS doesn't seem to work right. When you're
sick of testing inferno, just Ctrl-C the process and run "start
zygote".

I've found a few things that need to be fixed and will be working on
them Monday. However, if you just want to get it running on your own
phone, you should be able to do it. You'll need to have the full
Android build environment set up, not just the SDK, and you'll need to
have adb in your path. You may also need to put "agcc" (provided in
the repo) into your path in order to actually build Inferno. I believe
README.android has a summary of how to build Inferno yourself down at
the bottom.


John

On Fri, Sep 16, 2011 at 7:40 PM, John Floren <john@jfloren.net> wrote:
> We've only had one device with an actual radio in it, so we haven't
> been able to test on anything but the Nexus S, but there's probably a
> total of 100 lines of device-specific code. Mostly, you have to figure
> out:
>
> 1. The screen dimensions and the color depth
> 2. Which devices are for the touchscreen, which are for the buttons
>
> emu/port/main.c and emu/Android/screen.c contain all the
> device-specific code, I think. If there is any justice, the radio
> interface will be the same--we talk to "rild", the radio daemon,
> rather than directly with the hardware.
>
> John
>
> On Fri, Sep 16, 2011 at 7:35 PM, Devon H. O'Dell <devon.odell@gmail.com> wrote:
>> How difficult is it to get specs and port this to other android devices? I'd
>> love to run this on my motorola droid if I could get all the radios working.
>>
>> --dho (via said droid)
>>
>> On Sep 16, 2011 10:25 PM, "paul.a.lalonde@gmail.com"
>> <paul.a.lalonde@gmail.com> wrote:
>>> For all these plan9ish things on OSX I run a case-sensitive file-system in
>>> a file; just use the Disk Utility to make one and then mount it. I link mine
>>> into my home directory and use it for all case-sensitive apps.
>>> Paul
>>>
>>> Sent from my HTC Inspire™ 4G on AT&T
>>>
>>> ----- Reply message -----
>>> From: "John Floren" <john@jfloren.net>
>>> To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>,
>>> <inferno-list@vitanuova.com>
>>> Subject: [9fans] Announcing Inferno for Android phones
>>> Date: Fri, Sep 16, 2011 7:01 pm
>>>
>>>
>>> One caveat that I just came across: If you're trying to set up your
>>> phone from Mac OS X, it's quite possible that the case-insensitive
>>> filesystem will bite you. We have two directories at the same level,
>>> named "android" and "Android". If you do an adb push from OS X,
>>> they'll both end up in a directory called "android". Here's how you
>>> can fix it:
>>>
>>> (run adb shell)
>>> # mkdir /data/inferno/Android
>>> # mv /data/inferno/android/arm /data/inferno/Android/
>>>
>>> There may be other problems lurking, but I'm pretty sure all of the
>>> stuff Inferno needs is all lowercase.
>>>
>>>
>>> John
>>>
>>> On Fri, Sep 16, 2011 at 3:23 PM, John Floren <john@jfloren.net> wrote:
>>>> We would like to announce the availability of Inferno for Android
>>>> phones. Because our slogan is "If it ain't broke, break it", we
>>>> decided to replace the Java stack on Android phones with
>>>> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
>>>> to keep with the Inferno theme, but then we realized we're in Northern
>>>> California and the change was obvious.
>>>>
>>>> The Hellaphone runs Inferno directly on top of the basic Linux layer
>>>> provided by Android. We do not even allow the Java system to
>>>> start. Instead, emu draws directly to the Linux framebuffer (thanks,
>>>> Andrey, for the initial code!) and treats the touchscreen like a
>>>> one-button mouse. Because the Java environment doesn't start, it only
>>>> takes about 10 seconds to go from power off to a fully-booted Inferno
>>>> environment.
>>>>
>>>> As of today, we have Inferno running on the Nexus S and the Nook
>>>> Color. It should also run on the Android emulator, but we haven't
>>>> tested that in a long time. The cell radio is supported, at least on
>>>> the Nexus S (the only actual phone we've had), so you can make phone
>>>> calls, send texts, and use the data network.
>>>>
>>>> The Inferno window manager has been re-worked with cell phone use in
>>>> mind. Windows are automatically sized to fill the whole screen. The
>>>> menu has been moved to the top and the menu items have been made
>>>> significantly larger. Physical buttons on the phone are now used to do
>>>> many common tasks:
>>>>
>>>>    (these keys are for the Nexus S, different bindings are used for
>>>> the Nook, which has different keys available)
>>>>    * Back: Close the current window
>>>>    * Menu: Toggle the onscreen keyboard
>>>>    * Home: Minimize the current window
>>>>    * Power: Turn off the screen
>>>>    * Power+Volume Up: Open the screen brightness widget
>>>>    * Power+Volume Down: Turn off the phone
>>>>    * Power+Home: Restart Inferno
>>>>
>>>> Installation is reasonably simple. You'll need the Android SDK
>>>> (http://developer.android.com/sdk/index.html), with the platform-tools
>>>> package installed for the adb and fastboot utilities. We also strongly
>>>> recommend installing CyanogenMod on your phone before
>>>> proceeding--that's what we use to test.
>>>>
>>>> First, make absolutely sure you have the "adb" and "fastboot"
>>>> commands in your path--see the previous paragraph regarding the
>>>> SDK and try running "adb" to be sure. Download the tarball from
>>>> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
>>>> unpack it in your root. You should end up with a /data/inferno
>>>> directory (we put it there because of the Inferno build
>>>> process). Then, go to the /data/inferno/android directory and run
>>>> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
>>>> Reflash-Nook-Color.sh if you have a Nook). This will
>>>> automatically set up the phone to boot into either Inferno or the
>>>> regular Java environment--during bootup, the screen will go solid
>>>> white; if you touch the screen at this point, it will boot into
>>>> the regular Android environment, otherwise it will timeout and go
>>>> to Inferno. However, at this point you're not yet ready to boot
>>>> into Inferno, so reboot the phone and touch the screen to go into
>>>> the regular Android UI. The final task is to run the command "cd
>>>> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
>>>> Inferno, and you're ready to go.
>>>>
>>>> You can also clone the repository
>>>> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
>>>> is a significant effort. I do not recommend it if you wish to simply
>>>> try the system, but if you want to do development you should get the
>>>> repository.
>>>>
>>>> Disclaimer: If you break your phone, it's not our fault. Don't email
>>>> us, don't come knocking on our door, and don't call us--oh wait, you
>>>> won't be able to do that anyway, your phone is broken!
>>>>
>>>> Credit where credit is due: Ron Minnich came up with the initial
>>>> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
>>>> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
>>>> lion's share of the work of making Inferno into a usable cell phone
>>>> OS--no small feat, considering that neither had any Limbo or Inferno
>>>> experience before the start of the summer! They re-wrote the UI,
>>>> puzzled out the undocumented cell radio interface, figured out audio,
>>>> worked to make Inferno more portable across phones, and generally
>>>> figured out how to make Inferno and the Android kernel coexist
>>>> peacefully. Andy Jones, another intern, also did some very early work
>>>> with Android that helped us figure out the Android init process and
>>>> how to build for Android. I took care of getting Inferno running on
>>>> the phone in the first place and have been adding things occasionally
>>>> since then. We would also like to thank Andrey Mirtchovski for
>>>> providing the OLPC framebuffer code (which ported to the Android
>>>> phones relatively easily), and of course Charles Forsyth for keeping
>>>> the Inferno torch lit all these years (and helping me figure out some
>>>> puzzling problems throughout the summer)!
>>>>
>>>
>>
>

Re: [9fans] Announcing Inferno for Android phones

[John Floren]

We've only had one device with an actual radio in it, so we haven't
been able to test on anything but the Nexus S, but there's probably a
total of 100 lines of device-specific code. Mostly, you have to figure
out:

1. The screen dimensions and the color depth
2. Which devices are for the touchscreen, which are for the buttons

emu/port/main.c and emu/Android/screen.c contain all the
device-specific code, I think. If there is any justice, the radio
interface will be the same--we talk to "rild", the radio daemon,
rather than directly with the hardware.

John

On Fri, Sep 16, 2011 at 7:35 PM, Devon H. O'Dell <devon.odell@gmail.com> wrote:
> How difficult is it to get specs and port this to other android devices? I'd
> love to run this on my motorola droid if I could get all the radios working.
>
> --dho (via said droid)
>
> On Sep 16, 2011 10:25 PM, "paul.a.lalonde@gmail.com"
> <paul.a.lalonde@gmail.com> wrote:
>> For all these plan9ish things on OSX I run a case-sensitive file-system in
>> a file; just use the Disk Utility to make one and then mount it. I link mine
>> into my home directory and use it for all case-sensitive apps.
>> Paul
>>
>> Sent from my HTC Inspire™ 4G on AT&T
>>
>> ----- Reply message -----
>> From: "John Floren" <john@jfloren.net>
>> To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>,
>> <inferno-list@vitanuova.com>
>> Subject: [9fans] Announcing Inferno for Android phones
>> Date: Fri, Sep 16, 2011 7:01 pm
>>
>>
>> One caveat that I just came across: If you're trying to set up your
>> phone from Mac OS X, it's quite possible that the case-insensitive
>> filesystem will bite you. We have two directories at the same level,
>> named "android" and "Android". If you do an adb push from OS X,
>> they'll both end up in a directory called "android". Here's how you
>> can fix it:
>>
>> (run adb shell)
>> # mkdir /data/inferno/Android
>> # mv /data/inferno/android/arm /data/inferno/Android/
>>
>> There may be other problems lurking, but I'm pretty sure all of the
>> stuff Inferno needs is all lowercase.
>>
>>
>> John
>>
>> On Fri, Sep 16, 2011 at 3:23 PM, John Floren <john@jfloren.net> wrote:
>>> We would like to announce the availability of Inferno for Android
>>> phones. Because our slogan is "If it ain't broke, break it", we
>>> decided to replace the Java stack on Android phones with
>>> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
>>> to keep with the Inferno theme, but then we realized we're in Northern
>>> California and the change was obvious.
>>>
>>> The Hellaphone runs Inferno directly on top of the basic Linux layer
>>> provided by Android. We do not even allow the Java system to
>>> start. Instead, emu draws directly to the Linux framebuffer (thanks,
>>> Andrey, for the initial code!) and treats the touchscreen like a
>>> one-button mouse. Because the Java environment doesn't start, it only
>>> takes about 10 seconds to go from power off to a fully-booted Inferno
>>> environment.
>>>
>>> As of today, we have Inferno running on the Nexus S and the Nook
>>> Color. It should also run on the Android emulator, but we haven't
>>> tested that in a long time. The cell radio is supported, at least on
>>> the Nexus S (the only actual phone we've had), so you can make phone
>>> calls, send texts, and use the data network.
>>>
>>> The Inferno window manager has been re-worked with cell phone use in
>>> mind. Windows are automatically sized to fill the whole screen. The
>>> menu has been moved to the top and the menu items have been made
>>> significantly larger. Physical buttons on the phone are now used to do
>>> many common tasks:
>>>
>>>    (these keys are for the Nexus S, different bindings are used for
>>> the Nook, which has different keys available)
>>>    * Back: Close the current window
>>>    * Menu: Toggle the onscreen keyboard
>>>    * Home: Minimize the current window
>>>    * Power: Turn off the screen
>>>    * Power+Volume Up: Open the screen brightness widget
>>>    * Power+Volume Down: Turn off the phone
>>>    * Power+Home: Restart Inferno
>>>
>>> Installation is reasonably simple. You'll need the Android SDK
>>> (http://developer.android.com/sdk/index.html), with the platform-tools
>>> package installed for the adb and fastboot utilities. We also strongly
>>> recommend installing CyanogenMod on your phone before
>>> proceeding--that's what we use to test.
>>>
>>> First, make absolutely sure you have the "adb" and "fastboot"
>>> commands in your path--see the previous paragraph regarding the
>>> SDK and try running "adb" to be sure. Download the tarball from
>>> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
>>> unpack it in your root. You should end up with a /data/inferno
>>> directory (we put it there because of the Inferno build
>>> process). Then, go to the /data/inferno/android directory and run
>>> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
>>> Reflash-Nook-Color.sh if you have a Nook). This will
>>> automatically set up the phone to boot into either Inferno or the
>>> regular Java environment--during bootup, the screen will go solid
>>> white; if you touch the screen at this point, it will boot into
>>> the regular Android environment, otherwise it will timeout and go
>>> to Inferno. However, at this point you're not yet ready to boot
>>> into Inferno, so reboot the phone and touch the screen to go into
>>> the regular Android UI. The final task is to run the command "cd
>>> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
>>> Inferno, and you're ready to go.
>>>
>>> You can also clone the repository
>>> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
>>> is a significant effort. I do not recommend it if you wish to simply
>>> try the system, but if you want to do development you should get the
>>> repository.
>>>
>>> Disclaimer: If you break your phone, it's not our fault. Don't email
>>> us, don't come knocking on our door, and don't call us--oh wait, you
>>> won't be able to do that anyway, your phone is broken!
>>>
>>> Credit where credit is due: Ron Minnich came up with the initial
>>> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
>>> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
>>> lion's share of the work of making Inferno into a usable cell phone
>>> OS--no small feat, considering that neither had any Limbo or Inferno
>>> experience before the start of the summer! They re-wrote the UI,
>>> puzzled out the undocumented cell radio interface, figured out audio,
>>> worked to make Inferno more portable across phones, and generally
>>> figured out how to make Inferno and the Android kernel coexist
>>> peacefully. Andy Jones, another intern, also did some very early work
>>> with Android that helped us figure out the Android init process and
>>> how to build for Android. I took care of getting Inferno running on
>>> the phone in the first place and have been adding things occasionally
>>> since then. We would also like to thank Andrey Mirtchovski for
>>> providing the OLPC framebuffer code (which ported to the Android
>>> phones relatively easily), and of course Charles Forsyth for keeping
>>> the Inferno torch lit all these years (and helping me figure out some
>>> puzzling problems throughout the summer)!
>>>
>>
>

Re: [9fans] Announcing Inferno for Android phones

[Devon H. O'Dell]

[-- Attachment #1: Type: text/plain, Size: 6694 bytes --]

How difficult is it to get specs and port this to other android devices? I'd
love to run this on my motorola droid if I could get all the radios working.

--dho (via said droid)
On Sep 16, 2011 10:25 PM, "paul.a.lalonde@gmail.com" <
paul.a.lalonde@gmail.com> wrote:
> For all these plan9ish things on OSX I run a case-sensitive file-system in
a file; just use the Disk Utility to make one and then mount it. I link mine
into my home directory and use it for all case-sensitive apps.
> Paul
>
> Sent from my HTC Inspire™ 4G on AT&T
>
> ----- Reply message -----
> From: "John Floren" <john@jfloren.net>
> To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>, <
inferno-list@vitanuova.com>
> Subject: [9fans] Announcing Inferno for Android phones
> Date: Fri, Sep 16, 2011 7:01 pm
>
>
> One caveat that I just came across: If you're trying to set up your
> phone from Mac OS X, it's quite possible that the case-insensitive
> filesystem will bite you. We have two directories at the same level,
> named "android" and "Android". If you do an adb push from OS X,
> they'll both end up in a directory called "android". Here's how you
> can fix it:
>
> (run adb shell)
> # mkdir /data/inferno/Android
> # mv /data/inferno/android/arm /data/inferno/Android/
>
> There may be other problems lurking, but I'm pretty sure all of the
> stuff Inferno needs is all lowercase.
>
>
> John
>
> On Fri, Sep 16, 2011 at 3:23 PM, John Floren <john@jfloren.net> wrote:
>> We would like to announce the availability of Inferno for Android
>> phones. Because our slogan is "If it ain't broke, break it", we
>> decided to replace the Java stack on Android phones with
>> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
>> to keep with the Inferno theme, but then we realized we're in Northern
>> California and the change was obvious.
>>
>> The Hellaphone runs Inferno directly on top of the basic Linux layer
>> provided by Android. We do not even allow the Java system to
>> start. Instead, emu draws directly to the Linux framebuffer (thanks,
>> Andrey, for the initial code!) and treats the touchscreen like a
>> one-button mouse. Because the Java environment doesn't start, it only
>> takes about 10 seconds to go from power off to a fully-booted Inferno
>> environment.
>>
>> As of today, we have Inferno running on the Nexus S and the Nook
>> Color. It should also run on the Android emulator, but we haven't
>> tested that in a long time. The cell radio is supported, at least on
>> the Nexus S (the only actual phone we've had), so you can make phone
>> calls, send texts, and use the data network.
>>
>> The Inferno window manager has been re-worked with cell phone use in
>> mind. Windows are automatically sized to fill the whole screen. The
>> menu has been moved to the top and the menu items have been made
>> significantly larger. Physical buttons on the phone are now used to do
>> many common tasks:
>>
>>    (these keys are for the Nexus S, different bindings are used for
>> the Nook, which has different keys available)
>>    * Back: Close the current window
>>    * Menu: Toggle the onscreen keyboard
>>    * Home: Minimize the current window
>>    * Power: Turn off the screen
>>    * Power+Volume Up: Open the screen brightness widget
>>    * Power+Volume Down: Turn off the phone
>>    * Power+Home: Restart Inferno
>>
>> Installation is reasonably simple. You'll need the Android SDK
>> (http://developer.android.com/sdk/index.html), with the platform-tools
>> package installed for the adb and fastboot utilities. We also strongly
>> recommend installing CyanogenMod on your phone before
>> proceeding--that's what we use to test.
>>
>> First, make absolutely sure you have the "adb" and "fastboot"
>> commands in your path--see the previous paragraph regarding the
>> SDK and try running "adb" to be sure. Download the tarball from
>> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
>> unpack it in your root. You should end up with a /data/inferno
>> directory (we put it there because of the Inferno build
>> process). Then, go to the /data/inferno/android directory and run
>> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
>> Reflash-Nook-Color.sh if you have a Nook). This will
>> automatically set up the phone to boot into either Inferno or the
>> regular Java environment--during bootup, the screen will go solid
>> white; if you touch the screen at this point, it will boot into
>> the regular Android environment, otherwise it will timeout and go
>> to Inferno. However, at this point you're not yet ready to boot
>> into Inferno, so reboot the phone and touch the screen to go into
>> the regular Android UI. The final task is to run the command "cd
>> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
>> Inferno, and you're ready to go.
>>
>> You can also clone the repository
>> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
>> is a significant effort. I do not recommend it if you wish to simply
>> try the system, but if you want to do development you should get the
>> repository.
>>
>> Disclaimer: If you break your phone, it's not our fault. Don't email
>> us, don't come knocking on our door, and don't call us--oh wait, you
>> won't be able to do that anyway, your phone is broken!
>>
>> Credit where credit is due: Ron Minnich came up with the initial
>> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
>> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
>> lion's share of the work of making Inferno into a usable cell phone
>> OS--no small feat, considering that neither had any Limbo or Inferno
>> experience before the start of the summer! They re-wrote the UI,
>> puzzled out the undocumented cell radio interface, figured out audio,
>> worked to make Inferno more portable across phones, and generally
>> figured out how to make Inferno and the Android kernel coexist
>> peacefully. Andy Jones, another intern, also did some very early work
>> with Android that helped us figure out the Android init process and
>> how to build for Android. I took care of getting Inferno running on
>> the phone in the first place and have been adding things occasionally
>> since then. We would also like to thank Andrey Mirtchovski for
>> providing the OLPC framebuffer code (which ported to the Android
>> phones relatively easily), and of course Charles Forsyth for keeping
>> the Inferno torch lit all these years (and helping me figure out some
>> puzzling problems throughout the summer)!
>>
>

[-- Attachment #2: Type: text/html, Size: 8383 bytes --]

Re: [9fans] Announcing Inferno for Android phones

[paul.a.lalonde]

[-- Attachment #1: Type: text/plain, Size: 6173 bytes --]

For all these plan9ish things on OSX I run a case-sensitive file-system in a file;  just use the Disk Utility to make one and then mount it.  I link mine into my home directory and use it for all case-sensitive apps.
Paul

Sent from my HTC Inspire™ 4G on AT&T

----- Reply message -----
From: "John Floren" <john@jfloren.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>, <inferno-list@vitanuova.com>
Subject: [9fans] Announcing Inferno for Android phones
Date: Fri, Sep 16, 2011 7:01 pm


One caveat that I just came across: If you're trying to set up your
phone from Mac OS X, it's quite possible that the case-insensitive
filesystem will bite you. We have two directories at the same level,
named "android" and "Android". If you do an adb push from OS X,
they'll both end up in a directory called "android". Here's how you
can fix it:

(run adb shell)
# mkdir /data/inferno/Android
# mv /data/inferno/android/arm /data/inferno/Android/

There may be other problems lurking, but I'm pretty sure all of the
stuff Inferno needs is all lowercase.


John

On Fri, Sep 16, 2011 at 3:23 PM, John Floren <john@jfloren.net> wrote:
> We would like to announce the availability of Inferno for Android
> phones. Because our slogan is "If it ain't broke, break it", we
> decided to replace the Java stack on Android phones with
> Inferno. We've dubbed it the Hellaphone--it was originally Hellphone,
> to keep with the Inferno theme, but then we realized we're in Northern
> California and the change was obvious.
>
> The Hellaphone runs Inferno directly on top of the basic Linux layer
> provided by Android. We do not even allow the Java system to
> start. Instead, emu draws directly to the Linux framebuffer (thanks,
> Andrey, for the initial code!) and treats the touchscreen like a
> one-button mouse. Because the Java environment doesn't start, it only
> takes about 10 seconds to go from power off to a fully-booted Inferno
> environment.
>
> As of today, we have Inferno running on the Nexus S and the Nook
> Color. It should also run on the Android emulator, but we haven't
> tested that in a long time. The cell radio is supported, at least on
> the Nexus S (the only actual phone we've had), so you can make phone
> calls, send texts, and use the data network.
>
> The Inferno window manager has been re-worked with cell phone use in
> mind. Windows are automatically sized to fill the whole screen. The
> menu has been moved to the top and the menu items have been made
> significantly larger. Physical buttons on the phone are now used to do
> many common tasks:
>
>    (these keys are for the Nexus S, different bindings are used for
> the Nook, which has different keys available)
>    * Back: Close the current window
>    * Menu: Toggle the onscreen keyboard
>    * Home: Minimize the current window
>    * Power: Turn off the screen
>    * Power+Volume Up: Open the screen brightness widget
>    * Power+Volume Down: Turn off the phone
>    * Power+Home: Restart Inferno
>
> Installation is reasonably simple. You'll need the Android SDK
> (http://developer.android.com/sdk/index.html), with the platform-tools
> package installed for the adb and fastboot utilities. We also strongly
> recommend installing CyanogenMod on your phone before
> proceeding--that's what we use to test.
>
> First, make absolutely sure you have the "adb" and "fastboot"
> commands in your path--see the previous paragraph regarding the
> SDK and try running "adb" to be sure. Download the tarball from
> http://bitbucket.org/floren/inferno/downloads/hellaphone.tgz and
> unpack it in your root. You should end up with a /data/inferno
> directory (we put it there because of the Inferno build
> process). Then, go to the /data/inferno/android directory and run
> the Reflash-Nexus-S.sh script (assuming you have a Nexus S. Run
> Reflash-Nook-Color.sh if you have a Nook). This will
> automatically set up the phone to boot into either Inferno or the
> regular Java environment--during bootup, the screen will go solid
> white; if you touch the screen at this point, it will boot into
> the regular Android environment, otherwise it will timeout and go
> to Inferno. However, at this point you're not yet ready to boot
> into Inferno, so reboot the phone and touch the screen to go into
> the regular Android UI. The final task is to run the command "cd
> /data/inferno; ./parallel-push.sh". Reboot, let it boot into
> Inferno, and you're ready to go.
>
> You can also clone the repository
> (http://bitbucket.org/floren/inferno/) and build it yourself, but this
> is a significant effort. I do not recommend it if you wish to simply
> try the system, but if you want to do development you should get the
> repository.
>
> Disclaimer: If you break your phone, it's not our fault. Don't email
> us, don't come knocking on our door, and don't call us--oh wait, you
> won't be able to do that anyway, your phone is broken!
>
> Credit where credit is due: Ron Minnich came up with the initial
> idea--we've been kicking the idea of a Plan 9/Inferno phone around for
> years. Our summer interns, Joel Armstrong and Joshua Landgraf, did the
> lion's share of the work of making Inferno into a usable cell phone
> OS--no small feat, considering that neither had any Limbo or Inferno
> experience before the start of the summer! They re-wrote the UI,
> puzzled out the undocumented cell radio interface, figured out audio,
> worked to make Inferno more portable across phones, and generally
> figured out how to make Inferno and the Android kernel coexist
> peacefully. Andy Jones, another intern, also did some very early work
> with Android that helped us figure out the Android init process and
> how to build for Android. I took care of getting Inferno running on
> the phone in the first place and have been adding things occasionally
> since then. We would also like to thank Andrey Mirtchovski for
> providing the OLPC framebuffer code (which ported to the Android
> phones relatively easily), and of course Charles Forsyth for keeping
> the Inferno torch lit all these years (and helping me figure out some
> puzzling problems throughout the summer)!
>


[-- Attachment #2: Type: text/html, Size: 7038 bytes --]