Database Info

Problems Connecting to External Bluetooth GPS

So I picked up an external GPS receiver off ebay. It's the Globalsat BT-359C (http://www.usglobalsat.com/p-214-bt-359c.aspx). Turned it on, everything went fine as far as my fuze finding it. I'd goto add new device, it'd pull up "BT-GPS371D88", i'd select it, put it the four "0" 's, and it'd give me the message "your pocketpc is now connected with BT-GPS371D88". It comes up in the list but under disconnected. So i'm like eh whatever, and setup the outgoing com port to COM0 as per the instructions, and make sure its unsecure.
I go back to devices, highlight BT-GPS371D88, click it. Check off "Serial Port" in select services to use, and save. Then heres where everything goes wrong, I hit connect, and it gives me the following message "Your device did not connect with BT-GPS371D88. The connection failed or the passcode is incorrect." I've been tinkering with it all day, searching various forums to no avail. Even downgraded my 6.5 rom to 6.1 thinking it was maybe incompatible with something so new.
Now i'm stuck, I really want to get it working so i can use it for a trip thats coming up in a few days. Has anyone else had such a problem? is there like a quick fix that i'm over looking, or is it simply not compatible with the fuze? I managed to get it paired up and connected fine to my blackberry curve just to see if the gps unit was defective (did buy it off ebay). Any Ideas guys? Not sure where else to turn now.
Oh yeah btw my current rom that i'm using is
At0mAng Fusion Power V 5.X ROM Series
Windows Mobile 6.1 (Build 21051 1.6.4)
Located @ http://forum.xda-developers.com/showthread.php?t=537501

jimshepp said:
So I picked up an external GPS receiver off ebay. It's the Globalsat BT-359C (http://www.usglobalsat.com/p-214-bt-359c.aspx). Turned it on, everything went fine as far as my fuze finding it. I'd goto add new device, it'd pull up "BT-GPS371D88", i'd select it, put it the four "0" 's, and it'd give me the message "your pocketpc is now connected with BT-GPS371D
Click to expand...
Click to collapse
have a BT GPS for my Dell axim x51v, got some trouble too getting it to connect, but eventually did
here are some pointers:
1) Delete all pairings and com port pairings on the device
2) Pair the device (make sure that you put 'request authorization' or something... this ensures that you need to put the 0000 code to connect)
3) you need to set up at outgoing port on your device, to the BT GPS... COM 8 is norm
4) External GPS setting in the Start>Settings tab
hardware port is where you put the outgoing port in (3)
software port is where you put for your GPS software... COM4 is norm
third column where WinMo will manage GPS, say yes

This worked for me:
I have a Hermes (WM6.5) with a holoux bluetooth GPS, but the GPS was not connecting for me properly either. It seems to be a problem with the way WM6.1 pairs with bluetooth devices.
I managed to get mine to work without reflashing by downloading this alternative bluetooth manager:
http://forum.xda-developers.com/showthread.php?t=353774
Hope this helps.

Not trying to bump up an old thread for no reason, but I figured this info would be helpful for people utilizing searches.
After lots of research and frustration the past week I have gotten my external GPS (USGlobalSat BT-368i) to work with my HTC Fuze! Below are the steps I followed that have worked for me. Note that I still have the phone configured to use the internal GPS if the program is set to "Let windows manage GPS settings".
1. Pair the device using Bluetooth.
2. Under the devices tab select your external gps device, and check the box to use "Serial Port". Then choose Save.
2. Under the Bluetooth settings choose "COM Ports" tab.
3. Choose "New Outgoing Port", and then select your device and click next. Choose your port and preferred "secure" option. Then click Finish. (I have configured mine to use COM0 & Secure Connection)
The device will still show as "Disconnected", and you will not be able to connect it under the Bluetooth manager. It will give you an error saying unable to connect.
To use the external GPS device you can simply select the outgoing port you configured above in your program, and most likely you will use a baud rate of 4800. Once you enable the GPS in the program it should connect itself via Bluetooth to your device and begin using it.
You should also be able to configure it to automatically use your external GPS instead of the internal one under the "External GPS" settings, but my current ROM has the hardware portion of External GPS manager broken @ the moment. Therefore I have not configured this, and cannot confirm it.
Hope this helps someone!

