yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 4C] Gabbbbbbb:
Lots of flickering, everywhere except the camera.

u0_a92@:/ $ su

root@:/ # cat /proc/cmdline

sched_enable_hmp=1 sched_enable_power_aware=1 console=ttyHSL0,115200,n8 androidboot.hardware=libra boot_cpus=0-5 lpm_levels.sleep_disabled=1 msm_poweroff.download_mode=0 androidboot.selinux=permissive androidboot.bootdevice=f9824900.sdhci androidboot.serialno=ceae0c78 androidboot.hwversion=2.3.0 androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_sharp_rsp61322_1080p_video:1:none

root@:/ #
[Xiaomi Mi 4C] scrofanionel:
Bug confirmed. Screen flickering. Sharp screen model.
[Xiaomi Mi 4C] KopiJahe:
will get back to you later, my setup is f*cked up right now (windows 10 suddenly restarted mid-building, closing the VM, now it won't complete the build at all. Thanks, microsoft!), I cleaned the out folder, yeah, maybe another 14 hours... :silly:
[Xiaomi Mi 4C] kurokuroninja:
Rom build 20160611 faster than previous build.

Thanks very much ketut.kumajaya and emfox..

BTW, camera flickering bug still exist..

This is my result in terminal

u0_a85@libra:/ $ su

root@libra:/ # cat /proc/cmdline

sched_enable_hmp=1 sched_enable_power_aware=1 console=ttyHSL0,115200,n8 androidboot.hardware=libra boot_cpus=0-5 lpm_levels.sleep_disabled=1 msm_poweroff.download_mode=0 androidboot.selinux=permissive androidboot.bootdevice=f9824900.sdhci androidboot.serialno=76372279 androidboot.hwversion=2.3.0 androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_auo_nt35596_1080p_video:1:none

root@libra:/ #

For temporary fix still just disable HW overlays
[Xiaomi Mi 4C] muff99:
mdss_dsi_sharp_rsp61322_1080p_video
[Xiaomi Mi 4C] RandomDude:
You're welcome. Happy to donate a few dollars to keep your spirits up and development going!

---------- Post added at 08:50 AM ---------- Previous post was at 08:40 AM ----------

Snap camera flickering only = mdss_dsi_auo_nt35596_1080p_video

It doesn't bother me too much. I just use another app.
[Xiaomi Mi 4C] KopiJahe:
[MENTION=4021423]ketut.kumajaya[/MENTION] there's still very few flickers in the snap camera app (but not like before).
[Xiaomi Mi 4C] ketut.kumajaya:
That's strange I can't reproduce flicker issue on my device. I'll disable dynamic fps in the next commit and let's see user feedback.

Still no go for SELinux enforcing :( Maybe I have to rewrite the policy from scratch based on CAF.
[Xiaomi Mi 4C] BlackXhorneT:
You'll get it bud. It's just a matter of time and patience
[Xiaomi Mi 4C] Elias_Foreman:
Hello! Fingerprint Sensor does not work for aqua? :confused:
[Xiaomi Mi 4C] KopiJahe:
Good idea :good:

There's possibility that my build isn't right :silly:

Best luck man....

Yes, it doesn't work for aqua for now. IIRC, fingerprint requires SELinux status to be enforcing, and right now it is still permissive.
[Xiaomi Mi 4C] christianvari:
How is battery life in this rom compared to MIUI?
[Xiaomi Mi 4C] BlackXhorneT:
It's worth noting for those who follow both threads for the Mi4S (Aqua) - this one and the RR thread, that the 1.05 released kernel that they hoped would allow fingerprint use does not work. As mentioned in this thread multiple times, we need enforcing SELinux for that which is being worked on. It's a lot to do though so always remember to thank devs for their hard work and again (from my experience) this is the rom to use. Original and the best ;) RR feels half baked compared to this!

Keep up the awesome work guys!
[Xiaomi Mi 4C] Brunnys:
RR is built with the same open source, there are not differences , if not the ones of CM and RR.
[Xiaomi Mi 4C] AndropaX:
[MENTION=4021423]ketut.kumajaya[/MENTION]

https://github.com/kumajaya/android...mmit/f0a30a12738b933c9a1e69659a1ee2b3e3c34d0a

I'm not agree with that, in this case user haven't any way to enable it.

Nexus 4C Prime & Tapatalk
[Xiaomi Mi 4C] ketut.kumajaya:
Git revert always available for us :D I just want to check if multi touch bug still exists even if edge touch feature completely disabled. Test it and report back.

[MENTION=7453248]BlackXhorneT[/MENTION] Please check on your device (Atmel touchscreen) when enable on screen navigation bar completely disable navigation button.
[Xiaomi Mi 4C] BlackXhorneT:
I'll happily test, where's the option?
[Xiaomi Mi 4C] ermacwins:
Settings > buttons > enable on-screen nav bar
[Xiaomi Mi 4C] Gabbbbbbb:
What is the multi touch bug?
[Xiaomi Mi 4C] BlackXhorneT:
Nope. Not in there
[Xiaomi Mi 4C] ermacwins:
No nav bar option? Try typing nav in search under settings
[Xiaomi Mi 4C] BlackXhorneT:
Tried that, the search takes me there but there's no option at all
[Xiaomi Mi 4C] KopiJahe:
In case anyone interested, my build are updated with new commits.

Download:

https://goo.gl/m05hxJ

a little review:

- screen still flickers in snap camera (mine have sharp_nt35595_1080p_video display, check yours), other camera apps (or any other apps that I have on my phone) didn't flicker at all.

- there's an option to enable navbar, but it didn't disable the hardware button (also reverts their custom actions to the default one)

If there's a need for a dmesg or logcat, I'll provide later (going to bed now...)
[Xiaomi Mi 4C] BlackXhorneT:
Trying your build mate :) couple of things I've noticed,

