yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] maxiauer:
Thanks for the info !!!

So, haven't had time yet to check it, but I'm almost sure the unit had the CanBus connections and the 2 cables labeled Key1 and Key2 floating arround (without any connector). So, you suggest that I use the picture to check which cable is Key1/Key2 on the car side and connect them directly instead of connecting them to the CanBus decoder, right?

Which app do you suggest for the learning/controlling? There's one that came with the Stock SW (Malasyk), but that didn't seem to work (now I understand why, there was nothing to learn, the CanBus controller is doing all the work)

Also, if I connect only Key2, should that work?

Thanks in advance

Max
[Android Head-Units] ikerg:
Try with key2 only to check if works because it seems that key1 should be used by can bus (if not you will not have volume/track controls)

Enviado desde mi SM-G950F mediante Tapatalk
[Android Head-Units] jbyram2:
I found that I needed to connect my 2009 Mazda 6 to Eincar head unit as follows:

EINCAR - SW1 goes to Mazda SW1

Eincar - SW2 left unconnected

Mazda SW2 connected to car chassis ground

The steering wheel resistor/switch network in my car had no ground connection, but the head unit was monitoring resistance to ground to detect button pushes. With no ground connection it always read infinite resistance and did nothing.
[Android Head-Units] Sassokee:
Hi, I can't figure out which are the connectors for Key1 and Key2 as the quality of the image is very poor, do you have any better image? I tried googling but couldn't find any better..

There are wires connected to the Mazda radio harness for Key1 and Key2, Key2 is actually ground.. Do I need to cut those and connect the ones that are loose in the head unit?

Thins is really confusing and all the Chinese sellers are very unhelpful probably because of the language barrier...

As the OP mentioned it, it's mainly for the phone buttons (Answer, hang up, speech) as I want to use them too...

If someone has a schematic (Even lines drawn in MS Paint just to make it clear), that would be great.

Thanks
[Android Head-Units] Sassokee:
If anyone has information regarding this, that would be great, I spent the last couple of days googling this to no avail... From what I understood, all needs to be connected is Key 1 from the head unit to Key 1 in the car radio harness and the same for Key2, then I would be able to remap all the steering wheel buttons including the Bluetooth buttons.

What I don't understand is that the Key1 and Key2 on the car radio harness already have wires connected to them from the head unit side, those wires are going to the CanBUS decoder, can I just cut the 2 wires and connect Key1 and Key2 to them?

[MENTION=744370]ikerg[/MENTION], you seem to be experienced with this, can you please clarify/confirm it?

Thanks
[Android Head-Units] ikerg:
Key1 and key2 are needed for swc control and for retrieving can bus information.

Obviously if you have a can bus connected to your headunits....that wires are already used by can bus.

Try first by removing the can bus.. if all your SWC buttons are responding on the headunit

Enviado desde mi SM-G950F mediante Tapatalk
[Android Head-Units] Sassokee:
Thanks, I will try that and see how it is, but I guess I would lose other features from the CanBUS (Illumination, Reverse trigger for the camera)?

I will probably try to post on a Mazda 3 forum to see if people have information about it. Do you think Key1 is the 5V from the head unit and Key2 is GND?

I will try to unplug the head unit, use a multimeter and press the buttons to see if I get any readings, I will update this here.

From what I understood, you removed your CanBUS decoder and hard wired everything on your Mazda right? Can you please tell me more details about which wires you connected other than Key1 and Key2?

Thanks in advance, you are very helpful.
[Android Head-Units] ikerg:
I had first a MTCD without can bus...so I connected the key1 and key2 wires properly to specific pins into the Mazda adapter and it worked.

Then I realized that I needed a can bus for reverse signal....so I bought a Pac rp4-mz11. Even not necessary it converts as well the swc signal to standard brand SWC signal...and it worked

On my last head unit (specific for Mazda cx5) it comes with can bus and it was a plug and play procedure....everything works as expected.

I have only one button that it is not preasigned...and I had to assign ton an action by mtcdtools.

Enviado desde mi SM-G950F mediante Tapatalk
[Android Head-Units] Sassokee:
As I have a CanBUS decoder with my head unit and the multimedia buttons work OK, do you think I can assign the Bluetooth buttons using MTCDTools? The SWC learning app with the Malaysk rom doesn't seem to detect any button when pressed... But the multimedia buttons are pre-assigned I guess from the CanBUS.

