Posts made by x.Dub

Hi. I want to start working to upgrade the Nexus 5 to focal.
I already found a kernel in progress for halium 9, which according to Florian's information cannot be compiled.
I found these two repositories.
https://github.com/ubports/android_kernel_lge_hammerhead/tree/halium-9.0
https://github.com/ubports/android_device_lge_hammerhead/tree/halium-9.0
The last activity on both repositories is a year ago.
If anyone has any additional information or notes from previous attempts, please post them here.
If anyone else on this phone is actively trying to upgrade to halium 9 and focal, please post here. We can share efforts to get a successful outcome.

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

@povoq This client would allow this.

@povoq QML interface is newly designed by me and should still be QT 5.9 compatible. So far, it is also clean without the UT toolkit. It is practically lacking to connect the backend with the frontend, design a contact list, chat window and account management. Well, quite a lot of things are missing in the frontend (QML).

I was based on this project, which was written for Sailfish OS: https://github.com/Michal-Szczepaniak/Morsender

Backend is actually copied from the original project and cleaned of dependencies on Sailfish OS.

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

Hi, would it be this device a good idea for porting UT?
https://www.gsmarena.com/motorola_one_fusion+-10290.php

Lineage OS is available.
https://forum.xda-developers.com/t/rom-unofficial-lineageos-18-1-liber.4263381/

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'll just add to avoid misunderstandings.

• The display does not switch off immediately when the button is pressed, but goes out unnaturally slowly. After the set timeout, it will personally turn me off normally. However, I have 30 seconds set and I usually use the button.

@keneda I expressed myself in a wrong way... The display goes out unnaturally slowly only when the display is switched off with the button.

Findings after 30 days of use.

Details:

• The display does not switch off immediately, but goes out unnaturally slowly.
• The connection to the Internet via 3G / 2G takes quite a long time after the icon is displayed in the notification area.
• Charging notification is much delayed - the notification LED remains lit long after the cable has been disconnected.

More serious problems:

• Bluetooth is not working properly. It often does not want to search for devices, and if it turns off, it can only be turned on by a restart and only if WiFi is also turned on.
• All S3 Neo with UT have the same MAC address on the WiFi adapter.