yashsingh1/xdaforums huggingface dataset:
[LG G Watch] jrk190:
Fwiw I highly recommend looking at the zenwatch 2's webwear Rom to see how they got square display working.
[LG G Watch] ab123321:
...

I have already set square screen + settings crash was fixed itself. I think, port will be ready in a week (max 2)
[LG G Watch] jrk190:
Awesome, better at ETA's than Asus and moto
[LG G Watch] Jacobwitt:
Awesome!

I've been watching this thread for some time so I'd be happy to see this pan out in a good direction!
[LG G Watch] Nowhite:
Please make a video rewiev of android wear 2.0 on Lg G Watch
[LG G Watch] magicstick5:
Keep in mind this is a dev thread, any requests or ETA's questions should be separate
[LG G Watch] J0SH1X:
[MENTION=7534963]ab123321[/MENTION] any idea ? i cant decompile lenok-OEMSetup.apk

https://hastebin.com/itihopukeg.sql
[LG G Watch] ab123321:
OK, system fully works (I hope so)

Now I will rebase dory kernel on lenok/bass sources (to improve performance and support LZ4-compressed SquashFS for faster boot) and adjust ramdisk
[LG G Watch] Bwangster12:
When the time comes.... how will we flash this to our watch? Like the other ROMs I've seen, with a windows script? I'm totally stock, unrooted, never done anything on a watch.
[LG G Watch] konradit:
Depends on how the developer shares the ROM, on phones, most ROMs give you a flashable zip, this means you download a file, go to your recovery that supports flashing, then you wipe the OS and install the zip file and boot again. You can also use fastboot commands or adb sideload (google does this)
[LG G Watch] Bwangster12:
Oh, I'm rather UP on how to root, flash, etc on a phone... just have never done anything to my watch. I saw in another older ROM thread that the dev was saying not to flash what he was providing and you just needed to execute the script on a Windows PC. Wasn't sure if I needed to do some unlock bootloader, root, install TWRP type of process before I transfer the file to my watch and flash.
[LG G Watch] ubcjack:
A little off topic but ab123321 can you share how google assistant works on wear 2.0 port?

Is it faster than google now on wear 1.0. It is the main reason I'd like to try 2.0 if it can be faster and better in voice recogniztion.
[LG G Watch] RAAFAYS:
Google assistant is far faster than google now on android wear 2.0 at recognising voice and i assume that the only way of activating google assistant on the lg g watch would be through the complication that is natively there on all wear 2.0 devices to trigger the assistant as a shortcut.
[LG G Watch] jrk190:
There is also hotword detection. I recommend investing in wear launcher.
[LG G Watch] Vicioxis:
Oh, but what about saying ok Google? Is it not used for Google Assistant?
[LG G Watch] RAAFAYS:
It is but it's not recognised 100% of the time
[LG G Watch] darkassain:
hi

ive been looking at and have been trying to see how most of patching worked (well done on that part)

what i have seen is that make.sh script uses

zipalign -fpt 4 infile outfile

when zipaligning, but i have yet to see a zipalign binary or source that has the -t parameter (including building from aosp source)

any chance you could share it?

still having somewhat trouble getting the parameters right for the kernel+ramdisk (boots back to fastboot using the repo kernel and ramdisk) but that might be something on my end.
[LG G Watch] ab123321:
I use zipalign from Ubuntu APT repo. -t parameter zeroes out timestamps on files