On startup I get a message that "unfortunately, music has stopped" and the app won't launch (not an issue for me as I use apple music).

My animation speed on pulling the notification shade is VERY slow (Nova launcher) even after re-applying root for it.

Otherwise it's nice :). The on-screen Mac bar works and doesn't disable the lower capacitive buttons (although the lights go off).

Nice work :)
[Xiaomi Mi 4C] ermacwins:
Emfox 11th June build, screen started flickering, not camera but in whatsapp
[Xiaomi Mi 4C] ketut.kumajaya:
I don't understand why hardware buttons still working when on screen nav bar enabled. I'll upload a test kernel in attempt to fix this.
[Xiaomi Mi 4C] BlackXhorneT:
Go for it. I'll report back once it's tested.

For now, rolling back to 11th build. Slow animations are getting on my nerves a bit now...
[Xiaomi Mi 4C] ketut.kumajaya:
A test kernel boot-20160613-libra-aqua.img will be available at https://goo.gl/sLLLdb shortly. This kernel will enable on-screen nav bar on 11th build.
[Xiaomi Mi 4C] BlackXhorneT:
Clean re-installing 11th build and will flash kernel post install. Will report back with findings asap but it's not a quick process! Good grief I flash this phone a lot haha
[Xiaomi Mi 4C] NotChinaMobiles:
No flicker for me

Music App FC twice after each reboot

Galery FC for first start
[Xiaomi Mi 4C] KopiJahe:
Yeah, me myself didn't use the default music (removed with opengapps installer).

The notification slide is only slow if you're opening it via nova launcher gesture, if you open it manually, it is fast (at least for me).

What is your display mate?

I didn't use both stock gallery and music app, so I wouldn't know.

Maybe the FC is caused by using jack&jill? Will try to compile without that next time.
[Xiaomi Mi 4C] ketut.kumajaya:
Every aqua user can try my test kernel to check if it really disable hardware buttons when on-screen nav bar enabled.
[Xiaomi Mi 4C] NotChinaMobiles:
I had no FC with ur Build from 10.06.16.

