yashsingh1/xdaforums huggingface dataset:
[Samsung Gear 2] biktor_gj:
Stuck? sure, right now:

* fb_s3c -> if I give it the clock, it crashes, if I don't it complains that it can't get it and crashes (but it gets to do 'something' before it dies)

* smies -> if I use fb_smies it doesn't work, if I use Samsung_smies it doesn't compile

* cmdline -> half made, made a function to read bootloader's cmdline and replace it to 'android standards', to send androidboot.serialno and to be able to change rootfs to another partition to allow from normal booting to recovery (when you select recovery in s-boot it just passes a recovery argument - systemd.unit=recovery-mode.target -), it should mostly work, but unless video is resolved is worthless. Needs more work

* 3.10/3.18 directly from Tizen builds (build.tizen.org) -> I can compile it, the bootloader detects the dtb board data, revision etc, and then it doesn't boot (I'm guessing machine definition differences between what the S-boot expects and what the kernel is sending, but not looked too much at it, as it doesn't boot even when precompiled from the build system, maybe I need a newer bootloader which I don't have access to, and I'm not willing to break the water resistance to solder 4 tiny wires into the cpu's serial port and put glue inside of the watch just to know what it's doing...)

The most I have is writing garbage to the screen, nicely painted garbage, with dots and stuff, and then crash.

Abandoned? At least not yet :)

Keep in mind I'm trying this in the little spare time I have (mostly weekends), and that I'm not a skilled developer with ninja skills, I'm barely getting to know the platform I'm working with and I have no help and no documentation but the original hacked kernel source from samsung and some other kernel versions that don't even boot, so I can make no promises...
[Samsung Gear 2] Jataadroid:
Major props to you for the hard work.
[Samsung Gear 2] biktor_gj:
Yeees pleaseee ;) tell me when you have it and I'll link it in the first post!
[Samsung Gear 2] kavinzhao:
Sorry, my big fault. I checked Android Wear's build.prop and found that the line should be

ro.config.nocheckin=yes

Should be some differences between them?

