[ROM][Android 8/9/10][Unofficial] LineageOS for Mi-4c/Mi-4s

[WJXXBSH]

Finally I installed Weeb Gapps magisk Moudle, and The majority are fine.

There are 2 problems:

1. The device feels very lag in the opening of the apps and in the transition between them.

2. After restart takes the device nearly 2 minutes to find a cellular network

For the first problem, it will be optimized in the next version, but I cannot convince that it will be more smooth than Android 9 (just like 8.1 is better than 9).
For the second problem, it's a known issue since Android 9 (also happened to other roms), but may not be able to fix (at least I didn't find the reason).

 

[ciberfred]

Thanks for this sharing, just test the 17.0 version on my mi4c device and after remove the assets in install scripts, remove many fonts to get right place to install google store pico it's works.
just a word about daily usage, after a long charging during night i get a black screen only a reboot get the usuable interface.
no performance nor slowliness... it just work fine !

time to time get some screen/fingers issue but i think it come from my screen replacement...

thanks...
just need to know why this is not in the official lineage page as this version is working fine ! (like older).

 

[WJXXBSH]

Thanks for this sharing, just test the 17.0 version on my mi4c device and after remove the assets in install scripts, remove many fonts to get right place to install google store pico it's works.
just a word about daily usage, after a long charging during night i get a black screen only a reboot get the usuable interface.
no performance nor slowliness... it just work fine !

time to time get some screen/fingers issue but i think it come from my screen replacement...

thanks...
just need to know why this is not in the official lineage page as this version is working fine ! (like older).

The charging issue has been fixed in lineage-16.0 (as well as the 17.0 test builds on my phone), and a new verison of 17.0 will be uploaded soon, with some other fixes and performance improvements.
LineageOS has a strict limit if someone wants to maintain the official builds, but this rom will surely break the rules (including some hacks in source codes), that's why it's still unofficial. There will be lots of compromise changes if it (official builds) really happens.
The device tree and kernel that are used currently only meet (less than) 75% of the whole rules of official builds. Although the "Hardware" part has nearly no problem, things would become even worse after checking the "Software" part.

 

[ynuance]

Thank you for your work!!!
I'm gonna try android 10 on my MI4C!!!

 

[TiagoRveiga]

Hi thanks for your work!
I've tried lineage 16 previously but the GPS didn't work properly, tried to change the setup files but it the GPS fix was not good at all!
Other issue I've found was the Revolut app, it was not possible to install from official sources (device not compatible).

Do you know if the GPS is working fine in this lineage 17??
thanks, regards, Tiago

 

[WJXXBSH]

Hi thanks for your work!
I've tried lineage 16 previously but the GPS didn't work properly, tried to change the setup files but it the GPS fix was not good at all!
Other issue I've found was the Revolut app, it was not possible to install from official sources (device not compatible).

Do you know if the GPS is working fine in this lineage 17??
thanks, regards, Tiago

GPS works well on my phone, on both 16.0 and 17.0 (it means my device could get satellite signal properly, using "GPS Status" could help you to check it). The GPS profile is partly optimized for China, but should also work in other counties. Here is a test result in southern China:

I don't know much about "Revolut", but the problem might be caused by GAPPs (if you didn't install it), as most APPs outside China need it to work. If it was caused by "root access", you could disable it in "Developer settings" in Settings, then the "su" will hide itself.

 

[TiagoRveiga]

Hi, thanks for your fast reply! =)

I've tested with GPS Status and I couldn't get a proper 3d fix, usually the GPS fixed 3/4 satellites, I've reverted to the "Xiaomi" Rom and the GPS is working fine.
I had the GApps (Nano or Mini) I can't remember. I'll let you know if I've opportunity to try again!
The 16 was amazing... I had to revert because of the GPS, didn't try much to fix the REvolut installation!
Thanks! =)

 

[coiso0]

Hi!

Wich version (15.1/16/17) do you recomend, for daily use, with good performance and stability?

Thanks for your work!

 

[WJXXBSH]

Hi!

Wich version (15.1/16/17) do you recomend, for daily use, with good performance and stability?

Thanks for your work!

I'm using 16.0 on my phone currently, so it's the version I recommend to use. I only have one phone (this Mi-4c), so I prefer more stability.
The performance of 16.0 and 17.0 should be similar, but still lower than 15.1 (just regard it as "using iOS 9 on iPhone4s is not as smooth as iOS 7"). However, the 15.1 builds have not been updated for a long time, so 16.0 should be a better choice.

Update #1
Lineage-17.1 is more smooth than before, which has similar (or better) performance than 16.0, so I'm using 17.1 on my phone now.

 

[mtzero]

how to fix incorrect battery percentage ?

 

[elna.nitz]

For the first problem, it will be optimized in the next version, but I cannot convince that it will be more smooth than Android 9 (just like 8.1 is better than 9).
For the second problem, it's a known issue since Android 9 (also happened to other roms), but may not be able to fix (at least I didn't find the reason).

Ok So I switched to Lineageos 15 and it feels more lag than Lineageos 17...

Edit: Lineageos 17.1 is more smooth and faster than previous versions
Thank you

 

[WJXXBSH]

how to fix incorrect battery percentage ?

It should be fixed in the latest version.
According to the current test, this problem should be caused by ADB, which is enabled on every boot automatically. In the latest verison, ADB is disabled after boot, just as the solution in lineage-16.0.

 

[elna.nitz]

It should be fixed in the latest version.
According to the current test, this problem should be caused by ADB, which is enabled on every boot automatically. In the latest verison, ADB is disabled after boot, just as the solution in lineage-16.0.

Can I dirty flash latest update?

 

