yashsingh1/xdaforums huggingface dataset:
[Mi 3 Original Android Development] krishsns:
Hi thank developer for the last build. After updating latest cm13 03092016. My phone seems to laggy. Do anyone facing this kind of issue
[Mi 3 Original Android Development] TofikLupus:
I doubt he'll remove it. Mi4 LTE is not supported by CM. I'm not sure though, if any development specifically for Mi4 LTE exists. If not, then there's no development except official MIUI, which is kinda sad.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] bluviper:
not to mention mi5 is now out. hhmmm

we all wish they could extend the support to those devices.
[Mi 3 Original Android Development] Dev Null:
I accept that LTE is a totally different device, but since the camera image rotation (solved) I don't see any big difference. I don't expect camera to be better till Xiaomi don't release camera driver source.

There was the BSOD problem which had been denied to exist on supported devices, and a few weeks ago somhow solved as well.

Currently the last problem I can see, that there's no LTE selection in mobile network mode (LTE works anyway). It's not at all a problem for me anyway, I never use other mode than "best available".

Maybe that NFC service still exists, but it should be a "problem" for the supported 4w devices as well.
[Mi 3 Original Android Development] Luka12:
i paired mi3 with bluetooth speaker. often i have problem playing music. after pairing players play music for 1s, then have pause 1s and so on. it becomes unusable.

today i had problem, my phone was scrolling without me touching phone. like i have virus or something.
[Mi 3 Original Android Development] bluviper:
Contacts app collapsing after update.

cleaned cache and everything, sync off.

i just dont want to install the whole ROM. coming from a cyan delta update.
[Mi 3 Original Android Development] zeus.01.01.01.01:
issue

pls help ... my device always ends up in a bootloop whenever i try to flash any marshmallow based rom . I'm currently running on CM12.1 . i want to move to cm13 but this problem occurs always .. somone help me out of this .
[Mi 3 Original Android Development] miss:
I can think the same after turning on the radio fm
[Mi 3 Original Android Development] cpjoshi:
Please someone gives here, total process and required all files, because I am trying to install very first time... Please help me.... Thanks in advance...
[Mi 3 Original Android Development] vineshbalan:
A few of issues I face

- Trusted face doesn't work

- once in a day(mostly) the touch screen becomes non-responsive. Have to force reboot to get things running

- battery isn't great. Drains 20+% during night. And the battery percentage varies a lot between restarts.
[Mi 3 Original Android Development] mig0r:
fixed
[Mi 3 Original Android Development] sztofel:
This ROM should be installed on MIUI KK or MIUI MM ?

I have some issues with the camera (recording doesnt work - "cannot connect to the camera", probably because of the miui kernel version.
[Mi 3 Original Android Development] roshan2989:
guys,I'm getting android phone process stopped all the time on latest version?anyone having this issue...?even after restart
[Mi 3 Original Android Development] blur:
Neither, please make a clean install (factory reset) with CM13.

I think a lot of these issues are described in the last posts are caused by dirty flashing or updating nightly builds.

After a while with updating the nightly versions there seems to be a clean install required.

After 4 or 5x updating a make a clean install and I do have a smooth and stable OS with a great battery performance.
[Mi 3 Original Android Development] szwistak:
Anyone having a problem with bluetooth connection to car headset? My phone is connecting only in audio profile. When I force it to connect phone profile it gets disconneted with unknown reason or getting timeout. Did clean install using latest nightly
[Mi 3 Original Android Development] blur:
Here too a similar issue with BT audio. It is connected to my BT earphone, but the music is playing for 1sec. than an interruption of a few seconds than playing again for 1sec. ... etc.
[Mi 3 Original Android Development] xiamcm:
No difference, just wipe and install
[Mi 3 Original Android Development] cpjoshi:
Please reply
[Mi 3 Original Android Development] Luka12:
Same here ?
[Mi 3 Original Android Development] TofikLupus:
You should check out page #1 in the first place, you can find there all steps for flashing including the zip file. But anyway, if you're switching from MIUI and still have MiRecovery, you should first install custom recovery, I recommend TWRP and merged partition layout for which you can also find guides here in either General or Help section. I can't give you the links now, sorry.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] blur:
Now it works :confused:

I have deleted the BT-device and after a reboot I have made a new configuration of the BT earphone.
[Mi 3 Original Android Development] narugan26:
Do you guys recommend this rom for daily driver?
[Mi 3 Original Android Development] rxl.noir:
Yes. No SODs on my experience with the stock kernel.

Although there are some problems with bluetooth and missing APNs, you should be able to manually resolve it quick and easy.
[Mi 3 Original Android Development] dungos:
trying renaming your mi name under bluetooth settings..i faced this issue and able to correct it by renaming..
[Mi 3 Original Android Development] abhisek de:
i am not getting any root access in my mi3 ..please help asap
[Mi 3 Original Android Development] blur:
Do you know the way Developer Options -> Root access?
[Mi 3 Original Android Development] abhisek de:
i have done that...but still i am getting no root access
[Mi 3 Original Android Development] GhostWANTED:
flash supersu zip from recovery ;)
[Mi 3 Original Android Development] mig0r:
Totally agree. I had lost APNs, which was fixed after fresh install.
[Mi 3 Original Android Development] Luka12:
it doesn't solve problem :(
[Mi 3 Original Android Development] sztofel:
You are right- clean install solved problem, thank you! :)

