yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S] johnp1991:
This aw is amazing. It made my watch 10x better. Only problem is battery. I hope you find a fix soon but other then that thank you for your work
[Samsung Gear S] hurdlejade:
"The file you are trying to download is no longer available."

Can you reupload please?
[Samsung Gear S] Beukhof1:
[MENTION=803006]biktor_gj[/MENTION]

You're the man for making this happen.

Only one thing. The new link is down. Could you give us one that works :)
[Samsung Gear S] jhasty01:
[MENTION=803006]biktor_gj[/MENTION] I can mirror, just need file

Anyone have it?
[Samsung Gear S] biktor_gj:
Link is down because the tar file had a problem in it which didn't show when flashing with Odin.

Try this:

https://mega.nz/#!NVBUVLCB!FbwSoRHHD95hM7MHLvWO8oBuQcPO2pqasXaQLqKlDj4
[Samsung Gear S] gingerdude:
The above link takes me to a GNeo file, is the file for the Gear S just labelled wrong?
[Samsung Gear S] Beukhof1:
Im getting a error on this one. "unsupported dev_type"
[Samsung Gear S] biktor_gj:
I need to stop programming for the day, I obviously don't know what I'm doing anymore ;)

This should be your file!

https://mega.nz/#!NVBUVLCB!FbwSoRHHD95hM7MHLvWO8oBuQcPO2pqasXaQLqKlDj4
[Samsung Gear S] Beukhof1:
This is working for me... thanks... btw maybe take a day off ;)
[Samsung Gear S] Logon941:
It's working for you ? Can you make a call with SIM on gear s with this build android wear?
[Samsung Gear S] heat22:
Is it just me or does SetCPU, No Frills CPU control, CPU Adjuster all not hold the freq settings? Seem it adjusts to the min and max at first, then after the device wakes from sleep it no longer obeys these settings. I have Cool Tool on Xposed running in my status bar to constantly monitor cpu frequencies. That's how I realized these CPU control apps are not actually working. I uninstalled Greenify and Juice Defender in case it was causing some sort of conflict but the issue persists. So for now I have to leave the charger/battery attached to get any real good battery life and usage on 5.1.1. Any ideas why these settings don't stay after sleep? Kernel?

Nevermind, CPU Adjuster did the trick after a reboot.

Update: Still does not hold. Seems when you open certain apps it disobeys these CPU control apps settings. Then I have to manually set it again.
[Samsung Gear S] vijay555:
[MENTION=593032]heat22[/MENTION] is that with the per app performance settings enabled (I think in the battery settings?)

V
[Samsung Gear S] heat22:
Yep that was on, never paid attention to it. Disabled it but still, mhz jumps up past 600mhz as soon as I open say the YouTube app for instance. Then it calms back down. I have the cpu set to 300-600mhz Ondemand, Noop. Maybe ondemand allows for spikes in mhz? I'm lost.
[Samsung Gear S] vijay555:
[MENTION=593032]heat22[/MENTION]: yeah I think you may need a more aggressive governor. I think I've used GSam Battery Monitor to monitor CPU states and it seems to reflect accurately when I set the CPU state to a lower speed, although I haven't tracked it for days in active use.

I think it's quite clear that the CPU burns the battery when it's in active use, but in a passive state I can get about 36 hours or so out of the watch once I've used various apps to shut down unnecessary background processes etc.

So I'm more inclined to remove wasteful background processes but keep the CPU "ondemand" (ie able to spike when it needs it) so that the watch remains responsive. in use.

Perhaps we could use tasker or similar to always keep the CPU very low when the screen is off, but ondemand when the screen is on?

V
[Samsung Gear S] heat22:
Yep it was the governor. Changed it to Powersave, CFQ and it stays within the limits set by CPU Adjuster but as you said the device is not as responsive when using certain apps. Playing around with the other option settings now. As far as using tasker for what you suggest, I feel its redundant if you use the Ondemand setting which seems to do the same. Will probably stick with it in the end and set the min and max to 300mhz.

Wait 36 Hours!? Which apps may these be sir? I'm using Greenify and Amplify and CPU Adjuster of course but only make through half a work day. I have two Gear S watches. I have to charge my modded Gear 3-4 times before ever needing to charge my stock Gear lol.

Update: Check marked all the root settings for the Greenify app now the ondemand governor even stays within the limits. See if that'll get me similar battery life to yours. Do you keep yours bluetooth tethered with internet?
[Samsung Gear S] biktor_gj:
Need testers for this... Screen always on for wear!

Flash this kernel over latest Wear release:

https://mega.nz/#!1ERX1QTC!7uFfUfXR4e8bOL6ap8FgKHmmCqe12TjwWuoCrL4FEUk

