How we can prioritize issues on Github?
Currently there are ~415 issues created and i believe that some of them are more important for the users to be solved than the others.
Last time when i asked about that @Flohack proposed to prioritize issues by giving "thumbs up" on Github but in my opinion that didin't work out.

Maybe we could use some kind of voting poll for each OTA and besides the most important issues from your perspective you could take top 5-10 issues from the list. Thanks to this normal users like me would have some influence on how the system is developed.

@Keneda The main issue is that after 10 months of availability on the market Pinephone still cannot be used as daily phone with UT. If Xiaomi works smoothly with UT onboard I don't see any reason why not to spread a word about that. If more people give a try to UT (it doesn't matter on which hardware) our community can only benefit from that. Personally i'm also looking for a replacement of my Pinephone and Xiaomi might be a good option.

@UBportsNews Looking at github "Unity8+Mir upgrade project" is really astonishing how much work you've done so far.

Looking at the really low number of issues that still have to be solved when do you expect to move it from edge channel to dev/rc ?

Could you say something more about Anbox for OPO? We know that you managed to run it successfully .Can expect image for that phone in near future?

@elastic i'm not sure about rest of the devices but on my One Plus One I've got MultiROM installed and i can switch between Ubports and LinageOS without any problems.

@domubpkm Thanks for sharing this info. Then why this phone is on second place on https://devices.ubuntu-touch.io/ ?

Finally got mine too If i compare it to my previous OPO then i have to admit that bacon image was really mature and besides MMS issue everything worked there like a charm. With PinePhone we are just at the beginning of this road but i think that it should take less time to fix all issues due to growing number of Pinephone users with UBports onboard.
I think that was a good choice

@advocatux Yep, that's exactly this issue on github that i mentioned in my previous post.

Hi Guys,
I think that this issue is already reported on github. Unfortunately i haven't seen any progress there.
I've got exactly the same issue with my OPO and Orange in Poland.

What i noticed that from time to time i'm able to send and receive MMS. To do it i had to disable and re-enable APN settings few times, change to Flight mode and change back to the normal. Unfortunately after OS restart problem is back.
Is there any possibility to view log files of this messenger app or enable debug mode to check what's going on?

Small update,
I just installed Logviewer app and reporduced the error. Below you can check what I've found in application-legacy-messaging-app.log

adding channel "/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_c2cd668c0e76af3327867f501f034d5e/TextChannel11"
"ofono/ofono/account0" "2018-02-18T08:37:27Z-1" "/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_c2cd668c0e76af3327867f501f034d5e/TextChannel11" QMap(("chatType", QVariant(int, 1) ) ( "participantIds" , QVariant(QStringList, ("xxxxxxxxx")) ) ( "threadId" , QVariant(QString, "xxxxxxxxx") ) ( "x-canonical-tmp-files" , QVariant(bool, true) ) )
adding channel "/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_c2cd668c0e76af3327867f501f034d5e/TextChannel11"
file:///usr/share/messaging-app/AttachmentsDelegate.qml:23:1: QML AttachmentsDelegate: Binding loop detected for property "attachments"
adding channel "/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_c2cd668c0e76af3327867f501f034d5e/TextChannel11"
QObject::killTimer: Timers cannot be stopped from another thread
QObject::startTimer: Timers cannot be started from another thread

I don't know why this date and time is mentioned there 2018-02-18T08:37:27. The date is Ok but correct time is 09:37:27 so +1 hour.

@PhoenixLandPirat For me microphone works fine and i can make calls. On Gitlab indeed microphone is marked as not working but maybe that's different use case (for example video conferencing apps )

Hi All,
I follow Pine64 forum and i found quite interesting topic regarding mobian and MMS issues. One of the users developed script to retrieve not delivered MMS. If i remember correctly Mobian use ofono as well so maybe that's something that could be useful for us too.

https://forum.pine64.org/showthread.php?tid=11994

@Keneda The main issue is that after 10 months of availability on the market Pinephone still cannot be used as daily phone with UT. If Xiaomi works smoothly with UT onboard I don't see any reason why not to spread a word about that. If more people give a try to UT (it doesn't matter on which hardware) our community can only benefit from that. Personally i'm also looking for a replacement of my Pinephone and Xiaomi might be a good option.

@domubpkm Thanks for sharing this info. Then why this phone is on second place on https://devices.ubuntu-touch.io/ ?

@htc_tattoo Yes, i know that it needs some time to have all those main issues fixed and maybe my expectations were to high when i bought it. I was used to how system smoothly works on OPO and i expected the same with Pinephone. Unfortunately If you compare how Ubports works on OPO and Pinephone is like comparing riding on highway to ridging on a bumpy road.
Volla phone might be a good choice but this time i'm going to wait few months to verify if it's really stable before buying it

@applee
Pinephone is definitely not the best choice .

I bought Pinephone in March as a replacement of my old broken OPO that i used as my daily phone . Since that time i've launched my Pinephone every 2-3 weeks just to check if there are any improvements and it can be used as daily phone. Unfortunately i don't see any big improvements/fixes and in my opinion this phone can be used just for test purposes.
For me it was a bad choice.

For me Pinphone still cannot be treated as daily phone. People reported me several times that they tried to call me but couldn't reach me despite of the fact that my Phone was online. Sometimes text messages appear only after the reboot. Those issues are already reported on gitlab so it seems that i have to wait for the next update.

@PhoenixLandPirat For me microphone works fine and i can make calls. On Gitlab indeed microphone is marked as not working but maybe that's different use case (for example video conferencing apps )

Hi,
My carrier in Poland is Orange. What i noticed so far is when i change Cellular settings to 2g/3g/4g i cannot make any calls and if i try to call from another phone to my Pinphone i get message that this number is not available at the moment.
I can make calls with 2g and 2g/3g
The funny thing is that when i'm switched to 2g only i get the best mobile reception quality - reception triangle(not sure if that's correct name) is completely white.
With 2g/3g enabled i get only 50% white and 0% with 2g/3g/4g

Besides that I'm randomly completely out of range on my PinePhone while my OPO is running with LTE

Finally got mine too If i compare it to my previous OPO then i have to admit that bacon image was really mature and besides MMS issue everything worked there like a charm. With PinePhone we are just at the beginning of this road but i think that it should take less time to fix all issues due to growing number of Pinephone users with UBports onboard.
I think that was a good choice

Hello,

Did anyone received PinePhone UBports Community Edition ? I'm curious if they started to ship it the customers. I didn't get any info regarding shipping yet.