yashsingh1/xdaforums huggingface dataset:
[MTCD  Android Head Units Q&A] CadillacMike:
is this true for all the Android head units? that the Steering wheel controls only work on the default music player, but not on apps like Google Play Music or Pandora?
[MTCD  Android Head Units Q&A] Luxferro:
yes, unless someone modifies the stock behavior somehow - which would likely need source code...

The only global functions, in my experience, are steering wheel volume, mute, and the one the toggles between all the stock apps (radio, music player, video in, ect).
[MTCD  Android Head Units Q&A] tittn:
If i had known that would not have bought the 5.1 version :(
[MTCD  Android Head Units Q&A] f1x:
Hi guys,

please see this thread: http://xdaforums.com/android-auto/android-head-units/mtcd-spotifykeys-control-spotify-using-t3428930 and try SpotifyKeys.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Bonnie1977:
Hey all,

Has anyone tried rooting the new OTA firmware B560? If so, can you post which versions of TWRP and SuperSU were used? And if you happen to have the links to the downloads that would be great too! :)

T.I.A.
[Ascend Mate 7 Q&A, Help & Troubleshooting] pjdpinheiro:
Hi, for twrp I've used the version from this thread http://xdaforums.com/showthread.php?t=3156779 for supersu used the version 2.62 from chainfire website. Installed twrp through fastboot, then in twrp installed supersu. I believe newer versions of supersu works too.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Bonnie1977:
Stuck on Huawei Logo

Okay so I flashed TWRP with no problem, then rebooted normally. Powered off and entered TWRP recovery to flash SuperSU. It installs fine but then when I reboot it just stays stuck on Huawei Logo.

Please help!
[Ascend Mate 7 Q&A, Help & Troubleshooting] touns_j:
i am quoting myself here

SuperSU_v2.64_Pro and BETA-SuperSU-v2.52

what i did after upgrading to B560 ( from rooted B522)and loosing root is, flash twrp ,boot into twrp then flash superSu 2.64 pro zip in twrp , rebooted the phone but there was no superSu icon , i then went and install superSu 2.52 beta apk , rebooted the phone , then i opened superSu , it automatically updated the binaries and voila

ps: i reflashed the B522 stock recovery before upating to B560 with a full rom zip from http://xdaforums.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784

edit : i used twrp from [MENTION=4008653]somboons[/MENTION] app ,it is twrp 2.8.7.0 here's the link http://xdaforums.com/mate-7/development/tool-srk-tool-huawei-beta-02-20160501-t3369990
[Ascend Mate 7 Q&A, Help & Troubleshooting] Bonnie1977:
My problem is I never make it past the Huawei Logo. So I have no idea if SuperSU actually installs. I have reflashed stock recovery for B560, but that still doesn't seem to help. The next step I'm going to take now is to reinstall the update package for B560 and then if I'm able to boot up I'll try your method. Wish me luck! :)
[Ascend Mate 7 Q&A, Help & Troubleshooting] touns_j:
good luck mate , you will sort it out

ps: once you've manually flashed SuperSu , and click on reboot , Twrp will throw a message saying " you don't have root bla bla bla " , and offer to " root " , never accept that , ignore the request
[Ascend Mate 7 Q&A, Help & Troubleshooting] Bonnie1977:
actually I never got that message when I clicked on reboot. Can you tell me which TWRP version you used?
[Ascend Mate 7 Q&A, Help & Troubleshooting] touns_j:
i used twrp from [MENTION=4008653]somboons[/MENTION] app ,it is twrp 2.8.7.0 here's the link http://xdaforums.com/mate...60501-t3369990
[Ascend Mate 7 Q&A, Help & Troubleshooting] RobboW:
I used TWRP 3.0.2.0 from the package that Churdy linked in the main thread with all the different versions of software.

mega:///#!9kBWnY7T!ybhARn5UNXAyxrdQZ1ytKks24eCyzxkgdVhEza6zwFQ

