Capacitive SC GPS Navi Android 4.4 2
I was recommended by the vendor to do a system update to 4.4.4 and to update the MCU aswell. He provided the files. After I updated the MCU I immediately lost all audio. I cannot hear music, cannot hear GPS, cannot hear DVD's. Adjusting volume does nothing. I disconnected the head unit from power to reset it but did not help. I then performed a factory reset and to my surprise this also did not help.
What happened and how can I fix?
Need4Camaro said:
Capacitive SC GPS Navi Android 4.4 2
I was recommended by the vendor to do a system update to 4.4.4 and to update the MCU aswell. He provided the files. After I updated the MCU I immediately lost all audio. I cannot hear music, cannot hear GPS, cannot hear DVD's. Adjusting volume does nothing. I disconnected the head unit from power to reset it but did not help. I then performed a factory reset and to my surprise this also did not help.
What happened and how can I fix?
Click to expand...
Click to collapse
Have you tried wiping the dalvik cache partition?
did you play with the unit Hardware ? because it happen to me and I forgot to connect one of the cables. so you check that.
also if you are sure 100% that the problem from Software , so try the following:
1) Go to Bluetooth and connect your phone and make call check the sound is it working or not.
2) Go to Factory settings and check every option carefully try to play with it.
3) Last solution try to find the Original MCU ( maybe by contact the manufacturing ) or try to find MCU version that is 100% compatible with yours.
Related
Hi!
After the latest Marshmallow Update 6.0.1 I'm facing some sound related problems. My phone doesn't recognize the headphone/earphones when connected.
During calls, when I plug the conector, the icon of headphone doesn't appear in the upper side and the sound still being release from speakers.
After some google research, several users of several phone brands reported the same issue. I installed SoundAbout app to test and worked fine, except for the calls.
I'm using official stock ROM and tried to several reboots, wipe cache, factory reset and nothing happened.
Could someone please help me?
Thanks and regards!
And the saga continues...
UPDATE:
- Rolled back to firmware 5.0 and the issue continues.
- Forced new update through OTA, issue still happening.
I have a guess that this new firmware update changed the headphone/earphone hardware driver, so even with several actions the problem wasn't fixed.
syneval said:
UPDATE:
- Rolled back to firmware 5.0 and the issue continues.
- Forced new update through OTA, issue still happening.
I have a guess that this new firmware update changed the headphone/earphone hardware driver, so even with several actions the problem wasn't fixed.
Click to expand...
Click to collapse
Try a full wipe
Dramane Traoré said:
Try a full wipe
Click to expand...
Click to collapse
Thanks for the reply!
I've already done it.
Factory reset; wipe data; wipe cache partition.
I don't know what else I can do...
Any news?
Hey guys... Any news?
Even in safe mode, Android doesnt recognize the earphone/headphone connected...
I downgraded version, updated through OTA... updated all security patches and nothing...
Your hardware is probably broken, you should try replacing connector in the phone,
I've had similar issues. headphones work but the wired remote controls don't and the sound is like its under water. Music is all messed up like it's being really heavily processed. through the speaker it's fine. Calls and music are all the same through headphones. Tried different headphones!
Stock Marshmallow firmware, tried re-flash and factory default.
wielku said:
Your hardware is probably broken, you should try replacing connector in the phone,
Click to expand...
Click to collapse
I tested with different earphones/headphones... and the same problem happened. At first, I thought it could be an hardware problem... but with SoundAbout I could use the phones to listen music... now the problem is only with the mic.
Change the audio connector is not an option, since its too risky opening the board and it will make me lose the "water protection" not talking about the costs...
I'm still thinking it's a software problem, Today I'll try to perform a clean re-flash the marshmallow firmware factory dfault and see what happens...
Hello,
Coming from the CRAP build on my 955FD. The new CRB7 build is causing my car Bluetooth to suddenly stop and then resume audio but with a significant delay. It did not do this in CRAP. I am rooted and am looking for any way to fix this issue. Everything else works. I tried to downgrade but I believe we cannot downgrade galaxy phone anymore (odin stuck). Any advice would be very helpful.
What about try freshly pair your phone with car ?
Also try delete cache from stock recovery (or twrp, base on what rec. you have)
qpkqkma said:
What about try freshly pair your phone with car ?
Also try delete cache from stock recovery (or twrp, base on what rec. you have)
Click to expand...
Click to collapse
Actually formatted my cars head unit and re added the phone. Deleting the cache doesn't help either.
Because I came from ZRA5 to CRB7 with no_wipe , and I dont have any problems with car BT audio.
I dont think anyone will have other response than backup your data and do a factory reset :/
Well atleast it pairs, i cant connect to bt earbuds at all. Tried with a set of a friend aswell and the result was the same.
Atleast my usb c earbuds are finally working properly.
Actually found out my radar was causing the issue with bluetooth delay. Weird.
Hello, i'm having trouble with my Joying JY-VL-131N2 Intel Sofia 2gb for Volkswagen.
Couple of months ago i installed SuperSU on Android 5 and some months later i updated to Android 6.0.1 september update.
I also used hvdwolfs Joying Extra Tools app to install the Sofia Server Mod so my Tasker is up and running automatic on every ignition.
All went well for some months but sometimes the standard video player has freezes from time to time and my music clips stored on usb stick were halting for some seconds and then continued playing.
I decided to update Joying Extra Tools to latest version (50) and look if there maybe is an updated SofiaServer Mod. I thought it must have to do something with that because after every fresh reboot it plays nice as it should. I installed the Mod again and then unfortunatly i tried to change the Joying Settings to Standard Android Settings via the Extra Tools app. But the installation of settings.apk hangs so i rebooted.
After that the mcu had some strange behavior. The volume rocker sign at notification bar was gone and i couldn't use my steering wheel keys.
Also the storage seems broken or so. I were not able to access files on usb.
First i tried factory reset and the device boots up with standard settings but problems still persists.
Then i put the update files from sept. 1. - 6.0.1 on fat32 stick but update failed.
On reboot it was stuck at command line and shows...
"E:usb volume for path [/mnt/usb_storage/5009_60.zip]
cannot unzip update file!
Error wait here..."
After some minutes the mcu reboots and same odd android with faults is up.
It seems something in android system is broken. I managed to use my phones hotspot to get wifi and downloaded / installed Joying Extra Tools.apk. The device still seems to be rooted but i'm stuck at this point now.
Also under device info it doesn't show anything other then "Unknown" for example the MCU Version...
Can someone figure out what i did to my mcu and how to fix this?
Greetz
gdre
try to flash stock rom from other usb stick
I tried different USB Sticks and SD Cards but still the same with canot unzip error.
Maybe i'll give TWRP and GTX Rom a try.
try to flash this one.. if android doesn't boot completly just flash standard rom afterwards.
Help out someone else with same issue
Ok so i did unrar the 2 files on root of usb but nothing happened after connecting. then i copied whole stock 6.0.1 files on usb root but replaced Allapp.pkg and 5009_60.zip from your archiv.
It flashed! But then i got stuck at command line (see picture)... waited couple of minutes nothing happened.
Then i copied/overwrote back the 2 files (Allapp.pkg and 5009_60.zip) from stock update.
The HU bootet up to faulty android. I flashed the stock update but i got same error as described in first post.
"E:usb volume for path [/mnt/usb_storage/5009_60.zip]
cannot unzip update file!
Error wait here..."
The "Error wait here..." message appears after i got back in the car and turned ignition on.
Did i made some mistake?
gdre said:
Ok so i did unrar the 2 files on root of usb but nothing happened after connecting. then i copied whole stock 6.0.1 files on usb root but replaced Allapp.pkg and 5009_60.zip from your archiv.
It flashed! But then i got stuck at command line (see picture)... waited couple of minutes nothing happened.
Then i copied/overwrote back the 2 files (Allapp.pkg and 5009_60.zip) from stock update.
The HU bootet up to faulty android. I flashed the stock update but i got same error as described in first post.
"E:usb volume for path [/mnt/usb_storage/5009_60.zip]
cannot unzip update file!
Error wait here..."
The "Error wait here..." message appears after i got back in the car and turned ignition on.
Did i made some mistake?
Click to expand...
Click to collapse
What MCU version do you have.. ? Did you flash from stock recovery?.. try to flash latest official rom. See my signature for rom.
D3LTA said:
What MCU version do you have.. ? Did you flash from stock recovery?.. try to flash latest official rom. See my signature for rom.
Click to expand...
Click to collapse
The Problem ist i can't determine the MCU Version because its shown as Unknown Device under Settings.
Ok i need more advice i think... how can i boot into stock recovery? I put the files on usb stick, plugged in an wait until update massage appeared.
Did you mean i should flash the 2 files from testkeys.zip direkt with stock recovery?
so for now i will try to use an app like quick reboot to enter stock recovery.
otherwise please tell me exactly what i have to do
No worries we gonna fix this
Ok thank you I'm hopefull
Now i installed Quick Reboot app and let the app boot into recovery mode.
But when it reboots i got command line with something like sofia6.0! error wait here...
so it seems i even can't enter recovery mode
Can you flash TWRP recovery from within the custom.apk ? Is so you can then flash GTX ROM and update mcu from within car settings app (MCU files are in the rom)
In the gtx thread there is some info in description
"Due to Bluetooth, WiFi, and as well as nvram patches in the ROM and bootloader, you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM."
but i'm on earlier update so i don't know which is the last gtx version i could use.
i have sent gtxaspec a private message couple of days ago but no answer still.
i will try to install twrp first. i think when that works it could take in the right direction
i managed to install custom.apk. i had to access usb stick over root explorer from playstore because the stock filemanager won't let me access storage.
when i choose install custom recovery from custom.apk i get the message that i'm on the wrong update as i mentioned before
i think i maybe need an older version of custom.apk? hopefully then i'm able to install twrp that suits my current update version...
sadly in the mainthred the older versions if there any exists are not provided.
gdre said:
i managed to install custom.apk. i had to access usb stick over root explorer from playstore because the stock filemanager won't let me access storage.
when i choose install custom recovery from custom.apk i get the message that i'm on the wrong update as i mentioned before
i think i maybe need an older version of custom.apk? hopefully then i'm able to install twrp that suits my current update version...
sadly in the mainthred the older versions if there any exists are not provided.
Click to expand...
Click to collapse
Didn't see your message(sorry I get a lot)....
Update to the latest joying Intel room, listed in my thread under Q and A, then you should be able to install my ROM. ?
Don't attempt install on old firmware, it causes issues with the bootloader and if difficult to fix. Follow all directions I'm my thread.
We have to start completely fresh here. If you started from a ROM earlier than October, your current MCU version is < 9.20.
The errors you get ("can't verify ..5009_60.zip") is due to incorrect signing and mixing all kind of ROMs and files and probably the TWRP recovery image. That will definitely not work.
Download/Use the latest ROM (2018-1-26; see below in blue) from here. (From this Joying blog https://www.joyingauto.com/blog/category/updated-files-released/)
Code:
Below updated files is (2018-1-26) version . please check :
Updated files for HD resolution 1024*600 :
MCU version is 9.20 or more later please click Here
[COLOR="Blue"] MCU version is 5.25 or more earlier please click Here[/COLOR]
If you flashed the TWRP recovery from the custom.apk then first write the stock recovery back.
Before trying to flash remove all SD-cards and usb-sticks from the unit and reboot with the usb-stick (or sd-card) with the complete unzipped ROM. Do not alter anything on this downloaded ROM.
Please try to flash that first. Then we see if it works or what error message we get. Do not try all kind of things with the TWRP/gtx ROM before your firmware and MCU firmware is correct.
If this doesn't work then we use the reset method: Use the same usb stick and use a "pointy thing" (needle or so) to reset your unit. Do this 3 times (reset immediately when you see the logo coming). Then the unit's leds will cycle purple/pink a few times and reboot the unit again perhaps 3 times and will then (hopefully) start the flash of the ROM. The pink/purple flashing/reboot can take 10 minutes: Have patience.
Maybe @gtxaspec has a few hints here as well.
Edit: and now @gtxaspec's post and mine are crossing.
旧FYT SOFIA 1024x600 did the trick!
Now i think about flashing twrp and gtxrom
some problem left is my steering wheel control. i can't really remember but i think the profile was rcz_vw_low or something like that.
back then when i purchased the HU, steering wheel control works out of the box. with rcz_vw_l mode the buttons response but volume up and down only response repetitive.
before the update i was able to press and hold the button and the volume was increasing or decreasing without having to press again and again.
is this a problem with maybe wrong profile or some setting i missed?
other thing is i don't see setting for deactivating button/touch beep. before the update it was under car settings t think.
but first at all i'm happy and relieved that the HU is working.
thank you both for your help!
gdre said:
旧FYT SOFIA 1024x600 did the trick!
Now i think about flashing twrp and gtxrom
some problem left is my steering wheel control. i can't really remember but i think the profile was rcz_vw_low or something like that.
Click to expand...
Click to collapse
Nice to hear.
Try the RZC.XP(L)-VolkswagenALL
surfer63 said:
Nice to hear.
Try the RZC.XP(L)-VolkswagenALL
Click to expand...
Click to collapse
That worked!
and the volume increase decrease is working too... sometimes i'm a little bit dump ... i had to press quiet a bit longer then the volume goes up or down when i press and hold up or down key at steering wheel. it seems there is a slightly more delay since the update.
only thing that is annoying is the button/touch beep. there is no option to turn it of... maybe i can get root to find and change / rename the soundfile?
any suggestions?
Ok i figured out the annoying beep thing. In car settings you have to switch to no amp then under sound settings tab the beep can be disabled.
as long as an active amp is choosen the option for beep is gone.
Hope that could help someone.
Hi all, recently radio has stopped working on mtce head unit doesn't want to scan. I have tried factory reset, flashing alternate roms and trying a few mcu. It is a xcr2 and currently android 9. I have also tried disabling and re-enabling radio and changing from Australia to China and back again. Also checked cables are secure in head unit. Stating to suspect something hardware has failed, is there any other suggestions I might try.
Sounds like a hardware issue
Edit:
I finally solved it, so in case anyone else has the same issue, here it goes.
Hi. If you still cannot downgrade, I have a solution that worked for me.
Look on the head unit harness for a cable that is marked Key 1.
With the radio off, put a flash drive with your update file in the required folder. Connect that Key 1 cable to ground in your car, turn on your radio and reset your radio (mine has a reset pinhole). When the radio restarts, it will force flash the firmware. After flashing, remove the ground connection and the flash drive.
Original post:
So, against my better judgement, I decided to update my TS18.1.1 head unit to TS18.2.2 firmware by modifying the file names, which worked, and almost everything worked properly, but now whenever I start listening to radio stations, a different music app like Pandora will start on it's own playing music. I have reset and reinstalled everything like four times already and have not found a solution so I guess my only option is to go back to T18.1.1 firmware.
The problem is that after renaming TS18.1.1 software and trying to install, the head unit reboots, starts installation and stops. The radio reboots and the firmware is not installed.
The 2.2 firmware is from February 2023 and the 1.1 is from December 2022. Maybe this is why I can't roll back.
So my question is, is there any way of forcing the older firmware into the radio? Or will I have to wait inter a newer 1.1 firmware, if it's ever released to go back?
Hi, if you have root access and seeing all folders on mounted device disk, delete folder named "cache" if you have it. then restart and see if helps, and try to update system again with ver. 2
Anton TNT said:
Hi, if you have root access and seeing all folders on mounted device disk, delete folder named "cache" if you have it. then restart and see if helps, and try to update system again with ver. 2
Click to expand...
Click to collapse
Thanks for the suggestion but I do not have root. Still, I did find the solution.