Kernel repo on GH is fully identical to which I use locally (at least for now, I'm thinking about just adding LZ4 support to Squashfs like lenok/bass do on an, or rebasing entire kernel on lenok/bass sources). Ramdisk on Github doesn't include empty folder because of some git feature. I took stock boot.img and injected kernel & ramdisk using bootimg tool from multirom / lazyflasher
[LG G Watch] darkassain:
huh manpage in the ubuntu website doesnt list -t

http://manpages.ubuntu.com/manpages/zesty/man1/zipalign.1.html

-c Check alignment only (does not modify file)

-f Overwrite existing outfile.zip

-p Page align stored shared object files

-v Verbose output

-z Recompress using Zopfli

its not a big deal, thanks for letting me know about the timestamp stuff, ziptime does it too so ill go with that

ahh ok so its 100% on my side then (been using abootimg since it gives me a nice cfg file that has all the info, also does both packing and unpacking), thanks for the answer

EDIT: found that abootimg gave me files that wouldnt boot at all (even stock repacked images wouldnt) AIK actually booted to loading screen so at least i got something :D

also realized that the file_contexts.bin in the ramdisk repo is missing

/data/misc/batteryd(/.*)?	u:object_r:batteryd_data_file:s0

whereas the lenok2dory repo's file_context has it
[LG G Watch] J0SH1X:
No matter what I do kernel always stuck at LG screen no matter how I create it with lazykernelflasher with Mkboot with aik I just give up and wait the ages till in far future Rom once comes out
[LG G Watch] Bembee:
I also tried it, I get the bootanimation, but 1 sec later it's rebooting always (bootloop). (stock G Watch R system)

So yes I also waiting [MENTION=7534963]ab123321[/MENTION]'s boot file :fingers-crossed:
[LG G Watch] J0SH1X:
Maybe we can team up I have the patched system image but no kernel give me your kernel and I will report what happens

Gesendet von meinem LG-H815 mit Tapatalk

---------- Post added at 11:24 AM ---------- Previous post was at 11:21 AM ----------

I don't know why my message wasn't send 8 have the patched system image maybe I can try your boot.img and see what happens?

Gesendet von meinem LG-H815 mit Tapatalk
[LG G Watch] GtrCraft:
My try, stuck at LG screen. That means or kernel or blobs aren't working
[LG G Watch] J0SH1X:
Indeed same here we have to convince dev to give us the boot.img and it's kernel stock kernel give me bootlogo loop

Gesendet von meinem LG-H815 mit Tapatalk

---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------

Edit I mean it goes past LG logo

Gesendet von meinem LG-H815 mit Tapatalk
[LG G Watch] ab123321:
Oh, right, I forgot to push one commit to kernel XD (uncommited change, git push didn't work). Anyway, I will release port in 1-2 days (more specifically: when I will get to my PC). Everything works fine, but device sometimes lags
[LG G Watch] edi194:
I suppose that it can be rooted. If yes, eliminating lags'll be easy :)
[LG G Watch] GtrCraft:
Can you tell which commit?
[LG G Watch] ab123321:
https://xdaforums.com/g-watch/development/-t3624441/
[LG G Watch] J0SH1X:
PRAISE THE LORD ?????

Gesendet von meinem LG-H815 mit Tapatalk
[LG G Watch] DynamicDonkey:
WOOO Nice job guys! Get ready to make XDA front page!
[LG G Watch] Kod_kota:
Video

On youtube on the channel "Shabby Cat" came out the review of apparel for Android 2.0 on lg g watch
[LG G Watch] EpicLPer:
Awesome! My LG G Watch finally gets a use again :)
[LG G Watch] Jacobwitt:
Installed as soon as I saw, runs OK. Noticible lag for an older device but eh, it'll be worked out over time.

Good job ;)
[LG G Watch] skunk26000:
There is a new boot file to flash, watch is very fast and smoothn, can even change DPI a bit without lag after the new boot flash. ^_^

https://xdaforums.com/showpost.php?p=72785072&postcount=159
[LG G Watch] Jacobwitt:
Flashed Runs smooth as silk.

