yashsingh1/xdaforums huggingface dataset:
[Mi 3 Original Android Development] JBolho:
For me the solution was exactly the opposite. Using the stock CM kernel worked better than with Mosshi's... The only thing I had to do was disable the Adreno Idler.

App Settings sometimes can apply the custom settings without rebooting but normally it is necessary to reboot the device and launch the desired game from within App Settings at least for the first time.

Enviado do meu MI 3W através de Tapatalk
[Mi 3 Original Android Development] Ferrans90:
My sensor is no problem on snapshot cm13. Install CPU-Z and check Proximity sensor in sensor tab. If Proximity sensor's value remains blank when blocking it via finger, try reboot or a clean reinstall (wipe and install cm13)
[Mi 3 Original Android Development] miss:
to sound the FM radio, first find the favorite station and to hear her off screen, with display can not hear either by headphones or loudspeaker.

also with last night 17
[Mi 3 Original Android Development] Korozu:
How is the battery life?
[Mi 3 Original Android Development] Anandababu153:
Yes it is.

Clock crashes while triggering any alarm.

Screen becomes non-responsive to touches. Have to hard reboot. (Volume buttons will work, but not navigational button)
[Mi 3 Original Android Development] Bertazure:
I'm on CM 12.1 with TWRP, stock partitions.

But now, I want to merge the partitions and come to CM 13. I know that this ROM doesn't require merged partitions. But still, I want a larger system partition to flash larger GApps package.

Can I just flash the latest MIUI fastboot ROM from the official website using MI Flash tool? Will this method just merge the partitions correctly? Because I think this maybe the easiest method now.

I might be wrong. Please someone tell me. I don't want to brick my device.
[Mi 3 Original Android Development] mahla13:
Back to Stock

going back to stock rom from CM is a bit difficult, pls help!
[Mi 3 Original Android Development] Guiluge:
This comment is not relevant to this thread, but anyway, here's an answer.

It's actually quite simple to revert back to stock MIUI, but you'll need to do a clean flash to ensure a nice revert.

Just retrieve a fastboot image here : http://en.miui.com/a-234.html

