yashsingh1/xdaforums huggingface dataset:
[HTC One Mini] dipje:
I never dare say if UK is EU or not, I have the feeling it changes each month :P.

I have to add something I realize now though: The law here in the EU states that after 6 months, the manufacturer still has the obligation to have provided 'a solid product' (loosely translated), and how long that solid product has to last is determined in different categories. This is _independant_ of any warranty the manufacturer says the product has.

The first 6 months, the 'place the consumer got the product from' is responsible for this (i.e., the store).

After 6 months, it can be whatever the story/manufacturer wants it to be, but at least the manufacturer _has to_.

_But_, it's up to the consumer (you) to prove that the manufacturer is at fault and the product is faulty.

So in this case (a rom you flashed caused damage) I'm guessing you're having a hard time proving that it's not your fault :S.

But my original intent / statement still stands: The cracks and other hardware faults ('suddenly stopping') _are_ repaired cost free when it's clear it's HTC fault. I went to HTC directly and got it returned within 7 days repaired. So unlocking the bootloader doesn't mean 'no warranty anymore', that is not how it works (even if they try to make you believe that).

Destroying your phone (like throwing it in the fire, breaking it by letting it fall, or flashing something that breaks it) is not HTC's fault so that will be difficult. But you can at least try and play dumb, unlocking doesn't have to mean no warranty.

But there are people who are reporting getting a bill because 'custom software was found'. This is mostly the Vodafone repair service for instance who doesn't even let HTC handle it.
[HTC One Mini] AnGrY sCoTsMaN:
Read this post I put up a few months back http://xdaforums.com/showthread.php?t=2666925

However..

Unfortunately*EU laws that protect users who unlock their bootloader or root their phone, do not apply in the United Kingdom, as their laws overrule these EU rules, even though we're in the EU. But I would certainly use the EU law thing... See how ya get on.
[HTC One Mini] milchmaennchen:
Hi,

not sure if this is CM related but without knowingly changing any settings I cannot use my m4 as USB storage anymore (USB debugging info shows in notification, but the device is not recognized as USB mass storage by neither PC or Mac).

Is there any workaround? Ty
[HTC One Mini] corgan1001:
I ran into this issue once before, had to plug it in and turn debugging off/on again. Seemed to fix it right up.
[HTC One Mini] milchmaennchen:
Ty, [MENTION=4401622]corgan1001[/MENTION]. I tried that already but it didn't work for me.
[HTC One Mini] stephendt0:
Is the overheating fix merged into nightlies yet? It scares me to think you can damage your hardware permanently with this ROM :mad:
[HTC One Mini] didierk:
Has anyone problems using manual network selection? Automatic mode works without problems, but being near a border manual selection would be great.

As i start the manaual search, the progress circle rotates but after some seconds the error "Error during network search" appears.

Anyone with the same problems? I'm on 20140810 nightly.

Logcat

Thanks alot!

Greetings

Didier
[HTC One Mini] milchmaennchen:
Just tried and got the same error. I'm on 20140818.
[HTC One Mini] dipje:
Since some people had the problem within weeks, but others used to phone fine for 5 to 6 months or more before the problems popped out, you never know, testing it seems a bit impossible. You only know for sure if there aren't any new reports after a few years or so :P
[HTC One Mini] thecos77:
So what does that mean? CM development for the mini is dead? No one will be able to figure out the glitch that causes the overheating? I don't think so.
[HTC One Mini] BENETNATH:
open question

as we have now a official 4.4 rom, even if it's the worst way, could we just work with PREBUILT_KERNEL, as it was feasible for 4.0 ?

headers have to be added, but i'm not sure that the build process still allows it ..
[HTC One Mini] u-ra:
I'm getting my m4 back tomorrow, so development is not dead. I really hope to figure this **** out soon.
[HTC One Mini] gomezr:
:good:

Maintenance is hard work! Thanks for it! The HTC One Mini is a great phone, i love it. Let it life long!
[HTC One Mini] BENETNATH:
That s great news. U-ra, using prebuilt kernel could help ?
[HTC One Mini] milchmaennchen:
Glad to hear that. Keep up the good work.
[HTC One Mini] u-ra:
Fixed.
[HTC One Mini] EdiBese:
the other one cant hear me

Hello

Since i have CM 11 i got a problem during calling. The other one cant hear me well, i am too silent for him althoug i shout in the microphone. I dont know what the problem is. I had not this problem with the stock rom. I alread flashed the phone completely new with the newest nightly but same problem remains..
[HTC One Mini] didierk:
Hey folks

I just noticed the M11 snapshot on cmxlog :)

