yashsingh1/xdaforums huggingface dataset:
[Mi 3 Original Android Development] mdfarazb2:
Tq SO MUCH BRO....?My all sensors are working fine now....BUT a new problem popped up...First When i did that stuff on terminal emulator (on cm12.1) everything went good i restarted my phone as mentioned. But it stucked on the boot logo then i clean flashed the rom (cm12.1) again..but then also it stucked...Then i also tried to flash cm13 But again no success, stucked on the boot logo...Then finally i restored my miui7...And everything now working fine here..Now my question is that...does that mean i can't use CM rom again..?? Why was that stucking thing happened...???
[Mi 3 Original Android Development] TofikLupus:
Well, since I didn't have this issue, I can't tell what's wrong. But, maybe - what partition layout do you run on? Classic(640+640)/Extended/MM single partition layout? Maybe the persist image was taken from a newer MM layout and it doesn't work on the old layouts(or vice versa). MIUI flash packages carry all the images in its zip as far as I know, so it's possible that it works because all the images are the same version. Maybe you can now try and flash CM again after flashing MIUI.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Ank_S:
Lot of random reboots

I just moved from last CM12.1 to CM13 21021016, thinking CM13 to be stable by now. But, I'm experimenting lot of random shutdowns. I'm using MI3W, stock kernel, stock settings & clean flashed CM13. Not even using AdAway, V4A or any other utilities. Also, tried disabling Adaptive brightness. Installed OpenGapps pico-20022016.
[Mi 3 Original Android Development] mdfarazb2:
I think I'm on 1.2Gb extended partition.... Ok I'll now try clean flashing CM12.1 again and let's see what happens..(fingers crossed)
[Mi 3 Original Android Development] TofikLupus:
Did you flash the MM miui or KK miui? If MM MIUI, then it's not exended but single partition layout.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] mdfarazb2:
No i didn't use mm miui till now i was on kk miui.
[Mi 3 Original Android Development] TofikLupus:
you should do an update to MM MIUI so you have just one partition of each kind. It doesn't ruin anything.

MI3W 64GB/Tapatalk

---------- Post added at 21:42 ---------- Previous post was at 20:46 ----------

Anyone experiencing SOD while booting after installing Xposed? I can't get exposed to work in latest nightly. In 20th feb build it worked.

MI3W 64GB/Tapatalk

---------- Post added at 21:58 ---------- Previous post was at 21:42 ----------

1) Live wallpapers aren't a bug, the support was removed to save some space because the ROM was too large for standard double partition layout.

2) I agree, this bug didn't exist before.

3) If you mean activating powersave mode in Settings > Battery, well, I tried and it worked fine, no battery drain, no vibration.

4) That existed for me back in January but now everything is fine for me. It happens very rarely anyway, if it ever happens at all.

5) Don't know about that one, didn't try any other launcher, I'm happy with the stock one.

6) Volume down+Power combination to make a screenshot works perfectly fine, tried with both 20th and 21th feb build.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] mdfarazb2:
Okkk bro will try that too once stable global build will release.....
[Mi 3 Original Android Development] TofikLupus:
it's not released yet? In CZ/SK MIUI community, we're getting MIUI MM updates since january 21st. If you want, you can use http://en.miui.com/forum.php?mod=viewthread&tid=209941&highlight=ivan%2Baosp MIUI thread to merge all partitions to the new MM layout without the need of flashing MM miui. I used this procedure myself, the only thing is that I had to do all the steps manually because the bat script didn't work for me. You can see the steps for manual merging right below the OP.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] fredek_lodz:
I have cm-13.0-20160221.

If I turn on Settings->Display&ligths->Prevent accidental wake-up is not possible to unlock phone, only reboot. Anybody confirm?
[Mi 3 Original Android Development] TofikLupus:
Yes, in today's build, a commit was added which should fix non-functional setting of preventing accidental wakeups, and, well, now it works more often than it should. Try to randomly cover proximity sensor and try to unlock the phone while doing so. One of the attempts should be successful.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Ank_S:
Maximum CPU Frequency not used by kernel
[Mi 3 Original Android Development] fredek_lodz:
Only call turn on display and enable unlocks the phone, manually unlock don't work.
[Mi 3 Original Android Development] TofikLupus:
It worked for me if i was randomly running my finger over the proximity sensor while pressing the power button repeatedly.

