CyanogenMod 11.0 for HTC One Mini - m4

[pure.by]

Have there been any new reports of bricking?

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.

Sent from my HTC One mini using Tapatalk

 

[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

 

[EnricoDNY]

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

Can anyone tell me if the latest CM11 nightly is stable enough to flash please?

any bugs?

 

[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.

 

[xXminiWHOOPERxX]

Any CM12 love?

 

[u-ra]

Any CM12 love?

Yes.

 

[xXminiWHOOPERxX]

Yes.

Can't wait!!

 

[malikou]

Can't wait!!

can't wait too

 

[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.

 

[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.

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.

 

[mattplo]

Whoops sorry.

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

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.

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.

 

[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

 

[pure.by]

Are there still overheating problems with this ROM? Or is it safe to use

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.

 

[Everest_]

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 came in, 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.

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

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.

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?

 

[pure.by]

And if there's no active development how come there are still new nightly's everyday?

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.

 

[KennyHO]

HTC BlinkFeed

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

 

[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.

 

[u-ra]

stuff

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.

 

[sianyde]

Thanks

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.

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.

 

[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.