I'll test tommorow if bluetoth will work fine. As some other users - sometimes i had problems with lagging music playback.
[Mi 3 Original Android Development] Mortihead:
and get bricked CM13.

from FAQ:

First of all do not flash any supersu/superuser/superman zip package to get root. Go to Settings>Developement Settings>Root acces > Apps Only
[Mi 3 Original Android Development] blur:
Now I have installed CM13 on 3 devices an unknown number of nightlies and I always found root access.

Maybe a clean install is helpful.
[Mi 3 Original Android Development] diongdyh:
I always used SuperSU on CM even it has built in root. You won't brick your Mi3 for flashing SuperSU. The native root is just not convenient enough for me
[Mi 3 Original Android Development] GhostWANTED:
if u have twrp 3.0 it won't brick.. u must flash zip that u have downloaded for marshmallow ver. supersu 2.67..if u are on older twrp just dont swipe on "install supersu" if twrp ask u.. it already showed on the supersu zip install information.. read always all things that the console from twrp show u ;) sorry for my bad english
[Mi 3 Original Android Development] sanmesh789:
ok google feature is not working in cm13. phone cant detect the voice while setup
[Mi 3 Original Android Development] abhisek de:
Ya thanks... I just re-flashed it..now i got root access .. Thanks man?
[Mi 3 Original Android Development] Mortihead:
In last nightly frm 15.03 crash in clock application:

1) Click on clock widget on desktop

2) Click settings (3 dots in right bottom corner)

3) Crash

Crash in snap camera:

1) Run snap camera

2) shoot 1 or 2 fotos

3) Press "home" button (onscreen key)

4) Application SnapCamera crash.
[Mi 3 Original Android Development] fredek_lodz:
Confirm.

[IMG="Clock crash"]http://fredek.no-ip.org/XDA/Screenshot_20160316-081106.png[/IMG]
[Mi 3 Original Android Development] blur:
Here too.

And a unfamiliar high battery drain.
[Mi 3 Original Android Development] bluviper:
the camera bug and desktop clock widget bug doesnt happen on my end.

tho im still having the Contact app crash.

updated through Cyandelta app (every nightly, ever since)
[Mi 3 Original Android Development] Luka12:
does it work with some other kernel?
[Mi 3 Original Android Development] sivabommakanti:
does this need the new miui mm partion or old 1.2gb partion is enough?
[Mi 3 Original Android Development] Anandababu153:
1.2GB is good enough... I'm using this.

It works with MIUI MM partition as well.
[Mi 3 Original Android Development] blur:
On my Mi3 the BT-issue has vanished. I do not have tested other kernels.
[Mi 3 Original Android Development] Luka12:
i still have problem. usually it works after rebooting. at least for some time :(
[Mi 3 Original Android Development] sztofel:
Same thing here, clean install doesnt help in this case.
[Mi 3 Original Android Development] LKc丶:
Cyanogenmod team has released the first stable version of cm13 , hope we can get it soon :D
[Mi 3 Original Android Development] JBolho:
Installed latest nightly, clean install, everything working well except GPS. It "sees" the satellites but doesn't fix, just like in CM 12.1.

Other thing is gaming performance doesn't seem as good as in CM 12.1, Antutu score decreased by 4k...

Any suggestions?

Enviado do meu MI 3W através de Tapatalk
[Mi 3 Original Android Development] blur:
And now we have the first stable CM13 for our devices:

http://download.cyanogenmod.com/?device=cancro

:D

I am eager to see how it works.

EDIT: I think a clean install would be recommened.
[Mi 3 Original Android Development] diongdyh:
Snapshot, not stable
[Mi 3 Original Android Development] Dev Null:
did u try to reboot after install?

sensor problems are common before first "clean reboot"

---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------

how about the latest issues (f.e. alarm clock settings). are there any in snapshot and latest nightly?
[Mi 3 Original Android Development] blur:
you are right, maybe nearly stable ;)

