Hello,
I have CarLink version 2.23.0228.0844 installed on my OledPro head unit.
If I use CarPlay via CarLink, when making or receive calls, the sound suddenly get very loud after 1-2 beeps. And the whole call was very noisy. I believe the problem is from CarLink, as the sound is still normal if I call over the default Bluetooth connection of the head unit.
I tried searching every solution with CarLink but no luck.
Has anyone had the similar problem?
vitdaika said:
Hello,
I have CarLink version 2.23.0228.0844 installed on my OledPro head unit.
If I use CarPlay via CarLink, when making or receive calls, the sound suddenly get very loud after 1-2 beeps. And the whole call was very noisy. I believe the problem is from CarLink, as the sound is still normal if I call over the default Bluetooth connection of the head unit.
I tried searching every solution with CarLink but no luck.
Has anyone had the similar problem?
Click to expand...
Click to collapse
Not familiar with your unit, Mine, carlink Uses Wi-Fi for everything but phone, it uses Bluetooth You might be able to use a config,txt file to correct volume levels and bluetooth version.
you'll need fat32 formatted sd card with the "Isec6315update" out of the full update zip and a config.txt with this on it.
#test
ro.fyt.launcher=com.android.launcher4
ro.fyt.amp_type=0
sys.fyt.bluetooth_type=0
persist.sys.zlink.mic.vol=9.9
sys.fyt.ec_version=6
03hdfatboy said:
Not familiar with your unit, Mine, carlink Uses Wi-Fi for everything but phone, it uses Bluetooth You might be able to use a config,txt file to correct volume levels and bluetooth version.
you'll need fat32 formatted sd card with the "Isec6315update" out of the full update zip and a config.txt with this on it.
#test
ro.fyt.launcher=com.android.launcher4
ro.fyt.amp_type=0
sys.fyt.bluetooth_type=0
persist.sys.zlink.mic.vol=9.9
sys.fyt.ec_version=6
Click to expand...
Click to collapse
Thanks bro,
Where can I find the “lsec6315update”?
vitdaika said:
Thanks bro,
Where can I find the “lsec6315update”?
Click to expand...
Click to collapse
check inbox
vitdaika said:
Hello,
I have CarLink version 2.23.0228.0844 installed on my OledPro head unit.
If I use CarPlay via CarLink, when making or receive calls, the sound suddenly get very loud after 1-2 beeps. And the whole call was very noisy. I believe the problem is from CarLink, as the sound is still normal if I call over the default Bluetooth connection of the head unit.
I tried searching every solution with CarLink but no luck.
Has anyone had the similar problem?
Click to expand...
Click to collapse
Is it an FYT unit, post Android system information including MCU version
marchnz said:
Is it an FYT unit, post Android system information including MCU version
Click to expand...
Click to collapse
Yes. It's a OledPro 12.3 Android head unit.
Android version: 10
Build Number: QP1A. 190711.020 release-keys
System Info: APP 1920×720 2023-03-04 15:37:04
CPU: UIS7862 Octa-Core [email protected] GB(Memory) + 32 GB(Storage)
MCU Version: 2021.10.09 10:12:29 YIN_53_L6315_G23P48F64_E60_V:1.0
vitdaika said:
Yes. It's a OledPro 12.3 Android head unit.
Android version: 10
Build Number: QP1A. 190711.020 release-keys
System Info: APP 1920×720 2023-03-04 15:37:04
CPU: UIS7862 Octa-Core [email protected] GB(Memory) + 32 GB(Storage)
MCU Version: 2021.10.09 10:12:29 YIN_53_L6315_G23P48F64_E60_V:1.0
Click to expand...
Click to collapse
Being an Oledpro, where I have never heard off, doesn't tell us it's a FYT.
We can only derive from your MCU that it is a YIN type FYT with manufacturer code 53.
And CarLink is a reverse engineered piece of software to mimic the Android Auto layer in OEM units as good as possible.
Anyway, just like @03hdfatboy already mentioned: As far as I know also under Android Auto the BT connection is used for phone calls.
What might be an option to check is if your phone is set to "use WiFi for phone calls" and try to switch that on/off.
surfer63 said:
Being an Oledpro, where I have never heard off, doesn't tell us it's a FYT.
We can only derive from your MCU that it is a YIN type FYT with manufacturer code 53.
And CarLink is a reverse engineered piece of software to mimic the Android Auto layer in OEM units as good as possible.
Anyway, just like @03hdfatboy already mentioned: As far as I know also under Android Auto the BT connection is used for phone calls.
What might be an option to check is if your phone is set to "use WiFi for phone calls" and try to switch that on/off.
Click to expand...
Click to collapse
I think OledPro is a new 12,3 inch Android unit in Vietnamese market, since 2022.
As your suggestion, I tried to switch mode of "Call over WiFi" to On then Off on my iPhone 14 Pro, but it doesn't solve the problem.
I backed up the system using your guide post, and forgot the line "don't backup 360 camera". After backed-up, I modified the config.txt with the lsec6315update, and have successfully applied the config.txt, now the sound becomes a little bit better.
But, the system swiped my Camera 360 app. Is there a Camera 360 apk file to re-install it?
surfer63 said:
Being an Oledpro, where I have never heard off, doesn't tell us it's a FYT.
Click to expand...
Click to collapse
please see it installed on my Toyota Corolla Cross 2022
vitdaika said:
But, the system swiped my Camera 360 app. Is there a Camera 360 apk file to re-install it?
Click to expand...
Click to collapse
So far my backup script did not backup the 360 camera part as the script crashed on units without it.
I will now simply create two scripts: one for 360 camera and one for units without 360 camera.
In the mean time I wrote a script that should (re)install the 360 camera software.
For others: It will install the software, but it will of course only work if your unit really has the (hardware) 360-camera chip installed.
Please try the script: 360_installer.zip and let me know if it works.
As usual: unzip to a clean USB-stick and flash it.
surfer63 said:
So far my backup script did not backup the 360 camera part as the script crashed on units without it.
I will now simply create two scripts: one for 360 camera and one for units without 360 camera.
Click to expand...
Click to collapse
Just did that and added them to post #4 of the "General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware" forum thread.
surfer63 said:
So far my backup script did not backup the 360 camera part as the script crashed on units without it.
I will now simply create two scripts: one for 360 camera and one for units without 360 camera.
In the mean time I wrote a script that should (re)install the 360 camera software.
For others: It will install the software, but it will of course only work if your unit really has the (hardware) 360-camera chip installed.
Please try the script: 360_installer.zip and let me know if it works.
As usual: unzip to a clean USB-stick and flash it.
Click to expand...
Click to collapse
It does not work
vitdaika said:
It does not work
Click to expand...
Click to collapse
Strange. The apk should simply be on your system and this script only restores the 360res folder and contents.
My system does not have the 360 configuration so I can't check.
Someone else here with a 360 system and more knowledge about it?
Hello, I have a CPU unit: UMS512S MCU 2022.07.08 the problem concerns I can't find anywhere to increase the sensitivity of the microphone conversation via carlik 2.0 version 2.22.0714.0919 and via BT the voice is hard to hear can anyone help me?
Same problem….
To prevent fragmented info I will answer your cross-posted question here:
What helps a tiny bit is to add the following lines to a config.txt:
Code:
persist.sys.zlink.mic.vol=9.9
persist.audio.mic.senstivity=1
persist.btmic.gain=10
persist.btspk.gain=7
Simply put that config.txt and an lsec7862update for a uis7862, or an lsec6316update for a sui8581a, on a blank usb-stick and flash it.
As said: this only helps a little bit. It is just that the internal microsophone sucks. (like I already mentioned in another topic by you where you asked exactly the same).
Also @louforgiveno mentioned above solution a few days ago in a post.
surfer63 said:
To prevent fragmented info I will answer your cross-posted question here:
What helps a tiny bit is to add the following lines to a config.txt:
Code:
persist.sys.zlink.mic.vol=9.9
persist.audio.mic.senstivity=1
persist.btmic.gain=10
persist.btspk.gain=7
Simply put that config.txt and an lsec7862update for a uis7862, or an lsec6316update for a sui8581a, on a blank usb-stick and flash it.
As said: this only helps a little bit. It is just that the internal microsophone sucks. (like I already mentioned in another topic by you where you asked exactly the same).
Also @louforgiveno mentioned above solution a few days ago in a post.
Click to expand...
Click to collapse
#callquality
ro.fyt.amp_type=0
sys.fyt.bluetooth_type=0
persist.sys.zlink.mic.vol=9.9
persist.btmic.gain=10
persist.btspk.gain=7[
persist.audio.mic.senstivity=1
sys.fyt.ec_version=6
Would it be enough for me to add these codes?
thericksizzler said:
#callquality
ro.fyt.amp_type=0
sys.fyt.bluetooth_type=0
persist.sys.zlink.mic.vol=9.9
persist.btmic.gain=10
persist.btspk.gain=7[
persist.audio.mic.senstivity=1
sys.fyt.ec_version=6
Would it be enough for me to add these codes?
Click to expand...
Click to collapse
Yes, but the bottom line (ec_version) is not needed.
surfer63 said:
Yes, but the bottom line (ec_version) is not needed.
Click to expand...
Click to collapse
I did as you said and changed the config file. but there is no change. I haven't tried it on bluetooth, I just tried it on carplay. the caller's voice is very scratchy. as if the speakers were blown. In my previous tests, the sound in bluetooth was better than carplay, but still not very good.
as a result the config settings did not make any changes.
thericksizzler said:
as a result the config settings did not make any changes.
Click to expand...
Click to collapse
They did make a change if you check your properties.
But I already mentioned that it would be a very minor improvement. It is going from terrible to slightly less terrible.
Related
I made some changes in /system/etc/bluetooth/audio.conf that could improve the connection with cars or bluetooth headsets.
I didn't test it, I never use bluetooth. I think the only times I turned it on was by accident. This is not a real fix, but in many cases it solved the problem (it's a common issue among android phones).
The file changed is /system/etc/bluetooth/audio.conf. Extract the flashable zip to see the changes.
Let me know if these changes make your connection more stable.
Here the flashable zip:
http://www.mediafire.com/?xwqn5q2zrsn7qvj
Here a flashable zip to restore the original file:
http://www.mediafire.com/?vd5pxkcr10s2v91
It's not rom specific, you can use it on any stock rom.
Where you find this tweak?
gud work ! i've never had this issue but i hope this fixes the issue for the others !
Namaless said:
Where you find this tweak?
Click to expand...
Click to collapse
I found references to that file by accident, I did some research and found that some changes could improve the bluetooth connection.
Probably I need to do some more changes, but I need some user feedback, because I can't test it.
For example I set
Code:
master=true
but I found that this would make the connection not possible with some headsets. However this will prevent audio playback glitches.
loSconosciuto said:
I found references to that file by accident, I did some research and found that some changes could improve the bluetooth connection.
Probably I need to do some more changes, but I need some user feedback, because I can't test it.
For example I set
Code:
master=true
but I found that this would make the connection not possible with some headsets. However this will prevent audio playback glitches.
Click to expand...
Click to collapse
I have requested because my friend with gb have problem with car audio bt.. thanks.. check this
Hi, could these tweaks help solving this problem?
Namaless said:
I have requested because my friend with gb have problem with car audio bt.. thanks.. check this
Click to expand...
Click to collapse
I'll be shamelessly pointing to my kernel, now: Try this. I fixed a bluetooth bug for the user simbita in beta 12. He had problems with his car audio system before and reported them to be fixed with this release. Beta 13 should work equally fine.
DaiTeM said:
Hi, could these tweaks help solving this problem?
Click to expand...
Click to collapse
Maybe. Try it!
XDA_Bam said:
I'll be shamelessly pointing to my kernel, now: Try this. I fixed a bluetooth bug for the user simbita in beta 12. He had problems with his car audio system before and reported them to be fixed with this release. Beta 13 should work equally fine.
Maybe. Try it!
Click to expand...
Click to collapse
Nope :/ maybe it made my situation worse (my headset isn't auto-connecting). Gotta do more testing
PS: XDA_Bam, you got a new dmesg via PM! Feel free to share it if helpful
EDIT: confirm, after flashing this mod my headset isn't autoconnecting anymore. Gotta revert to old one.
DaiTeM said:
Nope :/ maybe it made my situation worse (my headset isn't auto-connecting). Gotta do more testing
PS: XDA_Bam, you got a new dmesg via PM! Feel free to share it if helpful
EDIT: confirm, after flashing this mod my headset isn't autoconnecting anymore. Gotta revert to old one.
Click to expand...
Click to collapse
Read the 4th message
Try this if you want: http://www.mediafire.com/?tdyvub5a2amqrus
I let this thread silently disappear because XDA_Bam fixed bluetooth and no one gave any feedback (I opened this thread two days before his fix)
Edit:
Anyway I think this .conf file will not fix your problem.
loSconosciuto said:
Read the 4th message
Try this if you want: http://www.mediafire.com/?tdyvub5a2amqrus
I let this thread silently disappear because XDA_Bam fixed bluetooth and no one gave any feedback (I opened this thread two days before his fix)
Edit:
Anyway I think this .conf file will not fix your problem.
Click to expand...
Click to collapse
Hi, thanks for your reply. I read all messages before posting, so I was aware of the incompatibility...I flashed your second fix but the headset still doesn't autoconnect. Reverted to stock one FTM (and it auto-connects flawlessly)
BTW, my main problem (the one that we're trying to solve with XDA_Bam) persists: "long press on headset doesn't do/trigger anything, instead of starting/trying to start some voice dialing app, like normal android behaviour". I think it's Samsung's bluetooth implementation/framework/stack/kernel/software fault (on JP-MIUI, it worked flawlessly). EDIT: exaclty, didn't fix anything...just another try
My conf: i9003, CleanKPURom 1.5, XDA_Bam kernel b13, Jabra EasyGO headset (that works perfectly on other phones).
Hey,
Does anybody know how to send data to the MFD (Multi Function Display)? I have a Corsa D. I get a "Welcome!!!" when it starts up.
I've tried decompiling a few apps (MTCCanbus, PCRadio) to see how they do it but it's pretty convoluted since you don't get the original variables and class names when decompiling.
Edit:
Just adding some useful resources to help me in my endeavors.
https://forum.xda-developers.com/showpost.php?p=71324770&postcount=7
https://github.com/xbenjii/mtccanbus-decompiled
I think someone may have done it in the very similar MTCB/C headuntis a few years back. You would also have to know all the code for your car's CAN Bus system as well I think
typos1 said:
I think someone may have done it in the very similar MTCB/C headuntis a few years back. You would also have to know all the code for your car's CAN Bus system as well I think
Click to expand...
Click to collapse
The bluetooth audio player already tells the MFD that it's playing through bluetooth, but I wanted a way to send the actual song/artist info to the MFD.
xbenjii said:
The bluetooth audio player already tells the MFD that it's playing through bluetooth, but I wanted a way to send the actual song/artist info to the MFD.
Click to expand...
Click to collapse
Yes, but my post still applies.
typos1 said:
Yes, but my post still applies.
Click to expand...
Click to collapse
Sorry, my point was that the code exists somewhere on one of the system apps in the rom. I've decompiled a few but couldn't find anything useful. I was just wondering if anyone knew a starting point.
xbenjii said:
Sorry, my point was that the code exists somewhere on one of the system apps in the rom. I've decompiled a few but couldn't find anything useful. I was just wondering if anyone knew a starting point.
Click to expand...
Click to collapse
Yes, it exists, but you need to find it and work out how to make it say what you want, I think it has been done to some extent for VWs, but I cant remember where, so youve got 3 years of MTCB forum to search through including the massive megathread that existed for 18 months before we got our own forum.
https://youtu.be/0sF8DlbRu-g
interesting...
I have a Astra H GTC ... same problem...
kaderekusen said:
https://youtu.be/0sF8DlbRu-g
Click to expand...
Click to collapse
I don't understand what I'm watching here. What does this have to do with the OP?
xbenjiiman said:
I don't understand what I'm watching here. What does this have to do with the OP?
Click to expand...
Click to collapse
Yeah, I dont get it either.
Just what I needed: https://forum.xda-developers.com/showpost.php?p=61202146&postcount=13705
Sure. In MTCMusic, you'd override the SendCanbusinfo(int, int) method in com.microntek.music/MusicActivity to broadcast the com.microntek.canbusdisplay intent action with extra time set to something other than the current playing time.
Of course this would only work for MTCMusic. If you wanted to use a 3rd-party media player, you could construct the same broadcast intent and pass the same info.
Click to expand...
Click to collapse
xbenjiiman said:
Just what I needed: https://forum.xda-developers.com/showpost.php?p=61202146&postcount=13705
Click to expand...
Click to collapse
You got success??
See your picture of the TID saying "capital"...
sousa_2005 said:
You got success??
See your picture of the TID saying "capital"...
Click to expand...
Click to collapse
I've managed to read the data that is being sent, so I'm going to have a play around with it today.
any update?
hello.
i have read and search for hours about "sending data to MFD" but im finaly not found what im lookink for.
my car is a Seat exeo/audi A4 b6
hu is xtrons PB78AA4P (gs) mit @Malaysk Rom android 8
i'am looking for the folders "com.microntek.music/MusicActivity" but i cant find them on my device. (i have searched in every folder)
how can i access this feature?
i want to write a feature to make a "custom welcome message" on the MFD and the next feature is to show the title of the current track is played instead of the playtime.
should i use xposed or make them with an .apk?
Following this.Also the radio RDS station name to be displayed on the MFD will be a great feature.Mine display only the station frequency on MFD display.( VW Passat )
At the beginning:
Flash/Upload modified MCU firmware can brick unit !!!! (in particular from an unknown source, untested etc.)
Maybe this thread will not only affect the modification of the MCU firmware.
I hope that this will help us understand the functioning of the MCU software, get to know bugs, new features and maybe even tricks.
So, if anyone finds something (any functions names, permanent tables), please share with us
MCU firmware was compiled using Keil and uses library (most likely these versions):
STM32F0xx_HAL_Driver 1.3.1 from STM32Cube_FW_F0_V1.5.0
FreeRTOS V8.2.1
What we need:
Tool to decode/encode MCU firmware from here:
mtcdmcutool.zip
The Interactive Disassembler
Useful additions for IDA from here:
MTCDida.zip
(copy appropriate folders to IDA directory)
Short explanation how to do:
Decode MCU firmware:
Code:
mtcdmcutool.exe -d dmcu.img decodedDMCU.img
Open decodedDMCU.img in IDA. IDA should ask with wich loader to load the binary file:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Of course, we choose "Android auto MTCD/E MCU firmware"
After a while, we should see:
other disassembled examples:
We can also load HAL/FreeRTOS structures/enums(script: MyScripts\MTCDLibStructsEnums.idc) and disassembled structures/enums (script: MyScripts\MTCDLFuncStructsEnums.idc)
Analyze, analyze, analyze and at the end patch the firmware
Encode MCU modified firmware:
Code:
mtcdmcutool.exe -e decodedDMCU.img modifiedDMCU.img
Flash/Upload to the unit (according to the standard uploading procedure dmcu.img)
Remarks:
if anyone know more HCT_CMD constants/names (MTCDFuncStructsEnums.idc) share with us
if someone disassembles meaning of fields from structures (MTCDFuncStructsEnums.idc) share with us
if someone disassembles meaning new functions please share
signatures was prepared based on GS_V2.72, but I tested on other versions and most functions was recognized
Excellent thread and very useful information. I can help map GPIOs to actual MCU pins from the schematic if that helps?
marchnz said:
Excellent thread and very useful information. I can help map GPIOs to actual MCU pins from the schematic if that helps?
Click to expand...
Click to collapse
Any help will be appreciated
Are you planning on releasing MCU firmware updates yourself? Or just gathering info so people can modify their own firmware?
I've got a unit for my Opel Astra J and the default buttons in the car don't work correctly. I would love to be able to modify their CANBUS decoding... Would that be possible through the MCU?
ThirtyOne34 said:
Are you planning on releasing MCU firmware updates yourself? Or just gathering info so people can modify their own firmware?
Click to expand...
Click to collapse
More to collect information for others. It would be nice if others would also share what they were modified.
I've got a unit for my Opel Astra J and the default buttons in the car don't work correctly. I would love to be able to modify their CANBUS decoding... Would that be possible through the MCU?
Click to expand...
Click to collapse
For my knowledge as of today MCU only translates messages from CANBUS into messages known for Android. While msgs from CAN bus are (these necessary) recognized/filtered in the CanBox. So if your CanBox does not send the right messages, MCU modification will not help. BTW: did you try Opel/Mazda Raise, Opel/Mazda Simple in factory settings? I've got version H and only these two settings work. For SteringWheel of course, becasue AirConditions etc does not work
Wadzio said:
More to collect information for others. It would be nice if others would also share what they were modified.
Click to expand...
Click to collapse
Let's hope so
Wadzio said:
For my knowledge as of today MCU only translates messages from CANBUS into messages known for Android. While msgs from CAN bus are (these necessary) recognized/filtered in the CanBox. So if your CanBox does not send the right messages, MCU modification will not help.
Click to expand...
Click to collapse
Yes, that's why I thought maybe I could change the translations for Android?
Wadzio said:
BTW: did you try Opel/Mazda Raise, Opel/Mazda Simple in factory settings? I've got version H and only these two settings work. For SteringWheel of course, becasue AirConditions etc does not work
Click to expand...
Click to collapse
I tried a lot of different factory settings, but I can't remember if Opel/Mazda Raise/Simple was available... Default it was set to 55 GM Simple. I will check again, though.
Airconditioning settings do work for me. (I have got manual airco.) I can turn the knobs and it shows an MCU pop-up on screen with temperature of air, airflow force (don't know how to call this in English), which fans are used, etc.
I can't use the default media controls on my dashboard, however. Some of them work, but incorrectly. These are the buttons I can remember without going to my car:
The "home" button for example turns the unit on/off.
The "next song" button is the back button in Android.
The "tone" button is the Android home button.
Pressing the big knob is next song, pressing the back button is previous song.
"Phone" button is GPS app.
"Previous song" button is mute/unmute.
The six number keys don't do anything (as far as I know).
"Play/pause" works correctly.
Volume knob works correctly.
"Open trunk" works correctly.
Turning ESP on/off works correctly.
Turning park assist sensors on/off works correctly when putting car into reverse. Also shows sensor strength on screen and there are audible beeps. Music volume is automatically turned down a bit.
Steering wheel controls all work correctly.
ThirtyOne34 said:
I tried a lot of different factory settings, but I can't remember if Opel/Mazda Raise/Simple was available... Default it was set to 55 GM Simple. I will check again, though.
Airconditioning settings do work for me. (I have got manual airco.) I can turn the knobs and it shows an MCU pop-up on screen with temperature of air, airflow force (don't know how to call this in English), which fans are used, etc.
I can't use the default media controls on my dashboard, however. Some of them work, but incorrectly. These are the buttons I can remember without going to my car:
The "home" button for example turns the unit on/off.
The "next song" button is the back button in Android.
The "tone" button is the Android home button.
Pressing the big knob is next song, pressing the back button is previous song.
"Phone" button is GPS app.
"Previous song" button is mute/unmute.
The six number keys don't do anything (as far as I know).
"Play/pause" works correctly.
Volume knob works correctly.
"Open trunk" works correctly.
Turning ESP on/off works correctly.
Turning park assist sensors on/off works correctly when putting car into reverse. Also shows sensor strength on screen and there are audible beeps. Music volume is automatically turned down a bit.
Steering wheel controls all work correctly.
Click to expand...
Click to collapse
Have you tried other settings in FactorySettings-> CanBus (Type, KeyMode, SwapKey)? Is there any difference in the work of these buttons? Or maybe would try another firmware? HA, GS, KGL etc and see if there is any difference.
Wadzio said:
Have you tried other settings in FactorySettings-> CanBus (Type, KeyMode, SwapKey)? Is there any difference in the work of these buttons? Or maybe would try another firmware? HA, GS, KGL etc and see if there is any difference.
Click to expand...
Click to collapse
Yes, I tried all combinations of type/keymode/swapkey, but nothing changes... Very weird.
Installed HA instead of KGL yesterday, but no difference. Still have to search for Opel/Mazda Raise/Simple.
ThirtyOne34 said:
Yes, I tried all combinations of type/keymode/swapkey, but nothing changes... Very weird.
Installed HA instead of KGL yesterday, but no difference. Still have to search for Opel/Mazda Raise/Simple.
Click to expand...
Click to collapse
Forget Opel/Mazda, you'll only have the SteeringWheel as mine. GM is better choose. Maybe you should contact with your seller and ask them what you must set to. BTW: do you remember what version you have on CanBox sticker? I'm curious because when I asked my seller why I dont have AirConditions infos and he told me: because I dont have dualCAN.
Wadzio said:
Forget Opel/Mazda, you'll only have the SteeringWheel as mine. GM is better choose. Maybe you should contact with your seller and ask them what you must set to. BTW: do you remember what version you have on CanBox sticker? I'm curious because when I asked my seller why I dont have AirConditions infos and he told me: because I dont have dualCAN.
Click to expand...
Click to collapse
Oh, ok. Too bad. Contacting the seller (Seicane) didn't help, unfortunately...
This is the only picture I have of my CANBUS decoder:
https://imgur.com/AqPlrxD
why the segment "CODE" begins with 0x8004000?
Is the "options bytes" state known?
0xb0ba said:
why the segment "CODE" begins with 0x8004000?
Click to expand...
Click to collapse
0x8000000 - 0x8003FFF => Bootloader
0x8004000 - 0x80.... => Main App
Is the "options bytes" state known?
Click to expand...
Click to collapse
Readout Protection
Wadzio said:
0x8000000 - 0x8003FFF => Bootloader
Click to expand...
Click to collapse
STM bootloader are 0x1FFFD800 (system memory) on STM32F09, or it bootloader from manufactured of mcu?
STM32F09 init vector is 0x00000004 (0x00000000 for SP) its maped to 0x08000004, not 0x80004004.
Wadzio said:
Readout Protection
Click to expand...
Click to collapse
only? nothing specific?
0xb0ba said:
or it bootloader from manufactured of mcu?
Click to expand...
Click to collapse
yes, its bootloader from manufactured.
but is it possible to get it?
if I copy the table of vectors from 0x8004000 to 0x8000000 the device will start?
0xb0ba said:
yes, its bootloader from manufactured.
but is it possible to get it?
if I copy the table of vectors from 0x8004000 to 0x8000000 the device will start?
Click to expand...
Click to collapse
Yes. Bootloader from producer. Is it possible to get it? From device/mcu no beacuse Readonly Protection (other "options bytes" I didn't check). I think the only way to get the bootloader is from producer. Or write your own
If you copy table vectors from 0x8004000 to 0x8000000 device will start.
Look at: https://forum.xda-developers.com/an...uide-how-to-unlock-bricked-mcu-units-t3748646
I have prepared a tool for doing this similar thing
someone watched an android application that updates mcu? is there a protocol for reading a flash from mcu?
Is it possible to edit the code within the MCU to change temperature unit readout on the AC readout? Celsius to Fahrenheit.
I have a 10in intel sofia 3gr unit in my 2003 honda accord and have been able to do everything on it (root,custom mods, etc...) but for the life of me can not figure out how to change the temperature units. There is no option in my android settings and I've messed around with my canbus protocal which makes the temperature badge in the notification bar disappear for a second but reappears moments later unchanged.
I've tried posting on the Joying Sofia 3gr thread but I haven't been able to find a fix.
Any help would be awesome! Thank you.
Bump^^^^^
Wadzio said:
MCU firmware was compiled using Keil
What we need:
The Interactive Disassembler
signatures was prepared based on GS_V2.72
Click to expand...
Click to collapse
First of all, many thanks for your tool and info about MCU
sorry my very pour English becouse it's not my native language
I want to finding and recognize functions, but I don't know what version of IDA need (I have IDA pro 5.5 now)?
What of Keil compiler version used by MCU image compiled?
How to step by step signature creating for new finding functions?
Thanks in advance
I want to finding and recognize functions, but I don't know what version of IDA need (I have IDA pro 5.5 now)?
Click to expand...
Click to collapse
I used 7.0
What of Keil compiler version used by MCU image compiled?
Click to expand...
Click to collapse
Probably 1.3
How to step by step signature creating for new finding functions?
Click to expand...
Click to collapse
IDA SDK Flair
1. Prepare pat file contains:
Code:
1420401E0006000EFBD17047........................................ 00 0000 000C :0000 I2C_Wait20
3220401E0006000EFBD17047........................................ 00 0000 000C :0000 I2C_Wait50
1E20401E0006000EFBD17047........................................ 00 0000 000C :0000 I2C_Wait30
F3B50024012681B0254676031C4F........012231463846................ 00 0000 007E :0000 I2C_DTV_ReadByte
..B0....0026..7E..4C0228..D001202076............................ 00 0000 00CE :0000 CarTaskHandle
..B0..4D0026E87E..4C022810D0012020760121227EC902..48..........48 00 0000 00CE :0000 CarTaskHandle
..B0....00....7E..4C0228..D001202076............................ 00 0000 00DA :0000 CarTaskHandle
92B0F74F0125F87E0026F64C02280FD0A5750121A27DC902F348........F048 00 0000 00A0 :0000 CarTaskHandle
..B0....01....7E0026..4C02280FD0....0121....C902..48..........48 00 0000 00A0 :0000 CarTaskHandle
etc
2. From SDK Flair run:
sigmake.exe -a128 "Description" file.pat file.sig
zipsig.exe file.sig
I'm thinking about installing an Amazon Echo or similar into my car as an AI interface.
Question, is there an input and/app that will mute or pause any music player currently in use and let Alexa or google home talk back?
Similar to your phone pausing or muting when an incoming call or notification comes in.
Or, has anyone managed to run Alexa in their Android unit? I.E. convert their Head unit into an echo or dot etc?
I have not purchased an echo or dot yet, and I'll probably go down the line of Raspberry Pi just for the tinker inside of me.
Cheers.
why not just install the Alexa app from the play store?
you still require the echo/dot unit to run it.
Your phone or other Android unit is only the settings portal.
Alexa needs to communicate through her own hub unit
H0U5ECAT said:
you still require the echo/dot unit to run it.
Your phone or other Android unit is only the settings portal.
Alexa needs to communicate through her own hub unit
Click to expand...
Click to collapse
That's not true at all. The app has full Alexa functionality as well as being used for changing the settings on other devices. The only difference is you have to press a button to activate instead of saying Alexa
Thanks.
I'll look into it.
I've seen on line some people connecting Alexa via Bluetooth into their headunit and also connecting her into the OBD2 input.
Think I'll just take the plunge and pick one up to tinker with in the meantime
Any update on this? Anyone successful in running echo or Google home with this using Bluetooth?
Uhh, we have android head units, and the google home is the same thing as OK or Hey Google on the head unit lol, this is redundant and pointless guys.
twist said:
Uhh, we have android head units, and the google home is the same thing as OK or Hey Google on the head unit lol, this is redundant and pointless guys.
Click to expand...
Click to collapse
Agree , its pointless provided the HU works fine with google assistant, but most of the time its not! Either it crashes or hangs the system or very slow to respond!
Update?
smnrock said:
Agree , its pointless provided the HU works fine with google assistant, but most of the time its not! Either it crashes or hangs the system or very slow to respond!
Click to expand...
Click to collapse
Any luck? I love Alexa at home and would be great in car with wake word. Can you ask for directions, play music , trigger home events? I receive my head unit tomorrow.
I run alexa on my Chinese head unit, it's not perfect, but I set it to load automatically and it does respond to voice, ie no button pressing, it's faster and less processor hungry than Google assistant.
It will quite happily play and change radio channels, music, news etc and loads Google maps with my route when I say "alexa, navigate home" for example.
Only issue is, you can't run the app in auto mode so I run it with a split screen, nav on one side, alexa on the other.
Responds to my voice even with lots of road noise.
Wagawag said:
I run alexa on my Chinese head unit, it's not perfect, but I set it to load automatically and it does respond to voice, ie no button pressing, it's faster and less processor hungry than Google assistant.
It will quite happily play and change radio channels, music, news etc and loads Google maps with my route when I say "alexa, navigate home" for example.
Only issue is, you can't run the app in auto mode so I run it with a split screen, nav on one side, alexa on the other.
Responds to my voice even with lots of road noise.
Click to expand...
Click to collapse
Is it an MTCD hesdunit, post system information including MCU version.
marchnz said:
Is it an MTCD hesdunit, post system information including MCU version.
Click to expand...
Click to collapse
I have no idea what that even means, however, it's just a generic, android head unit with 2gb ram.
Wagawag said:
I have no idea what that even means, however, it's just a generic, android head unit with 2gb ram.
Click to expand...
Click to collapse
Without knowing how would you know which forum to post in?
This forum for mtcd type head units. There's loads of info if interested to find out.
Post MCU version including system information.
marchnz said:
Without knowing how would you know which forum to post in?
This forum for mtcd type head units. There's loads of info if interested to find out.
Post MCU version including system information.
Click to expand...
Click to collapse
Well I was replying to someone who asked about using alexa/Google on a car head unit... I didn't realise I would be made so unwelcome.! And as for posting info, it's not up to you to tell me what to post... a please or thank you would be nice!
Wagawag said:
Well I was replying to someone who asked about using alexa/Google on a car head unit... I didn't realise I would be made so unwelcome.! And as for posting info, it's not up to you to tell me what to post... a please or thank you would be nice!
Click to expand...
Click to collapse
Post Android system information including MCU version
Wagawag said:
Well I was replying to someone who asked about using alexa/Google on a car head unit... I didn't realise I would be made so unwelcome.! And as for posting info, it's not up to you to tell me what to post... a please or thank you would be nice!
Click to expand...
Click to collapse
On your headunit there should be a screen that has About...System... or System Info or the like. Having a screenshot of this screen can be helpful to know exactly what kind of headunit you have (i.e. manufacturer, firmware versions, Android version, etc). There are identifying details on that screen that can be helpful to others on the forum.
It helps bring context to both help requested and help provided by forum members. Plus it helps forum moderators ensure questions end up in the right forum. Basically. one could expect similar results to your experience using alexa/Google on same or similar specfication headunit. How else would anyone else know if they have same/similar headunit without that identifying screenshot of About System?
Just trying to explain why it is desirable to have the details that a screenshot of the About System can provide.
I get that, but the other user was a tad curt.
Wagawag said:
I get that, but the other user was a tad curt.
Click to expand...
Click to collapse
So it's not an MTCx type device.
Requested moderator move to Android head units forum.
Hi guys. I have no setting in my settings to activate the function of letting the soundvolume follow the speed.
I found this setting, which should do the trick? Do I need to use "0" or "1" ?
My HU is a Joying 11.6" UIS7862, 8 GB ram/ 128GB rom and the firmware (System) is 2022-08-15
If, am I right that I put two files on a fat32 usb with a config.txt as one, which has
ro.syu.env_voloffset_level=0 (or 1)
And the file:
lsec6315update
from my current firmware.
This will only update the system with the new setting and nothing else?
Thanks in advance
lr_man said:
If, am I right that I put two files on a fat32 usb with a config.txt as one, which has
ro.syu.env_voloffset_level=0 (or 1)
And the file:
lsec6315update
from my current firmware.
This will only update the system with the new setting and nothing else?
Click to expand...
Click to collapse
yes, that is right.
Thanks a lot
..
surfer63 said:
yes, that is right.
Click to expand...
Click to collapse
Tried, without luck. It doesn't seem to work when I drive and there is no new setiing in Settings-menu.
I asked Joyforwa (Amazon) - (Joying I think). They say it's not possible.. Hmmm.
Just thinking. Can it be because I don't have a CANbus. (It's installed in a Land Rover from 1972 )
lr_man said:
Tried, without luck. It doesn't seem to work when I drive and there is no new setiing in Settings-menu.
I asked Joyforwa (Amazon) - (Joying I think). They say it's not possible.. Hmmm.
Just thinking. Can it be because I don't have a CANbus. (It's installed in a Land Rover from 1972 )
Click to expand...
Click to collapse
Which value for the setting did you use?
1 to set speed dependent volume
0 to disable speed dependent volume.
And also check what the property is right now.
Either use my HWGetInfo.apk to check on the properties (and the rest)
or, from a terminal, issue the command
Code:
getprop > /storage/sdcard1/properties.txt
and check the "ro.syu.env_voloffset_level=" in the created txt file.
I do not know whether it is dependent on the CANbus, but I don't think so. I think it is determined by the GPS module. It was in the Sofia 3GR and FYT never changes a working functionality.
But the best way is to ask Joying directly.
Edit: Do you really not have in your Settings -> Sound ->
Speed Compensated Volume
The last option in Sound, in whatever translation the Chinese make of this. This should set the sound volume depending on the actual speed
surfer63 said:
Which value for the setting did you use?
1 to set speed dependent volume
0 to disable speed dependent volume.
And also check what the property is right now.
Either use my HWGetInfo.apk to check on the properties (and the rest)
or, from a terminal, issue the command
Code:
getprop > /storage/sdcard1/properties.txt
and check the "ro.syu.env_voloffset_level=" in the created txt file.
I do not know whether it is dependent on the CANbus, but I don't think so. I think it is determined by the GPS module. It was in the Sofia 3GR and FYT never changes a working functionality.
But the best way is to ask Joying directly.
Edit: Do you really not have in your Settings -> Sound ->
Speed Compensated Volume
The last option in Sound, in whatever translation the Chinese make of this. This should set the sound volume depending on the actual speed
Click to expand...
Click to collapse
Thanks again. I looked in an old HWGetinfo-file (after I made the update with the config.txt) and I see it wasn't in the old file at all. As I wrote, Joying (or who they might be) said it couldn't be done. I have now set it to "1" and will try and see if it made a difference. I have also tried with some apps that claims to change volume against speed, but without luck..
I tried with a value of "1", without any luck. I also tried several app's that are supposed to turn the volume up and down, depending on speed, but again with no luck. Can the "system" somehow be "locked" for app's to control the volume?
It would be rally nice to have this function, as my Land Rover makes a lot of "good " noise, with increasing speed..
Can someone here show me a picture of the soundsettings, where "Speed Compensated Volume" is - and if, which HU it's from. As you can see from the picture of the soundsettings in my earlier post, the setting is not to be found anywhere in my HU. I have tried to download several different firmwares for the uis7862, but cannot find any reference to ro.syu.env_voloffset_level=
I don't really know what to look for, perhaps a missing app for the function?. I really miss the feature.
Thanks again.
edit: in the "properties"file, there is a line with: [ro.syu.env_voloffset_level]: [1]
lr_man said:
Can someone here show me a picture of the soundsettings, where "Speed Compensated Volume" is - and if, which HU it's from. As you can see from the picture of the soundsettings in my earlier post, the setting is not to be found anywhere in my HU. I have tried to download several different firmwares for the uis7862, but cannot find any reference to ro.syu.env_voloffset_level=
I don't really know what to look for, perhaps a missing app for the function?. I really miss the feature.
Thanks again.
edit: in the "properties"file, there is a line with: [ro.syu.env_voloffset_level]: [1]
Click to expand...
Click to collapse
Should be under sound.
deadeye920 said:
Should be under sound.
Click to expand...
Click to collapse
Thanks, but as you can see at the picture a some posts ago, it's not in my settings. So, I would like to see a picture of a setting, where it's shown - and info about the HU. and perhaps the make and firmware.
I'm a beginner.....
lr_man said:
Thanks, but as you can see at the picture a some posts ago, it's not in my settings. So, I would like to see a picture of a setting, where it's shown - and info about the HU. and perhaps the make and firmware.
I'm a beginner.....
Click to expand...
Click to collapse
I don’t quite understand. What would a picture of the screen showing that setting be any different to what has just posted above?
Perhaps I'm not good at explaining myself. Curiosity - I have not seen an actual screenshot, where the settings are. And to confirm that my HU are different from the rest ;-) As far as I can read, all uis7862 should be the same, so I'm looking for a solution to my problem - no "speed compensated volume" setting.
lr_man said:
Perhaps I'm not good at explaining myself. Curiosity - I have not seen an actual screenshot, where the settings are. And to confirm that my HU are different from the rest ;-) As far as I can read, all uis7862 should be the same, so I'm looking for a solution to my problem - no "speed compensated volume" setting.
Click to expand...
Click to collapse
I have it on my Teyes cc3 and also had it on my EKIY t900. I’ll do a pic next time I’m at the car of my cc3
I had to get something out of the car, so here are 2 bad images of the Setting.
Device -> Sound -> Speed Compensated Volume.
Note that the setting is done in animated text. It moves from left to right.
Thanks a lot, much appeciated, both of you. Now I have seen it live ;-) Now I just have to figure out to get the setting. Maybe an update of the firmware....
The below:
ro.syu.env_ voloffset _niveau 190000000_com.syu.ms
What do you think - has the line anything to do with my problem? Is it an app, an argument or a reference to something? Can it maybe be needed for the function. I saw it at the 4pda-forum. I'm a beginner.....
lr_man said:
The below:
ro.syu.env_ voloffset _niveau 190000000_com.syu.ms
What do you think - has the line anything to do with my problem? Is it an app, an argument or a reference to something? Can it maybe be needed for the function. I saw it at the 4pda-forum. I'm a beginner.....
Click to expand...
Click to collapse
I don't think so. I did set the "Speed Compensated Volume" to off/low/medium/high, but did not see any change in properties.
And where does that line come from?
Note also that you started with "ro.syu.env_voloffset_level". Now you mention "ro.syu.env_ voloffset _niveau".
I know that you found that "ro.syu.env_voloffset_level" from a post from tyuktha on 4pda, but where is this coming from?
I made a search for something with voloffset in it and ran into this on 4pda. I have no idea if it has anything to do with it....
https://4pda.to/forum/index.php?for....syu.env_voloffset_level+190000000_com.syu.ms
lr_man said:
Thanks a lot, much appeciated, both of you. Now I have seen it live ;-) Now I just have to figure out to get the setting. Maybe an update of the firmware....
Click to expand...
Click to collapse