Remove All Ads from XDA

Root cause for Gear 2 high battery consumption found, at least for non-Samsung phones

185 posts
Thanks Meter: 63
By mpogr, Senior Member on 21st May 2014, 06:13 AM
Post Reply Email Thread
4th November 2014, 08:06 PM |#121  
Junior Member
Flag Dublin
Thanks Meter: 1
Originally Posted by mpogr

I switched to using TizenMod 3.0 Gear 2 ROM, which has the fix already built in, and never looked back ever since...

i flashed that last night still no joy have to charge watch everyday
10th November 2014, 08:04 PM |#122  
Junior Member
Thanks Meter: 0
Originally Posted by 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.

Sent from my GT-N7100 using Tapatalk

---------- 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.

Sent from my GT-N7100 using Tapatalk

Did you remove your google account while the watch was connected with phone?
12th November 2014, 12:52 PM |#123  
Thanks Meter: 0
hello friends ... I took a few days ago and am having trouble qusto smartwatch battery drain .. I installed 3.0 tizenmod I cleaned the cache .. but to no avail .. I am attaching "dlog_main" thanks to all the help ... x the problem seems to this string:

11-12 12: 18: 33 926 1156 1156 E EFL: edje <1156> edje_calc.c: 2678 _edje_part_recalc () Circular dependency a when calculating part "dummy.icon." Already calculating X [01] axes. Need to calculate X [01] axes
Attached Files
File Type: pdf dlog_main.pdf - [Click for QR Code] (53.2 KB, 30 views)
22nd November 2014, 01:29 AM |#124  
Thanks Meter: 0

This helped me with my Gear 2 and the battery last much longer. Thanks.
I have the same issue with Gear 1 that is flashed to Tizen and not yet rooted. Will this work around work in Gear 1 as well?
22nd November 2014, 01:48 AM |#125  
Silverbolt's Avatar
Senior Member
Flag Auckland
Thanks Meter: 25
Cannot install either apk on the Samsung Galaxy Note 4
26th November 2014, 01:05 PM |#126  
Senior Member
Flag Santa Cruz
Thanks Meter: 18
Gear Mananger 2.214110499 has the same bug. My battery used to last 3 days... now only 9 hours!
26th November 2014, 08:27 PM |#127  
charlypaez's Avatar
Senior Member
Thanks Meter: 278
Sorry guys... I have a little doubt... Yesterday I update my rom in my Galaxy Note 4 sm-910c and today my gear 2 have high drain of battery, what I can do? Can some one help me? Maybe Bluetooth problem? Thank you for the advice!

Note 4, SM-910C Model.
25th March 2015, 03:36 PM |#128  
Junior Member
Flag Atlanta
Thanks Meter: 1
Applicable to Galaxy Gear S also
This thread was helpful to me. I thought I would add that I had the same problem with my Galaxy Gear S and Note 4. Saumsung was suggesting I send the device in for repairs when the batter would go from 100% to off in 4 hours. It was even charging significantly slower. The battery would only discharge at a normal rate when bluetooth was turned off. After clearing the data from the gear management application the device went back to more reasonable battery consumption.

Note: I'm only using the installations and firmware that came directly from Samsung on my device.
7th May 2015, 02:40 AM |#129  
Thanks Meter: 19
I'm Paired to my OnePlus One. I did a phone wipe and a watch wipe, and the drain was just horrible.

Getting a lot of these in my log.
05-06 16:05:11.207  6276  6276 E EFL     : edje<6276> edje_calc.c:2678 _edje_part_recalc() Circular dependency when calculating part "dummy.icon". Already calculating X [01] axes. Need to calculate X [01] axes
Flashed back to stock, and still the same problem. Using a OnePLus One
17th January 2016, 02:58 AM |#130  
Junior Member
Thanks Meter: 1
Originally Posted by mpogr

Edit: with new Gear Manager (Jun release), this method doesn't work anymore. The new approach is to install a "contact synchroniser killer" app on the rooted watch. More details are in this post.

================================================== ================================================== ================================================== ============================

Hi all,

Ever since I started using my Gear 2 Neo with my HTC One M8 phone (using the guide in this forum), I noticed that my watch consumes battery significantly faster than most of the users have been reporting. Even more strangely, sometimes after resetting both the phone and the watch (and I've done this a lot while experimenting and trying to get more stuff working) I had streaks of stellar battery life, well in line with optimistic reports here and elsewhere, but then, after a while, it started deteriorating very quickly.

So I decided it was time to do something about it. I installed Tizen SDK, hooked the watch up and started poking around. The first thing I noticed my watch CPU was, most of the time, sitting on 40%! Well, that doesn't sound right, does it? Then I noticed the log (located under /var/log/dlog_main) was full with messages related to contact synchronisation. It turns out the damn thing synchronises all of my contacts every several seconds. The trouble is I have well over 1500 contacts (that's consolidated from different sources, the number of raw contacts should be well over 3000). So it takes significant time to do this, meaning my watch (and the phone!) are thrashed by these stupid full contact syncs all the time! What's even more striking is the fact it doesn't help when I change it to "favourites only". Apparently, this affects only the contacts displayed on the watch, however, the sync process still takes all of them.

At this point I started poking around Samsung APK files to try and understand what was going on. Apparently, the APK responsible for contact sync is called GOPROVIDERS. Indeed, if you kill it, the thrashing stops, however, other important functions cease working as well. Aside of Contacts vanishing from the Gear, "Find my phone" is gone as well, but, more importantly, notifications stop working. While I could tolerate the first two, the last one was too much to give up.

I started decompiling and analysing sources. Apparently, there is a process running every several seconds that analyses if any changes have been made to the contacts. It uses pretty bizarre logic which seems to be relying on Samsung-specific fields in the contacts. Now, this already sounds suspicious, and, apparently, leads to full sync every several seconds. Obviously, the more contacts you have, the harder you're hit.

An interesting point in all this is that I'm not 100% sure the logic is working properly even on Samsung devices, so it might well be that the same issue is affecting people with high number of contacts using Samsung phones as well. I'd be really interested to see any feedbacks regarding this.

So, long story short, instead of fixing the logic (which is quite difficult in SMALI), I made a simple change which dilutes this logic invocations, right now 1:64. Since then I'm enjoying MUCH improved battery life.

The fixed APK is attached. You're welcome to give it a try at your own risk (you need to enable installation from untrusted sources + reboot and clean dalvik cache).

so I decided this is fortunately a bug. it's one that takes 25% of my battery life of both devices. I have about 3000 contacts. I own a business, and thirty years of owning phones, it add up. yes I could go clean up, but even if I delete half of my contacts, I will still be affected.

I decided to open a ticket with Samsung support. to my surprise, the gent Jeff was a pleasure to talk to, I even pointed the ticket to this thread to get them started and understanding the problem.

I would suggest if you are affected by this problem, call Samsung support at(888) 257-8100. they are available ,24 hrs a day, 7 days a week.

hopefully, this well get routed to the dev team. I have them the com.Samsung path (check my attachment for information on the path, cpu utilisation. I seer note I missed the -1. I'll keep this thread posted..
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2016-01-16-20-53-51.jpg
Views:	70
Size:	206.0 KB
ID:	3612718  
17th January 2016, 06:43 AM |#131  
OP Senior Member
Flag Melbourne
Thanks Meter: 63
I have different devices now (Samsung Galaxy S6 + Samsung Gear S) and don't have this problem anymore, so can't comment.

Sent from my SM-G920I using Tapatalk
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes