UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    August 15 devel channel update renders your device unable

    Scheduled Pinned Locked Moved Support
    32 Posts 8 Posters 6.1k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • LakotaubpL Offline
        Lakotaubp @domubpkm
        last edited by

        @domubpkm Yes roll back to RC seems to very the advice. Only just picking this up lots more on Telegram supergroup.
        I updated my OPO this morning to 248 and didn't see this welcome message so is it 249 thats the problem

        1 Reply Last reply Reply Quote 0
        • advocatuxA Offline
          advocatux
          last edited by

          @domubpkm thank you for changing the title, and thank you for your patience πŸ™‚

          1 Reply Last reply Reply Quote 0
          • D Offline
            domubpkm @advocatux
            last edited by

            @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 !

            advocatuxA 2 Replies Last reply Reply Quote 0
            • advocatuxA Offline
              advocatux @domubpkm
              last edited by

              @domubpkm lol we posted at the same time

              1 Reply Last reply Reply Quote 0
              • advocatuxA Offline
                advocatux @domubpkm
                last edited by

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

                D 2 Replies Last reply Reply Quote 0
                • D Offline
                  domubpkm @advocatux
                  last edited by

                  @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.

                  advocatuxA 1 Reply Last reply Reply Quote 0
                  • advocatuxA Offline
                    advocatux @domubpkm
                    last edited by

                    @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

                    K D 2 Replies Last reply Reply Quote 0
                    • K Offline
                      killerbee @advocatux
                      last edited by

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

                      advocatuxA 1 Reply Last reply Reply Quote 0
                      • advocatuxA Offline
                        advocatux @killerbee
                        last edited by advocatux

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

                        1 Reply Last reply Reply Quote 1
                        • D Offline
                          domubpkm @advocatux
                          last edited by

                          @advocatux I hit the phone against the wall, nothing happen for me ! πŸ™‚

                          advocatuxA 1 Reply Last reply Reply Quote 0
                          • advocatuxA Offline
                            advocatux @domubpkm
                            last edited by

                            @domubpkm lol

                            M 1 Reply Last reply Reply Quote 0
                            • M Offline
                              Marathon2422 @advocatux
                              last edited by

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

                              advocatuxA 1 Reply Last reply Reply Quote 0
                              • advocatuxA Offline
                                advocatux @Marathon2422
                                last edited by

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

                                1 Reply Last reply Reply Quote 0
                                • D Offline
                                  domubpkm @advocatux
                                  last edited by

                                  @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....

                                  advocatuxA 1 Reply Last reply Reply Quote 0
                                  • advocatuxA Offline
                                    advocatux @domubpkm
                                    last edited by 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

                                    1 Reply Last reply Reply Quote 0
                                    • LakotaubpL Offline
                                      Lakotaubp
                                      last edited by

                                      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

                                      advocatuxA 1 Reply Last reply Reply Quote 0
                                      • advocatuxA Offline
                                        advocatux @Lakotaubp
                                        last edited by 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 πŸ™‚

                                        1 Reply Last reply Reply Quote 0
                                        • advocatuxA Offline
                                          advocatux
                                          last edited by 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.

                                          1 Reply Last reply Reply Quote 0
                                          • LakotaubpL Offline
                                            Lakotaubp
                                            last edited by Lakotaubp

                                            Just had new update 430 land for OPO

                                            advocatuxA 1 Reply Last reply Reply Quote 0
                                            • advocatuxA Offline
                                              advocatux @Lakotaubp
                                              last edited by

                                              @lakotaubp if you feel adventurous... πŸ˜„

                                              LakotaubpL 1 Reply Last reply Reply Quote 0
                                              • First post
                                                Last post