Database Info

[Stock ROM] CAT B15Q ROM development

CAT has not yet managed to put official stock images or the kernel source code available - even for their oldest phones (even though they are required to)... so here's at least a beginning.
Every firmware archive contains the four partitions UBOOT, BOOTIMG, RECOVERY and ANDROID (/system). These are flashable using spFlashTool, a howto is here: http://forum.xda-developers.com/android/help/howto-firmware-flashing-cat-b15q-t2989627.
Please note that these firmware files were dumped from an EMEA B15Q, dual-sim - there are reports of other models being available under the B15Q model name. In doubt, always make a full backup using spFlashTool's readback mode before flashing one of these. (You should be doing these anyway before every firmware upgrade, CAT doesn't test stuff like compatibility with root!)
Credits for the scatter file go to bigal1337. Credits for spFlashTool and the driver package go to Russian website mtk2000.ucoz.ru.
1.019: https://mega.co.nz/#!UEp0hS7b!6aiqETvAu1Q9voNZtMLWoztbF7FGX0j9Pnj4rBhwoD4
1.022: https://mega.co.nz/#!YEAwmbxI!rVonLybVo6PL2bhNloGStR0EacKwE3-3hILzY9ri0NY
Scatter file: https://mega.co.nz/#!UEp0hS7b!6aiqETvAu1Q9voNZtMLWoztbF7FGX0j9Pnj4rBhwoD4
Tested tools:
MTK Driver package: http://mtk2000.ucoz.ru/down12/MTKUsbAll_0.9.2.rar
spFlashTool: http://mtk2000.ucoz.ru/down12/SP_Flash_Tool_exe_windows_v5.1420.00.rar
Do note that the drivers appear to be modified Google drivers and thus have no digital signature; you will need a 32-bit system to use them.
Flash mode needed for spFlashTool is achieved by removing the battery, starting the flash/readback in spFlashTool and then plugging in the USB cable. You may put in the battery afterwards.
The recovery, fastboot and factory test methods are entered by shutting down the phone and then:
recovery mode: press power + volup for 2 seconds, then release power, release volup as soon as recovery has booted
fastboot mode: press power + center for 2 seconds, then release power, release volup as soon as recovery has booted
test mode: press power + voldn for 2 seconds, then release power, release volup as soon as recovery has booted
In case that a B15Q or general CAT board is opened (for the B15, B15Q and the flagship S50), I request that this thread is moved into its rightful place. And in case anyone wants to help me with a CyanogenMod port, please PM me.

CWM Recovery
Using mtkdroidtools, I have built a CWM Recovery image to be flashed with spflashtool, all based on 1.022 firmware. There are two variants:
using stock Mediatek USB IDs: https://mega.co.nz/#!FRxxiRSC!EN5gORcYPtFONlH3V8-Yco3_w9RGhE8jevicedlT2kI
using Samsung USB IDs: https://mega.co.nz/#!8MowBZCJ!fhs-mXpGZR36g9JJh3IONIlOKBHIktFBDIrpynlK84M
The difference between them is that recovery #1 uses the same Mediatek USB id's as the stock image (and thus requires the Mediatek drivers in Windows, which sucks because these are not signed), and recovery #2 uses the USB IDs from a Samsung tablet - so you need the Samsung ADB driver instead, which is digitally signed and far more stable than the Mediatek.

Samsung USB ID fix
See above for the reason; the boot.img with Samsung USB IDs is at:
1.022: https://mega.co.nz/#!gcREQJKD!FCrxl9-PWSWM0_2Nh9D1KeA-zFV4nS9dmd6zjVnqPLc

Hybrid SD Card
And the CWM Recovery + boot.img for those who want to try out the "hybrid SD card" from http://forum.xda-developers.com/android/help/howto-external-sd-card-internal-storage-t2989650, the two images of 1.022 are here:
boot.img: https://mega.co.nz/#!MMYx1BYY!Rlnrxl1MURMgnx2luvPdYKJjMmNMbYVIGyFlGeRVcMY
recovery.img: https://mega.co.nz/#!wZQ1FIrS!iXAYfF3pgSySYsQ3f8ygGkDWE3Ulebx3JFgzRKXWNjs

