yashsingh1/xdaforums huggingface dataset:
[HTC One Mini] pure.by:
Of course it isn't and it won't ever be under the current attitude of the "development" "team" . And even if it will, there are just too many other major unacceptable issues with this ROM which make it kinda unusable on HTC One Mini anyway.

The overheating issue happens to other CM-based ROMs as well. In the other thread I mentioned above there was a recent report of the same issue on PacMan ROM (CM-based).

I have no idea whether this issue occures on the latest nightlies, but the M7-release surely effects

all

users (it just haven't happend to everyone, yet)

Keep us informed! I don't think it's possible that your phone keeps getting hotter from the inside after it's switched off. What you're probably experiencing is the processor slowly cooling down by emitting heat to the case (which gets hotter because of the absorbed heat from the processor).

EDIT:

Sorry mate, no I have no idea. To me the whole overheating and dieing issue happend in an instance, I had no time to react. If I were you now, I would just leave the phone off or boot into bootloader to make sure it doesn't do too much. I would also try to keep an eye on the battery so it doesn't drain by putting the phone on charger for 1 minute every 5 or 10 minutes, and looking at how that influences the heat. I have no idea why I'm saying this, it's just an instinct, something I would have done, based on no specific knowledge (and at the same time, based on all my knowledge).

I wish you luck, mate!

EDIT 2:

How's your phone now?
[HTC One Mini] milchmaennchen:
Sorry [MENTION=2886679]theodorius123[/MENTION] that sounds pretty bad.
[HTC One Mini] sausje85:
Hmm, my PC doesn't see the phone when it's connected with MTP?!

Any idea why this might be, i tried searching this topic but couldn't find anything (or i'm just really bad).

