Revision history [back]

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTube Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port on my power bank used, to charge the phone was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, so as other experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a full fresh, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to hunger meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

• Cellular was enabled (i.e. no Airplane mode)
• Display brightness was set to the lowest possible setting, auto brightness was disabled.
• Mobile Networking was turned off
• Wi-Fi was turned off
• Bluetooth was turned off
• Location tracking was turned off
• Android Support/Alien Dalvik was disabled
• The following apps were open:

Crest (to look for a potentially power sucking task) Hunger Meter (to measure the power consumption) Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running give a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding out the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above 1.5A is used.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTube Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port port, in use, on my power bank used, to charge the phone was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, so as other experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a full fresh, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to hunger meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

• Cellular was enabled (i.e. no Airplane mode)
• Display brightness was set to the lowest possible setting, auto brightness was disabled.
• Mobile Networking was turned off
• Wi-Fi was turned off
• Bluetooth was turned off
• Location tracking was turned off
• Android Support/Alien Dalvik was disabled
• The following apps were open:

Crest (to look for a potentially power sucking task) Hunger Meter (to measure the power consumption) Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running give a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding out the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above 1.5A is used.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTube Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, so as other experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a full fresh, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to hunger meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

• Cellular was enabled (i.e. no Airplane mode)
• Display brightness was set to the lowest possible setting, auto brightness was disabled.
• Mobile Networking was turned off
• Wi-Fi was turned off
• Bluetooth was turned off
• Location tracking was turned off
• Android Support/Alien Dalvik was disabled
• The following apps were open:

Crest (to look for a potentially power sucking task) Hunger Meter (to measure the power consumption) Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running give a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding out the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above 1.5A 5 V is used.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTube Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, so as other hopeful that others, experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a full fresh, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to hunger meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

• Cellular was enabled (i.e. no Airplane mode)
• Display brightness was set to the lowest possible setting, auto brightness was disabled.
• Mobile Networking was turned off
• Wi-Fi was turned off
• Bluetooth was turned off
• Location tracking was turned off
• Android Support/Alien Dalvik was disabled
• The following apps were open:

Crest (to look for a potentially power sucking task) Hunger Meter (to measure the power consumption) Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running give a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding out the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above 5 V is used.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTube Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, hopeful that others, experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a full fresh, fully fresh install, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to hunger meter, Hunger Meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTube YouTuber Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, hopeful that others, experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a fully fresh install, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to Hunger Meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

1. Cellular was enabled (i.e. no Airplane mode)
2. Display brightness was set to the lowest possible setting, auto brightness was disabled.
3. Mobile Networking was turned off
4. Wi-Fi was turned off
5. Bluetooth was turned off
6. Location tracking was turned off
7. Android Support/Alien Dalvik was disabled
8. The following apps were open:
9. Crest (to look for a potentially power sucking task)
10. Hunger Meter (to measure the power consumption)
11. Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running gives a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more and continues to stay there during use, regardless of how the phone is being used.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above anything other than 5 V is used, even if the port has the ability to output 5 V if requested by the phone.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTuber Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, hopeful that others, experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a fully fresh install, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to Hunger Meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

1. Cellular was enabled (i.e. no Airplane mode)
2. Display brightness was set to the lowest possible setting, auto brightness was disabled.
3. Mobile Networking was turned off
4. Wi-Fi was turned off
5. Bluetooth was turned off
6. Location tracking was turned off
7. Android Support/Alien Dalvik was disabled
8. The following apps were open:
9. Crest (to look for a potentially power sucking task)
10. Hunger Meter (to measure the power consumption)
11. Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running gives a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more and continues to stay there during use, regardless of how the phone is being used.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above anything other than 5 V is used, even if the port has the ability to output 5 V if requested by the phone.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTuber Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, hopeful that others, experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a fully fresh install, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to Hunger Meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

1. Cellular was enabled (i.e. no Airplane mode)
2. Display brightness was set to the lowest possible setting, auto brightness was disabled.
3. Mobile Networking was turned off
4. Wi-Fi was turned off
5. Bluetooth was turned off
6. Location tracking was turned off
7. Android Support/Alien Dalvik was disabled
8. The following apps were open:
9. Crest (to look for a potentially power sucking task)
10. Hunger Meter (to measure the power consumption)
11. Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running gives a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more and continues to stay there during use, regardless of how the phone is being used.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above anything other than 5 V is used, even if the port has the ability to output 5 V if requested by the phone.

