Message: 9
Date: Tue, 27 Apr 2010 21:42:08 +0300
From: "Ville M. Vainio" <vivai...@gmail.com>
Subject: Nokia Qt SDK beta released
To: maemo-developers@maemo.org
Message-ID:
<t2j46cb515a1004271142v2ae288f4s29134b85651d6...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
People that don't unconditionally love scratchbox may be delighted to
hear that madde + qt creator combination is taking steps to a more
official & endorsed status:
http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/IDEs/Nokia_Qt_SDK/
It has a simulator as well (i.e. a custom version of Qt libraries that
mocks various things, including hw events from Qt mobility).
CAUTION: You can't use the (excellent) hw debugging feature on your
N900 yet, PR 1.2 is needed. In the mean time, you can kick the tires
with the simulator (or a Symbian device if you have a spare windows
machine around ;-) ).
--
Ville M. Vainio
http://tinyurl.com/vainio
------------------------------
Message: 10
Date: Tue, 27 Apr 2010 21:04:40 +0200
From: chantra <chan...@debuntu.org>
Subject: Re: Meaning of Phone.Net.get_current_cell_info return values
To: "Dawid Lorenz (maemobile)" <a...@adl.pl>
Cc: maemo-developers@maemo.org
Message-ID: <1272395080.9313.165.ca...@rahu>
Content-Type: text/plain; charset="utf-8"
Hi Dawid,
Tks for your reply.
Actually, the fields you mentioned are the ones returned by
get_registration_status
get_current_cell_info fields are slightly different.
I did not find anything yet on those 2 last fields :s.
For instance, ATM, I have different returned result for cell_info and
registration:
Nokia-N900-42-11:~# ./get_registration_status.sh
method return sender=:1.17 -> dest=:1.538 reply_serial=2
byte 1
uint16 21013
uint32 21112
uint32 1
uint32 214
byte 3
byte 3
int32 0
Nokia-N900-42-11:~# ./get_current_cell_info.sh
method return sender=:1.17 -> dest=:1.539 reply_serial=2
byte 1
uint16 21013
uint32 21112
uint32 1
uint32 214
byte 0
byte 3
int32 0
Nokia-N900-42-11:~#
Tks for your help.
Chantra
On Tue, 2010-04-27 at 19:18 +0100, Dawid Lorenz (maemobile) wrote:
----- Original message -----
> Hi,
>
> I have been spending quite some time understanding the values
returned
> by:
> dbus-send --system --type=method_call --dest=com.nokia.phone.net
> --print-reply /com/nokia/phone/net Phone.Net.get_current_cell_info
> method return sender=:1.17 -> dest=:1.373 reply_serial=2
> byte 2 --> type GSM = 1, WCDMA = 2 ??
> uint16 2050 --> LAC
> uint32 17143306 --> Cell ID (cellid = res & 65535), RNC =
res >>
> 16
> uint32 1 --> mnc
> uint32 214 --> mcc
> byte 0 --> ???
> byte 3 --> ??? 3 on supported network, 0
on unsupported
> network, 2 when NSPS
> int32 0 --> error
>
> So far, this is what I have got, the 2 last bytes returned
parameters
> are the ones I try to get info from:
> byte 0 --> ???
> byte 3 --> ??? 3 on supported network, 0
on unsupported
> network, 2 when NSPS
>
> On my phone, I am generally getting values 0,3 respectively, and it
> seems that the last byte will change to 0 on unsupported networks
and 2
> when only NSPS is available.
>
> Is there anybody out there that can give me some more info on these
> values?
> Any Nokia developers that will know what those values stands
for :p.
>
> Any leads really appreciated :p
>
> Tks,
>
> Chantra
>
>
>
NSPS stands for No Service Power Save (or similar) and occurs when you
have no home/accessible network coverage, hence device will 'power
save' instead of searching for it all the time. Basically, the field
you're looking at here is current network status and tells you whether
you're within home network, is device searching for network or give up
and go into power save mode.
Don't know whether you want to know the meaning of other fields, ping
me if you do.
You might also install NetMon app from extras-devel and have a look
into its source (python). It reads that exact values you're after, so
that might give some extra clues to you. Good luck.
--
Dawid 'evad' Lorenz * http://adl.pl
null://real men never use nokia
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
!DSPAM:4bd72a4f61679706917093!
!DSPAM:4bd7354a61677892912075!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.maemo.org/pipermail/maemo-developers/attachments/20100427/b687b7a9/attachment-0001.htm>
------------------------------
Message: 11
Date: Tue, 27 Apr 2010 16:04:43 -0400
From: Demetris <demet...@ece.neu.edu>
Subject: Re: N810, GPS and Java
To: Henning Heinold <h.hein...@tarent.de>
Cc: maemo-developers@maemo.org
Message-ID: <4bd7435b.9090...@ece.neu.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hey Henning,
do you have any further info as to how to run the gpsd via the java-dbus?
I want to run this on the N800 and either interface through java or
javascript
clients.
Thanks
Henning Heinold wrote:
Hi,
you can start the gpsd via dbus. I don't know yet if the gpsd also sends
the coords via dbus. So try it out with the java-dbus bindings.
Bye Henning
__________________________________________________________________
Besuchen Sie uns auf unserem diesj?hrigen CeBIT Gemeinschaftsstand
"Open Source Berlin" (Halle 2 Stand C36) vom 02.03. - 06.03.2010!
__________________________________________________________________
tarent Gesellschaft f?r Softwareentwicklung und IT-Beratung mbH
Gesch?ftsf?hrer: Boris Esser, Elmar Geese
HRB AG Bonn 5168 - Ust-ID: DE122264941
http://www.tarent.com/
Heilsbachstr. 24, 53123 Bonn, fon +49 228 52675-0, fax +49 228
52675-25
Weigandufer 45, 12059 Berlin, fon +49 30 5682943-30, fax +49 228
52675-25
Sch?tzenstr. 18, 10117 Berlin, fon +49 30 27594853, fax +49 30
78709617
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
------------------------------
Message: 12
Date: Tue, 27 Apr 2010 23:30:18 +0200
From: Thomas Waelti <twae...@gmail.com>
Subject: Re: Help needed: packaging/distributing very small C app
To: Jeremiah Foster <jerem...@jeremiahfoster.com>, Joseph Charpak
<josephchar...@comcast.net>
Cc: maemo-developers@maemo.org
Message-ID: <2010427233018.917...@mobigo>
Content-Type: text/plain; charset="us-ascii"
Hell, frozen over. It took me four evenings, one hour each evening,
to tinker and try and fail and try again. But now it loooks good:
http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/mafw-play-list/0.1.0-5/
(To test it, you need to have one or more saved playlists on your
N900. Then open X-Term and enter "mafw-play-list NameOfYourPlayList"
and it should start the playback of this playlist.)
Thanks for all the help and support - it's been a positive
(community) but still frustrating (technology) experience :-)
I guess once you're spoiled by something like the Compact Framework
and Visual Studio, a casual hoppy developer finds the current state
of Maemo development quite difficult to accept...
Mainly, there was a major pitfall that I fell into:
- In configure.ac, pkg_check_modules, I had to put mafw and
mafw-shared as dependencies
- But in the Build-Depends of the control file, I had to write
libmafw0-dev and libmafw-shared0-dev
In addition, once something fails, it's still a bit unclear from the
current docs about where to continue/repeat which steps.
Thanks again and Happy hacking
-Tom
On Apr 22, 2010, at 11:02 PM, Joseph Charpak wrote:
On Thu, 2010-04-22 at 21:58 +0200, Thomas Waelti wrote:
Thanks everybody for your extensive support in documenting this
process. While I encountered a few smaller stumbling blocks, it
worked quite good (especially once the docs got updated by David)
I can report "halfway" success for now :-)
The reason is simple:
- No package 'mafw' found
- No package 'mafw-shared' found
How to proceed? Is this indeed a problem of the autobuilder (no
mawf libs) or of my source package?
The build-depends line in the debian control file is probably missing a
reference to mafw and mafw-shared. You have it locally so the program
finds it, but the autobuilder doesn't know to include it and therefore
can't complete the build. Remember the autobuilder only includes the
bareest minimum by default, you need to explicitly include everything
else.
I would suspect that is the problem as well. I would also look at
your 'Depends:' line to make sure you have all the packages your
app relies on at runtime installed with your package when it is
installed on someone else's machine. Build-Depends is for buildtime
dependencies, Depends is for runtime dependencies.
Jeremiah
------------------------------
Message: 13
Date: Wed, 28 Apr 2010 03:09:29 -0300
From: Fabio Leal <sousaleal.fa...@gmail.com>
Subject: Canola's main website
To: maemo-developers@maemo.org
Message-ID:
<l2ycb92e1bb1004272309j3f81b492o1e2424705a0c6...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi all,
Who is mantaining, nowadays, Canola's main website?
Things seems to be quite outdated there...
I'm planning to start to work on a new plugin and I'll probably write some
new tutorials. Who should I contact in order to have it exposed on Canola's
website?
Regards
--
F?bio Leal
http://fabiosleal.wordpress.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.maemo.org/pipermail/maemo-developers/attachments/20100428/1f45a3b2/attachment-0001.htm>
------------------------------
Message: 14
Date: Wed, 28 Apr 2010 10:13:12 +0200
From: David King <dav...@openismus.com>
Subject: Re: Help needed: packaging/distributing very small C app
To: maemo-developers@maemo.org
Message-ID: <20100428081311.ga4...@dave>
Content-Type: text/plain; charset=utf-8; format=flowed
On 2010-04-27 23:30, Thomas Waelti <twae...@gmail.com> wrote:
Hell, frozen over. It took me four evenings, one hour each evening,
to tinker and try and fail and try again. But now it loooks good:
http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/mafw-play-list/0.1.0-5/
(To test it, you need to have one or more saved playlists on your
N900. Then open X-Term and enter "mafw-play-list
NameOfYourPlayList" and it should start the playback of this
playlist.)
Thanks for all the help and support - it's been a positive
(community) but still frustrating (technology) experience :-)
I guess once you're spoiled by something like the Compact Framework
and Visual Studio, a casual hoppy developer finds the current state
of Maemo development quite difficult to accept...
Mainly, there was a major pitfall that I fell into:
- In configure.ac, pkg_check_modules, I had to put mafw and
mafw-shared as dependencies
- But in the Build-Depends of the control file, I had to write
libmafw0-dev and libmafw-shared0-dev
Yes, perhaps I could make this a bit clearer in the wiki. Maybe a bit of
dpkg magic to determine which package owns a particular pkg-config file
would be helpful?
In addition, once something fails, it's still a bit unclear from
the current docs about where to continue/repeat which steps.
Yes, this is hard to solve in such a compact tutorial, as there are lots
of steps where something could fail, and it is difficult to find the
right balance between proding too much and too little information.
Contributions welcome ;)
--
David King | http://amigadave.com/ | dav...@openismus.com
------------------------------
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
End of maemo-developers Digest, Vol 60, Issue 28
************************************************