And the front cam records up-side-down?!
[HTC One Mini] theodorius123:
after 1 hour being very very hot its cold now - as normal. but this only because IT IS DEAD now :(

after being happy with my new M4 for 3 weeks now I`m quite sure that this is my last CM-phone - even if I really really love it....
[HTC One Mini] pure.by:
Sorry to hear this, man :(

I think CM is a great ROM and not to blame. I've used it for years on all my devices so far and it was nearly flawless, with pros outweighing cons at an incomparable rate. But next time I'll double check that the specific CM port for my future device is properly maintained by a team of developers, before installing it. What I recommend to you as well.

And yeah, not to forget: read all the 100500 pages of the related forum thread as well, as an M-flag does not indicate quality, it appears.
[HTC One Mini] htc_one_mini_m4:
At this time CM ROM IS the problem.

There's no phone death ( not in a week, month, especially not in an hour or almost instant after flashing the ROM like it happened with CM11 ) with any ROM that's not based on CM.

Everybody fails sometimes, it's human nature.
[HTC One Mini] pure.by:
Yes I agree. I just meant to say that CM is a great ROM working flawlessly on dozens of phones, each maintained by a team of skilled developers. Which obviously isn't the case with HTC One Mini port: it's not maintained, by a single person, and about his skills I'm not going to say anything but the 200~300 bricked devices, including his own.

This all silently without a warning or a word, under the M-flag-release, ignoring all reports of bricked devices until it happened to himself, and then just silently drop the project and leave the thread, telling people it's their fault they didn't read 60+ forum pages.

Now I think that is the real problem, not CM.
[HTC One Mini] u-ra:
While I don't really care what you think about me or my development skills, I need to address some factual inaccuracies in your entitled little diatribe.

Did I say I dropped the project? When?

Between the time the first reports of overheating started coming in and my own device dying I was working round the clock (and not just me) to figure out what's wrong. I'm not really sure on what do you base your claim the problem was ignored. Are you following me around? How do you know I haven't worked on the problem even after my device died? (Because I did.)

You also claim there are "just too many other major unacceptable issues with this ROM", and yet you haven't reported a single one. I went through your post history. There isn't a single one. Which kinda tells me you like to demand things, for free, not give anything back, and then insult people who give away their free time to work on supporting a device and ask nothing in return.

Oh, and sorry I told you to read 60+ forum pages. You should totally expect to invest zero effort into using a replacement, warranty voiding, potentially unstable software for your device. It's almost as if you're forced to use it.

Now,

could someone attach the output of "adb shell find /sys"?
[HTC One Mini] theodorius123:
I would like to post a last comment here before leaving the M4-section - cause my Nexus 5 arrived today ;)

I would really like to say thank you to u-ra - I guess without your work we wouldn't have a working CM for the M4 - and in my opinion CM was working really great - despite this pain-in-the-ass-overheating problem.

I have to agree that a note in the first post, that this problem still exists, would be appropriate. but I would never blame anyone here for this stupid bug.

everyone here knows that we are doing things that can kill our phone - its written everywhere! so [MENTION=2309555]pure.by[/MENTION] stop blaming the person who did most for the M4-community!

I hope you'll be able to sort this problem out, for me it was just too much loosing two M4s in a month - so I hope my new N5 will last a little bit longer!

THANKS TO (almost) EVERYONE HERE!
[HTC One Mini] jenkins-84:
Well said, yeah I noticed a few new users seem to be trolling around these forums lately and only seems to the in original thread too.....
[HTC One Mini] u-ra:
Thank you, and I'm really sorry about your devices. I just wanna say I can't possibly take credit for this device, because the project was well on its way before I joined.
[HTC One Mini] kyasu:
I would like to say thank you to u-ra for your great work.

I use CM11 of one mini and one mini 2. Both are your work and very stable for me.

Here is.
[HTC One Mini] u-ra:
Can you check which of these thermal zones report meaningful numbers?

/sys/devices/virtual/thermal/thermal_zone10/temp

/sys/devices/virtual/thermal/thermal_zone0/temp

/sys/devices/virtual/thermal/thermal_zone1/temp

/sys/devices/virtual/thermal/thermal_zone2/temp

/sys/devices/virtual/thermal/thermal_zone3/temp

/sys/devices/virtual/thermal/thermal_zone4/temp

/sys/devices/virtual/thermal/thermal_zone5/temp

/sys/devices/virtual/thermal/thermal_zone6/temp

/sys/devices/virtual/thermal/thermal_zone7/temp

/sys/devices/virtual/thermal/thermal_zone8/temp

/sys/devices/virtual/thermal/thermal_zone9/temp
[HTC One Mini] kyasu:
Here is:

$ cat /sys/devices/virtual/thermal/thermal_zone0/temp
36
$ cat /sys/devices/virtual/thermal/thermal_zone1/temp
36
$ cat /sys/devices/virtual/thermal/thermal_zone2/temp
37
$ cat /sys/devices/virtual/thermal/thermal_zone3/temp
37
$ cat /sys/devices/virtual/thermal/thermal_zone4/temp
36
$ cat /sys/devices/virtual/thermal/thermal_zone5/temp
35
$ cat /sys/devices/virtual/thermal/thermal_zone6/temp
/system/bin/sh: cat: /sys/devices/virtual/thermal/thermal_zone6/temp: Invalid argument
$ cat /sys/devices/virtual/thermal/thermal_zone7/temp
35
$ cat /sys/devices/virtual/thermal/thermal_zone8/temp
36
$ cat /sys/devices/virtual/thermal/thermal_zone9/temp
/system/bin/sh: cat: /sys/devices/virtual/thermal/thermal_zone9/temp: Invalid argument
$ cat /sys/devices/virtual/thermal/thermal_zone10/temp
36612
[HTC One Mini] u-ra:
Would you (or someone else) be willing to try this thermald configuration and post logs?

http://vukad.in/m4/thermald

http://vukad.in/m4/thermald.conf

Push these two to /data/local/tmp and adjust permissions.

Run "adb logcat -s ThermalDaemon" in another window and pipe that into a file.

You should stop thermald with "adb shell stop thermald" and then manually run the new one with "adb shell /data/local/tmp/thermald -d -c /data/local/tmp/thermald.conf".

If there are no errors, try running something intense like Antutu stability test and watch the log. Stop the test in case of errors and start the old thermald. Don't run the test more than a minute or two.
[HTC One Mini] kyasu:
I tried running Antutu stability test for two minutes.
[HTC One Mini] u-ra:
I've updated the config file. Could you run this one a little longer?

Same location, http://vukad.in/m4/thermald.conf
[HTC One Mini] kyasu:
I tried running Antutu stability test for seven minutes.
[HTC One Mini] u-ra:
Okay, this is looking pretty good. I think everyone can push this to their devices now. If someone could make a flashable zip, I'd really appreciate it.

Note that this doesn't mean the problem is solved, it just means the device should have better protection. If your phone still gets too hot, try restoring or installing a Sense based ROM as soon as possible. It might save your phone. But then again it might not.

I'll be away for the next two weeks, but I'll be working on this more when I get back. Major props to kyasu for helping out with this!
[HTC One Mini] kyasu:
Ok, here is a flashable zip which can be installed in custom recovery.
[HTC One Mini] dipje:
I think the 'report' button is there just for people like pure.by.

Just saying thing like 'I hope you are never allowed to do dev again' violates the #1 rule on XDA by my opinion: Be grateful for the things people are spending their free time on.

Thinking that CM11 working on different devices has _any_ meaning for how it should work on this one is just plain ignorant and shows you that he/she really doesn't know how things work and what the devs have to do to get that far.

Not having posted much him-/herself. The thread with 'problems on CM11' that is linked to is not full of people having problems. It's 3 pages talking about 5 _maybe_ issues, one of which actually got his device back to working state (so it was something else). Wouldn't really call that a big problem.

All pure.by posts are edited / different now. "for the sake of all mini owners; I hope you get your device back ASAP" was "for the sake of all mini owners; I hope you never do dev again".

Post that was first ranting about the dev leaving the project and 'leaving the users' is now 'can you confirm that you stopped working on the mini or not'. To be honest I can't understand why his/her posts are still here and not deleted by a mod.

And after all is said and done, you have the clear disclaimer that you're putting stuff on your phone that the manufacturer has a reason to be protected, and put after all kinds of unlock-protections and stuff: It's not meant to be tampered with unless you know what you're doing and you accept the risks. What works one one device might not work on all the others, and since we don't _make_ the devices, the whole process kinda consists of "Let's do this and see how it works" so problems like 'oops, sorry to hear that it is working fine for me' are _bound_ to happen, no matter how good the dev is or how stable the device is. It's part of the risk of flashing custom stuff to your phone, and this is a good reminder for the people who tend to forget that.
[HTC One Mini] theodorius123:
I would like to share some information on how to deal in case of overheating - even if I hope it's gone now for everyone.

- for me flashing stock sense did not help.

- I noticed, that the phone can be kept alive as long as you charge it - when battery reaches 0% you reached "game over".

the battery drain is massive when the problem starts, so hurry up. I left the room and my PC went to standby and so stopped charging - and the phone was dead when I came back 30min later. while charging the phone was working for maybe 2-3 hours - but almost untouchable cause of the heat.

- as long as you don't reach 0% you can backup all your stuff, make a nandroid and copy this to your computer. so even the phone will die, you will not loose any data.

- as long as you don't reach 0% you may be able to save your phone with flashing something magic. but no idea what this could be ;) maybe the file u-ra and kyasu just published if you haven't done this already.

This is my experience - maybe its working different for others. But maybe this helps anyone here in some way.

PS: I'm really happy with my Nexus 5 - but missing the nice and smooth M4-body a little bit ;)
[HTC One Mini] pure.by:
Dear u-ra, I would like to apologize to you and to the community for the things I've said because of my frustration with a bricked phone. I shouldn't have posted that, because installing a custom ROM is, of course, something I do totally at my own risk. I am glad you replied in a friendly manner and I will alter my attitude in the future.

If I may, I'd also like to explain what caused such a frustration on my side.
[HTC One Mini] u-ra:
I thought you said you installed a stripped down CM version instead of Sense?

Also, you probably left TWRP as the installed recovery, right? If you switched it off and left it charging, it was TWRP which was handling offmode charging. TWRP has the same kernel and thermald as stock CM, so it likely has the same problem. I hadn't thought of that...

I guess people should also restore HTC recovery if they start having the problem...
[HTC One Mini] theodorius123:
I used a stripped down version of CM when the problem started. But I flashed a stock Sense ROM + kernel as fast as I can when I noticed the phone is getting warmer and warmer.

yes. did not know this....
[HTC One Mini] pure.by:
Thanks a lot for taking your time for the explanation, dipje. My apology is 100% sencere as I have honestly gotten no warnings at all (besides that Ghost PM'd me in a very friendly manner informing me that a small part of my post has been removed because it was seen as disrespectful). That very friendly reply actually got me rethinking the situation, and opened my eyes to having a wrong attitude. For which I apologize. As you have very well described, my frustration was greatly caused by my ignorance. I've indeed built up my expectations on CM based on my experience on other devices, which is wrong thing to do.

But the thing is, I didn't get angry when my phone initially god bricked. I got angry a couple weeks later when I've discovered that there were about ~20 reports of CM-bricked devices here on XDA, of which about 10 reports in this very thread alone.

Developer had know this, yet there was no warning of any type,

not here on the forum

(which is done easily by editing the first post),

not on CyanogenMod website

— I've done a full research before installing CM, besides that I decided that reading 600+ forum thread replies might be a little overkill. Seriously, if the developer is aware of a problem

this

huge, you expect a warning somewhere. I remember it from years back here on XDA: every ROM had a "Known issues" section before download link, like "Camera fixed, GPS not working yet" or something.

Or you would at least expect that CM in it's current stage should be placed under the "Experiments" or "Nightlies" section — I wouldn't even consider installing it on my phone in the first place. But instead, the release was labeled as "M7-release" (which 'actually' means "a seventh stable major version in a row, safe to install for everyone"). Even if the overheating problem would not have been there, I would get real disapointed by installing an M-release which is as buggy as current M7 — some core features of the phone are broken, like notification LEDs, no microphone in Skype and wrong loudspeaker volumes in many apps, just to name some I have discovered withing a first hour). But the overheating issue overshadows this all. You have to take into account that statistically speaking the ~20 reports here on XDA represent not more than 10~20% of the actual amount of phones bricked. You're talking hundreds, not dozens bricked phones here. I personally don't understand how this build can still be online under the M-category.

Once again, I

have

done a good research before installing CM on all my phones including One Mini. S-OFFing my phone didn't interest me at that point, as it was not required according to official CM installation manual for One Mini: http://wiki.cyanogenmod.org/w/Install_CM_for_m4 . Right now I'm on InsertCoin, which requires S-OFF and updated firmware, so I got S-OFF and updated my firmware, as simple as that. I can't be blamed for not knowing something not required to achieve a desired goal.

Long story short, the conclusion I made for myself: next time read all 100500 forum pages and don't expect anything.
[HTC One Mini] u-ra:
Erm, you seem to think M7 means "a seventh stable major version in a row, safe to install for everyone" for HTC One Mini, when in fact it means "a seventh milestone version in a row of CyanogenMod 11, which is more stable than nightly builds". This was the first M release for One Mini, so you should think of it as the M1 release.

EDIT: M7 was actually the second milestone release for One Mini.

Furthermore, the overheating problem was not known when M7 was tagged, or it would never have gotten an M release. You have to give us a bit more credit than that.

Also, your "bug report" is extremely vague. What's wrong with notification LED? Which apps have "wrong" loudspeaker volumes? What does "wrong" mean here? Too loud? Too quiet? I'm pretty sure mic in Skype was working when M7 was tagged. Can someone else confirm this?

This thinly veiled sarcasm is not doing you any favors. What bothers me the most is that you seem to think I (and other devs) don't care. I paid $350 for my device. I don't have stacks of money lying around so I can just let devices overheat and croak and move on. I bought it used, with no warranty. I have to take it into repair and foot the repair bill myself. And I'll do that just so I can keep working on it. Think about that for a second.
[HTC One Mini] nqr:
confirmed. skype mic is working on M7 and newer nightlies. (speaker phone aka with video, and handset modes)
[HTC One Mini] milchmaennchen:
Thanks for continuing development! And thanks for that thermald configuration!

BTW I'm running CM stable since some months with [MENTION=4861355]kyasu[/MENTION]'s kernel.
[HTC One Mini] scoobdriver:
Bricked / Dead

My Device Died, Wont switch on / Charge or anything withing 1 day of flashing this ROM - Just a warning to people.. The battery was draining very quickly and it got warm even when not switched on ? ?

anyone been able to fix the device once this happens or am I totally out of luck, cant get it to do anything, its totally dead.

Regards
[HTC One Mini] :
Try this. Charge the battery (it might not say it's charging, but it should still charge). Then hold power and volume up buttons at the same time. The navigation buttons might flash 10 times or they might not flash at all depending on the state of your phone. Just keep holding it and your phone should boot into the bootloader.
[HTC One Mini] scoobdriver:
Yeah I Tried that .. Nothing ... :(
[HTC One Mini] theodorius123:
sorry to hear that!

I now what you are talking about - after two dead M4s with the same problem I can tell you that - in my case - nothing helps.

but good luck!
[HTC One Mini] u-ra:
I'm really sorry to hear that. Is your device under warranty?

Also, did you flash the thermald zip from a few pages back? I realize now it is easy to miss, I'm gonna quickly update the first post.
[HTC One Mini] didierk:
Is the overheating issue somehow related to the hboot version 2.21 / 2.22 ?

Regards

Didier
[HTC One Mini] scoobdriver:
Well it would have been under warranty but I unlocked the boot loader which voids it.

I had flashed thermald as well
[HTC One Mini] htc_one_mini_m4:
Nope.

Running other ROMs with HBOOT 2.22 ( which is what 99% of the owners do, as most of the latest ROMs require HBOOT 2.22 ) without any issues.
[HTC One Mini] nqr:
Hey everyone,

Not sure if this is a cm11 bug, m4 specific, or just bad luck :). My 4G (LTE) will randomly disconnect a few times a day. By simply opening quick preferences and turning mobile data on and then off the issue is resolved, and I can connect again. Is anyone else having this issue?

hboot 2.22

8/8/14 nightly

s-off

supercid

AT&T (US)

I installed to a clean device (wiped everything except internal storage)

this issue has been present in nightlies before this as well, and in those instances I was on hboot 2.19 also with a clean install of the ROM after formatting everything.

EDIT: looks like it was the APN, cause as soon as i changed that to one i randomly found on google, i got an "LTE" icon instead of a "+" (I tried finding what each of those mean, but to no avail... until just a moment ago, i thought the "+" was for LTE) Will run with this for now, and hopefully my data connection doesn't drop as much
[HTC One Mini] dipje:
unlocking the bootloader doesn't void the warrenty. There are laws which protects it from that. But a lot of service centers or cell-carrier-repair-departments will try to f*ck you over and come with a bill.

My m4 was unlocked, rooted and custom rom and it got picked up for the cracks in the shell, got repaired free of charge. Not a guarantee for your situation of course, but just to say that unlocking doesn't automatically mean 'no repairs'.. but they might try to do it.
[HTC One Mini] scoobdriver:
Many thanks.. Do you have any links to the law around protection around boot loaders.
[HTC One Mini] dipje:
That here (with me) in the EU a device sold (in these case mobile phones) are in the category who are expected to last 3 years. (or 2 these days, but I believe 3), and are then required by law to have warranty on the hardware. Nothing you can do by means of the developer can remove that. Whatever warning and text they say on the htcdev unlock site, local law comes first :).

They will say of course that they don't give support on it (no help, do it yourself) and that whatever you flash on your phone is your doing (they won't help you with bugs in CM11 or something) but if they give you the option to 'unlock' something _that alone_ will not break any warranty. If they don't want to give warranty on it, don't let us do it.

Now, if something breaks because what we flash on it (which may or may not be the case here with the CM11-status) they might say that the device is broken by your own fault because what you flashed on it. But not because of the unlocking.

So that brings me back: Just unlocking shouldn't void your warranty, but it's different per country and I'm not talking about flashing CM11 afterwards :). How it should be, and how it worked out for me doesn't tell you the same happens with you. Primarily companies in between you and HTC (service centers, device carriers, the story that sold you the device) will try and something different.
[HTC One Mini] scoobdriver:
Many Thanks.. I'm in the UK .. Anyone have any experience .. ?>