Ubuntu Touch with OTA updates
#81
[quote pid='69649' dateline='1592855329']

#54 is the most recent version from the dev channel. the nightly builds jenkins builds do not correlate with the automatic ubports update (though they are close so it is easy to get them mixed up). I went through some ubuntu documentation and source code to check where the dev channel pulls its update package from:
Here it is: https://system-image.ubports.com/16.04/a...pinephone/

I'm not sure how the build system is triggered, but I guess it is done manually.
[/quote]

So, #55 and #56 finally came along. But after installing #56 the screen has become irresponsive. The phone seems to boot normally, though.

Just a question: If you download an update, it is presumably stored somewhere and then the phone goes into update mode on the next boot.

When #57 becomes available and the screen issue is fixed, where can I store this on the phone to trigger the update, rather than having to re-flash?
#82
(06-24-2020, 03:51 PM)Zweitaktmotor Wrote: [quote pid='69649' dateline='1592855329']

#54 is the most recent version from the dev channel. the nightly builds jenkins builds do not correlate with the automatic ubports update (though they are close so it is easy to get them mixed up). I went through some ubuntu documentation and source code to check where the dev channel pulls its update package from:
Here it is: https://system-image.ubports.com/16.04/a...pinephone/

I'm not sure how the build system is triggered, but I guess it is done manually.

So, #55 and #56 finally came along. But after installing #56 the screen has become irresponsive. The phone seems to boot normally, though.

Just a question: If you download an update, it is presumably stored somewhere and then the phone goes into update mode on the next boot.

When #57 becomes available and the screen issue is fixed, where can I store this on the phone to trigger the update, rather than having to re-flash?
[/quote]

Unfortunately I don't know the answer to that. This page describes the components of the update process: https://wiki.ubuntu.com/ImageBasedUpgrades
Maybe you find something helpful there. If you do, I'd be interested to know as well Wink

EDIT: You could also try the command line tool via ssh if you already have ssh working. See: https://github.com/ubports/system-image/...anpage.rst
#83
(06-25-2020, 02:09 AM)Momomentum Wrote: [...]

EDIT: You could also try the command line tool via ssh if you already have ssh working. See: https://github.com/ubports/system-image/...anpage.rst


That looks promising, but unfortunately with me it fails with the following error:
Code:
phablet@ubuntu-phablet:~$ system-image-cli -nv
library "libcutils.so" not found
failed to load bionic libc.so, falling back own property implementation
library "libcutils.so" not found
failed to load bionic libc.so, falling back own property implementation
b'\n'
library "libcutils.so" not found
failed to load bionic libc.so, falling back own property implementation
[systemimage] Jun 25 21:12:01 2020 (11933) No valid image master key found, downloading
[systemimage] Jun 25 21:12:01 2020 (11933) [0xffff7f8eb588] Requesting group download:
        https://system-image.ubports.com/gpg/image-master.tar.xz -> /android/cache/recovery/keyring.tar.xz
        https://system-image.ubports.com/gpg/image-master.tar.xz.asc -> /android/cache/recovery/keyring.tar.xz.asc

Exception occurred during dry-run; see log file for details
[systemimage] Jun 25 21:12:01 2020 (11933) system-image-cli exception
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/systemimage/main.py", line 365, in main
    state.run_until('download_files')
  File "/usr/lib/python3/dist-packages/systemimage/state.py", line 179, in run_until
    step()
  File "/usr/lib/python3/dist-packages/systemimage/state.py", line 210, in _get_blacklist_1
    'image-master', 'gpg/image-master.tar.xz', 'archive-master')
  File "/usr/lib/python3/dist-packages/systemimage/keyring.py", line 107, in get_keyring
    (ascxz_src, ascxz_dst),
  File "/usr/lib/python3/dist-packages/systemimage/download.py", line 209, in get_files
    self._get_files(records, pausable, signal_started)
  File "/usr/lib/python3/dist-packages/systemimage/udm.py", line 145, in _get_files
    _headers())
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.InvalidArgs: File already exists at: '/android/cache/recovery/keyring.tar.xz'


Does that look familiar to anyone?
#84
After getting the non operable touch screen problem, I downloaded the latest build(59 I think), backed up my userdata partition from jump drive, etched the new build and restored the user data partition, and that's got it back to normal. 

