the main issue for me not using this as main rom for my s3 gear is the 'turn the wrist' to turn on the screen (I think due missing the accelerometer drivers), but the rom is awesome, I really loved it.
[ROM - DEV] WearOS 2 for Gear S3
- Thread starter parasetam0l
- Start date
Hello,
I can not reply your posts one by one but I read all. Thank you all for your kind wishes!
I will take a look at vibration.
I also discovered that palm to suspend does not put lcd to hardware based always on display mode. This causes more battery drain. So do not touch the screen about 5 second, it will go to software and hardware based always on display properly. But with palm to suspend, only software based always on display works. You can understand it with screen brightness on AOD mode.
For whom wants to help on development, we organized a Telegram group.
JOIN HERE
I can not reply your posts one by one but I read all. Thank you all for your kind wishes!
I will take a look at vibration.
I also discovered that palm to suspend does not put lcd to hardware based always on display mode. This causes more battery drain. So do not touch the screen about 5 second, it will go to software and hardware based always on display properly. But with palm to suspend, only software based always on display works. You can understand it with screen brightness on AOD mode.
For whom wants to help on development, we organized a Telegram group.
JOIN HERE
Hello, im tried this firmware on R770 (S3 Classic), here is some feedback
Seems that Google Fit is not working , it means that HRM is not working at all.
Vibration is very low
Poor battery life when bluetooth is connected
In general performance is at high level, very smooth
Seems that Google Fit is not working , it means that HRM is not working at all.
Vibration is very low
Poor battery life when bluetooth is connected
In general performance is at high level, very smooth
Wow, this feedback is very important for me. Thank you a lot. What error you got from Google Fit? A lot of people said that HRM is working.
And also this confirms my theory.
Code:
In theory SM-R770 Classic will work too. They use same kernel and hardware.Again, thank you for your feedback!
Okay, i not understand that happened, but now HRM is working
If it works on GWG3 now, maybe some developer could help port it to Exynos 9110 devices like the GW1 and GW3. I also wonder if 2G GPRS/EDGE could be added because the E9110 has it and it can consume less energy than 4G because tx power required often is lower.
All Galaxy watches have combination firmware and kernel sources. If Samsung has not added some new security things to these watches, yes it can be ported. Just need to give it a try. Exynos 9110 shares the same GPU with 7270. So display part will be easier to work. I am not sure about 2G because LTE version of these watches are not selling in where I live. Also I do not have any Galaxy Watch.
Hello about Galaxy Gear S3 Classic, some few words from me. I worked as technican in one of the biggest Samsung hardware services in Poland as i confirm that hardware is exacly same ( PBA etc) like in Galaxy Gear3 Frontier. Also we install orginal rom via pogo or wifi and odin/fenrir, so its should be safe. You can swap also rom from frontier to classic and reverse and it just only change name in settings and set defualt watch face to classic/frontier style in first boot So yeah i also confirm that they 100% same hardware. Just frontier was more popular when its was relase Cant wait for new news about wearOS, im nearly to deploy also for my classic
So yeah i also confirm that they 100% same hardware. Just frontier was more popular when its was relase Cant wait for new news about wearOS, im nearly to deploy also for my classic 
hey i was wondering whether the same one could work for Samsung Gear Sport as they are not very different from gear s3.
This is completely different product line then gear S3 imho. But don't lose hope
Last edited:
I completely forgot how different those devices are courtesy of samsung's naming scheme. Diffrent processer and gpu and other stuff as well.
dude this is a first release, there is a lot of work that still needs to be done before everything will work
You are a real savior for our obsolete Gear S3. Thanks for your hard work.
fantastic work, I haven't seen something innovative like this in a long time. if we get a fully functional WearOS rom for the old watches it will be awesome!
We need more devs like you!
We need more devs like you!
After a few days, I can say it's much faster then stock rom. I'm really impreseed.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
17NEW 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)
12BATTERY 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 BUILD3
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.
Thank you! I noticed that too. Now I am uploading a small update.3
you can find instructions here https://www.samsung.com/za/support/...ble-and-disable-reactivation-lock-on-gear-s3/2I'm on the latest update + kernel.
I have few issues with it, I'm noticing a battery drainage. The watch barely finishes the day with a 25%. (Previous stays for almost 3 days)
I'm almost seeing a slow and sluggish performance on apps that wasn't on the previous release (e.g. Play store)
I'm not sure of this, but I also seen a slow changing time. I could be wrong though. -
50DISCLAIMER
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.
- Extract downloaded zip file to get tar file
- Enter wireless download mode
- Switch to AP mode
- Connect to watch from your wireless adapter
- Select tar file for AP section
- 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
- Find and download your Tizen firmware from internet. (Remember, you took note your firmware version before installation)
- If you can not find your firmware you can try THIS TIZEN FIRMWARE. (It may has different CSC. Be careful!)
- Flash
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 feedback25DEVELOPER 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
- GPS
- NFC
- Offline charging
- Step Counter
- Power Optimizations (power.exynos5)
- Audio and HFP (mixer_paths.xml)
- SSP Sensor Hub
- ...
- ...
- ...
- WearOS 3
21As 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
Code:
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.21Hello 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.19UPDATE:
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.