Thanks
[Android Head-Units] Sassokee:
I tried MTCDTools, it doesn't seem to recognize any buttons press, so I guess the only way is to remove the CanBUS decoder and wire everything up, I guess I can still use wires for REVERSE and ILLUMINATION from the head unit to the Mazda radio harness?
[Android Head-Units] ikerg:
He reverse signal, at least on my cx5, is coded (no resistive) so I needed can bus for getting signal

Enviado desde mi SM-G950F mediante Tapatalk
[Android Head-Units] Sassokee:
If I run the 5V on the video cable for the reverse, would that switch the display to the reverse camera when setting the gear on reverse?

I'm starting to think about getting the female connector for my radio harness and connect every single wire to it and get rid of the CanBUS decoder as the only thing that it does is just showing the reverse camera when switching to the reverse gear and thr use of media controls, but because I want to use all the other buttons (Bluetooth, speech etc...) I'm thinking about going that route.

There are pinouts for the head unit, the ones for the car should be online too...
[Android Head-Units] twokidsandaphone:
We have a Mazda 5 with factory Bluetooth. The steering wheel controls go directly to it. You need to take some dash apart to get to it and then unplug factory box. Since I couldn't find a connector to mate with the plug, I wiretapped the wire.

If you think yours is the same I can send you the wiring diagram a bit later. PM me.
[Android Head-Units] Sassokee:
That would be great, I think mine is behind the glove box from what I gathered, but if you could PM me the diagram that would be really kind of you my friend.
[Android Head-Units] twokidsandaphone:
Sent you a PM, but not sure it went through.
[Android Head-Units] Chu92:
Hi, I have the same problem as Sassokee. I have a Mazda 3, 2012, with the Dasaita 9'' model and I also have factory bluetooth. Can you send me the wiring diagram, too, please?
[Android Head-Units] ttoton:
Hi! I just bought a new PX5 8-core device for Mazda 6 2009 to replace an old 4-core Android 5.1 unit.

In the previous one both reverse camera and steering wheel control (I only have Vol+, Vol-, Mute, Prev, Next buttons) worked flawlessly.

In this model neither reverse camera nor steering wheel control work at all!

I do not have a video signal from reverse cam even in VID-in app when connected to AV-in RCA cable instead of CAM RCA.

I suppose both of them are differently wired in the new type of head unit.

In the previous one steering whel control and reverse gear signal probably were fed via CanBus.

In this device I have separate cables that go out from the back of the device named: "Reverse", "Key 1", "Key 2".

They are currently not connected to anything, as there were not such connections in my previous device.

Below is the general schematics. Please excuse me for not being very professional with the drawing ;)

https://ibb.co/qW64TZr

Now I only have a yellow RCA named "CAM-in" connected to the RCA coming from the CAM.

But it seems the cam doesn't even get powered.

Same with steering wheel control.

I suspect I need to cut the KEY 1, KEY 2 and Reverse cables that go to ISO port / or from ISO port to CANbus decoder / or somewhere else?? and connect them directly to those 3 appropriate connectors from the device.

Edit: This is partially confirmed by the Seller, who sent me this schematics of connecting the reverse CAM. You can see the "reverse" cable from the device is connected to the red wire that goes along with the signal cable from the reverse CAM. It was not like this in my previous unit.

https://ibb.co/wB7Mm98

Can you or anyone confirm if I'm thinking right?

Thank you in advance for your help.

Regards,

Tomasz
[Android Head-Units] ikerg:
If I read well...on the old one you had a canbus and on the new one not.

Without canbus it is very difficult to connect the cam as you are not going to get 12v signal when reverse..as that signal is coded (at least for Mazda cx5 and Mazda 6 2012+)

Enviado desde mi SM-G950F mediante Tapatalk
[Android Head-Units] ttoton:
I do have a canbus / canbus decoder, which looks exactly like the previous one, just serial no and production date is different. I just connected it to the ISO port, same as previous one.

But I have those extra cables from the device that are now not connected.

https://ibb.co/WWWXRT6

https://ibb.co/72hPsDW

[EDIT: Solved] Mazda 6 II GH '08 + MTCE PX5 KSP 4GB

I solved the steering wheel control issue with a simple solution suggested by the seller.

He suggested to connect KEY1 cable from canbus decoder

to RX cable

coming from the device, and

KEY2 to TX cable

