yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Need4Camaro:
Thanks for this information, is it okay if I inquire which heatsink / fan you specifically used from Amazon (or any vendor). I'm going to try this as it can't hurt at this point. Do you happen to know aproximately the measurements I'll need for a heatsink / fan? You recommend leaving the LID off? Also while I'm in there, should I disconnect the internal MIC and use only the external (altogether different issue because no-one can hear me.)
[Android Head-Units] luciusfox:
I have a heatsink like this;

https://www.amazon.ca/gp/product/B00REFDKJW

And fan like this;

https://www.amazon.ca/gp/product/B072Q3CMRW

That heatsink is actually a bit longer than the SoM, but there is enough space for it to stick out.

Yes, I absolutely recommend leaving the lid off, otherwise you're just recirculating hot air.

Its your call if you want to play with the wiring. Not sure why you would want to disconnect the internal though, contrary to some obsolete information you may have found that applies only to some MTC units, they are NOT wired up together. They are actually separate inputs to the DSP, which will select the external if it is plugged in, OR (not AND) the internal if the external is NOT plugged in.
[Android Head-Units] alessondanilo:
I did the procedure as you told me and it is causing errors as in the picture.

[IMG="Error"]https://imgur.com/a/0O5vg[/IMG]

And when I try to do the "normal" update from 5.1.1 I get the following error:

https://photos.app.goo.gl/Mva5SE4AMaxFOx4P2
[Android Head-Units] gtxaspec:
Edit the first line of the updater script, change the line that says something 3grw or wifi.

Also don't forget to remove the last line that flashes the bootloader, fwu something.
[Android Head-Units] alessondanilo:
I did this and is now giving error in assembling the participation system. And if I try to update by the normal method, it gives that image error 1, regardless of whether it is version 5.1 or 6.0. Can someone help me?
[Android Head-Units] gtxaspec:
Try flashing un modified 5009_60.zip, don't use twrp
[Android Head-Units] alessondanilo:
Where do I find this modified 5009_60.zip?
[Android Head-Units] alessondanilo:
I tried again to install, but is giving this signature verification error. How to get around this?

[Edited]

I'm guessing the problem is the changed keys of the new recovery image.
[Android Head-Units] luciusfox:
You can't use the factory or factory-modified recovery image to install an update that it doesn't like.

If you want to install it, do like gtxaspec said and fix the first line in the updater-script, because that is clearly telling twrp that it is a dangerous update.

twrp may also have a setting somewhere to ignore that line.
[Android Head-Units] alessondanilo:
Let's see if I'm doing it properly.

- Edit the first line of the update script that is in> 5009_60> META-INF> com > google> android> updater-script

Then I go into recovery mode through TWRP and install the zip, right?
[Android Head-Units] Need4Camaro:
Thank you very much for this, one other question, what did you screw the fan onto?
[Android Head-Units] alessondanilo:
I'm forgetting some configuration, because the system partition error continues.

Can you help me, I just want to get my head unit back.
[Android Head-Units] luciusfox:
Pretty much, yeah.

That first line in there is the reason why twrp hangs up and claims the update to be incompatible with the hardware.

But do please look through all the menu options in twrp first. It has a heck of a lot of options, so it wouldn't surprise me if it has one to override hardware compatibility checking.

---------- Post added at 07:51 PM ---------- Previous post was at 07:49 PM ----------

Looks like the problem may be access contention. Check if the partition is mounted before you try to install it. If it is, try to unmount it. There should be buttons in twrp for this.

You might also be able to work around it by altering the updater-script. For instance, drop the mount line, or add an unmount line.

---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------

The heat sink. Pretty sure I said that already.
[Android Head-Units] alessondanilo:
I signed the update package with the temporary keys and now the installation gets stuck on this screen.

[EDITED]

solved the problem

This last error I was giving was that I had removed the first line and the intel_install_firmware_update line from the update script.

I managed to get around this by downloading the original file 5009_60 and signing it with the test keys (no mending in the update script).

The update flashed like a charm.