Try?
[Samsung Gear 2] biktor_gj:
I tried that too but it still asked for Google Play... Anyway, we still need bluetooth just to set the time (it doesn't work using date -s from ADB) so we still need to fix that first.

I'm scared of the OpenGL thing more. If I can't get opensource hwcomposer to work or get a fully functional hwcomposer without cr*p to replace it, all the work I've done so far is useless...
[Samsung Gear 2] kavinzhao:
Set date? The date here is fine. Time's also correct. Maybe you can try setting that using TWRP? Don't know why.

And I think we can temporarily use software composer instead. Any ideas?

Edit: wait a sec.. What does "ask for Google Play" mean?
[Samsung Gear 2] biktor_gj:
Tried both running & twrp, it gets 2 hours less (probably timezone or something like that)

Hwcomposer is required for video, without it there's no display... It also handles VSync and framebuffer layers for the mali video library. So far I fixed the screen grambling on boot but I think something else is going on at the kernel level which doesnt play nice. I don't know if there's more to it though. Maybe I clean all that and the problem persists. The thing is I don't know enough of how gralloc<->hwcomposer<->mali exactly works, so if the kernel doesn't fix it, I'm not sure I'll be able to...

And the fact that the hwcomposer that works is completely hacked up by some samsung employee who seems had no time to do better than picking pieces of code from everywhere doesn't help...
[Samsung Gear 2] bitstra:
set timezone via adb shell:

adb shell setprop persist.sys.timezone "America/Chicago" (or your Country/City)

:)
[Samsung Gear 2] kavinzhao:
Biktor do you know why the screen flashes white bars when it turns on (from sleep, not when powering on (although there's a bigger one there) )? It's not a big problem but quite annoying. Perhaps we can set a screen-on delay?

---------- Post added at 23:06 ---------- Previous post was at 23:00 ----------

I see someone asking what's working and what's not. I'd like to list them so Biktor will have more free time..

**Working Devices List

Display (there's a tiny problem said in the previous post)

Touchscreen (working like a charm)

Vibration (just like the above)

Power Button( I wonder what's for home button)

USB(adb)

Bluetooth (half)
[Samsung Gear 2] biktor_gj:
The garbage on the framebuffer when starting and waking up from suspend? It annoyed me a lot too ;) it's a kernel issue on the s3c framebuffer. I have it fixed but haven't pushed to github yet. I will post the kernel update when I'm home :)

EDIT: Pick it up here: http://www.mediafire.com/download/cqc0nd29m4pw08q/kernel_s3cfb.tar
[Samsung Gear 2] jeffc83:
^^ Just flashed it in Odin....thanks, it is working perfectly! (that flashing WAS getting annoying, lol)
[Samsung Gear 2] shawn718:
Can this be downloaded...
[Samsung Gear 2] Darth Ziggurat:
Yes, there are several files spread across several post, and no normal user proof guide to flash them.

I think [MENTION=803006]biktor_gj[/MENTION] has plans to make a single flashable file with a more fleshed out guide after the gets networking over bluetooth to work, and maybe there are some other bugs he wants to tackle.
[Samsung Gear 2] kavinzhao:
Looks nice. Thanks.
[Samsung Gear 2] llsh:
Could we have any chanse to have internet over BT on Gear?
[Samsung Gear 2] sandvich123127:
Quick Fix To Bluetooth Problem

I got bluetooth to work as of now as a quick fix! What I did was that I searched for a launcher switcher after clearing my data in TWRP. The link that I used to download this was:

http://apps.evozi.com/apk-downloader/?id=kr.mobilefirst.launcherswitcher

Next, after downloading, I installed to my watch through adb :laugh:

Later, I had to use adb shell, and the code I used was:

After this, I checked my watch and it launched, notice near the bottom you can scroll, very slowly though :rolleyes: .

Now, I looked for the 2nd android thumbnail I saw and pressed the power button in the app, and VOILA, the launcher including bluetooth!!!!!!

The only downside is if you reboot, you have to do the adb shell again. And I'm not fully sure if the bluetooth can ever reconnect if disconnected :fingers-crossed:.

PS: Wait until the start screen (Just a minute) fails to connect, then proceed

PPS: DON'T RESYNC applications... it will disconnect bluetooth for the time being (like a minute), and it will go back to the setup screen which is a pain in the a**
[Samsung Gear 2] sandvich123127:
SO BEAUTIFUL, even if stock clock only works!
[Samsung Gear 2] bitstra:
Thanx! [MENTION=5752412]sandvich123127[/MENTION], please quote [MENTION=803006]biktor_gj[/MENTION] 's last post, so he will be informed about your workaround for skipping initial setup!

Edit: but the network over BT problem won't be fixed this way?
[Samsung Gear 2] biktor_gj:
Does it show as connected on the watch or it stays disconnected?

(Even if it doesn't work, that is...)

I'm trying to find the exact point there it drops the bnep connection (yes, it brings it up then kills it before attempting to use it)

Separated from the main issue, I've been playing with tizen 2.3 release. If anyone was looking into it, don't bother, it's an enormous waste. The only real improvement is the application launcher starts from down-up gesture... And that's it. The system image is filled and only contains a clock and the settings, and there's no way of backporting samsung apps.

I've been also looking at the clockwork proxy issue, and got the ota's for the gear live. I will try to update the image to the latest 4.4W2, and if possible, to lolipop... We'll see if it pays off!

By the way, pushed last changes to kernel to github

Includes more fixes to networking, backported IPC driver from sprat (still don't know if it's useless but just in case) and the bluetooth kernel module cleaned up a bit
[Samsung Gear 2] bitstra:
[MENTION=803006]biktor_gj[/MENTION], In his screenshot (watchface) there is no stroked cloud visible, so it seems to be stayed connected...

Can't test it because out of town��
[Samsung Gear 2] biktor_gj:
Well... oookay, now it does the first sync. Bluetooth keeps screaming like a little **** in the background and doesn't reconnect after the first reboot, but, hey, Google apps get updated on the first boot, so I have that going for me which is nice :cowboy:

D/rpctransport( 1168): sanitizeTarget: replaced target "othernode" with "NodeInternal{id='d125f382-336e-4d14-9c42-32317cc8120c', name='Xperia Z'}"
D/dalvikvm( 1210): GC_CONCURRENT freed 384K, 7% free 6108K/6532K, paused 40ms+10ms, total 138ms
[B]W/InitializeWearableSvc( 1210): Rebooting device after gcore upgrade.[/B]
D/ShutdownThread( 413): Notifying thread to start shutdown longPressBehavior=1
E/bt_upio ( 710): upio_set : open(/proc/bluetooth/sleep/btwrite) for write failed: No such file or directory (2)
E/bt_upio ( 710): upio_set : open(/proc/bluetooth/sleep/btwrite) for write failed: No such file or directory (2)
I/ShutdownThread( 413): Sending shutdown broadcast...
W/SyncManager( 413): Writing sync state before shutdown...

It even sends the weather and pending notifications from the phone!

Let's see if I can fix that reconnection issue and will post another image. Forget about battery or opengl though ;)

Edit: The checkin still fails, but it seems it doesn't block the watch anymore. Good enough for me :)
[Samsung Gear 2] matt54:
Baby steps my friend.

working for me too.
[Samsung Gear 2] pizza_pablo:
I've used the Beta 3 / Zenwatch 2 version, from this OP, since the day I rooted my Gear 2 Neo and it has performed well for over 2 years. It is very stable. I like it so much more than AW 2 on my Fossil Marshal.
[Samsung Gear 2] Alxoom33:
Just fyi, there is a more advanced version that's on YouTube by [MENTION=7121745]alvaromartinez[/MENTION]. You can search for my prior posts, I linked to it

Oh, found it....https://mega.nz/#!pFxSkajI!jsw...NBatPdlp70B3_5x-hWv0LFKBU1kMF4
[Samsung Gear 2] pizza_pablo:
What are the advantages, over Beta 3?

This is what I get when I follow the link...
[Samsung Gear 2] Alxoom33:
It's a newer marshmallow based wear version and is not based on Zenphone. Just works a little better.

You need to google [MENTION=4102854]alvero[/MENTION]martinez' YouTube channel posts to see if you can get an updated download link. Some of his videos are in the OP, so you can find them and look for the latest ones.
[Samsung Gear 2] armsel:
Zenwatch 2 -> I remember testing it and not liking it... will check it again...

Alxoom33 -> do you mean GNeo_AndroidWear_2016_0708:

https://mega.nz/#!pFxSkajI!jswoESwegKV4JNBatPdlp70B3_5x-hWv0LFKBU1kMF4

For me it is unstable and the battery goes down very fast...
[Samsung Gear 2] pizza_pablo:
From the OP:

When resetting watch, got into TWRP and check

DALVIK CACHE

CACHE

DATA

and wipe three times, each.

Sometimes upon startup the watch will state

UNFORTUNATELY GOOGLE PLAY SERVICES HAS STOPPED

Go back into TWRP and wipe above items one more time.
[Samsung Gear 2] armsel:
Thanks!

I did re-flash before reading your advice above (without wiping anything) and yes it gave me "UNFORTUNATELY GOOGLE PLAY SERVICES HAS STOPPED", but after restart worked fine...

I now remember what was my problem with this port - there is no way to disable touch to wake (even with Zenwatch manager) - and I don't like it - not only it is not battery friendly, but also I tend to change watch faces by accident... :)

Did you manage to find a workaround, or it doesn't bother you? (I read of changing a parameter via ODIN)

How many days you get on single charge (seems to me less battery friendly then the 5.1.1)?

"and wipe three times, each" -> are you saying this will help with the battery life?
[Samsung Gear 2] pizza_pablo:
I like TOUCH TO Wake, but it can be deselected.

Go to GEAR SETTINGS, in the app menu and it is second on the list.
[Samsung Gear 2] armsel:
If that is on the phone -> don't see it (screenshot attached).
[Samsung Gear 2] pizza_pablo:
No sir. On the watch.

APPS > GEAR SETTINGS > TOUCH WAKE to OFF
[Samsung Gear 2] armsel:
Thanks for pointing it out Pablo, but very strange (if we are on the same ROM) -> I don't have "Gear Settings" at all it on my watch, also the setting menu looks different.

I flashed Gear2_W6_Beta3 from the first page, downloaded sometime back (27 ‎March ‎2016 I believe):

Beta #3 (Zenwatch based): https://mega.nz/#!FFYjQCxR!Et4bc8QSX...cKsj5tnBNLPZog

Or there is another ROM? Or it is because I did not wipe it as advised...
[Samsung Gear 2] pizza_pablo:
How peculiar!
[Samsung Gear 2] armsel:
Very strange indeed!

What I did just now: downloaded the Gear2_W6_Beta3 again (from the first page - the link worked for me!), I wiped the watch several times as advised by you and flashed it, wiped it once again immediately after the flash and this time it didn't give the "google services has stopped..." message.

But still I don't have Gear Manager...and also now I don't have the zenwatch manager link anymore (seen in my screenshots from yesterday)...

Wonder how is this even possible?!...:eek:

I am thinking that most likely the developer was updating the build and just replacing the file without indicating the different revisions...

Any chance that you keep the version you have? If yes, would you please upload it for me on google drive or elsewhere? :)
[Samsung Gear 2] pizza_pablo:
I believe I still have all files on my laptop.

When I get home tonight, I'll look and if so, I will post them.
[Samsung Gear 2] armsel:
Thank you!

And I just saw the ZenWatch Manager is now showing on the watch... this ROM works in mysterious ways :)
[Samsung Gear 2] pizza_pablo:
It does sync apps for a day or two, but once I get it setup, it is stable.

As to the ZenWatch Manager on the watch, itself, mine states to download v3.0 onto my phone, but I already have v3.3 on the phone. Everything seems to function properly in this state.
[Samsung Gear 2] Alxoom33:
Why are you not using the most up-to-date version that was posted by [MENTION=4102854]alveromartinez[/MENTION] on You Tube?

Here is a link:

https://m.youtube.com/watch?v=bBqg72z8LOk

Download links: Odin: http://www.android.gs/download-odin-3... ROM: http://www.mediafire.com/download/bmc... Aditional ROM info: June 29th, 2015: Android Wear Lolipop - 5.1.1 (build LDZ22J)

Edit: The link may have expired, you may want to contact Alvero for an updated dl link.
[Samsung Gear 2] armsel:
Thanks Alxoom33!

I found working link: http://www.mediafire.com/file/bmcjbaikve5sob2/Gear2_Wear_Lolipop_5.1.1_06292015.tar.zip

http://www.mediafire.com/file/bmcjbaikve5sob2/Gear2_Wear_Lolipop_5.1.1_06292015.tar.zip

Still, I am skeptical if it will show the contacts properly on incoming calls.

The problem I believe is now with Wear OS (does not support older wear version I guess), but will give it a try.
[Samsung Gear 2] Alxoom33:
It works perfectly with my Pixel 2 XL and current version of Wear. I have both the Gear 2 and Nixon Mission both paired. No problems with calls and contacts showing up.
[Samsung Gear 2] Tigres2:
If you refer to the update on the android wear app, just after installing, disconnect from every possible internet connection and open the app. No message will prompt for update, and the watch will be detected. Hope this helps someone else too.
[Samsung Gear 2] ComicoX:
Can someone port Android Wear 2?
[Samsung Gear 2] kaos420:
I have my watch running with new android wear app. Works fine. When detecting check show all devices. Select your watch. Works fine.
[Samsung Gear 2] pizza_pablo:
Same, here. Neo on Beta 3
[Samsung Gear 2] armsel:
Hello Alxoom33, unfortunately this version (Gear2_Wear_Lolipop_5.1.1_06292015) didn't work for me - it is unable to sync the contacts for starters... - hence - showing only number at incoming calls... When I do to contacts on the watch - it says "Synchronizing..." but then fails - "with no contacts were found, add contacts to contact app on the phone..."
[Samsung Gear 2] armsel:
Pablo, once again may thanks for taking of your time and sharing your installation file!

I did re-flashed yet again (after I tried the Gear2_Wear_Lolipop_5.1.1_06292015) to beta 3, this time using you source files (and I now believe they are 100% identical to the one that is in the first post).

Strangely, I still don't see gear manager and the settings menu is (still) different then the one you have.

I was about to ask if also have Neo, but I got this answered already.

I have no explanation how is this possible...
[Samsung Gear 2] pizza_pablo:
My only guess at the differences is due to our regional difference.
[Samsung Gear 2] Alxoom33:
What phone and OS are you using? I am using the Google Pixel 2 XL and Android O DP2.
[Samsung Gear 2] kaos420:
Same here.
[Samsung Gear 2] pizza_pablo:
Moto Z2 Play and Pixel XL.

The Neo pairs the same with each of these phones and the same menu options were present on a Moto X Pure Edition, also.
[Samsung Gear 2] armsel:
I think the mystery is solved! :)

I believe you are on the newer - Gear2_Wear6_Rel6 from the first page:

March 4, 2016: https://mega.nz/#!QQwXQKCD!U-y82wTuB...GWtEXMZ6TPikQU

Fixes over previous builds: Text To Speech, IR Support & New Gear Kernel Settings

With this version I finally got the gear settings! Still waiting to see about the battery life - but for the few days I use it - it is very reliable!
[Samsung Gear 2] pizza_pablo:
Huh, all this time I've been thinking Beta 3.

I'll have to look at my Neo, when I get back home to see what the watch firmware version is.

I'm on travel until next Tuesday. I'll make myself a note to look and report back.
[Samsung Gear 2] kaos420:
Lol I'm definitely on beta 3 with no issues.
[Samsung Gear 2] Alxoom33:
Yes! I've been telling people for months to upgrade to the You Tube version, but everyone still uses Beta 3, which is for the Zenwatch!

Great!
[Samsung Gear 2] armsel:
Alxoom, Gear2_Wear6_Rel6 is basically Beta 3 (Zenwatch) with added gear settings and other minor changes... so far has been very stable for me and shows contact information on incoming calls.

Maybe battery life is a bit worse then 5.1.1, but I still need to observe further to see by how much...

The one that you recommended (if I have understood you correctly -> Gear2_Wear_Lolipop_5.1.1_06292015), is also not showing contact information on incoming calls.
[Samsung Gear 2] TacoNikky:
Hi guys,

Is there fastboot mode in samsung gear 2?

I would like to experience asteroid os on our watch but I am unable to use fast boot commands. Gear live and Asus Zenwatch 2 have asteroid os supports. We may port it if we have fastboot access.
[Samsung Gear 2] Alxoom33:
Not that I know of. As the watch is a Samsung, everything is done using Odin.
[Samsung Gear 2] pizza_pablo:
There are no samsung watches on the list of Asteroids supported devices, on their web site.

---------- Post added at 04:25 PM ---------- Previous post was at 03:40 PM ----------

Just checked the Neo and in SETTINGS > ABOUT > Build Number MEC23U
[Samsung Gear 2] armsel:
Yep, I got the same.
[Samsung Gear 2] Alxoom33:
Nope, the latest is: Build No. MWD48B
[Samsung Gear 2] pizza_pablo:
I wasn't looking for the latest. I was answering armsel.

I am satisfied with the function of the version my watch is running.
[Samsung Gear 2] kaos420:
Same running version MEC23U no issues
[Samsung Gear 2] armsel:
Thanks Pablo! Yes, it is very stable and all functions work, but I am disappointed by the battery life - I was able to go on 1 charge Monday morning to Thursday evening.

With this build - Wednesday morning I need to re-charge -> 18% left.

Still not bad considering that some modern watches require to be charged daily!

But since I an not using any applications that require Wear 6, I am bit disappointed that I am unable to stay on 5.1.1, although - this build (MEC23U) is even more stable then the 5.1.1 I was using so far!

I will try to find/install the build that Alxoom is talking about and compare...hopefully the battery life might be better. If not, I am staying on MEC23U. :good:

---------- Post added at 07:53 AM ---------- Previous post was at 07:00 AM ----------

Just installed... testing.:good:

Update (2 hours later) - 2 crashes so far (only 1 watch face installed). Never got any crashes on MEC23U. Battery also drops faster then 5.1.1. But let me see after it settles down a bit...
[Samsung Gear 2] pizza_pablo:
I charge the Neo, daily. Usually I have at least 40% remaining, when I hit the hay. Every once in a while, especially right after changing phones, it may be at 14%, at bed time.

I still love this watch, much more than my Fossil Marshal, on 2.0. I wish AW 2.0 never happened.

Too many drastic changes. The worst decision being to enable changing of the face with swipe left or right. Do folks really change faces that often, to warrant that function taking up two gestures?

I don't.
[Samsung Gear 2] armsel:
I guess we use them differently....

But still, 5.1.1 was much much more battery friendly then 6.

On mine I do not use always ON and touch to wake.

Even went so far to disable the microphone on 6.0 hoping this will disable "OK Google" listening and safe battery - but I saw no change at all.

I also don't see an option to turn Wi-Fi OFF on wear 6, did I missed it, or there is not such option? Not that we have Wi-Fi, but maybe causes battery drain...

As stated before I was able to get from Monday morning to Thursday evening on 5.1.1.

On Wear 6, I have to recharge Wednesday morning else it will not last through the day.
[Samsung Gear 2] pizza_pablo:
I've not seen a wifi setting.

I don't use always on display, but gestures and OK Google are on.
[Samsung Gear 2] armsel:
On 5.1.1 there was option to disable WiFi.

I am switching back to MEC23U:

Gear2_Wear6_Rel6 from the first page:

March 4, 2016: https://mega.nz/#!QQwXQKCD!U-y82wTuB...GWtEXMZ6TPikQU

On latest Build No. MWD48B - the battery life is similar to MEC23U, but MWD48B is more unstable for me.
[Samsung Gear 2] galaxy_z4:
Use Gear 2 with latest version of Android Wear app (Wear OS app)

Hey people,

First of, I'd like to thanks everyone who has worked on this project so far. I'm not an Android developer so I can't help much, but I encourage you continuing the progress of this thread.

Now, I have good news for people who hasn't been able to make things work in the past couple of months. I figured out how to

install Android Wear 6

on my Gear 2 Neo and make it work with the latest

version of Android Wear app.

This has been successfully tested with my Nexus 5X. I wish you the same luck!

Steps :

- Factory reset the watch and flash the latest version of Android Wear 6 available on this thread.

- On your Android phone : uninstall the Android Wear app (Now called Wear OS app) if you have it installed.

- Install the very first old version of Android Wear app.

- Run the app. It should find your watch. Pair the two devices.

- WARNING : This

will

take a while. Let the watch work.

- Once both your phone and the watch are paired together, update the Android Wear app to the latest version from the Google Play Store.

Voilà! Everything should be working now. All the watch's functionalities should work with the Wear OS app. I even noticed that the speakers of the watch were working now.

Let me know if this works for you people! I'll try my best to help you from here.
[Samsung Gear 2] armsel:
Hello galaxy_z4,

Yes and this is described several times in the thread.

And since I just recently tested many different ROMs, I also noticed that with the latest versions on Android Wear (6.0) there is no issue with the Wear OS application on the phone. I got this issue only with Android Wear 5.1.1

Still, it may differ from phone to phone (I am with OnePlus 3)...

No harm of repeating the solution as well... ;)