Good work who ever thought to turn on Core #1 ;)
[LG G Watch] eeljas:
I got a problem with the ROM, my watches battery died while using the ROM on it. And now it behaves wierdly, whenever I put it on its dock to turn it on, it shows the charging picture, for a long time, and then starts booting up, but always fails to boot up and then again the charging picture and so on. I tried to turn it on via the little button but nothing happened. What should I do?
[LG G Watch] Thisisabadname:
Try to catch it when it shows the LG logo and swipe from the top right to the bottom left. At the bootloader, go to recovery mode. Tap the screen once you see the Android to get options and clear cache. If that doesn't work, try factory reset. If all else fails, reflash the rom (although thatd be my first instinct)
[LG G Watch] motoralbi:
Installed this on my G Watch.

With only 1 core enabled it had visible lags, so I installed the quad core image with MP decision. Ran pretty well, assistant didn't take long to launch(ready in 1 second, more or less). Battery lasted me for over a day. (See screenshot below)

Now I'm testing the dual core mp decision boot image. Haven't seen much performance decrease from the quad core one so far. Probably this is the most balanced choice, I'll see how battery goes in the next few days.

Inviato dal mio LG-D855 utilizzando Tapatalk
[LG G Watch] kokesh:
Can you link the quad core image please? Can't find it anywhere.
[LG G Watch] motoralbi:
https://r.tapatalk.com/shareLink?ur...hare_fid=3793&share_type=t&share_pid=72886013

Inviato dal mio LG-D855 utilizzando Tapatalk
[LG G Watch] brostar2017:
i think ive done it the issue was trwp it would boot-loop with trwp but seems to install without it perfectly fine, im now not stuck in a boot-loop and waiting for first initial boot up. one question if it boots up how do i activate gestures??
[LG G Watch] MihaiSG:
Here:

https://xdaforums.com/showpost.php?p=72886013&postcount=260
[LG G Watch] Alexandgut:
I have TWRP installed and everything is booting fine. Once everything boots up, go to settings and enable the wrist gestures. Hope it all works out for you.
[LG G Watch] brostar2017:
A large percentage of users can't get it to work via twrp us included the only way it would work without a bootloop was not to use trwp and to use fastboot format commands. Other users came up with he fix on this page
[LG G Watch] Alexandgut:
I've been reading that on the thread. I used the fastboot commands to make it work, but I've used TWRP for resets since. I actually couldn't get it to work (no bootloops) until I flashed TWRP! Whatever the solution, I'm glad we can get this to work to extend the life of our G Watch.
[LG G Watch] MrContar1997:
So I've been looking at this and waiting for a few months until it gets stably enough, are there any functions that can't be used on this yet due to lack of buttons? I like the idea of wear 2.0 but if the battery life is bad and it lags and a lack of buttons hinders it then I think I'll wait
[LG G Watch] unseemlycoder:
Is it possible to build the ROM with a newer security update? :confused:

I noticed we are running on security patch of May 2017.
[LG G Watch] brostar2017:
Will the watch get wear oreo which is confirmed or wear 2.8 which is out now.
[LG G Watch] unseemlycoder:
I can confirm that Wear 2.8 is out for our watch. I am on it right now, on the lenok2dory android wear 2.0 ROM.

As far as getting Oreo for the watch is concerned, our port is based on the image from the LG G watch R. Since it didn't get the Oreo update, we may not see a custom wear ROM based on Oreo for our device.

Cheers.
[LG G Watch] hanschke:
do you got it now?
[LG G Watch] warwagon19792:
Apparently, the "ok google" hot word is slowing down wear 2.0 devices. Try disabling ok google on the watch, then booting into recovery and wiping dalvik and cache. Tried it on mine and at least at the moment it definitely seems faster. I'm also using the Bubble wear launcher which allows you to double tap the watch face to activate the google assistant.
[LG G Watch] brostar2017:
How did you get wear 2.8 I'm wear 2.1 and using the latest uploaded ROM on this thread.
[LG G Watch] warwagon19792:
In the Play store on the watch / Essentials for Wear OS / Wear OS by Google Smart.. The last one you will get is 2.16. After that you need a firmware update to get the latest version of Wear OS which this watch will not get.
[LG G Watch] brostar2017:
Finally got the brand new wear os app update wish the watch today and totally shocked an app update can completely change the U.I but loving the brand new look lg g watch, so much more functional swiping from each side for a new functionality and loving the Google feed pane. Finally new life to the watch.
[LG G Watch] hanschke:
I dont think we will get a newer port because of the silence here :rolleyes:
[LG G Watch] ericdabbs:
Are people still using this watch? I have sock drawered this watch. I am gonna be looking for a new smartwatch when more smartwatches come with the Snapdragon 3100 chip.
[LG G Watch] sjrmac:
I'll take yours lol :)
[LG G Watch] hanschke:
yes my dad use it and I too.
[LG G Watch] ShadowEO:
I still have mine, but it's relegated to AsteroidOS and Windows 10 use (through WinSteroid). That said, I have a roommate that's using the 2.0 rom on her OG G watch, and loves it.
[LG G Watch] bemolx:
I'm getting my stuff ready for this today. Gonna see what I can get with it.

Sent from Nexus 5
[LG G Watch] DespairFactor:
Sorry, I have been busy, will take a look now.
[LG G Watch] drewmrk8:
If this will actually be successful, that would be amazing!
[LG G Watch] ericdabbs:
I am not familiar with Android Wear autonomy for developers but how much leeway does Google give in allowing devs to develop open ROMs for the Wear devices?
[LG G Watch] konradit:
Android Wear is closed source and I tried to unpack the LG G Watch MM system.img with no success, the N emulator system image did parse with EXT4 Unpacker...
[LG G Watch] konradit:
[MENTION=5169465]DespairFactor[/MENTION] [MENTION=5543422]bemolx[/MENTION] any success with G Watch MM System.img ? It looks like until Google open sources Android wear our watch will be on 1.4...
[LG G Watch] DespairFactor:
Haven't had time still, I am working a lot, I worked 60 hours this week.
[LG G Watch] konradit:
Wow, 12 hours a day! You need some rest man.
[LG G Watch] DespairFactor:
I try to manage my dev work on my days off, but it isn't very easy, it usually takes away from the time allocated for social events of some sort.
[LG G Watch] hanschke:
Extractor_v2.4 from XDA dont work? It can extract CM for example.
[LG G Watch] konradit:
Party hard then! If you have time, could you explain to the n00bs here how would you port an emulator image to the G Watch? I will try then
[LG G Watch] konradit:
[MENTION=453210]hanschke[/MENTION] [MENTION=5543422]bemolx[/MENTION] [MENTION=5169465]DespairFactor[/MENTION]

I think the problem is my system.img from MM, its only 256 MBs compared with the 1.75 GBs of the Emulator N system.img, here is a log of what I did, https://gist.github.com/KonradIT/e2372ac3d74e671a3e98e8d3ecb93676

The last command is what I did to get the system.img of the G Watch running N, if you read the txt entirely you will see what I did. Can anyone point me out how to get the system.img? Then I guess is just moving files around and editing .props

I also did dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/systemimage.img which gave me a similar file to /dev/block/mmcblk0p19

EDIT: seems like the EXT4 extractor and Exktractor 2.4 from XDA cannot read SQUASHFS filesystem, which is what the system uses

EDIT 2: Well, I used 7Zip to extract the MM System Image from the G Watch!!! It works and now I got the extracted images fro MM G Watch and N Emulator, also I have unsquash and mksquash to build a fastbootable system.img later on. What do I do next?
[LG G Watch] DespairFactor:
You will need to try and compare files across the images to see what is different and what is the same, I would have grabbed the huawei image to compare vs the emulator vs the g watch MM
[LG G Watch] LittleJakub:
First off, I want to thank all the developers for putting even the smallest amount of their time into this! :good:

I won't hide the fact, that it would be FANTASTIC to see Android Wear 2.0 on our oldies! :D

Keep up the good work my friends! And once more, thank you sooo much! :)
[LG G Watch] ruben46_:
Thanks for your hard work. Shame on LG if they stop g watch support. I don't see improvements enough to buy a new wearable, our watch is full usable.

Enviado desde mi LG-D855 mediante Tapatalk
[LG G Watch] ericdabbs:
I don't see myself paying for a new smartwatch until some more significant improvements are made to Android Wear. It seems like the use of a "button" is the future of Android Wear (which I was confused why Google did not make it mandatory for all OEMs to add a hardware button from the very beginning) so I will not want to buy any future smartwatch without additional hardware buttons.
[LG G Watch] drewmrk8:
Not to be pushy or anything, but any update on this? I'm just curious. :)
[LG G Watch] TheLoonyRebel:
No offense but read the thread a bit before asking for ETAs (which is a no no around here).
[LG G Watch] hanschke:
thats right that asking is not a good idea but I think he wants to know if it is possible or they see that we cannot port it.
[LG G Watch] ericdabbs:
That is what i am wondering too. If it is possible to port android wear 2.0 and function when there is no hardware button available on the watch. I am glad that google decided to make hardware buttons mandatory on smartwatches because i thought it was always silly without one.

If it is not able to be ported...then im fine with it since i got it on BF 2 years ago on the cheap. Ill probably wait a few more years before getting a new smartwatch with better battery life and maybe full cell phone capability with LTE like the lg urbane watch 2.
[LG G Watch] hanschke:
I dont want to buy a new watch with small changes. If I will buy I need more space instead of 4 gb and a better battery life.
[LG G Watch] Spartaner25:
I repacked the huwawei preview image for the g watch and made a new boot with the huawei ramdisk and the dory kernel & cmd options.

No bootscreen, neither any tombstones.

Does anyone know how to boot directly to the recovery without going over fastboot to save a last_kmsg?

Otherwise it will be pretty much trial and error :/ .

Btw. the combined bootimg boots the 6.0 Wear Image fine, so I guess that the problems with booting the n variant are in the system img.

Trying the emulator now, maybe it's a resolution issue.

Emulator is not working any better, the binaries are bigger too, so I deleted a few things, but no luck.

Anyhow, I played around with the ramdisks to enable ADB (Thanks for the hint [MENTION=803006]biktor_gj[/MENTION]) and got something on the logcat:

- exec '/system/bin/sh' failed: Permission denied (13) -

It's something, even though I hoped to preserve any permissions.
[LG G Watch] biktor_gj:
Boot animation won't show up until all your video libraries are working. Usually that permission denied you're getting is because it hasn't mounted the system partition (that or SELinux messing with you).

When you get that message run adb reboot recovery and check in last_kmsg for things related to fstab. Chances are it's looking for another fstab file or there is something not working there...
[LG G Watch] Spartaner25:
I recreated the bootimg with

--cmdline 'androidboot.hardware=dory user_debug=31 maxcpus=4 msm_rtb.filter=0x3F pm_levels.sleep_disabled=1 console=null androidboot.console=null androidboot.selinux=disabled'

and had the same result

So it is unlikely that this is a SELinux related problem.

I rebooted with the image and ran

adb wait-for-device reboot recovery

which worked, except there is no /proc/last_kmsg .

A bit of background to the files:

The Images was downloaded from here (The Huawei One).

I "desparsed" the system, mounted the image,sudo rsync -av ed it into one folder, change the build.prop Huawei Watch appearances to the LG gwatch dorys one, replaced vendor/ and lib/hw with the dorys and resquashed the image.

The bootimage is created from the dory kernel, the huawei ramdisk but with dorys default.prop, fstab, uevent and init rc .

Edit: The Reason for the non existing last_kmsg could be the the result of not having the

CONFIG_ANDROID_RAM_CONSOLE=y

and other things in the defconfig. So I "just" need to rebuild the kernel...

