yashsingh1/xdaforums huggingface dataset:
[Samsung Gear 2] mpogr:
Are you saying your email synchronisation broke since installing my APK? That's strange, because the change I made is supposed to affect only contact synchronisation, nothing else. That said, I can't really test it, because I have a non-Samsung device, so emails don't work for me at all on the Gear.

Also, your experience confirms that the problem addressed by this fix exists for Samsung users as well. I'd like to suggest you to raise an official support request with Samsung. Maybe they'll eventually come up with a proper fix. This is something I can't do because I'm using the Gear with a non-Samsung device.
[Samsung Gear 2] dreamur:
mpogr:

I checked my log file and I am always getting this fail message during contact sync -

06-19 19:02:08.610 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.615 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.620 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.625 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.630 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.630 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.635 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.635 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.645 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.645 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.650 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

06-19 19:02:08.655 721 781 E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m
[Samsung Gear 2] mpogr:
Yep, that's the problem I had. Chances are my fix will work for you.
[Samsung Gear 2] vikramdhani:
Well seems like since I am on Samsung phone I am not able to install the apk :(
[Samsung Gear 2] dreamur:
mpogr: I have installed your apk and so far I am losing 35% after 11 hours. Not sure if that is the normal consumption for gear 2 but surely is an improvement before I applied your fix. Thanks a lot and I will continue tracking my battery.

---------- Post added at 12:45 AM ---------- Previous post was at 12:40 AM ----------

I am using Note 2 (N7100) and here's what I did (note: I'm no techie so this may sound cumbersome):

1. I saved first the apk to a local folder

2. Next click on Settings > Application Manager > click on goproviders > click Unistall

3. Open local folder and click on the saved apk from mpogr

4. Follow through installation process

5. Reboot. Did not even wipe Delvik cache as I have no idea where it is!

HTH!
[Samsung Gear 2] vikramdhani:
thanks but I am not been able to uninstall the goproviders app. there is no option to uninstalled View attachment 2807827

please advice if you can
[Samsung Gear 2] mpogr:
I use Super Manager for this sort of tasks. Look it up in Google Play store.
[Samsung Gear 2] vikramdhani:
so I have downloaded the super manager can you guide me how can I use it to delete the go providers
[Samsung Gear 2] mpogr:
In Super Manager, go to File Manager and navigate to the directory where you put my APK. Tap on it. Super Manager will think it's installed (because, from the system perspective, it's identical to the original APK), so it'll present you with "uininstall" option. Do uninstall and then, immediately, "install". Since you're standing on my APK, it will install it. If you do it quickly enough, it should work.
[Samsung Gear 2] dreamur:
Mpogr: I think your apk is preventing fitness for gear to sync with Note 2. I tried several times but the sync broke. I deleted it and let GM install its own and sync is workinf again.
[Samsung Gear 2] mpogr:
What kind of sync are you talking about? Can you elaborate what exactly broke?
[Samsung Gear 2] dreamur:
Mpogr: see below -
[Samsung Gear 2] dreamur:
Finally found a fix! I deleted my google account from the phone and reinstalled including contacts. Now the log showed no contatc sync error and battery is draining 1% per hour. Will continue to monitor battery life.

---------- Post added at 06:47 AM ---------- Previous post was at 06:44 AM ----------

Btw, I upgraded GM to xxx401 and I am not using mpogr's apk. All stock.
[Samsung Gear 2] mpogr:
Nah, sorry mate, didn't work for me. Maybe it does fix stuff on Samsung devices, but it didn't help at all on my HTC M8. I even fully reset my device (flashed a different ROM), installed Samsung stuff first and then added Google and other accounts. As soon as contacts are populated, the crazy thrashing begins.

I also updated to the latest release of Gear Manager, same issue. I already updated the new "goproviders" with my fix, will post it here later.
[Samsung Gear 2] kompis:
I installed the APK and it solved my battery problem.

Now, ear Manager is updated to version 2.1.14062401 and I have same problem again.

Would you please make the new version available. Thanks for great work.
[Samsung Gear 2] mpogr:
New approach

OK, the handler I updated in the 2 previous fixes didn't change from the previous version of "goproviders", so I hoped I could just use the same .class file, DEX it, stick into an APK, sign and be done with it. Unfortunately, it looks some other logic has changed, so now the same fix doesn't work anymore.

