yashsingh1/xdaforums huggingface dataset:
[Mi 3 Original Android Development] Me_Ashish_:
Since you replied this time. I clean flashed CM13, 31 December build with GAPSS only just for some screenshot purposes.

[IMG="Yesterday's Ampere Test"]http://i.imgur.com/mUhpLtk.png[/IMG]

After reflash:

[IMG="Test after 1st boot (didn't connect charger at boot)"]http://i.imgur.com/WcNyowb.png[/IMG]

[IMG="Reboot with Charger connected"]http://i.imgur.com/H5tYKhr.png[/IMG]

[IMG="Reboot without charger connected"]http://i.imgur.com/evKfxRW.png[/IMG]

[IMG="Again with charger connected"]http://i.imgur.com/tBoGYNi.png[/IMG]

{Kindly hover or long tap all the pictures in post to see the description}

Note that I ran today's 1st 2 tests for 20 seconds. And the last 2 tests for a minute. Screenshots were taken only after the speed didn't fluctuate much.

If not trusting the results by Ampere, yesterday I kept phone connected to charger for at least 10 mins gaining 0% charge.

The 3rd screenshot after reflash, as well as your screenshots are mistakes of the app and requires atleast a minute to give proper result. (Obviously impossible to have a legit more than 2 ampere speed I believe)

And I'm not sure if I should be really asking the below issue as its not a ROM issue totally (I suppose?)

I play Vainglory as game mainly. I get quite performance issue with stock CM kernel.

Taking look at CPU status, the graphic intensive game on stock kernel was using single core at higher frequency

[IMG="Frequency only for the time I played the game."]http://i.imgur.com/0Iso175.png[/IMG]

Also note that MPdecision was disabled so that all cores run atleast. Otherwise mainly 2 cores only run I believe (not sure)

This issue is actually not only with this ROM, its general issue what I get with CM based ROMs.

Earlier times when I set min frequency at 1.2 GHz, than the game mostly ran at 1.2 GHz.

This issue doesn't happen with custom Kernels in general.

The live CPU frequencies shown by stock kernels is also wrong as it falsely shows some cores running at more than the max frequency.

A noob question: Why doesn't CM has a network speed indicator. I'm not sure if I actually need to request this basic feature.

I'm not really complaining as I than install Xposed.

And due to the above reason CM is only usable with a custom Kernel and Xposed for me which are obviously not recommended when reporting bugs.

Would be glad if you would answer question I always had with CM.
[Mi 3 Original Android Development] BigFatTony:
Is this ROM compatible with the Mi4 3GB LTE version? Some posts on this thread seem to say so but in the introduction post and the official cyanogenmod wiki, there is no mention of an incompatibility.

Could someone clarify?
[Mi 3 Original Android Development] rajib4:
No, it's not supported.
[Mi 3 Original Android Development] DroidBot:
Fast battery drain issue solved in latest nightlies??
[Mi 3 Original Android Development] garyngkt:
Hi all just want to share my experience flashing from CM12.1

1) Flash as per instructions stated in OP. I just flashed from CM12.1 to CM13 using 20160102 nightly ROM. I am using normal partition and Open Gapps Pico version.

2) Reboot took a while and during optimizing apps suddenly screen went blank, not sure if still running in the background I couldn't power on the screen.

3) I forced reboot it by holding power button long time then it rebooted into CM13.

All seems well and nice. Thanks to all the devs for maintaining our device.
[Mi 3 Original Android Development] Akshay Varma:
which charger you used? :confused: I hardly get above 1200ma using in box 2a charger.
[Mi 3 Original Android Development] krishsns:
First of all happy new year to all. I flashed to latest ROM 02.

Simple marvells. Except the old bug.

Slow charging and camera performance.

sent from dharavi
[Mi 3 Original Android Development] KEKEMON:
Using 2jan build still charging slow
[Mi 3 Original Android Development] fredek_lodz:
Fast charging on the latest version 20160102 works only when reboot the phone with pluged charger.
[Mi 3 Original Android Development] blur:
here the same issue
[Mi 3 Original Android Development] sivabommakanti:
minor bugs i noticed :

1. my screen shows expanded view of the quickaccess toolbar when i unlock the screen many a times. So i have to first swipe up the quickacess 1st& then swipe again to unlock the screen.

2. no statbar notification when i switch on the torch (from quickacess). There was a torch toggle available in stat bar in the previous cm 11,12 builds.

3. The battery life is too good. :p
[Mi 3 Original Android Development] wky750:
Finaly, I can post reply here. :)

