yashsingh1/xdaforums huggingface dataset:
[Samsung Gear 2] flatherskevin:
Charged watch to about 70% at 11am and it was at 6% at 9am the next day. Screen always-on was turned on, and low bit ambient mode was turned on under wear development tools. Worked great. I also confirm that ambient mode watch faces are really difficult to see in the sunlight due to its nature of being dim to conserve battery life, but this is understandable. I hope that you guys are able to get the phone call from watch working because that is a really cool feature to have. Also, is there any way to give bluetooth tethered internet access to sideloaded apps? I know I have asked that in the past but no one really answered exactly how. I kept running into an issue where I couldn't mount the system folder because I did not have permission.
[Samsung Gear 2] annson08:
I'm afraid not. For that, use google fit instead. I know it has its draw backs but hey! Android is far better than wear in other features (I'm sure everyone would agree on that).
[Samsung Gear 2] fernandogdl:
i use an app called App2Wear to sideload apps trough bluetooth, look for it in playstore, it's free
[Samsung Gear 2] Alxoom33:
Couldn't find it in playstore. Searched. Can it go by another name.
[Samsung Gear 2] Hec1N1:
Try Apps2wear, its $1.99, not free.
[Samsung Gear 2] flatherskevin:
This does not install the applications in such a way that things like Chrome and other internet necessary applications can get connection
[Samsung Gear 2] menissalt:
Interesting, then Pandora might work, I installed it using that app and it crashed. Maybe I should just push it the normal way.
[Samsung Gear 2] biktor_gj:
Bug fix release (I hope... ;))

Things are mostly the same. I think I've fixed the birghtness while on ambient mode, and hopefully Android Wear has stopped working messages will be gone (was anyone experiencing those like me?)

Let's see if all of you who were having troubles with latest image have this working fine.

md5: def249f18214c7ca00a5bc65391d0c0f wear_511__07_22_2015.tar

Download, flash it with odin, and wait for it to come back.

LINK: http://www.mediafire.com/download/pr3vljpdecep0dd/wear_511__07_22_2015.tar

Note: Since the MTP implementation, ADB is NOT available during boot (so don't expect that).

This image has SELinux support on a filesystem level, unfortunately, the mali device node isn't on the SEPOLICY, so it doesn't show anything on screen, and I can't seem to find a way to recompile that policy, or export it and rebuild it with the missing pieces. Anyone with experience on SELinux here? It would be so easy if I had Android Wear source... Right now I've left it disabled in the kernel and everything works. Even in Permissive mode the thing would fall apart, don't know why...

Note #2: This build DOESN'T HAVE ROOT SUPPORT. Since it's not even working I didn't see the point, I will put it back when it works correctly (*fingers crossed*)

I've been looking a bit into the vibrator regulation, no matter what I changes it still vibrates like a dildo :) Will see if I can fix that up!

[MENTION=4995278]Razor29[/MENTION] check it out please!
[Samsung Gear 2] jeffc83:
Thanks [MENTION=803006]biktor_gj[/MENTION]! Flashing and testing now:) Yes, I ran into the "Android Wear Stopped Working" error but it would always be fine after pressing OK...if it means anything, all my other smartwatches do this too from time to time. (just not as often)

Regarding your dildo comment, my wife is going to be pissed at you;) LOL

New ROM booted okay, first thing I noticed is that the screen is VERY dim when in ambient mode...I cannot see it now but at least the flashing is fixed;) Thanks!
[Samsung Gear 2] biktor_gj:
I upped the lowest limit to 30nits from 10 just to avoid that low brightness, but I think there's something else that turns brightness into _really low_, probably one of the remaining low power mode commands to the LCD. It gave me one more force close but it might be for all the hard resets and crashes during testing... I've wiped data and it's resyncing right now, we'll see how it goes...

The lowest setting in brightness should be a bit brighter anyway, is it noticeable?

