I'm embarking on a project where I need to work at the c/c++ level under
J2ME and tie into the native phone stack as well. I'm trying to determine
whether I should initially target OpenMoko or Qtopia's Greenphone initially.
One of the decision points in this for me is the question of whether
Daniel sent his response directly instead of to the list by accident. I
confirmed that with him so I'm leaving his entire reply and adding my points
at the end...
-Original Message-
From: Silva, Daniel [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 07, 2007 10:40 AM
To: John Seghers
As one data point, I have managed to run phoneME Feature via qvfb inside
OpenMoko inside Xephyr on Ubuntu.
Tying together this thread with the UI thread, phoneME is one application
that would benefit greatly from having a framebuffer interface available. It
is designed to render to a frame
Luit van Drongelen wrote:
(most phones
and PDAs are QVGA).
Actually most phones sold today are 176 x 220, whereas most PDAs are QVGA.
There's still a lot of phones today that are 128 x 160 and the Sidekick III
is still 240 x 160.
- John
___
Michele Manzato wrote:
Don't get me wrong, I can guess (some of) the reasons behind the plain
words. But then I wonder whether there is really any transparency in the
development of Neo/OpenMoko?
One of the things I've seen while lurking on the list is the propensity for
people to want Neo
Tim Newsom wrote:
This is where XAML or XUL are particularly suited.
The idea is that the UI will be mostly svg commands or in some cases
images.. But rendered completely by the engine.
On Tue, 12 Jun 2007 4:29, Peter A Trotter wrote:
UI for these different screen resolutions and
Jonathon Suggs wrote
However, suggesting that people
shouldn't be expressing their interests about features no matter how
niche/picky/whatever is just plain wrong.
I specifically said, in my summary paragraph:
By all means give them feedback, tell them your desires, etc. But please
don't
Tim Newsom wrote
As I understand it, you would not even need to build a different svg
file. You could use the same one and it could automatically scale
because the engine would scale it.. It should be possible (in my mind)
to take a layout for 320 x 240 and draw it perfectly at 648 x 480..
Dirk Bergstrom wrote:
Ian Darwin wrote:
The phrase free phone already means the
opposite of what we want it to mean. It's done, finished, over. Move on.
Ugh, Ian's right. That phrase has been violently co-opted by the
carriers. Much as I like The free(d) phone, I don't think we can
Ortwin Regel wrote:
The screen size argument also doesn't work too well as the Neo has 640*480
which is plenty and an official forum would obviously make sure to fit
well into that resolution.
I'm sure it will fit well...but will you actually be able to read it without
a magnifying glass?
Giles Jones wrote:
On 25 Jul 2007, at 23:09, John Seghers wrote:
I'm sure it will fit well...but will you actually be able to read
it without
a magnifying glass?
Having owned a VGA PDA with similar screen size I can say that the
resolution helps with readability. Hopefully
Did you run modprobe gadgetfs default_uid=your uid before running QEMU?
I get continual kernel ring messages (dmesg, also reported in syslog) of:
dummy_udc dummy_udc: dequeued req deb73c40 from ep-c, len 4096, buf
Additionally, there are three lines output from QEMU's stdout/err:
Giles Jones wrote:
On 25 Jul 2007, at 23:42, John Seghers wrote:
ifconfig usb0 inet 192.168.0.200 netmask 255.255.255.0
ssh [EMAIL PROTECTED]
Interesting that the IP you use for usb0 is 192.168.0.200, then ssh
into 202. I thought this was a typo then considered that it was
deliberate
While I've not done so in the last few months, I have done a lot of work in
J2ME games. T-Mobile has a definite walled-garden mentality on some
aspects of web access. For the last couple of years (unless they've changed
very recently) while they have allowed browsing of most internet sites, they
No, it was definitely the SIM. Certain handsets with certain SIMs would not
download off our server (They would download the JAD, but not the JAR)--and
the JAR was being blocked, it wasn't a case of it downloading and then
refusing to install because of a bad certificate.
Changing the SIM would
Jimmy McMillan wrote:
Matthew. I was having the same problems for a while, but I found that
after I restarted the ubuntu VM, and started the qemu string (after it
was build) it worked fine for me. You make also wanna do another svn
fetch and start from scratch.
Another thing I've found
Jan wrote:
Somewhere I read that FIC will likely sell the phase 2 to phase 1 owners
for something like $150 (instead of $300 - yes, I know that phase 2 will
cost more likely around $450 instead of $300).
Hi Jan,
When FIC announced the Phase 1 phones, they told us that instead of paying
Marco Barreno wrote:
I have a question about SIM cards. If I have a 3G phone with its 3G
SIM, will I be able to put that SIM in the Neo? My carrier is ATT in
the US.
Hi Marco,
There have been some problems with ATT SIMs, some working, some not. See
the Wiki here:
Dr. H. Nikolaus Schaller wrote:
After unsuccessfully flashing different root-filesystems, I finally
found this note:
If you upload rootfs image that is smaller that previous one it
won't work - you need to attach to bootloader, erase NAND and then
upload your rootfs first:
cu -l
[EMAIL PROTECTED] wrote:
Why can't I get quality, authoritative answers to these questions?
Hi Alan. I'm not affiliated with FIC in any way, but I thought I'd give you
my viewpoint, for what it's worth. You are probably getting the answers
they *can* give. Whether that can is because they
[EMAIL PROTECTED] wrote:
Licensing
=
As mentioned, Qtopia is avaliable under the GPL. Strictly speaking it is
more open than GTK+ which is distributed under the LGPL (Lesser GPL).
...
On the other hand, Qtopia is avaliable under the GPL (The full on GPL, not
a GPL-like license, the
Giles Jones wrote:
Indeed, most people don't care about the technical reasons for it.
It's to be expected that the power management when the device is
switched on may be weak, but why does the battery drain so fast when
it's switched off?
My understanding is that it's a bug and/or the power
22 matches
Mail list logo