I am China CDMA user. I flashed the 0102 rom. It can find the sim signal, that is surprise for me! It's a good job!

But , "Unknown is displayed for incoming call" still exist. So the rom is can not regularly use.

Now I use mokee60.1, It fixed since 0102 rom.

Do Mokee and CM share the source each other? Will CM13 fix this soon?
[Mi 3 Original Android Development] KEKEMON:
Same here
[Mi 3 Original Android Development] patelumangv:
Next build may be.

http://review.cyanogenmod.org/#/c/126351/
[Mi 3 Original Android Development] ssomani123:
I can't switch my preferred network type to 3G or 2G. It is stuck on LTE (recommended). I have tried going to Settings>Mobile Networks>Preferred network type and using the *#*#4636#*#* code where it is stuck on LTE/GSM auto (PRL) and not allowing me to change to GSM only. I am using Mi4W.
[Mi 3 Original Android Development] ssss69:
The same happens to me
[Mi 3 Original Android Development] deaglecat:
Agreed.
[Mi 3 Original Android Development] krishsns:
Fast charging works when rooted. but also one new feature activated Fast draining.

sent from dharavi
[Mi 3 Original Android Development] garyngkt:
Yeah noticed charging is faster when plugged in then I reboot :D
[Mi 3 Original Android Development] garyngkt:
Start of new work day for the new year and updating to 20160104 nightly
[Mi 3 Original Android Development] Guiluge:
Yes, just updated to latest nightly : all good, and charging seems much faster this time !
[Mi 3 Original Android Development] xSmart007x:
otg works?
[Mi 3 Original Android Development] Guiluge:
You mean USB-OTG ? If so, it seems to work for me, but it depends what you wanna do with it
[Mi 3 Original Android Development] TofikLupus:
Is it after reboot with USB plugged? Or just unplugging and plugging back?

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Guiluge:
Just unplugging/plugging back.
[Mi 3 Original Android Development] TofikLupus:
Awesome, update downloaded, now downloading gapps.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Guiluge:
Okay, please tell us if you experience similar charging speed... or not :)
[Mi 3 Original Android Development] xSmart007x:
means that i can mount usb otg?

cause my tb files are on usb otg
[Mi 3 Original Android Development] garyngkt:
Any of u got issues with calls? I seem to have it even with latest nightly
[Mi 3 Original Android Development] Guiluge:
Oh ok, I have to find my OTG cable then and try !

---------- Post added at 09:59 AM ---------- Previous post was at 09:57 AM ----------

What kind of issues ? On previous nightly, it worked fine, but audio quality was not great at all.
[Mi 3 Original Android Development] xSmart007x:
do reply if works

thx in advance
[Mi 3 Original Android Development] TofikLupus:
Nothing has changed at all.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Guiluge:
Damn !
[Mi 3 Original Android Development] garyngkt:
I had a lot of dropped calls and sometimes the other party couldn't here me so I had to redial again. Trying to isolate the issue so just checking with u guys
[Mi 3 Original Android Development] TofikLupus:
Guys, so far I haven't updated Google Camera to the version for Android MM, because it's working, but I know that the MM Google Camera has problems with video recording and camera disconnections.

I mean, video recording works but it records in Camera mode(low FPS, changing framerate depending on light conditions, camera tends to disconnect after the recording is finished).

I just wanted to ask anyone who has the new Google camera, if the issues still exist?

If yes, i'll stay on the Google camera for Lollipop.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] krishsns:
There are still problem in android mm camera. Slow, and quality

sent from dharavi
[Mi 3 Original Android Development] DocWatsonITA:
Try Open Camera, is working very good for me
[Mi 3 Original Android Development] TofikLupus:
I have Open Camera but I like using Google Camera, and the 5.1.1 version works fine.

MI3W 64GB/Tapatalk

---------- Post added at 15:46 ---------- Previous post was at 15:42 ----------

By the way, has anyone tried to make a 5GHz hotspot with Mi3? Android M should allow to choose between 2.4GHz and 5GHz bands but it only shows 2.4GHz. I'd expect this phone to be capable of transmitting while it's capable of receiving 5GHz band.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] aslike2:
[MENTION=5451053]linuxxxx[/MENTION] Can you change the value of ro.telephony.default_network from 9 to 22? It will get mi4lte-ct find signal but do no harm to other variants (I guess).
[Mi 3 Original Android Development] djdarkrider:
I would like to report a bug(confirmed by multiple users), here are the steps to reproduce:

You will need Nova launcher(or any custom one) and Lock screen toggle in Notification panel.

1) Set custom launcher as default

2) Enable any lock screen

3) Disable lock screen by toggle or system profile

4) Reboot-you will face black screen and status bar.

To go back to normal pull down, enable lock screen and reboot. Also, there is no such problem using stock launcher .

Please, dear [MENTION=5451053]linuxxxx[/MENTION], consider looking into this. Thank you for all your hard work.
[Mi 3 Original Android Development] albertjol:
Flashing issues

Dear all

First of all, let's try to share my experiences with flashing this great new version

As I already ran my device on CM12.1, for a few months, I thought it should be easy to just dirty flash cm13 over it. However, the update freezed, at a message saying something like: detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system ...

After some investigation (putting some logging in the update script): this line did not finish:

run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");

It seemed that otasigcheck had a patch, this one: http://review.cyanogenmod.org/#/c/122539 . This patch was added in our cm13 nightlies, so this could be the problem. I simply replaced otasigcheck with some older checker (from cm12), and it worked, and the install went well.

I was using TWRP 2.8.7.0.

Today, I wanted to update to the latest nightly.

According to this post (https://www.reddit.com/r/cyanogenmod/comments/3ylilq/latest_version_of_cm_freezes_twrp_on_htc_m8/), I should try cyanogen recovery to flash, as it had a different shell which will not let otasigcheck freeze.

So I flashed the latest cm recovery nightly, but this assert was raised, giving the message: 'This package is for device: cancro; this device is .' :

assert(getprop("ro.product.device") == "cancro" || getprop("ro.build.product") == "cancro" || abort("This package is for device: cancro; this device is " + getprop("ro.product.device") + "."););

Apparently, no properties were set. For this time, I fixed this by entering this in an adb shell, while in recovery:

setprop ro.product.device cancro

And it worked...

Sorry for the long story. But now my questions:

- Did somebody of you also experience this problem (this freeze), and how did you fix this?

and:

- Who of you used CM recovery, did you also experience this assert? And what is a neat 'permanent' way to fix this, so i could just flawlessy flash upcoming nightlies without first setting properties?

Thank you

Other notes: the rom works well, but I have AdFree installed, and after every update, I have again to remove /system/etc/hosts and make a symlink to the updated /data/hosts. Everytime this hosts file is overwritten...

And I experience the 'slow charging', but that is already known...
[Mi 3 Original Android Development] atomix18:
Guys, are you having the problem with battery drain during deep sleep from systemui. When i go to battery in settings there are many awakes while the phone sleeps...
[Mi 3 Original Android Development] bigjailerman:
totally agree

---------- Post added at 02:45 PM ---------- Previous post was at 02:43 PM ----------

do you guys notice if you are plugged in with phone off you dont get the charging light?

---------- Post added at 02:56 PM ---------- Previous post was at 02:45 PM ----------

I ran into exact issue. It is the same thing I ran into the miui global beta builds, the cancro property name. In miui the work around was to unroot and not use cwm, use stock recovery. It didnt work here for me, I had to reinstall twrp (I was using the cm recovery) As soon as I rebooted into twrp I had no issue. I was above to use nightly.

The slow charging was a pain but I needed to reboot with charger plugged in. Now it went from needing 6 hours to fully recharge to normal 1.5 hours.

---------- Post added at 03:20 PM ---------- Previous post was at 02:56 PM ----------

can someone direct me how to disable fast charging?
[Mi 3 Original Android Development] Mr.trololol:
can you post a log in details? i wanna take a look at it.
[Mi 3 Original Android Development] garyngkt:
As of latest nightly I still need to reboot phone everytime to get faster charging
[Mi 3 Original Android Development] djdarkrider:
Here is a logcat from boot to black screen and a couple of minutes after. Taken from pc, phone was not touched. Hope it helps. Thank you very much!
[Mi 3 Original Android Development] mulde:
bluetooth music playing works for me with latest version from today!

fast charging only when rebooting with cable plugged in.

anybody having issues with vibration?

for me vibration doesn't work...
[Mi 3 Original Android Development] blur:
here it is not working, I have to think about a clean install.
[Mi 3 Original Android Development] AndroidWolf59:
Considering how "old" is my Mi3 I think Cyanogenmod13 is a great job.

And no problem if I have to restart to obtain a fast charger ;)
[Mi 3 Original Android Development] Mr.trololol:
Please take log in verbose mode while reproducing those steps for that bug, both before and after reboot.
[Mi 3 Original Android Development] TofikLupus:
Guys, did CM replace the Original stock camera with Snapdragon camera in CM13 recently? I see a lot of commits in the changelog related to Snapdragon camera(android_packages_apps_Snap). It sounds interesting to me. I'm running on CM12.1 now so I can't check it. I'm especially interested in next build with added HFR support, I'm just not sure if it's gonna work with cancro devices, i'm hoping it is though.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] ar4er:
Hfr/hsr working on cancro devices, i with freedcam, with good light, retrive 120 fps 720p and 90 fps 1080p. But snapdragon camera have some limitation, only 120fps and 720p resolution.
[Mi 3 Original Android Development] TofikLupus:
MI4 or MI3? I noticed MIUI Camera on MI4 shows a few more features compared to MI3. I know MI3 i capable of HFR too but so far i didn't manage to record even 720p at 60FPS(also no other resolution), it always ended up being 30FPS no matter what app I used and what i set. Oh but Slow motion video is working on MI3(well on MIUI, dunno if in CM) so at least that should be supported.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] blur:
I like this cam, it was in another cm13 rom, I think it was audihadis.