Wearmedia is working again?
[Samsung Gear 2] mahmoud_m_m:
1. First i would like to thank [MENTION=803006]biktor_gj[/MENTION] for the great spectacular work.

2. i am having the same issue regarding the navigation as shown in the attachment. a reboot didn't fix it. i would get a log if i knew how. any way i will start with a fresh flash in the weekend and see how it goes. i think a reboot right after the fresh install might be the answer as i installed some apps and played a bit the the watch.

3. regarding the battery life it is pretty good not as the samsungs software but a decent battery life see attachments. my settings were brightness at 4 , brightness boost off ,all notifications ,

wrist gesture on , always on screen is off and a custom watch face with weather updates. my use was decent answering calls and changing watch faces using widgets.

4. some apps the i used and they work great with the watch:

apollo wear launcher, crebrus ( great anti theft apps) paid , chronometer , wearable widgets, wear aware a cheaper anti loss app paid as well.
[Samsung Gear 2] jeffc83:
Okay thanks, I'll stand by! (I also think that's what it's doing)

Lowest setting in brightness is definitely noticeable between 1 and 2. (even 3-4-5)

Not sure about Wearmedia, haven't tried it yet. Can anyone else answer this for him?
[Samsung Gear 2] Alxoom33:
Yeah I was getting Android Wear fc messages, as well.[emoji12] [emoji12] thanks for the fix!
[Samsung Gear 2] DAGr8:
First build I flash since mtp was enabled, my watch still charges on pc but I lost adb and don't have mtp either, win7 64 bit. Not asking for help just reporting, I haven't seen anyone report anything about neither

Edit: biktor reported adb not working during boot I misinterpreted that one. Most probably reinstall Sammy driver will do the trick [MENTION=803006]biktor_gj[/MENTION] how do we logcat of no adb during boot?
[Samsung Gear 2] andrew.mackew:
I had pretty much the same problem. MTP wasn't working.. to get it working I got to go disable and re-enable ADB into developer menu.

I'm using Arch Linux, but it'll work on windows 7 too.
[Samsung Gear 2] DAGr8:
that was easy :) thx
[Samsung Gear 2] biktor_gj:
Aaaand I messed up again...

Who would have known that it's not the same to write this:

persist.sys.usb.config=mtp,adb

Or this:

persist.sys.usb.config=adb,mtp

It seems it's not my week :silly:

I've made two new boot images, one with only ADB to allow debugging on boot, and another one with both MTP and ADB enabled.

Pick your choice!

ADB Only: http://www.mediafire.com/download/cuo5fa95d5tgmv5/bootimage_ADB_ONLY.tar

MTP+ADB: http://www.mediafire.com/download/bs6rwapqcc35sc6/bootimage_MTP_AND_ADB.tar

(...flash with odin after flashing 07/22 image)
[Samsung Gear 2] mholdik:
Size

'

-O- really sunny day here...

'

The size (halfsized now) of rootfs.img little scares me. How did you get it.

Good luck
[Samsung Gear 2] emuandco:
The image was fixed size all the time. I guess now it's cropped.

EDIT: And the cam app is gone ^^
[Samsung Gear 2] mholdik:
Right... and everything works (my status). :)
[Samsung Gear 2] careingemt:
Hello

Just wanted to say great job biktor_gj ... just flashed tuesday night ( thanks Alvaro ) i am very impressed with port battery life using sleep as andriod is 20% better than i got with tizen

thanks for all the hard work

Fran


[Samsung Gear 2] biktor_gj:
I discarded all the empty space, that's why it is smaller, no need to worry :)
[Samsung Gear 2] kociubin:
Bluetooth Stops Working

First off, great work biktor! Thank you.

Bug Report: I occasionally run into an issue where bluetooth on the watch stops working and it disconnects from the phone. I have to reboot the watch to get things working again. It's easily reproducible whenever I initiate "Resync Apps" from within the Wear app on the phone. After a few minutes of resyncing apps, bluetooth dies and a watch reboot is needed.

