[1.0.7.16/18] Battery drain and heating up after Update 7 [not relevant]
Since I updated to the latest Firmware I've got massive Battery drain and the Jolla is getting very hot. Lighthouse says a Process called tracker-store is constantly using CPU with around 40-50%. Do anybody know this process or what to do? thanks!
Update: Today I had the same problem without tracker-store. My Jolla got very hot because different processes intensively used the CPU. Looking at Lighthouse told me, that the phone restarted by itself (uptime 10min) in my poket and tracker-store reappeared. Has anyone similar problems?
Update 2: Maybe the problem is linked to the new connman in my case, because after killing tracker-store in my case the phone also got hot in situation with poor wifi signal, where the phone always try to reconnect, I will figure it out with the old connman and report.
Update 3: still on 1.0.7.18, now it's appearing randomly - heating and massive battery drain - no special process but constant 50% CPU-Usage... :(
Update 4: maybe tracker-store is indexing the android apps rainisto (jolla) posted some kind of indexing after updating...
Update 5: got an answer from rainisto tracker-store is indexing your media files (may take up to 24h, if process is killed, will restart after restart)
Update 6: Tracker-store seemed to finish index, last time no need to kill the process - device still gets hot :(
Update 7: maybe related to mitakuuluu. Process doesn't appear in lighthouse but sometimes when CPU-Usage is high restarting mitakuuluu helps - who of you is using mitakuuluu?
Update 8: Developer is working on a fix in the futher mitakuuluu version: https://github.com/CODeRUS/mitakuuluu2/issues/141
Update 9: I observed my device for a couple of days. It's not only related to mitakuuluu gone wild. Battery drain is much higher than with paarlampi. Hunger Meter shows higher power consumption than before without using 4G...
Update 10: Maybe all lf us having problems should participate here: Battery Report for all Stages of Sailfish OS what do you think?
Update 11: 1.0.8.19 seems not to change anything in this case
Update 12: Mitakuuluu has been released in Version 0.8.1.-4, the release note describes different bugfixes and a probably fix for the 100% CPU-Usage-Problem. So let's have a try! I'm figuring it out since yesterday and I observed less battery drain through the night. I'm going to update the post in a few days with a final report, if the problems got fixed or if there other problems ;-)
Update 13: Sometimes I got the problems but under normal conditions no more problems. I have Hunger meter open all the time, in high power consumption phases I close mitakuuluu and reopen.
Final Update: Since massive problems with registration through mitakuuluu and getting banned for using mitakuuluu and Coderus stopping developing further, I switched to Android Whatsapp. Now my problems are gone. Now I have an average power consumption of 300mW, befor it was between 500-600mW. I don't know exactly if it is also related to updating to 1.1.0.39. Tracker-process don't use the CPU as much as before with the latest version.
noticed that when I use the camera or the internet then the area of the front camera is strongly heated.
sa.rasputin ( 2014-06-14 01:02:50 +0200 )editi noticed the same problem of sa.rasputin
Francesco ( 2014-06-14 10:15:52 +0200 )editshould like to bring this issue developers.
sa.rasputin ( 2014-06-14 10:31:28 +0200 )editDid you allready have a look at lighthouse while device is heated like discribed? Maybe it is also a special process causing the heat with intensiv CPU-Usage...
drummer12 ( 2014-06-14 16:52:28 +0200 )editHad a not so massive drain yesterday with 1.0.7.16: around 5% in half an hour without usage. Normaly the battery level reduces less than 5% during full night (8 hours without usage but WLAN connected).
Had used the hotspot for some minutes in the morning. Don't know if this was the cause.
Stopped all open apps. Checked top in terminal for CPU consuming processes. Nothing special. Battery drain still happened. Than switched on and off flight mode and it seemed to help.
axaq ( 2014-06-14 17:23:23 +0200 )edit