So I started investigating the other end, that is, the watch. The major difference is now we have ROOT on the Gear, so why not use it?

I quickly figured out that the offending process on the watch side was "w-contacts2-consumer". Apparently, if you just kill it, this stops Contact synchronisation only, while Contacts app on the watch remains fully functional. Unfortunately, this process is respawned every time Bluetooth connection is reestablished between the the phone and the watch.

I was looking for "cron" for Tizen, hoping to put "pkill" into a recurring task that'd run every couple of minutes. Unfortunately, I couldn't find "cron" on the watch, and the version of busybox suggested in one of the threads on this forum doesn't have it precompiled.

Then I thought: why the heck can't I just write a small app (command line) that would literally just do this:

while(1)
{
system("pkill w-contacts2");
sleep(120);
}

After a bit of playing around with Tizen SDK, I managed to produce this executable (attached). You can put it into /sbin, making sure permissions are 755. One last thing is to make it run as a service:

systemd-run --unit=kill_contacts.nonsamsung --description="Automatically Kill Contacts Every 2 Minutes" /sbin/kill_contacts

I don't think it'll survive a reboot though, I'll get it sorted later.

Now battery consumption is back to normal, and contacts get synchronised every time the watch connects to the phone, which is more than fine with me.
[Samsung Gear 2] enko420:
Please continue your amazing work. my battery life is so bad I dont even use the watch.

