yashsingh1/xdaforums huggingface dataset:
[Mi 3 General] aslike2:
2nd version delayed because Ivan found the cause of lag. But he is busy this weekend so he will fix it next week and then release the new version.
[Mi 3 General] orenzai:
Meaning it wont be released this sunday?
[Mi 3 General] gary138.138:
Bad news!

Ivan decided to postpone the release date of new M build for 1 week.

He will tweak the kernel to solve the laggy problem.

估计还要等一周，发现不流畅的问题是什么导致的了。周末没空搞，还要等下周把流畅性修复一下。。估摸着要整一下内核！！
[Mi 3 General] ajnexus5:
Thank you :D
[Mi 3 General] ajitkatte:
New build(5.11.17) released by Ivan - http://www.miui.com/thread-3129345-1-1.html

Here is the GDrive link - https://drive.google.com/file/d/0ByaT1kNEpeRZMV9UMWRoa0M4TGM/view?usp=sharing
[Mi 3 General] Abhi142:
Link share

Can anyone upload ROM on Google drive? Couldn't download ROM from baidu
[Mi 3 General] ajitkatte:
I've uploaded https://drive.google.com/file/d/0ByaT1kNEpeRZMV9UMWRoa0M4TGM/view?usp=sharing
[Mi 3 General] Hsmetric181:
Change log for latest build

1.kernel update fixes camera 2.temperature threshold for limiting heating issue and battery saving

3. Sounds optimize

4. Updated CPU scheduling section, make system more smooth

---------- Post added at 12:57 PM ---------- Previous post was at 12:52 PM ----------

Issues in latest build

Data issue

If data is not working ,turn off the data from switches ,dial a number and hang up ,turn data on again ,it should work now
[Mi 3 General] mipo007:
Other mirrors:

Lolabits: http://lolabits.es/mipo007/Android/....11.16-HB7ZpFMg3h-6.0.0,54404505.zip(archive)

Mega: https://mega.nz/#!AtQgUAYT!XMjDzwrKaMvfqnlDSTYk1FKT6nt1oQHxLsxtmMxkLNk
[Mi 3 General] vineshbalan:
Getting an error while clicking "Mobile Networks" in settings - com.android.phone stopped. Anyone else see this?
[Mi 3 General] sidkackar:
Now-on-Tap not working

Whenever I long press the home button, it shows that SYSTEM UI HAS SHUT DOWN. Please help.
[Mi 3 General] Jay sharma:
Download Banks gapps(300mb) and try
[Mi 3 General] Fyzher:
google play services keeps on crashing every 30 secs lol any idea?
[Mi 3 General] Jay sharma:
Which gapps?
[Mi 3 General] Hsmetric181:
Enable on screen nav button from setting,long press home button

Disable on screen nav button

Now it will not give system ui force close(and now on tap will start working)
[Mi 3 General] Jay sharma:
Works on stock partation?
[Mi 3 General] Hsmetric181:
I use minimal gapps ,without any issue

Method to install gapps is

Install rom in system

Backup rom using twrp/cwm

Restore rom you backed up

Now flash gapps

If this does not work for you,use minimal gapps

---------- Post added at 05:19 PM ---------- Previous post was at 05:18 PM ----------

There is no relation with partition used in this problem,so yes it should work on stock partition
[Mi 3 General] Jay sharma:
Getting an error while clicking "Mobile Networks" in settings - com.android.phone stopped
[Mi 3 General] vineshbalan:
Same here.!
[Mi 3 General] sajokj:
Mobile Networks in settings not working. it force closes and not showing any network.
[Mi 3 General] Hsmetric181:
Working fine for me
[Mi 3 General] Jay sharma:
which gaaps are u using?? Link?? Also what was your flashing procedure
[Mi 3 General] sajokj:
I dont think its a Gapps issue
[Mi 3 General] Me_Ashish_:
How is the performance in the new update. If again the CPU frequency in balanced mode is na at 1.19 GHz, it should suck
[Mi 3 General] rreynaldo:
This problem is with permissions, go to settings/applications/ and search google play services/properties/ permissions and check all permissions. for all google app check too.
[Mi 3 General] Jay sharma:
getting fc at settings-Mobile network :(
[Mi 3 General] ashwathravee:
It's... weird. In some places it's noticeably smoother than Lollipop, but when I start doing something that involves long lists like scrolling through Whatsapp contacts or my Reddit app, it stutters really badly and seems to get hot.

Then again, Lollipop with the default kernel wasn't buttery smooth either for me. I had to use a different kernel to get smooth performance.

edit: In Performance mode, it's very smooth at a solid 60 fps so I'm guessing it's something to do with the kernel again.
[Mi 3 General] Jay sharma:
rooted?? i was unable to flash supersu as it caused bootloop
[Mi 3 General] Hsmetric181:
Use supersu 2.52 beta zip,it's working perfectly

https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
[Mi 3 General] oyvinja:
Two questions:

1. If I'm running Ivan's lollipop rom (5.5.25), can I then simply flash the marshallow rom (5.11.17) directly over that? (with wiping, of course)

2. Ivan's lollipop rom had its own updater app for any updates Ivan made. Does the marshallow rom also have that? Or will each new update have to be flashed manually from recovery?
[Mi 3 General] ashwathravee:
Yes I'm rooted, but I'm not sure what that has to do with my original comment :)
[Mi 3 General] paul c:
When moving between versions, always clean flash. for me it takes about 30 minutes to rebuild my phone, using Titanium Backup:

do a backup in Recovery, in case you need to return to the previous ROM;

full wipe

install ROM, SU, Gapps

reboot and login

download TiBu & TiBu Pro from Play

restore previous Android ID in TiBu and reboot

Google Settings/Security, deselect "Scan Device for Security Threats"

restore user apps & enjoy

I never bother with restoring system data like sms or wifi access, you shouldn't do so if moving between versions of Android.
[Mi 3 General] userprince:
How to get root access?
[Mi 3 General] ganeshrnet:
I just rolled back to lollipop rom in my mi3w. The battery life is too poor. There is heating issues too. The network is totally inaccessible. Also the ROM is damn slow and gets stuck even in Performance Mode
[Mi 3 General] Fyzher:
Yea it seems i was using wrong gapps now it works fine but cant use mobile data whenever i enter mobile networks it crashes .. And data doesnt seem to work , weird but i can use fb on data , i cant use browser
[Mi 3 General] ashwathravee:
Yeah, I've had a similar experience. Still quite early it seems.
[Mi 3 General] error01671:
Flashed 11-16 version, very smooth and fast, need to do the trick to get mobile data working but it won't bother me that much. Also, please suggest me any recommend kernel compatible with this ROM, thanks.
[Mi 3 General] Jay sharma:
mobile network working in settings??
[Mi 3 General] Hsmetric181:
Working in MI3 ,don't know about mi4
[Mi 3 General] Jay sharma:
Doesnt work for me :( Using mi3w...cleanflash n install still mobile network crashes...also lot of overheating
[Mi 3 General] Fyzher:
even i have mi3 but data doesn't work properly can u get into mobile networks in settings? if so can u explain what exactly you did?
[Mi 3 General] Hsmetric181:
Yup, Can go to cellular network setting without any problem,even data is working for me

Btw, according to developer there is problem in data and mobile,and he even gave a solution for it ,

The solution below is translated from Chinese using google translate

"If you encounter to the data network can not use it, please open data network switches, dial-up once, then turned, and then hang up"
[Mi 3 General] Dharani_V:
If I Click on mobile Networks im getting a FC :/
[Mi 3 General] Jay sharma:
mobile data is working for me..but when i go to setting >mobile network it crashes
[Mi 3 General] spotik:
Titianium backup works fine in this new version?
[Mi 3 General] Jay sharma:
yep
[Nexus 5 Q&A, Help & Troubleshooting] chicohonda91:
Well marshmallow is out but the new camera apk is not. Is that apk going to be only for the new nexus 5x and 6p exclusively?
[Nexus 5 Q&A, Help & Troubleshooting] Srandista:
I don't think so, but it will be probably released after the 5X and 6P will be released.
[Nexus 5 Q&A, Help & Troubleshooting] MCPiston:
Is there same bug as in LP or KK? With "can't connect to camera"?
[MX Player] Yugastar:
My sony xperia z1 was recently updated to 5.1.1,until that it worked fine,but after the update,while dragging the time bar it got struck and the player hangs...
[MX Player] Thirumalai.K:
Kindly upload the logs when you report the bugs.
[General Questions and Answers] dev311k:
Hi XDAs

I always suffer from this strange error ..

I use Google Photo Sync on Only Wifi.

When I take a screenshot and

delete

it,

and get on Wifi -

Then Boom !

Google Photo tries to upload deleted picture . for hours. (Please see screenshot:))

and that picture(s) looks like that. white blank picture.

My Note5 is doing this task for 2 hours.

and it's still try to upload it.

I don't know when it will be end and

I don't know what to do.

I tried to delete thumbnails.. but it didn't help.

Is there Someone help me ?
[Android Q&A, Help & Troubleshooting] Powell730:
If I go with, lets say the OnePlus Type C cord, will I still get the faster data transfer speeds/fast charging as if I were using a straight USB type C cable? It seems as if you use a cable that isn't type C on both ends that you wouldn't be able to take advantage of the faster data transfer speeds. I would assume this also applies to the fast charging but I'm not sure...
[Android Q&A, Help & Troubleshooting] Skitals:
USB data speed will be the same because the Nexus uses USB 2.0 transfer. You won't get fast charging with a type C to type A cable. The type A only has the 4 USB 2.0 pins, whereas fast charging utilizes the power bus of the type-c cable (extra pins). So you will need a type c charger to get full charging speed.
[Android Q&A, Help & Troubleshooting] Powell730:
awesome, thanks for the response!
[Android Q&A, Help & Troubleshooting] cxm0429:
I have been looking for a type C to type C cable, any suggestion?
[Android Q&A, Help & Troubleshooting] Elnrik:
http://xdaforums.com/nexus-6p/general/usb-type-c-vs-usb-3-0-3-1-vs-usb-2-0-t3221676

The best you should get is about 2300-ish mA charging from type A connectors. Chances are you will get less. You will never get 3A from a type A port unless something has gone very wrong. See link for details.

---------- Post added at 11:43 PM ---------- Previous post was at 11:42 PM ----------

This is correct. Good post. Thanks
[Android Q&A, Help & Troubleshooting] NCguy:
Then why is the nexus engineer warning that C to A cables and adapters without the proper resistor will cause the device to attempt to pull 3 amps through the cable and burn up the charger? Seems he is saying pins or no pins it's going to attempt to pull 3 amps.
[Android Q&A, Help & Troubleshooting] Powell730:
Using an OEM Samsung fast charger with this cord:

https://www.amazon.com/dp/B013187HZS/ref=cm_sw_r_other_awd_eJIpwbAMNJ231

I got these results:

View attachment 3534256

Compared to these results with the OEM Nexus 6P charger:

View attachment 3534257
[Android Q&A, Help & Troubleshooting] dwswager:
Almost any definite answer you get is wrong because Google has decline to say what the did and full testing has not been completed There are 2 parts to this equation.

1. What is possible to deliver over an A to C connection

2. What the phone will do

As to the first, yes you can get 3A over A to C. The problem has been that there just are not any 5V/3A A port chargers out there. Companies have been making "over charging' chargers for years. I've been able to get 2.6Amp to the phone over an A to C charger limited by the charger capability.

As for part 2, the first thing the phone does when a cable is attached is to determine what type of facing port it is attached to. In this case, it will be a Dedicated Charging Port (DCP). It will check voltage on pin CC and determine it is not a C port and therefore not able to negotiate a power contract in that manner. Type C specs then require it to draw no more than default power (500mA) for USB 2.0. If the device wants more current, it is obligated to monitor voltage on the bus to determine if more current is available. Hence, the device should never over draw the charger.

On the charger side, it will monitor the current draw and limit itself via a maximum current setpoint beyond which it will shut down. If the PD (Portable Device) is designed appropriately, it won't ever hit that because it is monitoring Voltage and the voltage drop will tell the PD to limit the current it is drawing to maintain vREF.

What is really unknown is what is the exact trigger for the "Charging Rapidly" in the lock screen. I get it under 3A.

Recommendation: Use A to C if you need multiple charger ports to support other devices. Don't get bent around the axle over getting all 3A. Use C-C if you only need one port. And in the future, the whole world will be Type C so your investment will last longer. But don't believe that 3A will be widely used. It is a design requirement in the Type C spec, but not a power standard in the USB spec. For example, the Lumia 950XL and Sony Z5 both are Type C and are reported to use Qualcomm Quick Charge 2.0. which top out at 2A at 5V (though can do 12V/1.5A).

Good Test - Get a Male Type C to Female Micro B adapter. Put it on the end of the Type C to Micro B cable plugged into the Google supplied Charger and see what you get!

[IMG="Micro B Type C cable"]http://www.tripplite.com/shared/product-images/lg/U040006MICRO-FRONT-L.jpg[/IMG]

[IMG="Micro B to Type C Adapter"]http://www.cablestogo.com/product-images/28869/600/28869b.jpg[/IMG]
[Android Q&A, Help & Troubleshooting] xxsashixx:
The Google supplied type c to a cable says charging slowly when plugged into a PC which makes sense since type a should only pull 500ma from the port

The orzly cable that Benson tested shows me it says charging rapidly in that same port..

My other cable that I bought from a local electronics store shows "charging" only.. What does that mean? Is that a good sign that it won't damage up my port/charger/phone?

Thanks ;)

All this is so confusing for first gen adopters to these types of cables haha
[Android Q&A, Help & Troubleshooting] dwswager:
What this tells me 1st and foremost is don't go by what the lock screen says.

A USB 2.0 port on a computer motherboard is only going to output 500mA as you found out. A USB 3.0 port on a motherboard can output up to 900mA.

This is what Benson is saying. The Orzly cable is improperly designed such that it signals to the PD that it is 3A so I suspect that is why the 6P is showing Charging Rapidly.

Best way to test what is going on is to use a multimeter to test the current flow, but that means cutting open the wires or using a special plug with terminals. The next best thing is to use a battery app to see what the app says the draw is. This won't be as accurate and you should allow a minute for the device to come to full draw and the app to update.

Personally, I am almost 2 days on a charge where my previous phone required a late afternoon recharge so I am not all that keyed up over fast charging. It is nice, but as long as my phone is usable, not as big a deal because I recharge every night.
[Android Q&A, Help & Troubleshooting] xxsashixx:
I don't care about fast charging I just want to make sure the cable doesn't damage my phone from overcharging or what not.

Plus all the good cables are either oos or won't ship to Canada and are overly expensive..
[Android Q&A, Help & Troubleshooting] dwswager:
Then no worries. The Google Guy's whole point about the cables was that the phone might try to draw more current than the charger can supply and damage the Upstream Facing Port (read that as the charger). But any decent charger has overcurrent protection so neither the phone, nor the charger are in any danger.
[Android Q&A, Help & Troubleshooting] Elnrik:
I have to take exception to this. You keep saying people will be fine, there are protections in place, etc... But I have serious doubts if these protections are meant to be engaged every time a user plugs in. It's like saying it's OK to drive 120mph in a busy 45mph zone, because I'm wearing a seatbelt.

Further, I think you are doing a disservice to the community by posting that it's OK to use products that are clearly out of specification. If pulling more current than a charger could handle wasn't dangerous, they wouldn't be designed with some type of protection measures. As such, saying "neither the phone, nor the charger are in any danger" is patently false.
[Android Q&A, Help & Troubleshooting] dwswager:
Look, I think all devices should be designed in spec and wish the USB Forum would more strictly enforce the specifications. But the 6P is obligated, when it can't negotiate a valid power contract which it can't do with a USB Type A port, to use default power and if it wants more current to monitor the voltage on the bus to determine if more power is available. Hence, if it immediately begins drawing 3A, or it does not reduce current draw when the buss drops below vREF, then the 6P itself is out of spec!

Both sides of the equation, Device and Charger have responsibilities and protections in place. If we were discussing plugging a 10A charger into a 3A device, I would be a little more concerned. But we are discussing plugging a 2A charger into a device capable of using 0-3A.

I also would be a little more concerned if dozens of people weren't already using these cables with less than 3A Type A chargers with no problem. The phones and chargers are doing what they are supposed to do.
[Android Q&A, Help & Troubleshooting] Elnrik:
That it's perhaps the single most disjointed rebuttal I think I've ever read. It also completely deflects from my point that you are giving bad advice and doing the community a disservice... But hey, I'll play along. Let's break down your reply into intelligible pieces to see if there is any sense to be had.

Agreed.

All components using licensed USB technology are obligated to follow specifications.

It can negotiate power with Type-A ports just fine using cables which follow specifications. The port and the phone are not at issue here, no matter how much you want them to be.

It is monitoring voltage, but it cannot know current ratings of the system it is connected to without a marker or sign post, which is where the out of spec cable is defeating this process.

So the 6p is out of spec itself when it is being told, by an out of spec cable, that it is safe to draw 3A?

Conviently forgetting the cable.

Well, that would be safe because the 10A device could safely provide 3A.

Which is unsafe, because MATH. 3 > 2

There is just something fundamentally wrong with this way of thinking. I'd be a little more concerned if we had any damaged property, fires, or deaths, but since we haven't yet, everything must be OK. That's great.
[Android Q&A, Help & Troubleshooting] dwswager:
The USB Type A port has only 4 pins. VDD (+5V), D- (Data-)-, D+ (Data+) and GND (Ground). No way for a Type C device to use the CC channel to negotiate. It knows it is plugged into a legacy facing port.

The PD knows if more power is available or not by monitoring the voltage of the bus. If the PD trys to draw more power than the charger is capable of delivering, then the bus voltage will deviate from reference specs. As long as the charger is capable of supplying the current requested, it will be able to maintain the voltage within reference specifications. This is why the Tronsmart guy says his 2.4A will deliver 2.7A. It has enough margin capacity to maintain proper voltage over it's rated amperage up to about 2.7A.

I love my 6P and think it is the best Android phone on the market. But there are things that could be improved. I would like 2 fingerprint sensors, one back and one front, but if you are only giving me one on a phone this big, it would be better on the front. And 5V/3A was a mistake. It is a cheaper solution to faster charging. What does it say when the 2 port charger from Google is not 30W and they have no 15Watt (5V/3A) car charger available at all.
[Android Q&A, Help & Troubleshooting] Elnrik:
Great for Tronsmart. Not so good for users when they use that cable to transfer data or charge on a laptop, USB hub, or other data centric / non-charger type device and the current ramps up to 3A on a generic USB 2.0, 500mA, Type A port and fries something.

You're arguing that the phone should monitor what it could / should be able to pull from the port. I'm arguing that the USB specs are more complicated that that, which are the specs the phone follows, that the legacy ports and charging protocols follow, and is the current real-life facts of the situtation - not wishful thinking or hypothesizing of what it should or could do.
[Android Q&A, Help & Troubleshooting] dwswager:
When you get a report of a port getting fried, will you please post it here. The more data we have, the better.
[Android Q&A, Help & Troubleshooting] Elnrik:
*sigh* People, don't use non-complaint cables, ok?

A Google engineer has publicly stated in several places that it is not safe and has even posted instructions on how to test for it.

PC Magazine even ran an article on it.

Hell... Common sense should tell you messing around with improper charging currents and voltages isn't safe.
[Android Q&A, Help & Troubleshooting] dwswager:
*Sigh* This reminds me of all the negative Nexus 6P case reviews concerning the Laser Auto Focus by people without the phone or the case. They heard something on the internet and parroted it in review after review. Even the PC Magazine online entry is only a news items that repeats Benson's statements. No reporting of incidents, no comment from any company, including Google.

Has Google made an official statement? If this was such a big issue, does it not behoove Google to warn it's users?

I do not support manufacturers making out of spec equipment, including cables. Only that this is a whole lot of concern without a single verified case of incident.
[Android Q&A, Help & Troubleshooting] NCguy:
This is a valid observation although I think he is vastly underestimating the number of people doing it. Just think about the amount of noise being generated about something as tame as the black color wearing off or the glass cover on the back developing cracks. If these cables were prone to smoke chargers or worse damage units holy hell would be braking loose on the forums if not other media.

I also have to question if google would have released this device if there was substantial risk that something as innocous as using a perfectly fitting, common, USB cable or adapter would fry the charger, phone, and burn down the house while risking the lives of the occupants.
[Android Q&A, Help & Troubleshooting] dwswager:
First, the USB Forum screwed up by not mandating all USB Type C devices and cables be USB 3.0 compliant. Take Type C out of the USB 2.0 realm even though they would be backward compatible to USB 2.0. Oh, and BTW, all charging over 900mA was at one point out of spec. But manufacturers quickly figured out that a device will either default to USB power or adjuticated power by monitoring the voltage on the bus. And so 1.5A, 2.0A, 2.1A and 2.4A dedicated chargers forced the Battery Charging standard be developed and added to the overall USB spec.

My personal theory is that these cable makets did this on purpose to 1) preclude a Type C device from artificially defaulting to USB Default Power and 2) Force the Upsteam and Downstream devices to adjudicate power for themselves. This has 2 implications: one positive and one negative. On the positive side it would allow Type C devices to draw UP TO 3A from legacy connections. This means mixed Type C and Legacy environments can get the power they need from the same devices and allow sharing of, especially, dedicated charging port devices among Type C and Legacy (generally Micro B) portable devices. On the negative side, because Type C devices can get the full power, it will slow the adoption of Type C specific devices and the realization of a full Type C only environment and the functionality and interoperability benefits that will bring. Since I'm guessing at motives, that negative consequence is probably why this Benson has his panties all bunched up. YOMV!