As mentioned in a post below, I also observed the device heating up considerably despite being in stand-by without any process aside from Hunger Meter running, lending more credence to the hypothesis that something appears to actually draw from the battery and strain the phone.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Edit: Just fixed a few typos and logical inconsistencies as well as added some clarification concerning the fast-charging issue.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTuber Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, hopeful that others, experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a fully fresh install, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to Hunger Meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

1. Cellular was enabled (i.e. no Airplane mode)
2. Display brightness was set to the lowest possible setting, auto brightness was disabled.
3. Mobile Networking was turned off
4. Wi-Fi was turned off
5. Bluetooth was turned off
6. Location tracking was turned off
7. Android Support/Alien Dalvik was disabled
8. The following apps were open:
9. Crest (to look for a potentially power sucking task)
10. Hunger Meter (to measure the power consumption)
11. Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running gives a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more and continues to stay there during use, regardless of how the phone is being used.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above anything other than 5 V is used, even if the port has the ability to output 5 V if requested by the phone.

As mentioned in a post below, I also observed the device heating up considerably despite being in stand-by without any process aside from Hunger Meter running, lending more credence to the hypothesis that something appears to actually draw from the battery and strain the phone.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Edit: Just fixed a few typos and logical inconsistencies as well as added some clarification concerning the fast-charging issue.

Edit 2: Added some newly observed behavior, the device appears to be hot consistently.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTuber Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, hopeful that others, experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a fully fresh install, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to Hunger Meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

1. Cellular was enabled (i.e. no Airplane mode)
2. Display brightness was set to the lowest possible setting, auto brightness was disabled.
3. Mobile Networking was turned off
4. Wi-Fi was turned off
5. Bluetooth was turned off
6. Location tracking was turned off
7. Android Support/Alien Dalvik was disabled
8. The following apps were open:
9. Crest (to look for a potentially power sucking task)
10. Hunger Meter (to measure the power consumption)
11. Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running gives a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more and continues to stay there during use, regardless of how the phone is being used.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above anything other than 5 V is used, even if the port has the ability to output 5 V if requested by the phone.

As mentioned in a post below, I also observed the device heating up considerably despite being in stand-by without any process aside from Hunger Meter running, lending more credence to the hypothesis that something appears to actually draw from the battery and strain the phone.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Edit: Just fixed a few typos and logical inconsistencies as well as added some clarification concerning the fast-charging issue.

Edit 2: Added some newly observed behavior, the device appears to be hot consistently.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTuber Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, hopeful that others, experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a fully fresh install, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to Hunger Meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

1. Cellular was enabled (i.e. no Airplane mode)
2. Display brightness was set to the lowest possible setting, auto brightness was disabled.
3. Mobile Networking was turned off
4. Wi-Fi was turned off
5. Bluetooth was turned off
6. Location tracking was turned off
7. Android Support/Alien Dalvik was disabled
8. The following apps were open:
9. Crest (to look for a potentially power sucking task)
10. Hunger Meter (to measure the power consumption)
11. Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running gives a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more and continues to stay there during use, regardless of how the phone is being used.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above anything other than 5 V is used, even if the port has the ability to output 5 V if requested by the phone.

As mentioned in a post below, I also observed the device heating up considerably despite being in stand-by without any process aside from Hunger Meter running, lending more credence to the hypothesis that something appears to actually draw from the battery and strain the phone.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Edit: Just fixed a few typos and logical inconsistencies as well as added some clarification concerning the fast-charging issue.

Edit 2: Added some newly observed behavior, the device appears to be hot consistently.

Edit 3: My request to Jolla Zendesk has remained unanswered. I shall over the next days, downgrade back to 2.1.4 in the hopes of this solving the issue and thus potentially serving as a starting point to pin-point whatever is causing this exorbitant power consumption.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTuber Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, hopeful that others, experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a fully fresh install, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to Hunger Meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

1. Cellular was enabled (i.e. no Airplane mode)
2. Display brightness was set to the lowest possible setting, auto brightness was disabled.
3. Mobile Networking was turned off
4. Wi-Fi was turned off
5. Bluetooth was turned off
6. Location tracking was turned off
7. Android Support/Alien Dalvik was disabled
8. The following apps were open:
9. Crest (to look for a potentially power sucking task)
10. Hunger Meter (to measure the power consumption)
11. Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running gives a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more and continues to stay there during use, regardless of how the phone is being used.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above anything other than 5 V is used, even if the port has the ability to output 5 V if requested by the phone.