I use this time Pico Opengapps

I dont know wich Display my Phone has. Im sorry, i cant help u guys out with these. I can only Flash my Phone with ADB but the rest i dont understand ^^
[Xiaomi Mi 4C] KopiJahe:
The backlight is off, but the buttons are working.
[Xiaomi Mi 4C] BlackXhorneT:
Buttons working (including option to select from setup! (Image below) but the hardware buttons still work, just with the light off.

EDIT:

By the way, this photo of my Mi4S was taken by my colleagues Mi4C also running this Rom! (He also encouraged me to get the 4S in the first place :) )
[Xiaomi Mi 4C] KopiJahe:
[MENTION=4021423]ketut.kumajaya[/MENTION] I forgot to reboot my phone(I just booted your kernel via fastboot without flashing), and now my hardware buttons aren't working anymore, even if I enabled it via the settings, only the backlight is coming on. Rebooting to normal kernel brings back the hardware button.

I think we need to turn the display off and on again to make this take effect, will try to reproduce this.
[Xiaomi Mi 4C] miftahzy:
try porting validus rom

does anyone want to help me

I tried to port rom validus bootup homescreen

but I get the problem

1. baseband unknown

2. The camera fc

3. when the music plays SystemUI stop
[Xiaomi Mi 4C] SH1M4BD3:
Wooo..i missed some party here what a damn cool to see you guys arround [MENTION=1434892]ketut[/MENTION]kumajaya [MENTION=2689045]awaaas[/MENTION] what a proud to see you guys alive in this thread.. Keep it up, am waiting the 32GB variants of libra, hope you guys we'll not leave so soon

[emoji12] [emoji2] [emoji2] [emoji2]
[Xiaomi Mi 4C] ketut.kumajaya:
You can play with /proc/touchscreen/nav_button_enable procfs using echo and cat command :D Don't forget tell me what you have found.
[Xiaomi Mi 4C] ketut.kumajaya:
I have port this ROM from Nexus 5x (bullhead) in source level, almost fully working and stable. What do you meant by "port" here?
[Xiaomi Mi 4C] miftahzy:
I mean I was just trying ported but not build rom

I ported the rom of nexus 5x

would you try to build the rom?

sorry for my bad english :D
[Xiaomi Mi 4C] KopiJahe:
Okay, I can't reproduce "the success" I have earlier :silly:

But what I've found, that whichever I chose, whether it's to enable or disable on-screen nav bar from the settings, this command's output stay the same:

root@libra:/ # cat /proc/touchscreen/nav_button_enable
[B]1[/B]

enable? 1.

disable? 1.

enable, turn the screen off and on again? 1.

disable, turn the screen off and on again? 1.

Update:
[MENTION=4021423]ketut.kumajaya[/MENTION] I then tried to flash your kernel, and it worked!

So, my guess is that my phone earlier got into deep sleep, and then the display go to sleep, and when it wakes up, the updated value kicks in.

Same thing with my second success, I set the on-screen nav bar before reboot, flashed your kernel, effectively updated the value.

root@libra:/ # cat /proc/touchscreen/nav_button_enable
[B]0[/B]
[Xiaomi Mi 4C] ketut.kumajaya:
No, CM more than enough for me. This ROM development fully open, you can trace what I have done so far. No monster or mixed up commit from my side. You are free to hack bullhead ROM for libra but sounds like "reinventing the wheel" for me. If you good in ROM development, better start libra-caf ROM base on Yu sambar.
[Xiaomi Mi 4C] ketut.kumajaya:
Please try:

echo 0 > /proc/touchscreen/nav_button_enable
cat /proc/touchscreen/nav_button_enable
echo 1 > /proc/touchscreen/nav_button_enable
cat /proc/touchscreen/nav_button_enable
[Xiaomi Mi 4C] KopiJahe:
Nothing happens.