from the device (KEY1 and KEY2 cables from the headunit left unconnected!), or the other way around.

Suprisingly, this worked and everything works great, including prev/next in Spotify, without any other apps installed

https://ibb.co/HFgRZBB

https://ibb.co/9hXChkR

This feels rather like wrong labelling of cables (I really see no reason for connecting KEY1 to RX instead of KEY1 to KEY1, etc), but anyway. I would probably not even think of this solution, as this is ridiculous at a first glance ;)

Hope this helps someone.
[Android Head-Units] aamini64:
Hello

could you finally resolve the issue? I have the same problem, mazda 3 2012 with an chinese head unit (eonon android 8.1) and the phone buttons do not work (the rest of buttons work fine).

Thanks
[Android Head-Units] NiGHTSaturn:
I have the same exact issue for my Mazda 3 2012, I read the thread about 5 times and I still don’t understand which cables should be connected to Key 1 and Key 2 to make the SWC work fine. My CAN-BUS decoder only gives me access to volume and barely the next and previous buttons!
[Android Head-Units] Kewz4:
Any updates on this? I have the exact same issue. @aamini64 @NiGHTSaturn @maxiauer , did u guys find a solution?
[Android Head-Units] NiGHTSaturn:
Been about 2 years, for what I remember, at first, I could only register the volume controls, after a couple updates of the carplay app I was able to change register the skip buttons too, which was plenty for me.

As for siri, the microphone on this model is the worst I ever used so I don’t even bother using it till I find another model that accepts a line in microphone.

Key 1 and Key 2 were not used. The Can-Bus is worked for volume and skip. And they were registered on the Carplay app, not the main android radio settings.
[Android Head-Units] NiGHTSaturn:
For more info:

Check the comments with my Username if that helps.
[Android Head-Units] Kewz4:
Sorry for bringing it up again, it's the only thing on the subject I could find. So you never got the phone and voice Buttons to work? I can remap the volume up/down as well as next and prev buttons. What did u binded them to?
[Android Head-Units] NiGHTSaturn:
Like I said, the Car2Play app has a mapping function and it was still in beta testing but available. I never bothered using the mode and call buttons after that. Especially since how atrocious the microphone is. I will probably upgrade the radio again in the future since i’m keeping my car for a couple more years.

A lot of people told me that usually the can-bus does the job. It was all a matter of waiting for the updates.

And don’t worry, i’ve recieved a lot of help from the guy in the video to get my 12v source working, as it was my first time installing an aftermarket radio. So ask away! 😉
[Android Head-Units] Kewz4:
Welp, no luck here 😔 Tried every single Mazda3 Can type I could find, my phone and voice steering wheel controls are not recognized no matter what. That's why I asked you if they atleast were recognized.
[Android Head-Units] NiGHTSaturn:
I understand. It sucks! Do you use CarPlay or AndroidAuto?
[Android Head-Units] Kewz4:
I use Android Auto! but I sometimes the Hey Google command doesn't get recognized, that's why I was searching if I could make one of these buttons work so I could map that to one of the buttons. Also tried Carplay and it is great!
[Android Head-Units] NiGHTSaturn:
Update Car2Play, and check the settings IN Car2Play to see if voice recognition can be modifed. I know Siri works for me (barely with the microphone) but I never tested Google Assistant. Better to use Carplay or AndroidAuto for the best experience. I never used Seicane’s menus.
[Android Head-Units] Kewz4:
Will do, thanks! Hopefully the can bus can recognize it on the future. Again, thanks for helping on such an old thread.
[Android Head-Units] NiGHTSaturn:
Not a problem! 😊 I’m glad I could help a little bit. If only their customer service was better too… I have no idea which model I will go for next time.
[Honor 6X Questions & Answers] WetWilly:
I picked up two Honor 6X BLN-24 models, the serial numbers are within a couple hundred of each other, so I'm assuming they're from the same batch. Right now they're both on Nougat, but one looks like it has a partial install of Nougat and the other has a "normal" install. Here's what happened:

1) The partial install phone - I unboxed it, connected it to WiFi, did a check for updates; it found the Nougat update, so I let the system update itself, rebooted, had Nougat B360. Flashed TWRP, which is working fine on the phone.

2) The "normal" install phone - instead of updating straight to Nougat, I installed TWRP first and had a bunch of issues with the wrong TWRP .img file; that's a separate issue. Got Nougat installed eventually on the phone but ended up with the "Test Keys" build issue. Ended up doing the rollback to MM, then did the check for updates, it found the Nougat update and I let it install. Phone has Nougat, build shows as B360.

