[ROM - DEV] WearOS 2 for Gear S3

Search This thread
Approximately how long does the battery last with wear os installed?
Battery drains very quickly by the screen. If you keep the screen on, it'll last one hour tops. But if you close the always on and keep the screen closed when you don't use it, it has a pretty solid usage time. Approximately a day and a half in my case.
 

parasetam0l

Senior Member
Apr 5, 2011
72
355
Ankara
Thanks for make this. Hope you can find a way to install wearos on Amazfit Verge. Maybe it's little easier because old Amazfit Watch use Android on their watch but it's not wearos.
Never had an experience with Amazfit Verge. No CPU info, it has 512MB ram which is not enough for running WearOS smoothly. Sorry.

hey seniors sorry to say but i forget to turn off my reactivation lock sadly my watch stuck saying custom binary blocked by reactivation lock.. i can't go into wireless mode please can you solve my problem how to fix this ?
The only way is soldering USB cable and flashing Tizen firmware with Odin.

Never mind, I just realized it could be only not showing the ap Mode text because the weird green text, I was right, double click in power button and I found the wireless network in my laptop.

Hi, I am glad you made it. It is also a known bug :)

Code:
Same green text on Wireless Download Mode. It prevents debug messages (Switching to AP mode etc) but functionality is not effected.

Approximately how long does the battery last with wear os installed?
My watch is still connected to usb. So I can not say anything about battery life. I have still things to do for power management and kernel improvements. Also it depends on your battery's health. With disabled wifi (auto to completely off), always on screen, gps from settings, it can save your day.
 
  • Sad
  • Like
Reactions: aiui and Arsyad1105

Errox505

Member
Dec 22, 2016
6
6
OnePlus 7
I've been noticing that recharging is quite slow. Not sure how or what, but it's been 12 hours and I have to reboot it a couple of times to get more charge. 12:01 PM started charging -> 22:07 PM and it's only 83%.

P.S. I'm not sure if I could extract some logs wirelessly from my watch. If so, I'd love to share them if that would be more helpful.
 
  • Like
Reactions: lavasbey
I've been noticing that recharging is quite slow. Not sure how or what, but it's been 12 hours and I have to reboot it a couple of times to get more charge. 12:01 PM started charging -> 22:07 PM and it's only 83%.

P.S. I'm not sure if I could extract some logs wirelessly from my watch. If so, I'd love to share them if that would be more helpful.
Yeah that was an issue on my case too. Not that slow tho. Maybe try turning of the screen, if you didn't already, will solve a bit of your problem.

Watch automatically boots when chager is connected, but booting eats too much battery. When my charger and my watch heats up, it's like impossible to charge it. It is just looping.

Sooo, maybe adding an on off switch on auto boot solves the problem for a while?
 
  • Like
Reactions: Errox505

Errox505

Member
Dec 22, 2016
6
6
OnePlus 7
Yeah that was an issue on my case too. Not that slow tho. Maybe try turning of the screen, if you didn't already, will solve a bit of your problem.

Watch automatically boots when chager is connected, but booting eats too much battery. When my charger and my watch heats up, it's like impossible to charge it. It is just looping.

Sooo, maybe adding an on off switch on auto boot solves the problem for a while?
Hey, yeah, my screen is turned off. I just notice that there is a couple of percentage charging. But then gets stuck on a certain percentage, rebooting seems to fix it for a couple more percentage. And for heat, it's been quite the same temperature as usual from my perspective.

What do you mean with the automatic boot? I've noticed my watch been crashing sometimes (not sure how or what, just out of nowhere with no repeatable process to simulate it) and it just restarts itself. Is that what you mean?

I've been keeping track of the battery life combined with my settings, maybe it'll be handy in the future to keep track of it.
 
What do you mean with the automatic boot? I've noticed my watch been crashing sometimes (not sure how or what, just out of nowhere with no repeatable process to simulate it) and it just restarts itself. Is that what you mean?
No, I meant the booting after you connect your charger. Wheter you close the watch by shutting down or drain the battery to 0 percent, it stills boots when you connect to the charger. Maybe power off'd charging would be more usable.