Note: Can not downgrade to version 5.1.1 Sad
[Android Head-Units] gtxaspec:
Why can't you downgrade to 5.1.1?
[Android Head-Units] alessondanilo:
The installation does not accept 5.1.1. it looks like the partitions are different. I only know that an error occurs using twrp and if you try to install in the normal method, Setup identifies and generates that incorrect package message.
[Android Head-Units] edit:
This is the perfect example.

This, is what I was talking about [MENTION=8472040]luciusfox[/MENTION]. What seems easy for you it's not so easy for the "rest" of us.

Nothing goes that easy and if you encounter bumps along the road and you have zero experience to deal with them...

In theory lots of things are simple, but in practice things turn to be more complicated...
[Android Head-Units] alessondanilo:
exactly what happened to me, I'm new to Android. I know a bit of Linux, but I ended up having problems along the way that made me think that the head unit had died.
[Android Head-Units] edit:
I tried to explain to him that we need help here, and help needs to be translated in step by step tutorials that everyone can follow and succeed in solving their problems.

In fact I am asking all the skilled people, if you want the help everyone that it's participating or maybe just lurking and trying to figure out things.... write short tutorials easy to follow please !

Test and make sure the tutorials work... a soft bricked unit might be easy to unbrick for a skilled guys but might mean 50-80$ in shipping fees to China for servicing for others
[Android Head-Units] gtxaspec:
Dude, trial and error. That's how we all started. Sometimes stuff goes wrong and you have to figure out how to fix things. Sometimes you figure it out yourself, sometimes you ask and get help. This is the perfect example of someone who did the research and work, figured out how to fix it and was successful. I think it's a positive outcome!
[Android Head-Units] alessondanilo:
No! with me was giving error exactly for having removed these lines. I returned these lines and the installation blinked naturally
[Android Head-Units] sanangel:
Where is TWRP for Joying ?, Could you install xposed? ... It would be interesting a separate thread for this topic.
[Android Head-Units] surfer63:
I agree with you (@gtxaspec), [MENTION=8472040]luciusfox[/MENTION] AND [MENTION=309187]edit[/MENTION]:

Of course you expect users to try themselves and do not give everything on a silver spoon, because that is what we all have to do when learning something new. You have to work for it.

However, in this forum we have a huge difference in skill set among the various users. Some users do not even know what to search for and then it comes in handy to get some tips& tricks.

Some users do have a skill set in programming, sometimes because it is their day2day job. Others have a background as technical ICT-consultants, giving them extra knowledge on operating systems (for example).

Some users are building up their skill set by reading a lot and sharing their knowledge in extensive Q&A's where the rest can learn a lot from, like [MENTION=309187]edit[/MENTION] is doing.

We all have different skill-sets. I was once builder/compiler for Hugin on OS/X, later on I was change and release manager. (Now I'm no longer active there.) We also had a guy who had a background as loyer. He could fight a GPL license infringement.

If we had that guy overhere, he might be able to use the proper channels to fight Joying/FYT in their illegal kernel activities, without him ever being able to understand TWRP. We need to help each other.

Coming to TWRP: users who have only experience with the Joying way of updating, be it on the older MTCDs or newer Sofia 3GR Joyings, or with their Samsung, Nexus, Motorola phones occasionally receiving notifications that an "upgrade is ready to install", and who never touched Cyanogenmod or other custom roms, indeed have no experience with TWRP. Which makes it not so simple.

We all can do something to add to this community. I'm almost sure that if there was a clear step by step example, [MENTION=309187]edit[/MENTION] would immediately add it to his Q&A for others to benefit. In other words: we all (the "good ones") contribute in our own way.

We can learn by re-inventing the wheel, or by learning from others.

I fully understand that some are spending every minute of their personal, free (!!) time to bring us to the next level of Android on head units: That is really, really appreciated by the community. They simply don't want and actually can't divide more of their time in also writing howto's as that will take quite some time as well. I fully understand that, and most of us do.

But these same members are sometimes very unfriendly (to state it mildly) in their comments, which is not so nice.

Let's try to respect each other for what he/she is, and help each other.
[Android Head-Units] luciusfox:
He came up to an "already mounted" error. Probably the oem recovery mounted the system partition before the temp twrp started the install process, which borked the whole process (format a mounted partition, then try to mount it again).

Which means that he was 99.999% of the way there, but gave up at the very last (trivial) hurdle.
[Android Head-Units] Need4Camaro:
Hey I have one other question. I disassembled my unit and I found a silver plate covering the core. It looks like it's soldered on. Did you remove this plate or did you put the heat sink on top of it? Will I need to desolder this plate? Image attached.
[Android Head-Units] alessondanilo:
Friend, as far as I know, you'll put the heatsink on top of this plate, just like it does on Intel branded processors.
[Android Head-Units] alessondanilo:
Downgrade for 5.1.1

I will try again to downgrade to version 5.1.1, but now I will do it with more attention and care.

I will probably succeed, for the tricks I have learned here.

If I can, I'll give you the answer later!

:)
[Android Head-Units] luciusfox:
DO NOT remove the plate, or you won't have any way to attach the heatsink.

