Find's Treasure Forums

Welcome to Find's Treasure Forums, Guests!

You are viewing this forums as a guest which limits you to read only status.

Only registered members may post stories, questions, classifieds, reply to other posts, contact other members using built in messaging and use many other features found on these forums.

Why not register and join us today? It's free! (We don't share your email addresses with anyone.) We keep email addresses of our users to protect them and others from bad people posting things they shouldn't.

Click here to register!



Need Support Help?

Cannot log in?, click here to have new password emailed to you

Changed email? Forgot to update your account with new email address? Need assistance with something else?, click here to go to Find's Support Form and fill out the form.

Headphones won't work after update to v1.00

parkgt

Member
I tried the update today. Both my Controller and WS6 showed the V1.0 update. I was never able to pair the WS6. It would show "no coil" and I'd go through the setting to pair it. It would pair for about 30 seconds and then lose the pairing. When the WS6 was on the Vol menu, the "+" and "-" keys work as they were supposed to. The only problem was that the "Settings" and the "Menu" button mimiced the "+" and "-" buttons. I'd have to turn it off and back on to get out of that loop. Then, "Freq Shift" popped up on the screen and I can't turn the WS6 off now; it is locked up. Detecting season for me is quickly coming to a close and I having this major issue. Does anybody have any idea how I can fix this?
Same here!!!
 

Listener

Well-known member
I tried the update today. Both my Controller and WS6 showed the V1.0 update. I was never able to pair the WS6. It would show "no coil" and I'd go through the setting to pair it. It would pair for about 30 seconds and then lose the pairing. When the WS6 was on the Vol menu, the "+" and "-" keys work as they were supposed to. The only problem was that the "Settings" and the "Menu" button mimiced the "+" and "-" buttons. I'd have to turn it off and back on to get out of that loop. Then, "Freq Shift" popped up on the screen and I can't turn the WS6 off now; it is locked up. Detecting season for me is quickly coming to a close and I having this major issue. Does anybody have any idea how I can fix this?
Send it in quick if it’s under warranty. Tell them it is locked up. They will install it and return it. Maybe ask too expedite it politely.
 

T-DUB

Well-known member
I tried the update today. Both my Controller and WS6 showed the V1.0 update. I was never able to pair the WS6. It would show "no coil" and I'd go through the setting to pair it. It would pair for about 30 seconds and then lose the pairing. When the WS6 was on the Vol menu, the "+" and "-" keys work as they were supposed to. The only problem was that the "Settings" and the "Menu" button mimiced the "+" and "-" buttons. I'd have to turn it off and back on to get out of that loop. Then, "Freq Shift" popped up on the screen and I can't turn the WS6 off now; it is locked up. Detecting season for me is quickly coming to a close and I having this major issue. Does anybody have any idea how I can fix this?
Have you tried to hold the + and - button simultaneously to force it off?
 

BigTony

Well-known member
I tried the update today. Both my Controller and WS6 showed the V1.0 update. I was never able to pair the WS6. It would show "no coil" and I'd go through the setting to pair it. It would pair for about 30 seconds and then lose the pairing. When the WS6 was on the Vol menu, the "+" and "-" keys work as they were supposed to. The only problem was that the "Settings" and the "Menu" button mimiced the "+" and "-" buttons. I'd have to turn it off and back on to get out of that loop. Then, "Freq Shift" popped up on the screen and I can't turn the WS6 off now; it is locked up. Detecting season for me is quickly coming to a close and I having this major issue. Does anybody have any idea how I can fix this?
That sucks, but it’s only a software update away from working.
I had a similar problem back at .71, I couldn’t pair the headphones.
I reinstalled the remote then the headphones and it worked. Re- read instructions and take your time. Install remote first with the coil Near by. Than headphones. Use the single cable for headphones.
Back in .71 I wasn’t the admin on my pc so that screwed things up. This time I used Edge software.
Best of luck Tony NJ
 

Listener

Well-known member
Have you tried to hold the + and - button simultaneously to force it off?
It’s worth a shot, but my experience with that is it must be in A program detect screen to do that. Best shot is to re-install the update until successful or send it off. They will fix it or replace it with the updated version.
 

DigDog

Well-known member
Couldn’t hurt to do a reinstall might just unlock it. Probably first thing they would just do if you sent it in. Best of luck
 

targits

Well-known member
Why would you want one unit on one version and the other unit on another
I like to compare versions as they vary in little ways.for example prog 10 on v71 is good on steel junk ,but on v1 is not so good on steel junk like a horse shoe .v1 gives it a good tone and a good tid meaning I waste time digging crap
 

DigDog

Well-known member
I use v1 puck in the plug in 3rd party headphones and can keep v71 puck on v71 fones
That’s actually a good idea having the benefits of both versions. Just an extra set of headphones and you can split up the detector. This detector seems to have endless possibilities and customization options lol
 

BigTony

