Hi,
I have a problem with my new Sony SW2 during setup.
- Pairing buetooth -> done. Then the watch asks me to install SmartConnect (SC's icon and phone's icon)
- Install Smart Connect -> done. The notification in the watch is still asking me to instal SmartConnect.
- Install SW2 app -> done. Nothing happened. The notification in the watch is still asking me to instal SmartConnect.
Retry again, uninstall everything, unpair, etc. Still same..
Kindly help.
I can use my Sony SW2 now.
What I did:
- used another phone (Huawei P7), it was working fine, pairing, installing Smart Connect, installing Smartwatch 2 app.
- reset the watch
- used back my Lenovo P70. It was directly fine. No more problem as I've mentioned before.
Thank you for your attention.
Hi All,
Installed the latest ResurrectionRemix-M-v5.7.0-20160616-jfltetmo.zip on my S4 and cannot connect to Mercedes Benz navigation. Both system can see each other. No errors get displayed on the phone pairing devices. MB Command always displays an error "Access denied". There no differences if paring initiated from each devices.
Tried factory reset CM13 - same issue.
Tried factory reset and RR 5.7.0 after that - same issue.
Tried BlueDUN - couldn't see even any connection attempt.
Tried to connect to iPhone - iPhone reported an error - "Samsung Galaxy S4 not supported", no errors on S4.
Tried to connect to ASUS Android tablet - all worked, could send a file.
Thanks for suggestions.
I've been having problems connecting using the display mirroring option on any rooted & UnRooted FTV(S) on FireOS 5 with all of my devices. At first I thought it was a problem with the FW on my phone & tablets. But after some testing & catlogs. It seems the problem is with any version of the FTV(S) FireOS 5 FW.
I have a non-rooted phone that runs Marshmallow. And some rooted tablets that run different Android versions (CM 12.1, Nexus ASOP, etc). I CAN connect any of my devices to my rooted FTV1 on the last PreRooted FW of Fire OS 3. It works flawlessly. It doesn't even request authentication. I just have to click on the name of the FTV(S) on my phone or tablet for it to connect.
But once I try the same on any rooted or non-rooted FTV(S) on FireOS 5. My phone or tablets never see any FTV(S) if it's on FireOS 5. I even turned on the "wireless display verification" option in the developers menu in case that was the problem but it still acts the same way.
Before reporting in this bug into Amazon. I would like to confirm the bug. And I would like for those of you that find the same problem. To join me in reporting it. So we can get this fix as soon as possible.
To test the display mirroring aka Miracast option. All you need to do is turn on the feature on your FTV(S) by holding the HOME button until you get the shortcut menu. And choose "Mirroring". Then on your phone go to your Setting Menu. Choose " Display ". Then look for "Cast", "Mirror Cast", "Miracast" or something similar. Then either enable it thru the toggle ON or thru the 3 dot Menu option on the upper right side, "Enable wireless display". Depending how your device incorporates the wireless display option. You should see the name of your FTV(S) & you should be able to click it & choose to connect. Now your TV screen should tell you it's connecting until it starts mirroring your device. You can just hit back to disconnect.
Then please post your detailed experience below. I will get the ball rolling by posting my info on the next thread. Please try & copy the layout of the reporting.
Thanks for all your help.
FTV 1: Successfully connected with Phone or Tablet.
Rooted: Yes
FireOS: FireOS 3
FW: PreRooted FW v51.1.63_user_516012020
Any other Info:
Device 1: Successfully saw & connected with FTV.
Type: Phone
Model: ZTE Z981
Rooted: No
FW: Marshmallow - Android 6.0.1
Wireless Display Certification: Worked with it ON & OFF. (Same successful results)
Any other Info:
Device 2: Successfully saw & connected with FTV.
Type: Tablet
Model: Amazon 7" Tablet
Rooted: Yes
FW: Fire Nexus 20170208 - Android 5.1.1
Wireless Display Certification: Worked with it ON & OFF. (Same successful results)
Any other Info:
______________________________________________________________
FTV 2: Never saw or tried to connected with Phone or Tablet.
Rooted: Yes
FireOS: FireOS 5
FW: PreRooted FW v5.2.1.1_r1
Any other Info:
Device 1: Never saw or tried to connected with Phone.
Type: Phone
Model: ZTE Z981
Rooted: No
FW: Marshmallow - Android 6.0.1
Wireless Display Certification: Did NOT work with it ON or OFF. (Same results)
Any other Info:
Device 2: Never saw or tried to connected with Tablet.
Type: Tablet
Model: Amazon 7" Tablet
Rooted: Yes
FW: Fire Nexus 20170208 - Android 5.1.1
Wireless Display Certification: Did NOT work with it ON or OFF. (Same results)
Any other Info:
______________________________________________________________
FTVS 1: Never saw or tried to connected with Phone or Tablet.
Rooted: No
FireOS: FireOS 5
FW: FW v5.2.1.2 (562254320)
Any other Info:
Device 1: Never saw or tried to connected with Phone.
Type: Phone
Model: ZTE Z981
Rooted: No
FW: Marshmallow - Android 6.0.1
Wireless Display Certification: Did NOT work with it ON or OFF. (Same results)
Any other Info:
Device 2: Never saw or tried to connected with Tablet.
Type: Tablet
Model: Amazon 7" Tablet
Rooted: Yes
FW: Fire Nexus 20170208 - Android 5.1.1
Wireless Display Certification: Did NOT work with it ON or OFF. (Same results)
Any other Info:
Is this me? Plz help
Sent from my Amazon KFFOWI using XDA Labs
firetv559 said:
Is this me? Plz help
Click to expand...
Click to collapse
Translate ?
If your saying you are having the same problem. I am requestion detail info on your FTV(S) & what devices you tried to connect to. Like I showed on Post #2.
Recently some users including me are having issues with BT Connection, device search, setting device name and making changes persistent.
BT MODULES THAT IT WAS TEST ON:
SD-968 - [HA] [MCU MTCE 2.75] Firmware 20180201 and few earlier = WORKS
MD725 - [??] [MCU ???] Oreo Firmware = DO NOT WORK (According to feedback) LogCat needed to see if Firmware communicate with BT Module at all.
METHOD 1 (SHORTER):
1. Force Stop BT app
2. Clear DATA and CACHE for BT app
METHOD 2 (LONGER):
Here are the steps I've done to make it work.
1. Boot device (restart if it was not in deep sleep)
2. Directly go to system BT settings (drop notification and tap on BT)
3. Set Device name and PIN
4. Press refresh
5. Go to Home Screen (Home Button)
6. Open BT App -> Configuration
7. Name and PIN should be entered now
8. Disable/enable Auto Connect and exit app
9. reenter app and configuration to enable Auto connect
10. Make sure that all previous BT profiles for HU are deleted on phone and that phone is visible for all devices (usually when BT configuration is open device is visible)
11. Try to search for devices. It should fail (it failed for me)
12. Go to factory settings
13. Change BT Device even it is wrong one (I have SD-968 I changed to MD725)
14. Tap Apply -> Exit -> CANCEL on reboot prompt (without doing step 13 there will be no scheduled restart)
15. Reenter Factory settings and set correct BT Module (I have SET SD-968) Tap Apply -> Exit -> and Confirm REBOOT
16. After Reboot Go to BT App and try to search for phone it should be found (make sure it is visible like in step 10)
17. If all is OK you should see the phone and you should be able to use it normally (it worked for me)
Attached pictures of some steps for METHOD 2.
NOTE: I'm ATM at HA 6.0.1 Firmware from 20180201 and issue happened after upgrade. Also from what I see Users have same issue with and after Oreo update. Hope I helped
Thanks for the info. Have you tried this method also for oreo rom as well ?
A step that worked for me was to clear data and cache for bluetooth app..
julien_blanche said:
Thanks for the info. Have you tried this method also for oreo rom as well ?
Click to expand...
Click to collapse
Haven't updated to Oreo yet.
Phycopat said:
A step that worked for me was to clear data and cache for bluetooth app..
Click to expand...
Click to collapse
Good point it didn't worked for me but, it can also help. Added to main post.
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
I definitely have the BT issue. I have an Xtrons(GS) MTCD/E PX5 Oreo and an Xtrons brand OBDII. They won't talk or disconnect. I'll try this tomorrow morn and report back.
jdisco1 said:
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
I definitely have the BT issue. I have an Xtrons(GS) MTCD/E PX5 Oreo and an Xtrons brand OBDII. They won't talk or disconnect. I'll try this tomorrow morn and report back.
Click to expand...
Click to collapse
I have same GS MTCE 2.75 PX5 OREO but an old OBD2, give HU same password as OBD2 adapter..
jdisco1 said:
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
Click to expand...
Click to collapse
Point of 12-15 is that HU re init Module itself along with software. Not sure if it works that way on MTCD/E but usually it works on modular systems.
Tried with PX5 oreo installed with no luck. Both methods are not working for me.
PekeMM said:
Haven't updated to Oreo yet.
Click to expand...
Click to collapse
What???(I thought that this was a trick for oreo)
In my unit BT(MD725) works without any tricks for MM.
I tried your trick with 2 kinds of oreoROM(HA and GS) but BT did not work.
Thanks anyway
I'm sorry, but as I wrote I have SD-968 BT module not MD725. I'll update main thread with so far know to work devices.
Any news?
JonatanP said:
Any news?
Click to expand...
Click to collapse
Not that I know, I'll be back from Trip on Sunday, so I hope I'll finally finish the tests and upgrade to Oreo in April.
seems to be the same
The solution is to go back to android 6, the problem is that it is not as fluid in my case as android 8.
Hi, same problem here....
I can not use my ODB2 connector on my Android 8 radio either.
Is there an adapter that works?
Is there a trick to make it work?
Greetings and thank you!!
Hi..any update on how to get the bluetooth working on android 8..
Mtcd ksp px5
warata said:
What???(I thought that this was a trick for oreo)
In my unit BT(MD725) works without any tricks for MM.
I tried your trick with 2 kinds of oreoROM(HA and GS) but BT did not work.
Thanks anyway
Click to expand...
Click to collapse
if you still have android 8 installed, try going to factory setting and change the BT Device even it is wrong one (anything other then MD725) tap apply and exit and reboot.
after reboot change the BT device back to the original one (MD725) tap apply and exit and reboot.
after reboot go to the system BT and try to search if the phone name appears let me know.
i still didn't try the above method on android 8, but if anyone with MD725 module is still using android 8 please try and update us.
thanks
i was having problem with bt too...
here you can read my post https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
now i have Oreo Rom in a px5 board (32+4) with MD725 BT module working well
macoloco said:
i was having problem with bt too...
here you can read my post https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
now i have Oreo Rom in a px5 board (32+4) with MD725 BT module working well
Click to expand...
Click to collapse
Thanks, you said in that thread ".i have found a directory where all manufactures update.zip where listed
Go there , pickup last LM version" could you say where this directory is? Once there what do you do with that file?
bjt2 said:
Thanks, you said in that thread ".i have found a directory where all manufactures update.zip where listed
Go there , pickup last LM version" could you say where this directory is? Once there what do you do with that file?
Click to expand...
Click to collapse
i wrote all my procedure here
https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
and here
https://forum.xda-developers.com/showpost.php?p=77538182&postcount=796
Dasaita MMCNP - BT connection problem
Hi, I have Dasaita HA2106-V840-8 a problem with Bluetooth connectivity. First time I managed to connect my phone to Dasaita MMCP (car_kit), but after a few days the devices failed to connect. I guess my device has embedded SD968 BT chip, in accordance with the description.
When I enter the name of the device and new PIN in BT settings, and then turn on finding the device, they are not visible to each other. I tried this other day too, but when I turned MMCP, entered settings was gone (not memorized). No name, no PIN, but also there is no connection. Search doesn't have results. At the end I tried to unpair devices and pair them again, but I get a message on my phone "Unable to communicate with CAR_KIT".
When I entered in settings for BT (settings/car/factory setting/application-choose...) it was set to WQ_BC6. And then I tried to set up SD_BC6, reboot, search BT, nothing was found again. Then I returned to WQ_BC6, reboot, search BT, without success. In the end, I tried to set up SD968, but it's not worth it anyway, MMCP does not see a mobile phone. I also tried several phone models without success. I also went to the BT application and clear data and cache, but always the same thing - BT devices do not see each other. I'm not even sure BT is ON because it doesn't have a special slider to move On/Off.
What should I do? Please help me!
Hello all,
After finally updating my PX5 to the latest MCU and firmware (according to Hall9k) using his mod application, I am now experiencing low volume on everything (radio on max is pretty low volume when you're on the highway) and bluetooth settings always reset to empty settings and will not find my phone and my phone will not find the PX5.
I've tried resetting wifi and bluetooth settings, no luck. I've tried resetting the unit back to factory settings, erasing all data, no luck. I found a post regarding the bt issue and followed all his steps (changing the bt device and reverting back to it, etc.) but no luck. I found a post which said the device somehow needed to be an other one than previously set, so I've tried all the devices in the list, but no luck. Only at the parrot device, the bt settings were automatically reverted back to factory default (Car... something), but it wouldn't connect. Normally my device was on SD-968 I believe (not currently in my car).
So, that's my main issue now. How can I get BT to connect, without rolling back to Android 6.0.1? Because on 6 it worked.
And second, how can I get the volume louder? Again, after updating the volume somehow seems limited.
I don't want to go back to 6, if there's an other way, because 6 had its own problems...
I'm really lost here and have spend many hours in the car, trying everything I could find online (even manually clearing cash and storage of the bt settings, etc). There must be a way this should be fixed.
My Android 9 fw is from November (Hal9k send that one to me)
My MCU is MTCE_GS_V3.17bd_3