@Fla said in PinePhone:

So we have many information about the PinePhone hardware on this thread, but as we are on the UT forum, I was expecting some UT devs to indicate and keep us up-to-date with the status of UT on the PinePhone.

Well, let's ask

Any update on pine phone port?

@doniks said in OTA-10 call for testing:

@UniSuperBox said in OTA-10 call for testing:

RC was not pushed because no RC has been pushed. Only devel is building again. RC will be pushed later.

oh, ok. I'll try to install devel then ...

Jup, 2019-08-15/2
Thanks!

@UniSuperBox said in OTA-10 call for testing:

RC was not pushed because no RC has been pushed. Only devel is building again. RC will be pushed later.

oh, ok. I'll try to install devel then ...

@UniSuperBox said in OTA-10 call for testing:

@doniks, the issue with deb has been resolved. Updates are now being sent over automatically.

Thanks, though I don't think it is fixed. I ran the installer again and I still end up with 2019-W11. Also when I look here http://system-image.ubports.com/16.04/rc/deb/ and there http://system-image.ubports.com/16.04/rc/deb/index.json I don't see any changes.

Could you point me to where the code is that updates/generates those jsons, publishes the files to system-image server? I can poke around a little myself, maybe I find the culprit

It appears that this has been an issue for months. The last build was the 30th of March. Do you know if any of your users noticed the problem in that time?

I'm not hugely surprised that this issue might have passed unnoticed. I think the number of deb users is very small. Take the subset that run rc, take the subset that report the issue, you are likely to end up at 0.

Was it filed as a bug?

I don't think so. Haven't seen it fly by, nor can I find it now when searching for it. I'll file it.

@aravind_kamble you probably need the --force-sync as the error message suggests

Tried to test on Nexus 7 deb, but no luck:

Dusted off the device, ran

snap install ubports-installer
ubports-installer

seems I have (0.2.3-beta).
Chose 16.04/rc,
installation completed,
but I only get Ubuntu 16.04 (2019-W11), which is way too old

@kugiigi said in Trouble with install on Nexus 7 2013 wifi (flo):

I'm a bit lazy to really read everything in this thread but in my experience, it's always better to install stock android first

after having seen this error:

<3>[ 2.483093] mmc0: error -22 whilst initialising MMC card

I am pretty sure that stock Android doesn't make a difference at this point

@flowbee said in Trouble with install on Nexus 7 2013 wifi (flo):

% ls /dev/mmc*
ls: /dev/mmc*: No such file or directory

Here's a: adb shell dmesg > dmesg.log

UT Recovery (exhibiting e2fsck errors): https://pastebin.com/k1ARAK5f

right, UT has a

<3>[    2.483093] mmc0: error -22 whilst initialising MMC card

TWRP Recovery (normal/works for comparison): https://pastebin.com/AnJwjZFe

while twrp has no error and instead detects the partitions:

<6>[    2.714904]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30

which is the line I was looking for and the UT version does not have this detection of partitions, just the error. that's definitely a problem and it does sound very much like #300

But, I did get the flo-newkernel-2.zip . And the recovery in that zip does not give the errors!

OK, that DEFINITELY sounds like #300 then. Workaround could be to use ubuntu-device-flash command with the --recovery switch (syntax from memory might be called slightly different)

@UniSuperBox remember good ol #300 plaguing flo? Could this have regressed? Did we do smt with the kernel images?

@flowbee strange . Do you have /dev/mmcblablah... ?

Edit: And can you pastebin your kernel log? I think you can get it with adb shell dmesg > dmesg.log, ideally the UT rec and the twrp ones

Edit2: is it this thing https://github.com/ubports/ubuntu-touch/issues/300 all over again? but why?