I just had bricks from using genuine Chainfire SuperSU until I used the forum SuperSU Pro 2.64 which also comes with an unroot file.

mega:///#!0wITxJLR!S2iIVNjveSDMdne5QMNqd6so41vbTEK9tSJXJkOJJnw

I have not got Xposed to run properly yet though.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Bonnie1977:
I'm freaking out!!! I can't get any USB debugging recognition, so I have no way of reinstalling the B560 firmware update. I have stock recovery now and my phone just keeps staying on the Huawei logo. Please somebody HELP!!!!
[Ascend Mate 7 Q&A, Help & Troubleshooting] ahhl:
i use the above and it doesnt work. still no root eventhough it manage to install

i noticed during installation

it says

remounting system r/w :(

is this mean it fail to mount??

ok now this work.

before install supersu

go to mount menu and enable system mount

then only install supersu

--------------------

sorry to say i still cannot get full root. cannot go copy paste to system. it still read only. supersu not responding at all!!!?

i disable supersu ( the uncheck button) and exit. then launch again supersu, it update the binary successfully, and reboot. after reboot, i launch and re-enable supersu ( check button) then try to cut/past to system ...unfortunately unsuccessful
[Ascend Mate 7 Q&A, Help & Troubleshooting] RobboW:
Maybe Huawei security software is blocking it from running?

Did you wipe dalvik/cache?
[Ascend Mate 7 Q&A, Help & Troubleshooting] ahhl:
i did try to wipe dalvik/cache but it freeze. luckily i able to reboot successfully

---------- Post added at 10:24 AM ---------- Previous post was at 10:12 AM ----------

ok i go to phone manager and allow supersu to autolunch

now supersu works.
[Ascend Mate 7 Q&A, Help & Troubleshooting] RobboW:
I just used the unroot zip and it worked. This is good as I can root, make changes then unroot.

Edit:

It seems removing root has allowed my file manager to still do root operations, possibly as it was already allowed root access prior to uninstalling SU. Other user apps cannot access root. I just put the Huawei Notepad app back into system/priv-app from backups folder in Storage. Permissions were ok without altering. All I needed was a wipe dalvik/cache in TWRP and reboot.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Bonnie1977:
Unfortunately I reflashed the Stock Recovery and now I'm not able to do anything. I've tried adding the dload folder with the B560 update to reinstall the firmware, but it fails at 5%, with both the OTA update and the Full versions. I'm soooo scared that I have bricked my device. When I reboot into the stock recovery I get 3 options, Reboot System, Wipe data/factory reset and Wipe cache partition. And when I manually force it into fastboot/rescue mode the computer doesn't recognize the phone.

Please someone tell me that my device can be saved somehow! I don't know what else to do :*(
[Ascend Mate 7 Q&A, Help & Troubleshooting] RobboW:
Which stock recovery did you use though? It must be the right one to work.

I found a flash fail at 5% was when there is no update in the /System/dload folder if you're trying to force it to do OTA. I did that by accident. Thought I bricked it but it re-booted ok.

If you use the dload folder in SD card, Marshmallow prefers to kick off the update from the dialler app.

If you used the wrong recovery, maybe it will flash from SD ok with a different ROM but we need to know exactly what recovery you flashed to it. That controls partitioning which you probably messed up.

See if you can re-install a driver and see it with ADB somehow.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Bonnie1977:
I used this one... So it should have worked properly. How can I flash it from the SD card? I'm willing to try anything right now. Because I'm about to go crazy! :D
[Ascend Mate 7 Q&A, Help & Troubleshooting] touns_j:
this recovery works fine from me , i extracted it from B560 update.app.. hmm try and give B522 recovery a try then , put the update.app file in the dload folder and put it on your sd card root folder, then flash the stock recovery using recovery mate7 mobopx v2.1 http://depositfiles.com/files/dkok9h43y then use the 3 buttons trick to force install the firmware

edit : when updating with the full update , you only put the update.app file in the dload folder, nothing else
[Ascend Mate 7 Q&A, Help & Troubleshooting] Bonnie1977:
Yesssss!!! I finally got it fixed... I added the full B522 update to my sd and forced the update and it WORKED!!! The B560's wouldn't but that one did... I don't understand why seeing that I had B560 when I tried rooting my device. I'm just glad that I have my phone back!! :good::):laugh:
[Ascend Mate 7 Q&A, Help & Troubleshooting] touns_j:
i'm glad it worked (i should probably remove that recovery though , maybe the file got corrupted while i was uploading it who knows , but it works fine for me )
[Galaxy Note 3 Q&A, Help & Troubleshooting] ibtehaj29:
Help.