peel the stickers off of it, sand its surface to clean and rough it up a bit (helps the epoxy stick), same with the bottom surface of the heat sink, stick them.
[Android Head-Units] alessondanilo:
Once again I did the test and I do not know if I'm jumping some steps, but I can not install the version 5.1.1 update zip. I am doing the following:

After changing the recovery partition with the public keys, I am blinking the TWRP as indicated.

I make the changes in the update script, removing the indicated lines.

So I sign the update zip with public keys.

I do a cleanup and I try to install the zip.

TWRP generates an error.

The error generated is a number 6 error. As it has no description, then I was prevented from correcting. What am I doing wrong?
[Android Head-Units] surfer63:
Please share your updater script. It could be an error in there.

Beides: how did you modify that file? With notepad on windows, or with an editor supporting unix line endings?

========

Edit:

And did you remove the line

package_extract_file("nvm_fix.bin", "/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID023");

like gtxaspec told you?

To my knowledge it should NOT be removed.
[Android Head-Units] gtxaspec:
Are you flashing in twrp or recovery?
[Android Head-Units] alessondanilo:
I'm trying to flashing first the TWRP, to then finish the downgrade using the Recovery.
[Android Head-Units] gtxaspec:
Try flashing first using recovery, report back with results.
[Android Head-Units] alessondanilo:
ok I'll try, but from what I know, the recovery will not allow to be an upgrade from 5.1.1

The last time I tried the recovery first, the update stopped at this screen here.

[IMG="tela"]https://i.imgur.com/wBNS1tB.jpg[/IMG]
[Android Head-Units] gtxaspec:
Create a blank file named "Allapp.pkg" include it with your 5009 zip and try again. Make sure you signed the zip with the test keys too
[Android Head-Units] luciusfox:
Does a dummy file work for it? Or does it have to be in valid allapp.pkg format?

I would actually suggest that if he is installing 5.1, that he use the actual Allapp.pkg corresponding to that build, otherwise he will get no-heartbeat reboots every few minutes and no control of any of the car interface components.
[Android Head-Units] gtxaspec:
Yeah, dummy works.
[Android Head-Units] alessondanilo:
I'm finding that my head unit is different from the ones you tested, because the whole process of downgrading to version 5.1.1 does not work ... It simply does not accept the upgrade.

My head unit is the UM124N2.

Of course I did not try anything in depth, even though I only have free time at the weekend, but in all my quick tests it was not possible and in the last test he did not want to go into Recovery mode.
[Android Head-Units] alexyie:
i just saw new product released by Joying (RX5 cpu) with similarly looked with our Sofia unit, also with android 6, and it said it has Full RCA video output.

Is this Video output something hardware, or is it achievable via software/firmware to our unit?

this is the link:

https://www.carjoying.com/head-unit/universal-car-head-units/7-double-din/371.html
[Android Head-Units] surfer63:
Please do not hijack this thread. There are other threads discussing the PX5 (not RX5) models and/or sound/RCA.

And/or: ask Joying: carjoying@gmail.com
[Android Head-Units] derschnelle:
I am having problems with my GPS, I can't get any reception. Wiping and updating to September version didn't help.

Has this been an issue here before?
[Android Head-Units] edit:
Take the unit out and check if the GPS cable plug is attached securely to the unit, also check the cable for damage, the plug. Also you can pop the unit top open and check the GPS cable inside if it's still soldered to the SoM properly or got loose (broken).

