No. This watch also has built-in magnets for attaching the charger cable. These would interfere with the compass.
2 Likes
phones have speakers and electric motors and that doesnât prevent them from having a compass. the sources of magnetic interference (speakers, motors, etc) are constant and at a fixed distance, should be easy to acccount for, thatâs why compass calibrarion exists.
The magnets used to mount the charger are significantly stronger. The compass function only works with smartwatches that have a USB charging port or a mechanical attachment, such as the Samsung Gear R750.
it likely has one, asr seems to always have one, but just doesnt work at all, like the m81, you can test with better health tracker sensor tester or this watch face in UL
(file upload failed)
1 Like
does the Vwar branded watch come with English/International firmware, and the S13 comes with Chinese firmware? can I flash the Core 5 firmware on the S13?
The VWar and the unbranded S13 are exactly the same and have the same firmware. Only difference is the stock watch faces. No benefit from flashing firmware. In fact, earlier firmware had better battery life.
Both have a Chinese and an international version of the firmware.
Regarding compass, itâs far more reliable to use Google maps.. As pointed out, magnetic compass apps have too much interference in such a tiny device. Thatâs why there is no sensor for magnetic compasses on these. It was tried a few years ago and it was terrible.
is the international firmware available to download?
Check out this thread. Itâs all here
1 Like
@bsdinis Itâs part of the main post.
I might buy this watch today. I just have one last question, would a tempered glass screen protector work on this watch or is the surface too curved?
Curved glass
my S13 is on the way, should be here next week.
google doesnât yield much information about the ASR8601C, but I was able to find a .pdf document called âASR8601 Brief Specification v1.1â with detailed specifications and a vague block diagram, not sure if I can upload it here as it has an âASR Confidentialâ watermark all over it.
I also tried looking for any clues about rooting this device and I found this video on bilibili with the title Has the ASR watch brush been breached? ASRClient Officially Released! Supports s13, m81, xh022 and other ASR8601c models) and it has links to two GitHub projects in the description. the creator of the video also commented ASRT601C Android model has been released avb checksum, add more information.
(translated from Chinese).
found this. seems like it is possible to root these watches
Huaqiang North Asr8601c Android 13 watch successfully root
The device is xh026, and root is using ``https://www.bilibili.com/video/BV1vteEz1Eb1/`` Tools developed by the big vertebrates
one of the viewers commented
Go to AVB and then extract the boot brush, which is similar to the operation of the mobile phone.
from insider source i have heard the gsi have entered the boot animation and get stuck, for now not work yet
2 Likes
they say it is hopeful, but i would say just dont buy asr, it heat up so badly
1 Like
Thanks for the update.
We already have the official chip design and documentation, but obviously, we are not allowed to post it here.
If you have found something online, I suggest that posting links to the websites is a far better way to let people access it if they want to.
As all images in the firmware are signed with a private key (just like all firmware since Android 9) root could really only be achieved if DM VERITY and VB Meta are fully disabled. Along with enabling OEM unlock, several fastboot commands are needed to carry out the tasks mentioned above. It really is quite a serious piece of work to try and gain root access, especially Android 13, 14,15 and 16. The usual result is that people end up with an unusable device.
This is the main reason why it is not such a popular subject anymore and we donât encourage it for the same reason.
Getting Magisk to work with a patched boot image used to be the best way to proceed and maybe still is. But a LOT of research is needed before you attempt it. Searching for âusing magisk manager with ASR Android 13â may give some results - not sure if Magisk is even a thing anymore. The developer was talking about stopping his work because of the problems he was facing with the newer security in Android.
Cheers
the future is kernelsuâs
Yes, thatâs been a problem for sure.
There is also talk about the ASR chipset future with Android coming to an end.
Itâs just not production ready in my opinion. Even though I have the source code, itâs a mess and needs a LOT of work before it would be acceptable. I work with the solution provider and it has been a painful experience with this chipset 
1 Like
Yes. It is but it is not a solution that we will see very quickly I guess.
Given the requirements for kernel SU.
It would be great though 
just like gsi, now we have gki, so kernelsu will benifit allot from it, i heard they are developing gki for 8541E, but i have no proof only heard