root@libra:/ # echo 0 > /proc/touchscreen/nav_button_enable
1|root@libra:/ # cat /proc/touchscreen/nav_button_enable
0
root@libra:/ # echo 1 > /proc/touchscreen/nav_button_enable
1|root@libra:/ # cat /proc/touchscreen/nav_button_enable
0

If it's 1, it will stay 1. If it 0, it will stay 0. No matter how many times I enter echo 1 ._.

You'll see what I mean:

root@libra:/ # echo 1 > /proc/touchscreen/nav_button_enable
1|root@libra:/ # cat /proc/touchscreen/nav_button_enable
0
root@libra:/ # echo 1 > /proc/touchscreen/nav_button_enable
1|root@libra:/ # cat /proc/touchscreen/nav_button_enable
0
root@libra:/ # echo 1 > /proc/touchscreen/nav_button_enable
1|root@libra:/ # cat /proc/touchscreen/nav_button_enable
0
[Xiaomi Mi 4C] ketut.kumajaya:
A new test kernel boot-20160614-libra-aqua.img available at https://goo.gl/sLLLdb Please try it and report back.
[Xiaomi Mi 4C] KopiJahe:
It works! :highfive:

After echo 0, the lights turn off, and the hardware nav button didn't respond to my touch.

Edit: Also works via settings. :good:
[Xiaomi Mi 4C] ketut.kumajaya:
Now, please give me list of /firmware/image/ contents. I hope you still keep your original MIUI ROM, give me list of /system/etc/firmware/ and /system/vendor/firmware contents if available.

EDIT: You must find a way how to mount stock ROM system image.

EDIT2: Forget my above reply, please copy list of https://github.com/CyanogenMod/andr.../blob/cm-13.0/proprietary-files.txt#L135-L143 to your device, you can download all binaries from https://github.com/TheMuppets/proprietary_vendor_nextbit
[Xiaomi Mi 4C] BlackXhorneT:
Tested and working :). Through settings and initial setup. Solid work
[Xiaomi Mi 4C] ketut.kumajaya:
[MENTION=3813099]emfox[/MENTION] Kernel update and a big vendor update available for sync :good:
[Xiaomi Mi 4C] KopiJahe:
Done?

D:\tmp\Mi4s\proprietary_vendor_nextbit-cm-13.0\ether\proprietary>adb push lib\lib_fpc_tac_shared.so /system/lib/
8 KB/s (38408 bytes in 4.467s)

D:\tmp\Mi4s\proprietary_vendor_nextbit-cm-13.0\ether\proprietary>adb push lib\hw\fingerprint.msm8992.so /system/lib/hw/
7 KB/s (34428 bytes in 4.220s)

D:\tmp\Mi4s\proprietary_vendor_nextbit-cm-13.0\ether\proprietary>adb push lib64\lib_fpc_tac_shared.so /system/lib64/
11 KB/s (42656 bytes in 3.664s)

D:\tmp\Mi4s\proprietary_vendor_nextbit-cm-13.0\ether\proprietary>adb push lib64\hw\fingerprint.msm8992.so /system/lib64/hw/
10 KB/s (38792 bytes in 3.641s)

D:\tmp\Mi4s\proprietary_vendor_nextbit-cm-13.0\ether\proprietary>adb push vendor\firmware\fpctzappfingerprint.b00 /system/vendor/firmware/
0 KB/s (180 bytes in 2.233s)

D:\tmp\Mi4s\proprietary_vendor_nextbit-cm-13.0\ether\proprietary>adb push vendor\firmware\fpctzappfingerprint.b01 /system/vendor/firmware/
312 KB/s (6568 bytes in 0.020s)

D:\tmp\Mi4s\proprietary_vendor_nextbit-cm-13.0\ether\proprietary>adb push vendor\firmware\fpctzappfingerprint.b02 /system/vendor/firmware/
1812 KB/s (473248 bytes in 0.254s)

D:\tmp\Mi4s\proprietary_vendor_nextbit-cm-13.0\ether\proprietary>adb push vendor\firmware\fpctzappfingerprint.b03 /system/vendor/firmware/
1482 KB/s (253540 bytes in 0.166s)