On other devices I have seen rarely stable versions, normally the snapshot versions are more stable than the nightlies.
[Mi 3 Original Android Development] diongdyh:
There's a snapshot for cm12.1 and it's less stable than nightlies in my experience. Other people seem to think the same way. It's supposed to be more stable than nightlies though. And i haven't tested the cm13 snapshot, so can't talk much about it
[Mi 3 Original Android Development] blur:
ok, thank you, I have installed the snapshot and will see ;)
[Mi 3 Original Android Development] NicRim:
Hi friends! Thank you for such a beautiful ROM for Mi4! It is perfect, but I should report you some bugs. There is a problem with the volume during a call. The slider works, but the volume doesn't change at all. It remains the same. This problem is both in nightly builds and in snapshot. Are there any ways to solve this problem? Other ROMs don't have this issue (AICP, for example).
[Mi 3 Original Android Development] wta03dental:
What is the differences between snapshot and stable version?Is snapshot better than nightly?Please enlighten me.
[Mi 3 Original Android Development] blur:
nighty vs. snapshot:

Some issues I have had the last days, like BT-audio and fc of apps like clock,

are vanished with snapshot and are returning with the todays nightly build.

So I am back to the snapshot version.
[Mi 3 Original Android Development] ryanrinaldhi:
Is it possible to true dual boot this rom with miui mm?

Thanks
[Mi 3 Original Android Development] TofikLupus:
Nope, cm wiki says it's not possible for security reasons.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] ryanrinaldhi:
Thanks, but i saw in cm official website, theres no that kind of warning anymore...

In the past yes that is, but i think it can be possible now
[Mi 3 Original Android Development] Dev Null:
OMG...

installing 12.1 SNAPSHOT over 0313 nightly results a bootloop.

Never keep old files on your phone where you can install them by accident :(
[Mi 3 Original Android Development] TofikLupus:
You really think it is now possible if it wasn't before? The warning isn't present in cancro wiki anymore because they changed it to that it supports both merged and dual partition layout. For merged partition layout there's no dual boot. But for dual partition layout it's still not possible because the warning was saying that CM requires encrypted data partition which is possible but the other system in dualboot won't be able to read from that partition and that's the problem.

MI3W 64GB/Tapatalk

---------- Post added at 13:56 ---------- Previous post was at 13:52 ----------

In fact that IS a must, not a recommendation. I have no idea who told you it's a recommendation. You switch from a nightly channel to snapshot channel. Same thing is for switching back and it REALLY isn't worth flashing just for a simple build that carries "snapshot" in its name, because it's nothing else than another nightly, just not built automatically. And next day, there will be no more snapahots, but anothwr bunch of nightlies, which means you have to full wipe again just to switch back from snapshot channel to nightly.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] ryanrinaldhi:
Ok...i see your point

Thanks for the answer ;)
[Mi 3 Original Android Development] JBolho:
I've read in Cyanogen's official announcement about the snapshot that nightly users shouldn't install the snapshot because the nightly version is already using a more recent code base.

About my issues, i reinstalled the ROM to use CM's kernel and performance looks better, and Antutu score went to around 45k. I'm still having performance problems in some games, like PES Club Manager, the game randomly stutters a lot, i don't know for sure if it's the rom or the game itself.

I'm to test the GPS now and see if it fixes on the satellites...

(Update):

Performance issues seem to be solved after i used Kernel Adiutor and disabled the Adreno Idler. No more lag for me...

One other thing that really helps is using the App Settings Xposed module and customizing a game's resolution to 1280x800. Then it's just a matter of rebooting the device, launching the game, and the performance is way more improved without sacrificing looks.