Are others seeing this too? Or is it something with my phone (Galaxy S6)?

Below is a link to the watch logcat of the issue. Please let me know if any other logs would help.

http://pastebin.com/wHWt2Mz4
[Samsung Gear 2] biktor_gj:
Hi, bluetooth is fine according to your logcat. What dies is Google Play Services after a resync. When you resync, you force the reinstall of every app, even the google updates. It seems when it's Google's time to resync, it downloads the package fron the phone, attempts to update and everything dies when it tries to bring it online...

Are you running the 07/22 build? If you're not, please flash it and wipe data and see if it keeps happening. After I flashed that build and wiped data, play services haven't crashed again...

Hope it helps!
[Samsung Gear 2] biktor_gj:
Well... this is definitely not my best week.

With all the changes that I've done and all the git resets that I had to do on the kernel tree, I seem to have lost a very very tiny but very very important change.

One bug fixed every day to keep you guys entertained: Bluetooth atuosleep after 1second instead of 5.

http://www.mediafire.com/download/58z9co7vp881y6f/bt_1sec.tar

On the Gear Live, bluetooth low power mode is controlled by Android. On Tizen, is controlled by the kernel module, and it enters low power mode after 1 second of inactivity.

On our android kernel, Android _thinks_ it's telling the bluetooth module when to sleep, but in fact is autocontrolled by the kernel. On Android Kitkat, I had to set the sleep timer to 5 secons to mantain a stable connection. On lollipop though, the autosleep after 5 seconds makes it collide with the autosleep feature when ambient mode is enabled, and forces the watch to stay awake when the wake alarm timer is too close to the suspend timer, and this reduces the sleep time. Doesn't make any sense to you? don't worry, this will simply make it sleep more often, thus wasting a bit less energy :)

Just flash it with Odin on top of everything else. This change will be in all the following builds.

Oh, I almost forgot, a little advice:

I downgraded the android version of my phone from Android 5.1.1 to Android 5.0.1, and battery consumption on the watch while connected has more than doubled. So, for best results, if possible, stick to the latest Android version. I have no way to try with other devices, but if you have an Xperia Z, you might find this useful ;)
[Samsung Gear 2] adrock74:
Im loving this watch again. Added a velcro sports strap and riding high. Love checking this thread!

Sent from my SAMSUNG-SM-G870A
[Samsung Gear 2] andrew.mackew:
Thank you very much!

Please feel free to send us how many patches you find appropriated! :) We love updates.. you know that, we all, are a kind of flashaholics :D

By the way, any lucky with the camera?
[Samsung Gear 2] Kwbmm:
I finally found the time to flash this rom on my gear 2 neo, I used the latest update (Jul 22). I found some bugs in this first testing:

- Vibration UI is a bit confusing at least in my language: the header always says "Vibration off" regardless of the current status of the vibration. Then when vibration is OFF (bell icon with slash on it) the text below says "Activate". When vibration is ON (bell icon without slash) the text below says "Not active" (at least in my language). I think this can be easily fixed.

- At boot it always asks to "tap here to install superSU" but if I do so nothing happens, and If I swipe to the right and press Open, it crashes. The notification is not dismissable so now I just blocked the notifications from SuperSU.

- (doubt) when the watch is in low power consumption mode (screen always on) if I move it, it comes back with colors even if I disabled wrist gestures. Is that right?

- For some strange reasons, apps are displayed multiple times

- If from my watch I go into one of my contacts and choose "Send SMS" it always crashes

EDIT: Don't know if it's important, but my phone is a Galaxy S4 running Carbon Rom 4.4.4

EDIT2: Compass seems broken
[Samsung Gear 2] AuRoN89:
i confirm the multiple apps icons.
[Samsung Gear 2] kociubin:
I tried it on 07/22 build. It still disconnects while resyncing packages. But now Google Play Services restart automatically and everything reconnects. So, a reboot is no longer required.

