@FishFingers44 maybe that cable can be easily fixed? Is it broken or a bad connection?

@giukas I don't know :(. All I did was that I used some clean alcohol to wipe the SIM card and regarding the slot I've just looked inside if there is something visible that would cause the issue and haven't seen anything. So I just blowed some air there ... and it still wasn't ok since the contact was lost later again so what resolved the issue for me was to push the card into the slot thoroughly ... maybe I haven't had it fully inserted before ... there could have been some dust there that have prevented me to place the card correctly. Not sure ... but be careful and try not to destroy the slot it if isn't yet :). Good luck. PS. It could also be a SIM card issue. You may want to try another one to see if it works or try this one in a different phone.

great... i knew you problem was different.. but while i was looking for a wifi solution, i am sure i saw some infos on how to recover imei too on some kinds of phones..so..

Thanks, I will give all of it a try. Let you know what happens. Are there images that you can get and load?

perfect

@dobey ah, I see... thanks for clearing up.

Ok, seems to be broken then...I changed a lot in my phone, hardware seems to be on its end.. we don't have much alternatives...what about the meizu mx 4? Is it worthy to change from a N5 to this phone?

@druk13 nice guide, yeah, in German, but still. Hopefully that helps those guys that need to repartition theirs Pro 5.

Quick search says, it's possible. You have just to figure it out. And, don't forget to share your findings.

@ll you're welcome

Thanks! tar and un-tar those two dirs on the other device did the trick.

About the screen problem: I had the same problem, when I was on the train and charging the N5 on the wall socket. I think the problem was me charging on the Butt-Pants-Seat interface as well. As soon as I touched the protected earth wire of the socket (grounding myself) everything worked fine. Later I realized that the shielding of the cable was broken. I replaced it and hence forth I didn't have problems any more.

I configured now and restarted dekkod as: phablet@ubuntu-phablet:~$ cat ~/.config/dekko2.dekkoproject/dekkod.conf [FileLog] Enabled=1 Path=/home/phablet/dekkod.log [LogCategories] IMAP=0 Messaging=0 POP=0 SMTP=1 [StdStreamLog] Enabled=0 [Syslog] Enabled=0 phablet@ubuntu-phablet:~$ restart dekkod dekkod start/running, process 26955 The resulting log is very good and I'm familiar with such SMTP logs from sendmail and other MUA: [24252] Feb 02 12:39:16 [Debug] Running action TransmitMessagesRequest 107185203838979 [24252] Feb 02 12:39:16 [Debug] SMTP : newConnection [24252] Feb 02 12:39:16 [Debug] SMTP : Open SMTP connection [24252] Feb 02 12:39:16 [Debug] SMTP : RECV: "220 ms-10.1blu.de ESMTP Exim 4.86_2 Ubuntu Sat, 02 Feb 2019 12:39:15 +0100" [24252] Feb 02 12:39:16 [Debug] SMTP : SEND: "EHLO [127.0.0.1]" [24252] Feb 02 12:39:16 [Debug] SMTP : RECV: "250-ms-10.1blu.de Hello ppp-88-217-102-34.dynamic.mnet-online.de [88.217.102.34]" [24252] Feb 02 12:39:16 [Debug] SMTP : RECV: "250-SIZE 104857600" ... Now I have just to wait and catch the next send resulting in Drafts ...

@krille said in missing xmpp and a very slow install in libertine: In my opinion XMPP is not suitable to replace a messenger like Telegram or Matrix on mobile... mhmm as @dobey already said...

@guru I would for now carry on with that thread as only the name space has changed for the app. Development carries on the same. Lets keep it all together for now.