After some patience and tweaking with the "Faster GPS" app from Play Store, the GPS finally fixed on some satellites, and looks to be working. I'll be using it in a few hours to really test it on the road. So far on this device, until now, only MIUI had fast and flawless GPS, so let's see if that's different now.

Enviado do meu MI 3W através de Tapatalk
[Mi 3 Original Android Development] Me_Ashish_:
About the game lag issue. It happens with all ROMs with stock CM kernel. Installing custom kernel makes it fine.

You have to reboot device after setting resolution in app settings?

The issue I find with gaming is CPU frequency. I mentioned that while back but I never get reply from anyone who can answer why it happens http://xdaforums.com/showthread.php?p=64589323#post64589323
[Mi 3 Original Android Development] mig0r:
which custom kernel do you recommend?
[Mi 3 Original Android Development] Me_Ashish_:
For CM MM ROMs, Moshi is best. But its buggy and freezes sometimes. Can also use Fallen Shadow. But ZeurionX should be best.

Though I find CM ROMs having some kind of performance issue somehow with kernels too.

CAF ROM with its stock ZeurionX kernel is the best combination if you want gaming performance with smoothness even if you use it at lower frequency (to avoid much heating say).
[Mi 3 Original Android Development] mig0r:
so there is no custom CM kernel that's 100% stable? Then I'd rather stay with original CM kernel, as I'm not playing games ...
[Mi 3 Original Android Development] Me_Ashish_:
No! ZeurionX is stable.
[Mi 3 Original Android Development] mig0r:
tnx
[Mi 3 Original Android Development] Mr_Odwin:
I'm on an Mi4 and have a big issue with this and all other non-MIUI ROMs. I used Ivan's script to merge my system partitions. I use TWRP to install. Always wipe everything (cache, dalvik, system, even storage) prior to install. Installation of cyanogenMod and gapps (doesn't matter which package I choose, the problem persists) always goes smoothly, as does first boot. Then I usually do another boot and then get the settings how I like them.

The issues come when I start installing things from the play store. It's not every app install. It's usually an app with a larger file size where the issues arise. Half way through the app install the screen will go black and the phone will become absolutely unresponsive. The only way to fix this is to hold down the power for a few seconds. If the phone is plugged into a computer at this point I can see several drives in Explorer. Sometimes I get stuck in a bootloop and have to wipe dalvik cache to get it to start again.

It makes it pretty unusable for me.

Is there any fix for this behaviour?

(Tried again today and had to restore a backup after the issue persisted. I'm currently on the latest weekly xiaomi.eu ROM and its pretty rock solid for me, as was the global MIUI.)
[Mi 3 Original Android Development] vedantpro:
- Clock app is broken!!!

Whenever alarm rings, it crashes...

- sometimes phone screen becomes unusable.. Everything works except I can't interact with screen at all

Is there anyone with the same issue?? anyone of it???
[Mi 3 Original Android Development] TofikLupus:
Thanks, interesting, I will try it out. Anyways, meanwhile I tried out the package I mentioned before and as well as in 5.1.1, it works fine, the only requirement is SELinux being set to Permissive.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Dharani_V:
Thanks a lot :) As You Can See yours is going till 4100 mine was going only till 250mA. now i managed to find a temporary solution . Installed kernel Aduitor and set max freq to 2.2 and rebooted.. its fine now charging okay now
[Mi 3 Original Android Development] sushd99:
But I forgot to mention, if you want to use V4A with selinux enforcinng on 5.1, you need SuperSU installed.

I had to remove inbuilt superuser and flash SuperSU on cm12.1
[Mi 3 Original Android Development] TofikLupus:
No, that was a bug which sometimes happens. My charger is 2A, it's a nonsense that it charges at 4A.

MI3W 64GB/Tapatalk

---------- Post added at 17:24 ---------- Previous post was at 17:23 ----------

Oh, no way I'm gonna do that, I think I will just stay with my current installation then. It works anyway. Maybe I'll try yours some other time.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] sushd99:
I think its impossible for current to reach 4A.:eek: What charger is that?
[Mi 3 Original Android Development] TofikLupus:
It's a normal 2A charger, I said it's just a bug that happens sometime while calculating the charging current, it immediately dropped down.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] SenseiK:
GK R5 worked for me on Omni 6.0 anyone flashed on this rom?
[Mi 3 Original Android Development] djdarkrider:
Thank you [MENTION=5451053]linuxxxx[/MENTION] for your awesome job. However, the system profiles disabling lock screen, which was fixed after I posted it awhile ago in CM 12.1 thread is back.

