yashsingh1/xdaforums huggingface dataset:
[HTC One Mini 2] stkl:
TL;DR

At the moment LOS 14.1 receives regular security updates and with that is way more secure than many newer devices running outdated stock ROMs.

Nevertheless the One Mini 2 pretty much reached EOL (and never had a large community), so you should not expect any major jumps for this devce.

----

LOS 14.1 still receives patches from Android 7.1 and thus recent builds show the same security patch level. Updates are published monthly, but there is a certain delay for the changes being ported to LOS. Have been some days in the past, currently it's >2 months for 14.1

However the HTC MSM8974 Kernel (which the One Mini 2 uses) is not actively developed any more and thus receives only a bare minimum, so a couple of Android security patches that require Kernel adjustments may not be implmented.

Also keep in mind that the Android upstream only affects the Android part. Pure LOS components might be a different story and are likely to be patched less frequently.

As long as Android 7.1 receives security updates and a developer is willing to port the changes to LineageOS.

The first part is probably another 1-2 years from now (you might check the latest patches here: https://source.android.com/security/bulletin/). Some official LOS projects might also last that long, but that's hard to tell.

If anyone volunteers to build and maintain such version.... So most likely No.

I still have regular LOS 14.1 builds for the security patches, but no particular interest in porting a newer OS version (moved to Pixel 2 a year ago). [MENTION=7570463]nightcore500[/MENTION] has already put a lot of work in LOS 15 (don't know the actual state), but it is obviously not just raising a verison number and really hard for a single dev.
[HTC One Mini 2] ehsan247:
is this build dead ?

or will we get any update ?

waiting for Android Oreo or Pie :(
[HTC One Mini 2] stkl:
You were right, my sources have been pulled 2 before the last commit. I'm now on my custom build and radio is fine again.

Running well, userdebug build. Now I can start working on my OTG issues.
[HTC One Mini 2] nightcore500:
V0.2 is now released :)

LineageOS 14.1 is now ready to be used as a daily driver. :good:

Release V0.2 (11.05.2017)

switch to userdebug

switch to enforcing mode

fix NFC

switch to Jelly Browser

switch to Moto 8226 Thermal Engine

Update Qualcomm MSM Interface, Radio Interface Layer, GPS blobs

Update Camera & Sensor blobs

Update Widevine DRM blobs

Update graphics blobs

remove unused proprietary files

selinux: fix some denials

Kernel: re-add DT2W

Kernel: re-add our RT5506 changes

Kernel: fix SDCard driver
[HTC One Mini 2] Jonzethan:
Here you go. Hope it helps!
[HTC One Mini 2] nightcore500:
It seems that your device have a different touchscreen installed. Normally, our memul has a synaptics touchscreen. However the kernel from your current rom initializes a himax driver. Apparently it is a himax 8528 touchscreen.

Our kernel has no himax driver at the moment. I will activate this driver in our kernel config right now and run a recompile. The hotfix will then follow at midday.

Btw. DT2W will not work with your device because we do this directly in our synaptics driver. Sorry :/
[HTC One Mini 2] tryllz:
Better in every way than the alpha, performance is better, not laggy, camera, audio at their best, for signal I am yet to make a call and check..

How ever I ran into this issue again, same as in CM13 but was not there in alpha, where NFC keeps coming on and going off, not sure if its because I open the NFC window or it happens in the background. This is what I have observed that if I open the NFC window after a while, it is disabled, but if I open it again right after opening it once, it remains enabled. I AM ONLY TLKING ABOUT OPENING THE NFC WINDOW NOT ENABLING NFC, I DON'T USE NFC BUT IT REMAINS ENABLED AND CAUSES BATTERY DRAIN, THIS WAS ALSO THE SAME IN CM13..

I have attached screenshots and demsg (as per instructions from the post) as well.

Also not sure if anybody else has this, when I connect the device to PC, I HAVE TO GO IN THIS SEQUENCE to view both internal and external memory to show in windows explorer, the sequence being tap on PTP, then tap on MTP otherwise it wont show any memory, for me it has to be this sequence, if I tap directly on MTP the first time it doesnt work, it has to be PTP then MTP.

Thanks..
[HTC One Mini 2] nightcore500:
Looks as if your NFC is constantly activating and deactivating. I need a logcat for this.

EDIT:

Appears here all the time. After 10 trys the driver seems to run into a timeout.

Do you know if your NFC has ever worked? Looks like a hardware problem. The connection to the NFC chip does not seem to be in order.

In our alpha version, the initialization was not done at all, so your NFC was really deactivated or better called completely ignored.

You could try to prevent the initialization. Try to remove the libnfc-nxp.conf under /system/etc/

EDIT2:

I know about the problem. I'll take a look at the days.
[HTC One Mini 2] tryllz:
AND FINALLY THE DREADED ONE, THE AWAKE ISSUE....Its caught up again, and NO its not because the device screen is on and charging, the charging only started when i connected the device to pc which I about 10 minutes ago when I took the logcat, I did not use the device for about an hour, as far as I know it has to wakelock in android system but did not find a solution and I don't even have any app installed, its all stock..

Logcat attached...

THANKS MAN...
[HTC One Mini 2] tryllz:
I did a wipe from TWRP and reflashed and received this error :

Patching system unconditionally

E:\Unknown command [log]

E:\Unknown command [log]

then everything proceeded normally and device rebooted with OS installed..
[HTC One Mini 2] Finusfix:
Hey, can you please write less in caps? It's like you're shouting at us or would be annoyed. :)
[HTC One Mini 2] nightcore500:
Its normal on charging. But without this should not look like this. Have you installed any apps which maybe prevent the sleep?

I was just traveling for 3 hours. I could not observe this problem on my device. As soon as I switch off my device it goes into the deep sleep and wake soccasionally briefly for whatsapp, telegram and my email service.

Maybe it could be related to your NFC problem?

Could you please restart your device? Please do not charge it until tonight. Restart your phone again tonight and send me your last_kmsg. You can find it under /proc/.

No worry. That's normal. ;)
[HTC One Mini 2] tryllz:
Thanks..

I recall a similar issue from Stock ROM, there I turned off open Wifi discovery in Wifi settings and that solved the problem, here I have turned off the same and I'm testing it now.

I have restarted and will not charge and will generate a kmsg and upload it here.

No apps were installed, all stock..

Thanks again..
[HTC One Mini 2] nightcore500:
I have now added the himax hotfix. That should solve your problem.

[MENTION=535343]all[/MENTION] If your touchscreen is working you don't need to flash this hotfix.
[HTC One Mini 2] tryllz:
I have taken kmsg as if I go to sleep possibly the battery could run out and I might have to recharge it to boot it up, kmsg was taken after a restart.
[HTC One Mini 2] nightcore500:
This is not the last_kmsg or at least not the complete but I think what was logged here depends on your problem. Android still tries to activate your NFC. Because the NFC driver runs into a timeout after 10 attempts, the process starts from the beginning. And that again and again.

Have you already tested if your NFC problem disappears when you delete the libnfc-nxp.conf or at least rename? To your previous question, removing the config should only concern NFC.

Currently i don't have an another solution because it is obviously a hardware problem. Just try it. Remove or rename the file, reboot the phone and look again in your kmsg whether the following lines still appears:

c0 26295 [NFC] pn544_dev_write: writing 4 bytes

c0 26295 qup_i2c f9928000.i2c: QUP: I2C status flags :0xc1300c8, irq:132

c0 26295 qup_i2c f9928000.i2c: I2C slave addr:0x28 not connected

c0 6 qup_i2c f9928000.i2c: QUP: I2C status flags :0xc1300c8, irq:132

c0 26295 qup_i2c f9928000.i2c: I2C slave addr:0x28 not connected

c0 26295 qup_i2c f9928000.i2c: QUP: I2C status flags :0xc1300c8, irq:132

c0 26295 qup_i2c f9928000.i2c: I2C slave addr:0x28 not connected

c0 6 qup_i2c f9928000.i2c: QUP: I2C status flags :0xc1300c8, irq:132

c0 26295 qup_i2c f9928000.i2c: I2C slave addr:0x28 not connected

c0 6 qup_i2c f9928000.i2c: QUP: I2C status flags :0xc1300c8, irq:132

c0 26295 qup_i2c f9928000.i2c: I2C slave addr:0x28 not connected

c0 26295 qup_i2c f9928000.i2c: QUP: I2C status flags :0xc1300c8, irq:132

c0 26295 qup_i2c f9928000.i2c: I2C slave addr:0x28 not connected

c0 26295 qup_i2c f9928000.i2c: QUP: I2C status flags :0xc1300c8, irq:132

c0 26295 qup_i2c f9928000.i2c: I2C slave addr:0x28 not connected

c0 6 qup_i2c f9928000.i2c: QUP: I2C status flags :0xc1300c8, irq:132

c0 26295 qup_i2c f9928000.i2c: I2C slave addr:0x28 not connected

c0 477 qup_i2c f9928000.i2c: QUP: I2C status flags :0xc1300c8, irq:132

c0 26295 qup_i2c f9928000.i2c: I2C slave addr:0x28 not connected

c0 26295 qup_i2c f9928000.i2c: QUP: I2C status flags :0xc1300c8, irq:132

c0 26295 qup_i2c f9928000.i2c: I2C slave addr:0x28 not connected

c0 26295 [NFC] [Err] pn544_TxData: Error: retry over 10

c0 26295 [NFC] [Err] pn544_dev_write : i2c_master_send returned -5

Btw. when you use adb you can also follow the kmsg live with "adb root" and then "adb shell cat /proc/kmsg". (For this you have to turn on the root access for adb in the developer settings.)
[HTC One Mini 2] tryllz:
How do I locate the file libnfc-nxp.conf what is the path to it, I have used TWRP file manager but not able to see the file anywhere in /system/etc or proc folder...
[HTC One Mini 2] nightcore500:
If you use the TWRP filemanager you must mount the system partition first. You find the libfnc-nxp.conf under /system/etc
[HTC One Mini 2] tryllz:
If I use Mount in TWRP then nothing happens, it doe snot show me anything in PC and nothing in TWRP either, just shows this "Make sure to remove your device safely before unmounting"..

I recall in TWRP 2.8.5.0 I could mount without the need for a PC..

---------- Post added at 11:39 PM ---------- Previous post was at 10:45 PM ----------

Managed to get it done, renamed file and NFC remains disabled, turned off screen, will check after some time to know whether awake is active...
[HTC One Mini 2] DerLages:
Following the development since CM 12 and switched to the LOS 14.1 now.

It is running really nicely so far, good job, only experiencing some crashes with the stock browser (maybe ram related idk.)

Keep up!
[HTC One Mini 2] tryllz:
[MENTION=7570463]nightcore500[/MENTION]..

Thank you for your consistent support, having renamed the file, solved the issue, no more does the device remains awake and of course never needed NFC.

I used Root Explorer Pro file manager as none other method worked.

Thank You
[HTC One Mini 2] huub382:
[MENTION=7570463]nightcore500[/MENTION]:

i installed V0.2 and almost everything works perfect.

Only issue so far is the browser, who randomly crashes.

I installed Opera Mini and this one is working great.

The phone is working really fast, wifi is good, NFC works, Sound is better then before.

Thanks for this great Rom.:good:
[HTC One Mini 2] multiwirth:
I think the device is dead.

To be honest, it wasn´t ever alive.

Android oreo or pie won´t run great with the given specs anyways.
[HTC One Mini 2] wadderlou:
I discovered builds of Lineage OS 15.0 , 15.1 and 16.0 on a Russian website.

lineage-os.ru/?d=htc-one-mini-2

Maybe it´s worth a try.
[HTC One Mini 2] serban57:
Fake. There are exactly the same files: en.miui.com/thread-3223507-1-1.html
[HTC One Mini 2] multiwirth:
It is even impossible to download these files.

The file hoster´s download speed is horrible slow if you don´t buy premium.

In the end the download canceled due to an server issue and I gave up.
[HTC One Mini 2] Silver-HaOS:
Hi. I'm download LineageOS-16 file and reload on Mega - https://mega.nz/#!gDhDAQBT!bilmbb1Orzs-0a63B9sKBJRoVprStPsmB9PtRMtw9Rg
[HTC One Mini 2] userx404:
How about your imressions?
[HTC One Mini 2] Silver-HaOS:
I did not install this firmware. I would like to know the opinion of a specialist.
[HTC One Mini 2] userx404:
I'm not a specialist but looking in package's metadata file makes me doubt it's for memul.

post-build=xiaomi/mido/mido:6.0.1/MMB29M/V8.2.4.0.MCFMIDL:user/release-keys
[HTC One Mini 2] rattengift:
[MENTION=7570463]nightcore500[/MENTION], have you tried this? How about an upgrade of your great ROM?
[HTC One Mini 2] shikulja:
del
[HTC One Mini 2] Silver-HaOS:
I'm currently using LineageOS 14.1 Release V0.8 by nightcore500.

Everything is fine, except for one thing - the quiet sound of a call melody...

I tried to edit the file "mixer_paths.xml", but did not succeed. I found the sound control of the built-in speakers in only one place:

-<path name="speaker-headset">

<path name="headphones-generic"/>

<path name="speaker"/>

<ctl value="84" name="RX3 Digital Volume"/>

<ctl value="84" name="RX4 Digital Volume"/>

<ctl value="11" name="LINEOUT1 Volume"/>

<ctl value="11" name="LINEOUT2 Volume"/>

I fixed 84 to 93, but the volume did not change.

Tell me, please, if I am mistaken.

Thank.
[HTC One Mini 2] Silver-HaOS:
Hi, Friends.

HELP!

After 1 year of using the phone, I decided to do a full cleaning and re-flash the phone with the latest version.

Everything is fine, except for one - the DT2W does not work.

/sys/android_touch/tap_to_wake - 1

I flashed with older versions: lineage-14.1-20171104_104350-UNOFFICIAL-memul and lineage-14.1-20180119-UNOFFICIAL-memul - not working.

CM13 - working, but i don't like this firmware.

What can be done?

Thanks.
[HTC One Mini 2] userx404:
[MENTION=7570463]nightcore500[/MENTION]

I wanna ask if it is possible to get an security patch/update for this rom.

Due too the fact there woudn't be a newer stable major version it would be nice if this rom could get patches.

Thank you!
[HTC One Mini 2] multiwirth:
Hey there!

It has been silent here for a long time.

I'd like to ask if there's a manifest avaiable for 14.1 to make own builds.

I got some experience by building for icosa (Nintendo Switch) and i9300/n7100 from source but unfortunately the linked repo doesn`t have a manifest (or i haven't found it?).

I'm also interested in getting deeper into and maybe try getting 16.0 up and running on memul, i have absolutely no clue about this but well there are some devs that could help me out a bit.
[HTC One Mini 2] serban18:
Apparently this guy just vanished from the internet, or goes under other name. You can check his github page.

(this is a new account and I can't post links yet, but you can easily find his github account by its username)

It's nice to see memul is still relevant.
[HTC One Mini 2] kevios12:
i actually use this rom , this devices are bevor years verry good in performance now really laggy and some apps load to long, in some reasons need force restart the Phone, try it another roms, same. Or we have a Performance Kernel? or what can i do , make this phone more smoother. Greets
[HTC One Mini 2] multiwirth:
The biggest issue here is the 1GB ram,

But my Samsung Galaxy S3 i9300 (also 1gb ram) improved in stability and performance over the years with 16.0 now.

Also the S3 neo with 1,5gb ram and the same SoC runs pretty smooth, even got official lineage 16.0 now.

I would avoid having a lot of apps installed as most of them probably run in the backround.

---------- Post added at 09:09 PM ---------- Previous post was at 09:06 PM ----------

that's pretty sad.

However i already downloaded all the sources and it seems like i have to write my own manifest then.

Maybe i can use the one for i9300 as a reference since i have 0% clue about this.

Will also have to do a lot of research for 16.0 bringup (if this will ever happen even).

But as long as lineage merges security patches into 14.1, it might be worth building 14.1 with recent patches.
[HTC One Mini 2] kevios12:
i Hope for 16.0 ... So the 14.1 in some reasons are unusable
[HTC One Mini 2] gw1024gb:
mini 2 memwl

is this v version available sir ？
[HTC One Mini 2] serban57:
Don't use this rom for memwl. That model is a Verizon only device with a little bit more ram.
[HTC One Mini 2] E_054:
Just installed this, it's really smooth! The only issue is that I'm struggling to find the right GAPPS to flash.

I'm looking into how to make my own roms at the moment so I'm interesting learning the limitations that stop this phone from being giving a newer version of linageos
[HTC One Mini 2] E_054:
I was using the ARMx64 version of GApps - make sure you use ARM, 7,1, Stock
[HTC One Mini 2] _tnt_:
Hi, I tried to flash the Zip file: lineage-14.1-20180621-UNOFFICIAL-memul.zip

But I get an "Error 7", is it possible that there is a bootloader mismatch? Or how can I solve this error?
[HTC One Mini 2] MaRtYy01:
I personally used TWRP_3.0.2-0 V0.1 12.02.2017 again from xda, from same developer as the rom, it flashed it fine with no errors. Before beginning with the proccess I made sure that the phone is on latest update of the stock rom, which was still a android 4.4 anyway.

Using the rom for 5 days and it is flawless for now. I don't use gapps(for maximal performance) and I'm getting 4-5 hours of SoT battery life with battery on ~80% health. Overall I'm very happy, the speakers still sound great even without htc's software.

I recommend using htc camera 7.30.581119 + htc gallery 9.22.668813 for best photo quality. You can get them from apkmirror and installing them as normal apps works fine.
[HTC One Mini 2] _tnt_:
Thanks for getting back to me. I solved the issue by deleting everything before the flash: Cache, Dalvic Cache, System, Data

Afterwards it worked.
[HTC One Mini 2] userx404:
For those running this ROM with gapps and encounter some lags and ANRs:

I noticed the swap partion runs full. I installed "Swapper - ROOT" from gplay. Set the swap size to >200MB and the Phone runs fast(er) again. :)
[HTC One Mini 2] Jonzethan:
Thank you very much! Works perfectly now. Can you also apply the same fix for your CM13 rom?
[HTC One Mini 2] nightcore500:
Nice to hear. However, you will have to rename the file with every update because the system partition will overwritten.

Have you installed the v0.2? In the previous release with gello I had constantly this problem.

With the new jelly browser i did not have the problem again. At least until now ^^

This is simply due to the low memory. This happens most with sites that are overloaded with advertising.

No, I think I will not deliver more updates for CM13. The development of cyanogenmod was discontinued by the developers. The team behind cyanogenmod is now working on lineageos.

In simple words, cyanogenmod just changed its name to lineageos. Since we have now arrived at lineageos 14.1 I think that it does not make sense to make another update for the outdated cyanogenmod.

Already because android 7.1 offers many improvements compared to android 6.
[HTC One Mini 2] nightcore500:
Our config/kernel source is based on the msm8974 kernel source from CM/LineageOS:

https://github.com/CyanogenMod/android_kernel_htc_msm8974

What exactly do you want to connect via OTG? just connected my mouse/keyboard. Works without problems.
[HTC One Mini 2] stkl:
As I said, HIDs (keyboard, mouse, cryptkey, ...) work fine.

I tried a USB flash drive (works on other low-power hosts) and an external µUSB camera (endoscope camera, working with another other android devices). Both high-speed devices.

Edit:

I just tried an old Canon scanner, which is still running on USB 1.1 ... It's working :)

Not that I need a scanner on my phone, but it proves that the issue is related to high speed mode.
[HTC One Mini 2] nightcore500:
Yep, just tested a usb 2.0 device. Same problem.

Do you know if the problem already occurred in the stock rom?
[HTC One Mini 2] stkl:
Sorry, I can't remember, most likely never tried (flashed CM (11?) the first week I bought the phone).

Istill have a backup of the stock ROM laying around somewhere, maybe I will try.
[HTC One Mini 2] tryllz:
I am unable to install certain stock HTC apps such as phone dialer, messaging and music, is there any alternate way install these on LOS..

For phone and message it wont install saying a same name exists, while for music it wouldn't install at all (in CM13 it installed and crashed, never worked)..
[HTC One Mini 2] multiwirth:
The first look was great.

Very fast and stable rom.

I fixed the superuser problem (activated but not working su) by downloading and flashing the offical su addon.
[HTC One Mini 2] multiwirth:
Why is "ambient display" not included?

I got it on offical LOS builds so why isn´t it included in this unoffical version?

Would be nice if you could add it :)

btw. this german/english on the picture is caused by switching the language without reboot.
[HTC One Mini 2] hahn.lelo:
Hi i have some troubles with my radio ... Sometimes my device is getting hot and trying to establish connection without success ... Will try to send you log next time it happens!

---------- Post added at 08:19 AM ---------- Previous post was at 08:14 AM ----------

I had similar problems with some version of cm13 before too ...
[HTC One Mini 2] ExB:
Just installed on my wife's Mini 2 last night (full wipe, TWRP 3.0.2.0), so far seems good, much smoother than CM13. However, seeing the same problem as with CM13 on her phone, as the system is randomly asking to select a SIM card.. Did a quick search and couldn't find real fixes, anyone else with this problem or is it just me?
[HTC One Mini 2] ElektroDancer:
[MENTION=7570463]nightcore500[/MENTION]

I tested the v0.2 (not hotfix) over the last weekend. Now, the WLAN with 2 AP and one SSID at the same time are working on my phone. :good:

There are still 2 more Problems:

I have no mobile service (baseband: 1.101.1102.19.1017_10.26.4149.00L) from time to time in different places, where i had a signal before and my touchscreen is sometimes freezing if I want to unlock it. But when i try to unlock few minutes later, it workes.
[HTC One Mini 2] error274:
I installed v2.0 yesterday - works great except one big issue :^)

Working:

-Radio

-32 GB Micro SD

-Camera

-OTG

Issues:

-The Mobile Data connection does not work. When I activate it, for a moment an "H+" appears, then the connection is lost and the device tries to reconnect; I've included a picture which shows what it looks like. I already checked the APN, but it seems to be configured correctly.

-Music App: When I pause a Song and continue it again, for a half of a second or so the volume is very high even when the sound is muted; this applies to speakers as well as headphones. This bug does not appear using VLC.
[HTC One Mini 2] Marvbox:
Moin, 4 mobile problem: TWRP - Delete - cache only, not dalv!

This works fine on my device. This problem returns after a few boots, than delete the cache again. ;)

Thanks a lot guys, for your amazing work on the last weeks. It's unf..... Unbelievable what you are doing for us. :o
[HTC One Mini 2] error274:
Thanks for the advice - this fixed the problem! :)
[HTC One Mini 2] xxxmadraxxx:
My GF's phone also does this with CM13. So you're not alone there.
[HTC One Mini 2] userx404:
I had the same Issue. Switched back to CM until next release.
[HTC One Mini 2] Stefan Bauwens:
Do you need to fully wipe even if you have CM13 already installed? If so, does anybody know a good way to backup all the files, including the apps+data stored on the sd card which is formatted as internal storage?
[HTC One Mini 2] ElektroDancer:
You can use TWRP (our custom recovery). Select System, Data and Boot. https://www.howtogeek.com/240582/how-to-back-up-and-restore-your-android-phone-with-twrp/
[HTC One Mini 2] xxxmadraxxx:
adb backup -apk -shared -all /path/to/backupfilename.ab
[HTC One Mini 2] vonclutch:
Wow nice, this is rly good and extremely fluid :D

Only problem known for me is the network, it didn't work at all ( worked the 3 first day ^^ )

I tried to wipe the cache, not working :/
[HTC One Mini 2] Marvbox:
Sometimes needs my device a second reboot.