EDIT: So I tested it again and it didn't work this time. But i found out something different - after enabling this option, unlocking still works until you cover the proximity sensor for the first time, since then the unlocking stops working. I think there's a problem in the implementation of logic of scanning the proximity sensor and it doesn't reset once it detects less than 5 cm distance and gets either in a loop or just stops further scanning for some reason.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] fredek_lodz:
Mayby but don't work for me. I have active smart lock and unlock with MiBand.

In my opinion, the option Prevent accidental wakeup badly works, need fix.
[Mi 3 Original Android Development] TofikLupus:
Yes, it is wrongly implemented and needs a fix, I think it will come in upcoming builds because I bet it's not only an issue of cancro devices.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] bluviper:
with the latest nightly, I still have issues with streaming audio via bluetooth.
[Mi 3 Original Android Development] Ank_S:
Sometimes discharging even after plugging-in

22nd Feb Nightly
[Mi 3 Original Android Development] linuxxxx:
Lastest device-specific changes:

LiveDisplay kernel driver, it will work even better now with deeper integration with our hardware

FactoryResetProtection (persistentStorage.java cmhw class)

Various kernel and config minor fixes

Disabled proximity wakeup (did not play nicely with the device and prevent it from turning the screen on with power key)

IMPORTANT: before updating to 02 - 23 - 2016 nightly or newer you MUST turn off proximity wakeup check from your settings. If you update with that option enabled you won't be able to turn it off anymore unless you wipe your data. I can't help with this, it's an android limitation

Happy flashing
[Mi 3 Original Android Development] xMinistro:
Just installed the nightly build 2/22. The phone won't even turn on the screen once locked and screen off. I have to press the power button twice just to fire up the camera to turn on the screen. This is bad. Is there anyway I can revert to the old build?
[Mi 3 Original Android Development] blur:
I think you haven't read the posts above and:
[Mi 3 Original Android Development] xMinistro:
Oops. Yeah, it's fixed by just disabling the proximity sensor. Sorry about that.
[Mi 3 Original Android Development] blur:
Sorry I haven't such a charger
[Mi 3 Original Android Development] TofikLupus:
I have a 2A charger but it won't charge any faster until you use QC 2.0 charger. Fast charge is non-USB mode charging, for faster charging on computers without current limiting.

If you see AC mode, then it charges at ± the charger current, also depending on the USB cable used and power comnsumption of the phone.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Dharani_V:
Yeah I know That ! This Charger Is Qualcomm Certified and Works Well With Yesterdays CM12.1 Build !
[Mi 3 Original Android Development] TofikLupus:
Guys, got a question myself, will Viper4Android work on 6.0 with the setup used on LP ROMs? Meaning SELinux to permissive etc.

MI3W 64GB/Tapatalk

---------- Post added at 15:00 ---------- Previous post was at 14:58 ----------

Well you didn't mention that. In this case, I'm sorry but I don't know what to do. Mine is standard 2A 5V charger. I guess yours is then 9/12V?

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Dharani_V:
5V/2A And 9V/2A Will Test it myself now ! Thanks Anyway :)
[Mi 3 Original Android Development] atomix18:
Really bad thing is that even i have selected Power save mode in battery section, CPU is running on 2265 mnz, nothing has changed. And the other thing is that all cores are running most on 300 mhz 1497 mhz and 2267 mnz, but the mode is power save :), there are no offline cores like in Ivan's AOSP for example. I haven't changed anything in Kernel Auditor. When screen is off there is battery drain about 5-6% for an hour, deep sleep is only 50 - 60%. I did clean flash of the rom.
[Mi 3 Original Android Development] diongdyh:
Only 2 minutes of usage you've made your conclusion? *applause*
[Mi 3 Original Android Development] atomix18:
I wrote this because the same thing is in Mokee (CM) and AICP (CM) , so when i installed the ROM and saw the same thing with the Cores, you tell me what to do. You can see it yourself, install Kernel Auditor or other app and see. For me Battery modes only working in Ivan's AOSP.
[Mi 3 Original Android Development] Bertazure:
To learn more about quick charge, I googled and found this great post. Thought I will share with you guys :- http://lifehacker.com/charge-your-phone-in-half-the-time-quick-chargers-expl-1682276989

A question :- So the developer has enabled quick charge? And if I have a 9V/2A charger, I can charge the phone faster than using the original 5V/2A charger?
[Mi 3 Original Android Development] Me_Ashish_:
I installed Mokee nightly 2-3 days back. I experienced slow charge. When mobile data was on the charge speed according to ampere was less than 50 without data it was 250 about. But some hours later, the speed got normal. But it wasn't consistent.