Thanks for the help.
[Samsung Gear 2] Arry87:
I double this, tried to ask in q&a but no luck on hearing anything! Was using the rom with my neo but have upgraded to a Gear 2 (with camera) and that feature is just a deal breaker for me, although I am dying to get back to droid wear! Keep up the good work!
[Samsung Gear 2] :
That is because one of the apps are made by Samsung, and the other one is made by Google. No issue here :)
[Samsung Gear 2] alvaromartinezb:
I can also tell you, that we are future proof, android version speaking because I am running Android M and I have no issues whatsoever... And battery life doesn't seem to be affected! If you would like to run tests or something, we can try them out on my phone... I'll be glad to help!
[Samsung Gear 2] biktor_gj:
I'm holding off to that a bit while I smash the biggest bugs so I can have a clean base to work on. I think I have the base we need to make it work, but still haven't been able to solve a little dependency hell.

There's a new set of camera libraries bundled with Android Wear (I'm pretty sure next AW device _will_ have a camera), and they don't have Geolocation support. The Exynos camera library (of couse closed source) _needs_ the geolocation APIs to work, and if I replace the camera clients, the watch crashes and doesn't even boot...

I have taken all the libraries and camera app out of these builds to avoid unmet dependencies and errors while I clean everything. Once it is stable and working good I will get back to that, it's the last missing hardware feature!

So we can say still work in progress ;)
[Samsung Gear 2] Kwbmm:
But I'm not using a touchwiz based rom.. I have dumped every Samsung related app long ago.. How could that be?
[Samsung Gear 2] Hassaan Shahid:
I was having all sorts of disconnection and bluetooth issues, then i downgraded to stock kitkat 4.4 on note 3 LTE , now i face no bluetooth issues at all , currently at 17th july build of wear on gear 2 neo , will flash latest one today
[Samsung Gear 2] tihimasmo:
Plz try connecting bt hands-free and receiving phone call to hands-free by pressing answer on watch. Tell me how it went
[Samsung Gear 2] Hassaan Shahid:
I will report it in 1-2 hours . flashing latest build on gear right now
[Samsung Gear 2] zviki:
Are you serious? There is no way that some app can repair "burned-out(in) screen diodes". It can only become less visible, because you will burned-out the rest of the screen diodes. Settings in developer options is to PREVENT this effect, not to repair it.
[Samsung Gear 2] Hassaan Shahid:
1. Connected bluetooth handsfree (samsung) to phone , received calls via watch and it went to handsfree , ended call with handsfree button ..

dialed number from watch and it went to handsfree ..

2. connected bluetooth handsfree to watch . it connected without an issue . couldnt use it as i had no media on watch .

when i was on lollipop on phone (note 3 n9005) ,i was even having disconnections with tizen on gear 2 neo

for me all my blutooth connectivity issues got solved after Kitkat 4.4 downgrade on my phone

Now i wish there was a way to turnoff mic on wear which is on all the times and takes alot of battery.
[Samsung Gear 2] :
The OP used the Gear Live ROM as base, and the Gear Live comes with those apps. I have an HTC phone and those apps still show up.

MEEP
[Samsung Gear 2] mahmoud_m_m:
Guess what guys there is an app on the store that actually acts like a gallery app and music player. and the surprise is it plays directly on the watch speakers. the app name is Wear Media - music gallery . This app makes the watch even better on android wear.

[ EDIT] tested it on the watch speakers it is a bit fast tempo but when i connected my hands free to the watch it plays okay.
[Samsung Gear 2] gled:
Warning that a factory reset after having flashed 07/22, the mtp+adb boot image and that fix I had many Google Play Service and Android wear crash while the first sync was happening. It was also extremely slow and after reboot I could not see notifications sent to the watch...

I flashed back 07/22, did the factory reset, sync was an order of magnitude faster and did not experienced any crash.

