added a PR https://github.com/bhush9/rootfs-builder/pull/1

I created a wiki page for our sprint: https://community.kde.org/Sprints/Plasma_Mobile/2019

I have a similiar issue on my Samsung Galaxy Tab 3 7.0 running postmarketOS with Plasma Mobile on the software renderer.

Hi. My name is Camilo and I've been working on the Maui project, which consists of a framework to quickly develop apps that run on Android, GNU Desktops and also in Plasma Mobile with the help of Kirigami. The apps are VVAVE(music player), Pix(image/ gallery manager), Index(file manager), Buho(notes taking app), Station(terminal emulator) and Nota(simple text editor). An interesting aspect of this set of apps is the idea of having cloud integration and syncing between devices.

same, Xiaomi Redmi Note 4X (Snapdragon) [mido] , Adreno 506, MSM8953 Snapdragon 625
https://github.com/Halium/projectmanagement/issues/71#issuecomment-443450191

So sprint dates are confirmed to be 4-9 February, If you need travel support from KDE e.V. please sign up at : https://reimbursements.kde.org/events/80

In T9729#167975, @bshah wrote:

No I mean, well, the dates you have on the poll, we have requested, exactly those dates to Endocode (4-9). So I wonder if we need poll at all :)

No I mean, well, the dates you have on the poll, we have requested, exactly those dates to Endocode (4-9). So I wonder if we need poll at all :)

@bshah I removed the dates before FOSDEM.

I erm, think there has been some confusion? Looking at comments, we thought for everyone week after FOSDEM did work fine for majority of people, so we requested those dates to Endocode.

@neofytosk I opened a poll, please all submit your votes: https://framadate.org/plasma-mobile-2019

Great to see the interest for this sprint increasing!

+1
if is in february and not too soon proobably i can make it

I am working on a series of frameworks and frameworks improvements to make it easier to port applications to Plasma Mobile and Android. I am also the maintainer of Ring-KDE, a complete [phone] call stack with support for Plasma Mobile. Just saying I am interested to go to the sprint.

I would prefer the weekend before FOSDEM (or the week leeding up to it) ... have to go ski touring starting 9.2. ;)

As visible in screenshot, now notifications don't appear at all.. just notification count next to WiFi icon.

We have used Endocode office in past for Plasma Sprint, and we could ask them again.

@neofytosk I think the location I had in mind slowly gets too small and as @jbbgameich told me @bshah already contacted KDAB and they could provide us their office (is that correct?). In that case I don't see any special tasks only I can do from Berlin, but if there's anything I can do, just tell me. :)

Hi everyone, I am interested in participating I work on Mycroft plasmoid for plasma and I think it would be very interesting to have it supported and inside plasma mobile as an user experience. There is some work done on my end to port the Mycroft plasmoid to plasma mobile and also a kirigami standalone app, but I am surely interested in it having a deeper integration with the platform and the shell on the phone.

I am interested in joining.

8-10/02 would be nice for me. If we opt for a more-than-3-days sprint, the whole post-FOSDEM week is probably also OK for me, but I' ll have to ask for days-off and come back with an update.

The week after FOSDEM (4.-9. February) would be a convenient time for me, since there are holidays in that week in Berlin.

I will come after work if it's in Berlin

Judging from the responses so far, it seems like a good candidate would be Berlin/Germany, the week before or after FOSDEM.

Judging from the responses so far, it seems like a good candidate would be Berlin/Germany, the week before or after FOSDEM.

For sprint dates, I was thinking, it would be nicer to schedule it before or after FOSDEM, so I have reason to go to europe and attend FOSDEM 😛

I have only observed Plasma Mobile so far and not found the time and place to really contribute anything. However I'm still interested in attending a sprint. Freiburg, Germany is my home town so either Berlin or Randa would be lovely. I'll be in or around Berlin for the festive season but any other (prolonged) weekend would be fine as well.

I would already have a location for the sprint in Berlin (xHain Hackerspace). But I don't think I'll get it for 7 days, maybe 4 or 5 (Or we just don't get the evening time). Also if it's longer than two days it needs to be in my holidays (February 2-10 were nearest).

I'm maintaining Plasma Mobile project, and mainly working on overall packaging and architecture.

I' ve tried to help newcomers to contribute to Plasma Mobile; with @bshah we tried to make phabricator tasks more complete and easier to be assigned to newcomers and, for the same purpose, I 've created the findyourway interactive guide.

I have been working on Plasma Mobile packaging for postmarketOS.

I'm working on the Plasma Mobile and Halium packaging for Debian and Ubuntu based systems, and also try to improve some of the core apps of Plasma Mobile.
As @lnj mentioned I'm also working on Kaidan.

I'm working on Kaidan, the XMPP client in PlaMo (together with @IlyaBizyaev and @jbbgameich). I also ported Halium to my Xperia Z which is running Plasma Mobile, now.

I have been working on Halium and Plasma Mobile Debian packages for more than a year now, mostly building and testing things. I have been helping to promote Plasma Mobile in social networks, then presented at a conference in St Petersburg. I've just finished working on KDE Russia's website and switched to Kaidan, a Kirigami XMPP messenger, in hope to improve my programming skills to participate in development.

I'm working on bringing KDE Connect to Plasma Mobile and also proposed that we use the SMS app that we are currently developing for KDE Connect as the SMS app for Plasma Mobile. I'd like to discuss ideas about KDE Connect on Plasma Mobile and work on the PM-specific parts of the SMS app task

I think that KTimer and the timer in this clock can exist as separate applications. This is more like the AOSP default clock with only a basic timer. KTimer can offer more advanced stuff like multiple timers and running commands.

For the different apps l would also make different tabs like in vvave where you have album, artist, playlist views in different tabs with an icon tab indicator.

I like what I am seeing in theory. I would love to see an interaction map for this app just to understand how you go through different faces of the application.

I was just thinking the same. At the same time, we are evaluating the value of having a floating set of buttons in the kirigami interface so let's not hold on to them for functionality just yet. If there are other ways to get the same functionality within the app UI then great.

Instead of refresh I would use add and update with swipe top to down cause this is a common swipe.

Do we want time, stopwatch, alarms and timers to be in the same app? We already have KTimer (h[[ https://phabricator.kde.org/M130 | ere a mockup) ]]. Should we develop the remain apps standalone like KTimer or merge it in this "Clock" app?

Wouldn't tabs and navigation by horizontal swipes better to change location? Same for parameters, maybe with arrows to indicate that you can swipe right/left to view another parameter?

@andreaska Thanks. I'll change it to a tab instead

This look a bit confuse. Please review which functionality you want to offer, and how it will work on mobile form factor and on desktop.

About the previous and next buttons. I don't like them, because nobody know what happens before click next. For me it look like an kde hidden feature.

echo "127.0.0.1 localhost.localdomain" | sudo tee /etc/hosts

I have the same issue. Xiaomi Mi 5s Plus (natrium). My device looks like the HTC 10 picture.

I suggest using a 24h format for the clock to correspond to international standards. For the timezones, I would just use an indication of the time in UTC next to the city, for example, Berlin: UTC+2.

So I have updated the design a bit.
I moved the temperature units and wind velocity units to the global drawer following @bshah 's advice.
In the settings page, I have added a list of locations where new items can be added. Following @dkardarakos 's advice, the "Add" button is at the bottom.
The redundant information in the details page have been swapped with a graph for parameters throughout the day.
There's now a way to change the location.

I am really excited to see these mockups! Good work! Although not a designer, following Kirigami HIG I would put "location search" and more important settings at the bottom of the page to facilitate one handed navigation.

@mart this is just a drawing.

is this mockup a drawing or is a qml file with dummy data?

You're right about the duplicated information. Maybe we can swap it with time based graphs. For example if the user selects Thursday's forecast they will be able to see a graph of how the temperature changes throughout the day.
Thank you for your feedback.

Thank you for working on this, Awesome work! \o/

Note: To get Qt full debug output, export this environment variable: QT_LOGGING_RULES="*.*=true".

Task is done, if it needs changes, a new task can be opened.