Now with this ROM it is similar for me. The speed sometimes is normal but otherwise its less than 300. (The duration of is not very long?)

For people wondering about all cores running all times. You have to turn on MPDecision under CPU Hotplug which is turned off by default.

Every CM kernel reports wrong live CPU cores frequency always. You can set max frequency to something but you can see than some core hit more than that still. But if you will check frequency history, you won't find if CPU ran at more frequency which you could see in Live ones

Also I play Vainglory but CPU frequency doesn't run accordingly to the game. I set max frequency to 1.7 GHz. Played the game for 20 mins, the game was laggy. Checking previous frequency shows CPU ran at 1.5 GHz for like 5 mins only and higher them that never ran.

Later on I set min frequency to 1.26 and max to 1.9. Checking stats later on said CPU was running at 1.2 most of the time of gaming.

I have tried turning off and on per app battery profile which does nothing.

This issue never happens with any kernel other than CM. Since no other kernel is available I have stuck with the bugs I don't like (CAF Zeurian works but Wi-Fi doesn't)

PS why CM didn't care to add network bar indicator I wonder. It's essential feature and it shouldn't be like nobody asked it.

---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------

Turn on MPDecision under CPU Hotplug
[Mi 3 Original Android Development] Dharani_V:
Yes You Can !

---------- Post added at 07:46 PM ---------- Previous post was at 07:44 PM ----------

Can You Please Install This App https://play.google.com/store/apps/details?id=com.gombosdev.ampere and post Screenshots of it when Charging ? When i was on Cm12.1 it showed upto 470 mA on Normal 5V/2A Charger now its showing only 120mA and the phone is not charging at all . Im Using MI4
[Mi 3 Original Android Development] Me_Ashish_:
You noticed that 1st time or what. That doesn't mean quick charge (I believe there isn't anything which particularly shows that quick charge is working). Charhunf from wall adapter shows that every time (other than USB its always that mode of charging)
[Mi 3 Original Android Development] TofikLupus:
Here you go, mine isn't high either but I'll let it go for a while and see if that changes.

MI3W 64GB/Tapatalk

---------- Post added at 16:37 ---------- Previous post was at 16:26 ----------

So guys, lemme share some of my experience with the 2412 build.

The issues may only be on my phone but:

1) I went through more than 10 system crashes during the "Optimizing apps" screen and while unlocking the phone(the screen suddenly just flashed and went blank, I had to hold the power button to reboot)

2) I'm getting a lot of stutters and freezes, especially after reboot

3) the SoundFX tile is missing but that isn't such an important thing

Mainly the instability and lower performance is what bugs me. I'd like to try a clean flash but I don't want to lose my data.

One more thing that might cause the issues:

Flashed Xposed v79 and V4A audioFX replacement for Nexus 5 called "LolliViper.zip", if anyone has clue about it. In 5.1.1, all this worked well so I wanted to try it out here.

MI3W 64GB/Tapatalk

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

Oh, one more thing I forgot to mention:

After one of the crashes, I couldn't turn on wifi. I tried to turn on and off Hotspot, and afterwards wifi started to work.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] SenseiK:
Is it too early to use a Custom Kernel with this ROM?

Anybody got one working??
[Mi 3 Original Android Development] Me_Ashish_:
Didn't have any crash problems (have Xposed v78)

Zeurian CAF worked without Wi-Fi on unofficial CM (also on other ROM I tested)
[Mi 3 Original Android Development] foskikaiser92:
Anyone can tell me if i can begin to download and flash cm13 nightly on my mi3 or it is better to remain on 12.1?Now i'm on the 12.1 snapshot version(17th of november)
[Mi 3 Original Android Development] TofikLupus:
Stay on CM12.1, it's not worth using since not many features were added and a few things don't work as they should. Recording in camera doesn't work(Can't connect to camera) and HDR doesn't work as well. I'd rather wait till it gets more stable.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] aces170:
Nice will try in the weekend.
[Mi 3 Original Android Development] hermansyah19:
Actually this is the ROM that I've been waiting for. I'll continue to test this.

Sorry [MENTION=5451053]linuxxxx[/MENTION] I'll give more attention to the OP next time :D

Thanks for this great ROM.
[Mi 3 Original Android Development] sushd99:
V4A for 6.xx

http://xdaforums.com/showpost.php?p=64210561&postcount=20237