Means the overheating issues are finally patched? If not, is it still necessary to flash the thermald zip with an recent nightly version of cm11?

Greetings

Didier
[HTC One Mini] h8rift:
That's because u-ra is a boss. He went and had his phone repaired and fixed the things. Give the man some props! :D
[HTC One Mini] pure.by:
I follow the project rather tight, but can't remember any information coming by about overheating issue getting fixed. First post in the thread contradicts that, too. Seems to me that a fix like that would deserve an announcement.

Moreover, there has been at least one report of dead M4 with flashed thermald config, so it's not certain thermald fixes anything at all.

On the other hand, we have another project maintainer saying this:

I hope this is true. Would like to know what this information is based on, though, and whether it is certain regarding the deadly overheats.
[HTC One Mini] stoffel010170:
MPEG2 hardware acceleration support

Hi,

I have a problem by playing MPG2 video/streams on my M4 under XBMC. It seems that Android/Cyanogenmod doesn't support hardware acceleration for MPEG2 (see also http://forum.xbmc.org/showthread.php?tid=202623). Is it possible to add hardware acceleration support for MPEG2?

Thanks in advancs.
[HTC One Mini] pure.by:
[MENTION=2703964]h8rift[/MENTION], so what is the official status of overheat bug?

I guess community could use some clarification after dozens of bricked devices.
[HTC One Mini] didierk:
Hi all

I noticed that there was a change on thermald.conf on sept 25 by u-ra, but the change does not reflect the same changes as the thermald.conf in the patch file.

Does anyone know if it is still recommended to flash the thermald patch after installing an current cm11 nightly?

thanks & greetings

Didier
[HTC One Mini] u-ra:
No need to flash the thermald zip, it has been been integrated.
[HTC One Mini] jollywhitefoot:
Have there been any new reports of bricking?
[HTC One Mini] pure.by:
At least 1 report that I know of. Bricked device with manually flashed thermald config about a month ago. You can find it in this thread, if I'm not mistaken.
[HTC One Mini] BENETNATH:
good news :

HTC One mini - Android 5.0 Lollipop update, schedule TBA

http://www.gsmarena.com/htc_one_one_m8_one_mini_and_mini_2_to_get_android_50_lollipop-news-9947.php
[HTC One Mini] EnricoDNY:
Can anyone tell me if the latest CM11 nightly is stable enough to flash please?

any bugs?
[HTC One Mini] mattplo:
Ive flashed the latest Nightly (cm-11-20141104-NIGHTLY-m4.zip) from 2014-11-04 23:56:30.

Was on Stock 4.2.2. I just bought this phone second hand. I Unlocked the Boot loader via HTCDEV. That went very well and easy peasy. Second , I installed the latest TWRP (openrecovery-twrp-2.8.1.0-m4.img) from 2014-10-22 21:56:02.

I used fastboot flash recovery recoveryfilename.img method to install it. Again, easy peasy. Then I used RumRunners S-OFF. After having unlocked the bootloader, Installed custom recovery(twrp), S-Offing(RumRunner), I dl'ed the latest nightly from Cyanogenmods sight for my device and flashed. the ROM and the Gapps at the same time. Took a little while to boot but nothing unusual.

Takeaway: Its smooth. Very smooth. No bootloops as of yet. GPS works, Wifi works, Data seems to work. The kernel is basic. No ocing :/. Off to a good start. No Thermal issues at all. No unusual heat. I havnt applied any patches.

The bad: Microphone needs to be very close to yuor mouth when initiating "Ok Google". It works, as long as you put it close to your mouth. Headset problems. Microphones does seem to work in built in headsets. However You wont the caller. Speakers dont work. Normal non-headset calling works well.

Under ART, things seemed to be unstable. I switched back to Dalvik. Things seem fine now. As for battery life. I have not out it through its passes. Nothing seems out of the ordinary. Overall Good build. Howerver headset issues need to be fixed.
[HTC One Mini] xXminiWHOOPERxX:
Any CM12 love?
[HTC One Mini] u-ra:
Yes.
[HTC One Mini] xXminiWHOOPERxX:
Can't wait!!
[HTC One Mini] malikou:
can't wait too
[HTC One Mini] png666:
Did the same as above, except I used the latest nightly from today 29/11/2014

I am not a pro, nor a total noob, but I havent found any issues yet. :good:

No exploding, no thermal issues, no bootloops, stable connection - as far as I can notice - in both mobile and wifi networks. However, I did find a magical unicorn eating cornflakes with whiskey. I don't know if that's a kernel thing, or the ROM.