As mentioned in a post below, I also observed the device heating up considerably despite being in stand-by without any process aside from Hunger Meter running, lending more credence to the hypothesis that something appears to actually draw from the battery and strain the phone.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Edit: Just fixed a few typos and logical inconsistencies as well as added some clarification concerning the fast-charging issue.

Edit 2: Added some newly observed behavior, the device appears to be hot consistently.

Edit 3: My request to Jolla Zendesk has remained unanswered. I shall over the next days, downgrade back to 2.1.4 in the hopes of this solving the issue and thus potentially serving as a starting point to pin-point whatever is causing this exorbitant power consumption.

Edit 4: I am unable to obtain an older release of Sailfish and thus cannot downgrade. If anyone knows where I could download an older ROM, please let me know. Also, still no reply from Jolla Zendesk.

Edit: On 2.1.3.8, 2.1.3.5, power consumption is reduced to around 1200 mW during normal use, which lead me to conclude that my initial presumptions were correct. The power draw I've experienced on versions like 3.0.0.8 is simply excessive and not reflective of what Sailfish OS has consumed in the past. Please read my answers to this question for more details.

Hey everyone,

First of all, I would like to thank everyone on here, willing to help me. What follows is a very detailed write up on my experience with Sailfish OS, as well as when and how I started experiencing problems, both with charging and power consumption. As said write-up goes in depth beyond my current issues, I've also added a short summary at the bottom, solely containing the technical details surrounding my current situation.

Let me start out by saying that I've been a fan of Sailfish OS ever since it was first announced seven years ago. Sporadically following the development, I was always impressed by the constant stream of improvements and when the YouTuber Michael Fisher published a video highlighting the interface and Android App support, coupled with the fact I needed a new smartphone anyways, I pulled the trigger and bought a Xperia X with the goal of running Sailfish on it.

Initially, I started out with the most current stable release at the time, Sailfish OS 2.1.4. My experience was honestly great. The system ran stable, battery life was almost comparable to my outgoing device (a Xiaomi Redmi Note 3 Pro with a 4000mah battery behemoth) and most everything worked as expected. Especially the fact Alien Dalvik handled notifications as would be expected if an app ran natively surprised me, in a good way. Only major point of criticism at the time was the fact that Sailfish didn't offer a "top menu" accessible via any screen, something I knew was going to be addressed with Sailfish 3.

My experience on 2.1.4 thus was great with no major issues.

In June of 2018, Sailfish OS 2.2.0 was released and I, at first, felt great about it. Having support for the fingerprint sensor was, while not a pressing issue for me personally, definitely greatly appreciated and showed that the dev team were hard at work making consistent improvements.

However, this was the first time I experienced both battery and charging issues. It felt to me, as if both Screen-On-Time and power consumption in standby were severely worsened over 2.1.4. At the time, I was both in Italy and the United Kingdom quite a lot, which is why initially, I concluded that my seemingly reduced battery life was the result of the device being used more regularly for tasks such as navigation via HERE and communication among other things.

I realized that things did not work as intended when, despite the phone being consistently charged via a 10000mah power bank, it seemed to lose charge, something that obviously made no sense. Only when charging it via the official Sony wall adapter, did the phone receive a consistent and reliable charge.

Reading the print on said adapter, I noticed that it was rated to only output 1.5A at 5V, which is obviously far from anything that would enable "fast-charging".

The port, in use, on my power bank was rated to, at least, output 1.5A at 9-12V or, alternatively, either 2A at 6-9V or 3A at 3.6 to 6V, each depending on what the phone specifically requested.

Changing over to the "slow" port, at the time used by my camera, I was able to charge my Xperia X for the first time using the power bank. That port is rated to output 2.4A at 5V.

At the time unable to address these issues, as I was reliant on the phone, I unfortunately was essentially forced to run the phone connected to that "slow" charging port pretty much all day.

Once I found myself back home and with some time to debug this issue, I decided to do a full system reset of the phone. I found, to my surprise, that this did not in fact reset the phone to a factory state for a 2.2.0 install, but actually back to my initially flashed 2.1.4 state. As I had been looking through forums, like this one, unable to find people reporting the issues I experienced on 2.2.0 (a few people seemed to report issues similar to my fast-charging "bug" on older versions though reported to have fixed them due to a factory reset), I decided to once again upgrade to that version.

Sadly, this did not appear to remedy my issues. As however, not a few days later, Sailfish OS 2.2.1 was released, I decided to hold off on writing such a post, being hopeful that, despite not being noted in the change logs, this may be something miraculously addressed in 2.2.1.

