yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Accessories] dwswager:
Don't get me wrong, any cable should be designed to USB specifications. But so should the devices! The Fundamental problem is 5V/3A. Google apparently designed the phone around the connector spec instead of the USB 2.0 specification. 3A is the design requirement in USB Type C spec for what a standard cable must be able to handle, not a USB power specification. Look around and count the number of 5V/3A USB devices you find. I can only think of one...a specific Asus Transformer model that came with a captive 5V/3A charger with a Micro USB connector and warning labels not to plug it into any other USB devices. Even so, the Transformer did port detection so it wouldn't try to over draw from compliant source ports.

The BC1.2 (Battery Charging Spec) outlines three distinct types of USB port and two key monikers. A "charging" port is one that delivers currents higher than 500mA. A "downstream" port signals data as per USB 2.0. The BC1.2 specification also establishes both how each port should appear to the end device, and the protocol to identify what type of port is implemented. The three USB BC1.2 port types are SDP, DCP, and CDP:

1.	Standard Downstream Port (SDP) This port features 15kΩ pulldown resistors on both the D+ and D- lines. The current limits are : 2.5mA when suspended, 100mA when connected, and 500mA when connected and configured for higher power.

2.	Dedicated Charging Port (DCP) This port does not support any data transfer, but is capable of supplying charge currents beyond 1.5A. It features a short between the D+ and D- lines. This type of port allows for wall chargers and car chargers with high-charge capability without the need for enumeration.

3. Charging Downstream Port (CDP) This port allows for both high-current charging and data transfer fully compliant with USB 2.0. It features the 15kΩ pulldown resistors necessary for the D+ and D- communication, and also has internal circuitry that is switched in during the charger detection phase. This internal circuitry allows the portable device to distinguish a CDP from other port types.

Bottom line - if this phone is of such poor design that it starts fires, what will the common element of all those fires end up being? The Phone!
[Nexus 6P Accessories] DebauchedSloth:
Actually no. The phone is compliant with the USB-C spec, which allows for considerably more than 3W (See: the Apple Macbook USB-C charger, the Chromebook Pixel USB-C charger and so on.) If you are using a C->C cable, with a compliant C charger, there should be no issue. The issue comes into play with a C->A cable which is not compliant, which causes the phone to think it's got a C connection and thus try to draw more power (3W) than the power supply can put out (effectively, it shorts out the power supply.) This can smoke the power supply. Literally.

Solution: (a) Use only C->C charging (this is your best bet, since it is the fastest) or (b) use a compliant C->A cable with any USB A charger. The phone will then negotiate an appropriate charging rate, either very slow (straight USB) or BC 1.2 (if available) which will still be slower than C->C.

Personally, I'd just stick with C->C and not worry much about the cable, *except* if you are using a C->A cable for data purposes, in which case, choose that cable wisely or risk frying your USB port.
[Nexus 6P Accessories] niv3d:
I personally will be getting this http://goo.gl/CXIaHi to replace my car charger and possibly a second home charger. Along with getting a Type C - C cable from Google to eliminate any cable concerns. If you stick with Type c-c cables for charging you will be more than fine. I don't plan on charging my 6p using a Type A - C cable ever anyways.

Specifications:

Input (Micro): 5V/9V/12V 2A Max

Input (Type-C): 5V/3A Max

USB Output: 5V/ 2.4A

Type-C Output: 5V/3A Max

QC 2.0 Output: 5V/2.4A, 9V/1.5A, 12V/1.2A Max
[Nexus 6P Accessories] uodii:
Yes, because that's what a company like google willingly intends to do. Provide a phone that is capable of burning down houses and cars and entering into massive lawsuits in the process...because that's smart business.

It seems to me that companies are just inaccurately advertising to make a quick buck out the gate. They know that they can seriously capitalize on a situation when newer technology is involved. Doesnt that seem a little more feasible? Most consumers read reviews and only care the cable has proper connectors, a decent length, and doesnt feel thin and cheap. Most consumers dont realize how much more goes into cables as you can tell by 98% of the reviews.

At this point I'm just waiting for Google to get more cables in stock in the Play Store because the price is the just about the same as all these off brand cables and I feel they should work better since they make the damn phone.
[Nexus 6P Accessories] BladeRunner:
I'd be interested in reading his reviews, do you have a link?
[Nexus 6P Accessories] dwswager:
BINGO...and that is the fail! The Type C Spec is not a power spec, it is for the design of the connectors and cables which happen to carry power! You do not design a device around the specification for a 20 cent piece of metal. You design the device around the USB 2.0, 3.0 or 3.1 specification so it is interoperable with connected devices and when you decide to use a Type C connector, that spec also gets added to your design requirements. It does not replace the USB 2.0 specification which includes Battery Charging and USB Power Delivery.

BC1.2 requires comparing D- to Vdat-Ref at detection and then there are over and under voltage compliance allowing the PD to disconnect and renegotiate.

Under USB specifications, using a Type C connector you can deliver up to 100W. The Type C Spec is Item 34 in both the USB 2.0 and 3.0 specs. Point is, you don't get to pick and choose only what you want out of the larger spec and ignore the other applicable parts.

If a plethora of 5V/3A USB Type C products start appearing, then Google will have set a new standard. However, the Z5 and Lumia 950XL, both Type C, both are reported to support QC 2.0 which doesn't have a 3A capability. Even QC 3.0 doesn't support a 3A. It has voltage range from 3.6V to 20V in 200mV increments, but tops out at 2A.
[Nexus 6P Accessories] geoff5093:
Make sure you test the actual current when using this. I have many 5V/2.4A chargers and even the Google official type A to type C cable shows it's only charging normally, not rapid or fast.
[Nexus 6P Accessories] DebauchedSloth:
It does cover power delivery. Look at 4.6.2.1 (USB Type C Current) in the USB-C spec. In particular, look at the specification of the CC pin. Now take a bad cable that is intentionally or unintentionally screwing with the CC pin, probably intentionally so that their cable "rapidly charges", and you can see the problem.

I see your point, they should first negotiate using BC. The spec does explicitly state this is optional, though one presumes that whoever wrote it didn't think people would screw with the cables in quite this way.
[Nexus 6P Accessories] dwertz:
Yeah, them bas%%rds make it sound like it's a 3.1a. I had the link up but false alarm so removed it.
[Nexus 6P Accessories] DebauchedSloth:
Actually, what Google is up to makes perfect sense. The utterly "safe" path would be to never USB-C fast charge, since the operating assumption would be that the CC pin is being misused. In that case, your best bet is to fall back to either BC or QC, one of which is relatively slow and the other is kind of a proprietary hack. You'd also limit your charging current.

In an ideal world, we'd all implement USB-C and have access to lots and lots of potential power in a sane, standards compliant way (which kind of matters here since Apple is already using USB-C and not QC, and they've never implemented BC.)

The only thing really standing in the way of that is a bunch of non-compliant A->C cables, which is likely to be a really short term problem, if word gets out that those cables are *dangerous*.

So you do the right thing, implement USB-C charging and then start publicly calling out the crap cables. Which, ahem, appears to be exactly what they are doing.
[Nexus 6P Accessories] ctbear:
This is his profile on Amazon:

http://www.amazon.com/gp/pdp/profile/A25GROL6KJV3QG/ref=cm_cr_rdp_pdp
[Nexus 6P Accessories] dwswager:
It certainly discusses how to handle power. But in general, it deals with all C-C connections. Legacy is covered in the base 2.0 and 3.0 and BC1.2 as the actual requirements that must be met. The Type C spec is an add on to those specifications, not a replacement.

Does a Type A port have the CC pin? No! So a Type C device cannot negotiate a power contract over the CC with a Type A Upstream Facing Port. It does monitor CC voltage.

The Type C spec says precious little about legacy environments other to discuss behaviors for attachment and unattachment. It does go into gory detail about the electrical specifications for USB Type C to Legacy cables and adapters. That is because power behavior for legacy (which the 6P is backward compatible with) is covered in the USB 2.0 specification. But in USB 2.0, what does the Sink do? It:

1. Draws no more than default USB power (500mA) at startup

2. If it wishes to consume more than default power, it monitors vRd to determine if more current is available.

As a USB 2.0 device, then the 6P should, when faced with any legacy charger, use 500mA as start up and keep monitoring the bus to ensure voltage does not drop below spec as it ramps up power consumption. I believe this why when I first plug in my old phones, they might only show a 400mA draw, but if I look at them a minute later, they might be drawing 1800mA off a 2A charger.
[Nexus 6P Accessories] DebauchedSloth:
Right! And if the A->C cable doesn't screw with the CC pin, the fallback behaviour is correct (either slow charge or BC.) That's a compliant A->C cable. A non-compliant A->C cable is screwing with the CC pin (inadvertently or not, I suspect it's not), and therein lies the problem. There is the whole problem.

---------- Post added at 01:52 PM ---------- Previous post was at 01:37 PM ----------

It does this thing, as far as I can see. It detects a legacy charger (or port) by looking at the CC pin, which is correct, and controlling charge current per the chunk of spec I referenced above. A non-compliant cable (which incorrectly handles the CC pin) makes it impossible for the device to detect a legacy charger, since the cable is saying "Type C, full current available". That leaves Google with a choice: limit the current so as to never overload a potential legacy charger (i.e., assume the CC pin is forever non-functional, basically, and just fall back to legacy charging *always*) -or- believe the CC pin and take advantage of the higher current available with a C compliant charger and try to smoke out the bad cables.

They chose to believe the CC pin and smoke out the bad cables. I think that is correct.
[Nexus 6P Accessories] dwswager:
It won't smoke the cable, the cable will be just fine, if the 6P draws more current than the facing port is able to deliver it will burn the facing port (wall charger, hub, laptop, etc.) But what I am saying is that the 6P won't do that. It will monitor vRd and notice a voltage drop across the bus and will limit the draw.

The one real concern would be if it thinks it has a 3A source and immediately tries to draw 3A at startup. Most sources will have overcurrent protection and stop it, or the phone will stop it due to under voltage, but it might not react fast enough to save the source circuit. I would think legacy 2.0 computer ports would be most vulnerable to this. However, I wouldn't care if I had triple confirmation before hand, I would design the circuit to start at 500mA and draw up to my desired power. There just is no charging scenario where 3A startup is necessary. Cause in the end, if my device is burning laptop ports around the world, I'll take the beating not the cable guy that disappeared long ago.
[Nexus 6P Accessories] DebauchedSloth:
Yeah, my bad. I was saying google needs to smoke them out (i.e., call them out, make it known they are bad, etc.) Not that the cables would smoke. :)

They appear to do this. Not sure if that's in the spec or not, but they do appear to slow start and ramp up.
[Nexus 6P Accessories] ac16313:
QC 2.0 doesn't charge at 3A because it charges at 9V/2A~18W. The 6p will charge at 5V/3A~15W. Amps are not the only part of the equation voltage plays a role in determining power. Also why do people keep saying the Z5 has USB c it does not.
[Nexus 6P Accessories] dwswager:
Yes, but the battery never sees these voltages. Just used to push current from the charger. QC also uses 12V/1.5A. QC 3.0 will go up to 20V in 200mV increments. And yeah, that was my mistake. Sony had originally indicated USB Type C but pulled back. The OnePlus 2 uses it though.
[Nexus 6P Accessories] ac16313:
They have MANY and I mean many different voltages that it can run on. The equation for power is P=I•V where P is measured in watts the higher the voltage the lower the amps have to be to deliver the same or more power. 12V/1.5A will deliver 18W give or take obviously due to resistance and what not. So more watts faster charging, in theory. Plus then the phone will only draw what it wants so there's that too. Yeah I haven't looked at QC 3.0 tbh only looked up 2.0 because there was talk of it being supported so I was curious.
[General Questions and Answers] tolgahan33:
Darthstalker 928t variant note5 rom compatible with 928c model? if not i need some help about finding out correct and stable rom for my model.
[X Style (Pure) General] lazerus06:
I had a Sprint LG G4 that died on me (known defect with the Sprint variant of the LG G4). Since Best Buy couldn't get anymore, they sent me a $650 gift card to cover the full value of the G4.

I initially ordered the 32 Gig Moto X Pure in White and instantly loved it. Best Buy didn't have any in the stores at the time so I bought it without seeing it first. Two days ago, my local BB got some of the 16 gig versions in black. I loved the black so much more than the white I exchanged it ( I have a 64 gig SD card so once Marshmellow hits, storage won't be an issue).

It is an amazing phone. Only two things I slightly miss from my G4 are:

a) Picture quality. In well lit outdoor situations, not much difference. In low lit situations, the LG G4 can't be beat. Not a deal breaker with the Moto X but there is a difference.

b) Battery life - The LG G4 seemed to have better battery life for me. The Moto X quick charge out of the box however more than makes up for it.

Things that I love more than the G4:

a) Build quality - It seems like a much more solid build over the G4. Maybe the removable back on the G4 was a reason.

b) Software - Of course the closer to stock, the closer to heaven. So much snappier than the LG skin that they put on top of android

c) Speakers - No brainer, way better sounding front speakers

Overall, I consider this and upgrade from the G4 (for me). Love this phone so far.
[X Style (Pure) General] smokarz:
Hey, thanks for sharing your experience OP.

Have you run into any issues with space yet on the 16GB version?
[X Style (Pure) General] lazerus06:
Not really. I have to sort of baby it a little though(transfer apps to SD, set camera to store pictures on SD, etc...) I am not a big mobile gamer so I only have a couple of games.

I think if the feature that allows you to integrate your SD card storage with the internal storage wasn't going to happen in 6.0, I would have gone with the 32 gig.
[X Style (Pure) General] DrearierJester1:
As soon as M arrives officially, make sure to use a UHS-II rated card to avoid app lag issues. :)
[X Style (Pure) General] slicetwo:
I'm actually debating between the G4 and the MXP. Would you say the MXP is the way to go?
[X Style (Pure) General] lewwill:
I've had the MXPE over a month now and I am completely happy with it. I've been with moto phones since the Droid X and this is the best. I can't really find any faults wilth it.
[X Style (Pure) General] lazerus06:
Moto X. After using pretty much stock Android, I could never go back
[X Style (Pure) General] smokarz:
Can you set the camera to automatically save photos to the SD card?

Or do you have to manually move them to the SD cards after you take the photos?
[X Style (Pure) General] Oaklands:
You can set it to save to SD.
[X Style (Pure) General] benjamminh:
That's funny because I've had the MXPE for for eight weeks and just got the LG G4 for my wife to replace her note 3. I got it free from Verizon without using an upgrade so I couldn't pass it up. Haven't played with it much but don't care for LG UI.
[X Style (Pure) General] banshee28:
So, I originally had the same opinion on the battery and similar results. I then upgraded to a custom ROM (TruPureX), and its a full night and day difference. I can now go 2 days+ without charging with very light usage. Stock ROM would only do about 1 day with the same usage. There are probably a few reasons why, but I am much happier now with the phone knowing there are ways to help the battery last longer! :D
[X Style (Pure) General] Notstewie:
Good choice.
[X Style (Pure) General] tolymatev:
What about Note 4 to the Motorola?

Will that be an upgrade? I dont know if i should pull the trigger or not?

Thanks
[X Style (Pure) General] mademan420:
For me, the biggest difference is the overall improvement in smoothness coming over to the MXPE. Using any Samsung device for a couple of months, you will start to notice it slowing down while transitioning between the most basic task. This is what I hated the most about the Note 4. I never used the s pen, but loved the screen and cam. I was pleasantly surprised how nice the screen looked on the MXPE, even compared to the Note 4. Also the cam on the MXPE has great potential for taking pics, I'm just not a huge fan of the stock cam app. Hopefully this will get addressed in a software update. The last thing about the Note 4(Samsung in general) is how long it takes them to push out updates. From what I've been reading, the MPXE is already in the soak testing stage, so it will more than likely go live b4 the end of Nov. Hope this helps:good:
[X Style (Pure) General] lazerus06:
Personal preference really. After having a phone that runs almost pure stock Android, I could never go back to a Touchwiz based phone.
[X Style (Pure) General] scarboy6693:
I made the same switch but from an ATT Version. Other than the Camera, I love the Moto more in every way. Near-Stock android and no bloat just makes the phone feel a lot less cluttered and smooth. I didn't like LG's quick settings in the notification menu either because they felt like they took up more room than needed. Battery life with the same apps and all has been a lot better for me on the moto as well.
[X Style (Pure) General] Slash8915:
How would you compare the screen of the Moto X to the G4?
[X Style (Pure) General] krking20:
I have a LG G4 H811 and I am having a very hard time getting T-Mobile to unlock it. I like the G4, but I may have to sell it and get a unlocked phone. Moto X Pure may be my best option. I too am curious how the screen compares as well.
[X Style (Pure) General] Slys13:
Coming form a g4 ,I do miss the cam ...that's about it..went to a custom rom(purex) and batt has been great....I love the pure Android.. The ui would lag with the g4...I would say hands down pure is a better phone ....
[X Style (Pure) General] joshuadjohnson22:
For what it is worth I came from the G4, I like the G4 screen much better. Deeper blacks, more vivid colors. The moto x is much brighter and is pretty much all screen. The blacks are more of dark gray and not real blacks IMO. But I prefer the moto X over the G4 in just about every other department. The camera of the G4 is better. MXPE is smooth and pure android just works.

I did make the move to the nexus but the pure is a great phone. Just pray you never need warranty replacement. I'm jumping through their stupid hoops now trying to get a replacement. So far it has been 7 days since they put a hold on my CC for the replacement. What a joke... Spent all this time on the phone for them to tell me that they are closed and I have to call again tomorrow...
[X Style (Pure) General] NOSTALGIA:
good thing i never got a note 4...
[X Style (Pure) General] bigmatt503:
Does the verizon version still have the touch screen issues (miss taps and not registering touches)? I had the g4 and sold it and bought a Nexus 6 ..just curious if an update fixed it or not.
[X Style (Pure) General] benjamminh:
So far no touch issues.
[Android Q&A, Help & Troubleshooting] ShinDragon44:
Hello everyone,

I don't know if this is the right section to ask this, so excuse me if i've chosen a wrong one. (And sorry for my bad english, i'm italian)

I'm a bit confused about audio mods. I've seen a lot of threads about, for example, Dolby digital mod, dolby atmos mod or Maxx audio mod.

I would like to ask some advice to choose the best one (I listen to the music mainly in earphones)

P.S: My device is Xiaomi Mi 4c, with CM 12.1 Unofficial

Thanks!
[Android Q&A, Help & Troubleshooting] Orcam:
Hi there, welcome to the forums fellow Italian. Have a search for ViperFx for android. You will be satisfied I think.
[Networking] gladman:
Anyone here with a softbank x01ht (tytn) successfully connect to fido's gprs network?

I've tried everything here and around and cannot connect.

wifi works...just no 3g.
[Networking] jinner:
mine is working

I used the settings described in this post.

However, in that same thread, some guy says that some Softbanks that aren't properly unlocked don't let you change some settings. I don't know about that. But I can change my settings.

lol...durh...here's the link

http://www.howardforums.com/showthread.php?t=1153801
[Nexus 6P Accessories] fury683:
OP/mods can this thread be closed/deleted? Looks like a dupe here: http://xdaforums.com/nexus-6p/accessories/jumping-off-3a-bus-t3241826
[G3 Q&A, Help & Troubleshooting] StonebridgeGr:
Hello, i have LG G3 S mini with lollipop 5.0.2, i want to install kitkat, how i can do this? is there any kdz file to install? Thanks
[G3 Q&A, Help & Troubleshooting] redduc900:
Check the Firmware Files links in the OP of this thread for a KK KDZ specific to your phones model...

[Guide] LG G3 Stock Firmware (Go Back to Stock) KDZ & TOT Method

http://xdaforums.com/showthread.php?t=2785089
[G3 Q&A, Help & Troubleshooting] StonebridgeGr:
i cant find something about my phone d722 lg g3 mini
[G3 Q&A, Help & Troubleshooting] redduc900:
Check out this thread...

LG G3s,Beat,... [D722,...] General Thread

http://xdaforums.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048
[G3 Q&A, Help & Troubleshooting] StonebridgeGr:
in this post doesnt say about kitkat for lg d722,is only for lollipop and cm
[G3 Q&A, Help & Troubleshooting] camilo_j18:
Hello friends I have a problem with my LG LS885 force g3 , you install a different ROM model and I am full brick

It does not turn on

not led

not recovey

so no download

but found a file filtering lg that it might help me but I need a backup of the same model, who could provide me a backup? I would appreciate it beforehand
[G3 Q&A, Help & Troubleshooting] Droidriven:
Hello,

Welcome to XDA.

To better assist you, your thread will be moved to your device Q&A forum. The experts there may be able to help. Good luck.
[Sprint HTC One (M8)] primebeatz:
I have a Sprint M8. S On. Flashed a custom rom. I need to go back to stock unrooted. the utility failed because I had the wrong firmware or something. What do I do?
[Sprint HTC One (M8)] weidnerj:
I would just run the RUU against your phone. You can download it from http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.18_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_446215_signed_2.exe
[Sprint HTC One (M8)] Magnum_Enforcer:
Being S-on you'll need to run a RUU with a software version newer than what you currently have installed on your device.
[Sprint HTC One (M8)] primebeatz:
The ruu you sent didnt work. Error 155.
[Sprint HTC One (M8)] primebeatz:
I got the same error as before
[Sprint HTC One (M8)] primebeatz:
Well..it seems I need to lock the bootloader. How do I do that?