I have a galaxy note 3 Sm N9005 running on android 4.3. I want to upgrade it but whenever i check for an update it shows " your device is running on the latest software".
[Galaxy Note 3 Q&A, Help & Troubleshooting] GuestK0079:
Google.

Sent from my Note 3 running Purify CM13
[Galaxy Note 3 Q&A, Help & Troubleshooting] James_Watson:
I am sure that V4.3 is not the latest Android for Note 3. But I am not clear why you got that version checking result.
[Galaxy Note 3 Q&A, Help & Troubleshooting] JJEgan:
You get the latest version for individual phones .Basically dependant upon supplier/ network .

Sammobile lists latest firmwares .
[Galaxy Note 3 Q&A, Help & Troubleshooting] themagicalmage22:
Try updating via Kies
[Galaxy Note 3 Q&A, Help & Troubleshooting] ch.7amada:
Go to sammobile.com

Download the latest version and flash it using odin

Maybe there is something wrong woth your firmware....so try this method
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] talktosamson:
Not sure what happened. I'm on 6.0.1 modified with root/unlocked, but cannot backup or install roms to my SD card. Is there something I"m missing?
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] tydiamond11:
What might have happened is you have adaptive storage on. Or go to the boot loader unlocked form in android development and try what they are saying
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] karov87:
Try with this version: TWRP 3.0.0-0. Flash this zip: https://www.androidfilehost.com/?fid=24459283995309914
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] talktosamson:
That did the trick, thanks!!
[Galaxy Note 4 Q&A, Help & Troubleshooting] koyutoro:
Hello all. I'm here today seeking help with a problem I've been having with my note 4. A few weeks ago, the phone randomly started lagging really bad, reboots by itself and sometime fails to boot giving the "mmc read error". Usually requires several battery pulls to get it working again. Had this problem during 5.1.1, upgrading to 6.0.1 has done nothing. I have tried booting in to safe mode, clearing cache partition and a factory reset, all in vain. Phone is stock and clean, called Samsung and was politely told to "go f*** myself" since the 1 year warranty is over. Phone is Canadian. Thanks to all those who can help.
[Galaxy Note 4 Q&A, Help & Troubleshooting] ucof:
Hello - I've just had this very same error in the past 2 weeks and only fixed it today.

MAKE SURE YOU BACK EVERYTHING UP ASAP - NO EXCUSES.

Its a hardware failure I'm afraid.

I had to take my phone into the Samsung service centre today, and they replaced the motherobard after they confirmed it as dead.

My phone has the exact same symptoms as yours (lag, reboots, booting only into download mode), except that mine eventually refused entirely to turn on. Im not joking; the next time that it does turn on, make ure you do a phone and SD card full back up before you lose everything (pictures and such like).

I dont know about you, or where you are located, but my Note 4 has a 2 year warranty (Im in the UK) and I received it a year last March ago. Still well within warranty.

Alternatively, you could have a look on ebay for a new motherboard and replace it yourself.

Good luck!
[Galaxy Note 4 Q&A, Help & Troubleshooting] Wilsonb:
I was wondering..

I came across this Forum group since I was looking for boot problems with my SM-N910T3

I hope flashing pit will resolve this..

I recently started to have some low level issue and was hoping it was partition/boot related and not hardware.

