yashsingh1/xdaforums huggingface dataset:
[LG G Watch] helix512:
I wish I could help with the project but I have no coding experience at all. So I'll just wait till you great guys get a port that s can follow and put on G Watch W100
[LG G Watch] konradit:
[MENTION=803006]biktor_gj[/MENTION] [MENTION=1104826]Spartaner25[/MENTION] I'd say we wait until fall for Google to release the Android Wear 2.0 update to the ZenWatch 2, its got similar HW to the G Watch and [MENTION=554771]biktor[/MENTION]_qj ported the ZW2 Android Wear 1.4 to Samsung Gear S so it can be doable, using previews is kind of useless right now.
[LG G Watch] Spartaner25:
So today I tried a fresh start, deleted some stuff and recreated the scripts and played a bit with the original MM.

I extract the ramdisk and unpack it.

owner and group is set to me (spartaner), and additionally i chmod -x 'ed the init binary, the init.rc, the init.dory.rc and the zygote32.rc.

Repacked everything with mkbootfs, made a bootimg with mkbootimg.py and tried to boot it.

And it did with all the correct permissions, so I guess mkbootfs does this for me.

Now to the more interesting stuff.

The sturgeon(=Huawei Watch) ramdisk does not work with MM, it just reboots and starts with the original ramdisk (I always use fastboot boot boot.img).

The sturgeon ramdisk with the dory scripts (fstab.dory, init.dory.rc and ueventd.dory.rc) does not work either.

And that could be, because the dory ramdisk with the sturgeon init binary (and I replaced only the binary) does not work too. It tries to boot, and restarts to recovery. No last_kmsg, nothing in /sys/fs/pstore and no tombstone though.

And a quick test with the init binary from here shows that even the sturgeons MM binary does not work for the dory.

Maybe I'm better off working with the LGE Watch Urbane 2nd Edition (nemo).

Edit: The Nemo M Ramdisk from here with the dory scripts is booting.

I recreated a systemimage based on the nemo, but no success.

Booting with the regular MM Bootimage yields the no permission error, with the a modified nemo image I get nothing.

But there is one thing, which I dismissed earlier. While booting up the N image, the system does create a folder structure in /data, which means, that there is some sort of file system access.
[LG G Watch] DespairFactor:
Remember there are proprietary blobs, they are not in the ramdisk, they are part of the system, they will not be the same as the other watch, you will need to dump them out of the g watch MM image and repack the system image from nemo with those blobs.
[LG G Watch] konradit:
What partitions are needed for the dump? I can extract them now
[LG G Watch] konradit:
Remembe that the LG G Watch Urbane 2 LTE has 3G/4G and WiFi, so maybe framework-res/systemui/settings need to be edited to rip off all of that.
[LG G Watch] DespairFactor:
I am not sure where they are stored onm the device
[LG G Watch] Spartaner25:
Don't worry, I dump everything I change, but thanks for the help :D .

The blobs you probably mean are under lib/hw/ and vendor/ on the system partition, but in this case it's not my greatest concern, since the watches share the same board platform (Snapdragon 400 on MSM8226). But we should replace them sooner or later.

I tried to replace them in the sturgeon image, but I had no luck, maybe it's working better with the memo image.

