@emphrath OK

@lakotaubp OK I'll try that, thank you for the tip.

Hi everyone,
I have been on halium-devel for a few months. I found it quite good apart from long-standing problems like Morph crashing at first launch and the phone app freezing during calls, preventing me to hang up at the end of a call. Fair enough.
This post is about updates. Since the last successful one done on 25/04 (I think v459), every time there is an update, it is downloaded successfully but I keep getting thrown into Android recovery mode. There is an "apply update" option there but it's either "from ADB" or "from emulated", neither of which succeed.
I am reluctant to use the installer on a PC to reinstall the system, so any clue would be welcome. Thanks

I think they found the cause and bug is closed on Github. That was quick

Issue opened on Github:
Message App broken as in Ubuntu Touch 101 from rc channel

@domubpkm Yes thank you, I just realised... I don't really understand the split between gitlab and github, but I will get to the latter in this instance.

I can't see corresponding bug reports on ubport's Gitlab but... the messages app doesn't seem to live there either? Neither in "core" nor in "apps"... I am puzzled.

@applee no but I am happy to do that. I wasn't sure about bug reports for non-stable versions. Thanks.

Back to stable fixes issues with messages app. I might have a go at Dev channel later...

Hi everyone,
Having my two devices (hammerhead + bacon) on rc channel I got updated images this morning, to v101. Not sure about the changes but the messages App is broken. Can't send any text, can't see the history of messages, app freezes whatever I try.
Any clues or fix?
Thanks

The last two days I have been leaving the phone with wifi switched off (and manually back on, as and when needed only). Battery life has come back to "normal", so clearly there is something going on with wifi while phone is left idle.
I will now try the IPv6 trick. Thanks.

Hi everyone,
Like most of you in this thread, I have noticed a drop in battery life since OTA12 with very light usage of the phone. Nothing looking awful when taking a look at processes with "top" in the phone terminal, Unity8 with ~2-5% of CPU... which means that hardware is working too much when most things should be idle.
I will try:

1. disabling wifi (except when I use it)
2. try and disable IPv6

Will report back here...
thanks

OK so your problem is slightly different to mine... but overall I would say that wifi is not robust on UBports.
I remember that the Ubuntu 16.04 desktop also had problems in the early days, sometimes with kernel drivers (Realtek particularly) but sometimes also with IPv6 libraries messing up the connection.
Does your problem appear with all routers?

Hi,
I have had constant problems with wifi, with both Nexus 5 and OPO. To me it started before OTA5 though.
Sorry I am not able to provide a solution, but it could help if we had the same problem. A good test for me, to check:

1. if wifi works after boot, get something streaming from the internet. I use one of the internet radio apps - radio starts to play
2. then get to the web browser and browse until the pages stop loading (to me, after 4 or 5 pages...).
3. in my case, despite the fact that web pages stop loading, the radio keeps playing OK... which means that wifi is working, but new connections cannot be established.
4. if I go into terminal and ping my router (192.168.0.1 for me), it works. In some cases, just sending pings to my router is enough to reinstate the loading of web pages (but not always!).
   Doesn't make much sense to me...
   Also, this problem does not appear with all routers. I live in the UK and it seems like UBports doesn't like routers from SKY (I tried in two different houses). But at the office wifi never drops out.
   I can't see anything obvious from the logs but it's hard to interpret...

Hi all,
Valuable discussion, I think. I would concur with the comments above.
I also have OPO (16.04 dev channel) with occasional double boot. In my experience, the main issue by far is constant wifi drop-outs that make the phone unusable at home. But most people don't experience that problem so it won't be fixed.
Both these bugs are clearly not systematic and hard to reproduce, so we (user impacted) have to run investigations and provide more clues.
I don't think any of us is expecting miracles from a team with little resources. What I would hope is that people in the community would give me some guidance to investigate the bugs I am experiencing. This is where users (like me) that are not real devs, still can help improve the product...

Interesting investigations, thank you!
I had issues with contacts on SIM cards as well but never bothered to look into it - beyond my skills I reckon. But it would be interesting to see if you can get to some conclusions...

Hi there,

In my household we have two phones with UBports, OPO and Nexus 5, and wifi disconnections are a major issue. But it doesn't happen with all wifi routers... so very few people seem to experience it.
I am trying to identify the problem more in details before posting something on the forums. I am interested to see it it's still happening for you... if so then I will share my experience...
Thanks

OK sorry I got there finally... back in 16.04/rc now. My main problem was not to succeed in rebooting into recovery mode...
Thank you for quick response, very much appreciated!

Hi all,
I don't understand how to re-install another version... I don't think developer mode is enabled on my machine and I can't enable it any more due to the white screen of death we are seeing... so I can't see the solution?
Thanks, Marc

OK thank you for suggestion! I tried with Browser and got same problems :-(.
However, today I connected to the guest wifi in the office and everything worked fine. This is a building where only one wifi network is visible, whereas at home there is always a list of wifi networks from the neighbours etc.
So it's definitely a wifi problem, but dependent on specific wifi parameters like available connections, channels etc.
I think I will struggle to get to the bottom of it but I'm not giving up...