yashsingh1/xdaforums huggingface dataset:
[Sony Smartwatch 3] Mikegrmn:
So, I held off adding off topic stuff to the main thread for AW2.0 on Sony SW3.

I bought my SW3 maybe a month ago, because even after 2-3 years, it still looked as if it were the best option compared to my beloved Pebbles.

My Pebble time steel got replaced in the middle of last year when its battery died (actually, the battery got hot to a degree that I would probably have gotten burns from it). Once I saw a post of someone in the Pebble forums who had worn his time steel while sleeping and who got a big huge burn blister on his arm, I stopped wearing mine and was looking for a new watch.

Long story short (I could go on if you want to read it though....):

I looked into the Vector watches, but they were bought by Fitbit, too, so I´ve checked Android wear once again. I had a Moto 1. Gen once, but the battery didn´t even keep up for one work day.

With Sony SW3 being at about 2 days battery life, I decided on it, knowing that it may not get AW2.0.

I don´t regret buying it, even if AW2.0 doesn´t make it on my watch for whatever reason.

I just wondered if anyone followed up on older watches running AW2.0 previews and who can shed some light what it could mean for battery life.

I´d be ok if my watch battery doesn´t last as long as it does now (almost 3 days), but I would want 2 days at least. This gives me a nice time frame with enough left over power so that I don´t have to worry that the watch could die before day´s end.

I want my watch to show the time first (and I love the reflective always on display) and my notifications. The rest for me is nice to have, but I don´t need it. The "little" Google watch seems nice, but at 240mAh, first reviews indicate that it won´t be better than my first Moto 1.

And a watch needs to be a watch. Means for me that I don´t want to make calls on it and that it needs to be way smaller than a brick.
[Sony Smartwatch 3] matejdro:
Thanks, that is really good idea, other thread was really getting derailed every 5 minutes. I hope mods will declutter that thread and move all offending posts here.

According to reddit, last 2.0 developer previews did not cause any significant battery duration changes compared to 1.x versions. But on the other hand, both LG watches (only watches that run final 2.0 at the moment), experience wildly inconsistent battery life (some say it is very good, some say it really sucks).

Regarding warranties, you can still lock back the bootloader in the end and hope that they don't notice you tinkered with it. I'm not sure whether there even is permanent switch that shows bootloader has ever been unlocked, so I think everyone will be fine. The alternative is being stuck with an old dead OS, so IMO benefits outweigh warranty. Plus quality control on Sonys seem to be pretty good (There are usually a lot of posts about people complaining that their watch/phone/laptop/whatever has broken, but I have not seen any for SW3), so there is less chance you will need warranty.
[Sony Smartwatch 3] Mikegrmn:
Yup, like I had posted before. I want the new firmware, but don´t care about warranty too much (unless the watch would break within a couple of months). Before smartwatches, I bought a new watch about every 1-2 years anyways. In terms of price, I think they were around 120 bucks in average. So not really as expensive as a smartwatch. I like having options and when I feel the watch gets old or I want to have something new, I usually go for it. Same with my glasses which usually run around 500-1000 every 2 years, depending on the frame I choose. But glasses alone (without the frame) usually cost about 300-400. I don´t spend too much on other stuff (dining, clothes, cars), so getting some gadgets every now and then doesn´t break the bank. But it´s a matter of what´s important to you. Electronic stores today try to sell additional insurances, but I actually had never a gadget break on its own ;)

If it broke, it was usually my fault and mostly I handle my toys carefully.

So back to the battery. If the watch lasts 2-3 days like it does now, I´m more than happy and I still think it´s the best compromise in terms of size, features and battery. Pebble was great as long as it lasted, but I couldn´t read the display with my glasses off.

For that I used the ttmm watchfaces, and I made a similar one on Facer, and I can read SW3 with this watchface better when I wake up at night as compared to the smaller size screen on Pebble.

