During the CCC presentation the librem 5 devkit had a heat problem. As it is a devkit it should be quite easy to cool it. (No need to but the devkit in a small Case. So a big cooler/Fan can be attachted.)
Also I don’t think that the devkit had a Lot of Activity laying around without Interactions.
I couldn’t find any info in your latest news regarding this problem.
What is the status of the librem 5 regarding the heat problem?
Is it fixed there?
Are you still working on it?
We need Purism to make a statement about this issue. The other design compromises are acceptable but if the phone is physically incapable of running for extended periods at near max rated cpu frequencies this project will fail.
There was talk about this in the other CCC-thread. They need not make statements at this time but concentrate on the work. They got a few weeks to sort them out and another few to test (if Q3 deadline is to hold). It would be nice to hear something, but if they only got some pcbs last week, a week or three is more realistic at this stage. No point in saying anything before that, since nothing is certain or known before.
Besides: if “work * time = 1”, then we should expect major work done the closer the deadline nears
Because it’s not related to the PCB but to the CPU drivers.
On one hand, the i.MX 8M Quad silicon issues meant not only that the temperature of the battery was way too high, but also that it could discharge too quickly. On the other hand, the i.MX 8M Mini is made in an updated silicon process (14nm instead of 28nm) and has reduced features, resulting in a lower power consumption–but it’s new, and there could be unknown issues and risks. So a lot of research was made, and our development team started evaluating the i.MXM8 Mini to see if it could be used within our requirements–free software only, no binary blobs, mainline based software stacks.
And then the month of February began, and something else unexpectedly happened: NXP released a new software stack for our first CPU choice, the i.MX 8M–and all of the power consumption and heating issues suddenly disappeared!
I’m sure they’ve worked / are working on the drivers and dev-kit, but it’s not untill the final pcb and housing (which is probably part of the heat transfer and dissipation) are worked on, that it’s possible to know how it’s going to perform - different airflow (compared to dev-kit), accumulating heat within the case, heat transfer to and from other parts (especially under different stress/use profiles)…
I just dont have anywhere to go and my bronco has an untraceable coolant leak my mechanic said he couldnt find . I was here for jeanne and frances in 04’ 145mph sustained with gusts upto 195mph . So this aint my first rodeo . Last cat 4 I was in I saw a 60ft singlewide trailer doing cartwheels down my road end over end . It was wild. plus I got enough food and gear to make it if I survive the hurricane. Itll be fun
The CPU makes up for everything else pulling way too much power (see the open issues), and gets up to 99% slower in the process. It only shows that the thermal driver works. This test (stress -c 4) currently makes the phone (lockscreen) unusably slow. A few minutes after stopping “stress -c 4”, the cpu still won’t be able to cool down and stays at 80°C + 99% idle-injection. Indeed this is important, but right now, results in really bad user experience. https://source.puri.sm/martin.kepplinger
This sounds already frightening and it was only 3 weeks ago.
The presentation on the Chaos Communication Camp of the Chaos Computer Club was on 2019-08-22 so just a week ago. At about 44:20 of the presentation Nicole Faerber wonders about the development device: “Now it is off. I don’t know why.” and assures: “It works perfectly well.” and says: “It’s pretty hot so power management is still an area we have to work on.”
The power management problem has officially been mentioned.
I can’t judge how well she is up to date on that issue.
I can’t judge how the development device compares to the end product.
The development device was off in that situation.
It is unclear why it was off. Problems of heat and power management are only one possibility. Maybe it was simply a mistake of usage.
The device was hot.
My experience of performances on ramps is limited but as far as I know it can get very hot up there because of the spot lights. That may promote problems of overheat.
We could speculate all day long. As this is potentially a major issue and it is stated officially just a week ago by the CEO (she is?, isn’t she?) of Purism I think Purism should go for transparency and clarify the situation. No matter if overheating was the reason that the device was off.
I really don’t want to make panic. I just think a clarification is better than speculation.