| neochapay_home | yeaaaaaaaaa we have pulseaudio 12 | 08:29 |
|---|---|---|
| neochapay_home | and new favicon on obs ^_^ | 08:29 |
| Leif_Erikson | Hello Nemo friends. I wont to go on with the Nemo Mobile evaluation and have some questions. | 10:58 |
| Leif_Erikson | I manages to install the Glacier UX and the most core apps, that have been build with OBS. | 10:59 |
| Leif_Erikson | Now I want to evaluate the Messages app. I get the build error "glacierapp development package not found" | 10:59 |
| Leif_Erikson | This is not surprising. Which repository do I have to add to my build engine and which library (exact name) do I have to install? | 11:00 |
| Leif_Erikson | I think I have to add any repository with "ssu ar" to my build engine as a root user. | 11:01 |
| Leif_Erikson | My second question is, how I can evaluate a pure Nemo Mobile? | 11:02 |
| Leif_Erikson | I would like to test, which apps are running on Memo Mobile. I assume, that Sailfish apps won't start or crash because of missing Silica. | 11:03 |
| Leif_Erikson | If I select Nemo Mobile apps ans Openrepos.net nothing is shown. | 11:04 |
| vknecht | Leif_Erikson, I've tried to get write a kickstart file for my device which would install only required parts for Nemo, but I guess some important stuff is not pulled in anymore (like net-tools and busybox-static) so it only bootloops for now | 11:08 |
| vknecht | http://merproject.org/logs/%23nemomobile/%23nemomobile.2019-03-17.log.html | 11:08 |
| vknecht | also I'm not sure if the hw adaptation really has to be built with a mer target instead of a sailfishos one | 11:09 |
| vknecht | (like in the blog post example for hammerhead) | 11:10 |
| r0kk3rz | aside from nemo developed ones, i dont think there are any nemo apps | 11:15 |
| Leif_Erikson | If I understand correctly the linked chat archive includes a reference to a script to build an image for hammerhead, but if you flash the device with the image it get stuck in an infinite boot loop? | 11:20 |
| Leif_Erikson | You say, that no apps other than the glacier apps are running on Nemo Mobile? | 11:21 |
| Leif_Erikson | I realised, that you didn't include the messaging app in your script. do you have an idea, how to build the app? | 11:21 |
| vknecht | Leif_Erikson, no, the script is based on idol3 kickstart for sfos (with package list "unrolled" and excluding jolla ones) and this glacier kickstart https://gist.github.com/neochapay/59d7ac23691f97b683104c93aff23266 | 11:27 |
| T4 | <meierrom> Didn't Rinigus port puremaps? | 11:29 |
| vknecht | mentionned hammerhead wrt. https://neochapay.ru/blogs/zapiski-utkonosa-programmista/instructions-to-update-nexus5-to-latest-.html line 7 with "adapt-mer" | 11:31 |
| T4 | <meierrom> Having a silica mapper would increase the number of nemo apps considerably. | 11:32 |
| T4 | <DibyaXP> I guess you mean wrapper | 11:32 |
| T4 | <meierrom> No. Nemo should run without silica. However, the missing silica gui elements must be replaced. Sfos apps may still work thrn using mapping. | 11:38 |
| r0kk3rz | so make such a thing | 11:45 |
| Leif_Erikson | I think sich a wrapper or mapper from Silica to QtQuickcontrols-nemo would be mandatory for shipping Nemo Mobile. How many man month effort do you estimate? | 11:50 |
| Leif_Erikson | I think I have to read this document to understand, how to use the .ks file: https://sailfishos.org/content/uploads/2019/03/SailfishOS-HardwareAdaptationDevelopmentKit-3.0.1.0.pdf | 11:51 |
| Leif_Erikson | The HADK suggests, that the .ks file is related to a specific hardware isn't it? I the linked .ks file related to hammerhead? https://wiki.merproject.org/wiki/Nemo/Glacier | 11:52 |
| Leif_Erikson | Is there a more efficient way to test a pure Nemo Mobile? The linked blog entry of NeoChapay descripes just the installation of Glacier UX over Sailfish, doesn't it? This is what I have successfully done for an Intex Aqua Fish developer device. | 11:55 |
| Leif_Erikson | Dees a Nemo Mobile Image exist for any device? | 11:55 |
| Leif_Erikson | The Mer Wiki suggests, that only a Virtual Box Image exists. | 11:56 |
| Leif_Erikson | And from the i486 reference I conclude, that the instruction in the Mer Wiki is only for building a Virtual Box image: https://wiki.merproject.org/wiki/Nemo/Glacier | 11:57 |
| vknecht | that's what I'm trying to do ; afaik kickstart is the way to go for specific devices, with emulator/486 it's simpler because the base is the same, I suppose | 11:58 |
| vknecht | it's just that (afaics), when you exclude sfos specific packages, you then have to care about adding some required dependencies | 11:59 |
| vknecht | (like the net-tools and busybox I had to explicitly add in KS, so that boot could reach stage2/telnet 2323) | 12:00 |
| r0kk3rz | a kickstart is just a script for mic | 12:01 |
| Leif_Erikson | Sailfish OS has very rich add ons, not only the core apps, but also the settings, VPN, Android, Exchange ... So it would be important to check, which features would work with Nemo Mobile. | 12:02 |
| r0kk3rz | need a big nemo stuff meta-package to simplify the .ks | 12:02 |
| r0kk3rz | nemo isnt sailfish, android and exchange are right out | 12:04 |
| Leif_Erikson | Indeed. Nemo isn't Sailfish. Therefore just installing the Glacier UX is not sufficient for the evaluation of Nemo Mobile with its limits and potential. | 12:05 |
| Leif_Erikson | And I assume, that the most bugs I realised in the core Nemo apps, I have installed over Sailfish with Glacier UX are an impact of a different base system. | 12:06 |
| Leif_Erikson | I conclude. There is currently no available image of Nemo Mobile except the Virtual Box image, isn't it? vknecht is working on a .ks script for mic to create an image for hammerhead, doesn't he? | 12:08 |
| Leif_Erikson | And NeoChapay describes in his blog, how to install the Glacier UX over Sailfish. It's allmost the same instruction like in the Mer Wiki https://wiki.merproject.org/wiki/Nemo/Glacier/Installing#Installing with the difference, that he suggests to deinstall Silica, correct? | 12:10 |
| r0kk3rz | i wouldnt expect it to create any bugs in apps as such | 12:10 |
| r0kk3rz | there would likely be a lot more bugs in a clean nemo system | 12:11 |
| Leif_Erikson | Yesterday Marc posted a summary of my report. The core apps are very buggy on my Intex Aqua Fish with Glacier over Sailfish. | 12:12 |
| vknecht | Leif_Erikson, correct, except I'm not doing it for hammerhead (though it should just be a matter of changing adaptation repos, and package list a bit depending on patterns) | 12:12 |
| Leif_Erikson | We have installed the community port on a Nexus 5x. Works very good except the Bluetooth support. Let me know as soon you have a Nemo mobile Image. Amazon has still some Hammerhead devices. I would order one for the evaluation. | 12:14 |
| Leif_Erikson | Maybe you can post the advice or link to the image on the Mer wiki. | 12:14 |
| Leif_Erikson | Has someone a quick solution to test the message app? The glacierapp development package is missing for a build. | 12:15 |
| r0kk3rz | theres nothing special about the hammerhead :P | 12:18 |
| Leif_Erikson | Yes, it's a quite outdated device. But if someone can give me advice, how to build a Nemo Mobile image and flash the device, it would be worth to buy this old Nexus 5. | 12:20 |
| vknecht | https://build.merproject.org/package/show/home:neochapay:mer:nemo-devel-ux/libglacierapp | 12:20 |
| vknecht | https://build.merproject.org/package/binaries/home:neochapay:mer:nemo-devel-ux/libglacierapp?repository=latest_armv7hl | 12:21 |
| vknecht | posting the image I have would do any good, especially if you don't have an idol3 ;-) | 12:22 |
| vknecht | *wouldn't | 12:22 |
| Leif_Erikson | The links are pointing to the artefacts I need to build the messages app? | 12:25 |
| r0kk3rz | vknecht: just make sure you post your .ks somewhere | 12:25 |
| vknecht | you could reuse the ks, use suitable adaptation-community-* repos for your device, use https://build.merproject.org/package/view_file/nemo:devel:hw:$VENDOR:$DEVICE/_pattern/jolla-hw-adaptation-$DEVICE?expand=1 to create the expanded list of package | 12:26 |
| vknecht | r0kk3rz, sure, the kickstart is still at https://pastebin.com/tj3G607H | 12:27 |
| r0kk3rz | put it somewhere other than pastebin too | 12:27 |
| Leif_Erikson | So the .ks file is a kind of template for a script and I have to add links to resources of hardware adaption? | 12:32 |
| vknecht | kickstart is a silent install configuration for RPM based systems, where you specify packages to install and repositories from where to fetch them | 12:33 |
| vknecht | (and many more settings, and commands and scripts) | 12:34 |
| vknecht | https://gist.github.com/vknecht/a4c4a00ecbee472b6f3d7ed01e24509a | 12:40 |
| rinigus | meierrom: pure maps are ported to qtcontrols and kirigami. But should be relatively simple to port to nemo native, if such thing exists. I wouldn't worry about silica compatibility, active apps can be ported if there is interest | 14:40 |
| T4 | <samzn> nemo uses sighlty modified QtQuickControls, it's a standard unlike Kirigami | 14:48 |
| T4 | <meierrom> rinigus: active apps? | 14:49 |
| T4 | <meierrom> rinigus: you mean silica apps can usually easily be ported to nemo/glacier? | 14:52 |
| T4 | <meierrom> rinigus: and what about closed source apps, when dev is not interested? | 14:56 |
| T4 | <DibyaXP> Will it illegal to reverse engineer silica? | 15:04 |
| rinigus | meierrom: I mean the apps that actually are developed. And no, open source ones. If developer is not interested, there should be someone from community who will step up. | 15:07 |
| rinigus | As for reversing silica, it may make more sense to work with kirigami developers and get missing functionality from there | 15:08 |
| rinigus | samzn: just saw your reply. Then pure maps should work already. Just install it's dependencies, clone pure maps on device, run make platform-qtcontrols and run it using qmlscene | 15:15 |
| Leif_Erikson | I think we would need a solution to run apps, which use Silica, if our device comes with pre-installed Nemo Mobile. Consumers will expect an app store, that could be Storeman. | 15:38 |
| Leif_Erikson | The Silica API is well documented. Maybe we can develop a library, that maps QML types of Silica to the one of Nemo. | 15:39 |
| Leif_Erikson | I resume: Instructions to build an image with Nemo Mobile are available for Virtual Box. https://wiki.merproject.org/wiki/Nemo/Glacier | 15:41 |
| Leif_Erikson | vknecht is working on a .ks script to build an image for a physical device. This script is a kind of template and has to be edited for a specific device | 15:42 |
| Leif_Erikson | I have no idea, how to do that and which resources I have to link. I'll try to learn more with the documentation for Sailfish https://sailfishos.org/content/uploads/2019/03/SailfishOS-HardwareAdaptationDevelopmentKit-3.0.1.0.pdf | 15:44 |
| Leif_Erikson | I would welcome an update of the Mer wiki page with instructions for creating and deploying an image for a physical device. I could be a specific device, that is still available, so that we could buy one. | 15:46 |
| T4 | <DibyaXP> OnePlus 3T has Sailfish OS port | 15:46 |
| Leif_Erikson | The Plasma Mobile project has for example a very clear instruction, how to flash their legacy device to get Plasma Mobile. | 15:47 |
| Leif_Erikson | Yes, there are some ports available. Beyond official devices of Jala and Intex, we are using a Nexus 5x with a community port of Sailfish. | 15:48 |
| Leif_Erikson | I also would buy immediately a OnePlus phone, if someone can tell me, how to flash this device with a pure Nemo Mobile image. | 15:49 |
| T4 | <DibyaXP> Pure Nemo? That might not be possible yet | 15:50 |
| Leif_Erikson | Yes, with the help of this great community, I learned how to install Glacier UX and the standard app on Sailfish OS. But my impression is, that this is not sufficient to evaluate Nemo Mobile as a platform for our product. | 15:52 |
| T4 | <DibyaXP> Licensing sailfish os is kinda impossible so we wish the same | 15:53 |
| Leif_Erikson | That's the point. We would like to license Sailfish OS, but it's unlikely that Jolla will offer an agreement. So we evaluate Nemo Mobile as an option. | 15:57 |
| Leif_Erikson | We also evaluate UBports. It's more mature and robust, but the UX is poor in our point of view. Glacier UX is good point to start. | 15:59 |
| Leif_Erikson | I will play around with removing Sailfish libraries and apps from the developer device. At least I would like to see, how the system behaves if I deinstall Silica as NeoChapay suggests in his blog. | 16:00 |
| Leif_Erikson | And I would like to build and deploy the messaging app of Nemo. | 16:01 |
| Leif_Erikson | To resolve the build error; I have to add some repositories to the build engine as root first, I think. | 16:02 |
| Leif_Erikson | Which command do I have to use? Is it the following for Sailfish device? ssu ar libglacierapp http://repo.merproject.org/obs/home:/neochapay:/mer:/nemo-devel-ux/latest_armv7hl/ | 16:11 |
| Leif_Erikson | My build error is: glacierapp development package not found | 16:12 |
| Leif_Erikson | Di I have to install the library with zypper afterwards? | 16:12 |
| Leif_Erikson | sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -m sdk-install zypper in libglacierapp | 16:13 |
| vknecht | Leif_Erikson, try with libglacierapp-devel | 16:16 |
| Leif_Erikson | No provider of 'libglacierapp-devel' found. | 16:18 |
| Leif_Erikson | I'll try a pkcon refresh | 16:18 |
| Leif_Erikson | This doesn't help. I assume I used the wrong ssu command | 16:19 |
| vknecht | ssu lr ? | 16:19 |
| vknecht | and maybe need to refresh with zypper | 16:20 |
| Leif_Erikson | https://pastebin.com/swP4cNuJ | 16:20 |
| * vknecht senses much wrong in there | 16:22 | |
| vknecht | global are for i486, and user repo for arm ? | 16:22 |
| vknecht | then, no need to add same repo twice | 16:23 |
| vknecht | and afaik you should use the mer-* and nemo-ux from my kickstart (and adapt to 486 if that's the device type you need) | 16:25 |
| vknecht | and not "nemo-devel-ux ... http://repo.merproject.org/obs/nemo:/devel:/ux/sailfish_latest_armv7hl/" | 16:25 |
| Leif_Erikson | I need arm | 16:27 |
| Leif_Erikson | the global repositories are the default ones, that I haven't configured myself. | 16:28 |
| vknecht | now, I don't know much about the sdk and emulator, if that's what you're using | 16:28 |
| Leif_Erikson | This are the avilable targets: https://pastebin.com/Pj0TyZnz | 16:29 |
| Leif_Erikson | The emulator is another vm. | 16:29 |
| Leif_Erikson | The listing was from the build engine. It's the platform sdk | 16:29 |
| Leif_Erikson | I just want to build and deploy the message app. This app is not included in the obs listing. | 16:30 |
| vknecht | I guess you'd have to add mer-{core,qt5,mw} and nemo-ux with correct arch to each target | 16:36 |
| Leif_Erikson | Mmmh. I'm a bit confused. The official repo seem to be http://repo.merproject.org/obs/nemo:/devel:/ux/sailfish_latest_armv7hl/, that is referenced at https://wiki.merproject.org/wiki/Nemo/Glacier/Installing#Installing | 16:42 |
| Leif_Erikson | In your .ks file you are referencing the repository of NeoChapay. His Glacier UX version is buggy. I can't makje phone calls with it. | 16:43 |
| vknecht | ah, well, couldn't go as far as to actually test it :) | 16:44 |
| vknecht | you should be able to change to whatever other version/build you want by changing the mer repos to match | 16:45 |
| vknecht | when in the obs of the nemo-ux you want, check "Advanced" then "Meta" tab | 16:46 |
| Leif_Erikson | It's so frustrating. If I add ssu ar nemo-devel-ux http://repo.merproject.org/obs/nemo:/devel:/ux/sailfish_latest_armv7hl/ and then zypper refresh and zypper se glacier, the system can't find anything | 17:04 |
| Leif_Erikson | If Follow the link of the repository libglacierapp is listed. | 17:06 |
| Leif_Erikson | If I try sb2 -t SailfishOS-3.0.1.11-armv7hl -R -m sdk-install zypper in libglacierapp-devel as a mersdk user I get the error No provider of 'libglacierapp-devel' found. | 17:08 |
| Leif_Erikson | It's like I'm poking around in a fog. A documentation would be really useful to increase the community for Nemo Mobile and to train new developers. A cheat sheet would be shown: The key commands to set up the sdk and build apps. | 17:17 |
| neochapay_home | Leif_Erikson: sb2 -t SailfishOS-3.0.1.11-armv7hl -R zypper lr | 17:27 |
| neochapay_home | and now i make bug update of my cory mer:core all is rebuild | 17:28 |
| neochapay_home | and why you search into http://repo.merproject.org/obs/nemo:/devel:/ux/sailfish_latest_armv7hl/ ? it's outdated | 17:30 |
| Leif_Erikson | It's the documented repo on the Mer Wiki page. | 17:32 |
| neochapay_home | oh....it's outdated to :)))) | 17:32 |
| Leif_Erikson | Mmmmh. Glacier is not listed, althought I have added the repo with the ssu command: https://pastebin.com/xgDMgYBx | 17:33 |
| Leif_Erikson | Where can I find the up to date documentation? | 17:34 |
| Leif_Erikson | I think, also the git project has moved at least one time. | 17:36 |
| neochapay_home | sb2 -t SailfishOS-3.0.1.11-armv7hl -R zypper ar URL NAME | 17:38 |
| *** piggz_ is now known as piggz | 17:41 | |
| Leif_Erikson | Thanks for posting the terminal command. This works I could install the library and could build and deploy the messages app. | 20:51 |
| Leif_Erikson | Unfortunately I couldn't test the app, because my SIM in locked and I have to unlock the SIM with my PIN, but theGlacier UX doesn't support this feature. The status bar says "no PIN required", but this is not true. | 20:54 |
| Leif_Erikson | By the way: this is the official up to date project? | 20:58 |
| Leif_Erikson | Thanks for the today's help! | 21:05 |
| r0kk3rz[m] | But do you understand why that worked? It seems like you don't understand how that build system is constructed | 21:41 |
| T4 | <meierrom> Leif_Erikson: what is holding you from using another pin free Sim or removing the pin? | 23:14 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!