Hi. Some time ago I tried to create a client based on libpurple. Xmpp support would be a matter of course there. Unfortunately, I don't have much time to devote to this project. But if by chance someone has the time and mood: https://gitlab.com/x_Dub_CZ/zetaim

@povoq This client would allow this.

Hi, I don't know about the others, but at the moment I have no way to use Facebook messages on UT.

And what about creating an app based on libpurple libraries?
It had occurred to me before, but I knew it would be a lot of work.
Something like this:
https://github.com/Michal-Szczepaniak/Morsender

Libpurple can do a lot of protocols, including Facebook:
https://developer.pidgin.im/wiki/ThirdPartyPlugins

According to this thread on XDA, it looks like the MAC address is stored in /efs/wifi/.mac.info.
Maybe this could help fix the problem.

https://forum.xda-developers.com/t/hack-4-4-x-5-x-x-hack-mac-address.3296942/

I use a 128GB SD card formatted to FAT32.

@odo Hi. I don't know if my answer will be relevant. Do you have FAT32 or exFAT on your SD card? I have the same phone and when I flashed UT on it, I also had problem with a SD card. FAT32 didn't work for me for some reason. But if the SD card is formatted to exFAT, it works without a problem.

I don't like creating zombie threads. But I would like to ask when to expect carddav support in UT?

@cesar-herrera
Bluetooth works well on my phone (Asus Zenfone Max Pro M1). The file /etc/bluetooth/main.conf looks like this:
https://pastebin.com/TGA7NnxE
Maybe it will help you.

Hi, I found the correct configuration file and were able to fix this error:

warning: (ANDROID_DEFAULT_SETTING) selects NETFILTER_XT_MATCH_QTAGUID which has unmet direct dependencies (NET && INET && NETFILTER && NETFILTER_XTABLES && NETFILTER_XT_MATCH_SOCKET && NETFILTER_XT_MATCH_OWNER=n)

Unfortunately, the "make halium-boot" command ends with another error.
https://pastebin.com/rHBrZcLD

Does anyone know what to change so I can continue?

I decided to rewrite the original post and include information about the phone.

Phone: Cubot KingKong Mini

Specifications:
CPU (SOC): MediaTek Helio A22 - MT6761, 2.0GHz, Quad-Core, 64-bit
GPU: PowerVR GE8300
RAM: 3GB
ROM: 32GB
OS: Android 9
Slot: 2 x Nano SIM Card +1 x Micro SD card
Display: 4.0″ QHD+ Display
Resolution: 1080 x 540, 302 ppi
Rear camera: 13.0MP,ƒ/ 2.2 aperture,with 1* 0.5A LED flashlight
Front camera: 8.0MP,Fixed focus,4P lens
Battery: 2000mAh
Network: 2G:GSM 850/900/1800/1900MHz, 3G:WCDMA 900/2100MHZ, 4G:FDD-LTE:Band: B1/3/7/8/19/20
Wi-Fi: a,b,g,n, n 5GHz Dual band
Bluetooth: 4.2
USB: Type-C

Where to buy: https://www.aliexpress.com/item/4000203850799.html

There is an even "newer" version 2 on the market, which has exactly the same specifications. KingKong mini 2 differs only in the Android version (Android 10). It is likely that with version 2 it will be possible to downgrade to stock Android 9.

Where to buy version 2: https://www.aliexpress.com/item/1005001802751358.html

I have Device, kernel and vendor available for the port: https://gitlab.com/x_Dub_CZ/cubot_kingkong_mini-d936p

---

Original post:

Halium 9 for Cubot King Kong mini?

Hi. I'm trying to create a halium 9 for Cubot King Kong mini.
Device, kernel and vendor: https://gitlab.com/x_Dub_CZ/cubot_kingkong_mini-d936p
The "make halium-boot" command ends like this: https://pastebin.ubuntu.com/p/k8w5XMVJ2K/
Can anyone advise me what I'm doing wrong?

@aimar : Yes, that's why I had to replace the display. I'm quite sorry, the phone looked better without the bottom painted buttons.

I use a 128GB SD card formatted to FAT32.

I would just like to announce that my Aquaris E4.5 behaves exactly the same. Although I originally thought that the non-original display was to blame. I changed the display roughly at the same time as OTA16. The touch decoder broke in the original display.

Some news?

I'll get into the discussion a bit. Blootooth is always on on my cell phone. As for headphones or handsfree, neither will connect automatically. And if so, not correctly. My suggestion is to put a list of paired devices in the context menu - similar to WiFi. It would be close at hand and I don't think it would bother anything there.

By the way, some Android phones have the same problem with my bluetooth devices. I think the problem will be mainly in the imperfect bluetooth specification.