maemo.org - Talk - PHS8 modem

maemo.org - Talk (https://talk.maemo.org/index.php)

- Neo900 (https://talk.maemo.org/forumdisplay.php?f=57)

- - PHS8 modem (https://talk.maemo.org/showthread.php?t=93210)

Hello!

I've just made a short video showing the first Neo900 proto board (the same that Nikolaus had during OHSW) making a call to a GTA04 and vice versa, and sending a SMS message.

https://www.youtube.com/watch?v=FNSPEWvTJTc

The PC to which the board is connected is running Debian GNU/Linux with freesmartphone.org middleware (generic "singleline" fsogsmd plugin for now) and SHR GUI apps, installed from Debian repos. GTA04 runs full SHR distro.

I've also started documenting the most important stuff from our POV about the modem:
http://projects.goldelico.com/p/neo900/page/Modem/

For the record: video made with N900 :D

Impressive. Good to see it does actually work (maybe? Could be a web service ;) )

Looks good! Thanks for the vid, hopefully you guys throw out some more.
Ignore the haters and trolls! Keep it up!

Well, next step: connect the "Neo900" modem to the GTA04 USB, et voila: a veritable Neo900 prototyping setup, consisting of DM3730 and all, connected to PHS8 modem via USB, (almost) exactly like we'll see it in final Neo900. Arguable if a N900 would beat the GTA04, due to the hw kbd, or the GTA04 wins thanks to the DM3730 instead of N900's OMAP3530

@dos1:
Can you check the dependencies of phoneui-apps in Debian please?
I tried just the GUI (without modem) in a Virtualbox-VM running Jessie/amd64 and it seems there are some evas-related packages missing.

strace excerpt of phoneuid when starting phoneui-dialer in another terminal:

Code:

stat("/usr/lib/x86_64-linux-gnu/evas/modules/engines/software_x11/linux-gnu-x86_64-1.8.6/module.so", 0x7fffb5888280) = -1 ENOENT (No such file or directory)

write(2, "\33[31;1mCRI<4251>\33[0m:\33[34;1melem"..., 80CRI<4251>:elementary elm_win.c:2388 elm_win_add() ) = 80

write(2, "Software X11 engine creation fai"..., 52Software X11 engine creation failed. Trying default.) = 52

write(2, "\n", 1

)                       = 1

stat("/usr/lib/x86_64-linux-gnu/evas/modules/engines/fb/linux-gnu-x86_64-1.8.6/module.so", 0x7fffb58882b0) = -1 ENOENT (No such file or directory)

write(2, "\33[31mERR<4251>\33[0m:\33[34;1melemen"..., 78ERR<4251>:elementary elm_win.c:2574 elm_win_add() ) = 78

write(2, "Cannot create window.", 21Cannot create window.)   = 21

write(2, "\n", 1

)                       = 1

write(2, "\n(process:4251): libphone-ui-shr"..., 101

(process:4251): libphone-ui-shr-CRITICAL **: Wasn't able to create a window (ui_utils_view_init:76)

) = 101

write(2, "\n(process:4251): libphone-ui-shr"..., 73

(process:4251): libphone-ui-shr-CRITICAL **: Failed to init dialer view

Please note that the VM has e17 installed and therefore some evas-packages were already there.

phoneuid.log says this:

Code:

2014.05.20 23:15:50.185004 [libphone-ui-shr]    CRITICAL: Wasn't able to create a window (ui_utils_view_init:76)

2014.05.20 23:15:50.185062 [libphone-ui-shr]    CRITICAL: Failed to init dialer view

2014.05.20 23:16:40.841105 [phoneuid]   CRITICAL: Failed to register /org/shr/phoneui/CallManagement: An object is already exported for the interface org.shr.phoneui.CallManagement at /org/shr/phoneui/CallManagement

2014.05.20 23:16:40.841200 [phoneuid]   CRITICAL: Failed to register /org/shr/phoneui/Contacts: An object is already exported for the interface org.shr.phoneui.Contacts at /org/shr/phoneui/Contacts

2014.05.20 23:16:40.841224 [phoneuid]   CRITICAL: Failed to register /org/shr/phoneui/Dialer: An object is already exported for the interface org.shr.phoneui.Dialer at /org/shr/phoneui/Dialer

2014.05.20 23:16:40.841252 [phoneuid]   CRITICAL: Failed to register /org/shr/phoneui/IdleScreen: An object is already exported for the interface org.shr.phoneui.IdleScreen at /org/shr/phoneui/IdleScreen

2014.05.20 23:16:40.841276 [phoneuid]   CRITICAL: Failed to register /org/shr/phoneui/Messages: An object is already exported for the interface org.shr.phoneui.Messages at /org/shr/phoneui/Messages

2014.05.20 23:16:40.843448 [phoneuid]   CRITICAL: Failed to register /org/shr/phoneui/Notification: An object is already exported for the interface org.shr.phoneui.Notification at /org/shr/phoneui/Notification

2014.05.20 23:16:40.843500 [phoneuid]   CRITICAL: Failed to register /org/shr/phoneui/PhoneLog: An object is already exported for the interface org.shr.phoneui.PhoneLog at /org/shr/phoneui/PhoneLog

2014.05.20 23:16:40.843554 [phoneuid]   CRITICAL: Failed to register /org/shr/phoneui/Settings: An object is already exported for the interface org.shr.phoneui.Settings at /org/shr/phoneui/Settings

phonefsod.log has no entries for that time.
libevas1-engines-x and libevas1-engine-fb were not installed and after instaling the latter the above problem disappeared.

A second problem seems to be that phoneuid doesn't run stable. About 5 seconds after starting phoneui-quick-settings phoneuid segfaulted:

Code:

write(2, "\n(process:4579): libphone-ui-shr"..., 234

(process:4579): libphone-ui-shr-WARNING **: Failed to retrieve profile list: (2) GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freesmartphone.opreferencesd was not provided by any .service files; retrying later

) = 234

clock_gettime(CLOCK_MONOTONIC, {1647, 25740331}) = 0

clock_gettime(CLOCK_MONOTONIC, {1647, 26503659}) = 0

recvmsg(17, 0x7fff33640550, 0)          = -1 EAGAIN (Resource temporarily unavailable)

recvmsg(17, 0x7fff33640550, 0)          = -1 EAGAIN (Resource temporarily unavailable)

clock_gettime(CLOCK_MONOTONIC, {1647, 28722927}) = 0

select(9, [3 4 8], [], [], {1, 998000}) = 1 (in [4], left {0, 9984})

clock_gettime(CLOCK_MONOTONIC, {1649, 17836445}) = 0

clock_gettime(CLOCK_MONOTONIC, {1649, 18393219}) = 0

recvmsg(17, 0x7fff33640550, 0)          = -1 EAGAIN (Resource temporarily unavailable)

recvmsg(17, 0x7fff33640550, 0)          = -1 EAGAIN (Resource temporarily unavailable)

clock_gettime(CLOCK_MONOTONIC, {1649, 19765307}) = 0

select(9, [3 4 8], [], [], {0, 6000})   = 1 (in [4], left {0, 5982})

read(4, "\1\0\0\0\0\0\0\0", 16)         = 8

clock_gettime(CLOCK_MONOTONIC, {1649, 21164508}) = 0

clock_gettime(CLOCK_MONOTONIC, {1649, 21590473}) = 0

recvmsg(17, 0x7fff33640550, 0)          = -1 EAGAIN (Resource temporarily unavailable)

recvmsg(17, 0x7fff33640550, 0)          = -1 EAGAIN (Resource temporarily unavailable)

clock_gettime(CLOCK_MONOTONIC, {1649, 22879270}) = 0

select(9, [3 4 8], [], [], {0, 3000})   = 0 (Timeout)

read(4, 0x7fff33640280, 16)             = -1 EAGAIN (Resource temporarily unavailable)

clock_gettime(CLOCK_MONOTONIC, {1649, 27182245}) = 0

--- SIGSEGV (Segmentation fault) @ 0 (0) ---

+++ killed by SIGSEGV +++

Speicherzugriffsfehler

From that moment on even after restarting phoneuid I only get timeouts from the phoneui-apps without seeing a GUI.

Quote:

Originally Posted by sulu (Post 1426139)

libevas1-engines-x and libevas1-engine-fb were not installed and after instaling the latter the above problem disappeared.

I'm not a maintainer of those packages in Debian, but looks like I'll have to work on them somehow, as it seems they don't build with newer elementary anymore and are threatened to be removed from testing suite :/ No idea if previous maintainers are still interested in working on them.

Quote:

Originally Posted by sulu (Post 1426139)

A second problem seems to be that phoneuid doesn't run stable. About 5 seconds after starting phoneui-quick-settings phoneuid segfaulted:

That's because you're probably missing fso-frameworkd (Python FSO implementation) and/or proper config to it (and I guess it's the config). SHR apps rely on some daemons (opimd, opreferencesd, and possibly oeventsd) that weren't reimplemented in Vala. And unfortunately, looks like there's no usable default config for frameworkd in Debian packages...

Try to save this file as /etc/frameworkd.conf :
http://git.freesmartphone.org/?p=fra...70e1e3;hb=HEAD

...but libphone-ui-shr segfaulting due to missing opreferencesd is indeed a bug and I can reproduce it here after stopping frameworkd. Thanks!

fso-frameworkd is installed but I had indeed no config.
I saved the file in /etc (and in /etc//om-gta02 as the link suggests) and rebooted the VM.
But according to strace neither the deamon nor the UI applications try to read the config file.

It seems like phoneuid needs quite a while until it accepts connections from the UI applications. If I start one within 30 seconds after starting the deamon I still get the timeout. If I wait two minutes phoneui-quick-settings comes up and I can switch the autodimming slider. However, after another two minutes this window is unresponsive and I get timeouts again when starting new UI applications (for example from the dialer).
I don't see a pattern.

Quote:

Originally Posted by sulu (Post 1426150)

Do you have fsodeviced and fsousaged installed? Are they running?

Autodim and autosuspend sliders use them both, so they might act badly if they're missing.

This software was developed for SHR distro and distro-wise it's easier to ensure that everything needed is in place. Also, libphone-ui-shr isn't the most beautiful piece of code on Earth... I'm planning to rewrite it in some spare time, but there's already a lot of entries on my todo list :c

Quote:

Originally Posted by dos1 (Post 1426151)

Do you have fsodeviced and fsousaged installed? Are they running?

I'll check that in the evening.

Quote:

Originally Posted by dos1 (Post 1426151)

This software was developed for SHR distro and distro-wise it's easier to ensure that everything needed is in place.

I realize that. I will try to reproduce this in a fresh VM or probably even on real HW if you think that matters. But I won't be able to do that until the weekend.

btw: (of course) I've seen complaints about a missing modem in some of the strace outputs but I don't know how to reproduce them so I can't give you the exact message.
Maybe that's a point to look into because it's an unusual setup for a phoning suite and might need some testing.

Quote:

Originally Posted by dos1 (Post 1426151)

Also, libphone-ui-shr isn't the most beautiful piece of code on Earth... I'm planning to rewrite it in some spare time, but there's already a lot of entries on my todo list :c

Don't put too much effort in this right now! I'm just playing at the moment.

Quote:

Originally Posted by sulu (Post 1426175)

Don't put too much effort in this right now! I'm just playing at the moment.

I'm using this code on my phone every day, and some code mainternance is long overdue :)

BTW. You can try to use ofono-phonesim to simulate the modem.

Feel free to ask in case of problems. You can easily catch me on IRC ;)

Quote:

Originally Posted by dos1 (Post 1426151)

Do you have fsodeviced and fsousaged installed? Are they running?

Both were installed and running when I booted the VM yesterday evening.
The SHR lock screen came up automatically after some idle time and I could deactivate it via the autodim slider. So apparently this part is working.
But it took about 2-3 minutes after the boot again until the daemon seemed to be able to answer to any client programs. And it seems if you forcefully kill some client the daemon becomes unresponsive again.

Quote:

Originally Posted by dos1 (Post 1426151)

This software was developed for SHR distro and distro-wise it's easier to ensure that everything needed is in place.

I'm not sure I understand what you want to say here.

Quote:

Originally Posted by dos1 (Post 1426180)

I'm using this code on my phone every day, and some code mainternance is long overdue :)

Just a long-term wishlist item:
Depending on how extensively you'll rework the code, I'd love to see some simple CLI interfaces like these:

Code:

phonecli-dialer -call »phone number«

phonecli-messages -send »phone number« < »some text file«

phonecli-contacts -getnumber »some name«

The GUI could then just be an interface for these CLI tools.

Quote:

Originally Posted by dos1 (Post 1426180)

BTW. You can try to use ofono-phonesim to simulate the modem.

Thanks! I'll try that.

Quote:

Originally Posted by dos1 (Post 1426180)

Feel free to ask in case of problems. You can easily catch me on IRC ;)

Thanks for the offer, but I have an aversion against chats.

Quote:

Originally Posted by sulu (Post 1426303)

[...]
Just a long-term wishlist item:
Depending on how extensively you'll rework the code, I'd love to see some simple CLI interfaces like these:

Code:

phonecli-dialer -call »phone number«

phonecli-messages -send »phone number« < »some text file«

phonecli-contacts -getnumber »some name«

The GUI could then just be an interface for these CLI tools.
[...]

Or rather have the library or deamon providing functions for this stuff and have cli and gui clients which only use the function .so file or connect to deamon ;) That would be even more universal, as it would give some API for other apps without installing additional stuff on the phone ;) (unless it already works like that and one of the deamons you're talking about provides all that functionality and the gui interface is only a client, then please correct me)

Quote:

Originally Posted by sulu (Post 1426303)

Depending on how extensively you'll rework the code, I'd love to see some simple CLI interfaces like these:

Code:

phonecli-dialer -call »phone number«

phonecli-messages -send »phone number« < »some text file«

phonecli-contacts -getnumber »some name«

The GUI could then just be an interface for these CLI tools.

Code:

mdbus2 -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.Call.Initiate "»phone number«" "voice"



mdbus2 -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.SMS.SendTextMessage »phone number«" "»some text«" true



opimd-cli contacts query Name »some name«

Should be pretty simple to wrap into some bash scripts or whatever :) The only thing more complicated than one dbus call is opimd query, but I've written a handy CLI interface in Python for it long time ago: http://git.shr-project.org/git/?p=op...0e7b02;hb=HEAD

(and mdbus2 is a very nice dbus tool. You could do the same with dbus-send, but mdbus2 has simplier syntax and amazing interactive mode with autocompletion :))