And also, yeah. You have a different problem there. I don't know what to say to you. It looks like a background app has an issue. Maybe your watchface is the problem? I don't know.
 

Maxblock88

New member
May 18, 2022
2
0
Battery drains very quickly by the screen. If you keep the screen on, it'll last one hour tops. But if you close the always on and keep the screen closed when you don't use it, it has a pretty solid usage time. Approximately a day and a half in my case.
Wow that's way to quick to make it worth it. Will there be a way to make it better in the future?
 

Reimagine

New member
Jun 10, 2020
3
2
I know youve probably heard this a lot but youve trully done what no one else could. I am glad youre getting some media coverage on this.

If you could have battery stability and NFC working for google pay, I dont see why this wouldnt be the main OS for all of the gear s3's in use out there (mine included).

I wish you the best <3
 

Umbardacil

Senior Member
Feb 1, 2012
320
65
Knurów
Yeah

NFC is all what we are waiting for ☺️

Imagine my disappointment when i spent 500€ back in the days for a high tech watch, and i couldn't pay with it although it was hardware ready 😭 (my county - Poland 🇵🇱) doesn't support Samsung Pay.

So i wish OP good luck and i keep my fingers crossed. If your project becomes daily driver with Google payment method i will find a way to donate you 😉🙏👍
 

catamai98

Member
Apr 17, 2022
9
11
Yeah

NFC is all what we are waiting for ☺️

Imagine my disappointment when i spent 500€ back in the days for a high tech watch, and i couldn't pay with it although it was hardware ready 😭 (my county - Poland 🇵🇱) doesn't support Samsung Pay.

So i wish OP good luck and i keep my fingers crossed. If your project becomes daily driver with Google payment method i will find a way to donate you 😉🙏👍
I feel you, Romania here, same situation.
 
  • Like
Reactions: lavasbey

Errox505

Member
Dec 22, 2016
6
6
OnePlus 7

And also, yeah. You have a different problem there. I don't know what to say to you. It looks like a background app has an issue. Maybe your watchface is the problem? I don't know.
Coming back to the charging issue. I've placed my 0% battery on the charger today, and it went from 10:00 0% to 12:20 100%. I changed the watch face, but also disabled wifi and location. I also cleaned my charger a bit. Not sure what caused it, but it works fine.
 
Last edited:

catamai98

Member
Apr 17, 2022
9
11
Only annoying problem that I have is with the vibration, is not working always and when is working it is very weak
 

Enrico9800

Senior Member
Sep 23, 2016
131
15
DISCLAIMER

Code:
Your warranty is now void (if you still have one).
Read the steps carefully!
I am not responsible for data loss, bricked devices or devices which will need USB soldering!
If you do not know what you're doing, stop here!

DOWNLOAD WearOS 2 (Based on latest H MR2)
DOWNLOAD WearOS 2 (ALTERNATIVE)

GEAR S3 ONLY!! Installed and tested on a few SM-R760 Frontier and get succeed. In theory SM-R770 Classic will work too. They use same kernel and hardware.

BUT Korean and LTE versions are NOT TESTED. THEY USE DIFFERENT KERNEL CONFIGURATION. IT WILL PROBABLY CAUSE HARD BRICK!! USE YOUR OWN RISK!

BEFORE INSTALLATION

  • DISABLE REACTIVATION LOCK
  • Charge your watch to 100%
  • Keep your device charging while installing firmware
  • Have a stable computer with Wifi
  • Take note your current Tizen firmware version for going back to Tizen
  • Backup all your data
  • Keep your watch close to your wireless adapter

INSTALLATION (View Detailed Document Here)
  • Flashing process is the same as flashing combination or Tizen firmware
  • Wireless flashing takes 15~45 minutes.
  1. Extract downloaded zip file to get tar file
  2. Enter wireless download mode
  3. Switch to AP mode
  4. Connect to watch from your wireless adapter
  5. Select tar file for AP section
  6. Flash

DO NOT interrupt flashing process!
DO NOT shutdown your computer or allow your computer to sleep!
DO NOT enter recovery before WearOS boots completely!