*edit* I then flashed back the ADB+MTP boot image and the bt_1s fix WITHOUT resetting to factory and everything is working as expected, notifications on the watch etc...*/edit*

---------- Post added at 08:44 AM ---------- Previous post was at 08:43 AM ----------

I wish that too, never using "ok google", I'd love a way to remove it entirely, need to read about wear mods...
[Samsung Gear 2] Duck4Cover:
I am having issues after installing the latest, it keeps saying that Supersu is not installed and then it crashes.
[Samsung Gear 2] Hassaan Shahid:
Try wiping watch in recovery .

I didn't install SU . and in last 18hrs i got only 1 FC Android wear error and no Error related to SU
[Samsung Gear 2] tihimasmo:
[MENTION=2798090]gled[/MENTION]

So I still don't understand what you suggest. Wipe or not wipe?

Plz don't quote solid word blocks
[Samsung Gear 2] gled:
Wipe after installing 07/22, Before installing bt_1s fix...

Do Not wipe AFTER installing bt_1s.

That is how I got a stable build working.
[Samsung Gear 2] biktor_gj:
The bt_1second fix is just a kernel, you don't need to wipe after flashing any kernel that I might post. What makes a difference is if you're flashing a system image (a 250-500mb file), if it's just a boot image or a kernel you don't need to do anything.

Now back on topic. Camera! Did you think I forgot about you?

I don't know if it crashes because I have no camera, or if it crashes because I didn't make it work. At least these logs show up as attempting to open the correct device:

D/ExynosCameraParameters( 1330): m_antiBanding = 50hz
I/ExynosCamera( 1330): [CAM_ID(0)][]-INFO(m_companionThreadFunc[6620]):
D/ExynosCameraNode( 1330): [CAM_ID(0)][companion]-DEBUG(create[158]): Create
D/ExynosCameraNode( 1330): [CAM_ID(0)][companion]-DEBUG(open[223]): open
I/ExynosCameraParameters( 1330): INFO(getPreviewFpsRange[970]):minFpsRange=15, maxFpsRange=30
E/ExynosCameraNode( 1330): [CAM_ID(0)][companion]-ERR(open[245]):exynos_v4l2_open(/dev/video109) fail, ret(-1)
E/ExynosCamera( 1330): [CAM_ID(0)][]-ERR(m_companionThreadFunc[6637]): Companion Node open fail, ret(-38)
D/ExynosCamera( 1330): [CAM_ID(0)][]-DEBUG(m_companionThreadFunc):Companion Node(109) opened running)
E/ExynosCameraUtils( 1330): ERR(android::status_t android::getSupportedFpsList(android::String8&, int, int, int, android::ExynosSensorInfo*)):cannot find fps list
D/ExynosCamera( 1330): [CAM_ID(0)][]-DEBUG(m_companionThreadFunc):duration time( 1 msec)
I/ExynosCameraParameters( 1330): INFO(setDefaultParameter):supportedFpsList=
D/ExynosCameraParameters( 1330): DEBUG(setParameters):intelligent_mode : -1
D/ExynosCameraParameters( 1330): DEBUG(setParameters):intelligent_mode(-1) getVisionMode(0)

I'm uploading a _TEST_ image. THIS IS NOT A DAILY DRIVER. Need someone with a camera to try it for me.

EDIT: Nevermind, found another problem.... grrr....
[Samsung Gear 2] Arry87:
I have a camera watch, I'm not very savvy though if I experience any serious issues. Should I still try it? Or would I be pretty useless if I need to give feedback? Lol
[Samsung Gear 2] llsh:
Guys, i found one interesting thing.

Best battery statistics was on ROM from 5th july. It's a first ROM with audio support. Watch live with this ROM more than 2 days of quite intensive use!

I ask you check it out, please, install ROM from 5th july. It's so simple to move back to latest ROM.

I notice, that i don't use screen always on, so this is not a cause of best battery life, that ROM from 5th july doesn't support screen always on.
[Samsung Gear 2] tihimasmo:
After long last posting the logcat you asked for biktor, sorry it took time.

Scenario:

Call paired handheld from friend's phone. Using paired watch, swipe green button to engage incoming phonecall. Watch display shows phonecall successfully engaged. Paired handheld keeps ringing. Phonecall terminated from friend's phone. Logcat pulled.
[Samsung Gear 2] mahmoud_m_m:
i tried it now and it is working fine here i am on 22/7 plus adb+mtp and the latest bt 1sec. and the answer button answers perfectly.
[Samsung Gear 2] biktor_gj:
I don't know if what I'm seeing is what's happening because that logcat is really small.. If what you got there is the exact time where you swiped to accept the call, your Google services are crashing in the background when you do it. I would advise you to flash the latest version and do a full wipe and retry...

Well, it's not really a good metric... The July 5th version didn't have always screen on, so the display controller entered full suspend mode, not just low power mode like it does mode. Infrared didn't work either, so it wasn't consuming energy...

Anyway, I'm still looking to get a little more juice, and I changed a pair of things more into the kernel. I've made some little changes to bluetooth and cpu hotplug, hope it doesn't break anything!

http://www.mediafire.com/download/799sjypvbp63dtd/kernel_ts_.tar

All my tests are with screen in always on mode. Bluetooth always enabled and tilt-to-wake disabled

On a G Watch R I get about 22 hours of battery.

On the Gear 2 with previous kernel it was about 20.

I still haven't measured this changes, but I hope it's at least a bit better ;) You tell me!
[Samsung Gear 2] llsh:
I notices, that i didn't use always screen on all roms, i just tried this feature and turned it off, i don't need this feature.

Well if our watch don't go to full suspend mode EVEN if ASO is disabled in settings, i think, i would be cool to make a kernel w/o support of ASO feature (for users., that do not use this feature). But it's all up to you, Biktor. ROM from 5th of july gives really good battery time!
[Samsung Gear 2] tihimasmo:
I flashed 5/7 . I'm a screen off guy so I'll test your theory.
[Samsung Gear 2] llsh:
Thanks! Try to keep usual use cases for watch during testing
[Samsung Gear 2] gled:
73% and 1day 7h announced left... on the 07/22, adb+MTP and bt_1s...

- Wifi disabled

- Screen always on disabled

- Wrist movement disabled

- Luminosity 2, when out I sometimes use the boost

- 'Pure' watchface

Biktor_gj this is an awesome work.. I'll let it go to depletion to measure correctly and flash the new kernel to report back...
[Samsung Gear 2] AntwonJenkins:
[MENTION=803006]biktor_gj[/MENTION] Can we assume that all your new uploads have the previous little extra fixs in them?
[Samsung Gear 2] tihimasmo:
Flashing didn't help with answer on watch issue. It has been like this since I reflashed my phone rom. I must've disabled something vital in the aroma installer.
[Samsung Gear 2] Arry87:
Omg my time has finally come to go back to android wear!!! Come onnnnnn camera. Waiting to test!
[Samsung Gear 2] AntwonJenkins:
[MENTION=803006]biktor_gj[/MENTION] Since no one has posted yet, when I try to launch the camera, the screen rotates 90 degrees clockwise and that's it. Working on pulling a log for you.

EDIT:

logcat.log

dmesg.log
[Samsung Gear 2] WerWolv:
[MENTION=803006]biktor_gj[/MENTION]

Here are the logs. It didn't hard reboot but something rather interesting happend. It just closed without any message and went back to the Watch Face BUT with the wrong orientation. I could still interact with it but I didn't manage to get into the app Launcher. After I pressed the front button everything went back to normal.

I hope I did everything correct ^-^
[Samsung Gear 2] spityu85hun:
camera test image

sorry. camera not working. i tap open camera, no error message, app is quit watch screen :( i upload 2 log file

supersu install notwork, installer is crash