Happy birthday! What's the actual date, 15th or 16th of April? I'm confused by timezones

Yumi at my workplace

Btw, I plan to write a post in this forum about it but my gf is managing these Yumi account, if you want to follow:
Instagram: https://www.instagram.com/yumithetraveler/
Mastodon: https://tutut.delire.party/@yumi

Hello everyone,

I used UT as my primary OS on my Fairphone2 years ago, but now it's been a while I did not play with it. So yesterday, I went ahead a flashed the last UT 20.04 image on my pinephone braveheart which was previously running the 16.04 version.

First remark, it's not easy to find the instructions, which are in a blogpost: https://ubports.com/en/blog/ubports-news-1/post/pinephone-and-pinephone-pro-3889 and there they are not really up-to-date or super clear. I would gladly edit it if someone tells me how to do that.

Now, here is the list of my remarks. I'm posting them here instead of opening bug report at the moment because I've been away from UT for quite some time, so I don't know if those issues are common to all devices or specific to Pinephone. Please tell me, and also where to open a bug if you think that's needed.

• Installation:: The installation of Two-boot and UT went smoothly, nothing to say there.
• Performance: The OS works well but is very slow. I know the Pinephone is a low end hardware, but I think there are some performance issues here, idk if it's specific to pinephone or not. The drawer or Morph are quite smooth (let's say, okayish for this hardware), but the settings app takes 30 seconds to open! (I did it 3 times in a row, 31sec, 32sec, 30sec). There is clearly something wrong here. Same for the Weather app for example, the screen actually turns off before the app is even launched. I think there is something wrong with those apps, as the OpenStore or Morph launch in less than 5 seconds.
• Wi-Fi: The Wi-Fi connection is quite stable, compared to 16.04 which often disconnected and refused to reconnect. Although right I am writing this, I was in flight mode and after exiting UT is not able to connect anymore (but that's different than the issue with 16.04 where it was actually losing the connection)
• Battery: When the screen is off, even with Wi-Fi on, battery usage is bad but okayish. But with the screen on and playing with the phone, it is a disaster, I'm losing one percentage every minute. I used the phone a bit before going to sleep at 1am. At that time the battery was at 45%. I switched off the screen and the bluetooth but let the Wi-Fi on. I woke up at 4h40, at that time, the battery was still 45%. I switched off Wi-Fi. I woke up at 9h30. Battery is still displaying 45% with the chart being completely flat since 1am. I play a bit with the phone, battery suddenly drops to 32% and then 28% in the same minute. The chart adapts showing a "going down" constant lane from 45% at 1am to 28% at 9h30. So apparently the phone is not able to tract the real battery usage when in sleep mode.
• Camera: The camera is not working, which is surprising for me as it was working with 16.04 (with a bad quality and very low framerate but still, I had an image)
• GPS: I know there is no A-GPS on UT so to get a GPS fix can take quite some time. However, here I was not even able to ask for the permission. First time I wanted to try the GPS, I launched Morph, went in openstreetmap and tapped the location icon. Morph asked me for the permission, I said yes, and then nothing happened. And if I go in the location settings, it says that no app asked for the permission. Then opening the clock app, the weather app, which all are supposed to ask for the permission doesn't even make the dialog appear. And are completely frozen during this "looking for position" phase (which is dozens of seconds). Rebooting the phone and starting with the Alarm app first instead of Morph did not help.
• Alarm: The alarm worked well. It was able to wake up the phone. Tapping on "Repeat" or "Quit" was instantaneous.
• Torchlight: The torchlight works as expected. No performance issue.
• Screenshot: I was able to take screenshot of the screen. No performance issue.
• Sharing an image: This bug was already here years ago, it's a bit sad to see it still not fixed in 20.04. It is not possible to share an image using the gallery app. Steps to reproduce: Open Morph and navigate to Mastodon for example, write a new post and tap the button to attach an image. A screen appears asking for the app to select the file. If you use the File app, everything works well (you select the image, validate, and it is uploaded). But if you use gallery, you can select the file, validate, and then the screen is stuck, Morph never gets the file.

I will stop here at the moment, these were my first minutes with the phone. Thank you to everyone involved for the good work, I had no crash so far!

I didn't expect to see any work on 22.04 right now, let alone 24.04. That would be amazing of course, but isn't it a bit too optimistic? I guess many problems will be found once 20.04 will be widely adopted, so you will have to work on that first.

And what about the stabilization on Lomiri on desktop, being fully included in Debian etc?

@cliffcoggin & others about why not only a forum. Yes obviously for exactly this kind of topic (debate, announcement etc) a forum is perfect. But there are other use cases when you need live chat, debugging together with a user, preparing a release... Just jump in the Dev group or the Axolotl one in telegram and you'll see what I mean. And Mattermost would make all this groups much more discoverable.

That being said, sorry I didn't remember that ubports wasn't hosting their own gitlab, in that case obviously there is a bit more work to be done to put it in place and that's maybe not worth it at the moment (because I think the advantage is also to be self hosted, not to use a sass solution)

@totalsonic exactly like the whole gitlab stack, it is there business model, core is free (and clearly complete enough for a project like UT), and you may pay for premium features. Mattermost is the communication tool built to integrate with gitlab and the standard for developers allowing launch ci, be warned about new issues and merge request etc without leaving the chat. That's what I use at work for years, also now what we use at CERN and I can tell you it's a nice tool which would require less than 15min to be activated by the ubports sysadmins. But I guess I presented it wrongly and I know it's hard to make people change. At least I tried
I would have liked to have opinions from the core team on that topic though.

Well Mattermost can be accessed with Morph even if it probably isn't as smooth as with Teleports.

Hello everyone.
The UBPorts community is actually using Telegram to discuss about Ubuntu Touch. There are dozens of groups, about the OS, apps, support, groups in specific languages or even some dedicated to an app like Axolotl, or Waydroid...

With the current events ongoing in Russia (where Telegram is hosted), I feel like we should switch to a solution which is resilient to internet cutoff between Russia and the rest of the world, preferably a self-hosted one. Mattermost is a powerful chat (like Slack) allowing to organize discussions by team and channels and would in my opinion nicely replace Telegram. It can be very easily put in place because it is integrated into gitlab, which is already self hosted by the UBPorts foundation.

What do you think?

Cheers.

@flohack unfortunately, I really need a working Signal, so the nice 2-years UT adventure is over for me (yet). So my FP2 is now running /e/ OS, but I'm still following progresses made as I hope to be able to come back on UT as soon as Signal can be used there.

@prog-amateur yep, sorry but you won't have that before months on UT...

@flohack it was working with the port made by @peat_psuwit, I guess this build is using it?
That port also had a very bad battery life when wifi was on. Is that fixed?

push notifications aren't the main problem of unofficial signal client. If you use UT Tweak Tool to keep Axolotl running, you will receive the notification when you have a new message. The real problem is to keep following upstream changes. See the massive work needed to support groupsv2.

@antidroid 6P is done by @Flohack I think?

@fish My GPS is working on my Fairphone 2. I answered you in https://forums.ubports.com/topic/5746/fairphone-2-gps-does-not-work

The very first GPS fix is veeery long as Ubuntu Touch doesn't support A-GPS (yet). Enable the location service, navigate to maps.google.com and ask for geolocation, and then let your phone outside for 10 minutes. Then re-do the process and you should have your position.

@luna are the instructions in the first post still up-to-date?

There is a new firmware at https://github.com/WeAreFairphone/modem_zip_generator/releases since February 2020, did anyone flash it? How did it go?

Torch and flash are marked as working because they were working with the first camera module. They aren't with the new camera module. I submitted a MR to change that, and also to mark that there isn't any reboots now.
About battery, it really depends if you have Wi-Fi on or not. The Wi-Fi is draining mine.
The camera is indeed very slow to launch.

@peat_psuwit started a new port for the FP2 based on Halium 7.1 and this port and an updated gstreamer you have a smooth camera application and flashlight working. I don't know what's missing for the new port to be released. USB is broken I think, and no ability to charge without booting I would say.

@ubtouch-newbie can you please try to run /usr/share/ofono/scripts/set-context-property 0 Protocol ip in a terminal and tell us if it fixes the problem?

@domubpkm said in How to downgrade OTA-15 ?:

The request makes sense to me. I will go even further.
Generally speaking, it would be interesting to be able to reflash the two previous versions STABLE to see if the malfunctions were present in the previous version(s) for such and such / smartphone(s) that we bought late for example.
For me, for example, i would like to test OTA-13 and OTA-14 for cellular data on Volla Phone.

Could this be a credible request for the installer?

You can fix cellular data in Volla by running /usr/share/ofono/scripts/set-context-property 0 Protocol ip.

I tend to agree with @poVoq, if you have problems, contribute to see them fixed for everybody instead of holding upgrades.
Though I understand the point about comparing to stable to see if this is a regression. But for a new phone like Volla, more recent should always mean better.

@nutzernam We published a 0.9.6 a few hours ago with some fixes, please use that version. There still is a lot of work to do.