I used this, it's great! Now I have 16gb of "internal phone memory" and 14 of "external" sd card. Did not see any performance issues with my SanDisk Extreme III. Do not need root anymore, I wanted it only for link2sd. Thanks harddisk_wp!!!

walckenaerius said:
I used this, it's great! Now I have 16gb of "internal phone memory" and 14 of "external" sd card. Did not see any performance issues with my SanDisk Extreme III. Do not need root anymore, I wanted it only for link2sd. Thanks harddisk_wp!!!
Click to expand...
Click to collapse
Great to hear someone was crazy enough to replicate my hack But I strongly advise you to keep off OTA updates with the hack enabled.

harddisk_wp said:
Great to hear someone was crazy enough to replicate my hack But I strongly advise you to keep off OTA updates with the hack enabled.
Click to expand...
Click to collapse
i have got a message that my sd card is damaged... and there is no way to remove that notification? any ideas?
thanks!

mccloud90 said:
i have got a message that my sd card is damaged... and there is no way to remove that notification? any ideas?
thanks!
Click to expand...
Click to collapse
With or without the SD hack? Try putting the SD card into a Windows machine, chkdsk the fat32 partition. Then plug it into a linux machine and run e2fsck on the data partition.

harddisk_wp said:
With or without the SD hack? Try putting the SD card into a Windows machine, chkdsk the fat32 partition. Then plug it into a linux machine and run e2fsck on the data partition.
Click to expand...
Click to collapse
I tried the sd hack. There was a problem with my sd card partitions... but i reformated it with partition magic and now it works like a charm. No lag or anything.
Better than i was thinking
Greatings!

after one week
OKAY,
after one week of usage my phone became laggy and unstable.
Maybe this is because of my sd card but.... its 10class, i dont know
So i reflashed with the original partitions and now its fast and stable

Custom Rom
Will there be any possibility to create a Lollipop rom for this device?

proximity sensor problem
Do someone have the problem with the proximity seonsor that i have? There is a screen turning on immediately after turning of when the phone is placed next to my head when i am calling. This leads to a lot of changes in settings and everything that my face is changed durring the phone call.
I tried a lot of apps from play store that "fix" the problem but... they work not on 100% proper.
The sensor is working at 100% i have checked it already.
Please give me suggestions because its very annoing!!

Hi!
mccloud90 said:
Do someone have the problem with the proximity seonsor that i have? There is a screen turning on immediately after turning of when the phone is placed next to my head when i am calling. This leads to a lot of changes in settings and everything that my face is changed durring the phone call.
I tried a lot of apps from play store that "fix" the problem but... they work not on 100% proper.
The sensor is working at 100% i have checked it already.
Please give me suggestions because its very annoing!!
Click to expand...
Click to collapse
I had the same problem. CAT support told me to reset the phone to factory. I tried a lot of other things but only the factory reset helped me. My sensor was also working correctly, I also tried several Apps to chack this.
Give it a try. I know it's a lot of work, but it was (in my case) worth it. I changed the time an date settings with my face which lead to missed alarms and oversleeping
Greets,
Doggy

Current ersion?
Doggy77 said:
Hi!
I had the same problem. CAT support told me to reset the phone to factory. I tried a lot of other things but only the factory reset helped me. My sensor was also working correctly, I also tried several Apps to chack this.
Give it a try. I know it's a lot of work, but it was (in my case) worth it. I changed the time an date settings with my face which lead to missed alarms and oversleeping
Greets,
Doggy
Click to expand...
Click to collapse
You have hard reseted to what rom version? 1.19 or 1.22
I will give it a try
I need the phone rooted and i am not sure if the cwm recovery can be flashed over 1.19 as it was my original rom and i flashed it to 1.22 from files here on the forum

any news about any cyanogenmod rom?

Just to tell you that the new official update is awsome!!! Upgrade as fast as possible Greatings!