[WJXXBSH]

Can I dirty flash latest update?

Yes, I always do a dirty flash on my device.

 

[elna.nitz]

Yes, I always do a dirty flash on my device.

After dirty Flash, all Google Apps Crashing at the opening. What can I do?

 

[kyoto44]

After dirty Flash, all Google Apps Crashing at the opening. What can I do?

Clean flash..

 

[hkdg009]

Build lineage 16.0 issue

Hello, landlord, I encountered the following problems when building lineage 16.0 through the configuration file you provided:
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:75:5: error: incompatible pointer types initializing 'cfg_result_cb' (aka 'void (*)(bt_vendor_op_result_t)') with an expression of type 'void *(int)' [-Werror,-Wincompatible-pointer-types]
vendor_alloc,
^~~~~~~~~~~~
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:76:5: error: incompatible pointer types initializing 'malloc_cb' (aka 'void *(*)(int)') with an expression of type 'void (void *)' [-Werror,-Wincompatible-pointer-types]
vendor_dealloc,
^~~~~~~~~~~~~~
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:77:5: error: incompatible pointer types initializing 'mdealloc_cb' (aka 'void (*)(void *)') with an expression of type 'uint8_t (uint16_t, void *, tINT_CMD_CBACK)' (aka 'unsigned char (unsigned short, void *, void (*)(void *))') [-Werror,-Wincompatible-pointer-types]
vendor_xmit_cb,
^~~~~~~~~~~~~~
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:78:5: error: incompatible pointer types initializing 'cmd_xmit_cb' (aka 'unsigned char (*)(unsigned short, void *, void (*)(void *))') with an expression of type 'void (bt_vendor_op_result_t)' [-Werror,-Wincompatible-pointer-types]
vendor_epilog_cb
^~~~~~~~~~~~~~~~
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:79:1: error: missing field 'epilog_cb' initializer [-Werror,-Wmissing-field-initializers]
};
^
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:906:40: error: implicit conversion from enumeration type 'ant_serial' to different enumeration type 'bt_vendor_opcode_t' [-Werror,-Wenum-conversion]
int ret = vendor_interface->op(BT_VND_OP_ANT_USERIAL_OPEN, fd);
~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:919:44: error: implicit conversion from enumeration type 'ant_serial' to different enumeration type 'bt_vendor_opcode_t' [-Werror,-Wenum-conversion]
int ret = vendor_interface->op(BT_VND_OP_ANT_USERIAL_CLOSE, NULL);
~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~
7 errors generated.
This problem has troubled me for a long time, and no relevant solution has been found on the Internet. How does the landlord solve it?

 

[WJXXBSH]

Build lineage 16.0 issue

Hello, landlord, I encountered the following problems when building lineage 16.0 through the configuration file you provided:
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:75:5: error: incompatible pointer types initializing 'cfg_result_cb' (aka 'void (*)(bt_vendor_op_result_t)') with an expression of type 'void *(int)' [-Werror,-Wincompatible-pointer-types]
vendor_alloc,
^~~~~~~~~~~~
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:76:5: error: incompatible pointer types initializing 'malloc_cb' (aka 'void *(*)(int)') with an expression of type 'void (void *)' [-Werror,-Wincompatible-pointer-types]
vendor_dealloc,
^~~~~~~~~~~~~~
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:77:5: error: incompatible pointer types initializing 'mdealloc_cb' (aka 'void (*)(void *)') with an expression of type 'uint8_t (uint16_t, void *, tINT_CMD_CBACK)' (aka 'unsigned char (unsigned short, void *, void (*)(void *))') [-Werror,-Wincompatible-pointer-types]
vendor_xmit_cb,
^~~~~~~~~~~~~~
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:78:5: error: incompatible pointer types initializing 'cmd_xmit_cb' (aka 'unsigned char (*)(unsigned short, void *, void (*)(void *))') with an expression of type 'void (bt_vendor_op_result_t)' [-Werror,-Wincompatible-pointer-types]
vendor_epilog_cb
^~~~~~~~~~~~~~~~
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:79:1: error: missing field 'epilog_cb' initializer [-Werror,-Wmissing-field-initializers]
};
^
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:906:40: error: implicit conversion from enumeration type 'ant_serial' to different enumeration type 'bt_vendor_opcode_t' [-Werror,-Wenum-conversion]
int ret = vendor_interface->op(BT_VND_OP_ANT_USERIAL_OPEN, fd);
~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~
external/ant-wireless/ant_native/src/bt-vendor_vfs/ant_native_chardev.c:919:44: error: implicit conversion from enumeration type 'ant_serial' to different enumeration type 'bt_vendor_opcode_t' [-Werror,-Wenum-conversion]
int ret = vendor_interface->op(BT_VND_OP_ANT_USERIAL_CLOSE, NULL);
~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~
7 errors generated.
This problem has troubled me for a long time, and no relevant solution has been found on the Internet. How does the landlord solve it?

If the errors are caused by "-Werror" parameter, try to remove them from the related makefiles (eg. Android.mk). If you want to know everything I changed, please refer to repo_16.diff on GitHub.

 

[hkdg009]

If the errors are caused by "-Werror" parameter, try to remove them from the related makefiles (eg. Android.mk). If you want to know everything I changed, please refer to repo_16.diff on GitHub.

OKay,i'll try.

 

[hkdg009]

If the errors are caused by "-Werror" parameter, try to remove them from the related makefiles (eg. Android.mk). If you want to know everything I changed, please refer to repo_16.diff on GitHub.

What version system does the landlord use to compile? I am using Ubuntu 16.04 LTS. Did the landlord encounter such a problem during compilation ?