Well-known member
I was having same issue. Repeated the install. It took and everything was fine. And having tried the upgrade, I have to say I really like it.
I agree with liking the update on land. I’ll hold my opinion until I hit a beach, hopefully soon.
Tony NJ
 

Ytcoinshooter

Well-known member
If your device is not seen or recognized when you click connect in the update process start again closely watching the sequence on the screen. Using a MacBook Pro 2012 1/2 running chrome browser I updated yesterday to version 1.0 pretty smoothly. I did have to repeat the process carefully ( use the single cord ) for both the WS6 and WSA2 XL’s. It was my error trying to rush the sequence.
I got everything working - WSA2 XL, WS6, Mi-6 and the D2 master as it should. Remember to unpair and repair headphones to D2 master & WS6 . Only one set of headphones can be paired to a master D2 or WS6. So I chose to pair the WSA2 XL to the WS6 and Deus 2 remote. I tested using the WS6 as master to the WSA2 XL then I shutdown the xl’s and the WS6 took over audio seamlessly da coil a beeping. If I need to in hot weather I can pair the WS6 as slave to the D2 remote. I love the WSA2 XL’s so far no plans to take them off at all.
It was sooo nice not having g to borrow a win pc like last week to get to version .71 from .6 on my new D2. It came with 6. I’m just getting some hours on it and also working in my yard over the test plot. This is one very cool detector and nowadays I need the light ergonomics.
 

DigDog

Well-known member
Sometimes in the update or pairing process we get confused or just not paying close attention and miss one step or do it in the wrong order and then realize and it works just fine. Happened to me couple times then you are like duh lol.
 

buckeeeee

Well-known member
Sometimes in the update or pairing process we get confused or just not paying close attention and miss one step or do it in the wrong order and then realize and it works just fine. Happened to me couple times then you are like duh lol.
That is so true, thinking you know how to do it and just wing it, read and take your time. Today I received my WSAII headphones and right out of the box I hook them up to my Deus 2 and get message "Update Headphones", so I think no problem I Updated everything two days before so I break out the single cable and nothing all three three times with message "No Compatible device found", so I sit back and think what I did wrong. First thing, maybe I need to fully charge the headphones, so after 2 hours of charging I try again. I follow the directions slowly reading and watching and notice they push the minus button first and then the plus button and the light starts to rapidly blink and then it turns solid and I release the buttons, plug cable into the headphones and then into my computer and click on the next arrow and BAM I highlight the 1.0 and update.
This is now my main and backup detectors (see pics), I used my Simplex upper and lower rod ( XP Deus Metal Detector Plastic Mounting Bracket Kit for Remote Control) and mounted my WS6 with 13 inch coil and WSAIIXL as backup and Deus 2 remote with 11 inch coil and WSAII headphones as main detector.
 

Attachments

  • 20230519_180230.jpg
    20230519_180230.jpg
    1 MB · Views: 67

Ytcoinshooter

Well-known member
That is so true, thinking you know how to do it and just wing it, read and take your time. Today I received my WSAII headphones and right out of the box I hook them up to my Deus 2 and get message "Update Headphones", so I think no problem I Updated everything two days before so I break out the single cable and nothing all three three times with message "No Compatible device found", so I sit back and think what I did wrong. First thing, maybe I need to fully charge the headphones, so after 2 hours of charging I try again. I follow the directions slowly reading and watching and notice they push the minus button first and then the plus button and the light starts to rapidly blink and then it turns solid and I release the buttons, plug cable into the headphones and then into my computer and click on the next arrow and BAM I highlight the 1.0 and update.
This is now my main and backup detectors (see pics), I used my Simplex upper and lower rod ( XP Deus Metal Detector Plastic Mounting Bracket Kit for Remote Control) and mounted my WS6 with 13 inch coil and WSAIIXL as backup and Deus 2 remote with 11 inch coil and WSAII headphones as main detector.
You nailed it…the minus button first then the plus button. I watched the on screen demo carefully realizing I rushed that part. Spent my life before retiring in computer mainframes, desktops and networking…After failing to update the WS6 & WSA2XL the first tries…I figured I was the PEBCAC…and slowed down. (Problem Exists Between Computer And Chair).
I like your setup of main & back up detectors. I’m going that way eventually by picking up a used telescopic stem then add an 11” coil. I have the rest of the bits already to mount the puck.
 

Kapok

Active member
You nailed it…the minus button first then the plus button. I watched the on screen demo carefully realizing I rushed that part. Spent my life before retiring in computer mainframes, desktops and networking…After failing to update the WS6 & WSA2XL the first tries…I figured I was the PEBCAC…and slowed down. (Problem Exists Between Computer And Chair).
I like your setup of main & back up detectors. I’m going that way eventually by picking up a used telescopic stem then add an 11” coil. I have the rest of the bits already to mount the puck.
We call it a PICNIC error. Problem In Chair Not In Computer. :p
 
Top