There's a hard time switching between acces points. Again, I don't know if it's related to the ROM or just my bad configuration of those acces points. Doesn't harm to tell anyway. Maybe someone with actual knowhow could check as well.

You want extra info?

Dev unlocked, rooted.

s-off with rumrunner. (revone didnt work, I think it's an hboot issue in my case) S-offing is necessary!! I made that mistake by updating with S-ON; bricked the thing.

updated from stock sense rom I found on some website, to CM11.

SuperSU updated only in 'normal mode' not the recommended modus operandi for htc's, heck I didn't even try through recovery.
[HTC One Mini] png666:
Found some camera issues: the in-app camera is upside down. Regular cam is normal but in whatsapp and other messaging apps, it flips 180 degrees after filming/pics with the frontcam. Battery life is normal: about 24-27 hours on a full battery with normal use.

No other issues to report thus far.
[HTC One Mini] mattplo:
Whoops sorry.

---------- Post added at 07:52 PM ---------- Previous post was at 07:47 PM ----------

Google Camera(Play Store) doesn't seem to be affected by this. Nor does Instagram or Google+. One of the first things I do when I install is ditch the native camera app so I'll admit I've never seen this issue for this phone. All the apps I have installed that I've mentioned are not affected. Oh nor is hangouts. That's really all I have to test with (that incorporate a cam)

So can't verify.
[HTC One Mini] Everest_:
Are there still overheating problems with this ROM? Or is it safe to use :)

Edit: I'm going to flash this ROM right now :)
[HTC One Mini] pure.by:
Just some chronology.

1. Summer 2014. Overheating occurred on very large scale. Reports of bricked devices were coming in hot (pun intended) both for CM itself and CM-based ROMs. CM development stopped.

2. Autumn 2014. A thermald config patch allegedly solving the issue was posted in the thread.

3. A couple brick-reports (related tot overheating) came in, at least one of which occurred on explicitly confirmed thermald-patched (!) configuration.

4. No more brick reports came in. No forum posts or development either.

5. By the absence of forum activity (and hence, no fresh brick reports either) thermald patch was implicitly assumed to have solved the issue, and integrated directly into CM code. Temporary safety warning put in the OP after a lot of struggle was removed without a notice.

6. Winter. Still no forum activity, no fresh brick reports and no active development. *

Edit: My bad, I've missed M11 & M12 snapshots due to the lack of release notes both on XDA and CM forums. So development seems to be back once again.

To sum up: there has been no explicit fix which worked universally. But over last several months, there have been no brick reports either.

Whether this is the result of general absence of forum activity or an issue that has been resolved, is up to you. There have been no official statements.
[HTC One Mini] Everest_:
Thank you, i'm flashing this ROM right now :)

And if there's no active development how come there are still new nightly's everyday?
[HTC One Mini] pure.by:
This is a good question, and a mystery to me as well, but in general, there is no human factor behind those nightlies. Don't ask me how it's possible.

But I also see I was wrong about halted development. There are 2 fresh snapshots available which I have missed, because they were released without a note -- I follow both the official CM M4 forum and this XDA thread. So development is now resumed since a couple of months , which is good news.
[HTC One Mini] KennyHO:
HTC BlinkFeed

hi ... can someone help with App HTC BlinkFeed? I would like to install it.

thx
[HTC One Mini] sianyde:
CM 11 cm-11-20150118-NIGHTLY-m4.zip Tower "rejecting" my LTE setting?

First I'd like to begin by thanking the devs, especially h89rift and u-ra, for this ROM; its performed 99% flawlessly on my phone and is my daily driver. Hell, its practically perfect b/c I never had LTE to miss in the first place :)

HTC One Mini (m4) had AT&T stock software (Android 4.?) with Sense 5. I installed the latest stable Cyanogen 10.2 build using TWRP. I decided to use a different phone so I didn't try anything after installing 10.2. So I RUU flashed "RUU_M4_UL_K44_SENSE60_MR_Cingular_US_4.13.502.3_R adio_1.29.40g.00.19_10.32.40.1115L_release_385202_ signed_with_hboot" (which is AT&T Stock Android 4.4.2). I also installed an AT&T Sense 6 update and relocked the bootloader.

My wife previously had this phone on her AT&T account, always on stock software, and never had any issues with the phone.

Later, I decided to use the Mini. So I unlocked the bootloader again (which wipes all user data), and installed TWRP recovery again. I did a factory reset from TWRP, and cleared the cache and dalvik. I installed Cyanogen cm-11-20150111-NIGHTLY-m4. I wiped the cache and dalvik again for good measure. I then installed the google apps for KitKat. The install went perfectly and I have not had ANY issues with the ROM at all, save one. I didn't have a SIM in the phone when I installed CM. I received one 3 days later.