Edit2: I seem to be mistaken, there is no more Ram_console anywhere to be found, is seems to be merged with pstore

the important settings is here

Edit3: But I don't get any "ramoops" at reboot and don't know, how to enable them.
[LG G Watch] biktor_gj:
Sorry! My bad, I forgot it's a 3.10 kernel, check /sys/fs/pstore for logs, they might be in there

I had lots of of problems with the init binary from wear N while trying to make it boot on the gear S, I ended up using previous release's init just as a way around it (haven't been able to fully boot it yet though)

To back up system partitions, I tend to do a 'cp -rfpv SOURCE TARGET' more than using rsync. If unsure, check /system/bin/ if permissions arent't correctly propagated to the copy (depending on the target file system it could be another reason for the perm error) if they aren't, a simple 'chmod 755 /system/bin/*' on the target disk will do

Keep in mind when you get it to boot, your watch will think it's round and will render everything as a circle :) side effect of using round watch's system partition...

To ease a bit your development you might want to make your system partition as ext4, so you can play with the image live from your watch, but that can come later ;)
[LG G Watch] Spartaner25:
If I did not expressed that enough, I am very grateful for your input biktor_gj!

Sadly this directory seems pretty empty.

I looked around the kernel directory, and rebuilding the kernel would be no problem, but there is no helpful option to enable in sight.

Same Result

- exec '/system/bin/sh' failed: Permission denied (13) -

.

The Thing is, I could boot the MM System with the dory kernel and the Huawei Watch Ramdisk (everything unchanged, even the fstab). I do not feel like this should have worked...

The permissions should match (on the left the mounted ext4 image, on the right the rsynced one and the cped on, the later with the _cp appendix).

There should be no problem with the squashing itself, since I verified that it works with the MM Image.
[LG G Watch] biktor_gj:
Mmm next idea: set selinux to permissive and rebuild the kernel, and if you have some available space on the ramdisk, copy 'sh' to /system/bin but in the ramdisk file system. If it's not mounting it, you'll at least have a shell to examine all the things :)
[LG G Watch] Spartaner25:
I am not quite sure what you are meaning with that, I could disable SElinux completely while building, or disable it via cmdline (which I already do).

That sounds like something I like to do :D .

I have roughly 7Mb left on the ramdisk, so there is plenty of space.

But If I do so, I get the same result, which baffled me. I tried to unpack, copy and repack everything as sudo, to avoid any permission problems, but no luck.

I'm starting to think that I do something very basic very wrong, even though everything works fine on MM.

But there was one success, since I have so much space I pasted all the binaries from system/bin into the ramdisk, which resulted in a black screen, but suddenly there where 4 Partitions from the watch mounted.

From the top: /data /system /recovery? /?

I included the log from the recovery partition(Which looks like a pretty regular twrp log btw.).

But they are mounted as usb devices and no adb device is detected.
[LG G Watch] mnupea:
confirmed, LG won't update the G Watch to Wear 2.0 https://twitter.com/LGUSAMobile/status/735246368609083392
[LG G Watch] reepje123:
You are a bit too late, look on page 2. And btw, konradit was also the one who asked on twitter.

Apart from that, I appreciate that you guys are trying hard to get the N preview running on our G Watch!
[LG G Watch] biktor_gj:
Two things that could aslo be... When you copy the init scripts to the ramdisk... Do you keep the permissions in place? If you don't, init will refuse to use them.

Just in case, chmod 755 *.rc & chown them back to root

Also, while you're at it, I would take a minute and force init to load your rc no matter what. Open init.core.rc or init.rc and replace "import $(hardware).rc" or something like that for your initrc (I guess it will be init.dory.rc?)

Oh, check also permissions for the default.prop, if you set

ro.secure=0

persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=adb

Maybe something went south with permissions after and it's bypassing it entirely...
[LG G Watch] CedArctic:
Thrilled to see you guys working on this! Best of luck :D