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.
This thread is about development of Android Wear for Gear S
DISCLAIMER
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
GITHUB REPO: Github Android Gear S Kernel Repository (also called Ponte Solo)
Recovery:: Recovery boots and ADB is available. The recovery binary drops a Segmentation Fault when trying to open the framebuffer (no idea why, both CM's and TWRP drop it)
Android: Not booting. It starts to boot but gets in an endless boot with the bootanimation going on an on...
PROGRESS AND BOOT IMAGES WILL GO HERE... WHEN THEY ARE READY!
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 +-)
Android Wear for Gear S
This thread is about development of Android Wear for Gear S
DISCLAIMER
Code:
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.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
GITHUB REPO: Github Android Gear S Kernel Repository (also called Ponte Solo)
Recovery:: Recovery boots and ADB is available. The recovery binary drops a Segmentation Fault when trying to open the framebuffer (no idea why, both CM's and TWRP drop it)
Android: Not booting. It starts to boot but gets in an endless boot with the bootanimation going on an on...
PROGRESS AND BOOT IMAGES WILL GO HERE... WHEN THEY ARE READY!
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 +-)
Aucun commentaire:
Enregistrer un commentaire