Dekko2 Developer Community Thread

flohack · 26 Aug 2018, 21:03

@xray2000 Sorry I cant wipe my device, its my daily driver

Ellypsis · 26 Aug 2018, 22:09

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

joe · 26 Aug 2018, 23:47

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

A Former User · 27 Aug 2018, 04:55

@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

hummlbach · 27 Aug 2018, 06:08

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

arubislander · 27 Aug 2018, 06:15

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

stefwe · 28 Aug 2018, 14:47

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

arubislander · 28 Aug 2018, 14:59

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

Lakotaubp · 28 Aug 2018, 15:13

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.

stefwe · 28 Aug 2018, 16:42

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

hummlbach · 28 Aug 2018, 16:44

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

Lakotaubp · 28 Aug 2018, 16:57

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

dekkerj1 · 31 Aug 2018, 13:02

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

hummlbach · 9 Jan 2018, 09:16

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

dekkerj1 · 1 Sept 2018, 09:43

@hummlbach Thanks, that fixed it.

doniks · 9 Apr 2018, 22:07

@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

A Former User · 18 Sept 2018, 22:03

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

dR0W · 19 Sept 2018, 08:25

Thanks to all the developers involved in this project for the great work.
Tested on my BQ Aquaris E4.5

delijati · 20 Sept 2018, 23:39

Hi,
tried to debug an error i had with using Dekko2. So i compiled it (after some code changes) for amd and run into the Oxide not installed error.

So to sum it up as Oxide is going to be replaced by QtWebEngine this also needs to be done for Dekko2. Or is there a plan to add a transparent layer that redirects to qtwebengine?

Here the issues i created regarding that topic:

One other question is there a repo with the source of dekko1?

doniks · 21 Sept 2018, 05:25

Hi @delijati

Can you describe what you had to do to test on amd64? This is my attempt:
https://gitlab.com/dekkan/dekko/commit/8b3aa09c7ec7b9d10b957c2d1013afe3bf737ea8
If I remember it right, I could build it but wasn't able to run it.

Regarding oxide , yes at some point the rendering engine probably has to be replaced, but unless that becomes blocking, it has no priority at the moment.

What error with oxide do you get?

Wrt dekko1, dunno