IMPORTANT: If you're using tizen and you flash this you'll get a bootloop!

Then do a test run of the battery with screen always on enabled, and disabled, comment battery life in q&a thread :)

My watch expects 22 more hours of runtime with 92% battery and screen always on, let's see if we got our battery back!
[Samsung Gear S] computerguru:
[MENTION=803006]biktor_gj[/MENTION] - I should be able to flash the kernel tomorrow when I get my new charging cradle.
[Samsung Gear S] DQEight:
disregard
[Samsung Gear S] rebel1699:
Going to flash fresh 7-8 aw and kernel right now. I'll monitor for the next 24 hour period and report back with my usage and findings.
[Samsung Gear S] lachywallace:
Fair enough :/
[Samsung Gear S] minjoon0312:
Can someone please upload videos that shows running CM12.1 on Gear S?
[Samsung Gear S] biktor_gj:
Ho ho ho, christmas is early this year!

MODEM IS WORKING​

Asks for the PIN code, gets network coverage, and calls do work. Audio is routed to a non existant device though, so unless you put the speaker on you can't hear a thing, and I think microphone isn't working. Also, there's no 3G data. It starts but doesn't seem to be binding or it is being blocked by netfilter or something, we'll see...

View attachment 3470928 View attachment 3470929

Oh, and did you know what it was? After all the code I've read, it was... This: (init.ponte-solo.rc)

# Subsytem Restart

#adsp

write /sys/bus/msm_subsys/devices/subsys0/restart_level "related"

#modem

write /sys/bus/msm_subsys/devices/subsys1/restart_level "related"

#venus

write /sys/bus/msm_subsys/devices/subsys2/restart_level "related"

# Allow subsystem (modem etc) debugging

write /sys/module/subsystem_restart/parameters/enable_debug 1
[Samsung Gear S] gidi:
You are Santa and you are early this year!!!! WTF? What happened between your previous posts and the last one?

Lemme open a good bottle of wine I have been keeping for years!!!
[Samsung Gear S] biktor_gj:
What happened is that my hunch was correct. After examining the way the QMI_CSI driver made the tizen kernel crash in the "related" mode instead of "system" mode (which means related=modem reset, system=full phone reset) I looked more into the modem sysfs entries and started trying different settings, until eventually, I found what makes it tick ;)
[Samsung Gear S] gidi:
Dude, you are bigger than Elvis. We love you.
[Samsung Gear S] biktor_gj:
I've pushed all the modifications to Github:

https://github.com/Biktorgj/android_device_samsung_msm8226-common

https://github.com/Biktorgj/android_device_samsung_pontesolo

https://github.com/Biktorgj/vendor_samsung_pontesolo

https://github.com/Biktorgj/Gear_S_Kernel

Next on the list: Screen suspend & resume and thermal. When both things work correctly (right now if the screen shuts down the watch dies and reboots), I will post the first flashable image.
[Samsung Gear S] gidi:
Eagerly waiting...
[Samsung Gear S] glos7777:
woow you are the best :)
[Samsung Gear S] andrew.mackew:
Kudos! :) You're really, but really, skillful and a genius! Looking forward to flash it when ready! :o God bless you! :good:
[Samsung Gear S] Shum Channel:
Oh Gods! You did it, man! Now, our optimism is boundless!
[Samsung Gear S] Andycar:
And another round of applause to this great achievement!
[Samsung Gear S] almony8:
Excellent work, I couldn't be more excited for full android on the gear s. Patiently waiting and hoping for this, keep up the awesome work. Finally got my sprint gear s rooted, hopefully that means this will also work on the sprint variant
[Samsung Gear S] biktor_gj:
I'm a bit scared of how much RAM would that kill...

Anyway, if you want to try the modem, the easiest thing would be:

Pick this zip from here:

http://www.mediafire.com/download/nb3iih6e02uh5w0/targeted.rar

Boot the watch to android with the build that you have

Once you're in android, (remember to enable screen always on in developer settings/ set screen timeout to 30 min)

If you have ADB set in your path variable (you can run adb from any path), just go to where you unzipped the file and run "push_it.bat"(EDIT: Without the "_"; XDA, your word filtering just broke my instructions!). If you don't, then copy adb+libraries to the folder

After it has pushed everything and rebooted to download mode, flash the kernel in the same folder with the Odin window that just opened and on next reboot modem should be working without needing to recompile the entire source ;)

I found one more problem with the wifi that's making the kernel crash, by the way. It seems to be related to a kernel patch pushed to AOSP, so I hope that's an easy fix :)