CAT B15 help
Hi guys, i'm sorry i have to ask this in this forum but i've been asking for a couple of months now, and got no answer. I have a CAT B15 (not the B15Q). It is single sim version (IMEI write on the back) and i managed to do plenty of things in it. I swapped memory and worked fine, and even i installed a Dual Sim android rom and i managed to use the secondary Sim bay in it (that was tapped with a plastic fake sim) and used the phone with 2 sims for like 2 weeks. Then i started to play with deodex and build.prop and softbricked the phone, but it was piece of cake since it is easy to unbrick. The problem was that i wrongly flashed the phone with scatter file, and flashed all partitions in it, EBR1, MBR, UBOOT, etc, etc. The result was a non-working dual SIM phone. Everything works, but the SIMS, it does not detect any SIMs in it, in any of the SIM bays, and the IMEIs are wrong numbered. I did no buckup of the phone so i'm pretty screwed. I've been asking for someone to upload the EMEA_SS or US_SS ROM for the CAT B15, but nobody responded. I thaught maybe the CAT B15Q has a similar software/bands flashing partitions, but that i leave to you for answer. Anyway, if any of you has the possibility of taking the images of a single sim CAT B15 it would save me this awesome phone for me. I'm also willing to give a 20GB account of ownCloud server for 1-year free of charge if storage space is needed, no problem. This are the links i've been searching and asking.
All About CAT B15: http://forum.xda-developers.com/showthread.php?t=2430904
Root for Catterpillar B15: http://forum.xda-developers.com/showthread.php?t=2263455
Best regards,

proximity sensor problem
I also have the proximity sensor problem.
I have tried the factory reset but the problem is the same.
It has 1.026 rom.

Can anybody post the 1.026 software? Thanks!

yo2lzp said:
I also have the proximity sensor problem.
I have tried the factory reset but the problem is the same.
It has 1.026 rom.
Click to expand...
Click to collapse
Hallo my friend,
i had the same problem and that was so anoyng... so i went back to the shop where i bought my phone and told them about the problem.
After one week they called me and my phone was with changed whole display with everything inside and now i have working proximity sensor
So... i suggest you to go back to the store and tell them about your problem !
All the best!!

Using RK Batchtool on a bricked Joying 5.1.1 headunit

Hi Everyone,
I did a stupid thing and flashed my head unit with a 4.4.4 rom.
I can no longer get into recovery unless I use sd_Firmware tool. sd_Firmware tools doesn't restore the image though.
I am trying to use RK Batchtools to reimage the device but I cannot get the head unit to show up in device manager.
Am I correct in using any of the 2 USB leads that come out of the back of the head unit (normally used for 3g adapter or USB thumb drive) with a A to A USB cable to join to the laptop?
Is there any button pressing process required for it to connect to the laptop?
Many many thanks in advance. So angry with myself.

Same problem, Someone Can help us?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

