PSA: Do Not use GoPro USC-PC Supercharger [Model AWALC-002] - Pixel C General

According to Nathan K.'s recent analysis post, I thought I'd pass along the PSA, which could potentially damage your Pixel C and or any other USB C device.
Urgent PSA: DO NOT use the +GoPro #USB #TypeC USB-PD Supercharger [Model AWALC-002] with any third-party equipment -- ESPECIALLY not the Google Pixel C tablet! The GoPro charger may be IS unsafe and could cause immediate hardware damage!
Please refer to his post here https://plus.google.com/102612254593917101378/posts/eKMuTSuqTre for more up to date details.

Related

Future Desktop Mode?

Connecting some dots here. This is pure speculation and it might sound crazy but hear me out.
It has been rumored for a while that Google is adding a dockable desktop mode in Android, maybe similar to the WebTop OS in some Motorola Phones. There have been patents filed and reports claiming that it would release in Jelly Bean. That obviously didn't happen but maybe it is coming in 5.0 (Key Lime Pie?)
Samsung changed the MHL connector from a 5-pin configuration to 11-pin on the Galaxy S3. People were upset because their old MHL adapters would no longer work. Why did they change it? Changing to the 11-pin configuration allows USB Host support (OTG) with HDMI support simultaneously. I have yet to find a connector with both HDMI and USB ports so I'm assuming they are saving this functionality for down the road.
With a desktop mode, more RAM will obviously be needed with increased multitasking. Samsung reportedly upped our S3's to 2GB ram to make it more "future proof" for potential Jelly Bean hardware requirements, which ended up not being even close to required. Perhaps they were thinking that Jelly Bean would bring a desktop mode, but it was saved for a future Android release? Or perhaps they are planning on implementing some sort of Ubuntu for Android functionality?
Thoughts?
Hmm any bored people with experience want to try splicing a 11 pin MHL cord into a OTG and 5 pin MHL? Thinking about it now.. I don't see why it wouldn't be possible unless software is limiting it.. *And at that point is where I guess the devs come in*
This is excellent I just recieved my S3 MHL 11-pin connector, now to try it out tonight with OTG.
Hi danben7, does your mhl cable support simultaneous hdmi and usb-otg? I just ordered the Motorola Lapdock and was hoping to rig a set of cables to enable to use my S3 as a mini-laptop thru the Lapdock.
icarus78 said:
Hi danben7, does your mhl cable support simultaneous hdmi and usb-otg? I just ordered the Motorola Lapdock and was hoping to rig a set of cables to enable to use my S3 as a mini-laptop thru the Lapdock.
Click to expand...
Click to collapse
Nope, unfortuanetely it's not possible. MHL to HDMI needs the charger to be plugged in to the extra port.
Unless in the future samsung release a new MHL connector with OTG together, i don't see it happening. Honestly I don't know why they changed to an 11pin connector.
I totally see this happen for several reasons.
It will be the perfect competitive to Win8
Key Lime pie could suggest a big change since L follows K in the alphabet
At the IO they said the chose ASUS because the like what the do with the transformer series
The new Chrome OS version (v19 and newer) looks like the tablet mode of ICS.
Just add on-screen buttons next to the running apps and enable Widgets
Onskreen and Wind River show that Android can easily support a multi-window mode
Ubuntu on Android looks very promising
The 5 Nexus devices rumor suggest a Key Lime Pie launch before christmas
The 5 Nexus devices will include a ASUS device (I think) -> a ASUS device that is no 7incher will
be a perfect fit for a desktop mode
At least a slow joining between Android and Chrome OS is confirmed by leading Chrome OS developers
I think JB is just a antedated part of the planned yearly release cycle, to compete with Amazone and to
push Android Tablets
Sorry for not providing Links

KAYANG vs. MYUNGBO vs. LEEVIN vs. HONGUIN - Are they OEM SAMSUNG ?

KAYANG vs. MYUNGBO vs. LEEVIN vs. HONGUIN - Are they OEM SAMSUNG ?
In terms of the cable KAYANG vs. MYUNGBO etc... that MYUNGBO is infact an OEM SAMSUNG product,
Purchase a S3 from WindMobile or Rogers and take a look at the cable, yes, that is correct.. it is MYUNGBO
WHY? Samsung Electronics outsources various manufactures to produce their products and the following is a brief outline of the cable based on the country of origin
Samsung ECB-DU4AWC White Micro USB Cable often paired with the ETA-U90JWE
Leevin= UK/ USA
Myungbo= CDN/ Vietnam/ USA- some carriers in US depending on model
Kayang= Japan/ Korea/ USA- some carriers in US depending on model
Honguin- China/ Africa
All of these above cables are OEM Samsung and counterfeits typically do not have the logo printed on the cable itself, in terms of the adapter, yes the one with the chinese writing is fake, but the information in respects to the cable is incorrect.
In terms of what the little writing means on the cable, here is a breakdown and this information was found in Gregg l. Des Elms review (ctrl+F to myungbo) on amazon.com
If you carefully examine the length of the cables, you'll find some lettering on them. Somewhere in said lettering might be an amperage rating... which would be perfect, and would settle all bets.
Sadly, it's usually never quite that easy; and that's because what's written on most USB data and/or charging cables is no easy thing to decipher.
For example, on the charging cable that comes with the US version of the Samsung Galaxy SIII phone, we find:
US ECB-DU5ABE MADE IN CHINA, RT1C510ASE, E232407, AWM 21445 80C 30V VW-1 MYUNGBO KP NT NON-PVC
For starters, these cryptic numbers tells us that it's a US version cable; Samsung part number ECB-DU5ABE; made in China; using Myungbo-branded non-PVC insulation which subscribes to its E232407 plastics standard, and which further subscribes to the US Underwriters Laboratories (UL) safety standard as found on page 21445 of its Appliance Wiring Materials (AWM) guide.
Page 21445 of the UL AWM guide covers what's called the "UL 758 Standard for Safety of Appliance Wiring Materials", which covers a *WIDE* variety of appliance cables of varying voltage- and amperage-handling capabilities; however, generally speaking, the UL 758 standard covers 20 amps or less.
Well, of course, that doesn't really help us, 'cause I'm here ta' tell ya' that there isn't a USB data/charging cable on earth that'll handle 20 amps; and so we're talking, obviously, something somewhat less, here...
...but *WHAT* less? How much less? Oy. How to figure this stuff out... especially 'cause most of these cable makers won't actually specify the amps. The best they'll tend to do for us is show how many volts of which the cable's capable. Oh, sure, if that's all that's shown, then you can sit down with an Ohm's Law calcuator and figure it out... but, c'mon, who wants to do THAT in life, right?
Fortunately, I know the answer, and here's what I can tell you that'll help... it just kinda' cuts to the chase and makes all the other numbers irrelevant: any AWM-class cable which subscribes to what's on page 21445 of the UL 758 guide (and most newer USB charging and/or data cables are that; though there are a couple other AWM standards to which older cables subscribe which must be avoided) which is capable of handling 30 volts (as indicated by the "30 V" on the aforementioned SIII cable), and which can heat-up to 80 degrees Centigrade (which is around 175 degrees Fahrenheit) before it degrades or melts or smokes (which is what the "80C" on aforementioned SIII cable means) can easily handle 2.1 amps... a bit more, in fact.
So, then, that's really what you're looking for on these cables: something at or above "30 V" or "30V", and "80 C" or "80C"; along, of course, with the number "21445;" with or without the sometimes-added "VW-1". As long as you see that on the cable, then it's likely that said cable is capable of handling 2.1 amps...[/SIZE]

Pixel C will support USB 3.1 host and client modes over the Type-C connector!

Source: https://www.reddit.com/r/IAmA/comme...le_and_im_with_the_team/cxt6a65?context=10000
From Benson Leung (the USB type C Amazon reviewer / Google employee)
1) Type-C!
2) USB 3.1 Host & Client mode
3) USB PD (Power Delivery spec[1] ) fast charging for 24W
4) USB Debug Accessory mode.
KT: Tablets are all about the display.
Pixel C has a very high-resolution 2560x1800 display with 308 PPI.
It's also brighter than other tablets at 500 nits.
Pixel C is also the first Android tablet that ships with Marshmallow and will receive updates directly from Google
Click to expand...
Click to collapse
I am suddenly happy I bought type C cables that support 3.1.
i don't understand this : Pixel C is also the first Android tablet that ships with Marshmallow and will receive updates directly from Google
Nexus are not updated directly from Google ?
thanks
ragnar56 said:
Nexus are not updated directly from Google ?
thanks
Click to expand...
Click to collapse
Nexus 9 for example is build by HTC and was designed by Google and HTC together. Pixel C is google-only. I think that is what they are trying to say.
No, its two separate statements.
1. First tablet with marshmallow
AND
2. Will receive updates directly from Google.
Sent from my Pixel C using Tapatalk

Bounty 100 EUR - Displayport Alt Mode - Enable USB C to HDMI

Hello devs,
Please look into enabling the displayport alt mode!!!
Its really frustrating how this phone cuts quality (480p) when used with a 4K TV. The only way is usb to hdmi cable, but sony decided to disable this feature.
Can you please make a tutorial on how to enable this?
Bounty 100 EUR
Up
I have found this intresting information:
https://patchwork.kernel.org/patch/9195059/
It should be that easy as adding some lines of code?
Another intresting video:
https://www.ifixit.com/Guide/Sony+Xperia+XZ+Premium+USB+Port+Replacement/97361
From this video we know thatXZ premium has all the USB type c 3.1 pins connected to the motherboard and therefor to snapdragon 835 (5:07 in the video)
Also take a look at this:
https://cdn.arstechnica.net/wp-content/uploads/2015/01/type-c-pinout.png
Seems like the tx pins are responsible for Displayport alt mode
The good news is that they are soldered into the motherboard connector
Is it possible that the data pins have been disabled in kernel?
I look forward to this thing happening! (Although I'm waiting for a DRM backup method first)
as I said on the other thread, don't hold your breath, pins on a socket and PCB mean diddly squat.
Sony may very well disabled this or not even included supporting chips. I would strongly suggest if anyone wants to confirm this to find the same chipset on a different device with a working video out, then take a super high resolution photo of both sides of the PCB paying special attention to the numbers on the chips, then someone else do the same with the XZp
we will never be about to check the traces since it will be amulti layer PCB and we wont be able to check if any traces have been severed from a photo. but we will know if there are some supporting chips missing.
I disagree with you. Today chips are not just chips, are SOC.
Hardware is there. This tx prins are active for usb audio also, but not for video data transfer.
Sony hasn't implemented snapdragon 835 low cost version, because it does not exist. There are no other chips related to display port alt mode. It is done in Sd835. Simple as that.
Inerent said:
I disagree with you. Today chips are not just chips, are SOC.
Hardware is there. This tx prins are active for usb audio also, but not for video data transfer.
Sony hasn't implemented snapdragon 835 low cost version, because it does not exist. There are no other chips related to display port alt mode. It is done in Sd835. Simple as that.
Click to expand...
Click to collapse
SoC have been used for a long time mate, trust me, if Sony didn't want something there are dozens of things they can do to stop it. Its been a problem with SoC vendors for decades. a physical connection means nothing if its traces are cut
Of course its perfectly possible its just software limited but its equally possible its not physically possible. The proof will of course be if you can get it working... but They have been doing this for years now and are getting pretty good at it.
dazza9075 said:
SoC have been used for a long time mate, trust me, if Sony didn't want something there are dozens of things they can do to stop it. Its been a problem with SoC vendors for decades. a physical connection means nothing if its traces are cut
Of course its perfectly possible its just software limited but its equally possible its not physically possible. The proof will of course be if you can get it working... but They have been doing this for years now and are getting pretty good at it.
Click to expand...
Click to collapse
If you are so confident, then find out for your self, I would say.
You want me to prove that its broken or working? firstly I have no intention of putting any effort in to getting this to work, my device is perma locked and I really cant be arsed taking it apart and try to write over the ROM just to attempt to get this working.
Which leaves me with trying to prove its broken. as Ive said, multi layer PCBs will be impossible to check this without taking the device apart hell, ANY PCB will be impossible to check without checking each trace and that's not to say if QC hasn't used any fuses to blow certain circuits within the chips. If you get it working, then you will have your proof. all I'm saying is don't be surprised If it doesn't happen. it wont be the first time a manufacture has done this.
dazza9075 said:
You want me to prove that its broken or working? firstly I have no intention of putting any effort in to getting this to work, my device is perma locked and I really cant be arsed taking it apart and try to write over the ROM just to attempt to get this working.
Which leaves me with trying to prove its broken. as Ive said, multi layer PCBs will be impossible to check this without taking the device apart hell, ANY PCB will be impossible to check without checking each trace and that's not to say if QC hasn't used any fuses to blow certain circuits within the chips. If you get it working, then you will have your proof. all I'm saying is don't be surprised If it doesn't happen. it wont be the first time a manufacture has done this.
Click to expand...
Click to collapse
Nobody will be surprised, don't worry. Just that we don't know doesn't mean that we shouldn't try.
Trust me, displayport alt mode is disabled in kernel.
Tx pins are active for usb audio playback!
It seems the display link hardware is our only choice for the moment...
https://forum.xda-developers.com/oneplus-5/accessories/usb-c-to-hdmi-adapter-t3631169/page8
Inerent said:
Trust me, displayport alt mode is disabled in kernel.
Tx pins are active for usb audio playback!
Click to expand...
Click to collapse
Sorry bud, that doesn't mean anything more than USB Audio is connected...
Check this out! https://youtu.be/Ff9GfDpH42Q
Maybe some devs look into the buildprop and kernel of the s8 to search for relevant data and compare them with our xzp...
P. S. another proof that makes me think that this sh...t is disabled in software is that with the displaylink apk the one plus 5, xiaomi mi6, etc are working. The data is sent by Displaylink app to those TX usb pins and works!
So with an app it can be sent, but with our sony software not? C'mon!!! This is BS!
Inerent said:
Check this out! https://youtu.be/Ff9GfDpH42Q
Maybe some devs look into the buildprop and kernel of the s8 to search for relevant data and compare them with our xzp...
P. S. another proof that makes me think that this sh...t is disabled in software is that with the displaylink apk the one plus 5, xiaomi mi6, etc are working. The data is sent by Displaylink app to those TX usb pins and works!
So with an app it can be sent, but with our sony software not? C'mon!!! This is BS!
Click to expand...
Click to collapse
your saying that the Displaylink APK works on the Sony Xperia XZp and on the Sony XZp, data is sent to the correct PINs on the USB-C out but it doesn't display anything? on a linked display?
Need help from rooted devices.
Please add or search in buildprop for ro.hdmi.enable=true
If it's present like this #ro.hdmi.enable=true, just delete the #
If it's not present, just add this line ro.hdmi.enable=true
Save and test only with usb-c 3.1 to hdmi and display port alt mode compatibile cable!
Let me know
Inerent said:
Need help from rooted devices.
Please add or search in buildprop for ro.hdmi.enable=true
If it's present like this #ro.hdmi.enable=true, just delete the #
If it's not present, just add this line ro.hdmi.enable=true
Save and test only with usb-c 3.1 to hdmi and display port alt mode compatibile cable!
Let me know
Click to expand...
Click to collapse
yours not root-able?
Hi Dazza! Yes mine is not rooted ... yet! Enabling Display port is the final step towards rooting my phone.
For devs: BoardConfig.mk and BOARD_KERNEL_CMDLINE
Inerent said:
Need help from rooted devices.
Please add or search in buildprop for ro.hdmi.enable=true
If it's present like this #ro.hdmi.enable=true, just delete the #
If it's not present, just add this line ro.hdmi.enable=true
Save and test only with usb-c 3.1 to hdmi and display port alt mode compatibile cable!
Let me know
Click to expand...
Click to collapse
I already tested but it didn't work.

Picking up z4 from vzw today. Will test usb c to hdmi hub adapter as well as otg

Going to pick my z4 up from the vzw store today. Will test my usb c to hdmi hub adapter. Worked for my galaxy note. To bypass using dex so i could plug my phone mouse and keyboard to any hdmi tv. Got online for $11 worked great. Going to see if the z4 works for this and test out its otg capabilities today. Will let yall know
Also going to look into getting root. After i contact moto to see if we can get device on there bootloader unlock list
No go on the usb c to hdmi hub. Detects charging. But does not extend the display to the hdmi device. Tested on one of my tvs . Will test on my samsung smart but i doubt that makes a difference.
Regarding the bootloader unlock, are you saying it's possible that the VZ branded Z4 may be eligible through Moto's portal? I tried it and, as predicted, it failed. I just assumed all VZ phones are locked down.
I don't think any support MHL anymore as Miracast and Googlecast replaced it. Tried OTG and no worky. But, please prove me wrong.
Any luck on unlocking the bootloader? I've never had a Verizon phone but I came across this z4 practically brand new for a 100 bucks so I picked it up. If I knew that u couldn't unlock the bootloader I would have passed.
No dice on the bootloader. I emailed moto have heard nothing. No mhl no ucb c hub to hdmi . Its unfortunite i love this phone aside from that. Maybe if we bug the heck out of moto they will add it to there bootloader unlock. It worked for older vzw moto z devices. In other news I went to vzw paid $200 for the projector mod. A little disappointed. Not bright enough. At close distance maybe max of 40" its pretty decent. Only on a white surface with lights off.
detects charging, but doesn't actually charge
At least that's what the usb-c "charging bridge" I tried did. I am very disappointed, I can use the OTG keyboard and mouse through the usb-c adapter, the charge indicator came on... but no charge.. The battery ran down.
Is this what you found? I only tried one adapter.
I also discovered the moto Z4 is the only Android I've ever found a wired Xbox compatible controller to not work on OTG, the device shows up as a usb device but isn't recognized as a controller on this phone. ???
silver03wrx said:
No go on the usb c to hdmi hub. Detects charging. But does not extend the display to the hdmi device. Tested on one of my tvs . Will test on my samsung smart but i doubt that makes a difference.
Click to expand...
Click to collapse
This may not be the place but I haven't seen a debloat thread specific to the z4. I ordered one today after the sammy a50 didn't support 1x or 3g. I've only owned a droid x, s3, and s5 cid15. All rooted and with custom roms. But I'm afraid no root or unlocked bootloader for the z4.
Even so, I know you can uninstall or disable apps for the current user on the device through adb. Have you guys done any debloating of the verizon crap thats installed on the z4 from vzw?
I'm sure it can be done with adb but I'm not sure how effective it is.. My understanding is that the user you uninstall the apps for will no longer load or run for that user.
One other question is can this device be themed with andromeda since it's fairly close to aosp from what I've read. If not can it be themed at all. Thanks all for your assistance.

Categories

Resources