Uuuh. I have to keep my posts shorter :) But then again, this is why I made this thread, right?
[Sony Smartwatch 3] Mikegrmn:
Haha, now I was really confused. A mod must have moved comments from the dev thread to here, but the posts are right on top of everything else. If any mod is reading this, is it possible that posts that were moved are at least below the initial thread post, so that people know what this thread is about? Thanks.
[Sony Smartwatch 3] gurningchimp:
It'll be the timestamps of the posts that cause this issue, your thread was created as a reaction to the off topic posts so when they're moved it screwed it up :D
[Sony Smartwatch 3] Mikegrmn:
Duh. That´s bad.

Well well. Then I guess that it is like it is :(
[Sony Smartwatch 3] PDesire:
Okay I've told once about the TA partition thingy and I found some things out

At first:

It knows which firmware you flashed when, so they also get if you reflashed your FW to another version

Again every TA is unique as every SmartWatch and uses a SerialKey (same of your device)

Then the really bad thing: It knows when you unlocked the bootloader and that detailed

And idk if it's result of UB but the most of the TA partition is just written full of FF and 00 so no real DRM keys

Your PDesire
[Sony Smartwatch 3] alvid98:
Then the warranty is fully void if we unlock the bootloader
[Sony Smartwatch 3] Mikegrmn:
If a community rom would support stuff like custom roms on phones? Especially like functions that usually don´t come in regular stock roms. I think of something like automating flight and screen mode based on time of day.

With the 2-3 day battery, I like using my watch as my first alarm clock to wake me gently before my real alarm clock goes off, so I´m wearing it during the night, but I don´t need the screen on or notifications during the night. And it preserves battery.

E.g. on my phone, I love using the volume rocker to skip music while the screen is off. Or maybe adjust vibration settings. Stock just isn´t strong enough, so I use a separate app to have the watch shake 3 times instead of only once. But this only works for phone app notifications.
[Sony Smartwatch 3] Taxodium:
Functionality with iPhone

I would like to use my sw3 as a run tracker paired with an iPhone. There currently doesn't seem to be a way to use the GPS when paired with an iPhone. It looks like there will be some increased functionality for iOS users in aw2 but does anyone know of a way to load a running app like Runkeeper to sw3 with aw 1.x? Thanks in advance.
[Sony Smartwatch 3] sayak-brm:
You can install the app from ADB.

Sent using Tapatalk
[Sony Smartwatch 3] Dndcruz:
Mod Edit; Off -topic comment removed

---------- Post added at 06:28 PM ---------- Previous post was at 06:16 PM ----------

I have a question about theatre mode , whenever I enable it , the screen goes off for a few seconds and comes back to an always on display mode , but rest is same , unless I press the side button it won't wake up ....

Is this regular or is it a bug ? :confused:
[Sony Smartwatch 3] starsky135:
Mod Edit: Off topic comment removed

---------- Post added at 06:28 PM ---------- Previous post was at 06:16 PM ----------

I have a question about theatre mode , whenever I enable it , the screen goes off for a few seconds and comes back to an always on display mode , but rest is same , unless I press the side button it won't wake up ....

Is this regular or is it a bug ? :confused:[/QUOTE]

This has always been the case as far as I know.
[Sony Smartwatch 3] Az Biker:
* * * Thread Cleaned * * *

Apparently several users have not read, or have forgotten the Xda Rules for posting in the forum.

This thread is for comments, announcement, and news about the Smartwatch 3 / Android Wear 2.0... NOT whether users agree with Xda rules, or with Moderator actions, or how users think Xda should be operated.

If users in any thread continually violate the rules, requiring multiple Moderator visits in within a few days time, that thread may be closed until users figure out how to post without violating the rules.

The rules are created and enforced for a reason: Xda is a development forum, NOT a social media forum.

Please have another go at the rules, and follow them when posting in Xda.

Thanks for your cooperation.
[Sony Smartwatch 3] lekofraggle:
You could look into tasker or similar apps. The problem is, those apps may use more battery power than leaving the watch as normal. However, they should be able to control the settings for you. You may need root to do so as well.
[Sony Smartwatch 3] Charmandrigo:
The git is what must be constantly updated if it is gonna be a community project. But [MENTION=6126659]PDesire[/MENTION] hasn't said a thing since he was told about the reason of why it doesn't boot...

Also no one has said if there was info gotten about the other 2 ports that were achieved successfully

But I think the possible reason is the fact that Qualcomm releases their sources and this watch doesn't use a Snapdragon processor
[Sony Smartwatch 3] RJASSI21:
Guys dont forget [MENTION=6126659]PDesire[/MENTION] is working on more projects that just this one and he does have to maintain other ones aswell alongside making this port. I understand its great he is making a port for us but you do have to remeber a single guy cannot maintain all his projects and create a port which is why its taking him longer and more time. I couldnt care less when he releases it as long as I know the port is still on going. The longer it takes the more stable it will be and less issues will occur. I am aware that Pdesire works in a team also but im not hearing anything from the team, just Pdesire. Thats why I believe on he is maintaining this thread. Time will serve and we will get a port it isn't impossible since its been done for other devices we just have to wait and have patience. It could be worse with nothing for a port for the sw3 so just be greatful were getting one. It is considered rude to ask for etas on xda but I wouldnt consider asking the progress of the port rude since we only want to know how close the port is to releasing. Pdesire already said its 99% done it just wont boot so im sure the issue cannot be something that we can all collaborate and solve. Im just trying to give you all more hope in the port and hopefully you will enjoy it when it releases. Ive already lost hope for Sony and Google but not pdesire and his port.
[Sony Smartwatch 3] nawashi:
Personally I shall remain hopefully optimistic, this is being worked on and released without cost to us. As such please remember that our words carry as much weight as our financial contributions... Pdesire owes us nothing, so let's not make this project more trouble than it's worth.

I will be providing as much support as I can, and am hereby volunteering my sw3 for alpha and beta testing.

Lets make some stone soup!
[Sony Smartwatch 3] ry755:
Me too! But, even if the port doesn't end up working, we still have a perfectly working smartwatch.
[Sony Smartwatch 3] blast1987:
Let's Just wait and see guys. Porting usually take time.. and pdesire said he had some sources that cant share atm probably because it's proprietary code
[Sony Smartwatch 3] metahex12:
I will try to help to PDesire for fixing problems. I synced all source code and now my computer is compiling the source code (also i am fixing build problems etc.)
[Sony Smartwatch 3] drakonizer:
The source is outdated. The build will not boot, even if you got access to the clockwork sources. PDesire has to update some ramdisk changes to GitHub to get the build to boot to the bootanimation at least.

Trust me, I've tried.
[Sony Smartwatch 3] metahex12:
I found the clockwork sources. I am trying to fix build errors now.
[Sony Smartwatch 3] drakonizer:
You can use my repos from GitHub. Forked from PDesire's source and renamed to follow conventions. It builds fine, but does not boot.
[Sony Smartwatch 3] metahex12:
My build finished. I changed some SELinux policies. I hope it will boot
[Sony Smartwatch 3] metahex12:
With my build, it got bootloop between sony and smartwatch logo. (There is no bootanim) Sorry guys.
[Sony Smartwatch 3] drakonizer:
Told ya.

Try using the ramdisk stuff from stock M. According to PDesire that got him to the bootanim (the pic he showed), but when I tried it it didn't help. Maybe you'll have success. It worked with the boot.img he used. Unfortunately, it wasn't eng so no adb for me to debug. Plus without the ability to build a working boot.img from source, there's no bug squashing.

The issue is obviously with init.
[Sony Smartwatch 3] metahex12:
I just flashed system.img now (kernel is stock 6.0 and recovery is twrp) It got bootloop at bootanim. How can i get logs in this situation? [MENTION=5258151]drakonizer[/MENTION]
[Sony Smartwatch 3] metahex12:
Deleted

---------- Post added at 01:28 AM ---------- Previous post was at 12:56 AM ----------

I flashed a terrible boot.img. Now i can't flash anything from fastboot. When i write something at my linux terminal fastboot does not respond. I don't know why.
[Sony Smartwatch 3] Charmandrigo:
Doesn't this watch have a recovery mode?
[Sony Smartwatch 3] metahex12:
I totally bricked it. I am downloading Windows 7 for fix this (with sony companion)
[Sony Smartwatch 3] ry755:
Does it at least still have the bootloader on it? If not, then I think it may be bricked for good.
[Sony Smartwatch 3] metahex12:
I fixed my bricked SW3.
[Sony Smartwatch 3] EHKing:
Sorry, i have just arrived.

First of all, thank you for your work.

When do you think we could we have wear 2.0 working on SW3?

Thank you
[Sony Smartwatch 3] Supercharlie25:
Greatest thing you can say when you have just arrived to a topic.
[Sony Smartwatch 3] EHKing:
Sorry ?
[Sony Smartwatch 3] Supercharlie25:
Don't worry, it's ok ??
[Sony Smartwatch 3] CompuTechnoPro™:
Has this project been abondoned ? Been silent for a while. Still have hopes high.. [MENTION=6126659]PDesire[/MENTION]
[Sony Smartwatch 3] PDesire:
I would tell if it is abadoned, and no it is still running

Your PDesire
[Sony Smartwatch 3] CompuTechnoPro™:
That's good news. I don't mean to ask for ETA but, how's the project going?
[Sony Smartwatch 3] RJASSI21:
Pretty good as said previously. I dont think the progress has changed since. Its 99% done according to pdesire and it will only boot as far as the boot animation since thats as far successful pdesire has been, unfortunately, which is both good and bad since its practically done but not completely. Surely time will tell, its a great project that nobody can wait to be completed. Im sure it'll be done before the end of the year at least or before the next version of Android Wear surely.
[Sony Smartwatch 3] -Ric-:
Hum... How exactly would it even be possible to know that it's "99%" done if it won't even boot? That makes no sense. Actually the fact it won't even boot kinda points in the other direction lol...
[Sony Smartwatch 3] RJASSI21:
It does boot but only as far as the animation im just going by what pdesire said a few pages back he gave us a percentage like 90 or 99. It does boot, just not all the way I think it was said to be something with either the kernel or selinux but then people said it might not be selinux. Im not 100% sure you just need to read back a few pages thats all. Im just going off memory. It was a while back all this was said on multiple pages. I said 99% because its built just not booting thats all and because of what was previously stated. It's only that 1% needed which is to boot it. According to pdesire its built, created and done just a booting issue. It did only get to the Sony logo to begin with then pdesire somehow got it to the boot animation and since then thats the latest I know on the progress. Only pdesire could tell you more but im certain thats where the progress has halted.
[Sony Smartwatch 3] -Ric-:
I understand your point and I know you're just saying what was written in the topic before. I just personally don't believe that information, not even close.
[Sony Smartwatch 3] RJASSI21:
Oh OK well its only the information provided by the one who started the port so whether you wanna go of that is up to you but id doubt hed lie and im sure he would know more since he made the port.
[Sony Smartwatch 3] CompuTechnoPro™:
Lets just leave it to [MENTION=6126659]PDesire[/MENTION] guys..
[Sony Smartwatch 3] Mikegrmn:
Well, just thought about putting a sarcastic comment here, but I think I don´t.

I wonder why I kept checking this thread for the last couple of months (well, maybe because I had started the thread for all the posts that cluttered the dev thread. It may look like someone else started this thread, but this is because posts from the dev thread got moved here dating back longer ago than my first post).

And from my last post, it looks that our pDesire seems the hero of so many here, so that adding any doubt about this port getting done is being attacked.

Well, I think this´ll be my last post here and I "un-favorite" the thread from my bookmarks. If the watch ever gets an update, I will know from the main android outlets on the web. It´ll surely get reported.

Ah, btw. Even if the port makes it to 99% of booting, as long as it doesn´t finish to 100%, it´s no good for any one. He should start sharing so that this really becomes what XDA-developers once was all about. Just my 2 cents.

And now roast me if you need to. Seems a lot of people here need that. I´ll stay cool and won´t answer.
[Sony Smartwatch 3] drakonizer:
I agree with you. It does not sound like a community project if the source code is outdated and not updated.

Also, I don't believe it is 99% complete just because it reached the boot animation. It would be true if all that were left to solve were SELinux denials, but it doesn't boot on permissive either.

Obviously the issue is something bigger, and unfortunately the source code needs to be updated in order for me or anyone else to take a look.

I understand that the dev has a lot of projects to work on and might not have the time to do this. But a simple git push doesn't take much time, in my opinion. Also, now that we're on the topic of my opinions, a placeholder thread and all these posts were quite unnecessary and just gave people hope.
[Sony Smartwatch 3] Mysterion1:
I totally agree with you.

PDesire has been posting about his great and almost finished port since (wait for it) - FEBRUARY! He received hundreds of likes without any considerable results and it goes on...

He also claimed to be able to build Android O for this watch and made plans to call the rom DesireWear (which is the name of an american clothing brand btw xD) but he didn't build a working rom so far.

Some repos from totally unknown sources and a bootanimation which could basically be the one from AW 1.5 are no real proofs for anything (my opinion).

How could a 17 y/o guy even get some top secret sources from google nobody else was able to get access to? And why didn't he gave the community the possibility to work with him together?

I personally don't believe this port will ever be released. And I also would not start a hype for something, when I don't know if it will work or not.
[Sony Smartwatch 3] drakonizer:
I can verify that the port gets to the bootanimation. However, getting there is the trick. I used a boot.img provided by PDesire, and managed to reach the bootanimation with a system.img I built myself. However, debugging is impossible as I can't build a boot.img from source.

As for the clockwork sources, anyone can get their hands on them, if they know where to look ;)