There is an AT&T LTE tower right off the exit ramp where I work. I attempted to toggle on LTE using the quick settings in the status bar. The toggle remains on, but I cannot receive LTE signal. In Settings -> Mobile networks, I am unable to select "LTE (preferred)" unless I first put the phone in airplane mode. LTE will remain checked, but I observed when I am near that LTE tower, the setting reverts to "3G". If I enter phone setup via *#*#4636*#*#, i cannot make any setting other than WCDMA preferred unless I turn off the radio. Again, when i get near the tower, the setting will revert to WCDMA only. THe Advance Signal Status app shows n/a for everything under LTE (4G) Signal Info. It's almost as if the LTE-enabled tower is "kicking me off" the LTE setting b/c my LTE/WCDMA setting will hold on a non-LTE tower.

I'm on an LTE-enabled plan. Another stock device on my plan can receive LTE. I've set up my APN to the letter per AT&T's website. I even added fota like the stock rom had (even tho i'll never be doing fota updates w/ a custom ROM).

I've read on the net it may be a bad sim card, but i had the same problem on an LG Nitro running cm 11 latest nightly (brand new LTE enabled sim. I COULD set LTE without issue on that phone, but never had an LTE connection.) I've also tried wiping everything except the internal SD storage and reinstalling the ROM with the sim card in the phone.
[HTC One Mini] u-ra:
I've seen this happen a few times, but couldn't figure out why. It's even worse with CM12. Radio libs on m4 are really screwy like that. Check if toggling airplane mode makes it better. Reading comprehension fail.
[HTC One Mini] sianyde:
Thanks

Thanks for the fast reply, u-ra. No LTE is a small price to pay anyway. Never had it to miss it, and I would only have it when working or travelling anyway b/c I don't live in an LTE covered area. So far on the unofficial CM-12 I can at least select LTE (recommended). What I get in the status bar is what appears to be a full signal with "!" embossed in it, and the LTE/GSM setting will hold in the phone diagnostic.

I know Advanced Signal Status isn't ur app, and you don't do dev work on the p930 (AFAIK) but I was curious about one thing, if you have any insight and feel like giving it. On my Nitro, with no SIM card in it, signal status reports 0% signal for LTE when I enable it, rather than n/a. The m4 just shows n/a. My guess is signal status is getting its information from what the os reports, not from the radio itself, so I wouldn't have to be concerned about something wrong with the phone's LTE radio?

If I flash a backup of the RUU ROM, LTE doesn't work either. When I have time to deal with a totally wiped phone, I'm going to try relocking, erasing everything, and RUU flashing the stock ROM again and see if it eliminates the problem. If that doesn't work, then I at least know I have to look elsewhere other than the os.
[HTC One Mini] agentsmith988:
Interested to see what results you get flashing the stock RUU on a locked bootloader.

I have this exact same issue it's been driving me nuts. I can get LTE/GSM to finally stick after toggling the radio and then can select LTE (preferred) but it always resets back to WCDMA Preferred and 3G eventually. Extremely frustrating for such a great ROM.
[HTC One Mini] omgdwong:
Bricked

Just purchased this phone used and having mount errors.

Currently on hboot 2.22, twrp 2.8.1.1, unlocked s-on. Unable to flash roms and kernels, anyone able to assist?
[HTC One Mini] Explodroid:
Error 7

Hello I have my HTC One Mini on 4.4.2 hboot 2.22 S-ON rooted and unlocked. Unfortunately when i try to flash the rom i get error 7 in TWRP (2.8.4.0) so I can't even flash the ROM.

Anyone knows a solution?
[HTC One Mini] AhmedTaburov:
My bottom speaker wasn't working/responding so I installed Beats Audio app from this topic:

http://xdaforums.com/showthread.php?t=2713542

It works now!
[HTC One Mini] erral:
Hi,

Thank you for your work! But I have an issue to report.

I've tried to install the 20150209 and 20150216 nightlies and I have the same problem with both of them. About 90% of the time when i try to drag down the notification bar or the quick settings bar something seems to crash badly, the status bar disappears for a second and then it just takes me to the lock screen. I've tried to play around by changing status bar and notification drawer setting. Nothing seems to help. Also, it crashes and jumps to the lock screen whenever I try to change a setting in those categories. Sadly, this problem effectively renders the ROM unusable for me.

I'm positive that I flashed the ROM correctly with all necessary steps. If I can provide any more info, I will gladly do so.

EDIT

