Re: [SailfishDevel] Question about connecting a Sailfish phone to Ubuntu Linux box
Hello Sahlan, > [...] I did that in QtCreator and chose the Build / Deploy option, and it > told me RPMs had been created OK, but, under the Issues tab, I get the > message "No RPM validation suite is available for the current Sailfish > OS build target, the package will not be validated" > > Then I clicked Debug / Start and Break on Main, but nothing happens. > I've searched for info on how to debug on Sailfish with QtCreator but > haven't found anything. Can anyone suggest a url for a step by step page > of instructions? Check https://sailfishos.org/wiki/Application_SDK_Your_First_App, scroll down to "Set ARM Kit to Deploy to Device" and read through the end of the page (known issue: the page layout is somehow broken right now). By default the "Build RPM Package for Manual Deployment" deployment method includes the "RPM Validation" step. Your build targets (3.0.0.8) are too old and does not come with any RPM validation suite, hence the warning. Try with a more recent build target after you upgrade your phone. BR, Martin ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Question about connecting a Sailfish phone to Ubuntu Linux box
Sahlan, There is a potential routing issue, you have the same network connected to different devices (usb networking and vm/dev networks) so the machine may end up sending packets over one interface but not the other and vice versa. It's not advisable in general to work like that since you are making trouble shooting that much harder for yourself because you now have to account for unpredictable and undefined network behavior. Regards, Eli Op di 23 jul. 2019 om 23:29 schreef Sahlan : > Eli, > > My development PCs and VMs running on OSX (about twelve in total) each > use a static i.p. address from that range, but not the 192.168.2.15 address > that the phone is currently set to. No devices use DHCP. Are you saying > there might still be a clash with an address used by the Jolla subnet of > which I won't be aware? Tomorrow I will install arp-scan to see if it can > pick up an address clash problem. I will also try making a connection by > wi-fi instead of usb, as the phone reports wifi as being on the 192.168.3.x > subnet. When I added the Jolla phone, it reported success, but, as I said > in my second email, the Debug / Start and Break on Main does not seem to be > working. > > Regards, > > Sahlan > > -- Original Message -- > From: "E.S. Rosenberg" > To: "Sahlan" ; "Sailfish OS Developers" < > devel@lists.sailfishos.org> > Sent: 23/07/2019 19:38:41 > Subject: Re: [SailfishDevel] Question about connecting a Sailfish phone to > Ubuntu Linux box > > Sahlan, > Did you change your LAN to not be on 192.168.2.0/24? > As mentioned previously your LAN IPs clash with the Jolla USB subnet and > this *will* lead to unpredictable behavior. > HTH, > Eliyahu - אליהו > > Op di 23 jul. 2019 om 18:59 schreef Sahlan : > >> Hello, >> >> Thanks to the several people who gave advice on my problem, I have made >> progress. >> a) I updated my Jolla phone to the latest update it was offering: 3.0.0.8 >> b) I updated VirtualBox on Ubuntu to the new version 6 >> c) I uninstalled and reinstalled the Sailfish SDK, same version as >> before, 2.1.1, but this time I ticked the boxes to add images for my >> updated phone OS, 3.0.0.8 >> d) I made no changes to my settings for the phone Developer Mode, but I >> did open the terminal and issue the command devel-su >> e) Now, when I tried to add the phone hardware, the result was successful. >> >> I then built a skeleton Sailfish app in Qt Creator with the phone being >> the target. I added no code to the default code created. As you would >> expect, it builds fine. Now I am confused as what to do next. In >> Xamarin-Android development one naturally proceeds to the deploy stage, so >> I did that in QtCreator and chose the Build / Deploy option, and it told me >> RPMs had been created OK, but, under the Issues tab, I get the message "No >> RPM validation suite is available for the current Sailfish OS build target, >> the package will not be validated" >> >> Then I clicked Debug / Start and Break on Main, but nothing happens. >> I've searched for info on how to debug on Sailfish with QtCreator but >> haven't found anything. Can anyone suggest a url for a step by step page of >> instructions? >> >> PS Having updated my phone to 3.0.0.8, I see a message telling me >> 3.1.0.11 is available. I wonder if it is going to work its way >> incrementally through the available updates :) >> >> Regards, >> >> Sahlan >> >> -- Original Message -- >> From: "David Llewellyn-Jones" >> To: devel@lists.sailfishos.org >> Sent: 19/07/2019 11:04:27 >> Subject: Re: [SailfishDevel] Question about connecting a Sailfish phone >> to Ubuntu Linux box >> >> On 19/07/2019 12:27, Sahlan wrote: >> [snip] >> >> I have >> purchased a phone which is running Sailfish 3 and have set up Developer >> Mode on it. On Ubuntu 18.04 LTS, I installed the Sailfish Qt Creator IDE >> and built a simple test app. >> >> >> Which phone are you using? Did you flash it over USB to install >> Sailfish? Your setup with Ubuntu is pretty standard, so it should work. >> >> It's an obvious question, but did you, activate the Remote connection >> option, and give yourself a root password? >> >> >> https://jolla.zendesk.com/hc/en-us/articles/202011863-How-to-enable-Developer-Mode >> >> >> I connected the Sailfish phone via USB and >> confirmed with lsusb that the device is recognised as being connected. >> Under Tools / Options / Devices, I try to add the phone as a Sailfish OS >> Physical Device. The IP address, username and password correctly >> correspond to those on the phone, but clicking "Test Connection" always >> gives me the message "Host unreachable". Increasing the SSH timeout does >> not help. I also tried pinging the i.p. address of the phone from a >> terminal window, and it is not found, though I am not sure whether ping >> should work with i.p. over usb. >> >> >> Pinging should work over USB, and personally I'd focus on getting that >> to work first, since until you can ping it's unlikely ssh will work. >> >> It
Re: [SailfishDevel] Question about connecting a Sailfish phone to Ubuntu Linux box
Eli, My development PCs and VMs running on OSX (about twelve in total) each use a static i.p. address from that range, but not the 192.168.2.15 address that the phone is currently set to. No devices use DHCP. Are you saying there might still be a clash with an address used by the Jolla subnet of which I won't be aware? Tomorrow I will install arp-scan to see if it can pick up an address clash problem. I will also try making a connection by wi-fi instead of usb, as the phone reports wifi as being on the 192.168.3.x subnet. When I added the Jolla phone, it reported success, but, as I said in my second email, the Debug / Start and Break on Main does not seem to be working. Regards, Sahlan -- Original Message -- From: "E.S. Rosenberg" To: "Sahlan" ; "Sailfish OS Developers" Sent: 23/07/2019 19:38:41 Subject: Re: [SailfishDevel] Question about connecting a Sailfish phone to Ubuntu Linux box Sahlan, Did you change your LAN to not be on 192.168.2.0/24? As mentioned previously your LAN IPs clash with the Jolla USB subnet and this *will* lead to unpredictable behavior. HTH, Eliyahu - אליהו Op di 23 jul. 2019 om 18:59 schreef Sahlan : Hello, Thanks to the several people who gave advice on my problem, I have made progress. a) I updated my Jolla phone to the latest update it was offering: 3.0.0.8 b) I updated VirtualBox on Ubuntu to the new version 6 c) I uninstalled and reinstalled the Sailfish SDK, same version as before, 2.1.1, but this time I ticked the boxes to add images for my updated phone OS, 3.0.0.8 d) I made no changes to my settings for the phone Developer Mode, but I did open the terminal and issue the command devel-su e) Now, when I tried to add the phone hardware, the result was successful. I then built a skeleton Sailfish app in Qt Creator with the phone being the target. I added no code to the default code created. As you would expect, it builds fine. Now I am confused as what to do next. In Xamarin-Android development one naturally proceeds to the deploy stage, so I did that in QtCreator and chose the Build / Deploy option, and it told me RPMs had been created OK, but, under the Issues tab, I get the message "No RPM validation suite is available for the current Sailfish OS build target, the package will not be validated" Then I clicked Debug / Start and Break on Main, but nothing happens. I've searched for info on how to debug on Sailfish with QtCreator but haven't found anything. Can anyone suggest a url for a step by step page of instructions? PS Having updated my phone to 3.0.0.8, I see a message telling me 3.1.0.11 is available. I wonder if it is going to work its way incrementally through the available updates :) Regards, Sahlan -- Original Message -- From: "David Llewellyn-Jones" To: devel@lists.sailfishos.org Sent: 19/07/2019 11:04:27 Subject: Re: [SailfishDevel] Question about connecting a Sailfish phone to Ubuntu Linux box On 19/07/2019 12:27, Sahlan wrote: [snip] I have purchased a phone which is running Sailfish 3 and have set up Developer Mode on it. On Ubuntu 18.04 LTS, I installed the Sailfish Qt Creator IDE and built a simple test app. Which phone are you using? Did you flash it over USB to install Sailfish? Your setup with Ubuntu is pretty standard, so it should work. It's an obvious question, but did you, activate the Remote connection option, and give yourself a root password? https://jolla.zendesk.com/hc/en-us/articles/202011863-How-to-enable-Developer-Mode I connected the Sailfish phone via USB and confirmed with lsusb that the device is recognised as being connected. Under Tools / Options / Devices, I try to add the phone as a Sailfish OS Physical Device. The IP address, username and password correctly correspond to those on the phone, but clicking "Test Connection" always gives me the message "Host unreachable". Increasing the SSH timeout does not help. I also tried pinging the i.p. address of the phone from a terminal window, and it is not found, though I am not sure whether ping should work with i.p. over usb. Pinging should work over USB, and personally I'd focus on getting that to work first, since until you can ping it's unlikely ssh will work. It might also be worth trying to ping in the opposite direction (i.e pinging your computer from the phone over USB) by opening a console on the phone and using something like this: su-devel ping 192.16.2.6 Some of the advice on this page may also be useful (if not now, then once you have a connection!): https://sailfishos.org/wiki/Sailfish_OS_Cheat_Sheet David -- Website: http://www.flypig.co.uk ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to
Re: [SailfishDevel] Question about connecting a Sailfish phone to Ubuntu Linux box
Sahlan, Did you change your LAN to not be on 192.168.2.0/24? As mentioned previously your LAN IPs clash with the Jolla USB subnet and this *will* lead to unpredictable behavior. HTH, Eliyahu - אליהו Op di 23 jul. 2019 om 18:59 schreef Sahlan : > Hello, > > Thanks to the several people who gave advice on my problem, I have made > progress. > a) I updated my Jolla phone to the latest update it was offering: 3.0.0.8 > b) I updated VirtualBox on Ubuntu to the new version 6 > c) I uninstalled and reinstalled the Sailfish SDK, same version as before, > 2.1.1, but this time I ticked the boxes to add images for my updated phone > OS, 3.0.0.8 > d) I made no changes to my settings for the phone Developer Mode, but I > did open the terminal and issue the command devel-su > e) Now, when I tried to add the phone hardware, the result was successful. > > I then built a skeleton Sailfish app in Qt Creator with the phone being > the target. I added no code to the default code created. As you would > expect, it builds fine. Now I am confused as what to do next. In > Xamarin-Android development one naturally proceeds to the deploy stage, so > I did that in QtCreator and chose the Build / Deploy option, and it told me > RPMs had been created OK, but, under the Issues tab, I get the message "No > RPM validation suite is available for the current Sailfish OS build target, > the package will not be validated" > > Then I clicked Debug / Start and Break on Main, but nothing happens. I've > searched for info on how to debug on Sailfish with QtCreator but haven't > found anything. Can anyone suggest a url for a step by step page of > instructions? > > PS Having updated my phone to 3.0.0.8, I see a message telling me 3.1.0.11 > is available. I wonder if it is going to work its way incrementally through > the available updates :) > > Regards, > > Sahlan > > -- Original Message -- > From: "David Llewellyn-Jones" > To: devel@lists.sailfishos.org > Sent: 19/07/2019 11:04:27 > Subject: Re: [SailfishDevel] Question about connecting a Sailfish phone to > Ubuntu Linux box > > On 19/07/2019 12:27, Sahlan wrote: > [snip] > > I have > purchased a phone which is running Sailfish 3 and have set up Developer > Mode on it. On Ubuntu 18.04 LTS, I installed the Sailfish Qt Creator IDE > and built a simple test app. > > > Which phone are you using? Did you flash it over USB to install > Sailfish? Your setup with Ubuntu is pretty standard, so it should work. > > It's an obvious question, but did you, activate the Remote connection > option, and give yourself a root password? > > > https://jolla.zendesk.com/hc/en-us/articles/202011863-How-to-enable-Developer-Mode > > > I connected the Sailfish phone via USB and > confirmed with lsusb that the device is recognised as being connected. > Under Tools / Options / Devices, I try to add the phone as a Sailfish OS > Physical Device. The IP address, username and password correctly > correspond to those on the phone, but clicking "Test Connection" always > gives me the message "Host unreachable". Increasing the SSH timeout does > not help. I also tried pinging the i.p. address of the phone from a > terminal window, and it is not found, though I am not sure whether ping > should work with i.p. over usb. > > > Pinging should work over USB, and personally I'd focus on getting that > to work first, since until you can ping it's unlikely ssh will work. > > It might also be worth trying to ping in the opposite direction (i.e > pinging your computer from the phone over USB) by opening a console on > the phone and using something like this: > > su-devel ping 192.16.2.6 > > Some of the advice on this page may also be useful (if not now, then > once you have a connection!): > > https://sailfishos.org/wiki/Sailfish_OS_Cheat_Sheet > > David > -- > Website: http://www.flypig.co.uk > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Question about connecting a Sailfish phone to Ubuntu Linux box
Hello, Thanks to the several people who gave advice on my problem, I have made progress. a) I updated my Jolla phone to the latest update it was offering: 3.0.0.8 b) I updated VirtualBox on Ubuntu to the new version 6 c) I uninstalled and reinstalled the Sailfish SDK, same version as before, 2.1.1, but this time I ticked the boxes to add images for my updated phone OS, 3.0.0.8 d) I made no changes to my settings for the phone Developer Mode, but I did open the terminal and issue the command devel-su e) Now, when I tried to add the phone hardware, the result was successful. I then built a skeleton Sailfish app in Qt Creator with the phone being the target. I added no code to the default code created. As you would expect, it builds fine. Now I am confused as what to do next. In Xamarin-Android development one naturally proceeds to the deploy stage, so I did that in QtCreator and chose the Build / Deploy option, and it told me RPMs had been created OK, but, under the Issues tab, I get the message "No RPM validation suite is available for the current Sailfish OS build target, the package will not be validated" Then I clicked Debug / Start and Break on Main, but nothing happens. I've searched for info on how to debug on Sailfish with QtCreator but haven't found anything. Can anyone suggest a url for a step by step page of instructions? PS Having updated my phone to 3.0.0.8, I see a message telling me 3.1.0.11 is available. I wonder if it is going to work its way incrementally through the available updates :) Regards, Sahlan -- Original Message -- From: "David Llewellyn-Jones" To: devel@lists.sailfishos.org Sent: 19/07/2019 11:04:27 Subject: Re: [SailfishDevel] Question about connecting a Sailfish phone to Ubuntu Linux box On 19/07/2019 12:27, Sahlan wrote: [snip] I have purchased a phone which is running Sailfish 3 and have set up Developer Mode on it. On Ubuntu 18.04 LTS, I installed the Sailfish Qt Creator IDE and built a simple test app. Which phone are you using? Did you flash it over USB to install Sailfish? Your setup with Ubuntu is pretty standard, so it should work. It's an obvious question, but did you, activate the Remote connection option, and give yourself a root password? https://jolla.zendesk.com/hc/en-us/articles/202011863-How-to-enable-Developer-Mode I connected the Sailfish phone via USB and confirmed with lsusb that the device is recognised as being connected. Under Tools / Options / Devices, I try to add the phone as a Sailfish OS Physical Device. The IP address, username and password correctly correspond to those on the phone, but clicking "Test Connection" always gives me the message "Host unreachable". Increasing the SSH timeout does not help. I also tried pinging the i.p. address of the phone from a terminal window, and it is not found, though I am not sure whether ping should work with i.p. over usb. Pinging should work over USB, and personally I'd focus on getting that to work first, since until you can ping it's unlikely ssh will work. It might also be worth trying to ping in the opposite direction (i.e pinging your computer from the phone over USB) by opening a console on the phone and using something like this: su-devel ping 192.16.2.6 Some of the advice on this page may also be useful (if not now, then once you have a connection!): https://sailfishos.org/wiki/Sailfish_OS_Cheat_Sheet David -- Website: http://www.flypig.co.uk ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SyncML topic revived (further down the rabbit hole)
Chris Adams wrote: > Hi, > > (Sorry for top posting, OWA doesn't quote properly...) > > That old PR is actually mine, if you're referring to > https://git.merproject.org/mer-core/buteo-sync-plugins/merge_requests/1 > > I think it had some issues (e.g. didn't do UUID matching properly between > client and server, so it was more of an "import" rather than a true "sync" > IIRC), which is why it wasn't merged. Subsequent syncs might cause > duplication, or changes might not be propagated properly, in one direction > or the other. I don't recall precisely. > Do you mean the calendar part? We'll test for sure all of this before approaching you with MR. > Going forward: my personal opinion is that if you can make the required > changes to the stack to get everything working, we'd definitely like to > integrate those changes, as it would ensure that we have more parts of our > stack up-to-date, and less dead-code. > Thumbs up and fingers crossed! Thank you! > That said, at this stage I don't believe that it's high priority > internally, so not sure how much time/effort sailors will be able to spend > helping with this effort, unfortunately. Definitely can review and test, > but may not be able to help with active development day to day. But am > always happy to discuss etc (ping chriadam on freenode IRC in .au > timezone, or perhaps flypig or pvuorela in .fi timezone). As my previous posts were not showing on the dev list, I write here to test if it works. In any case I'll be glad to receive some advises and review on the progress done. What I did is to - rebase btcalendar on current master and add latest changes - remove bluez4 from buteo-syncfw and buteo-sync-plugins - replace what needed with bluez5 and - had "a lot of fun" getting the plugins running. Now it works, but has few things to polish and of course to test. It will be indeed wonderful if someone could help with review and advise in the process. Thank you in advance ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] libconnman-qt application examples
On 22/07/2019 23:57, David Weidenkopf wrote: > Sorry, I forgot to mention an assumption on my part. Given the API > design, it looks like it is usable from QML, and no C++ would be > necessary. Is that an incorrect assumption? Hi David, I'm struggling a bit with your negatives, but... no, this is a *correct* assumption! You can use libconnman-qt as a C++ library, but it also works as a QML plugin by adding "import MeeGo.Connman 0.2" at the top of your QML file. > Hi, we are interested in adopting libconnman-qt as our interface to > connman. Where can I find examples of usage? For example, I would like > to see how the library could be used to present a list of SSIDs to a > user. It is not clear from the API how to do this. If you're interested in the QML side of things, then the Settings app is a good place to start (jolla-settings-networking). It's not open source, but you can find the relevant QML files directly on a Sailfish device (or the emulator). For example, this file provides the UI for the main WLAN settings page: /usr/share/jolla-settings/pages/wlan/mainpage.qml This lists your saved WLAN networks. It does this using the SavedServiceModel model, which is a QAbstractListModel, and so can be plugged straight in to a ListView (or any of the related Qt repeaters). Look out for TechnologyModel, SavedServiceModel, NetworkTechnology and NetworkManager around lines 225-253 of the file, which are all from libconnman-qt. If you want to manipulate things more specifically, the NetworkManager provides access to NetworkService objects, and each NetworkService object provides details of a network (e.g. its name, its domain, whether it's connected, etc.). NetworkManager and NetworkService are basically wrappers around their respective connman dbus interfaces: https://git.merproject.org/mer-core/connman/blob/master/connman/doc/manager-api.txt https://git.merproject.org/mer-core/connman/blob/master/connman/doc/service-api.txt Another place to look would be in this file from lipstick-jolla-home, which provides the Wifi connection selector dialogue: /usr/share/lipstick-jolla-home-qt5/connectivity/ConnectionSelector.qml Somewhere around line 918 you can see the TechnologyModel which is used to populate the list shown to the user. There may be other better or open source examples, but these are the two that spring to mind. Getting a simple QML interface that shows saved Wifi connections should be relatively straightforward using these models. David -- Website: http://www.flypig.co.uk ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SyncML topic revived (further down the rabbit hole)
Hi, (Sorry for top posting, OWA doesn't quote properly...) That old PR is actually mine, if you're referring to https://git.merproject.org/mer-core/buteo-sync-plugins/merge_requests/1 I think it had some issues (e.g. didn't do UUID matching properly between client and server, so it was more of an "import" rather than a true "sync" IIRC), which is why it wasn't merged. Subsequent syncs might cause duplication, or changes might not be propagated properly, in one direction or the other. I don't recall precisely. Going forward: my personal opinion is that if you can make the required changes to the stack to get everything working, we'd definitely like to integrate those changes, as it would ensure that we have more parts of our stack up-to-date, and less dead-code. That said, at this stage I don't believe that it's high priority internally, so not sure how much time/effort sailors will be able to spend helping with this effort, unfortunately. Definitely can review and test, but may not be able to help with active development day to day. But am always happy to discuss etc (ping chriadam on freenode IRC in .au timezone, or perhaps flypig or pvuorela in .fi timezone). Best regards, Chris. From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Damien Caliste [dcali...@free.fr] Sent: Saturday, July 20, 2019 9:16 PM To: devel@lists.sailfishos.org Subject: Re: [SailfishDevel] SyncML topic revived (further down the rabbit hole) Hello, Le Samedi 20 juillet 2019, Tone Kastlunger a écrit : > buteo-sync-plugin tho, > so I suppose expectations for a more extensive changeset to be merged > upstream should be kept low? I'm afraid it's a question of poking. Submitter should ask for reason of silence or rejection up to getting an answer. I agree it's not nice. But Pekka or Chris always gave answers to my MRs in the past. Sometimes rejecting them but always with reasons and after discussion. So for this case, we can be optimistic! Have a nice day, Damien. ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