colostro said:
Same problem, Someone Can help us?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
OK Success, my head unit is back up and running.
I believe (somebody please correct me if i'm wrong) that the issue lies in the MCU.
I used sd_Firmware tool to generate a bootable SD card. This on it's own should've been enough to flash the device but mine would fail with an error asking to remove the SD card. Once you remove the SD card you're presented with a recovery menu.
Have a USB stick with ONLY the mcu img file, select restore from USB + wipe. This will re-apply the MCU file.
One that is done, the device will reboot but will not post. Restart the device using the boot SD card once again to repeat the process but replace your MCU file with your dupdate.img file.
This should get your device bootable again. Don't forget to load the recovery menu from the device and select the wipe data + cache option.
Let me know how you go

Thanks, i'm going to try.
I still used sd_firmware tool, but the sw doesn't recognize my sd card (Windows is ok, recognize it)...
I Can put my unit in recovery mode
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

colostro said:
Thanks, i'm going to try.
I still used sd_firmware tool, but the sw doesn't recognize my sd card (Windows is ok, recognize it)...
I Can put my unit in recovery mode
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
run SD firmware tool "as administrator" if you cannot see the tool.
Are you saying you can enter recovery mode without the use of a bootable SD card? Because if that's the case, we do not share the same issue.

We have not the same issue, i know.
After using Malaysk rom, my unit doesn't boot anymore, I entered in recovery mode and trying to update original rom but i receive an errore like this "device block required"
EDIT: I DID IT!!!!!!! Using your method (first MCU and then ROM), I recovered my hed unit... Thanks so much.... GREAAAAATTTTTT
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

Can you please tell me what you put onto your drive to make it "bootable" ?
Did you put the MCU file onto the drive or the firmware ?
My HU does nothing its just black screen
Thank You !!

You have to put firmware file (much greater file), then put the sd into gps slot and at least turn on your head unit and wait
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

colostro said:
You have to put firmware file (much greater file), then put the sd into gps slot and at least turn on your head unit and wait
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
Thank you I tried this but the tool wont write the file to the sd card as its not a .img file
Do I need to rename it ?
Thank You

have you original dupdate.img? I tried with my original head unit file and works fine

colostro said:
have you original dupdate.img? I tried with my original head unit file and works fine
Click to expand...
Click to collapse
No I dont =\

What version of MCU have you?

I'm actually trying to unbrick my Allwinner R16
I dont even know if this will work
Quadcore-r16-1.6g
Android 4.4.2
MCU Version
5.3.18-98-13-E50201-160406
SYSTEM VERSION
4.5.9_20160322

Cid6.7 said:
I'm actually trying to unbrick my Allwinner R16
I dont even know if this will work
Quadcore-r16-1.6g
Android 4.4.2
MCU Version
5.3.18-98-13-E50201-160406
SYSTEM VERSION
4.5.9_20160322
Click to expand...
Click to collapse
I'm Sorry but i can't help you... I don't know
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

Cid6.7 said:
Thank you I tried this but the tool wont write the file to the sd card as its not a .img file
Do I need to rename it ?
Thank You
Click to expand...
Click to collapse
The SD card is just to boot the device, flash the MCU from a usb flash drive.
You do have to create the SD card using the update.img file though. Get one from the "Factory images" thread.

Factory images thread ? I haven't seen this got a link ?
Thank You !

http://forum.xda-developers.com/and...ent/rom-factory-firmware-rk3188-mtcd-t3366561

morgish said:
OK Success, my head unit is back up and running.
I believe (somebody please correct me if i'm wrong) that the issue lies in the MCU.
I used sd_Firmware tool to generate a bootable SD card. This on it's own should've been enough to flash the device but mine would fail with an error asking to remove the SD card. Once you remove the SD card you're presented with a recovery menu.
Have a USB stick with ONLY the mcu img file, select restore from USB + wipe. This will re-apply the MCU file.
One that is done, the device will reboot but will not post. Restart the device using the boot SD card once again to repeat the process but replace your MCU file with your dupdate.img file.
This should get your device bootable again. Don't forget to load the recovery menu from the device and select the wipe data + cache option.
Let me know how you go
Click to expand...
Click to collapse
I was able to successfully flash an MCU using your USB method. Now to flash the rom image do I select restore from UBS + Clear all or just restore from USB in recovery? What's the difference?
Also, what does the 'upgrade' checkbox on the sd_firmware tool do vs. just drag and dropping the image file in windows? This piece of software is perplexing to me. Is its main function to create disks (cards or sticks) that will flash a device w\o having to go through recovery?

rotomoto said:
I was able to successfully flash an MCU using your USB method. Now to flash the rom image do I select restore from UBS + Clear all or just restore from USB in recovery? What's the difference?
Click to expand...
Click to collapse
I believe you can upgrade and keep your settings etc if you're going from one version to the bump up.
If you're going from major version diferences (or recovering from a big fault) it would be best to do the clear all (same as factory reset).
If you have flashed your MCU successfully, you may find you can use the unit's recovery and not the "bootable sd card"
rotomoto said:
Also, what does the 'upgrade' checkbox on the sd_firmware tool do vs. just drag and dropping the image file in windows? This piece of software is perplexing to me. Is its main function to create disks (cards or sticks) that will flash a device w\o having to go through recovery?
Click to expand...
Click to collapse
I wouldn't worry too much about the sd_firmware tool settings, simply use it as a boot disk to get into recovery then use recovery to reflash the device (As you have done with your MCU file)
Yes that's correct, flashing a device without using it's own recovery. I believe it's for band new units that has never had software (recovery) flashed?

morgish said:
I believe you can upgrade and keep your settings etc if you're going from one version to the bump up.
If you're going from major version diferences (or recovering from a big fault) it would be best to do the clear all (same as factory reset).
If you have flashed your MCU successfully, you may find you can use the unit's recovery and not the "bootable sd card"
I wouldn't worry too much about the sd_firmware tool settings, simply use it as a boot disk to get into recovery then use recovery to reflash the device (As you have done with your MCU file)
Yes that's correct, flashing a device without using it's own recovery. I believe it's for band new units that has never had software (recovery) flashed?
Click to expand...
Click to collapse
Hi,
does anybody know why I get this error in the SD Firmware Tool, every time when I tick "SD Boot"? My device is bricked and it doesn't enter recovery mode. Therefore I tried this tool, as I don't have a USB A-A. Creating the firmware SD without ticking "SD Boot" works fine, but trying to make it bootable gives me this error. Tried with 3 versions of the firmware for my device. Started the tool as an administrator, on a win7.
Thx in advance!

Xomax Android Car Radio How to Root

Hello.
i have a Xomax xm-2va757 Radio. It seems to be an Allwinner Venus a3.
My Problem is, that I can’t using other apps or launchers correctly. Because the Apps haven’t any access to the system notifications. And no, I have also no access to activate it. So if there is no hidden menu for it, I meet to root.
If buyed this device with Android 10q. But it is only 9 pie.
i tried many things but nothing worked. And no proper help from the Seller.
I also doesn’t know, how to get into recovery.
I tried an update file with supersu. And the system doesn’t said any error. But nothing happens after restart.
And Rom manager gets no internet, but WiFi is still connected. And king and also Kongo root does not worked.
I also want to deactivate the building music player, because it is only good when you have only 20 audiofiles(No Folder Structure).
so, what kind of data you need else?
oh, this is mine: Radio on Amazon
Thx for help
kindly

Hi, do you find any solution ?

Question File to update MCU

Hi All,
I wanted to find the file that I need to use to update my Head Unit, had an issue and it displays an error saying "Canbus Serial port:/dev/ttyS1 was used! !" and unabled my steering buttons.
Does anybody knows which file or where can I look for it?
Thanks in advance!
MCU Version: 2021.03.16 18:42:45 NOR_812_F2N_G23P32f32_Ver: 1.0(FYT)
Device: sp7731e_1h10

And what did your reseller say?
I would not simply write another MCU firmware over my head unit.
And how did this happen? Did you already flash it with another firmware?

I chated with the reseller and indeed told me that I had reload the can Box files, for such thing, unfortunately after many atempts asking for such file the reseller simply would not provide such file, thats why I try to research for an alternative download.
being completly new to this I was playing around with the configurations and tried to upload a new firmware without having selected any , so I guess the configurations messed up afterwards.
I have seen many different firmwares for the head unit , but the head unit works fine excepting the steering controls , so I am not sure if I have to update the firmware of the entire headunit, or the MCU or the CAB Box configurations.
Is there any known library or repository for many known versions of such firmwares so I can take the closest one to it? and hope to not trash the entire head unit?
Thanks in advance!

Your s7731 is less wide spread than the uis7862 or uis8514. There are not so many and not so many in this forum. In this case you might take a look on 4pda.

did you find any solution ?

i think have same radio as you
Where did you get your ?
Any luck finding a newer MCU update ?

royo210 said:
I chated with the reseller and indeed told me that I had reload the can Box files, for such thing, unfortunately after many atempts asking for such file the reseller simply would not provide such file, thats why I try to research for an alternative download.
being completly new to this I was playing around with the configurations and tried to upload a new firmware without having selected any , so I guess the configurations messed up afterwards.
I have seen many different firmwares for the head unit , but the head unit works fine excepting the steering controls , so I am not sure if I have to update the firmware of the entire headunit, or the MCU or the CAB Box configurations.
Is there any known library or repository for many known versions of such firmwares so I can take the closest one to it? and hope to not trash the entire head unit?
Thanks in advance!
Click to expand...
Click to collapse
Have u found mcu file ?

ghannaiem said:
Have u found mcu file ?
Click to expand...
Click to collapse
I got this file from the seller after asking a lot, but unfortunately I haven't been able to execute the file, if anyone can execute this correctly can u give advice on how to proceed?

royo210 said:
I got this file from the seller after asking a lot, but unfortunately I haven't been able to execute the file, if anyone can execute this correctly can u give advice on how to proceed?
Click to expand...
Click to collapse
Thanks for sharing .
File is old and does not contain MCU.
MCU unlikely to be issue

marchnz said:
Thanks for sharing .
File is old and does not contain MCU.
MCU unlikely to be issue
Click to expand...
Click to collapse
Then what does that File contains?
How can you tell?

royo210 said:
I got this file from the seller after asking a lot, but unfortunately I haven't been able to execute the file, if anyone can execute this correctly can u give advice on how to proceed?
Click to expand...
Click to collapse
Mcu file should be named as "mcuall.bin "
Unfortunately they do not provide it with firmware update . any way thanks so much for the link and i'll use the firmware you provide hoping it will fix the problem

ghannaiem said:
Mcu file should be named as "mcuall.bin "
Unfortunately they do not provide it with firmware update . any way thanks so much for the link and i'll use the firmware you provide hoping it will fix the problem
Click to expand...
Click to collapse
What Issue you have and are trying to solve with this firmware?

royo210 said:
What Issue you have and are trying to solve with this firmware?
Click to expand...
Click to collapse
If car is parcked for more than 48 hours headunit goes to deep sleep then when start using and ignition is on it stuck on boot logo and it wont boot until i force restart it with reset button

ghannaiem said:
Mcu file should be named as "mcuall.bin "
Click to expand...
Click to collapse
Are you sure?
I believe the OP's device uses an MCU file named stm32ud.bin, just like other FYT devices.

Hi me also with this device is there any update or can the android be changed thanks

j0hn83 said:
Are you sure?
I believe the OP's device uses an MCU file named stm32ud.bin, just like other FYT devices.
Click to expand...
Click to collapse
Stm32ud is for Gd32f-------- mcu types like in teyes cc2l/plus
While my device and also @royo210 's device use another type mcu chip here below is a picture for
And it is named in the system info as
NOR_812_F2N_G23P32f32_Ver: 1.0(FYT)

royo210 said:
Canbus Serial port:/dev/ttyS1 was used!
Click to expand...
Click to collapse
this is caused by BSP Serial Debug option in Developers Settings. Disable it and never enable again
do not try to flash any mcu firmware just for fun, you might not be able to revert this back and i think 100% this won't help you with steering wheel buttons

Does someone who can help me to find the firmware and the MCU for this one?
Intel Sofia3gr Rockchip RK30SDK
MCU: FY_90_C9_7703_18EM_JY2009B
Security patch level: 01-06-2016

Question A bit of a newbie Bluetooth question.

As my joying head unit only allows certain devices to connect due to Joying Bluetooth crippling, would adding a Bluetooth dongle allow other devices, or will the limitations still apply to the USB input?

looking for the same answer. Apparently older models could use Bluetooth dongle so long as it was the same exact Bluetooth chipset found inside the android head unit. Secondly, the Bluetooth config has to be altered to use the external dongle instead of the internal chipset. This was ~2017 era. So far nobody has fixed the Bluetooth exclusivity limitations. The only other way is if you have the FYT 7862 headunits and use custom firmware and rom to bring back bluetooth control thru the custom FYT mamager.

Tricky13 said:
As my joying head unit only allows certain devices to connect due to Joying Bluetooth crippling, would adding a Bluetooth dongle allow other devices, or will the limitations still apply to the USB input?
Click to expand...
Click to collapse
Does Bluetooth only reconnect to the last device used?
My unit allowed me to pair multiple phones (my wife and daughter also drive) but the Bluetooth system would only reconnect to the last phone used. So if I drove the car last, and then my wife drives, it won't connect to her phone without manually...
forum.xda-developers.com
Follow that thread, it might turn out useful

this is the best thing to happen to android HUs. You need YFT models for this firmware to work. https://forum.xda-developers.com/t/...dition-with-fmc.4542673/page-30#post-88513899

Unfortunately, nothing that would help my head unit in that thread.
Onkypig said:
looking for the same answer. Apparently older models could use Bluetooth dongle so long as it was the same exact Bluetooth chipset found inside the android head unit. Secondly, the Bluetooth config has to be altered to use the external dongle instead of the internal chipset. This was ~2017 era. So far nobody has fixed the Bluetooth exclusivity limitations. The only other way is if you have the FYT 7862 headunits and use custom firmware and rom to bring back bluetooth control thru the custom FYT mamager.
Click to expand...
Click to collapse
Thank you for that must be the first understandable and helpful comment I have had so far.

On a side note, I tried a Bluetooth mouse and that worked with its own dongle.

Tricky13 said:
On a side note, I tried a Bluetooth mouse and that worked with its own dongle.
Click to expand...
Click to collapse
So does a BT keyboard. I use that when I need to type a lot on my unit, for example when using the linux terminal.
But a Bluetooth dongle will not help at all.
But you are asking the same question again and again and do it by cross-posting in several threads. I already pointed you to the same thread as @louforgiveno did in post #3.
It DOES contain relevant information for your unit and it DOES contain the info you need to be able to pair more devices. I think it is because you only look at the title or because you don't understand it or did not read it completely, but it exactly gives the information you need.
It doesn't help to ignore that.
I do not understand either why you mention that the reply from @Onkypig is understandable. It leads to one of my posts explaining a flashing issue due to a corrupt USB-stick. There is no relevance at all to this question.

As I said before I am a newbie to doing anything to tweak Android head units or anything Android for that matter, and so far all I get is pointed to threads that apparently are supposed to be of some help but most of which I don't understand, but the end result is I just get criticised for not posting in the right place (this forum is bloody confusing to a newbie!) and not being able to understand the jargon instead of being offered help, so pardon me for being uneducated in Android.

Being new to "something" is OK. We all started that way. But you were saying that that thread that was mentioned by both @louforgiveno and myself was not (relevant) for your unit. By saying that you give a totally different impression to us.
Check what value your sys.fyt.bluetooth_type is.
- If you have your original firmware, check the config.txt
- If you don't have that, then check it yourself
- If you don't know how to do that, then download, install and run my HWGetInfo (from my signature below my posts). It will show you.
If the value is 1, create a config.txt containing sys.fyt.bluetooth_type=0
If the value is 0, create a config.txt containing sys.fyt.bluetooth_type=1
Save that text file onto a clean usb-stick and copy the lsec6315update from your Joying firmware also on that usb-stick, and nothing more than those two files.
Flash your unit with this and try again.
If it doesn't work, replace the value in your config.txt and put the original value back in. Flash that again.

surfer63 said:
Being new to "something" is OK. We all started that way. But you were saying that that thread that was mentioned by both @louforgiveno and myself was not (relevant) for your unit. By saying that you give a totally different impression to us.
Check what value your sys.fyt.bluetooth_type is.
- If you have your original firmware, check the config.txt
- If you don't have that, then check it yourself
- If you don't know how to do that, then download, install and run my HWGetInfo (from my signature below my posts). It will show you.
If the value is 1, create a config.txt containing sys.fyt.bluetooth_type=0
If the value is 0, create a config.txt containing sys.fyt.bluetooth_type=1
Save that text file onto a clean usb-stick and copy the lsec6315update from your Joying firmware also on that usb-stick, and nothing more than those two files.
Flash your unit with this and try again.
If it doesn't work, replace the value in your config.txt and put the original value back in. Flash that again.
Click to expand...
Click to collapse
​Tricky13, for real this is the answer and it was in that thread. One thing you'll learn if you hang out here long enough, is that @surfer63 usually has the answer and there aren't many, if any, who know these units better than him.​

surfer63 said:
Being new to "something" is OK. We all started that way. But you were saying that that thread that was mentioned by both @louforgiveno and myself was not (relevant) for your unit. By saying that you give a totally different impression to us.
Check what value your sys.fyt.bluetooth_type is.
- If you have your original firmware, check the config.txt
- If you don't have that, then check it yourself
- If you don't know how to do that, then download, install and run my HWGetInfo (from my signature below my posts). It will show you.
If the value is 1, create a config.txt containing sys.fyt.bluetooth_type=0
If the value is 0, create a config.txt containing sys.fyt.bluetooth_type=1
Save that text file onto a clean usb-stick and copy the lsec6315update from your Joying firmware also on that usb-stick, and nothing more than those two files.
Flash your unit with this and try again.
If it doesn't work, replace the value in your config.txt and put the original value back in. Flash that again.
Click to expand...
Click to collapse
Thank you for explaining, I have used the HWGetinfo and found the sys.fyt.bluetooth_type=1 however not sure what/where the lsec6315update is, and how do you flash this to the unit?
Does the USB stick need to be formatted to anything in particular?

Tricky13 said:
Thank you for explaining, I have used the HWGetinfo and found the sys.fyt.bluetooth_type=1 however not sure what/where the lsec6315update is, and how do you flash this to the unit?
Does the USB stick need to be formatted to anything in particular?
Click to expand...
Click to collapse
The USB-stick must be formatted as FAT32.
Unzip below zip onto it.
Put it in your unit and it will flash automatically.
After reboot test your BT devices.
If it did not help, change the value in the config.txt back to 1 and flash again to "restore" to original state.

dishe2 said:
​Tricky13, for real this is the answer and it was in that thread. One thing you'll learn if you hang out here long enough, is that @surfer63 usually has the answer and there aren't many, if any, who know these units better than him.​
Click to expand...
Click to collapse
Must admit that I wish I understood coding, but I admire those that can write and understand it.
surfer63 said:
The USB-stick must be formatted as FAT32.
Unzip below zip onto it.
Put it in your unit and it will flash automatically.
After reboot test your BT devices.
If it did not help, change the value in the config.txt back to 1 and flash again to "restore" to original state.
Click to expand...
Click to collapse
Many thanks for your help and patience, I will give it a try and report back.

Tricky13 said:
On a side note, I tried a Bluetooth mouse and that worked with its own dongle.
Click to expand...
Click to collapse
Any "Bluetooth mouse" with its own USB adapter is probably not actually Bluetooth.
It's simply a wireless mouse using the 2.4 GHz ISM band for communication.
To see if this is the case just plug the USB adapter into a desktop and look at the USB configuration descriptor.
That's lsusb -v in Linux or the usbview.exe utility in Windows.
What you'll see is what looks like a wired USB mouse, not a Bluetooth adapter.

surfer63 said:
The USB-stick must be formatted as FAT32.
Unzip below zip onto it.
Put it in your unit and it will flash automatically.
After reboot test your BT devices.
If it did not help, change the value in the config.txt back to 1 and flash again to "restore" to original state.
Click to expand...
Click to collapse
Just before I go ahead, I am using the latest update firmware ...
Here is the firmware for 10.1" 1920*1200:
Updated files please click Here.
Applicable Radio Models: UQS10N4G-H, UQS10N6G-H, UQD10N4G-H, UQD10N6G-H
Just wanted to check this is OK ?

Tricky13 said:
Just before I go ahead, I am using the latest update firmware ...
Here is the firmware for 10.1" 1920*1200:
Updated files please click Here.
Applicable Radio Models: UQS10N4G-H, UQS10N6G-H, UQD10N4G-H, UQD10N6G-H
Click to expand...
Click to collapse
I don't understand. Do you mean to use this as backup?
Or do you want to use it to flash? This you should not do. Only the files I put in that zip. The only thing is that if it doesn't flash, you take the lsec6315update out of the firmware and copy that onto the usb-stick.

surfer63 said:
I don't understand. Do you mean to use this as backup?
Or do you want to use it to flash? This you should not do. Only the files I put in that zip. The only thing is that if it doesn't flash, you take the lsec6315update out of the firmware and copy that onto the usb-stick.
Click to expand...
Click to collapse
No I mean that is the firmware I am currently using, I updated late last year, and I just wanted to check that it was OK to go ahead with using the one you provided as I know Joying use different for each display resolution.

Tricky13 said:
No I mean that is the firmware I am currently using, I updated late last year, and I just wanted to check that it was OK to go ahead with using the one you provided as I know Joying use different for each display resolution.
Click to expand...
Click to collapse
In the zip file surfer63 gave you is 2 files, not a firmware. An lsecupdate file that doesn't actually do anything other than tell the unit it is to be flashed. There's also a config.txt file with a single line, making only 1 change.
If it doesn't have the desired effect, change the 0 to a 1 in the config.txt, flash it again and everything will revert back to how it was.
It matters not what device you have or what firmware you are running.

j0hn83 said:
In the zip file surfer63 gave you is 2 files, not a firmware. An lsecupdate file that doesn't actually do anything other than tell the unit it is to be flashed. There's also a config.txt file with a single line, making only 1 change.
If it doesn't have the desired effect, change the 0 to a 1 in the config.txt, flash it again and everything will revert back to how it was.
It matters not what device you have or what firmware you are running.
Click to expand...
Click to collapse
Thank you! It always pays to double-check when you don't know exactly what you're doing.

Well, Bluetooth is still not connecting to the devices I want, but I now have an inverted screen!! Any ideas how to change this back?
I am going to revert the Bluetooth config back to as before, but no idea why the screen is now inverted?
At least being Joying, I can just spin it around on the mounts, but it's still very odd that It's become inverted?