If everything looks ok, order a new antenna and test with it, if it works keep it... if it still does not work return the GPS antenna... probably there is an hardware issue with the GPS on the SoM (but I don't think so).

In all my testing, all the flashing, all the firmwares tested, I never had any issues with the GPS.
[Android Head-Units] derschnelle:
Thank you very much for your advice! I just took the uni out and checked the gps-cable. It seemed fine, but still no reception. Then I changed to the joying-gps-mouse and voilà there it is. So it seems, my pre-installed gps-mouse is having problems.

For now I will use the gps-mouse from joying and will look into the matter later.
[Android Head-Units] edit:
I am happy that you solved the problem !

I had 2 of these GPS antennas broken down on me in the last 5 years.

I have a diesel car that it vibrates a lot more compared to a gasoline one so that might be one of the issues. These tiny vibrations might wear down the cable a lot faster if it's free and not tightened... and I doubt that cable on these cheap 10$ GPS antennas is of a very high quality.

My advice is : Make sure that the cable does not have tight (sharp) turns and it's not tensioned. Also don't let the cable loose inside your dash, get some zip ties and secure the cable from moving around or vibrating freely (if you have a diesel mainly).
[Android Head-Units] ZoSo028:
Hi guys, my Sofia unit has been experiencing problems lately with wifi disconnects. I have it set to connect automatically to my phone's wifi hotspot. The phone is always in its holder directly next to the hu, so the signal strength is presumably excellent at all times. The unit has been disconnecting from the wifi hotspot at random, and while it does reconnect eventually on its own, this has been leading to some problems with certain apps I run staying in their online modes. I'm also able to manually reconnect it when this happens. Would still love to fix the random disconnects entirely. Any advice?
[Android Head-Units] mwhelan182:
Hey, random question, has anybody had any issues since Android updating their phones, and Bluetooth connectivity with Intel Joying units?

I suddenly have no real consistency over the past few days, as it's almost a sound cut out, when music or any audio is playing via Bluetooth.

Also,possibly unrelated, I disconnected, reconnected a few times, got it to work, and after a minor glitch of not recognizing the phone, the hissing sound stopped, and music played per-normal.. So now I'm unsure if it's a Bluetooth issue with my phone or Bluetooth issue with the head unit S

Anybody experience anything similar?

Thanks!

Mike
[Android Head-Units] xdamember2:
I looked into this a while back and learned google/android does not support offline speech recognition on this processor. Unfortunate because There's an app I use which accepts dictation only with Google osr.
[Android Head-Units] TheGreek76:
I've had what sounds like identical behavior that started a few days ago. Random skips and cutouts every 3-10 seconds, seemingly at random.

My phone hasn't done any updates. Only updated apps on the phone and head unit. I've tried repairing, clearing the bluetooth app data, with no luck.

-Damon
[Android Head-Units] Andy2732:
Has anyone tried/have any thoughts on the latest update? (Oct,25th,2017)
[Android Head-Units] ch_swat_89:
I'm happy with the newest firmware.

Wifi problems solved. Bluetooth works better...
[Android Head-Units] dyabolikarl:
Anyone tested the SWC mod with the new update?
[Android Head-Units] ZoSo028:
Installed the latest update, now anytime I try to reboot the hu it reinstalls the system software, resulting in a full factory settings reset. Anyone else having this issue or know the cause?
[Android Head-Units] Jaihoidundso:
I have always full factory settings after update. Since I know that, I always make backups before I install the update.
[Android Head-Units] ZoSo028:
I know that the system goes back to full factory settings after an update. What I'm saying is that I'm experiencing an issue now since the latest update that every time I try to manually reboot the unit, it seems to do a full reinstallation as if I had just updated the software again.
[Android Head-Units] :
In my case this update was not good, the bluetooh in september update is great, now is horrible, everytime drops out, when i play some music in dezzer or another music player. I'm backing to september version.

EDIT: I made a factory reset and now the bluetooth is good, the music is not droping out. Made a factory reset after instalation.
[Android Head-Units] Logicsystem360:
Try to reinstall the update from another drive
[Android Head-Units] swanie2000:
Over the weekend, I updated my radio to the new Oct,25th,2017 version. After the install I noticed that my microphone(s) were not working anymore. I also noticed that in the Joying settings, there was a new option for bluetooth microphone, either front or rear. There is still a setting for high and low sensitivity, I tried both settings, with no JOY. All apps that would allow use of the microphone fail to hear the user input. Complete failure, as in no sound input at all. This is a big problem for hands free calling, to say the least.

So I tried in vein, over and over, (SDcard and/or USB) to roll back the radio to earlier firmware(s), in the hopes that it would roll back the new MCU update. I was able to reload previous firmware, but none had the microphone working. Finally I ended up grabbing the wrong Oct,25th,2017 firmware, and when I flash that, I got a big bright orange banner across the top of the screen saying MCU(followed by a bunch of Chinese letters). That stopped me last night. This morning, I reloaded the correct Oct,25th,2017 firmware, and I am now back to square one. New version Oct,25th,2017, with no microphone, and without the ability to reload the stock ASOP settings.apk, nor the NO KILL mod.

I don't think the microphone(s) I have are bad, as they used to work. The built in one on the front of the radio, and the rear connection that is routed up to the headliner, both used to work. I have not removed the radio from the dash, so it is not likely to have come unplugged. Both microphones failing at the same time points to something common between them, I suspect it is the MCU, as they did make a change there with respect to the microphone.

Can anyone else who has taken this ill fated step, please respond with your experience? Do you still have a working microphone?
[Android Head-Units] Nightmare[ITA]:
[MENTION=8707284]Luque86[/MENTION] [MENTION=2185201]ch_swat_89[/MENTION]

I had this issue too, just reflash the Firmware again that should solve the problems. After the first flash, the unit was a total mess.

Also hit the RST button after flashing.

For the Bluetooth issue have a look at this post:

Bluetooth fix
[Android Head-Units] edit:
Seems like an firmware issue.

What I would try in your place, not guaranteed to work, but some ideas that might help you :

WARNING : if you are NOT using any cooling mods (additional heatsink and/or fan) let the unit cool down before flashing or each intensive CPU operations like reset to defaults that takes a while to build up the files needed for booting up. Best is to open the case the put a fan in there to cool the SoM. There were rare cases when people got stuck in a boot loop that they could not get out of... long story.

First try a reset to defaults from the Android... clean everything, take the microsd cards out, clear the internal storage... start clean...

If it still does not work try to flash an older build of android 6 that has the MCU files in the root so you can downgrade the MCU: the files being STM8_PROJECT cov.s19, STM8UD.BIN

Hope that once you downgrade to an older version of the MCU and Android 6 build your mics will come to life... also use the RESET hole, it does clear the MCU settings.
[Android Head-Units] :
[MENTION=2146025]Nightmare[ITA][/MENTION] I tried, to do this, I made factory reset, I change my smartphone ROM, and nothing. I also reflashed, and nothing. My solution was come back to september update, now the bluetooth is working.
[Android Head-Units] swanie2000:
Which version do you recommend I down grade to? I tried going back to 9-1-2017, then 7-5-2017. Neither of them re-flashed the MCU, and I couldn't find the files you mentioned back in "all you need to know" #46. I guess the next one back is 5-25-2017. I will go have a look for those files you mentioned.

I have done the cooling mod, I have an 80x80mm fan on the top lid with a hundred holes in it, and also dedicated heat sinks glued to the heat spreader with artic silver epoxy. Fan is wired to the "amp" turn on wire, so it can be controlled via the radio interface.

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

Just to update this problem...

I was able to downgrade the MCU by using the 4 files [MENTION=309187]edit[/MENTION] mentioned from the 5-25-2017 firmware.

Downgrade went smooth, and it did not even loose my current radio setups, just flashed the MCU, and rebooted, all is good.

EXCEPT, my microphones are still not working. Next weekend, I will tear it apart and verify if the microphones work or not on another device. Not sure, at this point, what has happened. Maybe one of them shorted out, and because both are in parallel, shorting out one, will short out the other at the same time. While I am in there, I think it will be a good time to separate the two microphones.