[ROM - DEV] WearOS 2 for Gear S3
- Thread starter parasetam0l
- Start date
I have already flash it on Korea (R770),it works,but I can not connect it with my phone because global wearOS by Google cannot work in my area (China
It's abandoned, the developer didn't log in to XDA for months
I've used this for a month, but one day it unpaired itself from my phone for no reason, and I couldn't pair it again. Since reset within the ported Wear OS doesn't work, you have to reflash the ROM to start all over. That's too much work, esp if it unpairs randomly again, so I gave up and went back to the stock ROM today. At this point, I may just sell this watch and go buy Tickwatch
Don't buy the ticwatch. Crappy third party apps for most of the stuff, basically no support and I had the case of sensors completely stopping like many other on the recent 3pro model. No support from ticwatch, tankfull that Amazon refunded 100%. Also they wanted to update base wear software q2/3 2022 and still no eta in 2023.
The watch was nice but to many problems. I'm rocking the s3 again and wait for a bigger upgrade.
BTW gear s3 was running android wear significantly faster than my ticwatch s3pro. And modern Android based galaxy watch has more features, better sensors and most recent wear os base.
Yea, thanks for the warning, but I actually read reviews and know pros/cons. In my case, I only need it to be able to get notifications and check/send text messages, so I don't need any other features. So, my focus is price-point, not quality.
I want to come back to Tizen but when I go to the wireless download mode i see a green text and I can't see the watch AP in my computer
there must be some green texts,but when i use it,my computer see it.
try to tap Power button twice and check your computer later
So I started to do the wireless installation and accidentally knocked my watch off of the wireless adapter while it was flashing and now it is just showing “Secure Block: Fail (Boot) press power key to shutdown.” Does that mean the watch is totally bricked now? Cuz I can’t seem to get it working except I can get it to the part where I switch it to AP mode but it immediately goes back to the “Secure block: Fail (Boot) press power key to shutdown.” Any advice would be appreciated.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
65DISCLAIMER
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 feedback34DEVELOPER 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.20UPDATE:
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.