You can then flash it using fastboot (or MiFlash if you're a Windows user), and you'll have a fresh stock install.

Of course, you'll lose all your data in the process, so backup first.

---------- Post added at 10:32 AM ---------- Previous post was at 10:28 AM ----------

Is it still an issue in today's nightly ? I'll flash it this afternoon, but just in case you already did, I'm asking :)
[Mi 3 Original Android Development] diongdyh:
The latest MIUI from the official forum won't merge your partition since it's still on Kitkat. You've to download the beta fastboot MIUI MM which is leaked by testers to get your partitions merged. Go to Mi3 General and MIUI MM thread to search for it, any version will do, as long as it's a fastboot file. And flash it with MiFlash then you're good to go.
[Mi 3 Original Android Development] Me_Ashish_:
Launch from App Settings? How?
[Mi 3 Original Android Development] Anandababu153:
I'm still on 17-Mar nightly. Yet to update to 18th ..

In 17-Mar

Clock crashes every single time a alarm triggers.

The non-responsive touch is more like a random issue, but only while disconnecting the active calls I observed it (again a hit or miss)..

My guess, its related to the Proximity sensor changes which were introduced around Feb-20-ish ...
[Mi 3 Original Android Development] JBolho:
On the top right, next to the save icon, tap on the 3 dots menu, you'll see 3 options. The first one is "launch"... ;)
[Mi 3 Original Android Development] mi3user:
Should I update to latest nightly or snapshot?

I am Currently in 5 March Nightly.
[Mi 3 Original Android Development] TofikLupus:
Definitely nightly. Snapshot will have the clock bug as well as nightlies but in nightlies it will get fixed unlike the snapshot as it only gets released once a time.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Guiluge:
Okay, thanks, I'll flash latest nightly and try to reproduce this bug... or not.
[Mi 3 Original Android Development] Bertazure:
Thanks for your reply. I have found it.

By the way, I didn't know that MIUI China Developer ROM was still on KitKat.
[Mi 3 Original Android Development] LKc丶:
The developer rom has been on marshmallow for a long time.[emoji14]Here's the link:

Flash with MiFlash: http://bigota.d.miui.com/6.3.17/cancro_images_6.3.17_20160129.0000.14_6.0_cn_b43baea4ec.tgz
[Mi 3 Original Android Development] TheCarryEnd:
Is this worth installing now? Clock bug fixed?
[Mi 3 Original Android Development] mdfarazb2:
Is there any notification pulldown and ui lagging issue in CM 13????
[Mi 3 Original Android Development] Guiluge:
I'm only experiencing (rare) lags when my screen is off and I'm receiving app notifications. In other cases, general UI and notification pulldown are super smooth.
[Mi 3 Original Android Development] cssoz:
ya it doesn't work and im on 20160316 - snapshot of CM 13. full wipe clean flash.

Bluetooth audio loops and pauses (1 second. 2 seconds etc)

---------- Post added at 11:27 PM ---------- Previous post was at 10:33 PM ----------

To keep this simple

My phone:

- Mi 3W (was on Beta Android 6.0)

- TWRP 3.0 (flashed)

- Currently have SnapShot CM 13

Steps i did to flash CM 13 (clean install):

- Full wiped (including internal storage)

- Loaded back up Miui 7 then transferred cm 13 + Open Gapps

- TWRP > installed CM 13 > wipe cache/ART cache > flash GApps

- 5 - 10 min 1st boot > AMAZING performance! (Thank you CM team!)

Bug: Bluetooth audio bug.

- it plays music for 1 second > pauses for 2 - 3 > plays for 1 second > repeat

- I have searched here + official CM 13 - Mi 3 forums, no one has a solution

- I have try all of the work arounds > nothing worked

- Have wiped cache/art cache, at least 3 times over a 16 hour period.

- Googled some more, this bug exists since the beginning of CM 13 and it's across many devices also.

ADB Logcat.txt (~30 min) 5mb

https://drive.google.com/file/d/0BzVTh1-EkAQATjZsRmstQ1VVcVE/view?usp=sharing

Please see if this will help to solve the bluetooth audio bug.
[Mi 3 Original Android Development] Arman_Koradia:
I am currently on MIUI 7 MM Beta Tester for Global ROM. I have TWRP installed and my device is rooted.

Do i need any extended partition or anything to flash CM 13? Or i can flash like this by first wiping everything clean ??
[Mi 3 Original Android Development] luigieg:
Its in the FAQ, post #1
[Mi 3 Original Android Development] Arman_Koradia:
You mean to say this?

Does this work with new Miui MM (6.1.21+) partition layouts?

Yes it does, you can use any partition layout you want (miui KK, extended system1 or miui MM), CyanogenMod will adapt itself dynamically.

I once had a misfortune so don't want to take any risk. So making it double sure. Currently on 6.3.17 so i believe i can proceed without any risks!(following steps correctly)
[Mi 3 Original Android Development] thinhx2:
I flash rom 13 and use navibar, 3 Keyboard navigation is vibrator. Sorry i bad english
[Mi 3 Original Android Development] holysatan:
insufficient storage space available in system partition error 70 while flashing gapps pico/nano
[Mi 3 Original Android Development] fredek_lodz:
Today I tested phone encryption... this option not work regardless of what is recovery: twrp 2.7.0, twrp 3.0.0, cm recovery, rom stable, nightly ... this is a dummy ... it is crap, no security option. Any solution?
[Mi 3 Original Android Development] Bertazure:
Oh!! ? Thanks...

Great to know that...That's what I thought before.

Then making merged partitions is going to be so easy......
[Mi 3 Original Android Development] vualeks:
Streaming problem

Hi,

I've just flashed the latest snapshot (cm-13.0-20160316-SNAPSHOT-ZNH0EAO1QN-cancro.zip) on my Mi4 (16GB, 3G only) in hope that it might not have a really annoying bug that version 12 of cyanogenmod also had and it seems that it's still there. The problem that I experience (and I couldn't find that others were complaining about it) is when I try to stream play on 3G any podcast using Podcast Addict (or any other podcast app that I tried) the app just gets stuck on connecting to feedproxy.google.com and then timeouts. On wifi streming works just fine.

Now, I've tried this to confirm:

1. shared 3g connection on my Mi4 (wifi hotspot) and connected another Android phone with podcast apps, tried streaming and it worked ok.

2. tried that old MIUI 4.4 rom on my Mi4 and streaming worked ok also

3. watched network traffic with 'Ping tools' and it showed that there is no traffic after the app tried to connect to feedproxy. On MIUI 4.4 it showed full speed traffic

that confirmed to me that it is not 3g provider or phone problem, but cyanogen related. Can anyone else confirm or look into this?

Btw, thanks for your work, other than this bug, the room looks and works great :)

EDIT: I've just found a workaround, when connected through VPN, it works ok. I kinda don't like those VPN apps, but I guess that's what it is...
[Mi 3 Original Android Development] dchinu:
Bug report on Snapshot release (Regression) : wifi connection is buggy from quick settings panel. It forgets password and fail to switch between saved networks from QS tile (password prompt). works ok on wifi settings menu. Same for bluetooth QS tile.

Working ok on 5/3 nightly.
[Mi 3 Original Android Development] thinhx2:
I use cm13 19/03 dont open next picture in galery. Sorry i bad english
[Mi 3 Original Android Development] mig0r:
Tried the Snapshot. Couple of FCs, definitely not more stable than Nightly, so I'm back to Nightly...
[Mi 3 Original Android Development] vedantpro:
Maaaaannn... Has anyone also experienced bsod.. Like phone is running normally, you are using it browsing or chatting and then poof, black screen.

I have already experienced it thrice in past 5-7 days. It definitely was not in earlier builds

After 1st March or so the builds are just getting worse and worse imo. New bugs are popping up, with old bugs intact.

I really though getting a snapshot means we are getting more stable builds but ughhhh

I can no longer use it as my daily driver, there are just too many bugs >_<
[Mi 3 Original Android Development] thegreatsid:
1. Can't change in call volume during calls, or at any other time.

2. Bluetooth problem still persists

3. Biggest problem for me, for some reason, audio recording volume is really low in Stock sound recording app and Recforge II which I have to use for YouTube videos. Don't wanna go back to cm12.1, of someone has a fix please share. :/

That being said, no bsod or other issues for me on 20160318.
[Mi 3 Original Android Development] vedantpro:
Use build for atleast 3 days... It is then when the bsod and other issues come for me( no manual reboots in between)
[Mi 3 Original Android Development] fmcheetah:
Hi,

Just keep in mind there is no google stuff (playstore,..etc..) in this Dev. Rom.
[Mi 3 Original Android Development] Anandababu153:
21-Mar Nightly,

Tested the clock bug... Its fixed. tried 2 alarms. Works fine. Can you confirm this?

New Bug

Was on a call like 2 mins, then got a 2nd call waiting.

Attended the 2nd call, guess the 1st caller hanged up just before attending the 2nd call.

2nd call went quite normal. Disconnected the 2nd call.

Saw a pop-up in home screen with 2 options, (like 1 have not attended 2nd call)

1. Ignore the 2nd call

2. Attend and put call 1 in hold.

I chose option 2 ( 1 or 2 doesn't matter) then immediately a reboot happened.

Anyone facing like this in today or nightly build prior? (I didn't try to reproduce it again)
[Mi 3 Original Android Development] Guiluge:
Yep. I triggered an alarm this morning, no problem at all.
[Mi 3 Original Android Development] babacyber:
Hi Guys - I am on the 19th March Nightly build and my proximity sensor does not work. As a result the screen does not shut off when on call and my ear presses the mute and other buttons.

Anyone else has this similar problem?
[Mi 3 Original Android Development] TofikLupus:
Have you also tried accessing clock settings? It's still crashing for me. I'm on today's nightly just to check if the issues are gone.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Anandababu153:
Tried to visit every settings in the clock app... No crashing at all..
[Mi 3 Original Android Development] Guiluge:
I just tried to access clock settings : it's still crashing for me too !
[Mi 3 Original Android Development] pranavv.shriwas@gmail.com:
Is someone experiencing proximity sensor issue on snapchat and nightly???
[Mi 3 Original Android Development] TofikLupus:
Today i tested proximity sensor in Sensors Multitool and it works for me. Try it in some test mode or sensor testing app, if it works there, there's not much to do.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] pranavv.shriwas@gmail.com:
its not workin while calling
[Mi 3 Original Android Development] mig0r:
mine works, mi4.

But what bugs me is that the screen needs like 4 seconds to wake up when reciving a call, so I have to wait those 4 seconds to answer a call..

---------- Post added at 04:12 PM ---------- Previous post was at 04:09 PM ----------

try flashing open gapps MINI version instead of nano or micro -> stock google Clock app replaces Cyanogen clock, everything works
[Mi 3 Original Android Development] Guiluge:
Since it's not a deal breaker for me, I'll stick with Cyanogen clock until they fix it :)

Thanks for the hint anyway !
[Mi 3 Original Android Development] vedantpro:
Nightly 3/21

- All clock bugs fixed (for me atleast)

- can change to power saver manually from both settings and quick settings (finally)

- disappearance of toggles is still an issue ( for me only Hotspot toggle )

(will wait to check for bsod, unresponsive screen and other once in a while bugs)

// audiofx crashes sometimes when other music player is opened/running
[Mi 3 Original Android Development] Guiluge:
I'm on 03/22 nightly (today), and clock settings still crash here...
[Mi 3 Original Android Development] Anandababu153:
Are you updating by using Delta updates? a clean flash might help?

(but again this is not a serious issue to lose your precious data and spend another 30-45 mins settings up your phone again).
[Mi 3 Original Android Development] Guiluge:
No Delta updates, I prefer flashing full nightly updates.

And as I stated yesterday, it's not really important for now.
[Mi 3 Original Android Development] fmcheetah:
+1
[Mi 3 Original Android Development] Anandababu153:
Ok, by saying "full nightly updates", i guess you do a dirty flash without "factory reset / Data Wipe" right?
[Mi 3 Original Android Development] Guiluge:
Well, I'm updating wih CM Updater, so I wouldn't consider this method as dirty, but yes.
[Mi 3 Original Android Development] xSmart007x:
am i the only one never had clock crash?

im using stock gapps btw and been dirty flash like i cant even remember when the last time i did clean flash
[Mi 3 Original Android Development] fredek_lodz:
I have crash too, in clock setings... probably since 14.03 build (asop base upgrade?) ...

[IMG="CRASH clock setings"]http://fredek.no-ip.org/XDA/Screenshot_20160316-081106.png[/IMG]
[Mi 3 Original Android Development] TofikLupus:
Google clock (included in stock gapps) vs. cLock (Cyanogenmod clock app) is the key. Recently, CM has some issues with their stock clock app, and installing stock gapps replaces it with the one from Google which works fine.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] nxnayx:
Can I do a dirty flash from the snapshot?

I can install the last nightly.

Thank you in advance!
[Mi 3 Original Android Development] Guiluge:
I guess it would work, but I strongly suggest a clean flash here.
[Mi 3 Original Android Development] TofikLupus:
No, it will NOT work. Will definitely get into a bootloop.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] fredek_lodz:
Yes work.

I make clean install snapshot (full wipe system, data, cache), tested then upgrade (dirty flash) to 12.03 nightly... no bootloop.
[Mi 3 Original Android Development] Guiluge:
Even if you flash the nightly released right after the snapshot ?

EDIT : well it seems to work for some people... Anyway, clean flash is the best here.
[Mi 3 Original Android Development] TofikLupus:
Some guy a few days ago complained he got a bootloop switching from Snapshot stright away to Nightly. It was last week, don't remember the day, you can find it in this thread if you want.

MI3W 64GB/Tapatalk
[Mi 3 Original Android Development] Guiluge:
I know, I found it strange... but what can I say, I never use snaphosts.
[Mi 3 Original Android Development] Jongla:
Wifi keeps automatically connecting and disconnecting to my laptop's hotspot even after turning wifi off.

And 10-14% discharge overnight mostly caused by wifi.

Latest Nightly.
[Mi 3 Original Android Development] fredek_lodz:
I installed google clock, problem solved, thank you :)
[Mi 3 Original Android Development] abhisek de:
Download repartition.zip and flash it via cwm.... First take backup of your system and then after flashing that zip advance restore your system...and u r done ... After doing this flash twrp and then flash cm13 rom and only pico gapps and then reboot...if u flash any there bigger gapps u might get fc(s) on boot

For eg -Google play services mainly and play store ...

---------- Post added at 04:58 AM ---------- Previous post was at 04:55 AM ----------

After updating to the latest nightly my mi 3 gets switched off occasionally....
[Mi 3 Original Android Development] thinhx2:
Cm13 22/3 i flash rom,no flash gapp,setup wizard is f.c
[Mi 3 Original Android Development] Dev Null:
Snapshot's been runing for 135 hrs, without any problem.

No FCs, no WiFi-, or BT problem.

Standby power consumption is a bit more than expected, approx 1.5% per hrs. It was nearly 1% per H with the nightly of 0313. Maybe a few settings are still different.

Vibra practically doesn't work (sometime works, but just for a few minutes, usually doesn't do anything; slightly worse than with latest nightly, but just a feeling), but I'm afraid it is going to be a hw issue. :(
[Mi 3 Original Android Development] geoemm:
I have a merged partition and cm12.1(snap) + twrp. Can I do a clean wipe and flash cm13 (snap) directly?
[Mi 3 Original Android Development] diongdyh:
Yes
[Mi 3 Original Android Development] vedantpro:
I'm facing this problem for the past 10 days... But FCs doesn't occur until 3rd or 4th day for me i.e. At least after 50 hrs of runtime

---------- Post added at 11:03 AM ---------- Previous post was at 10:36 AM ----------

Anyone knows how to make otg work in recovery (twrp)....
[Mi 3 Original Android Development] Jongla:
just connect it,go to settings,mount USB storage.

It doesn't find the OTG at once,but i keep tapping it USB storage and it connects after 4-5 tap.

Edit:The "keep tapping" part isn't necessary maybe.or you can just wait and tap once. :v
[Mi 3 Original Android Development] vedantpro:
I have tried this thousand times may be :P... Not working...

I just want to take a nandroid backup

It used to work with twrp with miui but since cm 13 it never worked in recovery, even in latest 3.0.0 it doesn't work

My goal is to just create a nandroid backup. Any help would be appreciated
[Mi 3 Original Android Development] thinhx2:
i use all version cm13 and now i use cm13 23/3/2016. how to connect wireless speakers via bluetooth. my friend use iphone 4,asus zenfone go can connect via bluetooth. i use mi3, i dont see wireless speakers on bluetooth. please support wireless speakers. sorry i bad english
[Mi 3 Original Android Development] Bertazure:
Good....this was perhaps easier. But I have already flashed latest China Dev fastboot ROM(from official website) using Mi Flash(flash_all.bat) and have got the merged partition without any problem.

---------- Post added at 08:53 AM ---------- Previous post was at 08:46 AM ----------

I was on CM 12.1 stock partitions.

To get merged partitions, I flashed :-

1. Latest China Dev fastboot ROM(from official website) using Mi Flash(flash_all.bat) and got the merged partition without any problem.

2. TWRP recovery 3.0.0 using Flashify.

3. CM 13 Snapshot using TWRP.

4. Opengapps Stock (Mar 20 version) using TWRP.

And then cleaned cache and rebooted.

Everything seems to be fine. The standby time is awesome, hardly any battery drop. The ROM is very smooth and performance is great. Many thanks to all developers out there, specially linuxxxx.:)

The only problems are:-

1. In CM File Manager, the small icon at the top left (which shows the folder details and size) is not there. Instead, in its place, an exclamation mark is shown. Clicking on it pops up a message showing 'File system is not available.' or something like that.

2. If Google Camera is updated to latest version, video cannot be captured.

When I switch to video from camera, it says 'Camera error-Can't connect to camera.'

But once or twice of all these times, I have been able to successfully switch to video mode, but then it shows 90° rotated view stretched out to fill the screen.

However after uninstalling the latest update of Google Camera(ie. reverting back to preinstalled version of Google Camera), everything works fine.

In the Play Store, the reviews for this app is not great(actually bad) recently.

3. Sometime the quick tiles keeps missing, like the Torch or Compass. Yesterday at night, the Torch did not work. Tapping on it seemed to do nothing. Only after a reboot, it started working fine.
[Mi 3 Original Android Development] Hattiwattiman:
Hello, I just did a clean install yesterday with the latest nightly and my proximity sensor did not work at all. I had issues with the proximity sensor on the CM 12.1 also. It worked very poorly and my ear was activating all kinds of stuff from the quick draw panel etc.

I downloaded an app from Play for calibrating the proximity sensor and now it works perfectly! ATTENTION, you can try this at your own risk and I am not responsible for any malfuntion of the phone. The app requires root access and this is why I wanted to put a disclaimer here. It should work just fine and it also worked for my friend who has the same issues with CM 12.1.

Both phones are Mi 3 WCDMA.

Huuuge thanks for Linuxxx who made the work for 12.1 and 13.0 for us!! :good:

PS. I hope I did not brake any rules as I am new at the forum.
[Mi 3 Original Android Development] thinhx2:
last build cm13 23/3 and mokee 24/3. have 1 big bugs:

Calls to xiaomi mi3, mi3 reboot,dont reply call. please fix. now i use d.u rom. call no bugs
[Mi 3 Original Android Development] SikupleDroid:
I already flash the ROM, its OK. But when I'm flash the pico gapss it get an error it said that I don't have insufficient space, and tell me that I have to download smaller one. But I flash is pico, the smallest one. Arm-6-pico
[Mi 3 Original Android Development] titogrima:
You need merged system partitions to flash gapps on CM
[Mi 3 Original Android Development] SikupleDroid:
Can yo tell me how to merged? Or where is the tutorial thread link
[Mi 3 Original Android Development] fmcheetah:
Hi,

same problem for me too !!
[Mi 3 Original Android Development] Jongla:
? maybe faulty cable?I don't think ROMs have any effect on OTG support for recovery.
[Mi 3 Original Android Development] fmcheetah:
Hi,

I can confirm that it does not work, it is a CM13 problem , everything worked fine on the latest MIUI 4.4.4. with CWM R7.

In CWM i did not test OTG. In TWRP 3.0 it is not working!

Ferdinand
[Mi 3 Original Android Development] abhisheksharma26jan:
Latest nightly (23 march), reboots on every incoming call. Please Fix :rolleyes:
[Mi 3 Original Android Development] ssomani123:
How is the camera performance on the snapshot?
[Mi 3 Original Android Development] titogrima:
Search in google "Repartition_MI3W_1_2GB". The first result link to xda thread
[Mi 3 Original Android Development] TofikLupus:
That's for extending a partition, he wanted to merge the original 2 partitions into one.

MI3W 64GB/Tapatalk