With installer 1.2 you can use it with selinux enforcing. I use a similar script [MENTION=2815792]maximumentropy[/MENTION] to run V4A on cm 12.1 with selinux enforcing.
[Mi 3 Original Android Development] Vasoconstriction:
Hey awesome job, I'm very grateful for all you and the Cyanogenmod team has done. I think the biggest issues right now are the BSOD's any idea if these are addressed or if these will be addressed? If it's been fixed with the device specific kernel fixes you just mentioned I'll be happy to return to Cyanogen and do some stress testing and provide logs if there are any problems.
[Mi 3 Original Android Development] vroyibg:
No more BSOD for a long time now. Flash latest nightly and experience yourself, how do you know there is BSOD if you didn't even used it.
[Mi 3 Original Android Development] Vasoconstriction:
Ah awesome! I'll definitely try it out again then. Last build of CM13 I was on was a week ago and I still got BSOD when doing intense stuff on the phone. I switch ROMs every few days, but since BSOD's are super annoying I skipped Cyanogenmod for a week
[Mi 3 Original Android Development] vroyibg:
I haven't got any BSOD since months ago, what is your device,do you use custom kernel, do you clean flash?
[Mi 3 Original Android Development] rorzer:
When Linuxxxx says to disable proximity wakeup, does he mean "prevent accidental wakeup" under the display and lights setting page?
[Mi 3 Original Android Development] rxl.noir:
Yup. That one.
[Mi 3 Original Android Development] kingmaxeps:
Does this ROM works on the new merged system partition (1.4gb)

And if it works how to flash It over miui mm
[Mi 3 Original Android Development] Dev Null:
I agree, awesome ROM. My problem was (?) also the BSOD, but I use unsupported hw: Mi4LTE

Anyway, didn't have a BSOD since using 2102 - not a really long time, but gave me hope.

This morning upgraded to 2302, hope it will not be worse.
[Mi 3 Original Android Development] wta03dental:
Is it possible to make incremental update for each nightly?
[Mi 3 Original Android Development] blur:
maybe it is possible,

but linuxxxx recommended to use the full rom for updating.
[Mi 3 Original Android Development] Anandababu153:
CyanDelta, using it for the past few weeks, works fine ...
[Mi 3 Original Android Development] TofikLupus:
I was using CyanDelta for several months and now I'm using CM Downloader, both work flawlessly. The idea behind delta updates is awesome and I don't see what's the problem.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Vasoconstriction:
Xiaomi Mi 3, ofcourse I had the stock kernel at the time of BSOD and ofcourse a clean flash, otherwise I wouldn't be reporting it. I guess you got lucky somehow, since lots of users were pestered by BSOD's. But I always had BSOD's after doing really heavy gaming (Unreal Engine 4 demo's) or when opening heavy apps in recents while I was unrarring something. So only if I really stressed the system I got BSOD's, you might be a lighter user and therefore have avoided the BSOD's.
[Mi 3 Original Android Development] vroyibg:
Maybe. Mine is MI4w and I'm not a heavy gamer. But i haven't seen anyone report SOD on MI3 here recently.

Anyone here who using MI3 please confirm the issue.
[Mi 3 Original Android Development] TofikLupus:
Haven't had one for about 2 weeks, but I restart often, so I dunno if the issue still exists.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] fredek_lodz:
Prevent accidental wakeup switch stil exist in built 20160223, it's correct ?
[Mi 3 Original Android Development] manoj.red.hat:
Yes it correct

proximity issue still exist
[Mi 3 Original Android Development] anshulajain:
I use a Mi4w and have BSOD once every 2-3 days. It usually happens when I connect to a USB charger on my laptop or a car charger. Sometimes it happens when the phone is kept idle for a long time.
[Mi 3 Original Android Development] Dev Null:
what's the issue exactly? I don't have any in connection of the proximity device. i use it to switch on/off the device, without any issues.
[Mi 3 Original Android Development] manoj.red.hat:
turn on prevent accidental wakeup you will understand [MENTION=1985735]Dev Null[/MENTION]
[Mi 3 Original Android Development] vroyibg:
Used to faced this but it was because i flashed custom kernel.
[Mi 3 Original Android Development] TofikLupus:
He probably meant an issue with the "Prevent accidental wakeups" option in screen settings. There was a bit of talk about it. Though, it would be nice if linuxxxx managed to get it working properly as I found this particularly a useful feature. Hope to have this feature fully functional in future updates :)

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Dev Null:
I always keep it turned on, still no issue I can notice.
[Mi 3 Original Android Development] mig0r:
I have it turned on and now I turned it off to see any difference. There is NONE.
[Mi 3 Original Android Development] manoj.red.hat:
Strange [MENTION=1985735]Dev Null[/MENTION] when I turn on accidental wakeup , I couldn't unlock my phone using power button with screen lock . it got locked
[Mi 3 Original Android Development] TofikLupus:
I don't know if this is still an issue of feb 22 build and later but linuxxxx has posted about what you should do to prevent this issue a few posts back. Try and find it if you haven't. The 22 feb and later builds should have this feature disabled, but you need to have it turned off before updating to 22/2 or later. Sorry if you've done these steps.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Rahuljs:
same issue is happening with me but when i twice press power button it unlocks
[Mi 3 Original Android Development] bluviper:
if you have activated the volume rocker to wake up, it would wake the phone easily.

and yes I also experience this, the power button does nothing unless you press it twice.
[Mi 3 Original Android Development] Dev Null:
kinda strange

never happened to me. always kept this switch ON, but have never had any issue with unlocking.

I use power button pretty rare, since I usually setup proximity based lock/unlock app, but several times a day I still used the power (and volume) buttons as well.
[Mi 3 Original Android Development] gupta_040:
hii [MENTION=571465]linuxxx[/MENTION] .

just wanted to know is there a feature to prevent app from closing in recent apps tray, as it is in MIUI. where i can prevent a specific app not to close from a bunch of recent apps just by swiping it down and it locks that particular app so that i can close all other apps at once but the particular app still remains running.
[Mi 3 Original Android Development] kingmaxeps:
Universal Remote doesn't work, any cure
[Mi 3 Original Android Development] vroyibg:
Battery statistics show that wifi consume 130% battery @@.
[Mi 3 Original Android Development] vedantpro:
Memory use by System keeps on increasing...

It starts off at 600-650 mb

After two days of use without reboot it reaches around 800-850 and keeps on increasing until I don't reboot.

Anyone having the same issue??
[Mi 3 Original Android Development] Dev Null:
No issues at all since 0223.

No BSOD, or memory leak, or anything I can complain.
[Mi 3 Original Android Development] xiamcm:
Thanks! For the message. I've been waiting for such info sitting on cm12.1.

I have mi4 lte too, now I will flash cm 13 at last.
[Mi 3 Original Android Development] Sylfaen:
I'm only one who meet the issue with 'auto-rotation' feature? It glitching, phone reacting to it for 1-2 minutes.

G-sensor is working correctly, but very-very slow and glitchy
[Mi 3 Original Android Development] TofikLupus:
I think I had exactly what you have, originally i thought the sensor stopped working because it stopped reacting to tilting, but after some time it started rotating itself without any tilting. Now that you said it, it makes more sense to me. But i haven't happened for a few weeks now. Just restart your phone.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Sylfaen:
Not helping at all, maybe full wipe will help, but that is undesirable for me :c
[Mi 3 Original Android Development] TofikLupus:
Do a backup of cache+data partition using TWRP and then wipe the partitions and try to boot CM afterwards.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] bluviper:
Ive been using Cyandelta to update, and yes same experience here.

Nothing to complain about. well maybe just the BT audio streaming/connection
[Mi 3 Original Android Development] blur:
Hi,

can I use delta-updates if there is a gap of number of days?

thx
[Mi 3 Original Android Development] Akiyo:
Bluetooth issues

Hey! I just switched over from MIUI 7 to CM13 - everything seems to work fine, except Bluetooth is completely borked for me (nightly 26th, 27th). Either its nearly impossible to find the device I am trying to pair, or it just say "Connected (no phone)" but the device, such as my car stereo, say it isn't connected. Fresh install, clean wipe on system, data, cache, original kernel (phone was stock before CM)

I have tried modifying init.qcom.bt.sh to change hfp from 1.5 to 1.7, nothing good came out of it. Is this issue known or its just me, and how can I further assist in resolving this? Because CM13 is almost perfect for me.

(Well, if I can get network speed in KB/s on my status bar without 3rd party app, that'd be awesome too)
[Mi 3 Original Android Development] manoj.red.hat:
On 24 feb cm13.1 nightly

case:- Wifi on 24x7

Bluetooth 24x7

problem:- Sot 2-3 hr

Battery drop at night drastically from past 2 days

Any Solution ? or except miui any ROM based on L/M for better battery life along with camera and stability?