Modified kernel image to use 4 cores on Android Wear 2.0

[JMS74]

So?
Try a different USB port and plugging and unplugging until the permission dialog shows up on your watch.

If it worked with another devices it means it's not the port.
Any way tried with all the ports and it's the same

Enviado do meu A0001 através de Tapatalk

 

[shirioko]

If it worked with another devices it means it's not the port.
Any way tried with all the ports and it's the same

Enviado do meu A0001 através de Tapatalk

Try
Settings -> Developer options -> Revoke debugging authorizations
and then plug it back in

 

[JMS74]

Try
Settings -> Developer options -> Revoke debugging authorizations
and then plug it back in

Already tried that a dozen times, doesn't work

Enviado do meu A0001 através de Tapatalk

 

[JMS74]

Tried on a windows 10 laptop that has Android Studioo installed and it worked, the permissions options open just upon connecting on the watch.
Thanks for your help.

 

[[email protected]]

Will try.

HI, I had the same issue (watch shuts down as soon as i disconnect it from the cradle) so what I do is: go to settings/ apps/system apps/charging mode and erase all data and disable, when I remove mi watch from the cradle, it did not turn off, after 30 minutes working, re-enable the app (charging mode) it seems work.......... hopefully

 

[maartenw8]

I did not have those issues... Perheps try to flash stock AW, and try it again.. Using the 4 core version. No bugs, great performance and pretty gppd battery life. After a full day of always on screen and higher usage, the battery is still 48% charged.

Good job and thank you so much, OP!

 

[ldti]

HI, I had the same issue (watch shuts down as soon as i disconnect it from the cradle) so what I do is: go to settings/ apps/system apps/charging mode and erase all data and disable, when I remove mi watch from the cradle, it did not turn off, after 30 minutes working, re-enable the app (charging mode) it seems work.......... hopefully

tried it. same behavior, unfortunately. it's like something is wrong with the kernel..

 

[bongersj]

Reflashed to Android 5.02 and 6.01. Disconnected from cradle and device died! It will slowly turn into a slightly bigger problem

 

[ldti]

Will try.

Still the same..

 

[bongersj]

Still the same..

As I have this issue now in all ROMs it can't have anything to do with system settings . I went back to AW 1.5 and device was not running without cradle. Updated to AW 2.0 (Stock) with same result. I entered bootloader to drain battery down for a few hours without cradle. Then I charged it again to 100 percent and its running without cradle again, but with stock boot.img. I tried to start x-core boot image without flashing and device powered down again. Calibration lost and I have to start from scratch again.

 

[majekqwert]

It will work on Wacth Urbane (W150) ?

 

[ldti]

Will try.

As I have this issue now in all ROMs it can't have anything to do with system settings . I went back to AW 1.5 and device was not running without cradle. Updated to AW 2.0 (Stock) with same result. I entered bootloader to drain battery down for a few hours without cradle. Then I charged it again to 100 percent and its running without cradle again, but with stock boot.img. I tried to start x-core boot image without flashing and device powered down again. Calibration lost and I have to start from scratch again.

So something is definitely wrong with the modded kernel..

 

[ranf]

I cant set any permissions to ADB on connecting it to a computer.
I turn ADB on on the dev settings and when connecting to my linux laptop the adb devices detects the watch but it shows "no permissions" and doesnt allow me to do any commands like "adb reboot bootloader".
I noticed that the key permission dialog box that sets adb permissions to a device never showed up, its supposed to appear on the phone when connecting the watch to the laptop using the craddle isnt it?
Any help? please...

Create an udev rule and reboot or use

sudo adb devices -l

https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
you need different idVendor and idProduct (see the output of lsusb)

 

[pablotiss]

It will work on Wacth Urbane (W150) ?

No, but there are some others in XDA for Urbane

 

[reaktor TuT]

Thanks a ton for this boot Image! I'm using the 2 core version and watch is running like a dream. AW2. 0 was a bit sluggish. Now it's running better than AW1. 5 as far as smoothness.

I'll give it a good battery test over the next few days and report back.

FYI, unlocking watch and flashing boot Image was done on Windows 10 laptop.

 

[Ambious]

Running great for me, thank you!

 

[adlx.xda]

I cant set any permissions to ADB on connecting it to a computer.
I turn ADB on on the dev settings and when connecting to my linux laptop the adb devices detects the watch but it shows "no permissions" and doesnt allow me to do any commands like "adb reboot bootloader".
I noticed that the key permission dialog box that sets adb permissions to a device never showed up, its supposed to appear on the phone when connecting the watch to the laptop using the craddle isnt it?
Any help? please...

If Linux, try running adb as root to see if it could be a user permission problem on your Linux side.

Enviado desde mi A0001 mediante Tapatalk

 

[maartenw8]

4 core version is a bit too battery-draining for me.. Starting the day at 100% and ending at around 38%.. I'll try the 2 core version tomorrow to see the performance difference!

 

[therock11]

I unlocked, flashed it to boot, and then locked and did start and I got a weird circle boot animation. It then appeared to reboot and begin with the normal boot image again. Is this all correct?

 

[drewcu]

New to flashing...

Can someone please tell me how long this process should take? ADB just says "Downloading..." and never seems to finish (let it go all night, and then tried again and let it go 33 minutes). (My bootloader is unlocked, ADB seems to be able to execute other commands through my computer to the watch, but for the record I do have a 3rd party charger.)

fastboot boot bootdual.img

Thanks!