https://android.googlesource.com/kernel/msm/+/8528e86900a975d93cbaca9b4d2ab2e1bc605f5c

About brightness, found what's killing it. Tried 5 different solutions but none of them are working yet (hint: DSI clock halts and never comes back)

About thermal: using tizen config. It's still hot, but that'll do for now, we'll see how it works when the display can be shut down properly...

And in case someone with the Gear2 is reading, I found the problem with the translator app crashing half the framework... The libmedia.so I need so the hwcomposer keeps running makes audio crash at some points with the latest version. Looking for a solution for that...
[Samsung Gear S] pippo_105:
You're a real Santa, pal! Thank you!

OK I know you'll kill me, but is there a little possibility to have, in future, a dual boot Tizen/Android for Gears S? It would be the Egg of Columbus: the notifications with a smartphone (when paired), and the freedom of android when solo. ^^
[Samsung Gear S] biktor_gj:
I'm affraid not. Despite it would leave the watch with zero space available for anything (4Gb is not enough), there would be too many problems:

Kernels compiled manually don't boot tizen, so you can't make a custom kernel to allow multiboot, but you can't use tizen kernel to boot android either

I'm replacing the csc partition, so we would loose recovery in android to keep tizen booting

Don't want to even think about the issues with the modem ;)

Permissions on data partition are different and make tizen crash when coming from android (even if it could be fixed on each boot its a problem)

In the end you would need a custom bootloader chainloaded to lk/odin flashed as a kernel that would allow to boot kernels from somewhere else... Too big of a mess to end up having 100mb free for apps ;)
[Samsung Gear S] pippo_105:
In the bottom of my heart i knew it. Thanks for your time. :)
[Samsung Gear S] gidi:
I think that we can have notifications indirectly through a service like push bullet.

Tizen OS Gear S supports remote connection through wifi/cellular data with a Samsung phone.

If we run full Android on th watch we can pretty much do anything.

Personally speaking, i think that standalone is what this beast was created for.

BTW [MENTION=803006]biktor_gj[/MENTION] do you think we could have BLE working on the watch?

Again thank you!
[Samsung Gear S] Kirrrr:
There is SWAppLink app for Android-->Android notifications.
[Samsung Gear S] lachywallace:
Wouldn't it be better to port android wear instead of cm?
[Samsung Gear S] cerico76:
I'm going to flash it tomorrow! So excited! Thanx a lot!
[Samsung Gear S] computerguru:
Just flashed the 7/8 build and the "screen always on" kernel. Will report back in the next couple days.
[Samsung Gear S] computerguru:
[MENTION=803006]biktor_gj[/MENTION] - one issue I'm noticing is some screen anomalies...where the colors are completely off and it has scan lines...like an old CRT. This is with "always on" turned on. It'll do that for a minute or two, then correct itself. Managed to grab a video of it happening earlier. Ignore the red blinking dots...that's my Kinect infrared sensor reflecting on the watch.

[YOUTUBE]csz451fLb34[/YOUTUBE]

Also, sometimes if you press the button to turn on the screen, then press it again to turn off...it fully turns off the screen...even though always on is enabled.

Also, don't know off this has been reported yet (hard to sift through 140 pages of "ermagerd...this is great"/"when is the next update" posts...haha), but the touch screen sensitivity seems a tad bit sensitive throughout all these builds. I have to lightly tap to get it to register as a tap...otherwise it registers as a gesture. Makes it difficult to select menu items.

I'll still continue on with my battery tests.
[Samsung Gear S] primod808:
Computerguru certain watch faces on the gear a doesn't play nice. Had the same problem you had try to use another watch face see if that helps.
[Samsung Gear S] computerguru:
[MENTION=3756476]primod808[/MENTION] - The display issues have been happening in random places...thinking it's not watchface related. In fact, the video above was of the initial syncing right after pairing...so no watchfaces were running at that time. :-/
[Samsung Gear S] rebel1699:
I can confirm. This also happened on mine during the initial sync. Lasted about 10 seconds, and cleared up. Only happened once since, when watch was waking to normal screen. Again, only about 10 seconds.
[Samsung Gear S] lauerp:
It happens for sure when I receive calls on the cellphone and I answer on the phone. Right after answering in the phone, the watch bugs.
[Samsung Gear S] primod808:
Ok it might be a rouge app. From my experience from early AW BUILDS i had that CRT screen of death and the way i found out it was and app that didn't play nice with my gear s. Once i disable notifications from that app within the AW app the CRT SCREEN OF DEATH was gone.
[Samsung Gear S] computerguru:
So far...so good w/ always on. Been off the charger with light usage since 7:00/7:30 AM EST. It's 4:15 PM now...I'm at 74%...and it says I still have a day left!
[Samsung Gear S] LenAsh:
All posts that should be in Q and A have magically disappeared.... as foreseen. Twice.
[Samsung Gear S] computerguru:
Update - been off charger since 7:30 AM EST yesterday...and now at 5%. Looking like 33 hours with light usage and "Always On" mode enabled. I'll start tests w/ it disabled tomorrow.
[Samsung Gear S] biktor_gj:
Yepp that's my bug :) I'm making it enter Amoled Low Power Mode too soon and sometimes, when waking up, it's not disabling it just at the time it should (there are some commands that need to be sent to the LCD to disable the function) so the screen ends up in fully working mode while it's still thinking it should be sleeping. So far so good, that can be fixed :)