Randomly phone boot directly into Download mode with error;

ddi: mmc_read failed

Often I have to pull battery and hold down /power / home for 10 sec to boot up again.

I didn't see an explanation of the purpose of the pit process ; could someone explain?

I am very familiar with custom roms and kernels, Pit is new to me..

Thanks
[Galaxy Note 4 Q&A, Help & Troubleshooting] MisterKanister:
Hi Wilson,

welcome to the club, I am having the exact same problem now.

And bad news first, nothing will help you/us except a change of the motherboard... So bring it to a Samsung service center, the only thing you could do.

Believe me, I tried everything there is to try, including full wiping with flashing PIT files, etc. etc.

Forget it!

This is a hardware issue, as the mmc's are faulty and die after a year. Great.

Just to inform you, a pit file contains the infos about the partitions on the phone, their sizes, file system, etc.

So if you somehow compromised the structure or filesystem of the partitions, you could revert them back to the stock format.

Yeah, but doesn't help if your flash memory is corrupt on hw level...
[Mate 8 Q&A, Help & Troubleshooting] Mercilesslee:
Hey guys I have been using Waze to drive around the city but yesterday I can't use Waze or Google maps. I did not update the phone it just stopped working. Any suggestions? My location accuracy is on high and my battery is on performance.

Thanks
[Pixel C Original Android Development] ggow:
[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]

Prerequisites for Installation

- Must have an unlocked bootloader

- TWRP installed

- If you haven't already done so flash the lastest vendor.img

Fresh Installation

- Backup your existing ROM first

- Perform a factory reset

- Flash the ROM File

- Flash Gapps of your choice (any arm64 6.0 version)

- Reboot

- Enjoy!

Downloads

*** Please do NOT create any mirrors ***

- CM-13.0 for Pixel C

- MXC89L vendor.img

Source Code

- Kernel Source

- Device Tree

- Vendor CM

Credits

- Cyanogenmod

- CAF

- Google

- nychitman1

XDA:DevDB Information

CM-13.0, ROM for the Google Pixel C

Contributors

ggow

ROM OS Version: 6.0.x Marshmallow

Based On: Cyanogenmod

Version Information

Status: Stable

Created 2016-06-06

Last Updated 2016-08-06
[Pixel C Original Android Development] ggow:
Release Notes / Changelog

06 Aug 2016

- August 2016 Security Patches Included

08 Jul 2016

- July 2016 Security Patches Included

28 Jun 2016

- Merged 2554 commits from Google's "chromeos-3.18" kernel branch into cm-13.0 kernel

20 Jun 2016

- Fixed installation getting stuck

- Added support for the Pixel C Keyboard

08 Jun 2016

- June 2016 Security Patches Included

06 Jun 2016

- Initial Release
[Pixel C Original Android Development] ilpolpi65:
Thanks !!!???
[Pixel C Original Android Development] Samt434:
Thanks a lot !!

Going to test it :)

---------- Post added at 12:11 PM ---------- Previous post was at 12:02 PM ----------

As pixel C is 64 bit, should i download arm64 gapps instead of arm gapps ?
[Pixel C Original Android Development] ggow:
Yes, arm64 should work fine.
[Pixel C Original Android Development] Avencore:
Did you apply any patches that improve the slow wifi download speeds?
[Pixel C Original Android Development] ggow:
I haven't noticed slowness in WiFi, if you have problems like this then let me know :)
[Pixel C Original Android Development] Avencore:
Interesting :) Did you also try it on stock rom? Because for a lot of people, including me, wifi speeds seem to drop rapidly after a certain distance from the router: https://productforums.google.com/forum/m/#!topic/nexus/CM9tv3pjTfQ

Will try out your Rom on the weekend. Anyways, thank you for bringing Cyanogenmod to our Pixel C :D
[Pixel C Original Android Development] ggow:
I didn't notice it on stock either but I wasn't looking for the problem either, will check later at home on cm-13.0. I'll post some network transfer speeds.