D:\tmp\Mi4s\proprietary_vendor_nextbit-cm-13.0\ether\proprietary>adb push vendor\firmware\fpctzappfingerprint.mdt /system/vendor/firmware/
253 KB/s (6748 bytes in 0.026s)

all automatically assigned with rw-r--r-- attributes.

Edit: I also make this zip to simplify this (for when I update the ROM)
[Xiaomi Mi 4C] ketut.kumajaya:
And then delete /system/lib/hw/fingerprint.libra.so and /system/lib64/hw/fingerprint.libra.so, add a screen lock, reboot. After a boot complete take a dmesg and logcat, give me the output.
[Xiaomi Mi 4C] KopiJahe:
See the attached.
[Xiaomi Mi 4C] emfox:
done.

any significant improvement of those vendor updates?
[Xiaomi Mi 4C] ketut.kumajaya:
06-15 09:31:55.634 987 987 I SystemServiceManager: Starting com.android.server.fingerprint.FingerprintService
06-15 09:31:55.639 490 490 D PermissionCache: checking android.permission.MANAGE_FINGERPRINT for uid=1000 => granted (894 us)
06-15 09:31:55.640 490 490 V fingerprintd: nativeOpenHal()
06-15 09:31:55.646 490 490 D fpc_fingerprint_hal: fpc_module_open
06-15 09:31:55.646 490 490 I fpc_tac : App name length: 19
06-15 09:31:55.646 490 490 I fpc_tac : Max app name length: 23
06-15 09:31:55.646 490 490 I fpc_tac : Application name is: fpctzappfingerprint
06-15 09:31:55.646 490 490 E fpc_tac : sysfs_node_write openat failed 13
06-15 09:31:55.646 490 490 E fpc_fingerprint_hal: fpc_module_open failed -13
06-15 09:31:55.646 490 490 E fingerprintd: Can't open fingerprint methods, error: -1
06-15 09:31:55.647 987 987 W FingerprintService: Failed to open Fingerprint HAL!
06-15 09:31:55.647 987 987 V FingerprintService: Fingerprint HAL id: 0

Looks better than before.

New blobs must be better :)
[Xiaomi Mi 4C] GoldGanja:
Could it be possible to add the option for disabling or enabling touch boost in next kernel version, like on many Nexus 5x available kernels? sys/module/msm_performance/parameters/touchboost 0
[Xiaomi Mi 4C] AgiZ10:
There is so much going on here but i am not sure how far the development is towards a stable rom for everyday use. Is this one ready for daily driver or are there any bugs left (mi4c here).

Btw, thank you for so much effort!
[Xiaomi Mi 4C] akrai:
I use the day 30 one of emfox and is totally stable
[Xiaomi Mi 4C] christianvari:
In latest build i get screen flickering in camera with a clean install.
[Xiaomi Mi 4C] AndropaX:
[MENTION=4021423]ketut.kumajaya[/MENTION]

Are you sure that bullhead fp reader mounting in ramdisk is also suitable for mi4s ?

In miui it looks like that:

# config fingerprint fpc
chown system system /sys/bus/spi/devices/spi12.0/bus_lock
chown system system /sys/bus/spi/devices/spi12.0/clk_enable
chown system system /sys/bus/spi/devices/spi12.0/fabric_vote
chown system system /sys/bus/spi/devices/spi12.0/hw_reset
chown system system /sys/bus/spi/devices/spi12.0/input
chown system system /sys/bus/spi/devices/spi12.0/modalias
chown system system /sys/bus/spi/devices/spi12.0/pinctl_set
chown system system /sys/bus/spi/devices/spi12.0/power
chown system system /sys/bus/spi/devices/spi12.0/spi_owner
chown system system /sys/bus/spi/devices/spi12.0/spi_prepare
chown system system /sys/bus/spi/devices/spi12.0/uevent

