I the banner. Also kudos to everyone who participated and made this possible.

@krogoth I like @dobey 's answer. Cause it's not a simple 'no'. It is accompanied by some hints, how you can try to approach the problem, if you want to solve it. Keep going @dobey , excellent work.

@hummlbach Ok. I've decided. I'm ready to maintain the messaging app, if there isn't anybody else. I think I can read/write code, but I'm not familiar with the workflow of maintaining an app on UT. So what do I need to do/know for starters?

Hello there.

I made a pull request, to be able to build messaging-app with clickable tool. This can be usefull for develpoing and testing purposes. And who knows, maybe sometimes all apps come as clickable (snap, ...) packages and can be uninstalled to make UT more flexible.

I'm writing this, to bring a little bit of attention to the PR, to do some testing, if it can be accepted. Feel free to ask any questions.

@dtarrant I played with clickable and webapps few weeks ago .... this is the result: memrise webapp

After looking to my history, these were my steps to init, build & deploy to phone:
on notebook with Ubuntu MATE 18.04

1. install & setup clickable & docker

   sudo add-apt-repository ppa:bhdouglass/clickable
   sudo apt update
   sudo apt install clickable docker
   

2. go to your project dir & create project via clickable (project folder will be created)

   cd ~/projects/ubports/webapps/
   clickable init
   

3. after app creation was successful, you should see an dir created in your current dir with the name of the project you typed in clickable initialization. Enter the project dir

4. try to run (I've figured out, you have to use sudo to run docker)

   sudo clickable -e
   

5. edit files, play, debug, etc ...

6. to deploy to phone, there is a .click package (like appname.developername_1.0.0_all.click) in build folder in your project dir. If not use step 4. or build with

   sudo clickable --output .
   

   this produces a .click package in current dir & tries to copy it to your phone via adb.

on the Ubuntu Touch phone
0) upload .click package to your phone somehow, if not uploaded yet

1. install uploaded .click package via Ubuntu Twaek (or some other way)
2. have fun

So I found out it is possible to select messages in thread fo mass operations. But not as expected. Instead long-hold anywhere on message line, you have to long-hold on left (or right) edge of screen, or somewhere between 2 adjacent message bubbles. It is not every time, but 1 out of 5 attempts is successful, and select mode is turned on.

It is only on my fp2, or are you experiencing the same behavior on your phones too?

@thrill_seeker Quick search on github.com/ubports found a folder for morph search engines implementation. The code in SearchEngines.qml scans through the dir for *.xml and uses them. So to add new search engine, add a new XML to the dir. You can look on the other to figure out how to write a new one. Good luck.

@Ghostrider said in Ubports with a jbl go speaker:

@advocatux I tried your suggestion, I've a terminal return : no space on /var/cache/apt/archives

This is normal for FP2, since last 2 or 3 OTAs. You can try to free some space using these commands extracted fom another post:

$ sudo mount -o rw,remount /
$ sudo rm -r /var/cache/apt
$ sudo tune2fs -m 0 /dev/loop0

If previous commands can't free enough space for /var/cache/apt/archives, you can temporary mount-bind the folder to somewhere else with more space, as described in this post:

$ sudo mkdir -p /userdata/system-data/var/cache/apt/archives
$ sudo mount -o bind /userdata/system-data/var/cache/apt/archives /var/cache/apt/archives/

After this you can try the @advocatux suggestion and it should work without free space problems. Maybe you will have more luck.

I tried the sudo ubports-qa install xenial_-_new-bluez, but it didn't finish and got stuck on bluetooth restarting. After rebooting, as I wrote in previous post, no improvement was observed. And because of the freezing on bluetooth restart, I couldn't revert things back with sudo ubports-qa remove xenial_-_new-bluez, so full image reinstall was needed. Has anyone more luck with this, as I had?

You can bind /var/cache/apt/archives temporary, using mount -o bind command.

# create dir in userdata space 
$ sudo mkdir -p /userdata/system-data/var/cache/apt/archives
# mount - bind
$ sudo mount -o bind /userdata/system-data/var/cache/apt/archives /var/cache/apt/archives/

Now your /var/cache/apt/archives has more space until reboot.

@advocatux said in Ubports with a jbl go speaker:

@Ghostrider there's a new bluetooth version for testing. If you know what you're doing and you are comfortable tinkering, you can give it a try. Run sudo ubports-qa install xenial_-_new-bluez. If after doing that your device gets stuck (because it's trying to restart bluetooth) you just need to reboot your device.

That new version works way better than the old one btw

I'm an FP2 & JBL GO user too and I can't use the speaker with Ubuntu Touch too. I've tried your advice and use new bluetooth version, but the outcome is the same. You connect to speaker, speaker beeps, that it is connected, but no music is allowed to play in music app, and you can't disconnect the speaker, or shut down bluetooth. You have to restart device.

However my other JBL Clip 2 speaker works with UT. And both, with the JBL GO speaker, are working with my Ubunu Mate 18.04 laptop.

@Tellina when I don't know how to test them I always ask and they always answer me (after some time), than I follow the steps (see example).

EDIT: as @Tellina poited out (in private message):

Hi, thanks for your response. Well, don´t get me wrong, but I do not agree with "your" approach. Lets assume 100 persons are testing and following your way. The developer has to answer 100 (different) mails and might risk get answers which are not in line with the issue to test. This is why test cases should always consist of a description what to test and what the expected result is. Cheers

I forgot to mention. First I read the issue and all comments. If there is already a test description there, or I can figure out how to test, then I will not ask any question and just write my test results (with a decription what I tested).

Always read (everything), think twice and don't spam with unnecessary questions. That's one of my mottos.

Hello.

On FP2, using RC chanel, after the last 2 (or 3?) OTA upgrades (currently on rc v.90 = 2020-W43) the phone is asking for my wifi password again.

My wifi name is "jezek" and it is still in the "Previous networks" in wifi settings (with password filled in). But the phone doesn't autoconnect. After selecting the wifi "jezek" from indicator, it asks for password for "jezek-1" network. After filling the password everything works and there are "jezek" and "jezek-1" networks in "Previous networks" settings.

Has anybody similar experience?

It is a minor bug, but typing wifi password after every OTA upgrade is kinda annoying.

@mymike said in Improve system settings disk usage analyzer:

Do you have a cool idea on how to switch between the views?

Hmm... I dunno what cool is, but here are few ideas:

1. Switching through the select box (with "Per dimensione" text). One of the options would be the default "Per folder" view.
2. Tabs/icons like in Contacts/Clock app
3. Hide the switch folder/app in settings
4. small switch icon in top right (like radar view in weather app)

Edit: Maybe someone has more cool ideas for switching, or maybe switching is overkill and only one view is better? (I personal always prefer more choices to choose from)

@mymike said in Improve system settings disk usage analyzer:

What do you think about displaying a bar for each app, instead of numbers?

Why not do both? And you could switch between the views.

Off toppic: All I know about Ainu culture is from Golden Kamui anime. It's in season 3 and it gets better & better. Before I didn't knew anything about Ainu people.

Good luck with translation & propagation. My opinion is, that every language matters.

The only time I had trouble installing Ubuntu Touch on FP2, was when I misread the instructions and rebooted using Volume Up + Power off. Or was it Volume Down + Power off? It took me half a day realizing that. I was mad at myself, I consider myself to be good at these kind of things, but in the end reading with comprehension failed me.

For me, my bluetooth speaker (JBL Clip 2) works even better after OTA-13. Now I'm on rc channel, and BT speaker still works. But I had such experience with my previous BT speaker (JBL Go). The difference between them is (among other) bluetooth version they use (Go: 4.1, Clip2: 4.2). What am I trying to say is, there are many speakers with different BT versions in use, so when making a bug report, don't forget to report the speaker parameters too.

Edit: Can't test my prev speaker (Go), it's not among us anymore.

If someone has an idea for a test, that could identify (narrow down, rule out, ...) the culprit, I'm all ears and in testing mood.

@lduboeuf @AppLee I've browsed through the qml code yesterday too and I didn't find any repeating in sending. I made another test, in a hope I would confirm/falsify repeated sending through the app.

1. Sent SMS to cousin (see posts above for details) - again, the message got gray (with circle), got first billing for SMS (6 cents)
2. Waited for second (cca 30 s after first) and third billing (cca 1 min after second) - closed the message app.
3. Waited if there are more billings - Yes more billing, one every 1 minute.
4. Opened message app, gone to the cousin conversation (to delete the message, cause from previous experience it stops the billings). And I was surprised to see, that the message got green and the billing stopped.

So, from this experiment I deduced, that the message-app tells someone (modem firmware, daemon, ...) to send a message. Than it (the someone) tries to resend the message, until some notification from operator comes, or the message-app tells it to stop trying (message got deleted or marked as green).

Maybe someone with more insight can confirm/falsify my speculation.

@stanwood @AppLee It's definitely not SIM card connection. I have to confess, I didn't make the cleaning of the SIM card, cause I think I can rule it out, I never had problems with mobile signal or some SIM related outage. And I made following test with full network coverage.
I choose 2 contacts:

• brother: when called, it's ringing, he is picking up calls.
• cousin: when called, it's not ringing, a default voice tells me to leave message after beep.

The I did fllowing acions:

1. Sent SMS to brother: sent successfully, immediately green and got one billing.
2. Sent the same SMS to cousin: message got gray with the circle. After 5-10 seconds a billing came. Doing nothing, waiting. After another 10-20 second second billing came. Deleted the still gray message. Waited some time, to ensure the billing stopped.
3. Sent the same SMS to brother: message got gray (with circle), got billing, than second, deleted the mesage. Tried again to send the same message, not successful either, deleted it.
4. Called brother: he picks up, and I asked him how many SMS he got from me. Answer was 1.
5. No action was performed, but after a minute or two, I got bunch of billings and brother sent me an message, that he got other 3 messages.

Maybe the carrier had som problems. But I don't think the app should try to resend unsent messages more times, when the status is not received some time (this is a speculation I made according to observation). I sent 3 identical messages to my brother in the test, but he got 4 at the end.

Note: In the process of writing this reply, I communicated with my brother and another other contact through SMS without flaws.

@Keneda Wow free SMS, what a dream. Maybe in 50 years we well have free SMS in my country too