[GUIDE/TUT] How to get ICS devices run OBD2 interfaces via WIFI WITHOUT DROPS

Did you end up buying a OBD2 Wifi (not bluetooth) interface for your car, noticing android got some problems with ad-hoc connections and can't connect that easy, that you may have thought?
Well, if so, I'm at least not the only one
In my case I wanted to have a look at my engine stats etc. You might also be happy about checking the vin stored in the cars ecu with the one you got on paper, when buying a used car or else. Anyway I did not want those crappy bluetooth thing for some bucks. I wanted it to use wifi and also to be able to connect via usb to a laptop, if neccessary.
I got mine from eBay for about 80$. There is a bunch of these things avaible everywhere. I can't really tell you which one is better in which way. Most of them come out of china and are built pretty cheap, just like mine
BUT at least they work the way the should, once configured right.
IN GENERAL --> without any kind of workaround you shold keep in mind:
BT OBD2 is used for android devices. No Problem
WIFI OBD2 is usually used for iDevices, as they're not allowed to share BT with non-iDevices.
I didn't really make up my head about the second part, as I'm using android on every device I personally own.
Here's a tutorial on how I solved it anyway:
1. Buy yourself some OBD2 interface with wifi and the software you desire. Didn't test anything else but torque pro; no guarantee that other apps support these android-wifi-adhoc-obd-interface-workarounds
2. you need a rooted phone, in every possible case afaik.
3. Plug in your OBD interface and look, if you can see it in your wlan list.
In my case...I couldn't^^
If you see it jump to Number 4.4, if not, just keep on reading.
4. Getting my device, which is a HTC Sensation, with ARHD 6.6.7 - 4.0.3 ICS, connected to it required some effort:
4.1. I used a different wpa_Supplicant, to be able to see adhoc networks
I got this one: http://forum.xda-developers.com/showthread.php?t=1549065&highlight=adhoc also attached in the Thread. Full Credits go to the dev, although I don't know who it was exactly.
4.2. REMEMBER TO BACKUP YOUR ORIGINAL WPA_SUPPLICANT AND SWITCH WIFI OFF BEFORE!
It's stored in system/bin; so you'll need a explorer (mount R/W) for your phone's file system. I always used the root explorer. Worked flawlessly everytime. (mount R/O afterwards).
4.3. Flash the attached file in recovery -> I did at least find the adhoc network after it. Remember that some wifi off, wifi on sometimes solves problemes with this. This was at least the case for me. Reboot.
4.4. Now that you can see the OBD interface in your wlan list, you propably tried to connect, didn't you?
For most of us, this won't work, that easy, as your OBD interface doesn't work as a DHCP router, so you're in the need of taking a static IP.
Therefore it always depends on which IP range your interface is networking. In the most cases this will be 192.168.0.X
Picture #1 is a screen of the config tool, that came with mine so I can modify these values. (What is not really neccessary, cause you're doing this with your phone.)
Picture #2 are my stats. You can edit yours by long pressing on your desired OBD device in your phones wifi list and pressing "edit network". After that, change to advanced configuration and choose static IP.
4.5. Save your preferences and try to connect. Again I think my wifi needed a reboot to work with the values set now. So just swith it off/on again.
5. You're done. More or less. Because this is just what made me able to connect but drop my connection to the OBD after trying to access it via torque. It did connect (as seen on adapter status in torque), but lose connection after some seconds. It just didn't really work for a longer period of time. There also used to be connecting errors with my home wifi.
5. After hours of testing and experimenting with this whole topic I came to the conclusion my home network didn't work anymore or rather my phone couldn't keep up the connection. What you have to do is switch back to your old wpa_supplicant. Don't worry, your OBD interface should be saved and is still accessable afterwards.
5.1. SWITCH WIFI OFF. Navigate to system/bin via root explorer or similiar. (mount R/W) locate the wpa_supplicate and delete/rename/remove it and put the original file back in it. (mount R/O afterwards). Reboot.
(Picture #3 shows how it looked on my device after switching back to the original file.)
5.2. You're finally done.
Remember not to forget that wrong permissions could lead to errors. Refer to my attached screenshot or your original file, if neccessary.

where you found the configuration tool??

Cannot Pair Sony DualShock 4 Controller to my phone?

Hey everyone. I am running a stock, rooted OS (v 4.4.2). I have version 1.4 of the remote play app installed, and it works awesome! With the on screen controls it works great, and is very snappy.
I am running into a bunch of issues getting my DS4 to pair to the device via bluetooth.
I tried doing the native bluetooth pairing (holding share + PS on the controller, and scanning on the GS5). The device showed up, but if I tried to pair it, it would literally just sit there and never do anything.
Next, I ended up having to use SixAxisPairTool in conjunction with SixAxis Compatibility Checker (as mentioned in other threads). I used the compatibility checker to get my BT local address, and then I used the PairTool to change the master address to the one listed. When I try to pair the device with bluetooth inside the compatibility checker, it flat out fails and says no devices are connected, and to connect with usb.
Except the instructions on their website say the exact opposite - to disconnect the controller from usb and press the PS button to pair. When I stop trying to pair in the compatibility checker, I get an error saying that the maximum number of devices are connected.
So, I closed out of the compatibility checker, and opened back up the native bluetooth settings, and tried repairing again. This time the device showed up, and it is now listed as paired. But there is no light on the DS4. If I press the PS button, it does one of the following: it flashes white constantly, it flashes white once and stays lit for a few seconds and then goes off, it flashes white several times then stays on for a second.
I have unpaired the device inside the phone, and then pressed the PS button, and I get prompted with a request to pair the device. When I accept, the same thing happens. The light disappears on the back of the DS4, and nothing happens.
I tried using a joystick tester to see if it was connected and the light just didn't work properly, but there doesn't seem to be any communication between the two devices.
I would really like to avoid having to buy an OTG cable (namely because I can't seem to find a decent one except for questionably sourced ones from a reliable vendor), and really was hoping for a wireless setup.
Can anyone help a brother out here? I have had a prompt in my dock for months about a system update for my phone, but I have been hesitant to install it because I don't want to lose root, and none of the ROMs out there seem to be vanilla stock + root.
Edit:
I unpaired the controller from my phone, and opened back up the compatibility checker. Ignoring the pair button, I just started the software. Then I hit the PS button and it flashes white 2-3 times and stops. If I do this again, it will repeat. No text changes on the screen. I can do this two more times. When I attempt to do this a fifth time, I get an error message saying "Maximum number of clients already connected."

Question Bluetooth connectivity issues

I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.

Turn off global power management completely in Device Care.
Network reset, reboot and clear system cache from the boot menu.

Ok, I've done a network reset, and cleared the cache partition. I checked Device Care for something like global power management, and I couldn't find anything. Most of the pwm settings are off except the "optomise daily" setting.
I'll let you know later if I have the same issue again.

These, this is a N10+ running on Pie.
To check if you have disabled global power go to Developer options>standby apps, all buckets should show as active otherwise power management is enable.

KindarConrath said:
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Click to expand...
Click to collapse
Are those the only three devices you connect via BT? What other apps do you use that need to use BT (i.e. Galaxy Wear, Apple Music, etc.).
You mentioned "Nordic Semiconductors Bluetooth App." I looked it up. Why do you need a third party generic BLE connecting app? It seems to me that could be the problem. You shouldn't need a third-party app to connect your BLE devices. The S22U's native pairing will work with any BT device that adheres to BT standards.
Try uninstalling the nRF Connect app and see what happens.

The only other Bluetooth devices I have are other in-house hardware, running on SiliconLabs BGM13P chips or NRF52840 chips...
The NRF app isn't a replacement for your bluetooth pairing app, its a debugging app... it can connect to BLE devices and show their GATT profiles, update devices that have Nordic's OTA update code and copy a devices GATT profile to act as a BLE Server.
We use it for testing and debugging.

KindarConrath said:
The only other Bluetooth devices I have are other in-house hardware, running on SiliconLabs BGM13P chips or NRF52840 chips...
The NRF app isn't a replacement for your bluetooth pairing app, its a debugging app... it can connect to BLE devices and show their GATT profiles, update devices that have Nordic's OTA update code and copy a devices GATT profile to act as a BLE Server.
We use it for testing and debugging.
Click to expand...
Click to collapse
Ok. I recommend uninstalling nRF Connect anyway. If anything, to rule out the app. How old is your car and the Raspberry Pi? Even though BT 5.2 is backwards compatible, sometimes older BT devices won't work with newer devices. That doesn't account for the S Pen issue though.

I uninstalled nRF connect, and changed all the settings you both recommended. Exactly the same behaviour when I went to leave work. My car stereo would do music but not calls, then when I restarted my phone, it worked. Then when I got home, my S Pen would not connect to my phone, then I restarted my phone and it worked.
Its not a problem of not being compatible, its a problem of something stops working.
Please also note that these devices worked fine together in the past. I am concered that it is either a change made by an update or a Bluetooth chip that is faulty....

OP- Have you debloated at all and if so maybe you've removed something relevant that might be causing these issues?

No, stock image, no OS modification beyond the things that Samsung offers (GoodLock and Stock customisation)
I have our in-house apps for interacting with our equipment (over Bluetooth) installed, but #1 they shouldn't affect anything if they are not open and #2 they don't do this to ANY of our other test equipment.

I would just like to say, that I appreciate the assistance that you are all offering! I have used many forums over the years when looking for support on things and I rarely find a place that is more ready to try and help than XDA forums!

KindarConrath said:
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Click to expand...
Click to collapse
I've seen the issue of the spen disconnecting but only a couple of times and the issue worked itself out within a couple of minutes with me not having to do anything.
I've also have had a couple of wonky issues when connecting a new Samsung phone to my car. I've narrowed down my issue to the fact that when I transfer my data & settings via Samsung smart switch, it includes the details of my Bluetooth pairings. To fix it, I have to go in and delete my Bluetooth phone settings from the car and from my phone and re-pair them.

Rubby1025 said:
I've seen the issue of the spen disconnecting but only a couple of times and the issue worked itself out within a couple of minutes with me not having to do anything.
I've also have had a couple of wonky issues when connecting a new Samsung phone to my car. I've narrowed down my issue to the fact that when I transfer my data & settings via Samsung smart switch, it includes the details of my Bluetooth pairings. To fix it, I have to go in and delete my Bluetooth phone settings from the car and from my phone and re-pair them.
Click to expand...
Click to collapse
As cool as I think Smart-Switch is as a program, I actually never use it when moving from one phone to another. The junk that Google drags with me from one phone to the next is already too much, I like to use a new device as a chance to do some housecleaning. So no old-data oddities here.

KindarConrath said:
I uninstalled nRF connect, and changed all the settings you both recommended. Exactly the same behaviour when I went to leave work. My car stereo would do music but not calls, then when I restarted my phone, it worked. Then when I got home, my S Pen would not connect to my phone, then I restarted my phone and it worked.
Its not a problem of not being compatible, its a problem of something stops working.
Please also note that these devices worked fine together in the past. I am concered that it is either a change made by an update or a Bluetooth chip that is faulty....
Click to expand...
Click to collapse
Hmmm.. Ok. You're probably right about the suspect causes. I know there is a code you can dial to get into diagnostic mode, I just don't know what it is.
The only other option you can try (as a last resort) is to factory reset it. If it is update caused, a factory reset MAY fix it. If you take it to a service center, send it in for repairs, or do a warranty replacement, they're going to factory reset it, or have you reset it.

have you tried running diagnostics in device care ?
or check with this dc
android
Bluetooth test*#*#232331#*#*
samsung
Bluetooth Test Mode*#232331#

I still haven't done a factory reset, but I continue to have the issue.
I have run the BT Test in device care, it always reports good.
I tried the codes, neither of them work as the first one is for vanilla android and the second is for older versions of Samsung firmware.
I've tried completely unpairing from the car radio and re-pairing, disconnecting and connecting from the other device to no avail.

KindarConrath said:
I still haven't done a factory reset, but I continue to have the issue.
I have run the BT Test in device care, it always reports good.
I tried the codes, neither of them work as the first one is for vanilla android and the second is for older versions of Samsung firmware.
I've tried completely unpairing from the car radio and re-pairing, disconnecting and connecting from the other device to no avail.
Click to expand...
Click to collapse
I'm not entirely sold on the idea that it is a hardware fault. It could be a hardware limitation; meaning you cannot connect to more than a certain number of devices simultaneously. I don't know how many BT devices you can connect to at once. I know at least two simultaneous connections (I've only had two simultaneous connections at a time).
You said you have other BT devices in your house other than those three your having issues with. How many are there? How many are you connected to at any given moment?
Is it possible that you have too many simultaneous connections?

When you try to connect to your car.. Did you check under BT connection (your vehicle) to make sure both audio and calls are checked..

doubledragon5 said:
When you try to connect to your car.. Did you check under BT connection (your vehicle) to make sure both audio and calls are checked..
Click to expand...
Click to collapse
Yes, and I've disconnected, reconnected and even unpaired and re-paired the phone to the car.

gernerttl said:
I'm not entirely sold on the idea that it is a hardware fault. It could be a hardware limitation; meaning you cannot connect to more than a certain number of devices simultaneously. I don't know how many BT devices you can connect to at once. I know at least two simultaneous connections (I've only had two simultaneous connections at a time).
You said you have other BT devices in your house other than those three your having issues with. How many are there? How many are you connected to at any given moment?
Is it possible that you have too many simultaneous connections?
Click to expand...
Click to collapse
Unless having multiple connections causes the BT to fail completely, no. Even after turning the car off and walking away, it still will not connect to the S Pen. The only BT devices I use with that phone regularly are:
S Pen, Car (Music & Calls)
At work I develop devices that use Bluetooth and I sometimes connect to them, but only ever one at a time.

Question Some questions about a FYT unit with Unisoc UIS8581A

Hi gents and ladieas alike,
Recently I purchased a unit with the info
{
"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"
}
its a 4gb 8core with 32gb of storage.
Iam extremely new to this and Im yet to figure out what certain things mean so please be gentle
1. Is there any mods worth doing?
2. Is there any better firmware to flash/use to make this unit 'better'
3. I have changed to nova launcher and it seems to be snappier, any questions here?
4. What can I use to re-program buttons on my steering wheel? What it comes with doesnt seem to work.
5. Its actually android 10, not 11, its spoofed I checked.
The Device manufacturer is SPRD
Any help would be greatful!
Thanks in advance

iionas said:
Hi gents and ladieas alike,
Recently I purchased a unit with the info
its a 4gb 8core with 32gb of storage.
Iam extremely new to this and Im yet to figure out what certain things mean so please be gentle
1. Is there any mods worth doing?
2. Is there any better firmware to flash/use to make this unit 'better'
3. I have changed to nova launcher and it seems to be snappier, any questions here?
4. What can I use to re-program buttons on my steering wheel? What it comes with doesnt seem to work.
5. Its actually android 10, not 11, its spoofed I checked.
The Device manufacturer is SPRD
Any help would be greatful!
Thanks in advance
Click to expand...
Click to collapse
It's a FYT unit. Any firmware from a FYT reseller can be used be it for uis7862 or uis8581A. The 8581A is simply the "lighter" less poweful brother of the uis7862. There are some minimal tweaks you have to apply and the lsecupdate binary is different. Of course, if you find a real uis8581firmware it might be better.
1. Only if you have problems, go for a mod.
2. If you do not even know the brand/reseller of your unit, how can anyone advice for better firmware? Next to that: 98% of the firmware for FYT units is identical. Only some differences in "theme" for the launcher (but you use Nova anyway). Your app firmware is of December 2021. There is newer available, but that means it will wipe your system. So far I only flashed newer kernels (read the uis7862 Q&A, etc. thread) hoping they patched the kernel with Android bugfixes and security improvments in the newer kernels, and keep the rest as it is (no AllAppUpdate.bin), thereby also keeping all my settings and 3rd party apps. Again: If you don't encounter errors, there is no need for other firmware. Note: do not flash T'eyes firmware. It is not bad but it does contain quite some restricted firmware making your unit perform much worse.
3. I use Nova as well and I am happy with it. No questions here
4. Do you have a CAN-bus? if so, they are hard-coded and you can't reprogram them unless you use something like my "FYT HW OneKey" app that lets you reprogram part of the buttons.
5. That's correct. The android level is determined by the SDK. The Android version setting (for easy version status) is nothing more than a property and can just as easily be set (or faked) to 17, 31 or 145, etc..

surfer63 said:
It's a FYT unit. Any firmware from a FYT reseller can be used be it for uis7862 or uis8581A. The 8581A is simply the "lighter" less poweful brother of the uis7862. There are some minimal tweaks you have to apply and the lsecupdate binary is different. Of course, if you find a real uis8581firmware it might be better.
1. Only if you have problems, go for a mod.
2. If you do not even know the brand/reseller of your unit, how can anyone advice for better firmware? Next to that: 98% of the firmware for FYT units is identical. Only some differences in "theme" for the launcher (but you use Nova anyway). Your app firmware is of December 2021. There is newer available, but that means it will wipe your system. So far I only flashed newer kernels (read the uis7862 Q&A, etc. thread) hoping they patched the kernel with Android bugfixes and security improvments in the newer kernels, and keep the rest as it is (no AllAppUpdate.bin), thereby also keeping all my settings and 3rd party apps. Again: If you don't encounter errors, there is no need for other firmware. Note: do not flash T'eyes firmware. It is not bad but it does contain quite some restricted firmware making your unit perform much worse.
3. I use Nova as well and I am happy with it. No questions here
4. Do you have a CAN-bus? if so, they are hard-coded and you can't reprogram them unless you use something like my "FYT HW OneKey" app that lets you reprogram part of the buttons.
5. That's correct. The android level is determined by the SDK. The Android version setting (for easy version status) is nothing more than a property and can just as easily be set (or faked) to 17, 31 or 145, etc..
Click to expand...
Click to collapse
Wow thanks for the reply mate you're an absolute damn legend
I'm quite ok with how it functions I don't have any said errors or problems. Good to know some of this info really I mean it thanks again.
Mine is faked however I don't really mind or care I didn't think the components would have been able to power this soc!
I don't have any functions for a cheap Chinese thing it does it job with Waze and music. And occasionally YouTube for a podcast.
Yes sir I do have canbus so I'll be looking for that tool asap. I wanted to reprogram a button for Spotify next song. Nothing special!
Is there ever a time where I should be updating the firmware at all? Like sau year down the track? Or do they stop servicing them?
I was hoping there was a hal9k mod for this one too but I lucked out there

iionas said:
Yes sir I do have canbus so I'll be looking for that tool asap. I wanted to reprogram a button for Spotify next song. Nothing special!
Is there ever a time where I should be updating the firmware at all? Like sau year down the track? Or do they stop servicing them?
I was hoping there was a hal9k mod for this one too but I lucked out there
Click to expand...
Click to collapse
In the settings you can reverse next-previous and/or Vol-Up/Vol-Down if your app/system reacts the other way round, like Spotify does for example. You do not need my app for that.
Like said: so far I have only updated the kernel (6513_1.zip) and nothing else. I only use the unit for navigation, radio and music. Note though that those FYTs still contain an error where they erase your Google contacts if you sync them. It seems the latest T'eyes/Joying firmware doesn't do that anymore, which als means that the somewhat slower resellers like Mekede etcetera should follow soon. (but I don't call from my car. Maybe twice a year)
All those mods are for MTCD/E models, not for FYT.
The only FYT mod is made by @gordgelin but only for real T'eyes models (like mentioned :some T'eyes stuff only works if you have a T'eyes id on your unit).
Tyukta at 4pda makes "a best of" mod where he simply takes the latest kernel and combines it with (what he considers) the best apps (themes actually) from other firmwares (the AllAppUpdate.bin) and he himself also does some theming to apps.

surfer63 said:
In the settings you can reverse next-previous and/or Vol-Up/Vol-Down if your app/system reacts the other way round, like Spotify does for example. You do not need my app for that.
Like said: so far I have only updated the kernel (6513_1.zip) and nothing else. I only use the unit for navigation, radio and music. Note though that those FYTs still contain an error where they erase your Google contacts if you sync them. It seems the latest T'eyes/Joying firmware doesn't do that anymore, which als means that the somewhat slower resellers like Mekede etcetera should follow soon. (but I don't call from my car. Maybe twice a year)
All those mods are for MTCD/E models, not for FYT.
The only FYT mod is made by @gordgelin but only for real T'eyes models (like mentioned :some T'eyes stuff only works if you have a T'eyes id on your unit).
Tyukta at 4pda makes "a best of" mod where he simply takes the latest kernel and combines it with (what he considers) the best apps (themes actually) from other firmwares (the AllAppUpdate.bin) and he himself also does some theming to apps.
Click to expand...
Click to collapse
Cool well thats pretty straight forward I dont have any issues with it, so Ill be leaving it for now and just using your tool for re-programming buttons.
The infamous google contact deletion happened to me, i managed to restore which is really good, however it was annoying. It would of been really good if the google phone app would of worked with it over BT, but it does require a sim (the unit goes support 4g however i dont use a sim).
Ill be ready over the guides today to see for your tools

Hi Gentlemen,
I bought same FYT few days back, succeeded with installation to old MB w211. However i faced problem with Bluetooth connection. It seems like Bluetooth driver or module in head unit is not working properly. I tried to reset factory settings, but still have issue with Bluetooth connection.
Could you please be so kind and share your advice on that. Maybe firmware update is required, but i don't know where to find it out.
I would really appreciate your assistance. Sorry for my English, i am not native speakers.
Thanks in advance Gentlemen.

Hi, is anyone willing to share about what kernel to download? And my Bluetooth is not working recently and shows “null”. Help!!! My android SDK29

how to get the firmware for this unit.

how to get the firmware for this unit.
Uis8581A

saifulmly said:
how to get the firmware for this unit.
Uis8581A
Click to expand...
Click to collapse
One reviews forum or contacts seller.

saifulmly said:
how to get the firmware for this unit.
Uis8581A
Click to expand...
Click to collapse
This unit? Which unit?
That is like: "My phone has a snapdragon-750 cpu". Which firmware should I download?
(select about 25 brands with 200+ models).
Be more specific.

I have a k4811 (8581) and was wondering if there is a way to fix adb to make it work? enabling it in dev options does nothing (the device isn't detected when a laptop is plugged in to USB and adb wifi also rejects connections).... will the FYT MC app work on this device? ex. root button?

Hello everyone, I bought a UIS8581A and I also have problems with bluetooth where I can't connect my ELM327 adapter because I can't even open the bluetooth settings to do so.
The salesman who sold me the radio can't help me right now. Can anyone help me?
Otherwise I have to return the radio to the seller

fabius12 said:
Hello everyone, I bought a UIS8581A and I also have problems with bluetooth where I can't connect my ELM327 adapter because I can't even open the bluetooth settings to do so.
The salesman who sold me the radio can't help me right now. Can anyone help me?
Otherwise I have to return the radio to the seller
Click to expand...
Click to collapse
You should have an app called "Bluetooth" (not inside settings, but an actual preinstalled app).
What happens when you open the Bluetooth app?

I continue the discussion here which talks about my problem with the OBD module
OBD over WIFI and the Internet
I am a recent FYT user on UIS8581A, Android 11 (fake). I have a sim card connected to it that provides internet. When I connect WiFi with OBD, internet connectivity is broken. WiFi without internet has priority in data transmission over SIM card...
forum.xda-developers.com

Yesterday I tried to pair by changing the radio name, password and all the craziest tests I could think of but nothing.
My bluetooth screen is the first photo I attach
When I try to connect one of my three working ELM327 minis, nothing happens, I touch the symbol of the chain to connect, it asks me for the pin of the ELM module, I insert it (it is 1234), after a few seconds a message appears "pairing succeeded". But that's not true, because the chain symbol doesn't change, in Torque I don't see the module (try various versions of torque) and I can repeat the bluetooth pairing indefinitely but it never works.
Any app I use for bluettoth tells me that bluetooth is not working or can't be turned on. But if I connect a smartphone it works.
I do not know what to do
Anyone can help me?
Whats App Image 2023 03 08 at 10 49 16 — Postimages
postimg.cc

I am trying to understand what is happening with my bricked UIS8581A unit.
I flashed the wrong FW. It appears to be completely dead apart from feeling warmth on the rear of the unit when I add power to yellow and red (power and acc) wires while it is grounded (black). I have an update.zip (1.2GB) and a full firmware (3.6GB) from the seller.
The part I am wishing to understand is this:
With the full FW uncompressed in an update folder on a USB stick's root, plugged into the 4pin usb port on the unit, I power the unit on and there is no indication of the USB stick being accessed (red LED on USB stick not lit). I have a USB-A to USB-A cable plugged into the second USB port (6 pin). When I plug the other end of the male to male USB into my laptop (up to date USB drivers installed) that is powered on, the USB stick's LED begins to flash as indication it is being accessed. The LED remains lit for several minutes and then begins to flash (appears to be random flashes). After about 20-30 minutes the USB's LED flashes in a repeating pattern. I have left this USB stick continue whatever it is doing for hours. After disconnecting the laptop from the USB, disconnecting the USB stick, and cycling the power to the unit, the unit is still bricked. Plugging the USB stick back into the 4 pin USB port (with power on), the USB's LED remains unlit indicating it is not being accessed still. Recycling the power to the unit does nothing. Only when I re-connect the USB-A to USB-A cable from the unit to my laptop the USB stick is accessed. Disconnecting the cable, the LED turns off. This is the only life I have witnessed since bricking the unit.
I am wondering why the USB is indicating it is being accessed, only when connected to my laptop.
Does anyone know what is going on here when I connect the unit with my laptop and the USB's LED indicates it is being accessed?
Please don't reply, unless you have specific knowledge.
To all who don't reply, thank you for not wasting my time! It is appreciated...

@S2artb What comes to mind is how you are resetting your unit. I'm not sure if this will work and/or if this applies to your unit. There is a reset hole in the top left of the display. I'm not sure of the exact sequence, but you can try that. Search this or the forum that applies to your unit, if this forum doesn't apply to yours.

S2artb said:
I am trying to understand what is happening with my bricked UIS8581A unit.
I flashed the wrong FW.
Does anyone know what is going on here when I connect the unit with my laptop and the USB's LED indicates it is being accessed?
Click to expand...
Click to collapse
Do not connect your unit with the laptop. This will not help at all.
Which unit do you have? This is the FYT forum and there are many UIS8581A units that are not FYT.
Which wrong firmware did you use?
You tell us absolutely nothing that we need to help you.