Unfortunately, that wasn't the case. As I still was not able to find other people reporting similar issues on either 2.2.0 or 2.2.1 I still wanted to hold off on writing such a question, as I somewhat felt that this issue may be caused by my specific use case, rather than Sailfish itself, thus making me feel like I could still find the culprit of said issues myself, then later reporting my "fix" on here, hopeful that others, experiencing similar behavior could benefit from it.

Equally, I wanted to wait for the release of a "flashable" release of Sailfish 3, as I speculated/hoped that perhaps a fully fresh install, without any updates in between may be able to solve the problems I experienced since 2.1.4.

As I likely don't have to tell you, with Sailfish 3.0.0.8, those "installable images" of Sailfish 3 were just released. I thus set to work, first fully factory resetting my phone, then right after that flashing Sailfish 3.0.0.8 together with the Sony vendor binary images.

Using the phone for a day now, this sadly has not rectified the issues I've been experiencing.

Due to this, I finally decided to do some digging on my own, trying to pin-point the culprit.

Using both Crest and Hunger Meter, I made a surprising discovery. The power consumption was, to put it mildly, terrifying, as the phone, according to Hunger Meter, consumed above 2000 mW.

Looking at this paper, in which a Xperia XZ2 is measured consuming less than 500 mW total, that seemed fairly excessive: https://www.sciencedirect.com/science/article/pii/S1877050916317756

Due to this, I decided to turn off features in an attempt to figure out, what was consuming so much.

I ended up taking measurements with the phone in the following state:

1. Cellular was enabled (i.e. no Airplane mode)
2. Display brightness was set to the lowest possible setting, auto brightness was disabled.
3. Mobile Networking was turned off
4. Wi-Fi was turned off
5. Bluetooth was turned off
6. Location tracking was turned off
7. Android Support/Alien Dalvik was disabled
8. The following apps were open:
9. Crest (to look for a potentially power sucking task)
10. Hunger Meter (to measure the power consumption)
11. Screenshot (as to make a Screenshot of the results)

Following is the output of Crest and Hunger Meter while everything with the exception off cellular connection was disabled and the screen was set to the lowest brightness possible:

As you can see, Crest doesn't show any task that could be responsible for requiring in excess off 2000 mW of power. Adding to that, turning on Airplane mode also does not lead to a reduction in power consumption. Waking the phone up from standby with only Hunger Meter running gives a result of around 1000 mW that, seconds after turning the phones screen on, jumps to over 2000 mW once more and continues to stay there during use, regardless of how the phone is being used.

Concerning my issue with fast-charging, i.e. that it appears to actually discharge the device, I was unable to discern any way by which I could obtain data that might help in finding the root cause.

I hope that this is a resolvable issue and am very thankful for any assistance.

Summary:

Had great battery live on 2.1.4, however, since 2.2.0 the phone draws in excess of 2000 mW, a behavior observed even after a factory reset and a fresh flash off the 3.0.0.8 image.

Phone also draws over 2000 mW when screen brightness is set to the lowest possible setting, Alien Dalvik, location tracking, Bluetooth and networking are disabled and no process that could draw this much is being run.

Adding to that, phone draws in excess of 1000 mW while in standby with only Hunger Meter open.

Also, phone discharges when a charge port rated above anything other than 5 V is used, even if the port has the ability to output 5 V if requested by the phone.

As mentioned in a post below, I also observed the device heating up considerably despite being in stand-by without any process aside from Hunger Meter running, lending more credence to the hypothesis that something appears to actually draw from the battery and strain the phone.

When looking through forums, like this one, I sadly was unable to find similar issues that were not fixable via a simple factory reset.

I hope you are able to help me resolve this seemingly excessive power draw. Should any further information be required, please don't hesitate in telling me whatever would be necessary.

Thank you very much and have an excellent day.

Edit: Just fixed a few typos and logical inconsistencies as well as added some clarification concerning the fast-charging issue.

Edit 2: Added some newly observed behavior, the device appears to be hot consistently.

Edit 3: My request to Jolla Zendesk has remained unanswered. I shall over the next days, downgrade back to 2.1.4 in the hopes of this solving the issue and thus potentially serving as a starting point to pin-point whatever is causing this exorbitant power consumption.

Edit 4: I am unable to obtain an older release of Sailfish and thus cannot downgrade. If anyone knows where I could download an older ROM, please let me know. Also, still no reply from Jolla Zendesk.