06-24-2020, 03:51 PM
[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?
#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?
