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

    Dekko2 Developer Community Thread

    Scheduled Pinned Locked Moved App Development
    132 Posts 31 Posters 72.6k Views 10 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.
      • D Offline
        domubpkm @flohack
        last edited by domubpkm

        @flohack Hi.

        I have had just te problem of mails not sent : they were putted in Draft folder.

        So i tried : restart dekkod in terminal before opening dekko and it seems to solve my problem.

        1 Reply Last reply Reply Quote 0
        • ? Offline
          A Former User @flohack
          last edited by

          @flohack It seems when you have installed the alpha before and then installing the beta you have this problem. I have wipe my device and install only the beta. Then it works here i can read every email and send emails also.

          flohackF 1 Reply Last reply Reply Quote 1
          • R Offline
            rocky58 @Lakotaubp
            last edited by rocky58

            @lakotaubp yes, me too on my OPO, dekko2 can't display emails content

            1 Reply Last reply Reply Quote 0
            • flohackF Offline
              flohack @Guest
              last edited by

              @xray2000 Sorry I cant wipe my device, its my daily driver πŸ˜‰

              My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

              EllypsisE ? 2 Replies Last reply Reply Quote 0
              • EllypsisE Offline
                Ellypsis @flohack
                last edited by

                @flohack Maybe if you use the UT Twaek Tool to clear the cache of the dekko2 app?

                arubislanderA 1 Reply Last reply Reply Quote 0
                • J Offline
                  joe @Lakotaubp
                  last edited by

                  @lakotaubp said in Dekko2 Developer Community Thread:

                  @joe https://gitlab.com/dekkan/dekko/tags/0.1.6-beta1
                  should be it.There are issues with account verification

                  Thanks. Is this like a daily build link, or the current click. i.e. Will the next newest one be at a different link?

                  H 1 Reply Last reply Reply Quote 0
                  • ? Offline
                    A Former User @flohack
                    last edited by

                    @flohack Yes i understand that it was my daily driver to but i one have a working email client that was a must for me so i take the risk πŸ˜‰

                    1 Reply Last reply Reply Quote 0
                    • H Offline
                      hummlbach @joe
                      last edited by

                      @joe no, there are no daily builds. Here is the list of releases or tags: https://gitlab.com/dekkan/dekko/tags.
                      We will add a new click package there everytime we fixed something until @DanChapman returns.

                      1 Reply Last reply Reply Quote 0
                      • arubislanderA Offline
                        arubislander @Ellypsis
                        last edited by

                        @ellypsis had the right idea. No need to wipe the device. Clearing cache, app data and config of Dekko 2 in the Tweak Tool also does the trick.
                        Don't forget to stop the dekkod service after that, or else perform a reboot, before re-adding your account(s).

                        πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
                        Happily running Ubuntu Touch
                        Google Pixel 3a (20.04 DEV)
                        JingPad (24.04 preview)
                        Meizu Pro 5 (16.04 DEV)

                        S 1 Reply Last reply Reply Quote 1
                        • S Offline
                          stefwe @arubislander
                          last edited by

                          @arubislander Your description don't work for me on my n5.

                          Meizu MX4 16.04 | Nexus 5 16.04

                          arubislanderA 1 Reply Last reply Reply Quote 0
                          • arubislanderA Offline
                            arubislander @stefwe
                            last edited by arubislander

                            @einstein212 did you also reboot your device or stop dekkod then start dekkod before re-adding your email account(s) to Dekko?

                            If you did. What issue do you face exactly?

                            πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
                            Happily running Ubuntu Touch
                            Google Pixel 3a (20.04 DEV)
                            JingPad (24.04 preview)
                            Meizu Pro 5 (16.04 DEV)

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

                              Now dekko2 beta working on OPO.
                              Remove cache, data,config and delete with UT Tweak
                              Then ran rm -f ~/.config/upstart/dekkod*
                              Restart device. I then ran the rm command again, just to be extra sure. Reinstall dekko2 beta1. You should get set up account page. Thanks to Johannes Renkle for the command and everyone else involved.

                              S 1 Reply Last reply Reply Quote 2
                              • S Offline
                                stefwe @Lakotaubp
                                last edited by

                                @lakotaubp Your last instruktions worked. Dekko beta is now running. Thanks to all how are working so hard to get this running...

                                Meizu MX4 16.04 | Nexus 5 16.04

                                1 Reply Last reply Reply Quote 0
                                • H Offline
                                  hummlbach
                                  last edited by

                                  Special thanks for that finding goes to @zubozrout and @Flohack. They found out what was wrong.

                                  LakotaubpL 1 Reply Last reply Reply Quote 2
                                  • LakotaubpL Offline
                                    Lakotaubp @hummlbach
                                    last edited by

                                    @hummlbach and so say all of us. Big Thanks.

                                    1 Reply Last reply Reply Quote 0
                                    • D Offline
                                      dekkerj1 @flohack
                                      last edited by

                                      @flohack Same problem on my Nexus 4, Do you know if this is a specific problem with the Nexus 4?

                                      1 Reply Last reply Reply Quote 0
                                      • H Offline
                                        hummlbach
                                        last edited by hummlbach

                                        @dekkerj1 No thats no nexus 4 specific issue. (Its working fine on my nexus 4.) The versions posted here have an issue with starting the daemon fetching the mails in the background called dekkod. The file needed to start (.config/upstart/dekkod.conf) contains a version specific path (it shouldn't, will be corrected in the next days) thats why you need to execute the command:

                                        @lakotaubp said in Dekko2 Developer Community Thread:

                                        Then ran rm -f ~/.config/upstart/dekkod*

                                        If you have installed on of the alphas you need to delete at least dekkos cache, since the alphas messed up the cache for some mails causing dekko to crash. You can clear the cache either by using the ut tweak tool or by executing rm -rf .cache/dekko* in the terminal. (To be sure, close dekko before doing all this. At best also stop dekkod by running stop dekkod in the terminal.)
                                        Afterwards restart your device if you haven't stopped dekkod from terminal.
                                        There are still some corner cases causing problems. Me for example has problems with deleting mails. @lionelb has reported hes still unable to read mail and dekkos is crashing if repeatedly tries to. But in there very most cases it seems to work fine. If you're still having problems, please report whats the problem exact. At best check whether its a known issue on
                                        https://gitlab.com/dekkoproject/dekko/issues and report it there if its not yet.

                                        D 1 Reply Last reply Reply Quote 0
                                        • D Offline
                                          dekkerj1 @hummlbach
                                          last edited by

                                          @hummlbach Thanks, that fixed it.

                                          1 Reply Last reply Reply Quote 0
                                          • D Offline
                                            doniks @flohack
                                            last edited by doniks

                                            @flohack said in Dekko2 Developer Community Thread:

                                            Just asking to know if we should try to get more help rushing in πŸ˜‰

                                            @Flohack I'm thinking: one thing ubports core team could maybe do to facilitate work on dekko would be to fix packages/dependencies for amd64.

                                            Right now the development workflow is more or less tied to testing on an armhf device. If we could sort out these errors: https://gitlab.com/dekkoproject/dekko/issues/104#note_88572323 then I think we might be able to test dekko on development machines directly which would simplify things.

                                            Update: or maybe not. whatever the problem was in that issue 104, it doesn't hit when we do it like this https://gitlab.com/dekkan/dekko/commit/8b3aa09c7ec7b9d10b957c2d1013afe3bf737ea8 . Now ultimately that doesn't succeed either (yet?), but at least it doesn't stop at apt dependencies

                                            1 Reply Last reply Reply Quote 0
                                            • ? Offline
                                              A Former User @doniks
                                              last edited by A Former User

                                              I'd like to add my thanks and congratulations to everyone who has worked on this.

                                              1 Reply Last reply Reply Quote 2
                                              • First post
                                                Last post