chmod 666 /sys/bus/spi/devices/spi12.0/bus_lock
chmod 666 /sys/bus/spi/devices/spi12.0/clk_enable
chmod 666 /sys/bus/spi/devices/spi12.0/fabric_vote
chmod 666 /sys/bus/spi/devices/spi12.0/hw_reset
chmod 666 /sys/bus/spi/devices/spi12.0/input
chmod 666 /sys/bus/spi/devices/spi12.0/modalias
chmod 666 /sys/bus/spi/devices/spi12.0/pinctl_set
chmod 666 /sys/bus/spi/devices/spi12.0/power
chmod 666 /sys/bus/spi/devices/spi12.0/spi_owner
chmod 666 /sys/bus/spi/devices/spi12.0/spi_prepare
chmod 666 /sys/bus/spi/devices/spi12.0/uevent
[Xiaomi Mi 4C] ketut.kumajaya:
I don't even check 4s boot image or system image, a bit different in kernel source but not too much. Should be easier if I have an access to 4s device.

EDIT: In my opinion, kernel source adaptation for Nexus blobs much better, if possible. I'll include bullhead fingerprint firmware in the next commit and build fingerprintd from source. Let [MENTION=2689045]awaaas[/MENTION] try it later.
[Xiaomi Mi 4C] miftahzy:
build 30 may versi?
[Xiaomi Mi 4C] KopiJahe:
Yes please... :silly:

Also, if you want, I can provide you with any info you want about 4s (boot/system/whatever). But not the device :p
[Xiaomi Mi 4C] akrai:
right now im using the latest one, and all perfect
[Xiaomi Mi 4C] ketut.kumajaya:
Still with nextbit ether fingerprint firmware, try 20160616 test kernel https://goo.gl/sLLLdb and give me dmesg and logcat output as you have done before. Good luck with your aqua :D Yea, upload aqua boot image for me.
[Xiaomi Mi 4C] cbolumar:
Hi kumajaya, very very good job . Thanks.

Could you say me the diference between NIGHTLY roms in your drive and your sources?

When i try your last NIGHTLY ROM (16-04-2016) RIL is working with sim 2 , only have problems to store videos but ROM is running very very smouth

But when i build CM13 using your sources :

- I must change in BoardConfig. mk ANDROID_COMPILE_WITH_JACK to true ( with false i have some problem building LiveLockScreenService )

- Ril don't work with SIM2 ( i can't use SIM1 because hardware problem)

- Selinux go to Permisive

- Store video is working

- Other things seens to work OK

Regards
[Xiaomi Mi 4C] ketut.kumajaya:
No ROM from me but from [MENTION=3813099]emfox[/MENTION] as a test build to confirm my source really a build able source codes.

- Jack a resource hungry compiler, he kill my host computer. As stated at post #1, revert disabled Jack if you have a high performance machine

- RIL support still buggy, I managed to fix slow GSM registration problem and enable dual SIM support but data over GSM stop working. I'll fix it eventually ;)

- Permissive SELinux for now. When everything goes working, we will switch to enforcing

- Everything else should be OK. Our device tree source already passed Google and Cyanogen quality standard and no dirty hack from my side. Camera and sensor hack so clean and no boringssl-compat that potentially break crypto support, i.e. Here maps and Facebook should be run smoothly

I hope we will have a fully working and stable ROM next week. Thanks for your feedback.
[Xiaomi Mi 4C] ketut.kumajaya:
[MENTION=3813099]emfox[/MENTION] :victory:
[Xiaomi Mi 4C] cbolumar:
Hi , that means RIL is working with your sources ? I have AICP ROM waiting for RIL :p
[Xiaomi Mi 4C] ketut.kumajaya:
After the next commits. Just rebuild the ROM to confirm everything goes well.

EDIT: The best part, no Lollipop RIL blobs ;)
[Xiaomi Mi 4C] ketut.kumajaya:
RIL still working properly after flash a new build, time to factory data reset, reformat /system :D