How far from the router should I be to see the issue?
[Pixel C Original Android Development] Avencore:
Thanks in advance. Just some speeds to compare with:

Pixel C

Down: 27,31 Mbps

Up: 15,51 Mbps

Galaxy S7 Edge:

Down: 111,64 Mbps

Up: 14,88 Mbps

Measured using the Speedtest app and Stock Rom on both devices at the same distance from the router.

For me its enough if there is one wall in between and 5m distance.
[Pixel C Original Android Development] Samt434:
Hi ggow, which Gapps did you flash ?

The rom is working great except i can't flash Gapps !

For me, after flashing the Gapps, at start up the google configuration assistant crashes endlessly after flashing Gapps (both with openGapps and banks Gapps).

---------- Post added at 03:12 PM ---------- Previous post was at 03:00 PM ----------

Finally i have it working : just install the Gapps just after the flash of the system.

DO NOT boot the system before flashing Gapps, otherwise if you flash it after you won't be able to boot (the assistant will endless crash...).

If you did that mistake (like me), a wipe of the cash and of the data partition before flashing Gapps works :)
[Pixel C Original Android Development] ggow:
Yes, I used banks gapps, flashed directly after the ROM.
[Pixel C Original Android Development] ggow:
Near Router

Pixel C

49.46 Mbps

19.00 Mbps

Nexus 6

48.14 Mbps

19.58 Mbps

Upstairs - Much Further Away

Pixel C

47.31 Mbps

18.82 Mbps

Nexus 6

49.38 Mbps

18.99 Mbps
[Pixel C Original Android Development] Avencore:
Thank you for your tests. Your results look promising :) Do you use 2,4 or 5ghz wifi?
[Pixel C Original Android Development] ggow:
I use 5ghz on a huawei talktalk router.
[Pixel C Original Android Development] Avencore:
Okay I use 2,4ghz currently.

Anyways I'll flash your Rom on the weekend and report back.
[Pixel C Original Android Development] ilpolpi65:
keyboard is working ?

thanks
[Pixel C Original Android Development] ggow:
I haven't got a keyboard to test.
[Pixel C Original Android Development] ilpolpi65:
[quote name="ilpolpi65" post=67226890]keyboard is working ? <br />

<br />

thanks<br />

<br />

<br />

I haven't got a keyboard to test.

Thanks anyway
[Pixel C Original Android Development] ggow:
New Build is Up

- Dated 08 Jun 2016

- June 2016 Security Patches Included

- I have contacted peeps at Cyanogenmod on the 6th June about getting official builds...

- ...until that happens I will continue to provide updates here
[Pixel C Original Android Development] Istvan_86:
Hi mate,

See more developers coming is just amazing and get official updates sounds very nice also.

I´m downloading the files but I have two questions, I never flash the newest vendor.img and I´m currently using latest version for Pixel C of TWRP + Dirty Unicorns ROM.

Q1-> I must download and flash vendor.img MXC89F just after the factory reset right?

Q2->I can download any standard arm64 GAPPS package from XDA and flash it right?

Thanks for all the hard work here!!!
[Pixel C Original Android Development] ggow:
Q1 - You can factory reset, flash ROM + gapps then reboot from twrp to fastboot and then flash vendor.IMG

Q2 - yes
[Pixel C Original Android Development] Istvan_86:
Hi again,

Ok I do the process in that order and I´m downloading Open GAPPS arm64 version.

One more question, I also have Super SU v2.74, I think that v2.72 adds support for Pixel C, can I flash it in order to get root or ROM is prerooted?

Thanks again for everything.
[Pixel C Original Android Development] ggow:
No need for SuperSU, you can enable root access within the ROM in developer options.
[Pixel C Original Android Development] Istvan_86:
Very nice mate, I try to flash your ROM in a few hours. if not I do it tomorrow and post results here.

Thanks!!!!!!!!!
[Pixel C Original Android Development] HostZero:
http://xdaforums.com/pixel-c/orig-development/twrp-twrp-3-0-2-0-testing-help-pixel-c-t3395442

if anybody can test this recovery and say if its booting or not!
[Pixel C Original Android Development] NYCHitman1:
Would be nice if you gave proper credit and kept the commit authorship for the commits you took from me and others.

https://bitbucket.org/pixelc/androi...mits/fbf5c0fef447e75dd1edbc213248bf05577b6788

https://bitbucket.org/pixelc/androi...mits/5dc1eeb8a05e053a4e945bd2f68137d521f47b83

https://bitbucket.org/pixelc/androi...mits/7b5d71bfca816f447b611a1c51e8b4cc93be056e

https://bitbucket.org/pixelc/androi...mits/c061ed83bdefe5e59e8e19f363ca234a7648fbf9

https://bitbucket.org/pixelc/androi...mits/ea428b23398d3d35454a4423512d80bb097a6e78

https://bitbucket.org/pixelc/androi...mits/0298334188a07bd930bc2e378297e2a44ad447ff

https://bitbucket.org/pixelc/androi...mits/35b2ccd2720cb329b45063a2dffda5c305771170

https://bitbucket.org/pixelc/androi...mits/950be724894f14446b3e25285e926dc562e2388d

https://bitbucket.org/pixelc/androi...mits/abc246d85e3a5b85f54abcb5f3600d2a9672e73c

Must I continue? :rolleyes:
[Pixel C Original Android Development] ggow:
- I'm not an expert with git. What would be the best way to add authorship.

- What I should have done was take your device tree no google's and put my changes on top - I guess this would have retained authorship on the device tree - I will sort this out.

- Then I will add proper credits

- Also I should add it was NOT intended to take anything from you or anyone else!
[Pixel C Original Android Development] ggow:
- [MENTION=2489052]NYCHitman1[/MENTION] - device tree updated

- Credits added to OP
[Pixel C Original Android Development] Murmel2k:
Woot! Cyanogenmod for the Pixel C? I've already had given up hope. Love you, guys!
[Pixel C Original Android Development] rey_1178:
How did this go? I just got my pixel c as an upgrade from my Tab S 10.5 and see the same thing with WIFI. When I distance myself with both tablets the Pixel C slows down much more than the TAB S. I can be getting 40mb dl while the Pixel C is doing 10mb. Next to the router isn't a problem.
[Pixel C Original Android Development] ggow:
Are you using 2.4 or 5Ghz?
[Pixel C Original Android Development] J_M_H:
I don't think that the WiFi problems have anything to do with the ROM. See this post:

http://xdaforums.com/showthread.php?t=3345129
[Pixel C Original Android Development] rey_1178:
Both. The 5ghz works better than the 2.4 but both really do very poor compared to the tab S. I was hoping it was rom related and that cm13 had improved this. I appreciate the replies.
[Pixel C Original Android Development] ggow:
So is this a problem you're having on stock or cm13. I haven't seen the problem here on cm13. I wasn't on stock for long enough to test.
[Pixel C Original Android Development] rey_1178:
Actually I haven't flashed a rom since I'm not sure if to keep it. I asked in case I could fix it with cm13. It's stock right now.
[Pixel C Original Android Development] ggow:
I posted some speed test results on Post #13 of this thread. So at least the problem doesn't seem to show for me on this ROM. However this is only a single data point.

Maybe some more people will report back soon.
[Pixel C Original Android Development] ilpolpi65:
I suppose I'm making a mistake..I tried to install but remain stuck during 'installing zip' process...using [MENTION=5480152]followmsi[/MENTION] twrp
[Pixel C Original Android Development] ggow:
Could you post your twrp log?
[Pixel C Original Android Development] ilpolpi65:
Sorry I can't....I flashed back N3....but thinking about I remember that before installing the zip rom I performed a factory reset but I forgot to make the 'classic' wipes.....could be that ?
[Pixel C Original Android Development] ggow:
A factory reset should be fine.