The screen not refreshing is going to be harder, since it seems the frame is not refreshed while the watch enters suspend mode (I thought I fixed that when I made it force-enter vsync suspend when the Kernel power management engine enters full suspend but obviously is not enough :))

But, all in all, with all the bugs that need to be smashed, that's not as bad, we've gone from 12 hours of battery runtime to about 24, so, even with all the issues(that won't arise with screen always on disabled) will stay with this codebase

Edit2: for all of you who want to know how alpm works on wear, or any other porter out there...

With screen always on mode set to off the display enters two states on framebuffer driver:

FB_BLANK_UNBLANK

FB_BLANK_POWERDOWN

When using screen always on, we start with UNBLANK mode on boot, then we switch to VSYNC_SUSPEND when entering Low Power Mode and every 20 seconds or so, we switch between VSYNC and FB_BLANK_NORMAL to allow a screen refresh, and it normally sticks to blak_normal when powered on. Sometimes though, you still end up in blank_unblank mode after sometime and that's where I'm getting it a bit messed up

Edit: about the touchscreen... It's always been bad for me, it seems like the curved screen makes it a bit harder to press into the "touchable" screen sections in Wear. I will take a look to it, maybe there's some calibration kernel side, or some modification on density side that can help enlarge that physical->virtual mapping on touch events... Will take a look!
[Samsung Gear S] wyldphyr3:
I just flashed 20160708 together with Kernel 20160715 (coming from 20160622) via Heimdall. So far, so good.

Afterwards I wanted to to wipe the watch. I know that it's not needed, but since it's no big fuss to re-sync the watch, I just wanted to be sure. When I entered recovery (directly after flashing), it showed up, but when I pressed "Wipe" the screen went blank and I wasn't able to turn it back on again. But it felt, like the watch was still getting touches. Since it was vibrating with every touch. I was very careful while touching the blanked screen, since I did not see what I was touching. Wipe obviously did not work. I tried this several times (rebooted every time) and I also tried pressing another option in recovery, which resulted in the same behavior.

First boot of the system worked fine though. Looks like a bug with the new kernel and the recovery to me.

Edit: System also works fine (did a wipe from Settings, since I already unpaired on the phone). I love that screen always on mode so much that I have disabled tilt waking in favor for it. In most cases I just want to see the time and in these cases the wakeup time for tilting often bothered me. So always on is a better solution me. If I need more than the time I can still push the button.
[Samsung Gear S] rebel1699:
Any idea why the q&a thread is not showing up in the official xda app?
[Samsung Gear S] borispoesen:
working great

android wear is running really Smooth on my gear s,

i don't use always on so can't say if it bugs,

but for me the watch is doing everything it needs to do

and battery life is really nice

thank you for your hard work
[Samsung Gear S] akarui_kage:
Hi,

very nice work bringing Android Wear to the Gear S. Unfortunatly the download link is not working :(

(new user cant post pictures or url's)

ranpunokasa.me/error.png
[Samsung Gear S] computerguru:
Update on "Always On" disabled battery test: Been off the charger since 7:30 AM EST yesterday w/ moderate use...and at 53%. Current estimate is it'll run out of juice at 3 PM tomorrow. 57 hours is pretty fantastic for moderate usage! And during the first few hours yesterday, it was estimating 4 days at light usage!!!

Having that good of battery usage will make re-enabling the modem down the road a bit more tolerable. :) Thanks for your hard work [MENTION=803006]biktor_gj[/MENTION]!
[Samsung Gear S] kekken3:
Could somebody please reupload it?
[Samsung Gear S] computerguru:
The download links on the first post do appear to be broken...but the links on page 141 work just fine:

http://xdaforums.com/gear-s/development/dev-gear-s-android-port-t3177740/page141
[Samsung Gear S] satjunkee2016:
Just registered to add my thanks on building this ROM and tweaking the kernel.

Running light usage on the 7/08 image and 7/15 kernel. Off charger at 6am with Always On enabled, Gestures Off, and WiFi Off. Didn't get the same run time as some others here but still made it to 10:30pm with 21% left. Over the last few days had the screen bug only once and it rectified itself during the next screen sleep. Many thanks biktor_g for your work. You've made my upgrade from a Sumsung Note 3 to Nexus 6P much more agreeable now that I can still use my Gear S.
[Samsung Gear S] biktor_gj:
Testing a new cyanogenmod 12.1 build right now...

Mostly patching all the fixes I made for Android Wear, now Cyanogenmod has palm down to suspend, step counter support etc... With modem and wifi, 7 hours, 53℅ with little use

Testing the important stuff [emoji1]

Meh, needs more RAM...
[Samsung Gear S] Deezy88:
what version you have of cm11,the one i had so so useable, battery lasted 50 mins
[Samsung Gear S] Djingi:
Please give us a Link to your new build

btw i love your work!

greets from Germany
[Samsung Gear S] DQEight:
Oh god, how about with swapper for root?

I don't want a wrist oven though but cool to see lol
[Samsung Gear S] MasterPo:
Hey biktor_gj,

Really love your work, since I follow this thread and use your builds from the very beginning. Here's my question concerning usability of CM with smartphones. The first "Galaxy Gear" based on true android was rootable with "NullROM". Don't know how it communicated with Gear App on Smartphone, but isn't there a possibility to implement this "communication pack" in your own CM builds?

Of course I can send you a download link for "NullROM" Build 23...

I appreciate what you're doing and would love to support Gear S becoming an "everyday-use device"
[Samsung Gear S] DQEight:
From what I remember from when I had my gear on nullrom is that it didn't communicate with phone just like with cm on gear s. The most you could do is pair the two with Bluetooth for internet sharing.
[Samsung Gear S] chiikko561:
Thanks brother. I been waiting for a new cm update. The last update runs great for me so I know this update will just be a cherry on top... [emoji1]
[Samsung Gear S] G1NT0NN1C:
Try pushbullet. It works fine on the Gear s with CM.
[Samsung Gear S] :
I sorted through Codes but still can find what was causing the error with bluetooth headset?

Most Internet calling apps gave me know luck ?

I still I still got a couple more things I want to try have you had time to look into this issue as well??
[Samsung Gear S] -LBT-:
I personally wouldn't want to rely on any internet, cloud-based service for the notifications.
[Samsung Gear S] MasterPo:
NullRom 23 worked fine for me. No problems. Never. If this would work somehow, it would be the easiest way, since Gear Manager runs on every smartphone. First Galaxy Gear was running KitKat, this could be the only problem "pushing" it into CM 12 or 13... :(
[Samsung Gear S] Ngiphone:
cant pair AW 20160708 with nexus 5

hey guys I just flashed 20160708 on my Gear S watch (Gear s) is up with AW but when trying to pair the phone (nexus 5) does not find it

any ideas on what im doing wrong here ?

factory reset solved it ! its now pair and working amazing !
[Samsung Gear S] Ngiphone:
dialed for Gear S AW

hey Guys, the version is runing fantastic but as i understand the SIM call in\out so the watch will be able to call on its own does not work . is it the same with you guys ? no way to make it work as this one of big things from the Gear s

thanks for an amazing job !
[Samsung Gear S] rebel1699:
This is covered in the op
[Samsung Gear S] Logon941:
Hi guys... i'm willing to buy this smart watch and use it like a standalone phone:) because of this thread of android wear rom and CM rom.... so i'm asking you to help me with some advices. Is there any diference between the korean version and european version? I found some cheap korean gear s on ebay...
[Samsung Gear S] kevmass:
MOD EDIT: NO SELLING ON PUBLIC FORUMS
[Samsung Gear S] vijay555:
None that I'm aware of once you re-flash it. I'm using a Korean version in Europe. Before you flash it the device is in Korean (ie syncing instructions to a Samsung).

V
[Samsung Gear S] arieluya:
I found answers to this and more here :svetius:

BTW, flashed AW (downloads from posts #1401 and #1409), been there done that. Cute and all, but still prefer full Android - more fun! :D

AW: Found the CRT issue and the touch issue (Biktor is aware of both) - difficult to freely navigate, seemingly because of the curved display. Would be cool to code some watch faces specifically for this screen size, just for the fun of it and to proof that AW actually works with this device. Skype self-installed, but after tapping on the icon, it never opened.

Going to re-flash CM and start reporting on it.
[Samsung Gear S] samsow:
hello guys , after going back to tizen succefully following all the steps i only get 2 GB memory instead of 4 GB .