[OFFICIAL] CyanogenMod 13.0 - Mi3 [cancro]

[chiwawa10]

With the latest snapshot, I noticed that my phone's battery is draining faster as it doesn't go into doze during the night. Anyone facing the same issue here? A quick look at the battery stats tell that Android OS takes up the largest chunk of battery consumption.
My device is Mi3W.

 

[alviumair]

+1.
Was facing the same issue on Miui 7 too.

 

[squirrel27]

Do the latest snpashot or nightlies work properly on Mi 4 LTE?

 

[improntus]

Mi3. CM13 & Zuerion Xv2.4. Five days with the rom. Really happy. Thanks a lot.
DT2W activated. Also DTon StatusBar to sleep.
Some problems first days with data network. Fixed adding apn. First, don't let me do it. When did "save", nothing happens. But then I force close after press "save" and get really saved.
Now my data works well.
Xposed installed and inteli3g module installed from playstore (the module helps me saving battery).
NO vibration at incoming calls but is activated.

Attached screens of battery life.. Lot of changes in configurations these days let's see what happen next days.

Great work. Love the rom. Lot of customization. Thank you again.

 

[maaz2020]

With the latest snapshot, I noticed that my phone's battery is draining faster as it doesn't go into doze during the night. Anyone facing the same issue here? A quick look at the battery stats tell that Android OS takes up the largest chunk of battery consumption.
My device is Mi3W.

Even i noticed it , it doesn't go to sleep . screen is always awake.

 

[dchinu]

BT and Wlan Mac Id

The Android OS related kernel wake locks are related to (ipc0000002a_sensors.qcom) which is a very recurring bug in xiaomi kernel codebase, you can track it in xiaomi bug tracker to 2014.
You can only flash latest fastboot and check if it still active. (Seems to work go with cancro_images_6.9.15_20160805.0000.29_6.0_cn_b3434079ea)

Battery drain related issues are hard to debug as Bug report dump says battery capacity of the device is null. (battery historian output is least informative, no graph and kernel related wakelock sources are blank)

My major gripe with the current state of development is Bluetooth and Wlan mac id are not properly set.
Two MI3 can't share files over Bluetooth as they both have same BT mac. This is also a old regressive bug traced to cm 12 nightly for various devices. @linuxxxx

https://jira.cyanogenmod.org/browse/NIGHTLIES-1930

https://forum.cyanogenmod.org/topic/111587-wifi-and-bluetooth-problem/

 

[chiwawa10]

To my surprise, the problem of not going into Doze mode just went away. After I rebooted my phone, this problem seems to have gone away. I guess its only a matter of time before the bug reappears. It is just waiting to be triggered.

 

[dchinu]

Those who are facing battery drain in standby due to Android OS wakelock, Update your baseband to MPSS.DI.4.0-4f2eb48. That comes with latest miui Dev rom (fastboot). Than wipe and restore your CM backup or fresh install. I was facing this issue from very beginning of CM 13 nightly release, Seems to solved with this Radio update. Lets wait for some more testing and btw with play service 9.x Net_scheduler is also showing high counts of wake events.

 

[motofire]

There is some problem with the voice. When ever I make a call, voice is cracking on the other side. I thought my network had a problem, got checked by the rep. No issues. Changed the sim cards, same problem. I am facing this issue in CM13 only. Using Mi3W.

 

[alpha80147]

Uber issues

I'm having troubles with Uber force closing on the latest nightlies (ever since 18th September) at least. Couldn't find an earlier one, so I rolled back to the latest snapshot. Uber works just fine on the latest snapshot. Let me know what I can provide* to properly document this issue. Thanks!

Edit: *Step by step instructions would really help!

 

[[email protected]]

Hi,
Has Bluetooth a2dp audio stuttering bug been resolved? or still need to use custom kernel for this?


thanks

 

[oL00No]

Hi,
Has Bluetooth a2dp audio stuttering bug been resolved? or still need to use custom kernel for this?


thanks

It has not.

 

[dchinu]

Those who are facing battery drain in standby due to Android OS wakelock.

With the latest snapshot, I noticed that my phone's battery is draining faster as it doesn't go into doze during the night. Anyone facing the same issue here? A quick look at the battery stats tell that Android OS takes up the largest chunk of battery consumption.
My device is Mi3W.

+1.
Was facing the same issue on Miui 7 too.

Even i noticed it , it doesn't go to sleep . screen is always awake.

I was bugged by this issue like forever and found a work around : Install Greenify 2.9.x and enable experimental Aggressive Doze and Doze on the Go. Don't use hibernate or any other tweak. You can tick the doze notification to see on notification when the device went and exit doze.
Been testing for two days no more Kernel related wakelock and battery life is positively improved.

 

[chiwawa10]

I was bugged by this issue like forever and found a work around : Install Greenify 2.9.x and enable experimental Aggressive Doze and Doze on the Go. Don't use hibernate or any other tweak. You can tick the doze notification to see on notification when the device went and exit doze.
Been testing for two days no more Kernel related wakelock and battery life is positively improved.

Thanks, I will give it a try. Hopefully it will improve the battery life.

On another note, anyone here knows when cancro device will receive the cyanogenmod 14 based on Android 7.0 Nougat?

 

[mms047]

Thanks, I will give it a try. Hopefully it will improve the battery life.

On another note, anyone here knows when cancro device will receive the cyanogenmod 14 based on Android 7.0 Nougat?

Don't know. No news yet. Looks like maintainer is dead or something!!

Sent from my cancro using XDA Labs

 

[diongdyh]

Don't know. No news yet. Looks like maintainer is dead or something!!

Sent from my cancro using XDA Labs

Cancro is old. I would dump it as well if I were him.

 

[mms047]

Cancro is old. I would dump it as well if I were him.

Yeah it is, but still there is a lot of users!! and it has a lot of potential yet!!! but the fact is, he should announce or something!

Sent from my cancro using XDA Labs

 

[Guiluge]

Cancro is old. I would dump it as well if I were him.

Old does not mean outdated, this device is still quite powerful, and latest Android versions run just fine on it.

It makes sense to get updated versions for cancro then.

Sent from my MI 3W using XDA-Developers mobile app

 

[JBolho]

Cancro is old. I would dump it as well if I were him.

There are older devices getting CM14, and by the way... Current AOSP 7.0 and AOSP-based NitrogenOS have better performance than MM roms, even with ZeurionX kernel capping the CPU @ 1.7ghz.
It's not a question of dumping the device, MM roms are as stable as they will ever be, even official RR-M has its final version.
The objective now should be reaching the most stable and updated 7.0 based rom for these devices, as a well deserved last "hoorah" for the Snap800 and 801.

 

[linuxxxx]

I see many of you where wondering if cancro would be getting cm-14 or not: well this could be a real thing:

Don't ask me to provide you builds of cm14, I won't, if you can't live without the latest android release there are other guys here on XDA posting cm14 builds.
I've been really busy and I just got some time to bring this up. At the moment video recording is broken, as any other device with a 7.0 rom. Everything else is fine from what I could test.

Until cm14 nightlies release starts (video recording needs to be fixed first), I'll keep cm13 up to dated with patches from aosp security bulletin and others important fixes (if there will be any).