[Samsung Gear S] biktor_gj:
Given that all the other threads were about how amazing it would be to run Android on the Gear S and I'm actually trying, I though it was time for a new thread.

Android AOSP/Wear for Gear S​

This thread is about development of Android AOSP & Wear for Gear S​

View attachment 3445494View attachment 3445495View attachment 3445496View attachment 3445500View attachment 3445502

This thread has a dedicated Q&A section: http://xdaforums.com/gear-s/help/qa-gear-s-android-port-t3177751

Please post questions there!

DISCLAIMER

Your warranty is now void. Not only void,
it's not comming back. The moment you
flash anything on this thread you can say
goodbye to it. I almost hard bricked my
watch once. It can happen to you too.
I do my best to post things that aren't
dangerous for the device, but anything
as simple as a 9 instead of a 4 in the GPU
driver might make it overheat and kill it.
Everything here is at your own risk.
You have been warned.

NOTICE: THIS IS ONLY FOR GSM VERSIONS WITH UNLOCKED BOOTLOADERS. I DON'T KNOW IF VERIZON'S CDMA VERSION WILL BE LOCKED, BUT AT&T VERSION IS, SO NONE OF THIS WILL WORK. YOU WILL GET AN AUTH FAIL IN ODIN IF YOU TRY TO FLASH IT, AND IF YOU'RE STUBBORN, YOU WILL GET A BOOTLOADER ERROR MESSAGE SAYING THE DEVICE HAS BEEN TAMPERED WITH.

Current development stage

Kernel:: Working on it. Patched framebuffer, added android modules, fixed scheduler incompatibilities with ADB building in AOSP tree. A lot of work to do

Recovery:: Recovery boots and ADB is available. The screen doesn't work correctly so it's barely usable. ADB works though

Android: Fully booting. DPI set to 200 to keep things inside the screen. Except for the apps that need a bigger screen, it's usable

Want to look at the code that makes this tick?

Kernel: kernel / samsung / pontesolo

Device Tree: Device / Samsung / pontesolo

MSM8226-Common: Device / Samsung / msm8226-common

Vendor Tree: Vendor / Samsung / Pontesolo

Main components status

Boot paths: Normal/Recovery/Charge: Charge mode is dead, others are OK

Display: Working, limited ALPM coded. Not dying, but not working as it should

Touchscreen: Working

Vibration: working

Audio: partial (Audio Out + Mic works, bluetooth headset doesn't)

Bluetooth: Working* (Internet sharing, BLE, data connections, A2DP works. HFP/HSP is NOT working -help needed!-)

Wifi: Working

GPS: Working

AGPS: Working

Baseband: Working

Sensors: Partially working (accel, gyro, magnetic, light, HRM, tilt, Palm Down, OK,Context sensor is a Work in Progress)

Power management: Partially working

Thermal control: partial

Latest Android Wear Image:

Beta #4 : [url

https://mega.nz/#!QNABnCRJ!blKdj2t7LeKh8Ro_-ZR0-aEFDfTt0dgoF3SEKol44_Q

[/url]

Post Date: July 6th, 2016

Version: Android Wear MWD48B/ Android 6.0.1

Issues:

Sensor implementation is partial, but functional for casual use

Screen Always ON not working correctly, but not dying either

Battery drain is too high (it survives a day to me, about 16hours)

Hands Free Protocol non functional

Modem unsupported by Android Wear

Most of watchfaces are a bit screwed up because the screen is not square

Latest Cyanogenmod Image:

CM12.1http://www.mediafire.com/download/tiqhu53ve5hvj64/CM_20160221_Zipped.zip

Post Date: February 21, 2016

CM Tree sync date: February 20, 2016

Version: Cyanogenmod 12.1 / Android 5.1.1

Matching Google Apps (if you don't know what to pair it with): http://www.mediafire.com/download/e35w73s81q7u8im/open_gapps-arm-5.1-nano-20150925.zip

GOING BACK TO TIZEN

BE VERY VERY CAREFUL

. PROBLEMS FLASHING THE RECOVERY IMAGE MAY RENDER YOUR DEVICE IN AN ENDLESS BOOTLOOP. TO HELP AVOID THIS, CLEAN UP WATCH'S USB CONTACTS, AND THE DOCK'S POGOPLUGS BEFORE FLASHING THE IMAGE. ALSO USE A STABLE COMPUTER TO FLASH THE IMAGE.

I've rearranged the package flashing order to help mitigate the situation and have a way out in most of the situations, but given the amount of issues this watch has, be prepared for anything. Check the post below for details.

Recovery Image #2: http://www.mediafire.com/download/pu44524rv2vn9st/TizenRecovery_v2.zip

USER DATA PARTITION TEMPLATE

EMERGENCY USE ONLY! Use it if you destroy your data partition and CM/TWRP stop booting: http://www.mediafire.com/download/patgdf2gpdxzkd8/user.zip

Gear S specifications

Qualcomm MSM8226. Quadcore @ 1.2 GHz

512 Mb of RAM

4 Gb of flash, divided in 25 partitions (see below)

Adreno 305 GPU

Qualcomm MSM8226 Audio + Audience ES705

BCM4334W Bluetooth/WLAN controller

Samsung SensorHub (STM32)

Partition layout

aboot -> mmcblk0p8 --> Odin / LK Bootloader

boot -> mmcblk0p16 --> Main Kernel + DTB

csa -> mmcblk0p2 --> Watch params (IMEI, calibration data for sensors, nvram etc)

csc -> mmcblk0p22 --> Localization settings (look csc.img in flash package)

dbi -> mmcblk0p9 --> unknown

ddr -> mmcblk0p10 --> unknown

fota -> mmcblk0p1 --> self explainatory

fsc -> mmcblk0p13 --> unknown

fsg -> mmcblk0p12 --> unknown

modem -> mmcblk0p21 --> Modem firmware files

modemst1 -> mmcblk0p3 --> unknown

modemst2 -> mmcblk0p4 --> unknown

module -> mmcblk0p20 --> Linux kernel modules (mounted on /lib/modules in Tizen)

pad -> mmcblk0p15 --> unknown

param -> mmcblk0p11 --> unknown, probably modem related

ramdisk1 -> mmcblk0p18 --> boot ramdisk - unused

ramdisk2 -> mmcblk0p19 --> recovery ramdisk, unused

recovery -> mmcblk0p17 --> Recovery Kernel + DTB, unused

rootfs -> mmcblk0p25 --> Main firmware (/ on Tizen)

rpm -> mmcblk0p5 --> Part of Trusted Zone firmware - don't touch this

sbl1 -> mmcblk0p7 --> Part of the bootloader chain, don't touch this

ssd -> mmcblk0p14 --> unknown

system-data -> mmcblk0p23 --> Part of personal data, Tizen won't boot if this is corrupt

tz -> mmcblk0p6 --> Trusted Zone for ARM, don't touch this

user -> mmcblk0p24 --> User data partition (2.5 Gb +-)