Let me explain the architecture of FSO/SHR system a bit:

FSO daemons (fsogsmd, fsodeviced, fsousaged, etc.) talk directly with the hardware and provide a dbus API for other apps to use. So, for instance, fsogsmd exports an API for basic stuff like "send message", "initiate a call", "release a call", definies signals for "incoming message", "incoming call" etc. and other applications can use that API to talk with the modem, no matter which modem it is (as long as it's supported by FSO).
So FSO daemons are "servers" here.

Then, there are SHR apps. Here it's a bit more complicated, as there are both servers and clients, even simultaneously.

phoneuid - it's a daemon that runs the UI stuff. It's also a server that exports its own dbus API. phoneuid actually does nothing else than displaying particular UI screen when requested to do so. You can use this API in your app to, for instance, request user to add a number to his contact book (as opposed to doing it for him via using FSO's opimd directly).

What's interesting - phoneuid doesn't have its UI implemented in it. It's modular - it can use a different library for every screen (like contacts, messages, dialer etc.) and it's configurable by the user in config file. By default it uses libphone-ui-shr (which uses E17 libs) for everything, but you could write your own library - and it doesn't matter if it would use GTK+, Qt or dunno what else instead. UI libraries use standard FSO API to perform actions, just like the mdbus2 calls above.

And the last one:

phonefsod - the binding between FSO and SHR. This is a daemon that listens on FSO signals and reacts accordingly by launching phoneuid actions. For instance, when FSO reports incoming call, phonefsod calls org.shr.phoneui.CallManagement.DisplayIncoming and phoneuid displays a "incoming call" window as implemented in libphone-ui-shr. Or, when FSO reports timeout on inactivity, phonefsod calls org.shr.phoneui.IdleScreen.Display, and phoneuid displays the lock screen.

There are also phoneui-apps (like phoneui-contacts, phoneui-dialer etc.), but those are just thin wrappers on single dbus calls and can be easily replaced with mdbus2 invocations.

I suppose we're drifting a bit away from the topic in this thread, but hopefully this helps a bit... and maybe someone will decide to give it a go and will become a SHR developer - there's A LOT of stuff to do, so it's a perfect opportunity to learn when hacking on interesting stuff! :D

Quote:

Originally Posted by sulu (Post 1426303)

Just a long-term wishlist item:
Depending on how extensively you'll rework the code, I'd love to see some simple CLI interfaces like these:

Code:

phonecli-dialer -call »phone number«

phonecli-messages -send »phone number« < »some text file«

phonecli-contacts -getnumber »some name«

http://wiki.maemo.org/Phone_control#Make_a_phone_call
http://wiki.maemo.org/Phone_control#Send_SMS
http://maemo.cloud-7.de/maemo5/usr/local/bin/contact2

cheers
jOERG