Suspending on Battery and Overheating Shutdowns

For starters, identify what causes the abnormal heat. Is the CPU getting busy? Is there an interrupt storm? Does it still happen when the phone stays suspended with all HKS engaged? Is it a software or hardware thing?

My phone gets fairly warm when under active usage and generates some noticeable heat when charging with high current, which is perfectly normal. It stays close to ambient temperature otherwise, plugged in or not. That’s the expected behavior. If what you’re experiencing is different, you need to look closer at what’s going on. There’s tons of reasons why it may happen and it’s hard to tell what could it be without having the device in question in front of you.

3 Likes

I certainly understand all of this. I need some support from Purism and I am not getting it. Which is a bummer. I appreciate your thoughts, time, rants, efforts, etc.

2 Likes

No, I didn’t install the package for that kernel. So, since it is marked as installed (installed), rather than automatically installed (installed,automatic), it must have been present in the PureOS image, which the script selected when I was reflashing my Librem 5 earlier this year. I do not know why the package is not in the apt repository (local).

apt states that the kernel package version is 6.5.13pureos1~byz1 and the homepage is https://source.puri.sm/Librem5/linux. An arbitrary package from the build artifacts of the source code repository cannot be guaranteed to be stable. There is an output that is marked 6.5.13pureos1_byz1 and has a kernel package for download. However, some of the files in the package are not the same as the files installed on my system.

~$ wget https://source.puri.sm/Librem5/linux/-/jobs/430075/artifacts/raw/debian/output/linux-image-6.5.0-1-librem5_6.5.13pureos1~byz1+gitlabci1_arm64.deb
~$ dpkg-deb -x linux-image-6.5.0-1-librem5_6.5.13pureos1~byz1+gitlabci1_arm64.deb testdir
~$ cd testdir
~/testdir$ sha1sum $(find .) | sed 's|\./|/|g' | sort > ~/testfile1
~$ sha1sum $(dpkg -L linux-image-6.5.0-1-librem5) | sort > ~/testfile2
~$ diff ~/testfile1 ~/testfile2
552a553
> 777c9362da02bb513a57a405a9cd90a5d5c4f4e4  /usr/share/doc/linux-image-6.5.0-1-librem5/changelog.Debian.gz
691d691
< 94e8a06233c5d0e6735e99666b7bfd1a2e957941  /usr/share/doc/linux-image-6.5.0-1-librem5/changelog.Debian.gz
984d983
< d16ce14f554fbf72a0c299c9e85e1ea815ab10e0  /boot/vmlinuz-6.5.0-1-librem5
1055a1055
> e130b636a86198f630de31e92b1fb1a35bd25943  /boot/vmlinuz-6.5.0-1-librem5
1160d1159
< f8a1ec132de0ccf4f0a86a98e9dacdc7eb68bc90  /boot/System.map-6.5.0-1-librem5
1179a1179
> fc7b66d88692516e4be421f455b2332d4ae4fb2d  /boot/System.map-6.5.0-1-librem5

Could it be a difference between the released and the unreleased packages?

$ cp /usr/share/doc/linux-image-6.5.0-1-librem5/changelog.Debian.gz changelog1.gz
$ cp ~/testdir/usr/share/doc/linux-image-6.5.0-1-librem5/changelog.Debian.gz changelog2.gz
$ gunzip changelog1.gz
$ gunzip changelog2.gz
$ diff changelog1 changelog2
0a1,6
> linux-librem5 (6.5.13pureos1~byz1+gitlabci1) UNRELEASED; urgency=medium
> 
>   * Gitlab ci build of dff3971eca8b4c3d253f62a370c5bbe667e9c8bc
> 
>  -- root <root@runner-y2ccahwv-project-566-concurrent-2>  Fri, 08 Dec 2023 13:05:31 +0000
> 

The latest code marked as released in that source code repository is for 5.7.19+librem5.1, so I am confused.

Unless there is a clearer way to identify and get a previously released kernel package, I would stick to the packages in the apt repository or available locally.

2 Likes

It’s a different build coming from different infrastructure, but from the same source code.

Old packages get removed from the archive.

3 Likes

Very thorough. I appreciate the time you spent on this very much. I will probably stick with image 6.3.9-1-librem5 for now.

1 Like