Wiped everything again, even formatted data and flashed the 20150216 nightly again. The issue seems to be gone this time around. Strange, because I'm absolutely sure I've done everything right previously. I'll keep you informed if anything comes up again :)
[HTC One Mini] HelioDS07:
Battery Drain since some days

Hi guys,

I experianced a drastic battery drain since some days.

It took me a while to figure it out.

Now it looks like it is the "Google Play Services"-App. It does wake up the device regularly and avoids deep sleep of the device.

It seems it is not the first time this problem occured with CM based roms.

I used the fix on this link.

http://xdaforums.com/oneplus-one/general/guide-google-play-services-battery-t2832525

Here is described how you can check if you are affected and an additional fix.

https://forums.oneplus.net/threads/...son-heres-the-fix.284095/page-4#post-10355312

Regards
[HTC One Mini] HelioDS07:
Battery Drain workaround not working any more

Hi,

has anyone also battery drain issues with the google play services on this ROM.

How did you fix them?

The fix described above does not work any more :(

I am using cm-11-20141112-SNAPSHOT-M12-m4.

THX
[HTC One Mini] pure.by:
Why would you even use this abandoned, outdated and potentially unsafe ROM in 2016?

Sent from Tapatalk
[HTC One Mini] MikeyNash:
Working so slow on HTC that I crash my phone!
[HTC One Mini] shahab khan:
How do i root it perhaps i have htc one remix by verizon????
[HTC One Mini] one_million:
Latest nightly/snapshot still have headset issue on some apk (fb messenger/skype). When calling -can't hear nothing in wired headset.
[HTC One Mini] pure.by:
This ROM is a gimmick and it never worked to begin with. All it did was cook up couple dozen M4's.

Why would you even use it when CM12 is available?
[HTC One Mini] one_million:
CM11 is an official version. CM12 not. CM12 unofficial got much more bugs than CM11 official. And got the same one bug with headset,i can't heare nothing when calling messenger or skype. This apks are my hands....:rolleyes:
[HTC One Mini] pure.by:
Really? CM11 is more stable than CM12 in your opinion?

From what I remember, unofficial CM12 was waaay better maintained than the 'official' CM11. Honestly, CM11 could not even handle audio playback properly, with all kinds of pops and clicks and unpredictable volume levels in every app. Not to forget the SIM-card getting deactivated every other day at random times.

I have honestly no idea how a ROM as buggy, raw and dangerous as CM11 could have made it to the "official stable" unless it was done under false pretense. After the ROM made it to the front page and dev got his perks for being an 'official CM maintainer' his interest in maintaining the project vanished suspiciously fast.

Not to forget how many phones CM11 had destroyed by overheating and not a single sh*t given by the dev about that. Moreover, refusing to put a warning in the OP and putting all the blame on users for not reading entire 160+ forum pages before flashing.

And bluetooth audio works on CM11?

That would really surprise me since CM11 couldn't even handle the phone's own speakers, while bluetooth audio was an issue with all custom ROMs for M4, iirc.

Also, it's worth mentioning that the development for CM12 was dropped late 2015, while development for CM11 was dropped around mid-2014 (with only a couple thermal patches added later that year).
[HTC One Mini] one_million:
Thx for your reply. In my opinion cm11 and cm12 for htc m4 is crap. Any way,yesterday I came back to stock rom,relocked and so on....phone is much slower but I can use now apk that I need without any problems. Offten I am changing my phones,and everytime when I get new one,always use cyanogenmod,coz it is the best for my :cool:
[HTC One Mini] pure.by:
You're welcome and yeah, CM all the way! But M4 is unsupported so I guess stock is indeed the best choice.

I was quiet enjoying CM12 for a week though, before my M4 died second time. Just happened out of the blue when I picked the phone up to dial a number. No overheating or anything, so don't know if the ROM is to blame or whether it happened "naturally".

Didn't have any issues with the ROM though, have not discovered any major bugs either and was running as smooth as 1GB RAM device can get.

First time was on CM11 due to overheating bug it had; dozens other phones were fried too.
[HTC One Mini] ZiemlichUndead:
For me, there is no quality option in the Youtube app.

Anyone else with this bug?
[HTC One Mini] pure.by:
Try CM 12, it's better in every way and was magically updated recently.
[HTC One Mini] ZiemlichUndead:
I did. But the cm12 kernel does not support swap. But i really need swap. For cm11 there are swap compatible custom kernels but not for cm12

Any idea?

At the moment i am on stock rom cause it is swap compatible but i dont really like it...

PS: Sry for bad english :P
[HTC One Mini] pure.by:
Stock and CM12 are the only ROMs that work.
[HTC One Mini] ZiemlichUndead:
But swap doesnt work for cm12 and again: I need swap!