WHAT IS WORKING
  • WearOS functions (Notifications, Play Store, Google Account, Assistant etc)
  • Always on display
  • Wifi
  • Bluetooth
  • Vibrator
  • Bezel (works like crown)
  • Tap to wake
  • Palm to suspend
  • Mic
  • HRM (Hear Rate Monitor - Sensor)
  • Sensors (Accelometer, Gyroscope, Light)
  • Audio
  • TWRP

KNOWN BUGS
  • Poor Battery Life compared to Tizen (Old device, new operation system)
  • Audio (Low sound level, bad quality)
  • HFP calls on watch (Bad noises, distorted sound)
  • If you remove your watch from charger, WearOS charging indicator keeps showing until reboot. Prevents battery saving mode. Disables vibration for notifications.
  • Some menus on Settings belongs to Ticwatch (just ignore them)
  • Offline charging boots device
  • Tilt Sensor (Raise your arm to wake device and wrist gestures) is not working
  • GPS is not working
  • NFC is not working
  • Step Counter is not working
  • Device serial number is 12345678
  • Device name shown as Gear S3 (NOWN)
  • Wear application on phone sees device as Ticwatch Pro 3
  • Some green text above SAMSUNG logo while booting
  • Same green text on Wireless Download Mode. It prevents debug messages (Switching to AP mode etc) but functionality is not effected.
  • If device goes to TWRP, just click Reboot -> System.
  • Selinux is in Permissive mode
  • ADB Root is active
  • KNOX will be tripped!!

RESETTING WATCH OR CONNECTING NEW DEVICE
NEVER use WearOS settings menu to reset watch!!! It is not tested and may be brick your device.


Option 1: Flash WearOS again
Option 2: Boot to TWRP and Wipe Data (IMPORTANT! Be sure “Use rm -rf instead of formatting” is selected on TWRP settings. (TWRP Settings -> General Settings)

GOING BACK TO TIZEN
  1. Find and download your Tizen firmware from internet. (Remember, you took note your firmware version before installation)
  2. If you can not find your firmware you can try THIS TIZEN FIRMWARE. (It may has different CSC. Be careful!)
  3. Flash
SOURCES
Github (parasetam0l) for kernel, device tree and other SMDK - Samsung related files.

THANKS TO
TO21Consortium for beautiful SMDK source
YariKartoshe4k for Exynos 7570 kernel source
Biktorgj for Gear S and SSP sensor sources
OneOS for TicWatch WearOS2 system dump
Many other developers I came across with Google search.
can you port also to galaxy watch3?
 

tsp12 haha

New member
May 19, 2022
4
3
I know it's getting tiring how a lot of people say they created an account just for this. I just wanted to say that it worked perfectly! Yes, although it still thinks it's charging after taking it off the wireless charging thing, it still works completely fine! I downloaded it through the Wireless Download menu, as definitely a non expert in these type of things, it was quite easy to install! Thank you for basically bringing back life to this old watch.
 

catamai98

Member
Apr 17, 2022
9
11
Now I have one day of use, and is working great, only the problem with vibration and google pay. Battery seems pretty normal to me, maybe a little bit worse but not a big difference. Awesome work :)
 
  • Like
Reactions: parasetam0l

