August 15 devel channel update renders your device unable

domubpkm

@advocatux Done, change the title of the post. For solving the problem, i must wait at least tomorow to get my ubuntu computer back ! I have only a windows 10 netbook with me....
Thanks very much !

advocatux

@domubpkm lol we posted at the same time

advocatux

@domubpkm I don't know about windows netbooks but maybe you can install adb in it?

domubpkm

@advocatux It's can wait.. It's not fully vital. It's not my main phone. My main phone has Vidid 15.04 r3 for the moment.. Because it's a real lack for me (and others maybe) not to have a fully operational dekko : I'm conscious of the big efforts of the developpers on dekko.

advocatux

@domubpkm I'm reading the fresh bug report now (https://github.com/ubports/ubuntu-touch/issues/821). Maybe you can try that workaround that works in FP2 at least, before doing anything else

killerbee

@advocatux Workaround doesnt work for my BQ10 FHD, but fallback to rc channel does

advocatux

@killerbee yeah, it seems the workaround doesn't work for Pro 5, Arale, and Frieza (those are the devices reported for now).

domubpkm

@advocatux I hit the phone against the wall, nothing happen for me !

advocatux

@domubpkm lol

Marathon2422

@advocatux
I think someone is trying to convince you Devs that you need that "edge" LOL

advocatux

@marathon2422 good point XD (but I'm just a user)

domubpkm

@advocatux I don't now if i said something unrealistic or infeasible : i don't think there is a command prompt, something similar as TERMINAL in UBPORTS RECOVERY. Isn't it ? If the system freeze, don't you think it would be a good idea to be able to lauch commands lines so as to unfreeze a phone without another computer ? Or to have a mechanism to change the channel (in this case devel to rc ?). If it is stupid idea, sorry....

advocatux

@domubpkm no, there isn't.

It's not an stupid idea at all but I don't have the technical knowledge about how recovery works in detail, maybe someone with that sort of expertise will reply later.

Off the top of my head, the first problem I see is the (possible) lack of space, but on the other hand I've seen custom android recoveries with much more tools than stock android recoveries, so...

Edit: thinking a bit more about it, the main problem is how to have a keyboard on-screen for input. It would has to be a list of pre-formatted commands or something like that

Lakotaubp

Just to clarify etc on getting round this issue.
1 Stay on RC or don't update your dev device with todays update, or revert to RC in system settings.
2 Wait till next dev update is released with issue fixed.
3 Update to that and all should be ok.
Is this correct

advocatux

@lakotaubp going to RC is the fastest and easier way to have a running device again, and keep it on the save side.

If whoever is hit by this issue want to run a lower devel version, that's feasible too but I think the RC way is more user friendly for now.

Edit: I forgot to say yes, that's correct

advocatux

Some people has asked me in private how to stay in the devel channel, so I think it's better if I post the command here

ubuntu-device-flash --server=http://system-image.ubports.com touch --device=codename --channel=ubports-touch/16.04/devel --revision=version_number

Change codename for the proper one for your device. See here https://devices.ubuntu-touch.io/ the codenames list
version_number means a version number that is not affected by this issue. See the latest good one (that's the previous version to the one affected) for your device here http://system-image.ubports.com/ubports-touch/16.04/devel/

Edit: the issue has been fixed now (https://github.com/ubports/ubuntu-touch/issues/821#issuecomment-413356669) so you can use the latest version_number.

Lakotaubp

Just had new update 430 land for OPO

advocatux

@lakotaubp if you feel adventurous...

Lakotaubp

@advocatux white screen of blue circle doom after 5 min. Looks like OPO stuffed up

truscellino

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