also, if you could explain in a little more detail on how to do your new fix that would be great, im trying to do sdb shell cp kill_contacts.7z /sbin and I get cp: cannot stat `kill_contacts.7z': No such file or directory

but the file is in the directory im in because i used tab completion for the name
[Samsung Gear 2] kompis:
In setting for contacts in Gear Manager, I changed to Favorits and it helps and is much better than having all contacts to sync.
[Samsung Gear 2] mpogr:
Tried that in the past of my device (Sense 6 HTC One M8) and it didn't help at all. Apparently, the phone still sends all the contacts to the Gear, this setting just changes what's displayed on it when you open the Contacts app.
[Samsung Gear 2] mpogr:
OK, I think I need to publish a bit more detailed tutorial on how to use this app.

First of all, the 7z file is an archive, the actual executable is packed inside (use 7zip software on your PC to extract). You can then use sdb to push the file to the Gear. Once within the Gear shell (e.g. using "sdb shell"), if you did "sdb root on" beforehand, you can change permissions ("chmod 755 kill_contacts") and copy the file to /sbin ("cp kill_contacts /sbin"). Then you can run it as a service ("systemd-run --unit=kill_contacts.nonsamsung --description="Automatically Kill Contacts Every 2 Minutes" /sbin/kill_contacts"), but it will still not survive the Gear reboot. I need to figure out how to create a proper service configuration file, so it gets started automatically upon reboot. Will update on that later.
[Samsung Gear 2] best97:
Thank you for sharing this

I've got a question, should I insert this file into my Galaxy S4 or into my Gear 2? Because there are /sbin folders in the S4 and in the Gear 2 :)

Thanks :)
[Samsung Gear 2] mpogr:
Gear 2. Please, read my next post for more details.

Also, just in case you missed it, you need to have root on you Gear 2 / Neo.
[Samsung Gear 2] enko420:
if someone only has 200 contacts in their phone, could this still drain battery life?
[Samsung Gear 2] mpogr:
Don't know, it also depends on how often the watch/phone decide to synchronise. Sometimes looks like they're doing it all the time, so the exact number of contacts might not matter.
[Samsung Gear 2] baseball4355:
Oh wow yeah mine dies so fast
[Samsung Gear 2] evanlizhanzhang:
how to do it

my phone can not read sim card， what can i do ?and i have restore the factory setting , and no use
[Samsung Gear 2] kompis:
I prefer a work around without need for root like modified Goprovider apk, if possible.
[Samsung Gear 2] mpogr:
The goproviders solution is too fragile, as any update of Gear Manager breaks it. Rooting the Gear is actually very safe and you can always flash it back to factory...
[Samsung Gear 2] stickydonkey:
I too had battery issues all of a sudden. The Gear 2 would barely last a day. NOW, I am on my 4th day at 42% remaining!!!!! :laugh:

I ended up factory resetting both devices. Set Gearmanager/MyApps/Contacts to Favorites instead of All. It tells you then that you will have to manually resync if you change your Favorites contacts details. I have also turned off the Wake gesture. Everything else is standard. I haven't installed any other apps to the Gear 2.

Hope this helps someone.

Using Gear 2 and Galaxy S5
[Samsung Gear 2] L3534N:
Same here
[Samsung Gear 2] dwpang:
hi hi may i ask whats the battery drain like when you guys run the music player?

the battery like went down 50% after listening to 1.5 hours.

is it common for you guys?

if it's left alone, battery is pretty gd. 2 or 3% drain every 2 hours.
[Samsung Gear 2] hashcheck:
My battery life sucks on a neo 2 with all fixes tried. In 1hr dropped 10%
[Samsung Gear 2] vikramdhani:
Mine sucks as well. Connected with Samsung note 3
[Samsung Gear 2] Skin1980:
I just want report my story:

With ur mod,after 56hr from full charge, always connected to bt, i had 70% left!

Really nice job!
[Samsung Gear 2] mpogr:
Thanks for the feedback, which mod are you referring to? Is it the original goproviders mod or the new contact-sync-killer one?
[Samsung Gear 2] Skin1980:
I'm referring to Goproviders mod... I also use a custom watchface but not from watchstyler... If i'm not wrong its called clocky from playstore that install the wgt directly on the phone and is very battery friendly.
[Samsung Gear 2] mpogr:
So that means you didn't upgrade to the new Gear Manager. Otherwise you would need the second mod...
[Samsung Gear 2] rorijam:
I will try the same measures as You did, because know after 4 resets and trial an error, I have to recharge in the middle of the day to keep it running until 8 pm :(

It is running between 5 to 7 hours know... I have WATCH STYLER and TRENDIE, very nice Watch Faces installed, it is very sad for to Me to avoid using this faces... but if necessary lets have an ugly watch then :) ...SAMSUNG: You Ought to solve this!

Thanks...
[Samsung Gear 2] Lazzeuz:
still unfamiliar with the fix

Hi guys, i just received my gear 2 neo about a week now, and its draining VERY FAST!!! about 7hrs could drain a fully charged watch

I read about your fix but still unfamiliar about it, could you simplify it (sorry but im not that tech savvy :( ) step by step and is it safe for my gear 2 neo?

any help would be appreciated !!

Edited, Im using note 2 (unroot) 4G NT 7105 and galaxy gear manager build 22 Jul (its new)
[Samsung Gear 2] vat829:
i'm getting no such file or directory as well. Please help
[Samsung Gear 2] Lazzeuz:
no update anymore??? hope someone could give a hint of how to solve my problem NT-7105 and gear 2 neo with fast draining battery :silly::highfive:
[Samsung Gear 2] mpogr:
Well, the latest update is to use "kill_contacts" app on the Gear. This one is universal because it doesn't depend on the version of the Gear Manager. You do need to root your Gear for it to work though.
[Samsung Gear 2] Lazzeuz:
i'll try to look it up then...wish me luck =)

so to round it up i need:

1. root my gear 2 neo

2. install the kill_contacts

3. reset the gear manager ???
[Samsung Gear 2] mpogr:
This is not needed.
[Samsung Gear 2] Lazzeuz:
okay...oh and the kill_contacts app is in 7z archive isn't it?
[Samsung Gear 2] mpogr:
It is. Unpack and push to /sbin using sdb (make sure you did "sdb root on" beforehand), then change permissions to 755.
[Samsung Gear 2] vat829:
Hey mpogr, I'm still getting No such file or directory now matter what I do can you do a detail tutorial so i can see what im doing wrong
[Samsung Gear 2] mpogr:
While manipulating files using command prompt (Windows or Unix), you need to remember the following rules:

1. When invoking an executable, it either needs to be on your path (%path% environment variable in Windows, $PATH in Unix), current directory (only on Windows) or you need to specify full/relative path to it (using \ on Windows or / on Unix). For example, if your "sdb.exe" on Windows is in "c:\tizen-sdk\tools", you need to invoke it using "c:\tizen-sdk\tools\sdb" or do "cd c:\tizen-sdk\tools" and then "sdb".

2. When referring to a file as a part of other command, you need to specify its relative or full path (filename only will do it only if you're in the very directory where the file is located). For example, if your "kill_contacts" file on Windows is in "C:\Users\blah\Downloads", you need to do "cd c:\users\blah\downloads" and only then you can refer to it by its name. e.g. "c:\tizen-sdk\tools\sdb push kill_contacts /sbin". If your current directory is "c:\tizen-sdk\tools", then it needs to be "sdb push c:\user\blah\downloads\kill_contacts /sbin".

Likewise, after you pushed the file to the watch, you need to use the same logic, just in the Unix land, e.g.:

C:\Users\blah\Downloads> c:\tizen-sdk\tools\sdb push kill_contacts /sbin
C:\Users\blah\Downloads> c:\tizen-sdk\tools\sdb root on
C:\Users\blah\Downloads> c:\tizen-sdk\tools\sdb shell
# chmod 755 /sbin/kill_contacts
# systemd-run --unit=kill_contacts.nonsamsung --description="Automatically Kill Contacts Every 2 Minutes" /sbin/kill_contacts

Hope it helps. Remember to run the service (repeat the last command) after each Gear restart!
[Samsung Gear 2] ahmedmsvb:
Solved - No Root

Hello,

I think the issue was solved for me without root (at least error "

E W-CONTACTS2-CONSUMER: ct-sap-svc-parser-contacts.c: __ct_sap_svc_get_default_number_str(998) > [0;31m* Critical * contacts_record_get_str() Failed(-61)[0;m

" stopped appearing).

The steps followed were:

1- Remove contacts with special characters.

2- Remove Google account

3- Add Google account again.

4- Restart phone

5- Factory reset Gear 2 Neo, perform the pairing again (without using the data restore option in Gear Manager).

6- Select only Google account in the "Contacts to Display" option in your Contacts app from the phone.

Notes:

- During the issue, I was getting the above mentioned error +200 times each single second. This means the Gear was trying >200 times a second, and this is the cause of battery drain.

- After applying the steps [1-6], the error no longer appears in my log file +20 minutes now.

Hope this helps someone else.

[Edit]: 1 hour since the solving the issue with <1% battery consumption
[Samsung Gear 2] wiedz:
To make kill_contacts permanent, you can create service so that it will automatically start on reboot

create file named kill_contacts.service

[Unit]
Description=Automatically Kill Contacts Every 2 Minutes

[Service]
ExecStart=/sbin/kill_contacts

[Install]
WantedBy=multi-user.target

push this file to /etc/systemd/system

change mod to 644

enable service

start service

c:\sdb root on
c:\sdb push kill_contacts.service /etc/systemd/system
c:\sdb shell
sh-3.2#chmod 644 /etc/systemd/system/kill_contacts.service
sh-3.2#systemctl enable /etc/systemd/system/kill_contacts.service
sh-3.2#systemctl start kill_contacts.service

check running service using :

journalctl -u kill_contacts.service
[Samsung Gear 2] mpogr:
Thanks mate, I was too lazy to dig all this out...
[Samsung Gear 2] mpogr:
Sorry mate, tried this before, it helps, but only temporarily. Sooner or later (e.g. after Gear/phone reboot), the issue comes back...
[Samsung Gear 2] JimSmith94:
I had to change "ExecStart=/sbin/kill_contacts" to "ExecStart=/bin/kill_contacts" because that's where you originally said to push kill_contacts to, but it's running now. Thanks!
[Samsung Gear 2] OngL:
The fix has been very useful for me, I have a very long Gear 2 battery (previous normal was 2 days, then becomes ½ day, after the root fix becomes 1 week).

I'm interested to try your fix below without root. Which part of the contact that should not have special characters? Any way to filter it easily in Google contacts? Lastly, is this 'fix' stable for few days running?
[Samsung Gear 2] ahmedmsvb:
Working [Even after restart]

Hello,

For me:

- Some contact names were having special characters.

- Sorry, I don't know a way to filter it easily in Google contacts.

- The fix is stable till now (~1% per hour consumption and 25% per day [Pedometer is on always]).

- I double checked by restarting my gear (and the phone), and examining the dlog_main file --> our error didn't appear in it
[Samsung Gear 2] wanggit:
I got this message after doing sdb push "can not close remote file with failed msg 'Read-only file system'.

please help.
[Samsung Gear 2] wiedz:
Ah, forget to make the system rw.

c:\sdb shell mount -o remount, rw /
[Samsung Gear 2] wanggit:
Thanks! Now my drain rate is 8-10% in 6 hours with gesture on.
[Samsung Gear 2] Skin1980:
[MENTION=787470]mpogr[/MENTION]

I sent u a PM, or at least i think that i sent u ( sorry but i cant see in my output folder)
[Samsung Gear 2] rogerioteo:
root Works fine for me.
[Samsung Gear 2] aiu:
Hi,

After installing the service battery drain is well better but I cannot figure out how to sync my favorites after adding a contact and also the logs seems not to sync at all. Does anybody else seen this?

Thanks,

Alex.
[Samsung Gear 2] aiu:
After multiple tests I come to the conclusion that with the service enabled the logs and contacts will not sync at all, ever. In order to get the logs and contacts to sync again you need to remount / rw and then disable the service with systemctl and reboot. Afterwards the sync works fine but the battery drain is of course back. Does anybody have an idea on how to keep the gear syncing without affecting the battery life? Is this behavior something expected or it is just my gear? Thanks in advance for any reply.
[Samsung Gear 2] Skin1980:
I have an LG G3 and my contacts are sync. Cannot help with call logs since it never worked for me, also with stock.
[Samsung Gear 2] sivarajkumar:
Complete procedure for newbie

Hai can you explain in details the code for a newbie as i am not familier with codings but have sdb.exe and like to test your way of doing.

Thanks inj advance
[Samsung Gear 2] aiu:
Hi mpogr,

First thanks a lot for all your work. Using the root/service method on the Gear 2 for me didn't work well because I was unable to sync contacts or logs anymore. I decided to flash stock back on Gear 2 and downgrade GM to 2.1.14052101 and use the goproviders apk you provided specially for this version of GM. Now battery drain is great, logs sync well but contacts will not sync again. If I manually try to sync them from the Gear 2 side it says Syncing for a while and then it stops without really syncing them. Do you have any suggestions on how to sync the contacts in this scenario?

Again thanks a lot for all your great work!
[Samsung Gear 2] mpogr:
What device do you have? On non-Samsung devices only contacts would synchronise anyway... If you have Samsung, why would you use these fixes anyway?
[Samsung Gear 2] aiu:
Galaxy S5. As you wondered in the OP the problem exists even on Samsung devices. My Gear 2 drains a full battery in 8h without your mod. A friend of mine with a Note 3 has experienced the same.

Anyway how should contacts sync be affected by using your goproviders?

Again thanks for your great work.
[Samsung Gear 2] mpogr:
Look, what goproviders fix does it just dilutes the sync logic invocations 1:256 (in the latest version). Also, I didn't create that fix for the latest versions of Gear Manager, so using the modded goproviders with those is not recommended and could break all sorts of things. I don't really know why the fix on the Gear doesn't work for you though. After connecting the Gear to the phone, there is typically enough time for the contacts to synchronise, even just once. The sync process is killed every 2 minutes, so it's a matter of luck. But, if you attempt several times (just disconnect/reconnect the Gear with the phone), it should work.
[Samsung Gear 2] aiu:
I am using goproviders with the corresponding older version of GM just as you recommended. I think it works ok now. How often is 1:254? I don't know the original behaviour so I cannot calculate it.
[Samsung Gear 2] mpogr:
It's hard to tell, because the frequency of the sync doesn't seem to be constant. It's probably about once in 1-2 hours.
[Samsung Gear 2] aiu:
I see. Anyway thanks a lot for this fix. I was not using the watch anymore because of the battery issue. Now it is usable again. Really great work.
[Samsung Gear 2] GSBJackson:
Found my root cause. Had over 9,000 duplicate entries in my corporate contact list. Once deleted, now I can go all day with battery at 90%.

Running latest version from Samsung.
[Samsung Gear 2] vinny.1967:
Hi wiedz, sorry to bothering you I'm very new to this but how do you create kill_contacts.service file?

thanx
[Samsung Gear 2] JazonX:
Hi, Can I know the last version (Version Number if possible) of Gear Manager that worked with the modded GoProviders.APK Mate?

I'm on Galaxy Note 3, with Gear 1 (Null)

Thanks!
[Samsung Gear 2] jazzdoctor:
Help!!!!!

I really appreciated the GoProviders fix....now back to the same 12hr to dead Gear2 paired with Samsung Note3...any thoughts as to how I can address this...I work in a Mac/Apple environment . Not sure if that program functions on the Mac. Any direction would be greatly appreciated. Thanks!!!