Thought everything was fine and didn't really take a good look at the phones since I had to do other stuff to do before migrating to the Honors.. Now I'm ready and I'm noticing that one phone - the one that went to Nougat straight out of the box - doesn't have a bunch of apps that the second phone has, like the FM radio, CNN, Lyft, News Republic. Outside of the FM radio, I don't care about the other apps, but something else is missing - the System Update option in Settings. There may be other stuff missing, but the System Update thing is problematic.

So I figure my options are:

1) Rollback the phone that's missing things to MM, then retry the update, or

2) Try a dirty flash of the Nougat B360 update and data files.

3) Flash the smaller update_data file for the B360 build that contains most of the apps (but doesn't look like it has the FM radio)

Or is there another option?
[Honor 6X Questions & Answers] shashank1320:
Go with option 2. If no success then I would suggest for option 1.

Need couple of favours as you did rollback. Do you have the rollback package file? If yes, please share.

If you are rooted, use Huawei mutli tool and backup the oeminfo file. I need both these files so that if anyone messed up with their phone we will be able to revive and also address the nrd test keys issue and the best we can do is to debrand from other variant to US variant.

Thanks beforehand.
[Honor 6X Questions & Answers] narshi shukla:
I had similar issues my phone was showing as nrd test keys and the backup of twrp also indentify phone as nrd test keys. When I checked updated update it was showing no update. My phone wassoft bricks so i download and updated package for build no b 340 and in build no it was showing nrd test key

Later i flashed zip shared in volte fix thread on xda as I was not having volte.

After flashing all thing went good test key issues resolved also so u can try that zip also.
[Honor 6X Questions & Answers] WetWilly:
Thanks for the replies, I'm away from the phones for a few days but will report back.

For shashank1320, the intermediate rollback package (the one that's flashed first from Nougat before the actual MM ROM) is still available on the US Honor site at http://www.hihonor.com/us/support/details/?DOC_ID=94205
[Honor 6X Questions & Answers] narshi shukla:
You can use it if it matches with your last build no
[Honor 6X Questions & Answers] shashank1320:
Thanks downloading now. Yes then you can use this file for rollback.
[Honor 6X Questions & Answers] WetWilly:
Here's the latest update. - I tried the dirty flash method and it wouldn't work. AT ALL. I'm getting the "software failed update" at 5% message that several others have received. I downloaded the BLN-24C567B360 FullOTA package from three different sources; all had the same hash and *none* of them would work using the dload method. I ended up flashing the MM rollback package (which worked perfectly via the dload method) then flashed the MM firmware (also worked perfectly using the dload method). The phone booted into MM, it found the 2.35GB Nougat update (which is the same size of the Nougat .zips I downloaded), and it installed the update. It also installed the FM Radio (a system app) and the US package of apps that for some reason it didn't install when it upgraded to Nougat fresh out of the box.

I actually did this rollback/roll-forward twice since something odd happened while playing with SafetyNet with Magisk and the FRP Lock tripped. The next thing I know I'm getting the "data partition is corrupted" message and, again the B360 update.app files wouldn't flash. Thankfully the rollback worked. FYI, rolling back to MM relocks the bootloader. At this point I'm just keeping both the rollback and MM packages saved together on an SD card; flash rollback, pop card, rename folders on PC, pop card back in 6X, flash MM, reboot, find update, OTA to Nougat. Easier done than said, actually.

I am curious about why none of the B360 Nougat update.app files will flash on either phone. I don't think it's coincidental because the e-Recovery via WiFi doesn't find a package, and if I try System Recovery in HiSuite it says "no recovery available; take device to a Service Center".
[Honor 6X Questions & Answers] itisiryan:
If you get this issue again, try to format data inside TWRP.
[Honor 6X Questions & Answers] WetWilly:
I actually tried that. I ran into this same issue previously when I had TWRP installed, and TWRP's wipe data didn't work. Ultimately had to do the rollback to MM/roll-forward to Nougat and re-unlock the bootloader.

I can't figure out why my two phones won't flash Nougat using the dload method. The only logical reason is the upload.app file signatures, but I haven't found any alternative Nougat files for BLN-24C567B660.
[OnePlus 5 Questions & Answers] exce1ia:
Can changing to DCI-P3 or sRGB drain battery more? Is there any processing in the background happening?
[OnePlus 5 Questions & Answers] jhs39:
I haven't noticed more battery drain after switching to DCI-P3 but they are just different color profiles. I don't know why there would be a significant amount of difference in processing power of one over another. Even if there is a difference the phone is certainly powerful enough to handle it.
[OnePlus 5 Questions & Answers] Gabbbbbbb:
There is processing, but it's so negligible in terms of power, that you shouldn't worry about it at all.
[OnePlus 5 Questions & Answers] exce1ia:
Thanks. I think it also saves the screen from burn-in as the blue pixel is less used.
[OnePlus 5 Questions & Answers] Gabbbbbbb:
If you can make the whites yellowish it can certainly make burn ins to appear slower.
[OnePlus 5 Questions & Answers] exce1ia:
Yea DCI-P3 looks yellowish compared to default. Also applies to sRGB.
[OnePlus 5 Questions & Answers] Gabbbbbbb:
I wouldn't expect too much from it though, maybe it would slow the burn ins by at most 10%?

But hey, it's good for one's eyes.
[OnePlus 5 Questions & Answers] exce1ia:
I thought it would slow it for about 30%. Yea but it's good for the eyes which is good.
[OnePlus 5 Questions & Answers] evilhomura89:
I doubt switching to DCI-P3 or sRGB will reduce the rate of screen burn in or will be good to the eyes.

The purpose of having these calibration is so that the color will appear more "realistic" - ie, what you see is what you get from your printer. Basically it's a standardization of color information across different devices. It's important that what you see (on a calibrated screen) is exactly the same as what others see on their (presumably calibrated) screen.

I find it to be very useful for photography as it will actually prevent post-processing errors such as over or under-saturated colors.
[OnePlus 5 Questions & Answers] Gabbbbbbb:
Actually you are wrong about the burn in. As long as whites are more yellowish with the aforementioned calibration modes, then it will help with burn in, albeit very little. Also there is a reason why blue light filter modes are out there included on almost all smartphones, warmer display tones do tire the eye less and you can achieve this result by screen calibration too. I realize that the original intent of the srgb & DCI modes is different, but if the displayed colors are warmer, then ..
[Nokia 6 Questions & Answers] jimmygumble:
I accidentally selected the United States radio band in the *#*#4636#*#* phone information menu. Since I'm not from the US this disables the cellular radio on the phone for my region.

There's no other options in the "select radio band" menu other than "united states". Online solutions mention an "auto" setting but there's no such option in that pop up menu.

I've tried a factory reset to resolve this but it didn't work. I've also tried different radio settings in that phone information activity (LTE, CDMA etc). I've tried resetting network settings in the system settings app. I've also tried reinstalling the latest OTA update (September) through recovery but it did not change the radio back.

Erasing the modem state using fastboot won't work since the device has a locked bootloader. I assume it fails for me because of a locked bootloader anyway. This was a suggested solution for others and I feel like it would work.

I think a full firmware flash would also fix it but I don't see any TA1033 firmware files anywhere and Nokia still haven't released any tools either.

What do you think?
[Nokia 6 Questions & Answers] mj_arafat:
I use the Indian version. I'd faced the same problem while doing the same *#*#4636#*#* settings. I also did all the above solutions which u mentioned. At last I had to go to Nokia service centre and told them that this happened all of a sudden and didn't disclose 4636 setting thing,as they might use it as a void of warranty issue. They simply rolled back the system to June version and the phone was back to normal. But one thing that I'm facing now is that I'm now not getting any update to the latest one. I think they might have block it or something coz I don't know much about android. I need to go to the service centre soon. If u r going to the service centre make sure that they don't block the update setting.
[Moto Z Play Questions & Answers] ghannna:
I have unlocked my bootloader, currently I am using stock android Marshallow 6.0 retin channel. Can I download Nougat OTA and manually flash through stock recovery. I have not rooted my device and I have not changed the recovery.
[Moto Z Play Questions & Answers] WiserJr:
If you install the Verizon version your device will update automatically.
[Moto Z Play Questions & Answers] St.Noigel:
DON`T DO IT!!! If you want to have OTA`s - just reflash lastest RETIN FW.

If you have 6.0.1 - flash 7.0 and you`ll have OTA to 7.1.

P.S. Don`t give OTA if your FW was downgraded