[BUG] <title>excessive overheating

[Whoisipo]

Code of conduct

• I have read and agree to adhere to the Code of Conduct

Self-training on how to write a bug report

• I have learned how to write a bug report

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

On an ipad, for the past couple months the chat has been plagued with constant issues: from absolute disaster when it comes to synchronization (I’ve been using a single address on iOS iPadOS and MacOS ) to the overall inability to sending or receiving files/messages send /receive simple text message .
For the past couple weeks my iPad is getting really hot when I leave the iPad on probably any live chat,. Probably waiting on some gif or an image to get through the pipe.

Expected Behavior

To just work!

Steps To Reproduce

Wait on some image /file to get downloaded and leave the iPad on the relevant chat/session window.

iOS Version

iPadOS 17.5.1

Session Version

2.6.2(452)

Anything else?

No response

[KeeJef]

If you have upgraded to version Session iOS version 2.6.3, you should be experiencing fewer issues with sending and receiving attachments. I am curious if you are still encountering the overheating issue on version 2.6.3. If so, it would be helpful if you could send the Session logs from your device (in Session, go to Settings -> Help -> Export logs) and attach them here or send to our support email.

[Whoisipo]

com.loki-project.loki-messenger 2024-08-19--15-04-00-604.log
currwntly on version 2.7.0
Still,. The Synchronisation between a mac, an iPad and an iPhone is a nightmare. Completely unpredictable. A load of images sent to me from different users won’t get downloaded, ever.
Thank you for your time and effort.

[naturalbornhamburger]

Hi, I am a new user, both of session and github.
Obviously my problem with session seems to fit in here.
I have serious battery usage problems with the current iOS version on my iPhone 12 Pro and I can also observe this on an iPhone 7 Plus, both with their latest iOS Versions and Session 2.8.2. It appears not to be a constant behaviour which is easily to be reproduced.
On the iPhone 12 Pro:
1h 32 minutes in foreground,
42 minutes in background = 2h14m total takes 46% battery usage, though display brightness was set quite low and used in an inside, quite dark environment. Plus the phone heated up quite strong.
A friend with an Android phone seems to face similiar experiences.
Any ideas? Thank you.

I tried to contact session internal group but I was rejected to post my message there with the note that new users are not permitted to post there.

[KeeJef]

Hmmm it does seem like Session is a bit of a battery hog on my device too, i think the increase in battery usage coincided with the move to libquic for communication with Service Nodes, is this your understanding too @mpretty-cyro ? If so, we are working on some libquic changes, not sure if any of those changes are likely to reduce battery usage though?

[mpretty-cyro]

Hmmm it does seem like Session is a bit of a battery hog on my device too, i think the increase in battery usage coincided with the move to libquic for communication with Service Nodes, is this your understanding too @mpretty-cyro ? If so, we are working on some libquic changes, not sure if any of those changes are likely to reduce battery usage though?

Yep pretty much - for the worst 10% of cases the battery usage increased by:

• While the app is in the foreground: about 0.7% per day (from 3.6% to 4.4%)
• While the app is in the background: about 2.65% per day (from 0.25% to 2.9%)

It's hard to say why the background usage has increased this much compared to the foreground usage but I know I've also fixed a few bugs with background polling and finishing off work when immediately being sent to the background, so not sure if those have had an impact (eg. maybe it didn't work at all previously)

@KeeJef There may also be additional tweaks we can make when running in the background to disable some of the logic so that it takes less work (eg. refreshing the snode pool, maybe a couple of other things) but a number of the changes we could make will likely result in making and background work less reliable if the app isn't opened frequently enough 😕

[naturalbornhamburger]

My iPhone recently (yesterday) heated up so much while using Session in foreground, that it even stopped charging due to overheating. And that in an inside room with little light and at 20°C room temperature. Never had something like that before with any other app.
Currently running on iOS 18.3, btw.

[naturalbornhamburger]

I‘d appreciate letting me know if there will be cure for this disease, pls. see attached two screenshots. I will have to ditch Session otherwise since it is literally destroying the iPhone battery.

[KeeJef]

Yeah, we're merging in some libquic fixes into the GroupsV2 release which should be coming out soon. We're hoping that these fixes will resolve issues where libquic was using 100% of CPU in certain cases. We think this 100% CPU usage may be leading to increased battery drain, so resolving these issues in libquic should reduce battery drain. But we wont know this for sure until we deploy the new GroupsV2 release.

[mpretty-cyro]

@naturalbornhamburger I just wanted to give you a heads up that the libQuic changes won't be included in the upcoming GroupsV2 release (2.9.0) but are a high priority so should be included a release shortly after - the main reason for this is that 2.9.0 has already completed internal testing whereas the libQuic changes are still being tested

If you wanted to track the changes these are the PRs involved (the first one being the core changes and the other two just updating libSession to use the new code):

• Working 0-RTT, stateless reset, retyping, more efficient datagrams oxen-io/oxen-libquic#156
• Header reductions oxen-io/oxen-libquic#157
• Updated to the latest stable libQuic, Retyped the networking code libsession-util#26

Once these have all been merged and the testing completed there will be a PR on this repo to use a new version of libSession that includes the changes

[naturalbornhamburger]

@mpretty-cyro : Thank you just for not getting me the feeling of not being forgotten. Would you mind changing your point of view into a plain user ones? Meaning that I have no clue what needs to be done, HOW LONG it takes (I started my conversation with KeeJeff back in November I think) nor do I have any ressources to estimate myself if and when it is solved at all? As I said: It affects two totally different iPhones with various iOS versions heavily, renders Session useless and not recommendable for mobile use on iPhones imho. So - what is the expected time line explained for dummies? I mean, the origin of this thread is already getting close to a year now indicating that something could be terribly wrong from a user perspective.
Thank you very much.

[naturalbornhamburger]

May I again ask for a time schedule, at least a rough estimation? To demonstrate, pls. see again what actual Session does to an iPhone battery.

[mpretty-cyro]

@naturalbornhamburger we've just started the rollout for Release 2.10.0 which includes a few updates to the networking code and a fix for at least one behaviour that could result in excess CPU usage (the app may not automatically update for a few days, but you can manually install the update via the AppStore)

Let us know if you still happen to experience the battery drain issues as we are also looking at adding a setting to switch between using Quic and HTTPS/TCP for sending network requests which may also help if the new fixes don't resolve the issue