Fwd: Yes, Apple's Building A TV — And It Will Be Powered By Siri

---------- Forwarded message ----------
From: SAI Select <newsletter <at> businessinsider.com>
Date: Mon, Oct 31, 2011 at 06:19
Subject: Yes, Apple's Building A TV — And It Will Be Powered By Siri
To: Fernando Cassia <fcassia <at> gmail.com>

October 31, 2011
Yes, Apple's Building A TV — And It Will Be Powered By Siri

Say goodbye to your pile of remotes. Say hello to a massive new
business for Apple.

http://articles.businessinsider.com/2011-10-28/tech/30331649_1_siri-google-tv-remotes

FC
--
"The purpose of computing is insight, not numbers."
Richard Hamming - http://en.wikipedia.org/wiki/Hamming_code

--

-- 
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the "Neuros" group.
To post to this group, send email to Neuros <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros

SVN Server

NuttX realtime OS ported to run on the Neuros OSD 1.x

I arrive at these news one year late. But, I don't remember seeing
this posted here

http://tech.groups.yahoo.com/group/nuttx/message/480

///////////
NuttX v5.9 for the Neuros OSD 1.0 consumer unit builds,
boots, and runs both `nsh' and `ostest' just fine, using
the CodeSourcery 2010q1-188 EABI toolchain on GNU/Linux.
No changes at all were needed (other than the expected
tweaking of the compiler path in `setenv.sh�). Thanks!
///////////

Perhaps with a lighter kernel the problem of running out of memory
will be gone? :)

I still think a Neuros OSD v1.x with 256MB of RAM and an embedded Java
VM would have been great. :)
[If anyone succeeds in replacing the surface mount ram chips to
replace them with a pair of compatible 256MB SDRAM ones let me know
:)]

FC
PS: WRT the memory issue... Is the document below wrong? I fail to see
if it's the development boards which had 64MB vs 32MB on the
production release, or the other way around...
http://wiki.neurostechnology.com/index.php/OSD_Developer_Board_v1

the statements contradict each other:

"Differences between the Developer Samples and the Production Product
   8MB Flash and 32MB RAM _instead of 16MB/64MB as in Production_ "

"Development Board Features

    DM320 Multimedia SOC with 200 MHz ARM926, 120 MHz C54x DSP
    _64 MB of SDRAM_ "

--

-- 
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the "Neuros" group.
To post to this group, send email to Neuros <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros

Socks on the OSD...

Hi there!

Just thinking aloud... I wonder if any of you knows how much memory
does a SOCKS5 server need, and if it´d be possible to make one fit
inside the OSD.

Suppose I have an OSD in a different subnet, and I want to use it as a
low-power proxy (actualy socks) tunnel server...

Of course, the process would be killed when using the OSD for its
original purpose (recording video), but it could be used as socks
gateway when not in use for video.

Right now my only concern is not what kind of performance one might
get, but more like if a basic socks5 server would fit in the OSD´s
limited RAM...

Thoughts? comments? expletives? ;)
FC

--

-- 
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the "Neuros" group.
To post to this group, send email to Neuros <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros

Fwd: Update on Neuros

>
> What did I say?
> http://open.neurostechnology.com/node/755
>

It's always been something we've sought to do.  A reasonable fraction
of OSDs were sold under other brands actually.  But now it is, indeed,
more of a focus.

>
> In any case, good luck with your efforts!. Can you tell us a bit more
> about is Neuros designing products for?.

Two main areas:  controllers for connected devices.  Ie next
generation remote controls.  In a world of connected TV, PCs, blu ray
players, we need something that consolidates control of them...

Second area is android peripherals.  Largely through the lack of a 30
pin standardized connector, Android has been left out of a lot of
peripheral development.

We're going to be developing (hopefully) for a number of major brands,
but not surprisingly, our first major customer is Digital Innovations.

We're actually going to be in the market for an android contract
developer.  I'll be posting a job description shortly.

--

-- 
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the "Neuros" group.
To post to this group, send email to Neuros <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros

Update on Neuros

Hi everyone,

Talking with Nero today I realized how long it's been since I've given
the list an update.

First, most of you have no doubt noticed Neuros has exited the
consumer facing business (at least for the time being). We've done
this in order to focus our attention on licensing and private label.
These are products Neuros  designs, develops and manufactures for
other consumer brands. this is a strategy that really allows us to
focus on our strengths in engineering and innovation.

Over the coming weeks and months I'll be talking more specifically
about some of the products we'll be launching.  We focused on 2 main
areas of peripherals: controllers and android accessories.  I believe
they are products a lot of you will have some interest in.

I think you'll be excited to see the amount of progress we've quietly
made over the last year. In the meantime I just wanted to drop a quick
note to let you know we're still alive and chugging along.

Joe

--

-- 
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the "Neuros" group.
To post to this group, send email to Neuros <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros

neuros OSD1 nmsd process

I扉e been playing with the OSDv1 and telnetting to it. It runs the OSDNG 
firmware and I扉ebeen telnetting to the box and observing cpu usage with 
"top".

While playing back a video file, vplayer uses 1.1% of CPU, and top uses 
3.5%, idecode_video uses 1.5% and process 慨msd戟ses 22%, another (2nd) 
nmsd uses 0.9%.

Question: what is nmsd? and why are there two running?.

Just curious.

FC

--

-- 
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the "Neuros" group.
To post to this group, send email to Neuros <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros

OSD: build closed-source code with my toolchain

invalid filenames in SD card

One of my SD cards got corrupted and displays several files with
mangled filenames... namely high-ascii chars

Windows XP refuses to rename those diaplaying some odd error message
that I didn´t write down.

Will Linux do? Or is there another solution? The files are there, and
two of the mangled filenames are very long OSD recordings.

The card is a 4GB SD (non-SDHC) PQI, FWIW. Format was obviously fat32.

FC

--

-- 
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the "Neuros" group.
To post to this group, send email to Neuros <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros

Using the tablet for something

Hi folks,
Among other projects I'm working on lately I'm trying to use the
Neuros tablet to do something useful.

Basically what I plan to do is to put a small app on it that will
connect to a daemon on the Link (or my laptop, or on the OSD1 when I
finally get around resurrecting one and making it my low-power audio
player remotely controlled by my laptop or cellphone).
The app will get from the daemon the metadata for the currently
playing track and display it on the screen in the most readable way
possible.

The tablet itself will be hanging somewhere on a wall where anyone in
the room can see it -- velcro straps, a wooden frame/cradle, something
like that, depending on what I manage to scavenge around.
Possibly when there's no music playing it will act as a wall clock, or
display RSS feeds and that stuff, or just go to sleep to consume less
watts (if doable on android and this hardware, I don't know).

I'm doing this because being a glorified wall  is at least better than
sitting in a box gathering dust, for learning some more about android
dev and so that my girlfriend will stop asking me "what band is this
?" ten times a day ;)

So to start off I cut away the power cable and soldered a couple extra
meters of wires to it, since I really hated the tiny tiny power cord
and I will need to have a long wire anyway since I'll be hanging it
not too near the wall outlet.

Then I tried uploading an hello world app to the tablet with adb, but
it's not seeing the tabled via USB (it's seeing it only as mass
storage).
So I thought that a newer firmare would've been better, and tried
"Mercury" from a link from slatedroid [1]

However with Mercury the wifi is pretty wonky, not connecting and not
seeing the networks even one meter away for a while, but then suddenly
connecting -- but when trying to browse it's actually still offline
even though the WiFi icon is showing as connected with full power.
adb over USB still doesn't work.

I also tried the original 2.0 version of the firmware from the
manufacturer (from a link that Joe posted on this list a long time
ago), but same crappy wifi and broken adb.

So for now I'm gonna go ahead developing the app in the emulator,
hoping that someone of you can help me figure out how to get the
system in a somewhat stable config that can be used. I don't need the
latest and greatest, just something working.

If there's a better firmware for the tablet or a newer version of
Mercury or anything that will give me a more decent WiFi and adb
usage, please let me know.

Cheers,
--
nero

[1] http://www.4shared.com/file/97peRAjL/M002_Slatedroid_Mercury_RC__Lo.html

--

-- 
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the "Neuros" group.
To post to this group, send email to Neuros <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros

neuros-beta closed?

Has the neuros-beta mailing list been closed?.

FC

--

-- 
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the "Neuros" group.
To post to this group, send email to Neuros <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros