Amazfit Sport Watch (Pace) BT/wifi issue. The database of faulty watches. - Amazfit

1602 chinese watches:
Raúl |CN | 14357/000594xx | Aliexpress | Feb 2017 | Feb 2017
simoec | CN | 14357/00032xxx | Gearbest | Feb 2017 | March 2017
Igor | CN | 14357/00030xxx | Gearbest | March 2017
Antonino | CN | 14357/000040xx | Gearbest | Jan, 30 2017 | Feb 20, 2017
Marco | CN | 13426/00049193 | Gearbest | Nov 14, 2016 | Jan 20, 2017
Luc | CN | 13426/000478xx | Aliexpress | Nov 24, 2016 | Jan 2017
Claudio | CN | 13426/00042991 | Gearbest | Dec 12, 2016
Alexandr | CN | 13426/00042837 | Aliexpress | Sep 2016 | Dec 2016
José | CN | 13426/00039422 | Gearbest | Nov 24, 2016
Zdenek | CN | 13426/00038951 | Gearbest | Nov 16, 2016
Fabio | CN | 13426/00038545 | Gearbest | Dec 20, 2016 | Jan 30, 2017
FalconFour | CN | 13426/000371xx | friend's junk shelf | Mar 24, 2017 | Apr 19, 2017
Patrik | CN | 13426/00033712 | Gearbest | 12 Dec 2016 | Jan 2017
RockGenox | CN | 13426/00032571 | Gearbest | Nov xx, 2016 | Dec xx, 2016
John | CN | 13426/00032251 | Gearbest | Dec 14, 2016 | Feb 13, 2017
Filippo19 | CN | 13426/00028483 | Gearbest | Nov 13, 2016 | Jan xx, 2017
Thomas | CN | 13426/00021214 | Aliexpress | 06 Oct 2016 | Jan 2017
Jesus | CN | 13426/000109xx | Gearbest | Nov 11, 2016 | Jan 10, 2017
1612 US Pace watches:
fazz33 | US | 16121649002569 | amazfit.com | Feb 21, 2017 | March 05, 2017
George | US | 161216490021xx | amazfit.com | Dec 19, 2016 | ~ Jan 20, 2017
SAIT18 | US | 1612164900015xx | amazfit.com | 26 Dec 2016 | Jan/Feb 2017
Stefano | US | 161216490008xx | amazfit.com | 24 Dec 2016 | 10 Mar 2017
SM | US | 161216490012xx | amazfit.com | ~Dec 22, 2016 | ~Feb 26, 2017
Adam | US | 16121649000450 | amazfit.com | Dec 13, 2016 | Jan 5, 2017
Daniel | US | 16121648000xxx | amazfit.com | Dec 28, 2016 | Jan 25, 2017
Vode | US | 161216480000xx | amazfit.com | Dec 22, 2016 | Jan 4, 2017
Craig | US | unknown| amazfit.com | Dec 20, 2016 | Jan 9, 2017
CSG | US | unknown | amazfit.com | ~December 24, 2016 | ~January 2, 2017

We started collecting this data on FB group. Please add yours if your watch turned to be faulty, using this scheme:
Name (nick) | version (CN or US) | serial number | supplier | date of purchase | date of failure
If you are concerned about privacy replace the last 2 digits of your S/N with “xx”.
Thank you in advance.
What is the BT/wifi issue? It manifests itself when after some time of working good bluetooth connection range of your watch permanently drops to about 30 cm from a phone. WiFi range also drops accordingly. Basically you're losing all wireless communication - no notifications, failed wifi test.

Latest info:
Chinese watches - all faulty units have their S/N starting with 13426/... or 14357/...
English watches - all faulty units have their S/N starting with 16121648 or 16121649. No failure reports for newer 16121651 yet. There are also some older 1612 ones with mixed numbers from chinese serials, we don't know about their failures.
There is only one "unofficial" company statement made by Huami representative on FB group. The company is aware of the issue, they claim only less than 1% watches are affected and they already made various software and hardware "improvements".
Chinese users are getting replacement watches very quickly. But their watches still fail again with the same issue, there are cases of 2nd or even 3rd replacement procedures. Draw you own conclusion if the supposed hardware "improvements" were actually done by Huami...
The most probable cause of failure is electrostatic discharge coming from human body in certain circumstances, eg. undressing. Any modern electronic device should comply with industrial standards for that matter (IEC 61000-4-2) and should withstand static discharge. As the watch is product of China - probably it was never tested according to the standards.

Hi,
when my wife come back, check the serial of the amazfit. Same problem but only with software update apparently.
I think is software problem and not hardware problem... but is only my thinking!

The problem is very well recognised on chinese Huami forum. If reported, chinese moderators no longer offer any software/firmware related solutions, they provide a phone service number to arrange replacements. There are MANY replacements going on there and, sadly, replaced watches fail again.
Huami refuses to give any information about what is going on.

I have seen on huami forum....
Anyone have returned the Watch at gearbest?

There are already cases in progress. Basically if the watch failed within 45 days period from receiving it, Gearbest offers full refund. Theoretically, as no one got the money back yet In other cases they offer "repair". They claim they will contact Huami for repair instructions and they repair watches themselves(!). That kind of info one of us got from them.

calzone123 said:
They claim they will contact Huami for repair instructions and they repair watches themselves(!)
Click to expand...
Click to collapse
They are a bit early for April's fools aren't they?
The fact is, they know s**t and that's why they plan to repair them. There will be a technician checking the function and they will get the information that it can not be repaired.
You need proper tools to disassemble the watches and to mount them and check if they are sealed properly.

calzone123 said:
Latest info:
Chinese watches - all faulty units have their S/N starting with 13426/... There is a new production batch starting with 14357/... and no reports about failures yet.
English watches - all faulty units have their S/N starting with 16121648 or 16121649. No failure reports for newer 16121651 yet. There are also some older 1612 ones with mixed numbers from chinese serials, we don't know about their failures.
Click to expand...
Click to collapse
Mine starts with 14357 and doesnt have issues until now.

I'm searching inside dmesg and firmware...
[email protected]:/ $ cat /system/lib/firmware/wifi/
bcm43438.cal fw_43438_a0 fw_apsta_43438_a1
cal_43438_a0 fw_43438_a1 fw_bcm43438.bin
cal_43438_a1 fw_43438_a1_test fw_bcm43438_apsta.bin
why there is different firmware?
-rw-r--r-- root root 370594 2008-08-01 14:00 fw_43438_a0
-rw-r--r-- root root 359859 2008-08-01 14:00 fw_43438_a1
-rw-r--r-- root root 329723 2008-08-01 14:00 fw_43438_a1_test
Anyone have rooted watch can test to change with other?
With a rapid search i think the chip of wifi/bluetooth is the same of raspberry pi 3.
Thanks

We have 14357 and 161215100 no Bt/wifi issues. The 14357 was accidentally dropped in the shower, still no symptoms.

Hi all, now that amazfit watch is available again at gearbest, I've asked them if their stock is still 13426/xxx.
No meaningful answer unfortunately. But they are so kind that now I feel guilty
Your original question is "Dear Sirs, according to a user survey there are a lot of bluetooth/wifi issues related to devices from production stock whose serial numbers start with 13426/... (see this thread: https://forum.xda-developers.com/sm...azfit-sport-watch-pace-bt-wifi-issue-t3560649 ) May you please confirm that the devices you're selling are not from this faulty stock? Many thanks in advance, Fabio"
Here is the answer from Our Customer service Team:
"
Hello DrBourbon,
I am sorry
* All the item have been tested seriously before sending to our clients.
* Fast delivery for catching the market.
* Our professional sales will give you best support in the business for any questions.
* We deeply know quality is our company’s life.
Click to expand...
Click to collapse

Unfortunately we got the first faulty chinese watch with 14357/... serial number.
There are some speculations as to the cause of the failure and one of them is ESD (electrostatic discharge). Some people report their watches happen to go into "shutdown confirmation" screen by their own. It was my experience too, before my watch failed.

I apologize, but haven't facebook
My info
Filippo19 | CN | 13426/00028483 | Gearbest | Nov 13, 2016 | Jan xx, 2017

RockGenox | CN | 13426/00032571 | Gearbest | Nov xx, 2016 | Dec xx, 2016

fazz33 | US | 16121649002569 | Amazfit US website | Feb 21, 2017 | March 05, 2017

drbourbon said:
No meaningful answer unfortunately. But they are so kind that now I feel guilty
Click to expand...
Click to collapse
Yes they are always super friendly but mostly only repeat what is alreday said in the product description (which is total nonsense sometimes) or just write stuff that doesn't help at all.

Updated database and info in 2nd/3rd post.
As more and more watches with new S/N 14357... fail it means Huami did not fix the problem.
The most probable cause of failure is ESD (electrostatic discharge).

Has anyone got any support from the Amazfit pace website? I've put a support case in about 2 weeks ago and haven't had a single reply back.

They hardly ever answer emails. Much better chance to get in touch on their Facebook group: https://www.facebook.com/amazfit/?fref=ts

Related

Scancodes for Prophet - WM6

I found, that its very annoying having different Scancodes in WM5 and WM6. As for Wargus or Duke3D, there's no integrated Mapping-Setup.
I have no idea, if the ROM matters, but i used Transformer 1.1
So here's my little contribution:
Code:
/---------------------\
/ 72 c4 76-75 c3 \
|c1 70 +-------------+ |
| | -PROPHET- | |
| 25 | Keymap WM6 | |
|28 26 | HEX | |
| 27 | | |
| | -RiWaLE- | |
|c2 71 +-------------+ |
\ 73 /
\---------------------/
for comm-button pressed 2-3 secs: c5
and in decimal:
/---------------------\
/ 114 196 118-117 195 \
|193 112+-------------+ |
| | -PROPHET- | |
| 37 | Keymap WM6 | |
|40 39 | DEC | |
| 41 | | |
| | -RiWaLE- | |
|194 113+-------------+ |
\ 115 /
\---------------------/
for comm-button pressed 2-3 secs: 197
i hope someone can use this!

[Q] MOTOROLA® DROiD™RAZR™ MΛXX | Verizon® | USΛ 3G/4G Signals Not Receive !

[Q] MOTOROLA® DROiD™RAZR™ MΛXX | Verizon® | USΛ 3G/4G Signals Not Receive !
My MOTOROLA® DROiD™RΛZR™ MΛXX | Verizon® | USΛ RUNNiNG ΛNDROiD 4.1.2 iS NOT RECEiViNG 3G\4G Signals,I MESSED UP THE DEFAULT CONFiGURATiONS ON MOTO.SERViCE MENU. . . IT RECEiVES ONLY 2G.WiFi.BT iS OKEY ! HOW TO RESTORE MY DATA SiGNALS. . .THANKX FOR CARiNG DEAR ALL. . .:laugh:
SYSTEM VERSiON
98.72.16.XT912.Verizon.en.US
BASEBAND VERSiON
CDMA_N_05.21.00R LTEDC_U_09.1D.00
KERNAL VERSiON
3.0.8-gbacb1cf
[email protected] #1
SMP PREEMPT Fri Feb 1 20:50:31 CST 2013
BUiLD NO.
9.8.20-72_VZW-16

Why do latest Android Security Update firmwares have old file dates?

I'm not a noob, but I am confused about something that I think should be simple:
Monthly Android Security Updates
I apparently have to install these manually, since OTA updates fail supposedly because I run a rooted phone w/ custom bootloader/recovery.
Google has been making it a point to release security patches every month:
http://source.android.com/security/bulletin/index.html
March 2016's is here:
http://source.android.com/security/bulletin/2016-03-01.html
On that page they say:
"The Nexus firmware images have also been released to the Google Developer site.", with a link to:
https://developers.google.com/android/nexus/images
I download firmware for my Nexus5 Hammerhead MMB29K:
https://dl.google.com/dl/android/aosp/hammerhead-mmb29k-factory-1943f0f5.tgz
I unzip that file and list the contents:
Code:
Pvs-MacBook-Pro:hammerhead-mmb29k pv$ ls -la
total 1218408
[email protected] 8 pv staff 272 Nov 18 15:44 .
drwx------+ 28 pv staff 952 Mar 9 10:55 ..
[email protected] 1 pv staff 3195188 Nov 18 15:44 bootloader-hammerhead-hhz12k.img
[email protected] 1 pv staff 974 Nov 18 15:44 flash-all.bat
[email protected] 1 pv staff 845 Nov 18 15:44 flash-all.sh
[email protected] 1 pv staff 798 Nov 18 15:44 flash-base.sh
[email protected] 1 pv staff 574092301 Nov 18 15:44 image-hammerhead-mmb29k.zip
[email protected] 1 pv staff 46515712 Nov 18 15:44 radio-hammerhead-m8974a-2.0.50.2.28.img
Pvs-MacBook-Pro:hammerhead-mmb29k pv$
So, my question is:
Why does Google say that the March 2016 Security Updates Nexus devices are available for download, but the files themselves are dated November 2015?
This begs more questions:
Are the March 2016 Android Security Patch Levels really in the 6.0.1 November 2015 dated files?
If not, then why does Google say that I can get the March 2016 updates for my Nexus 5 from the firmware download page?
How do I non-OTA update my Nexus5 to the latest Security Patch?
Thanks!
Pv

Question Csc questions

Hi!
I have a few questions regarding CSC on this device (well, S22 in general I suppose):
I live in Sweden, so I have the Exynos version with EUX CSC if that matters.
I did not insert a SIM on first launch, so I got no "operator branded" CSC/firmware. My software line looks like this:
{
"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"
}
1. If I had inserted the SIM first, I think I would've gotten a "NEE" somewhere in there. Does it matter that I didn't? Because I have worse cell reception now than on my old Huawei P20. Could it be that it isn't "optimized" for my operator?
2. If it does matter, can I get it there by doing a factory reset and starting over with the SIM inserted?
3. Ideally I would like to use a CSC that has call recording (legal in SE), by what I've read SEK (Ukraine) is best? I don't use Samsung Pay or use a Watch, so that bit doesn't matter.
I did find a video on YT (
) that says Caller ID won't work though. True?
What does that mean exactly?
Does it mean I won't see who is calling ("Unknown Caller" or something on the incoming call screen, instead of the number)?
Or maybe it won't register that 07xx is a Swedish "mobile area code" and display +46 in front of all numbers like a foreign number?
Perhaps my number won't be shown to others?
Or something else?
Thanks in advance!
SamFw Tool 4.7.1 - Remove Samsung FRP one click
Hi Today, we introducing SamFw FRP Tool version 4.7.1 Main function: Remove FRP with one click Change CSC with one click Remove FRP for new se...
samfw.com
Use this tool to get your phone's supported CSC list. Then use the software to change it.
Takes seconds, for me no data was wiped and OTAs work perfectly. Changed on both my S22+ and my Tab S8+.
Not sure about all the questions about called id etc, just giving you an easy option to change. I see no problem of changing back if you feel it was better before.
DubelBoom said:
SamFw Tool 4.7.1 - Remove Samsung FRP one click
Hi Today, we introducing SamFw FRP Tool version 4.7.1 Main function: Remove FRP with one click Change CSC with one click Remove FRP for new se...
samfw.com
Use this tool to get your phone's supported CSC list. Then use the software to change it.
Takes seconds, for me no data was wiped and OTAs work perfectly. Changed on both my S22+ and my Tab S8+.
Not sure about all the questions about called id etc, just giving you an easy option to change. I see no problem of changing back if you feel it was better before.
Click to expand...
Click to collapse
Yeah, I tried SamFW today.
Caller id seems to be that it searches for unknown numbers and shows who it is. Don't need that, so I followed the YT video.
Changed to SEK, and call recording works and all else seems good so far.
Apparently (according to Samsung support, so not 100%) the S22 has no "branded EUX" anymore, at least for Nordic countries and our other local Swedish carriers, he wasn't sure about the rest.
I'm not entirely sure I can go back to unbranded EUX again like before. I guess if I leave the field empty in SamFW, but that seems dangerous to try on a brand new phone.
Haven't tried googling this, but how would I get the list of CSCs in SamFW? What Button to press? There was no scroll list, just a text field next to the button?
filigran said:
Yeah, I tried SamFW today.
Caller id seems to be that it searches for unknown numbers and shows who it is. Don't need that, so I followed the YT video.
Changed to SEK, and call recording works and all else seems good so far.
Apparently (according to Samsung support, so not 100%) the S22 has no "branded EUX" anymore, at least for Nordic countries and our other local Swedish carriers, he wasn't sure about the rest.
I'm not entirely sure I can go back to unbranded EUX again like before. I guess if I leave the field empty in SamFW, but that seems dangerous to try on a brand new phone.
Haven't tried googling this, but how would I get the list of CSCs in SamFW? What Button to press? There was no scroll list, just a text field next to the button?
Click to expand...
Click to collapse
On one of the other screens, I think under adb commands or similar there is an option to get the CSC list.
DubelBoom said:
On one of the other screens, I think under adb commands or similar there is an option to get the CSC list.
Click to expand...
Click to collapse
Ah, yeah, there it is. Thanks! ADB -> Get list supported CSC.
For future readers (or myself when I forget):
A Galaxy S22+ (SM-906B/DS) that had "EUX/-/EUX/EUX" as CSC from the beginning (sold in Sweden) and changed to SEK instead shows these CSC codes in SamFW 3.1, probably the same if I hadn't changed (ymmv):
ACR | AFG | AFR | BKD | BOG | CAU | CPW | DKR | ECT | EGY | EUX | EUY | FWD | ILO | ILP | INS | KSA | LYS | MID | MOB | MOT | MSR | MWD | NPL | O2C | PAK | PLS | PRT | SEK | SER | SIM | SKZ | SLK | SRR | SWC | TIM | TOP | TUN | TUR | VIP | WWA | WWC | WWD | XFA | XFE | XFV | XSG
So I suppose I can just ype "EUX" and get back to stock again if I notice any issues. Perfect.
filigran said:
Ah, sim, aí está. Obrigado! ADB -> Obter lista de CSC suportado.
Para futuros leitores (ou para mim mesmo quando esqueço):
Um Galaxy S22+ (SM-906B/DS) que tinha "EUX/-/EUX/EUX" como CSC desde o início (vendido na Suécia) e alterado para SEK mostra esses códigos CSC no SamFW 3.1, provavelmente o mesmo se eu tivesse não mudou (ymmv):
ACR | AFG | AFR | BKD | BAG | CAU | CPW | DKR | ECT | EGY | EUX | EUY | FWD | OIT | ILP | INS | KSA | LYS | MEIO | MOB | MOT | MSR | MWD | NPL | O2C | PAK | PLS | PRT | SEK | SER | SIM | SKZ | SLK | SRR | SWC | TIM | TOPO | TUN | TUR | VIP | WWA | WWC | WWD | XFA | XFE | XFV | XSG
Então, suponho que posso simplesmente digitar "EUX" e voltar ao estoque novamente se notar algum problema. Perfeito.
Click to expand...
Click to collapse
Boas. Eu tenho um G988W do Canadá CSC XAC .... será possível mudar para um CSC europeu? Se eu tentar e não der certo bloqueio o tlm? Muito obrigado
filigran said:
Ah, yeah, there it is. Thanks! ADB -> Get list supported CSC.
For future readers (or myself when I forget):
A Galaxy S22+ (SM-906B/DS) that had "EUX/-/EUX/EUX" as CSC from the beginning (sold in Sweden) and changed to SEK instead shows these CSC codes in SamFW 3.1, probably the same if I hadn't changed (ymmv):
ACR | AFG | AFR | BKD | BOG | CAU | CPW | DKR | ECT | EGY | EUX | EUY | FWD | ILO | ILP | INS | KSA | LYS | MID | MOB | MOT | MSR | MWD | NPL | O2C | PAK | PLS | PRT | SEK | SER | SIM | SKZ | SLK | SRR | SWC | TIM | TOP | TUN | TUR | VIP | WWA | WWC | WWD | XFA | XFE | XFV | XSG
So I suppose I can just ype "EUX" and get back to stock again if I notice any issues. Perfect.
Click to expand...
Click to collapse
HI.
I want to ask you what do you mean that call id not working and did you face any problem efter changing CSC. because I also live in Sweden. any disadvantages for doing that?
thanks
@filigran
Hi guys, sorry to hijack your thread, but could you post your S22+ stock IMGs please? I have a brick, and until someone posts stock fw on samfw.com i won't be able to boot.
My thread below and sorry again
https://forum.xda-developers.com/t/stock-binary-v5-imgs.4594759/

Question SM-A025G what CSC to use for nativ call record and BT problems.

Hello, as we all know, it is not possible to record calls anymore on Samsung mobile phones.
But I have read that by changing the CSC it should be possible to record calls.
I Own one SM-A025G with the following CSC
Reading list CSC...OK
3IE | AMO | ATL | ATO | AUT | BGL | BOG | BTU | CNX | COA | COS | CPW | CRO | DBT | DTM | EUR | EUX | EUY | FTM | H3G | HUI | ITV | LUX | MAX | MBM | MET | MOT | MSR | NEE | O2C | O2U | OMN | OPV | ORO | ORS | ORX | PHE | PHN | PLS | PRT | ROM | SEB | SEE | SIM | SIO | SWC | TCL | TIM | TMH | TMS | TMZ | TOP | TPH | TPL | TSI | VD2 | VDC | VDI | VGR | VIP | XEF | XEH | XEO | XEZ
(from SamFw_Tool_v3.3.1)
Is it one of the CSCs with which it is possible to activate call recording?
Have only found SEK CSC for SM-A025F, but cannot be flashed in the mobile?
(but identical hardware?)
Problem with BT.
Wireless headphones do not work during calls !!
Airpods or skullcandy and two different varieties of cheap bt headphones have been tried, can only hear voice but they can't hear me talking during calls.
Music works well.
Slightly better when changing BT codecs. But the quality of voice calls is poor. unusable solution.
It is not possible to turn off "Disable Bluetooth A2DP Hardware Offload" it is grayed out in dev options. Something that is recommended in the forum otherwise.
Any help or answer is appreciated!

Categories

Resources