EDIT: Setup Wizard directly detect GSM data network :victory:

[MENTION=3813099]emfox[/MENTION] Force sync your source and rebuild :good: You can try the resulted build this time. Don't forget to set SIM 2 ringtone, somehow none by default :laugh:
[Xiaomi Mi 4C] emfox:
Done, a new build uploaded.

Edit: I've dirty flash it myself from Teamsuperluminal's rom, now that everything works fine except vibrate on touch. I'll try backup and clean data later to see it.

Edit2: data and cache cleaned, vibration on touch still not availabe, seems upstream issue, so wait for the next build.

Edit3: my another sim card of China telecom (network type is cdma2000) has no signal… no matter which slot it is inserted.
[Xiaomi Mi 4C] ketut.kumajaya:
Please try and confirm if https://github.com/kumajaya/android...mmit/59645ef8b78200d633f81f14a9de8c858209b91d work.
[Xiaomi Mi 4C] emfox:
will build later.

never mind, the cellular data switch has been occasinally turn off, silly me...

now after swap two simcards to each other slot, now even the card has network signal lost data connection, phone call and sms ok, no data(no 'LTE' or 'E' or whatever over the little signal icon). swap back and forth, reboot, the problem still exist.
[Xiaomi Mi 4C] ketut.kumajaya:
Manual select network operator and check APN settings. The last method, delete /data/data/com.android.providers.telephony in TWRP.

EDIT: :laugh: :laugh: :laugh:
[Xiaomi Mi 4C] cbolumar:
Hi , I built CM13 and AICP .

CM13 : RIL is working . :good::good:

Problems with vibration.

AICP: RIL is working

Camera don't work : Can't connect with camera service.

Some FC in AICP settings (Only in one specific area)

Problems with Vibration.

Good job ketut.kumajaya and emfox :cool::cool:

Regards.
[Xiaomi Mi 4C] zhart:
Can someone briefly clarify what the difference is between this, and other cm13 builds? like team superluminal?

Really good to see some developing starting on this phone! keep it up! :D (y)

ALSO, Is it safe to use the CM OTA updater? i use the 18. build from that google drive :)
[Xiaomi Mi 4C] ketut.kumajaya:
Known issue:

- Incorrect power consumption info

- HDR camera crash, Google camera video support crash

- LED blinking

- Touch vibration but call vibration working

- MAC address for WiFi and Bluetooth not get extracted

- No CDMA support

I write this from scratch based on Nexus 5x device tree source and blobs. Camera blobs partially from stock Lollipop, STMicroelectronics LSM6DB0 sensors HAL from stock Lollipop, both wrapped using a clean hack. RIL blobs from Yu sambar, Marshmallow branch. So, no much Lollipop blobs inside this ROM. Sorry, I mean inside this source ;) As a CyanogenMod contributor, I hate a closed source ROM that based on CyanogenMod community source codes. Reuse even a single line of my code for your own closed source project feel unfair.
[Xiaomi Mi 4C] emfox:
It doesn't work, no any visible changes. I assume it would display more setting from network type choosing dialog or what, but cannot find any difference.

here's the log of choose sim 1 setting --> Network operators ( the screen displaying "Error while searching for network") --> Choose automatically (the screen displaying "Registered on network")
[Xiaomi Mi 4C] ketut.kumajaya:
I'll build a patched RIL for you. I must be careful because our source almost AOSP, only confirmed working patch will be pushed at review for upstream change.
[Xiaomi Mi 4C] emfox:
Although gsm is more common use but cmda support should be important too because our device support both of them. I remember nexus 5x support cdma too, am I wrong?
[Xiaomi Mi 4C] ketut.kumajaya:
Please dial "*#*#4636#*#*" (without quote) and check listed value in "Set preferred network tipe".
[Xiaomi Mi 4C] emfox:
it's LTE/GSM auto(PRL) and I changed it into LTE/GSM/CDMA auto(PRL), and still nothing happend.