And that the LG G Watch Urbane 2 LTE should have a few extra settings is completely correct, but until we get the base system running (e.g. Graphics'n Stuff) we do not need to worry about that.
[LG G Watch] DespairFactor:
That is actually false, the blobs are for all the sensors and additional hardware for the device too, if they are incorrect or not complete it can prevent boot
[LG G Watch] Seraph08:
i might be in to help with this i just gotta find the time to really look into it.
[LG G Watch] Spartaner25:
To avoid any confusion about what I am doing, and to make it easier to work together, I packed my workflow into a few shell scripts.

I tried to follow as much recommendations as possible, but if you have a good idea, I would love to see a merge request (You can sign in with your github account btw.).

And before someone asks, no, the watch is as dead as it was before.

https://gitlab.com/Spartaner25/dory_scripts

Edit:I tried to boot the MM images from the nemo, and it did not work. So there is either something deeply wrong with the whole setup, or the nemo is also not the right donor choice and we have to wait till a square watch gets Android N.
[LG G Watch] psychoTR2:
I wanna thank you guys for your work on porting Wear 2! These watches are still good, and I think its a shame that LG doesn't see fit to support them. The G Watch is the first of only, what, 4 watches from LG? Correct me if I'm wrong, but it can't be THAT hard to maintain, can it? Maybe it's the lack of a hardware button...

Anywho, I wish I could help, but I don't have any coding knowledge (your conversation might as well be in Esperanto to me!). I'll test anything you guys push out, though! I'll keep a close eye on this thread. Thanks again!
[LG G Watch] GeminiPete:
What about flashing the Urbane with Urbane 2 AndWear Dev Prev 2.0?

Anyone tried that? I was using AW 2.0 on my Huawei as m daily driver but got a bit frustrated with the batter life, lack of voice commands and that ultra annoying hardware back button (I REALLY hope google reconsiders that supremely tedious and idiotic change, the back swipe is so much faster and non-intrusive, it just works!).

Anyway, since both are LG, both round, should be easier? And if nyone hasnt tried it, would i run the risk lf bricking my Urbane if i tried it or would it just mean flashing the stock Urbane 1.4 ROM back to it or would the boot loader possibly get overwritten (yeah, sorry, total noob here but have the imagination and desire to try out interesting experiments if its not a total cluster guaranteed to fry my beloved but speakerless Urbane!).
[LG G Watch] colliflower1107:
You are talking about the Urbane, this is the original G Watch forum, the square one.
[LG G Watch] GeminiPete:
Yes, you are correct and im fully aware of that. Since it seems porting from round Urbane 2 to the square G was proving quite difficult, my question was if anyone had tried porting AW 2.0 from the round Urbane2 to the round original Urbane, as it would seem theoretically much easier to do. I could find no thread for it, so thought this would be an okay pace to ask, as they are all LG Watches and such a thread woud attract those interested or possibly experienced with such. Did I break some rule by daring to enquire about a watch model not specifucally referenced in the thread title? I admit the strictness of such things surprises me. Regardless of any posting faux pas, i still am curious about The original Urbanes ability to run 2.0 - should i start a completely new thread for such a question or is it okay to ask here?
[LG G Watch] colliflower1107:
If im honest i would post it in the Urbane forum.
[LG G Watch] jophil2412:
You should post questions related to a different device in its specific forum. On the one hand you won't likely get an answer here because you are talking to g watch owners who might not have an urbane. On the other hand it's off topic as simple as that. This thread is about porting it to the g watch and nothing else. Should there by chance be a guy who tries to port it to the urbane he won't likely be reading this topic because no one would look for it over here and instead post it in the correct forums. I hope you get it
[LG G Watch] drewmrk8:
That might be a good idea to just wait.
[LG G Watch] kokesh:
Wait for what?
[LG G Watch] konradit:
For other square watches to get N, such as ZenWatch 2, biktor_gj already ported ZenWatch 2 MM to Gear 2/Neo, so it might be possible
[LG G Watch] andreglud:
After reading this whole thread, I'm still left with one question. What's the process in completing a test build?
[LG G Watch] hanschke:
I dont think we get any build after reading all...
[LG G Watch] EpicLPer:
Is there no way to get around SquashFS? From reading so far that's at least one big problem to get AW2 running.
[LG G Watch] biktor_gj:
Getting around squashfs should be the easiest thing to do, you either recompile the kernel with squashfs support, or you dismantle the port squashfs image, extract its content and put it into an ext4 image (that's what I do with Gear Live to port it to the gear 2&S)
[LG G Watch] kokesh:
There is a guy in this forum, who made a rom without squashfs for previous Wear version.
[LG G Watch] Spartaner25:
SquashFS is not really a problem.

Sure it makes it impossible to modify the partition on the fly, but there is no problem in creating a SquashFS Image, since I verified it with the a G Watch Image itself (unpack it an resquash it worked fine).

The Problem I encountered was, that I was not able to get either the Nemo or the sturgeon image to boot, and even if, it would be pretty useless, because they are round watches. So right now, I am waiting for a Watch 2.0 release for the Zenwatch or any other square watch.

And feel free to look through my scripts, which take off a lot of boring work. Maybe some one off you got a great idea what I've been missing.
[LG G Watch] ab123321:
IMHO, the best solution for now is waiting until AW 2.0 is released. We'll be able to combine LG G Watch R ROM (some core files and kernel commits) and Asus ZenWatch/2 ROM (Square-display apps). Porting

preview

image from Urbane 2 is a waste of time
[LG G Watch] ericdabbs:
I still wonder how we would be able to account for the lack of a hardware button?
[LG G Watch] magicstick5:
Yeah, I am wondering that too. Maybe a on screen button that substitutes for that? Or use the small button on the back of the watch?

Anyways, we can't start yet because the ZenWatch 2 hasn't got 2.0
[LG G Watch] ab123321:
There IS button, but it's small and placed near charging pins. I've already made something to press it without needle or pen, but it prevents charging/PC connecting
[LG G Watch] kokesh:
NO, that is a reset pin. It is most likely low level, so you reset in any broken state of the OS. And even if it wouldn't, I see you taking your watch off your hand and pressing a toothpick in, so you can do a simple Back action in whatever activity you are doing at the moment on the watch.
[LG G Watch] EpicLPer:
No that's not a reset pin, that's an actual hardware button. When you're using Android Wear normally press it once, the watch will turn its screen off. When you hold it for a second or 2 you'll be greeted with the System Settings menu. Only when you hold it in for longer then you'll reset the watch.
[LG G Watch] KevinX8:
Yes it's more than likely the equivalent of a power button on the watch seeing as most phones force reboot if you hold their power button for 10 seconds.
[LG G Watch] ab123321:
Believe me, it's possible to press it without taking watch off (using some likeness of button, as I've done). Yes, it's not a worthy replacement for real button, but it works.
[LG G Watch] EpicLPer:
We won't need it that often anyways, all it does is to either Lock the watch it to do something that's unimportant anyways.

So most of the time it's not used anyways, besides a little paper ball or something Stück into that hole and fixed with Tape should hold too lol
[LG G Watch] ab123321:
Yeah, porting N from LG G Watch R should be easy. I'm comparing latest system dumps from both watches now. Main magic is in framework-res.apk: there are some different overlays for each device. For example, bool config_windowIsRound determines UI shape (false for squre-watches, true for round-watches). The only barrier, maybe, will be some propietary libs, unique for most models, firmware and bootloader. Google has tradition to update BL with every big update, wich will be Android N.
[LG G Watch] Bwangster12:
Doesn't 2.0 have you pressing a hardware button to go "back." How are we supposed to do that using the reset button on the back? Walking around with a paperclip? lol
[LG G Watch] EpicLPer:
Paperclip? 2 Cents

New watch? 250 Bucks.

Inconvenience? Priceless!

;P
[LG G Watch] Bwangster12:
Honestly, whipping out a paperclip in order to poke the little button on the underside of the watch is not ideal for me.
[LG G Watch] magicstick5:
Yeah I'm sure we can use the gesture to go back if we don't want to use the reset button.
[LG G Watch] Bwangster12:
Ahh, good call... forgot about that.
[LG G Watch] ab123321:
There is a gesture for doing this? o_O
[LG G Watch] Bwangster12:
Shaking your wrist cancels or goes back... once gestures are turned on.
[LG G Watch] ShadowEO:
Doesn't matter, the G Watch's hardware button is identified to the OS as the keycode for the power button. So it wouldn't really be useful as a back button anyway.
[LG G Watch] aloknm:
An onscreen floating back button would be the best option even though it might not be ideal taking up parts of the small screen.

The back gesture would be impractical cause I am sure google will release that to developers so that they can implement it in their apps.
[LG G Watch] ab123321:
lol, our screen is already small, floating button would only disturb user
[LG G Watch] magicstick5:
It's one of the only ways....
[LG G Watch] Ki870:
Hey,I just wanted to know if you will do a preiview build or will you wait until the final relase... because the zenwatch 2 has a build.. eiter way I think you should try a preview build so were not waiting 2 months after its released.
[LG G Watch] TheLoonyRebel:
Hey I see you are new around here on XDA. So let me give you a tip of advice which is don't come around here and start making demands to developers on what they should and should not do. They work very hard to share their ROMs, kernels, and mods to us. So it's very insulting that you just make a post like that telling them who are doing this for free (or donations) that they should just do this.
[LG G Watch] armada786:
Regarding the back gesture, there's always the wrist gestures for navigation. Google also said they'd be truly systemwide so I don't think they'll be removed. Even if the back gesture is neutered (a choice that still seems awful to me) there is still the back wrist gesture. So no accessible button shouldn't be a show stopper.
[LG G Watch] aloknm:
Running around with paperclips is not feasible and the back gesture might be used for something else. On screen button is the only way.
[LG G Watch] ab123321:
You can do whatever you want. But hardware button can be used without installing any apps. And, please, show me an app, that emulates power button at AW
[LG G Watch] aloknm:
iOS has this and has worked well for them. Image below

[IMG="iOs Button"]http://cdn.hightechdad.com/wp-content/uploads/2013/03/HTD-broken-iphone-softbutton-1.jpg[/IMG]
[LG G Watch] ab123321:
iOS on Android Wear? Yeah, you're right
[LG G Watch] aloknm:
I am not saying its a perfect comparison but just that it works. Obviously the button is going to be a lot smaller in our case.
[LG G Watch] khaytsus:
Hardware button? You mean the reset button? Nonsense, that cannot be used as a regular button.

Anyway, if gestures could be done, over-ride the palm-sleep one for back or something, who actually uses that??
[LG G Watch] dersie:
With have this floating button also in the "Wear Mini Laucher"
[LG G Watch] aloknm:
Sorry havent used it so I didnt know.
[LG G Watch] ab123321:
Why? Actually, it's just a little power button. It's as on other watches, but smaller and uncomfortabler.
[LG G Watch] khaytsus:
You do realize that this is the back button right? Something used a LOT?
[LG G Watch] goast:
No pointing in arguing about the reset button on the back

..no one in their right mind would try to use that has a back button or walk around with a freaking paperclip.... This is one of the stupidest things to be arguing or discussing about on here... There is no point in all this hypothetical talk... Let's wait until 2.0 comes out then worry about how we are going to resolve the issue
[LG G Watch] googleygoggles:
Wellp... I guess this thread is gonna on hold for a bit until Wear 2.0 is fully released. Anyways, in regards to what should we do about the back button problem, im guessing we are gonna have to find some sort of replacement, and considering that, a software button would most likely be bad idea with the small screen estate.

Should the OP setup a poll to vote later on or would that be a bad idea?
[LG G Watch] hanschke:
if the beta will come it will be nice too ;)
[LG G Watch] ShadowEO:
They were trying, but from what I've read here, they were unable to get it to boot. So our main chance is waiting for the ZenWatch (2?) version to drop since it's made for square watches.
[LG G Watch] ab123321:
We should wait for LG G Watch R release
[LG G Watch] J0SH1X:
i was busy with LG G3 Android 7 since its out for some days im in for a new project, so after my phone and tablet are on 7 now my watch needs to be on 7 too
[LG G Watch] ab123321:
Man, final nougat for AW even haven't released. It will be released in October probably
[LG G Watch] ab123321:
Can anyone deal with sepolicy binary?
[LG G Watch] ab123321:
I've launched LG G Watch R's system (marshmallow) on my watch!

But it doesn't boot :P

Thanks to working adbd, logcat was working.

During surfaceflinger launch it attempts to load hwcomposer.msm8226.so. For unknown reason, hwcomposer tries to load libwpa_client.so (a WiFi lib) wich was removed by me (because it does not persist in G Watch'es ROM). Since I'm not going to return it back, I need some help from you, guys
[LG G Watch] Spartaner25:
You could either replace the hwcomposer lib with the one from dory, or build a stub ibwpa_client.so lib, which offers the same methods but does nothing.
[LG G Watch] ab123321:
No, both HALs load this lib. I've already solved this (lenok's libhardware_legacy.so loaded this, temporary replaced it with dory's one) and... I have bootlooped bootanimation (very big progress)! Now system doesn't boot because of improper framework-res.apk signing, now I'm going to cut sign checking algorithm from system (system will become more unsecure, but IT'S JUST A WATCH, we can allow us that dirty haxes)
[LG G Watch] ab123321:
Booted!

Current limitations:

- You'll need to do factory reset on your watch ("fastboot -w") to install port

- First boot is laggy and buggy, after reboot everything should be ok

- I've used LG G Watch kernel (because it's useless to port it from Watch R here, on marshmallow)

- libhardware_legacy.so was taken from LG G Watch ROM

- Pre-installed LG's watchfaces are round (because LG are asses)

