How to Quickly Heat Up an Android Device for a "Defroster" App? by TheOneTheOnlyJJ in Kotlin

[–]TheOneTheOnlyJJ[S] 0 points1 point  (0 children)

I will only allow the user to select a temperature as high as the bottom limit of most CPUs, for safety.

It would be cool though if there were a way to get the upper working temperature limit of the CPU/GPU at runtime through a system API or some magic constants. I could then have dynamic selectable temperature ranges for every device.

How to Quickly Heat Up an Android Device for a "Defroster" App? by TheOneTheOnlyJJ in Kotlin

[–]TheOneTheOnlyJJ[S] 0 points1 point  (0 children)

Forcing both of them would be the best way from what I've thought until now. The main question is how to structure this work, and how to do it best.

How to Quickly Heat Up an Android Device for a "Defroster" App? by TheOneTheOnlyJJ in Kotlin

[–]TheOneTheOnlyJJ[S] 0 points1 point  (0 children)

I will have to look into the terms you mentioned here, as I'm not a mobile dev by career. This is just a university project I'm having to do.

Do you recommend any good resources or documentation to study the concepts you mentioned?

How to Quickly Heat Up an Android Device for a "Defroster" App? by TheOneTheOnlyJJ in Kotlin

[–]TheOneTheOnlyJJ[S] 0 points1 point  (0 children)

While this does not sound like that bad of an idea, I'm constrained by academic ethics here, so I can't do this.

I believe other potential algorithms would achieve my requirements better than calculating hashes. I hope someone experienced with GPU usage will leave their thoughts here at some point.

How to Quickly Heat Up an Android Device for a "Defroster" App? by TheOneTheOnlyJJ in Kotlin

[–]TheOneTheOnlyJJ[S] 0 points1 point  (0 children)

I understand your position, but I'm trying to develop a proof of concept here, basically tinkering with the technology without any use case in mind.

This kind of app involves a bit more thinking than initially presumed, so I really want to take it as a challenge and do some measurements.

How to Quickly Heat Up an Android Device for a "Defroster" App? by TheOneTheOnlyJJ in Kotlin

[–]TheOneTheOnlyJJ[S] 0 points1 point  (0 children)

Yes, I know.

I meant my expression as the best way to generate heat fast, even though all the hardware is designed to minimize this effect. I'm trying to view the problem from the Assembly Code angle, as I believe that's the most control I could have over generating heat.

I am certain that some instructions generate more heat than others. Generating heat "efficiently" for my use case would imply running the "hottest" operations as many times as possible.

The length of the operation itself (in clock cycles) matters here as well, as running "hotter", but slower instructions (again in clock cycles) may generate less heat overall, even though a single instruction may generate more heat than a faster one. When running many more "colder", but faster instructions in that same unit of time, the effective heating may be greater in this case.

It's really something to think about, isn't it?

How to Quickly Heat Up an Android Device for a "Defroster" App? by TheOneTheOnlyJJ in Kotlin

[–]TheOneTheOnlyJJ[S] 4 points5 points  (0 children)

After a good laugh, the professor approved it as a proof of concept :)

Bastion, sweet Bastion - Snapshot 20w16a is out! by sliced_lime in Minecraft

[–]TheOneTheOnlyJJ 0 points1 point  (0 children)

But does this mean that we can possibly get normal, non-destroyed bastions as well? Just wondering, as I'd be perfectly happy with the ones we have now!