yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S] SweetBearCub:
Why the hell did you quote a post more than a page long post to add a 1 sentence plus signature comment?
[Samsung Gear S] DQEight:
Excellent. One step closer to going back to this being my main watch over the Microsoft band.
[Samsung Gear S] AlexSMR:
biktor_gj, It has turned out to run on wear WIFI and GSM?
[Samsung Gear S] biktor_gj:
Small update

Small update on Android Wear Build.

Changes:

Fixed and enabled touchwake (tap on screen to wake up the watch)

Brightness control working

New sensor library (WIP) with partial sensor support.

-> Working correctly: Accelerometer, Gyro, Geomagnetic sensor

-> Partial: HRM (enabled and processing correctly, android doesn't seem to understand it yet). If you want to help, hep me find out why Fitness reports a time out after receiveng the sensor data -check logcat -

-> Missing: Context Sensor (ssp_sensorhub, ssp_context): Step counter, Step detector, Gesture control

-> Modified some power saving stuff, don't know if it's better or worse... we'll see!

https://mega.nz/#!wYJlUDzC!kAk-ljxNqU3J4TDSMkS6VtJ_HJ-hVyDD0RTqIXM2Nao

Google Fit now reports steps, but don't have a clue on how it does that without a functional step counter, it's probably doing something with accel & gyro sensor, but results aren't any good. Anyway, just so you know :)

Have fun
[Samsung Gear S] AlexSMR:
It has turned out to run on wear WIFI and GSM?
[Samsung Gear S] ash786i:
[MENTION=803006]biktor_gj[/MENTION] Clean install or over previous Wear??

Thanks for all your hard work :)
[Samsung Gear S] biktor_gj:
Not absolutely required, but Google Fit won't see the new sensors (even if they don't work yet) unless you wipe, so you dont need to do it now, but if it gives any issue, wipe just in case
[Samsung Gear S] cerisu:
Just flashed over the Tizen. After flash, format data and ewerything seems to work fine. Still testing. I`ll report more later.
[Samsung Gear S] Yorgo1982:
keep rebooting

i keeps rebooting. only one time it stayed for 20min and than it rebooted again.

any idea ?

i have the R750W

and by the way when wiping data E:Unable to mount '/recovery'

Thanks
[Samsung Gear S] biktor_gj:
Did you disable Screen always on in settings?
[Samsung Gear S] Yorgo1982:
I tried both.
[Samsung Gear S] fourcute:
I tried. my situation is similar to that of Yorgo1982 . already return TIZEN
[Samsung Gear S] Yorgo1982:
i think on my side its fixed, i tried it all the day to make sure before that i give the result.

so the wipe of data dont do it in recovery ( as it didnt work for me at all ).

when u r in android wear and synced turn off the always on from the phone.

in android wear go back to settings and unpair it, its gonna wipe it and restore it ( without error msgs in recovery )

now go back and pair it as soon as its paired in the phone android wear app turn on the always on. et voila.
[Samsung Gear S] rubycoru:
I had the same problem kept reset my watch , but when you turn off the option screen always on , the problem was solved , the only drawback I see right now is that google fit does not work as it should , otherwise all pretty good, battery lasted me 16 hours.

I used the google translator for this, I hope that is well understood as I am Spanish

Thanks for your job biktor (^^)
[Samsung Gear S] lachywallace:
I really cant wait till gestures work :))
[Samsung Gear S] fourcute:
thanks for biktor_gj and yorgo1982. how to see the hrm? i use the app hear trace ,but no data out.

---------- Post added at 03:58 PM ---------- Previous post was at 03:52 PM ----------
[Samsung Gear S] ItzShadowz:
Have to admit the battery has been slightly improved especially when sleeping. My battery was around 80% and dropped around 25% overnight around 9 hours. You may not think it's much of an improvement but compared to how much it dropped before I'd say it's quite a step forward.

Enjoying the newest build so far! Really glad brightness and tap to wake (or whatever it's called) is working, great work!
[Samsung Gear S] gingerdude:
agreed battery definitely improved, no force closes. flashed with no wipe. oh and the tap to wake is great. thank you very much.
[Samsung Gear S] fourcute:
battery
[Samsung Gear S] divine1250:
I have one word for the development on this project...EPIC!!!! So epic I had to post a comment which I stopped doing a while ago(too many immature so-called adults). I have been silently following this thread from jump and I have flashed both CM and AW but eventually stuck with AW for ecosystem purposes. I never posted about issues that I came across because I believe that if a dev actually posts a ROM its stable enough for those with knowledge on flashing AND troubleshooting to tweak things that may help iron out bugs. Therefore I only post to help a fellow member or members when I know the answer to his or her problem or to say this to a deserving dev "biktor_gj my friend, You Are Awesome Man"!!!…. Thank You For All Your exceptional work!
[Samsung Gear S] dna556:
Thanks for the very hard work to let us find out absolutely incredible android experience on Gear S!

There are 2 minor questions about CM12.1

1. BT headset with phone calls and messengers - will it be fixed anytime soon? It's the only thing that can't let the Gear S on Android be a daily build.

2.Battery life, with ur build 31 kernel it is better, than with the last one, but there were screen glitches.

Looking forward to test your new roms! Thanks again for making it all possible.

BTW it plays music with my a2dp sbh-50 like a charm. No issues except battery life.
[Samsung Gear S] DQEight:
He says he's given up on CM in tthe q&a thread because it's too restrictive with only 512mb ram.
[Samsung Gear S] rebel1699:
No, he said he is giving up on CM13. He is still working on 12.1.
[Samsung Gear S] DQEight:
My bad then.
[Samsung Gear S] biktor_gj:
Aaaaand we're counting steps! Not sure how accurate it is, but at least it's counting!

Oh, wrist tilt gesture working too!

Remaining(sensors side)

Make the HRM report events like it should (it should be working but obviously something doesn't work)

Make virtual sensors: linear acceleration/significant motion (that should fix the rest of the gestures)

Fix the rotation vector sensor (this should finally make orientation work in Cyamogenmod)

As suggested, I'm looking into AOSP CAF/ marshmallow to see if I can get something usable out of it... We'll see
[Samsung Gear S] topcaser:
How cool is that? Thanks for that. You are genius. Let's see how the battery performs...

Sent from my Galaxy S5
[Samsung Gear S] rebel1699:
Have you had any functional issues since the June 8th update of the AW app? It looks like the update has broken wifi and call audio routing to the watch. As far as wifi, it will stick on "Automatic" for a time, then move to off and cannot be turned on. The new Android Wear app requires cloud sync to be enabled for wifi to function. But, it will not work even while that is enabled. This is the case regardless of whether bt is connected or not. AW seems to also be requiring bt to be unpaired for wifi to work. Call audio is enabled on both devices as well, but failing. Thought you might want to see if this update will require you to make some changes in future builds to adjust for these new differences. I think they might want to keep you busy :) I can not say if this issue is present if AW was installed to the watch before the app update, but it seems to be effecting fresh installs to the watch, at least for me after three different fresh installs.
[Samsung Gear S] lauerp:
You missed the part of posting questions and doubts in the Q&A post. Thank you.
[Samsung Gear S] lauerp:
adding to what risoobeon said up here: if you're coming from CM12 you must do a data wipe.

---------- Post added at 01:22 PM ---------- Previous post was at 01:21 PM ----------

adding to what risoobeon said up here: if you're coming from CM12 you

must

do a data wipe.
[Samsung Gear S] yaboo007:
Thanks for the response risoobeon. Watch has no reboot issues, and battery lasts nearly two full days.
[Samsung Gear S] DJ_Mic:
Thanks risoobeon, disabled always on and its working now.
[Samsung Gear S] :
Successful flash here.

Cm 12

Canadian Sm-r750w.

Battery does better than I expected.

Excellent work ☺️

Can't wait to see the end result
[Samsung Gear S] jhasty01:
Dude, if you guys want to know specifics you will probably have to test for yourselves.

And more importantly!!!!

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

Please post questions there!
[Samsung Gear S] biktor_gj:
Aaaaand finally!

Heart rate monitor working in Android Wear!

New build coming tomorrow with the latest sensors:

Step counter

Heart rate monitor

Tilt sensor (no gestures yet besides waking up on wrist move)

New build is based back in Gear Live, it's less battery hungry and watches scale better than Zenwatch...oh and wifi works :)

Sensors/Missing:

Barometer

Linear accelerometer/significant motion (need to learn how to implement virtual sensors)

UV sensor

Context Sensor fixes (probably a lot)

If anyone can find how to properly:

Get display state from a native library in C

Get battery state

Get current system time

Please drop me a line!
[Samsung Gear S] DQEight:
I think I speak for most of us when I say...

OMGOMGOMGOMGOMGOMGOMGOMGOMGOMG

But Seriously, thanks for the work you're putting in on making this watch greater than samsung ever considered. You are the reason I haven't ditched this thing for an Omate Truesmart + or a huawei watch/pebble.
[Samsung Gear S] computerguru:
I've been out of the loop on this thread for a while (upgraded to an LG G5 and haven't looked back at Sammy since...haha.) Still have my Gear S...so willing to help out if needed. I am by no means a fluent Android developer (I'm primarily C#, and have done some *nix C back in the day), so sorry if my comments below aren't the answers you're looking for. :)

Get display state from a native library in C

You're wanting to pull the display state from the Java side into native code, right? Unless something already exists to do this, what about creating a shim that exposes the data from the display manager via a named socket? Not the most elegant solution, but it's a thought.

Get battery state

¯\_(ツ)_/¯

Get current system time

I'm sure you're talking about somewhere at the kernel level, but just in case you're not, does gettimeofday() work?
[Samsung Gear S] biktor_gj:
Here here, grab it while it's hot:

Gear S / Android Wear Marshmallow / Sensor support / Wifi

https://mega.nz/#!lMIXWY4B!OeaWSG6odYSxxMdRpbiZ-2CAPDlvncpKif6KLY5piE0

Remember to wipe after flash!
[Samsung Gear S] delboi:
The watch faces fit now perfectly with the screen yay biktor your a boss!
[Samsung Gear S] skyred5:
Could I make a small request that you update the first thread? Pretty please?:o
[Samsung Gear S] LenAsh:
Questions MUST be posted HERE - a dedicated Q and A thread for this.

Any further questions will not be moved, they will be deleted without warning.

Thanks
[Samsung Gear S] AizenKnower:
I read twice that we should not ask any question here but it doesnt make sens to forbid it.

The topic Q&A is fine if we need help or tutorial or everything else to help the installation but herewe should be allowed to ask about the progress of the development and updates and feedback of users.

I dont understand the sens to forbid all questions. If it is just a topic to say only "good job" or other congratulations I think you should block replies and people will just clock on +1 or like or thank etc...

Please let people be interested about his work and ask feedback here because the other thread is more likely dedicated to those who have issue to install or to use.

My questions are only about the progress and update not about issue or installation.

Edit: it seeams that this thread is only Android WEAR port and not the Android AOSP that seems to be given up and since my interest is to use my 3g sim and the android WEAR port is not supporting it, I apologize for my questions.

It seems no one use CM with sim but all feedback are only about Android wear which I am not interested.

Best regards
[Samsung Gear S] Xabiman:
Hi! I've read calls not working actuality. I mean to make or receive calls using watch's audio. Is it possible using last update of Android Wear? What do you mean "calls working"? Any help with this? It's important for me to change from Tizen to AW.

Sorry if this post is not at Q&A thread, but I've used search and I've found and quote this post at this thread. Thanks for your comprehensive.
[Samsung Gear S] biktor_gj:
First of all, don't read this as I'm mad at you or anything like that, I'm just exposing my thoughts in here, and this is in no way an attack at anybody (just in case, since we're a lot non-natural English speakers here, what one tries to explain can be easily misunderstood)

About questions:

There are two threads, to separate questions to actual development stuff. See, a developer thread, in XDA, is meant for development related discussions. That means:

Patches

Code

Issues related to development environment (issues on general use go in q&a)

Instructions on building something, fixing something

Development related questions (for example, what would be the best implementation approach for X, or check if this developer here who made this has some piece of code that can work for your situation etc.)

On the other side, a Q&A thread, is meant for questions and answers, for *user* questions and answers. That is:

How do I flash this

Can I break my (whatever) if I flash this

How long does battery last

Will it work on my watch

Can you make it work on my watch

How do I go back to Tizen

What is the best watchface

When will you get me a new build (answer to this is always "When it's ready")

I flashed this without reading and now the watch bootloops

Those kind of questions should go into Q&A, because they don't add *anything* into the development thread. In fact, I stopped posting information, questions, or any other thing beside the occasional build and a photo of something new I managed to get working because it pisses me off so much to see everyone asking the same things over and over again in this thread that I don't even care anymore. And I'm pretty sure that there's something I managed to fix that will be useful for others at some point (for example, the only open source library for Samsung Sensorhub Platform not using IIO device nodes in the kernel), but you just get to a point where you don't care anymore, since whenever I post something another post appears asking the same thing over again. This attitude from some people at XDA is what makes people stop participating, and at the same time, anyone with development skills that could help won't even try to add anything because everything he/she sees is people complaining and asking questions, so why bother?

About wether this thread is dedicated to Wear / Cyanogenmod, you could have figured it out yourself if it wasn't full of repeated posts. Yes, this thread is dedicated to both of them. Due to my limited time, I'm working mostly on Android Wear, which is what needs more love to get it to a mostly functional state (last build is quite usable if you ask me), but all the changes I make to get Android Wear better fall back into the Cyanogenmod device source code you can find in my github account (https://github.com/Biktorgj), so when I post a new build of CM12.1, it will go with all the fixes I've done to all of it, hopefully this will make it run better too :)
[Samsung Gear S] AizenKnower:
Yes I understood and I am new and I have read all the posts but again it was unclear but now if I understood this one is for devs and other one for user (maybe put a bold warning in the front page).

I will discuss there on Q&A. (If I found an evidence it is only for devs and mostly AW I will not bothered you. And also People are not clear if they use CM or AW here or on Q&A but anyway. Got it and dont worry I appreciate your work and thank for github.
[Samsung Gear S] wyldphyr3:
I got some Bugs in the current version (GearS_Sprat_Marshmallow_20160622). Not sure if they are caused by my unusual way of flashing as posted inQ&A or if those are general bugs.

Sometimes the watch goes into recovery instead of normal booting at restart. After pressing reboot in TWRP and choosing "System" it boots normal. (likely a flashing bug on my side)

In about 80% of connection attempts to the phone made by apps they fail, seems random as the same app may work on the next attempt. I tested it with Ingress, Spotify, DB Navigator (booking app for german railway).

The watch did not synchronize the time intially. I had to turn off time sync and turn it back on, to get it displaying the correct time.

Tilt gesture seems unreliable, but I think that's a hardware problem, as it was the same behaviour using Tizen and it's still better than no gestures.

With the new sensors (I guess GPS?) the compass app is available but calibration is impossible and the compass won't work (not sure if this should already work)

However for my purpose this last update was great. I really like the watchface scaling and as I'm a bioinformatician I really love seeing the heart rate sensor working.
[Samsung Gear S] t2bacdp:
For the 1st bug : boot normaly, in TWRP choose reboot. When CM or Android wear logo appear, force reboot by long press power Burton. When rebooting appear, choose reboot system. Next reboot should be normal.
[Samsung Gear S] DQEight:
I'm not really seeing a difference maybe it's the faces I use...
[Samsung Gear S] rebel1699:
It does not require a bold warning on the front page. This thread is clearly marked as [DEV] and the other as [Q&A]. You must pay attention to the thread titles and their description. Always check the title on Xda threads, as it will help you with forum navigation.

As for yesterdays build, it is a huge improvement. A few watchfaces still would not scale correctly. But, if you uninstall and reinstall them, it seems to fix itself. No clue why. Instaweather works to perfection. Wifi and gps working out of the box.

Issues: Occasionally, vibration turns itself on for no apparent reason and will persist. To shut it off, hold power for about 2 seconds. This has happened once while already booted, and even survives a reboot. Most of the time, it happens during a reboot, and persists the entire boot. It cannot be stopped until fully booted (with 2 second power hold). I am thinking it may be triggered by a missed call notification. I will test that theory in a bit to see if I can reproduce. Compass is indeed not calibrating, but that is expected with the current state of the sensors, so no complaints here.

Edit: Missed call is not able to reproduce the constant vibration issue.

Again, great job [MENTION=803006]biktor_gj[/MENTION]
[Samsung Gear S] risoobeon:
I would agree with all reports so far and thank you all for your precise feedback. I would also like to mention (I may be missing something) battery is reduced for me on this build I believe mainly due to screen waking every time I lift my arm I also can't seem to turn off waking gesture.
[Samsung Gear S] biktor_gj:
You can turn off tilt to wake from Android Wear app in your phone, by going into your watch settings, and deselecting tilt to wake (or whatever is called in your settings, it's the option under screen always on)
[Samsung Gear S] biktor_gj:
You can disable that by going into Android Wear app on your phone, going into watch settings and disabling tilt to wake (or whatever is called in your language, it's the second option)

You might get slightly less battery life since parts of the modem are booted in this build (a man needs to do his tests ;))
[Samsung Gear S] risoobeon:
Agreed!! And really np at all I'm sure I speak for everyone here no build is a bad build all moving in the right direction! ! Anything we can do to help you on this quest ?
[Samsung Gear S] parasetam0l:
Hello [MENTION=803006]biktor_gj[/MENTION]

Do you think of sharing your kitchen (build environment) ? I want to play with source code and burn my gear s :) Or I will try to build mine on a free time.

BTW thanks for your work.
[Samsung Gear S] primod808:
Just a battery usage update on my usage on the latest AW update. I get about a solid 9 hours of usage with all sensors/location/tilt enable. From fully charged at 9am and dead at 645pm.. Not bad at all!
[Samsung Gear S] :
I've been working on getting Bluetooth audio for calls on CM12

Still no luck

I Still have other things that I want to try

I believe this theory is correct posted by [MENTION=554771]biktor[/MENTION] gi

Correct acdb ids for bluetooth are 21 and 22 (rx and tx),I have them on my audio platform info file and they seem to get correctly parsed, though audio stays muted. It seems like the internal amp switch connecting the lineout from modem doesn't link to AUX_PCM, so audio gets routed but there's no input on the other side

I'm still kind of new working in this area

If anyone else with skills want to jump in with ideas fill free

Maybe we start a bounty for this issue and get all hands on deck?
[Samsung Gear S] :
Trying different test and internet calling apps

Calling through the internet with no cell signal Bluetooth audio still gets muted

I did noticed when calling through the internet with Hangout when I hang up the call I can hear through the Bluetooth as the Gear S unmute the Bluetooth headset I can hear calls on the other side

I may be wrong but I don't think the modem handles the calls for internet calling
[Samsung Gear S] ItzShadowz:
I don't know if this has already been answered, but that normally happens because you have 'screen always on' turned on. Exact same thing happened to me until I turned it off. If it's happening and you have it turned off already then it must be an issue in the most recent build.
[Samsung Gear S] risoobeon:
No issues (other than already known) with current build! And battery had improved since turning off WiFi! All in all a very stable daily use build thanks ?
[Samsung Gear S] LenAsh:
I warned you...

http://xdaforums.com/showpost.php?p=67445557&postcount=1371
[Samsung Gear S] andrew.mackew:
[MENTION=803006]biktor_gj[/MENTION]

Hey bro, I was searching along the thread but I didn't find so far.. so here is my request.. Could you please share your local_manifests.xml file and any eventual trick to build CM?

Thanks bro!
[Samsung Gear S] biktor_gj:
Better have a separate post....

New build!

Build Type: Mostly stable, don't bother using screen always on as it will only consume more battery and eventually leave the display in powerdown forcing you to restart. You can leave it on while setting it up though, and once you're in the homescreen, disable the setting for now.

Build Number: MWD48B

Android Wear Version: 1.5.0.2884951

Google Play Services: 9.2.56

Android Patch Level: May 1st, 2016

Considerations: Modem is booted along with the watch, and the QMI interface is active. This time around Samsung disabled all the settings, so you won't see the "Network settings" option, and nothing about telephony will work, so modem is unusable, but I'm leaving it in a stable state by letting it boot and communicate with QMUX, hopefully that'll make integrated GPS work, and it won't be draining the battery trying to communicate all the time (we'll see).

Always ON screen: This will drain your battery, since it's colliding with suspend function for the frame buffer. This is a work in progress, and, as such, is only half way through. If you disable the feature it will suspend as normal, so battery won't take a hit just because it is available

Palm down to suspend is working, put your hand over the screen to shut it down

For the rest, more or less as before, HRM working, Accel & Gyro working, pressure half way through, light sensor non functional (I think this is a build limitation)

If anyone finds how to stop Google Fit from checking your heart beat every half an hour without blocking access to it via permissions, please let me know.

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

As usual, flash with Odin. If you were running the june 22 build before, there's no need to wipe, if you weren't, wipe data before/after flash

EDIT: Updated first post