But I didn't find a way to bring it to CM13 official, I've taken the .apk file but the cam is not working under CM13 official.

You mean HDR? Thats working. too late ;)
[Mi 3 Original Android Development] ar4er:
And mi3 and mi4 support it. I have mi3. It from it:

H264, 13987.3kbps, 1280×720, 120.0fps

MP4A, 96.1kbps, 48.0kHz 32bit, 2 каналов
[Mi 3 Original Android Development] TofikLupus:
No, I mean HFR mode. High FrameRate is what it stands for.

MI3W 64GB/Tapatalk

---------- Post added at 16:41 ---------- Previous post was at 16:39 ----------

And btw I have the camera in my CM12.1, flashed it using the Oneplus One flash zip

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] lovefallen:
I'm on the 20160107 nightly and I can't switch to 3G. If I try to do it when in airplane mode, i see "invalid mode(-1)" in settings. I upgraded from 20151227 where it was "working", meaning every reboot put me in 3g and I had to switch a couple times to make 2G stick.
[Mi 3 Original Android Development] TofikLupus:
Thanks, i thought they both support it, at least their hardware if not software.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] vishal24387:
Slow motion vdo rec (120 fps) done by any app on mi3 looks really bad. Look like software trick. Doesn't look like real slow motion vdo rec. Look this vdo rec by moto G. It is really a good quality HFR rec.

https://www.youtube.com/watch?v=gK_uS1X6r3o&feature=youtube_gdata_player
[Mi 3 Original Android Development] Bertazure:
For all your questions, look here :- http://review.cyanogenmod.org/#/c/127107/

And these two links for our device:-

http://review.cyanogenmod.org/127266

http://review.cyanogenmod.org/127212

I think you will get your answers here. Really excited about this. Thanks developers.
[Mi 3 Original Android Development] ar4er:
Just leave it here

https://www.youtube.com/watch?v=NLBDMAhM2Ek
[Mi 3 Original Android Development] TofikLupus:
So I tried FreeDCamera on CM12.1 and I'm quite amazed the manual functions work on it, being it the only camera on non-MIUI ROM which actually has these features working even without Camera2 API. The only thing which I still can't figure out though, is high framerate recording. Timelapse setting doesn't work for me, giving me still a 30FPS result. And I haven't found any other settings for framerate apart from "Timelapse framerate", which is, of course maximum of 30, but in that case, if the video was recorded at higher FPS, the result should be slowed down. Am I missing something?

I will try it on also CM13 very soon, most likely today.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] ar4er:
Timelapse is timelaps. Hfr is hfr) Working hfr be on next relise. With hfr i have one problem, need find solution to correct video-hfr fps while record or after, because if bad light camcoder not return max fps and then video played not as needet. Snapdaragon camera have same problem with it.

Latest version:

https://drive.google.com/file/d/0BxyW21X5s5IubVkyRnpDeUxtLUU/view?usp=sharing

Cm13 and based on it roms have problem with Render Script engine and on it roms focuspicking not working.
[Mi 3 Original Android Development] rodeo1974:
Hi, Call Recorder working ?
[Mi 3 Original Android Development] fredek_lodz:
Lack of access to VOICE_CALL in the ACR.

I hope that dev will fix because in CM12.1 worked well.
[Mi 3 Original Android Development] fredek_lodz:
On latest 20160110 build aplication camera make force closes when we switch to film mode. Need clean app data to use again. Anybody confirm?
[Mi 3 Original Android Development] amarjot25:
Howz d quality of camera nw?
[Mi 3 Original Android Development] blur:
​