I'm quite surprised at how well this worked, all downloaded apps and user settings still in place!  So there is something to be said for ubports partitioning scheme after all.
#85
Anyone else noticing that after dev62 and including dev63 SMS sends and receives but the actual text bubbles dont show up under the message thread with each person? Went from having an almost operable phone to a paperweight. Hopefully everyone noticed this and its not just my phone
#86
Maybe I don't understand how these updates are supposed to work. How did we go from a phone that worked to a useless paperweight that we cant even text with? Four updates in a row now SMS does not show up in the text threads
#87
(06-30-2020, 06:43 AM)LMalilil Wrote: Maybe I don't understand how these updates are supposed to work. How did we go from a phone that worked to a useless paperweight that we cant even text with? Four updates in a row now SMS does not show up in the text threads

Its called a regression and it's very common in software development, especially software with such a high level of complexity. Changing one dependancy to improve something or fix something pertaining to that dependancy can have unintended consequences for the thing that it was dependant on, in this case the messages app.

If you want stability, switch back to stable. If you want a bleeding edge device that has a high chance of becoming a useless paperweight, stick with dev. 

Sorry to be blunt and potentially obvious but that just the situation.
#88
(06-30-2020, 06:57 AM)patrickjquinn Wrote:
(06-30-2020, 06:43 AM)LMalilil Wrote: Maybe I don't understand how these updates are supposed to work. How did we go from a phone that worked to a useless paperweight that we cant even text with? Four updates in a row now SMS does not show up in the text threads

Its called a regression and it's very common in software development, especially software with such a high level of complexity. Changing one dependancy to improve something or fix something pertaining to that dependancy can have unintended consequences for the thing that it was dependant on, in this case the messages app.

If you want stability, switch back to stable. If you want a bleeding edge device that has a high chance of becoming a useless paperweight, stick with dev. 

Sorry to be blunt and potentially obvious but that just the situation.

This.
You can find me on IRC, Discord and Twitter


#89
(06-30-2020, 06:57 AM)patrickjquinn Wrote:
(06-30-2020, 06:43 AM)LMalilil Wrote: Maybe I don't understand how these updates are supposed to work. How did we go from a phone that worked to a useless paperweight that we cant even text with? Four updates in a row now SMS does not show up in the text threads

Its called a regression and it's very common in software development, especially software with such a high level of complexity. Changing one dependancy to improve something or fix something pertaining to that dependancy can have unintended consequences for the thing that it was dependant on, in this case the messages app.

If you want stability, switch back to stable. If you want a bleeding edge device that has a high chance of becoming a useless paperweight, stick with dev. 

Sorry to be blunt and potentially obvious but that just the situation.
No its all good man. I was just puzzled cause every developer update since I got it has had full sms capability. Was starting to think I was just having issues with my particular device. So I haven't had a single update in the Stable channel. I have OTA 3 from Release Candidate and it seems to work until the phone sleeps. is that the stable version?
#90
Yep! OTA3 is the latest stable as far as I'm aware Smile


Possibly Related Threads…
Thread Author Replies Views Last Post
  Ubuntu Touch on Pine64 Rondarius 11 3,679 10-11-2023, 12:36 PM
Last Post: Rondarius
  Ubuntu Touch vs Standard Pinephone OS MarsColonist 8 5,984 06-26-2023, 07:50 AM
Last Post: gregb49
  Reinstall Ubuntu Touch on PinePhone with 10 drives? Peter Gamma 4 2,930 05-24-2022, 06:42 AM
Last Post: Peter Gamma
  UB Touch build with debos layton-dev 0 2,273 04-23-2021, 08:12 AM
Last Post: layton-dev
  Whats the latest with UB touch? Cree 9 11,465 03-11-2021, 10:59 AM
Last Post: andybleaden@gmail.com
  UT move to Ubuntu 20.04 Concrete_panda 2 5,287 11-24-2020, 12:43 PM
Last Post: DrewTechs
  Horrible energy consume on Pinephone/UB-Touch firefox-58 9 11,778 10-15-2020, 12:28 PM
Last Post: plainenough
Star Updates stuck on stable channel. Cree 6 7,892 10-04-2020, 11:26 AM
Last Post: Giiba
  Pinephone 3G Bluetooth Working Pretty Well With Latest Mobian Updates rmcg 0 2,528 09-27-2020, 10:22 PM
Last Post: rmcg
  How to enable SSH on UBPorts Ubuntu Touch? eaglecup 12 20,320 09-15-2020, 03:42 PM
Last Post: voidmain

Forum Jump:


Users browsing this thread: 1 Guest(s)