Battery behavior 2.0.0.10

Question

12

Battery behavior 2.0.0.10

asked 2016-01-27 00:42:52 +0300

palikao

4258 ●55 ●85 ●75

updated 2018-12-03 23:05:35 +0300

Tanghus
10524 ●85 ●118 ●125

https://github.com/tanghu...

I would like to submit to the community my case: I purchased the JP1 with SFOS2 (2.0.0.10) installed. I noticed, with normal use, not intensive, that the behavior of the battery is very strange: it is discharging by 20% in just 1 hour of use (3G), and hardly, starting at 8 AM, I can reach 10 PM with my JP charged.. I would expect to make 1,5 days..

I have only WhatsApp (Android) on autorun.

Here are some screenshots (for 2 days and 4 days).

image description

edit retag flag offensive close delete

Comments

I also have strange battery behaviour (2.0.0.x and 2.0.1.x) Btw, what app are you using to show battery life?

richdb ( 2016-01-27 08:37:20 +0300 )edit

These screenshots are taken from System Monitor app, a SFOS app

palikao ( 2016-01-27 09:47:46 +0300 )edit

2

More of the same:

https://together.jolla.com/question/126248/will-the-201x-update-solve-battery-drain-issues/

https://together.jolla.com/question/127658/2017-battery-drain/

;)

Kollin ( 2016-01-27 11:41:21 +0300 )edit

1

@Kollin I hope too, but I'm on 2.0.0.10, and those are hopes and bugs from 2.0.1.7

palikao ( 2016-01-27 18:50:10 +0300 )edit

Same problem here now! Since one week I have a massive problem with battery drain. In test case battery is 100% full, and phone stays in my pocket most of the time during working hous. But after 8 hours it is nerly empty.

Tried following, but did not help:

Disabled Situations autostart
Restart and kept all Android apps closed (especially Whatsapp)
Bought a new accu, because I thought it is damaged
Rebooted multiple times

No solution after all. What makes it strange, 2.0.1.0 is installed this a month or so, but problem exists only a week. Any new ideas?

SaimenSays ( 2016-03-01 19:56:55 +0300 )edit

I also have strange battery behaviour (2.0.0.x and 2.0.1.x) Btw, what app are you using to show battery life?
richdb ( 2016-01-27 08:37:20 +0300 )edit
These screenshots are taken from System Monitor app, a SFOS app
palikao ( 2016-01-27 09:47:46 +0300 )edit
More of the same:
https://together.jolla.com/question/126248/will-the-201x-update-solve-battery-drain-issues/
https://together.jolla.com/question/127658/2017-battery-drain/
;)
Kollin ( 2016-01-27 11:41:21 +0300 )edit
@Kollin I hope too, but I'm on 2.0.0.10, and those are hopes and bugs from 2.0.1.7
palikao ( 2016-01-27 18:50:10 +0300 )edit
Same problem here now! Since one week I have a massive problem with battery drain. In test case battery is 100% full, and phone stays in my pocket most of the time during working hous. But after 8 hours it is nerly empty.
Tried following, but did not help:
Disabled Situations autostart
Restart and kept all Android apps closed (especially Whatsapp)
Bought a new accu, because I thought it is damaged
Rebooted multiple times
No solution after all. What makes it strange, 2.0.1.0 is installed this a month or so, but problem exists only a week. Any new ideas?
SaimenSays ( 2016-03-01 19:56:55 +0300 )edit

Answer 1

5

answered 2016-03-02 19:28:53 +0300

SaimenSays

6943 ●92 ●146 ●141

Maybe I've figured out the problem, at least in my case. After disabling the mobile data connection, battery drain was gone. But this is not a steady solution for me, because it was never a problem in last year. So I did a little investigation and accidentaly I see the message on terminal:

Letzte fehlgeschlagene Anmeldung: Mittwoch, den 02. März ... von 59.47.5.236 auf ssh:notty
Es gab 5325 fehlgeschlagene Versuche seit der letzten erfolgreichen Anmeldung

So there is someone or a bot on the net, trying to attack my phone. And so sshd causes CPU usage, GSM modem is working the whole time and drains my accu.

Why is sshd open on mobile connection?
How can I figure out if someone had success and entered my phone? Unfortunately there is no /var/log/auth.log
How can I block all open ports on mobile connection?

edit flag offensive delete publish link

Comments

I would have thought mobile connections to be behind NAT to prevent this kind of stuff.

If you are 100% you are not giving your IP out via some app to someone who has grudge on you, you could contact your operator and ask them to give you new IP and/or block the bot's IP and the bombing should stop. But it won't work if some of your apps/services leak your new IP to the bot.

avhakola ( 2016-03-02 21:38:58 +0300 )edit

1

well, if you're with Deutsche Telekom / T-Mobile you get a public IP Address without NAT, so you may be attacked accidentally .

jollajo ( 2016-03-02 22:02:52 +0300 )edit

2

I can login to phone via ssh when I use the ip of 'rmnet0', so it is sure a public IP. Now I'm trying to setup iptables to get rid of this problem and also avoid misleadingly open ports by apps.

But in my opinion an all ACCEPT policy is a completly disaster of sailfish OS!

SaimenSays ( 2016-03-02 23:39:20 +0300 )edit

1

Well Port Sentry or Fail2Ban could slow the attacker down, but doesn't remove the problem...

avhakola ( 2016-03-03 01:26:47 +0300 )edit

1

Actually I can confirm failed ssh login attempts on German T-Mobile/Congstar network. You can check via journalcl | grep ssh

I'd guess i would help to switch sshh port away from the standard port 22 to e.g. 2222. However I'm worried of side effects.

jollajo ( 2016-03-03 10:15:57 +0300 )edit

Answer 2

3

answered 2016-04-02 18:58:27 +0300

Bury
91 ●3 ●7 ●10

updated 2016-04-02 19:03:29 +0300

My case is similar.

Android support, WLAN, BT, GPS off. 2G. Only I have set the alarm. Interestingly, after the reboot suddenly the battery level increased by a few percent: / It is my first contact with this situation.

image description

edit flag offensive delete publish link

Battery behavior 2.0.0.10

Comments

2 Answers

Comments

Question tools

Stats

Related questions

Battery behavior 2.0.0.10

Comments

2 Answers

Comments

Question tools

Public thread

Stats

Related questions