Here the same, I tried it with a clean install, but switching to video does make a fc.

EDIT: I tried it with thte google camera, the same issue, also with build 20160107.
[Mi 3 Original Android Development] linuxxxx:
Known issue, already fixed. We're currently investigating if there's a better one. Google camera 3.x does not support video recording on non - nexus device, they're two different issues. Any other camera app will be fine for today

Inviato dal mio A0001 utilizzando Tapatalk
[Mi 3 Original Android Development] vishal24387:
Any possibility of more improved hdr pic quality?? And any possibility for support for good quality HFR vdo rec like Moto G or G2 have inbuilt in their stock camera?? :)

Sorry for asking too much.
[Mi 3 Original Android Development] garyngkt:
I noticed with recent versions, sometimes I have to rekey in the wifi password for certain SSIDs, any of you have the same issue?.
[Mi 3 Original Android Development] userprince:
+1

If I select different SSID from notification toggle then I need to type the password again.
[Mi 3 Original Android Development] rajib4:
I had the same issue with current version of google camera. Download the google camera version 2.7.008 from apkmirror.com here is the link this is the latest google camera version which works absolutely fine. I haven't faced a single issue after installing this one. But just make sure of one thing, don't update it through play store then you will be back to square one again :p

Hope this helps.

Cheers :cool:
[Mi 3 Original Android Development] sivabommakanti:
Is charging speed fine now on 10jan build?
[Mi 3 Original Android Development] deepesh.tickoo:
any fix for supersu?

i tried installing 2.52 beta through recovery, it didn't work.
[Mi 3 Original Android Development] TofikLupus:
Why would you want to use SuperSU, CM has built-in root access manager.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] deepesh.tickoo:
because cm root doesn't work everywhere, like titanium backup.
[Mi 3 Original Android Development] blur:
I have no problem with stock-root and Titanium since the first nighly.

---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------

thx for the tip, but I like the snapy cam and will wait for the fix.

---------- Post added at 06:45 PM ---------- Previous post was at 06:09 PM ----------

here it is in no time:

http://review.cyanogenmod.org/#/c/127499/

:highfive:
[Mi 3 Original Android Development] deepesh.tickoo:
But I'm unable to get Titanium backup to work even once.
[Mi 3 Original Android Development] sushd99:
I do this on cm12.1.. might work with cm13

First enable cm root apps + adb

Then install SuperSU app from play store and grant it cm root access

Then in SuperSU app, go to settings and scroll down to full system unroot

After unroot, reboot and make sure SuperSU app got uninstalled, it should get uninstalled automatically after system unroot

Then wipe dalvik and cache and flash SuperSU zip

Check the version of SuperSu compatible with marshmallow.

This works on cm12.1 not sure about cm13, try and see.
[Mi 3 Original Android Development] garyngkt:
OK thanks for confirming this :D

Also I'm having dropped calls. While talking halfway suddenly the other party not able to hear me anymore
[Mi 3 Original Android Development] sumyt:
Only annoying bug that bothers me as a daily driver phone was the slow charging issue , confirmed that after reboot (keep the charger connected) charging works as normal .

On 20160110 build CM13 .
[Mi 3 Original Android Development] pkatsaras:
Does anyone with root explorer, face force close of the app when trying to open it?
[Mi 3 Original Android Development] blur:
no, its working fine here.

---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------

there is no need to install SuperSU
[Mi 3 Original Android Development] pkatsaras:
Are you in the latest nightly 20160110?
[Mi 3 Original Android Development] blur:
Sorry, no, I avoided to flash that nightly because of the cam issue.
[Mi 3 Original Android Development] Pallmalli:
+1. Same here. Latest nightly.
[Mi 3 Original Android Development] sumyt:
anyone have any idea workaround on the slow charging issue ? really tired of rebooting everytime when i need to plug it to wall .
[Mi 3 Original Android Development] kakho55:
Reverse back to cm12.1 ...

CM13 battery drain fast and charge slow.
[Mi 3 Original Android Development] sushd99:
You did not read the whole thing and you dont know in what context I said.

He wanted to know how to switch from cm root to SuperSU
[Mi 3 Original Android Development] sumyt:
Ya I think I will do that . just need a reformat and move abit of data quite abit trouble .

Do u have idea which CM12.1 version is the best ? Do I go for latest CM12.1 nightly (20151222) or the CM12.1 snapshot (release) .