It could be reproduced in cm 12.1 with this steps:

1. Have a profile that disables the lock screen (If you set to disable PIN you won't get the issue).

2. Reboot phone

3. Phone should turn on but screen will be black, nav bar buttons should show as well as signal icons etc.

4. Bring down notification bar, click on your profile toggle and switch profiles off completely

5. Turn screen off then back on

6. Screen should appear like normal.

In CM 13 it acts a little different:

1. I am on profile with protected lock screen.

2. I am connecting to home wi fi and another profile turns on - with disabled lock screen.

3. I can use my phone, but home button doesn't work, landscape apps run in portrait mode, I do not have extra reboot options.

4. I reboot my phone and get a black screen and status bar.

Disabling system profile eliminates this issue.

I have set up my phone to switch to profile without lock screen protection, when I connect to my home wi-fi and I have the black screen issue every time.

Please, let me know, whether you will look into it, or maybe I have to post somewhere else.

Thank you so much!
[Mi 3 Original Android Development] Dharani_V:
Its a Bug in the App. Max Current Will be 2A !
[Mi 3 Original Android Development] atomix18:
Deep sleep for an hour................................................................

And if you say it's normal..............
[Mi 3 Original Android Development] KiranP23:
can anyone kindly post link for supported Recovery . i am having issue with TWRP-v2.8.7.0-cancro-preview-20150621
[Mi 3 Original Android Development] TofikLupus:
I'm using TWRP 2.8.7.0 without any issues for more than half a year.

http://puu.sh/m7ixP/ece6b24dfe.zip

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Bertazure:
Yes, there should not be a problem with TWRP, but if you need, then this is the link for the official cyanogen recovery :-

https://download.cyanogenmod.org/get/jenkins/140731/cm-13.0-20151224-NIGHTLY-cancro-recovery.img
[Mi 3 Original Android Development] krishsns:
Privacy guard crash when swiped to device tab.
[Mi 3 Original Android Development] i snort flour:
If you close an app out completely that was using root access and it claims that it is still an app using root access how is that not bug? Some programs the notification functions properly and others it don't. It's a wide known issue on every cm across the xda forums since they included this feature into the rom. Anyway great rom. Rock solid like the unofficial. No real issues found on my end.
[Mi 3 Original Android Development] TofikLupus:
I agree, I just tried it out and the icon stays in the notification bar even after the root-accessing application was closed(also from the recent apps list).

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] sushd99:
When next snapshot arrives, will it be cm 12.1 or cm 13?
[Mi 3 Original Android Development] Bertazure:
Ofcourse cm 13. But the release of a snapshot build purely depends on the developer. If he thinks that a certain nightly build is stable enough, then he will release a snapshot based on that, perhaps making some slight changes.

But the developer may never release a snapshot.

What you can be sure of is that there will be a nightly release almost everyday. From the discussion in this thread, you can find a good stable one and flash it.
[Mi 3 Original Android Development] sushd99:
Oh thanks... I am right now on 12.1 nightlies, was thinking if there was a stabler snapshot before release of 13.0, it would have been better. Dont want to migrate to early 13.0 builds.

Thanks anyways.
[Mi 3 Original Android Development] TofikLupus:
I tried to switch USB mode to Charging only in Developer options but that didn't help much. My phone was discharging faster than charging, so I decided to turn it off. After about half an hour I turned it back on and found it's finally charging at the normal speed. Maybe the phone needs to be connected to a charger before booting up.

Oh and one thing. If you're not done charging and unplug the phone, you must repeat the process, turning the phone off and back on.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] romanpatel:
Proximity sensor not working on latest snapshot cm13.. Only m facing or its common issue???
[Mi 3 Original Android Development] mig0r:
yup, same here, turn off the screen and back on and it should work / Mi4
[Mi 3 Original Android Development] Mortihead:
I seems to find conditions of crash:

1) Install Google Photos

2) Set "Camera Shortcut" option

3) Make shoot in snap camera

3) Press "home" button (onscreen key)

4) Application SnapCamera crash.

Without "Camera Shortcut" option all ok without crash.

Clock settings is still crashing :( (nightly 17.03)