- LG Call app crashes for unknown reason (maybe for this reason it's not available officially for our watches)

- I've forgotten, to be completed
[LG G Watch] sykomaniac:
Can I ask why you would port the marshmallow version?
[LG G Watch] magicstick5:
Great job :svetius:
[LG G Watch] ab123321:
Because if I can port marshmallow, I can port nougat too
[LG G Watch] Spartaner25:
Great Job!

What did you change to get the rom booted?

Is it still a squashfs image or did you go with ext4?
[LG G Watch] hanschke:
that sounds great!
[LG G Watch] ab123321:
I use squashfs, ext4 is too big for our watch

Here is the repo: https://github.com/ab123321/lenok2dory/
[LG G Watch] magicstick5:
Nice job. The G watch circular will will be getting nougat soon. We are almost there!:D
[LG G Watch] jrk190:
This is great! I've had the Moto 360 for a while but I'm ending up switching with my dad for his G watch because of this. Really excited!
[LG G Watch] Motawa88:
and how do you use the back option?
[LG G Watch] ab123321:
It's marshmallow, not nougat. I'm just swiping right

P.S. Fixed some very stupid derp today (WiFi has been showning in settings lol). BTW, you can track fixes and updates on my Github repo
[LG G Watch] pro_granade:
Are you currently working on porting Nougat over to the watch?
[LG G Watch] aloknm:
No, he cant port it unless it rolls out for the watch which I suspect will happen sometime after the Oct 4th Google event.
[LG G Watch] ab123321:
Yes

Also there is still no apktool with nougat support
[LG G Watch] pro_granade:
Oh, sorry. I thought Wear 2.0 was already released. I just got my watch last week.

---------- Post added at 04:42 AM ---------- Previous post was at 04:42 AM ----------

Are APKs that different? I thought the only thing changed around APKs was the new runtime, and that was changed on 5.1/6.0 with JACK compiling. APKTool (should) still work?
[LG G Watch] ab123321:
JACK is on marshmallow too. Also, Jack actually isn't compiler, it's build system.

Apktool support usually means support for new Android API
[LG G Watch] pro_granade:
Ah, alright. I've only ever managed ROMs, never really got too much into it, sorry lmao. I'd be happy to test or help out whenever the time comes.
[LG G Watch] konradit:
"Early 2017" everyone, on to waiting! :(

http://www.androidpolice.com/2016/0...3-confirms-public-release-delayed-early-2017/
[LG G Watch] jrk190:
I'm assuming the dev preview can't be ported?
[LG G Watch] hanschke:
there is a new wear apk too which is only working with the preview of 2.0 and hope we got a port!
[LG G Watch] ab123321:
It can be ported, but let's wait for final release, OK?
[LG G Watch] magicstick5:
Wear 2.0 has been delayed until 2017:(. It would be nice if someone could port dev preview 3, although waiting wouldn't be that bad....
[LG G Watch] jrk190:
I mean you'll be doing the pouring so I can wait ????

It would be nice to try the preview though, to get an idea of how navigation will feel without a physical button.
[LG G Watch] ab123321:
Maybe

I'll port nemo's system, but it has much more differences than lenok's/bass'es (LG Watch Urbane 1st actually is LG G Watch R with different watch-case and set of pre-installed apps).

Also, there is a horror with SELinux on Nougat. I don't know what I'm going to do with it. file_context.bin is now not a problem, the problem still is a sepolicy binary. Should I recreate policy from scratch or patch existing dory's/donor's binary? How I'm going to do it? Mayby it's better just to switch selinux to permissive/disabled state? There are many such questions
[LG G Watch] jrk190:
I'm pretty sure setting it to permissive will make it easier.
[LG G Watch] googleygoggles:
Most likely an unpopular opinion but... Just disable it. Screw security. It's a watch.

An OLD watch at that. What, is there gonna be a hacker willing to go through all that trouble for practically nothing?
[LG G Watch] goast:
I wholeheartedly agree... I am even running n 7.0 on my one plus one and it's permissive too... But for the everyday user being compromised isn't an issue... Stay away from porn sites and pirate app downloads and you'll be fine... Bring on the aw 2.0 lol
[LG G Watch] googleygoggles:
Neither of those are possible on a watch anyway :laugh:

Unless...

https://play.google.com/store/apps/details?id=com.appfour.wearbrowser

Dun. DUN. DUUUUNNN
[LG G Watch] kokesh:
+1 I don't care about security on my f'n watch. I can't realistically see someone trying to hack my watch from within the bluetooth range :)
[LG G Watch] magicstick5:
Same here, lol
[LG G Watch] googleygoggles:
Exactly! Especially with having to work within Bluetooth range for a stable connection for any hack to work! Its obvious that Android Wear and Bluetooth is more of a small bursts of data kind of deal since Bluetooth is slow and can drain watch battery.

So, realistically, the only way for someone to hack your watch would be with it charging close to your phone, and even then not much data can be gleaned of the watch.

So, disabling SELinux/setting it to permissive solves that problem.

I guess the biggest problem now is the missing button.

How about the palm gesture?
[LG G Watch] AceofSpades90:
Any updates on the actual port? Regardless of security I'll be down to use it.

The dev thread is pretty vacant :/ Not a good sign...
[LG G Watch] ab123321:
There is still no official AW 2.0. Only buggy Developer Preview for two watches.

I'm working on solving some Android N peculiarities now.
[LG G Watch] hanschke:
I will try the buggy preview if I got it ;)