Top Liked Posts

  • 1
    i have a bug (?) or this is general problem with firmware
    my watches stopped to charge at 84%, im replugged dock at night and at this moment i have 94% of charge
    on dock is red indicator that means that watches not fully charged
    UPD. on charger charge level decreased from 94 to 92%
  • 16
    NEW RELEASE:

    Hello everybody,
    Here is the new release. This version needs a clean install so it will AUTOMATICALLY WIPE YOUR DATA. Just flash with netOdin / Odin as usual. I also updated the first post.

    DOWNLOAD NEW RELEASE
    DOWNLOAD NEW RELEASE (ALTERNATIVE)

    Changelog (22/06/2022):
    • Charging indicator issue is fixed. (No need to restart watch anymore for disappearing indicator)
    • Audio level is increased to default.
    • Some audio fix (mixer_paths.xml).
    • Raise arm to wake device is working now. (Tilt sensor, decreases battery life).
    • Always on display with palm to suspend is fixed.
    • Serial number issue is solved. (1234567 to device's own serial number. Affects bluetooth name too)
    • Partial fix for offline charging. (Still boots to system)
    • Some fixes for sensor service. It seems it doesn't crash anymore. Also logcat is showing context sensor debug data now. It is easy to track values and extract step counter data.
    • WearOS application on phone now has Gear S3 image (before, it was Ticwatch Pro 3)
    14
    SMALL UPDATE:

    • Charging indicator issue is fixed.
    • Audio level is increased to default.
    • Raise arm to wake device is working now. (Tilt sensor).
    • Always on display with palm to suspend is fixed.
    • WearOS application on phone now has Gear S3 image (before it was Ticwatch Pro 3)
    • Serial number issue is solved. (1234567 to device's own serial number. Affects bluetooth name too)
    • Partial fix for offline charging

    I am currently dealing with offline charging. I fixed it on kernel side and android side. But offline charging crashes kernel because of framebuffer. DMA is not working while screen is off. I am trying to solve framebuffer issue.After that offline charging will be fixed. Then I will release a new build.

    A couple of questions:

    1. Can you tell us which bugs you managed to fix up to now?
    2. The upgrade procedure would be the same as the first installation or it's simpler?

    Hi, thank you!. For your second question, next build will need to wipe data because of serial number and some system app changes. But newer builds won't need to wipe data. Installation will be the same. Because Odin does not support incremental installation. We always need to install full package. TWRP side is the same.


    Are these the latest steps / instructions to install? I'm not as tech savvy, so waiting for a more stable version so I don't brick my watch.

    Anyone on here using an iOS app to use with their Google WearOS? Don't have an android unfortunately :(

    Yes, they are the latest. If you follow steps carefully, it is hard to brick your device. Stability of WearOS doesn't effect bricking chance. Also iOS has WearOS app. So It will work.

    I appreciate your work.how soon wear os3 will be applicable?

    There is no WearOS3 source except Samsung's one. I noticed that Google also released a pure WearOS3 emulator image for ARM based Macs. I am currently looking what can I do. But it seems dead end because of RAM usage. x86 emulator image uses about 1.5GB of RAM. I will take a look for ARM one.
    11
    BATTERY PERCENTAGE FIX FOR 22/06/2022 UPDATE:

    With latest update (22/06/2022), some people's battery percentage is stucked at the same level and is not updating until reboot. Here is the fix for that. No need to wipe data or do something special. This file contains kernel update only. Just flash directly with netOdin/Odin.

    DOWNLOAD KERNEL UPDATE FOR 22/06/2022 BUILD
    3
    I'm on the newest update and I got a message that I have a new update and asking me to put the watch on the charger.

    Is it safe to update?

    Hello,
    After first setup, your watch will update some of system apps for example Google Play Store. This notification is for that. You can continue without charging or put your watch to charger. Because of this updates, until installation finishes, your battery will drain faster and your watch will be slower. After finishing background updates and background optimizations, your battery and performance will be better.

    when charging no indicate of progress percentage its only for me or the others and how fix it?

    Thank you! I noticed that too. Now I am uploading a small update.
    3
    I'll make a video if I find a free time to do this
  • 48
    DISCLAIMER

    Code:
    Your warranty is now void (if you still have one).
    Read the steps carefully!
    I am not responsible for data loss, bricked devices or devices which will need USB soldering!
    If you do not know what you're doing, stop here!

    DOWNLOAD WearOS 2
    DOWNLOAD WearOS 2 (ALTERNATIVE)

    Latest Release: 22/06/2022 22:58

    BATTERY PERCENTAGE FIX FOR 22/06/2022 RELEASE (CURRENT BUILD):

    With latest release (22/06/2022), some people's battery percentage is stucked at the same level and is not updating until reboot. Here is the fix for that. No need to wipe data or do something special. This file contains kernel update only. Just flash directly with netOdin/Odin.

    DOWNLOAD KERNEL UPDATE FOR 22/06/2022 BUILD

    GEAR S3 FRONTIER/CLASSIC ONLY!! Installed and tested on a few SM-R760 Frontier and get succeed. SM-R770 Classic is also confirmed.

    BUT Korean and LTE versions are NOT TESTED. THEY USE DIFFERENT KERNEL CONFIGURATION. IT WILL PROBABLY CAUSE HARD BRICK!! USE YOUR OWN RISK!

    BEFORE INSTALLATION

    • DISABLE REACTIVATION LOCK
    • Charge your watch to 100%
    • Keep your device charging while installing firmware
    • Have a stable computer with Wifi
    • Take note your current Tizen firmware version for going back to Tizen
    • Backup all your data
    • Keep your watch close to your wireless adapter

    INSTALLATION (View Detailed Document Here)
    • Flashing process is the same as flashing combination or Tizen firmware
    • Wireless flashing takes 15~45 minutes.
    1. Extract downloaded zip file to get tar file
    2. Enter wireless download mode
    3. Switch to AP mode
    4. Connect to watch from your wireless adapter
    5. Select tar file for AP section
    6. Flash

    DO NOT interrupt flashing process!
    DO NOT shutdown your computer or allow your computer to sleep!
    DO NOT enter recovery before WearOS boots completely!



    WHAT IS WORKING
    • WearOS functions (Notifications, Play Store, Google Account, Assistant etc)
    • Always on display
    • Wifi
    • Bluetooth
    • Vibrator
    • Bezel (works like crown)
    • Tap to wake
    • Palm to suspend
    • Mic
    • HRM (Hear Rate Monitor - Sensor)
    • Sensors (Accelometer, Gyroscope, Light)
    • Audio
    • TWRP

    KNOWN BUGS
    • Poor Battery Life compared to Tizen (Old device, new operation system)
    • Audio (Low sound level, bad quality)
    • HFP calls on watch (Bad noises, distorted sound)
    • Some menus on Settings belongs to Ticwatch (just ignore them)
    • Offline charging boots device
    • GPS is not working
    • NFC is not working
    • Step Counter is not working
    • Some green text above SAMSUNG logo while booting
    • Same green text on Wireless Download Mode. It prevents debug messages (Switching to AP mode etc) but functionality is not effected.
    • If device goes to TWRP, just click Reboot -> System.
    • Selinux is in Permissive mode
    • ADB Root is active
    • KNOX will be tripped!!

    RESETTING WATCH OR CONNECTING NEW DEVICE
    NEVER use WearOS settings menu to reset watch!!! It is not tested and may be brick your device.


    Option 1: Flash WearOS again
    Option 2: Boot to TWRP and Wipe Data (IMPORTANT! Be sure “Use rm -rf instead of formatting” is selected on TWRP settings. (TWRP Settings -> General Settings)

    GOING BACK TO TIZEN
    1. Find and download your Tizen firmware from internet. (Remember, you took note your firmware version before installation)
    2. If you can not find your firmware you can try THIS TIZEN FIRMWARE. (It may has different CSC. Be careful!)
    3. Flash
    TELEGRAM GROUP
    PLEASE JOIN FROM HERE

    SOURCES
    Github (parasetam0l) for kernel, device tree and other SMDK - Samsung related files.

    THANKS TO
    TO21Consortium for beautiful SMDK source
    YariKartoshe4k for Exynos 7570 kernel source
    Biktorgj for Gear S and SSP sensor sources
    OneOS for TicWatch WearOS2 system dump
    Many other developers I came across with Google search.

    @trapecija For SM-R770 Classic feedback
    24
    DEVELOPER NOTES :

    • Soldering USB and Odin USB mode: Done
    • Install Combination firmware (COMBINATION-FT30_R760XXU2CQL1): Done
    • Root Access (Combination firmware is pre rooted): Done
    • Build Tizen Kernel: Done
    • Upstream Tizen Kernel to latest (from 3.18.14 to 3.18.140): Done
    • Enable Android configs and disable some Samsung stuff on kernel: Done
    • Kernel cmdline patch for booting from mmc: Done
    • TWRP device tree: Done
    • Build TWRP: Done
    • MM (memory management) and FB (framebuffer) patch for IOMMU error: Done
    • PMIC patch for enabling USB: Done
    • Created fstab file: Done
    • Update Android Binder kernel driver: Done
    • Android Boots with ADB support: Done
    • USB Charging: Done
    • Mali T720 GPU Driver Update: Done
    • Decon Framebuffer: Done
    • S6E36W2X01 LCD Panel: Done
    • Compile AOSP9: Done
    • WearOS2 Port: Done
    • Broadcom 43102 Wifi and Bluetooth SDIO: Done
    • Palm to suspend: Done
    • Audio: Partially Fixed (Low sound level and quality)
    • HFP (Handsfree Protocol): Partially Fixed (Mic works, speaker distorted sound)
    • Brightness: Done
    • Vibration: Done
    • LSM6DSL Accelometer and Gyroscope Sensor: Done
    • TSL2584 Light Sensor: Done
    • PPS960 Heart Rate Sensor: Done
    • SSP Sensor Hub: Partially
    • Tap to Wake: Done
    • Always on display: Done
    • Bezel: Done
    THINGS TO DO:
    • GPS
    • NFC
    • Offline charging
    • Step Counter
    • Power Optimizations (power.exynos5)
    • Audio and HFP (mixer_paths.xml)
    • SSP Sensor Hub
    • ...
    • ...
    • ...
    • WearOS 3
    21
    As we know Android and Tizen are linux based operation systems. Android has its own libraries (bionic) at system side and it is heavily customized version of linux. Tizen has more pure linux libraries and linux approach for drivers, system configuration etc.

    For who is dealing porting android on linux devices:
    If your device does not have UART for bluetooth and initializes HCI on kernel side like solis, your keyword is

    UPDATE:
    I fixed bluetooth and wifi. I was able to complete setup after after fixes.

    What is working?
    • Display
    • Bluetooth (Everything except audio functions)
    • Wifi
    • Battery
    • Palm screen to suspend device
    • Google Services
    • WearOS functions (Notifications, Google Assistant etc)

    What needs to be fixed?
    • Audio (Largo is not using by any other android device)
    • Vibration
    • GPS
    • NFC
    • Sensors
    • Double tap to wake
    • Always on screen
    • Offline charging
    • Bezel (tizen_detent)

    After fixing audio and vibration I will test wireless download mode. If everything goes well, we will be ready for alpha release :) Here are some photos.
    21
    Hello all and thank you for your kind interest.

    UPDATE:
    I fixed audio. Now microphone and speaker is working. I also fixed HFP (Hands Free Protocol, which is used by phone calls). Now we can make calls from watch. Audio routing works but speaker is not working as expected. I think it is due to volume levels and gain levels. Tizen sets gain differently. I can not solve this yet.

    I also fixed screen brightness. I did some kernel tweaks, switched Tizen's Javaw governor to interactive governor. I added some Android requirements (/proc/cpu_time/ etc) to the kernel.

    Now I am working on vibrator. It has different approach from usual vibrators. ZH915 is not a timed_output device. It is an event driven input device (FF_RUMBLE).

    As I said, after vibration fix, I will test wireless download mode.
    18
    UPDATE:
    Vibration is ok.

    My first approach is converting FF_RUMBLE device to timed_output. I found this driver for ZH915 which is based on timed_output. But it is not working due to dts (gpio pins) incompatibility. After some digging, I found fftest is used for testing force feedback devices on linux. After finding source code of fftest, I cross compiled it and run on device, made some changes (intensity, effect types) and found correct configuration. And there it is, device vibrated.

    After finding correct configuration, it is time for vibrator hal. With big help of Qualcomm's Vibrator Hal, I developed our own vibrator service. (Actually copied a lot of code from qualcomm repository, changed configuration and fixed build errors). And vibration is working now.

    I also tested wireless download mode. It is not working due to my fake cmdline configuration. Device is booting system when you select wireless download. Don't worry, kernel part is easy to fix. After fixes I will try again wireless download. Maybe offline charging will work too.