But your overall point still stands. The naming of the ROM was a bit premature and the hype was unwarranted.
[Sony Smartwatch 3] Mikegrmn:
Thanks for the positive comments. I wrote that I wouldn´t answer, but then again, I thought that all fanboys chime in, telling my how great the project goes.

So thanks again. There still seems to be some sense of community after all.
[Sony Smartwatch 3] -Ric-:
I would just like to clarify that I do NOT believe that he lied or wanted to fool anyone. At all. I just think he severely underestimated the task. It happens, we're all humans after all.
[Sony Smartwatch 3] RJASSI21:
Of course not. Im not sure what pdesire is doing as of now, but it seems people are becoming very inpatient. Nobody seems to be happy to know we have a boot animation and pdesire has the power to easily pull the plug on the port. Either someone else can take over and try obtain the sources from Google or its wait wait wait... In your own time pdesire, we can all wait abit longer right? Maybe not for some? What are we to do now though? Our only bet for aw2.0 on the sw3 is pdesire and his what I would now agree to be only a half complete project, if that. Honestly I do appreciate the effort put into this. Pdesire you also said many weeks ago that you were going to update project meli and nothings been said on that? My guess is he's either abandoned/dropped all projects, keeping quiet for something top secret to amaze us or he's just trolling us. I doubt that last one. Hope is slowly fading pdesire. How much longer before time will tell? Guys also do not forget pdesire does all this without the acceptance of donations too for his own fun and will. I still have hope because im only really after the play store feature. What more can be said? Either wait or do it yourself somehow if you cant wait. Thats all I can think of. Good luck with the port pdesire I hope you can manage to finish it before the new year.
[Sony Smartwatch 3] metahex12:
I can confirm that the ROM is in bootloop. PDesire is not telling lie. But in my opinion "fixed 99% is not true" (At bootanimation) I think boot.img (ramdisk or kernel) is causing error at background. But we cannot see the log. Because debugging is not activating. I can't work on source anymore. I am a student and i have university exam this year. (Like SAT in USA) I have to study for it. I hope PDesire or someone will manage to port it successfully.