[DEV] Gear S: Cyanogenmod & Android Wear Ports
Breadcrumb
biktor_gj
Senior Member
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.
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
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 +-)
biktor_gj
Senior Member
There seems to be a lot of people falling into the bootloops when coming back to Tizen, so I thought I would try to explain, again, what causes it, and how I got out of them every time.
The reason for the bootloops
The reasons for falling into the bootloop is a combination of some factors:
1. The bootloader in this watch is poorly coded The bootloader resets the power key status on each reboot, unlike most of other ODIN based bootloaders, so when the watch reboots, the key gets released and then reattached.
2. The kernel panic reboot time is set to 0 on stock kernel. The kernel is configured in a way when there’s a critical error (a kernel panic), it automatically reboots without spending the DEFAULT 5 second delay before rebooting
3. When moving from Android to Tizen, or from Tizen to Android, the init binary is moved from one partition to another The way I’m building this ROM, moves /sbin/init from the 25th partition (/dev/mmcblk0p25 -rootfs- ) to the 19th partition (/dev/block/mmcblk0p19 -boot-). The thing is, if you, for example, mix and run the stock tizen kernel with the Android Root FS, it will look for the init binary in partition #25 instead of #19. As it won’t find it there, it will panic and reboot endlessly. That means that if Odin fails after flashing the Tizen Kernel, but *before* the rootfs, you might end up in a boot loop.
Ways I’ve fallen into the bootloop
When modifying boot images and not setting correct permissions and/or making mistakes in permissions in boot files. If you’re playing with the boot image for Android, and you set the wrong permissions to /init or /sbin/init, or you make a big mistake inside the init.*.rc, the kernel will panic just after mounting the boot partition, forcing a reboot.
When corrupting the rootfs partition in Tizen: If you took a backup of it and it wasn’t in good condition, after you restore it if the Kernel cannot correctly mount it, it will panic and reboot all the time. Since the kernel needs about 2 seconds before mounting the partition, it will panic before you have your 5 seconds to force the hard-reboot
When flash process failed at the wrong time. You’re there, reflashing Tizen, and the dock misbehaves and drops the USB connection, or your PC halts, or the watch reboots (all of them happened to me at some point). The flash process fails when it’s in the middle of flashing the rootfs but the Gear’s bootloader doesn’t notice it. The rootfs partition gets corrupt, but when you reboot the watch, instead of automatically entering download mode and showing a screen saying «There was an error, connect to Kies to recover» the watch bootloops when trying to mount the root partition.
When flashing the wrong kernel It’s possible that some kernels from some firmware don’t contain the needed DTB board definition for the revision of your watch. Happened to me with some older firmwares.
HOW I GOT OUT OF THEM
So, you’re stuck. You’re pretty much f***d up, aren’t you? Let’s try some things.
1. Check if you’re really f****d.
Let the battery drain, so the watch will shut down completely, and let it cool down. Depending on the battery you had it might get quite warm.
Got it? Good. Clean both the dock’s pogoplugs (the connector), and the charging contacts on your Gear S.
If you have a backup battery equiped dock, have it with some charge, if you don’t, have a wall charger available.
YOU HAVE A BATTERY BACKED DOCK:
Connect it to the watch, without connecting the dock itself to anything. If you see the battery logo, you’re good.
YOU HAVE A DUMMY DOCK:
Connect the dock to the wall adapter, then connect it to the watch. If you see the battery logo, you’re good.
*IF IN ANY CASE YOU CONNECT IT TO A USB PORT ON A COMPUTER, THIS WON’T WORK* The watch will detect it’s connected to a computer and will start in a different boot mode.
*IF, WITH THE BATTERY BACKED DOCK, IT GOES STRAIGHT TO THE GEAR S LOGO, I DON’T HAVE A CLUE ON WHAT YOU CAN DO, NEVER GOT INTO THAT*
Let’s say it’s not as f****d up as to not show the battery logo, proceed to step 2.
1. Measure the time it takes, between the moment you connect the dock/charger and the moment the screen turns on to show the battery logo. Once you have it:
2. Disconnect it and let it shut down again.
3. Connect again, and start pressing the power button JUST BEFORE THE SCREEN TURNS ON. Timing is key, and IT IS HARD TO FIND . As I said numerous time, the first time I got it, I spent about four hours trying to get it right. I finally found the exact time, but I can’t measure it in miliseconds. You will need a lot of patiente. Once you’ve been there once, if it happens again you will get out of it faster.
WAYS WE CAN HELP AVOID THE SITUATION.
My Android images are safe. No Android firmware I’ve posted should leave you in a bootloop. But, depending on your bootloader, and your model, my Tizen Restore Firmware can cause you issues while flashing which might end up in a boot loop.
1. Know your device. My Tizen Restore Firmware is based off R750XXU1BOA7. This means it’s designed for SM-R750 / SM-R750Z. *THIS IS THE ONLY DEVICE I HAVE TESTED WITH, WHICH IS MY OWN*. A lot of other people has restored their watches with this same firmware, but obviously, there’s a bunch of people who’s having issues with it.
2. Backup your system-data partition You can use others’ backup, but keep in mind you’re exposing your data with it. Also keep in mind that your system-data partition is tied to the Tizen release you were running at the point of backup, so it might get messy when you restore another firmware on top of it.
3. Have a known full flash that you know works for your watch . I only provided my Tizen restore package as an emergency in the early days. People shouldn’t flash it blindly. You should have a good full firmware package which you *have already flashed* before even trying to flash Android, so you know you have a good set to come back.
4. Clean the USB/Charging contacts before you begin, on both the watch and the dock . This is a watch, and has constant contact with your skin. It gets dirty. Before you do something sensible as wiping the NAND and flashing something over it, do your best to ensure that the connection to the computer will be stable while it’s in this process. Numerous times Odin has failed on me because of this.
5. If you find this hard to handle, you shouldn’t be doing it! This watch wasn’t correctly made. You need to know what you’re doing and in case you have problems you will need to have the necessary knowledge to fix it. This is not your average flashing, this is not a Nexus phone. This is a buggy watch made for a different OS, and might present different issues than those you may have found playing with other watches/phones.
WE CAN MAKE TIZEN RESTORE FIRMWARE VARIANTS TO HELP OTHERS, BUT I NEED YOUR HELP.
I can make recovery firmwares for the different watch variants, but I will need you to provide me with:
* Your Watch Model
* A backup of your system-data partition (better if it’s a clean backup, with the watch unpaired and the least amount of settings configured)
* A Full firmware that you know runs on your device: You can know if it’s a full flash if you open the TAR package and it has at least, some of the following files:
— dzImage
— aboot.mbn
— modem.bin
— rpm.mbn
— tz.mbn
— rootfs.img
You can post them in this thread and I will do my best to package them and post them in the first post.
I WON’T ANSWER PRIVATE MESSAGES REGARDING THIS ISSUE. If you want to PM me for helping me on development related stuff, feel free to do it. If you want to thank me, it’s okay. If you’re going to ask me for help because you didn’t read the warnings, the instructions, or didn’t do your job I won’t reply. You have the Q&A section for Q&A related questions, and I have explained this quite some times already. I won’t tell this everytime someone f*cks up. I simply don’t have time to do that, and the little time I have I’d rather use it on actually working with the watch to make it run Android better.
Источник
Android Wear apps modified for Amazfit Pace?
Breadcrumb
sammis9
Member
there’s a place where I can find some good app (apk) modified to works on my Amazfit Pace? I’ve already installed ADB.
m.Tamaro
Member
Senior Member
Yes, it is possible. The info was provided in another forum (requires registration), for watches that use full Android instead of Wear, like Amazfit Pace. I’ve found this info here:
http://amazfitcentral.com/2017/11/16/use-android-wear-apps-amazfit-pace/
I have successfully ported some, it’s not that hard. Most apps for AW 1.5 that doesn’t require the companion phone app to work are very easy to install on Pace.
sammis9
Member
Delinux
Guest
Yes, it is possible. The info was provided in another forum (requires registration), for watches that use full Android instead of Wear, like Amazfit Pace. I’ve found this info here:
http://amazfitcentral.com/2017/11/16/use-android-wear-apps-amazfit-pace/
I have successfully ported some, it’s not that hard. Most apps for AW 1.5 that doesn’t require the companion phone app to work are very easy to install on Pace.
shadowcaster666
Senior Member
These are all apps that I found on forums and such while looking for Pace compatible apps. They should mostly work (I haven’t tested all of them). As far as I know all of these apps are free. If anyone is the owner/developer of any of these apps and would like me to remove them let me know.
Delinux
Guest
These are all apps that I found on forums and such while looking for Pace compatible apps. They should mostly work (I haven’t tested all of them). As far as I know all of these apps are free. If anyone is the owner/developer of any of these apps and would like me to remove them let me know.
yangba
Member
Thank you for the Amazefit Pace compatible apps.
I have been looking for «A Scheduler» application for Amazfit Pace where I can schedule an appointment a month or 2 months later, an an alarm or alert will notify me at the scheduled time.
If anyone here can help me with that application I will be very very happy.
———- Post added at 05:05 PM ———- Previous post was at 05:01 PM ———-
Thank you for the Amazefit Pace compatible apps.
I have been looking for «A Scheduler» application for Amazfit Pace where I can schedule an appointment a month or 2 months later.
If anyone here can help me with that application I will be very very happy.
yangba
Member
«A Scheduler» application for Amazfit Pace
Thank you for the Amazefit Pace compatible apps.
I have been looking for «A Scheduler» application for Amazfit Pace where I can schedule an appointment a month or 2 months later, an alarm or alert will notify me at the scheduled time.
If anyone here can help me with that application I will be very very happy.
Senior Member
Thank you for the Amazefit Pace compatible apps.
I have been looking for «A Scheduler» application for Amazfit Pace where I can schedule an appointment a month or 2 months later, an alarm or alert will notify me at the scheduled time.
If anyone here can help me with that application I will be very very happy.
This apps works well with small round displays, and can sync over wifi so you can use your computer or phone to enter data and read it on your watch:
— TickTick (very good reminder app even in free version, can connect with Twitter or email account)
play.google.com/store/apps/details?id=com.ticktick.task
TickTick usually uses RAM while on background (needed for sync and notifications, of course), otherwise it performs very well. I just wanted TickTick to remove the top bar when scrolling an item when viewing it.
yangba
Member
Tick Tick Installed on Phone
Hi
Thank you very much for the reply.
I just installed the Tick Tick in my Mobile phone, but this app is for Mobile phone and not for Amazefit pace watch.
Is the Mobile app able to remind me on my Amaze fit watch.
Thanks in advance.
Senior Member
Hi
Thank you very much for the reply.
I just installed the Tick Tick in my Mobile phone, but this app is for Mobile phone and not for Amazefit pace watch.
Is the Mobile app able to remind me on my Amaze fit watch.
Thanks in advance.
wayfactory
Member
Senior Member
$ilvano
Member
Spekk
Member
Stopwatch wear app
I tried to install the ported stopwatch wear app (StopwatchTT.apk) to stratos but if gives an install error (not supported)
I can’t get android studio to work (Error:Android Source Generator: Error: Can’t find bundle for base name messages.AndroidJpsBundle, locale nl_NL ) and i don’t know how too.
Somebody here who can make it work for Stratos or give me some guide how i can make it work with Android Studio?
The original stopwatch is laggy and verry diffcult to touch
yangba
Member
Tick Tick application not available for watch
Senior Member
Hello. Did you read my previous comment? You must download and install the regular app (the same used on phones) to the watch. Then open it and choose the account to sync it using WiFi.
Once TickTick is installed on watch, connect with your Twitter account (you must have done this on phone too, same account, so it can sync to watch). You will need a browser, I recommend installing XBrowser on watch too, it is small and works well. You may want to install PaceOn too, it turns WiFi on and keep the screen on so it doesn’t disconnect.
———- Post added at 16:07 ———- Previous post was at 16:01 ———-
Sorry, but I don’t like to apps outside Play Store. That said, I have used files downloaded from APKMirror or APKPure (I can’t guarantee this one is safe), OsmAnd is version 2.5.3 and Galileo Free is 1.6.6.
Regarding hiking, I have tested both regular apps (the one that runs on phones) and they work somehow on Pace too, ViewRanger is very sluggish, but AlpineQuest runs surprisingly well (only the paid version records tracks tho):
https://play.google.com/store/apps/details?id=psyberia.alpinequest.free
yangba
Member
Tick Tick application unsupported in Amazefit
Hello. Did you read my previous comment? You must download and install the regular app (the same used on phones) to the watch. Then open it and choose the account to sync it using WiFi.
Once TickTick is installed on watch, connect with your Twitter account (you must have done this on phone too, same account, so it can sync to watch). You will need a browser, I recommend installing XBrowser on watch too, it is small and works well. You may want to install PaceOn too, it turns WiFi on and keep the screen on so it doesn’t disconnect.
———- Post added at 16:07 ———- Previous post was at 16:01 ———-
Sorry, but I don’t like to apps outside Play Store. That said, I have used files downloaded from APKMirror or APKPure (I can’t guarantee this one is safe), OsmAnd is version 2.5.3 and Galileo Free is 1.6.6.
Regarding hiking, I have tested both regular apps (the one that runs on phones) and they work somehow on Pace too, ViewRanger is very sluggish, but AlpineQuest runs surprisingly well (only the paid version records tracks tho):
https://play.google.com/store/apps/details?id=psyberia.alpinequest.free
Thank you very much for the reply.
Tick Tick apk is unsupported after installation it does not open.
This apk needs to access google play.
Источник
