yashsingh1/xdaforums huggingface dataset:
[HTC One Mini 2] tryllz:
Hi [MENTION=7570463]nightcore500[/MENTION],

If you are asking about data, I do not use data, otherwise the radio connection is always stable on my device, I made international calls and sound was crisp clear, connection was perfect.

Overall the network is always stable for me.
[HTC One Mini 2] petie2106:
everything works fine. only nfc dosnt work.

---------- Post added at 07:11 AM ---------- Previous post was at 07:07 AM ----------

Tutorial: How to properly post a bug
[HTC One Mini 2] stkl:
Just flashed a custom build based on the latest Github sources. Switched to userdebug, which might not have been the best idea, but anyway...

NFC working

DT2W working

UHS SD card working

However radio is no longer detected and I experience random reboots after approx. 5 minutes -.-

Will switch back to eng build and figure out.
[HTC One Mini 2] nightcore500:
Your proprietary tree is not on the latest commit. Check: https://github.com/nightcore500/proprietary_vendor_htc_memul
[HTC One Mini 2] stkl:
I rebased my Kernel repo onto the latest official 14.1 branch yesterday wihtout the RT5506 (deb3463) and Prima driver (b189754) changes, as there have been updates for both parts recently. Can't tell any difference for audio or wireless experience so far.

I know there have been issues with the Prima drivers for some devices (I luckily had none), but imho at least our RT5506 changes might be obsolete, so we could be closer to official than before.
[HTC One Mini 2] Andruxcx:
Am i the only one with the extreme lag on camera apps? Even when i try to take a pic through whatsapp the phone freezes for a bit. Is there any way to fix this?
[HTC One Mini 2] stkl:
No, that's been a point of discussion ever since v0.1.

Lightweight camera apps make things little smoother, but when the apps are overloaded with features and automatically load gallery images (that's what makes WhatsApp camera integration slow) they generate quite some load.

It's definitely not the camera itself. Stupid apps like QR scanners are usually pretty fast.
[HTC One Mini 2] Andruxcx:
Ok

---------- Post added at 05:45 PM ---------- Previous post was at 05:29 PM ----------

Is it hard to go back to stock ROM? All I needs is a Nandroid backup?
[HTC One Mini 2] multiwirth:
I´m just wondering why this is like this.

On my galaxy S3 which has also only 1gb ram running LineageOS has no such problems with the camera
[HTC One Mini 2] stkl:
Same camera app, same background-tasks, same system config?

Lots of reasons why one device runs faster than another. There are definitely some bugs left in the One Mini 2 LOS 14.1, and I'd say it got worse with the CAF kernel (imho no reason to revert though).

The HTC camera modules might need little more resources than the Samsung ones, can't tell that for sure. But for me it strongly depends on what I've been running before opening the camera app. And as said before, scanning QR codes also requires camera access and autofocus and there is hardly any lag, while my phone crashed twice when taking a photo from WhatsApp, so I strongly suspect the app/system, not the camera blob.
[HTC One Mini 2] mahfiaz:
Another regression compared to CM13: when calling to support numbers they often ask questions about language preference etc, requiring you to push number buttons accordingly. This version of LOS does not send sound on button presses. Which renders some support lines unusable :(
[HTC One Mini 2] nightcore500:
Can anyone confirm that? I don't have this problem on either of my two devices.
[HTC One Mini 2] stkl:
Me neither. Have used the dial keys during calls in the past without any issues.
[HTC One Mini 2] nailyk:
We have an issue with z3 where OK siri is preventing microphone from working with calls.

Could this be related? Can you try to disable this everywhere and/or without gapps ?
[HTC One Mini 2] HandyBesitzer:
I didn't called much with my phone since i'm on LOS 14.

But it felt like the speaker volume is always on it's maximum while a call. I need to reduce it every time manuell. Can someone confirm that??

---------- Post added at 11:02 AM ---------- Previous post was at 10:56 AM ----------

i used the version 7.30.581119, too But it didn't save the pictures. Any ideas why?? Besides, it wasn't detected as a camera, so i couldn't use it on the lockscreen
[HTC One Mini 2] Andruxcx:
I changed the volume once during a call an it stays that way for me
[HTC One Mini 2] nightcore500:
It's a known fact. The volume increase was a bit too high in the last update. This will change in the coming update.
[HTC One Mini 2] nightcore500:
You mean "OK google"? Doesn't seem to be the problem. On my test device is currently the pure LOS. Same problem. I guess it's related to our new CAF based kernel and our mixer path configuration.
[HTC One Mini 2] nailyk:
OK. Just a clue as we had similar problem cause by ok google and fluence settings. Looks like we still not have the right combination to get everything working.

Good luck for the audio fix.
[HTC One Mini 2] Andruxcx:
Is it possible to change 3d rendered resolution? I noticed that on Huawei p8 lite the snapchat filter resolution is super low even though it can run better and our resolution is much higher, we can run it but its laggy. Is it an Los thing? I am wondering if theres a way to change the res just for my needs.

-Edit-

Scratch that the original is whack
[HTC One Mini 2] SecUpwN:
Ever since installing I have a very strange issue: No touch on *any* ROM! Please help!
[HTC One Mini 2] multiwirth:
You may have a broken digitizer.

Do you use TWRP and can you use it?

CWM was avaiable for a short time through cm11 nightlys which doesn't need touch to navigate.
[HTC One Mini 2] SecUpwN:
[MENTION=5614382]multiwirth[/MENTION], again: Touch is working perfectly on TWRP, yet does not activate on any other custom ROM. When flashing back to stock, everything works normal. I did S-OFF and Super-CID today to have a deeper look. Please help me solving the riddle here. Thanks! [MENTION=7570463]nightcore500[/MENTION], would you please help me as well?

UPDATE: Appears as if this ROM needs an update for the Himax driver as mentioned here. Danke! ;)
[HTC One Mini 2] multiwirth:
mhhm sorry, can´t help you in this case.
[HTC One Mini 2] katruzzy:
I have installed 14.1 and when i connect it to jvc car audio player via USB it is not recognized, and i cannot use it to send audio to car speakers via USB.
[HTC One Mini 2] DerLages:
i have a JVC aswell ... bluetooth via stock player works just fine, havent tried with their app jet.
[HTC One Mini 2] katruzzy:
My JVC does not have bluetooth, and it works very well wirh other devices via USB.
[HTC One Mini 2] stkl:
Just tried myself, can confirm USB audio does not do anything. Also tried to force the device in "audio source" mode (developer settings, usb config), no effect.

Quick look in the deice config reveals the USB audio paths are mapped (hopefully correct), so unfortunately it's not that simple... I'd suspect the source of this problem is to be found somewhere in our not yet perfect USB config (similar to other OTG issues I already experienced).

My car stereo however detects the device in MTP mode ("file transfer") and just reads the files from the device, not sure if that could be a possible workaround for your situation or if it's not supported by JVC or you're using streaming services...
[HTC One Mini 2] stkl:
[MENTION=7570463]nightcore500[/MENTION] Just noticed you missed the wireless MAC overlay in the latest release. Device is revealing the internal Airgo MAC instead of the HTC one.
[HTC One Mini 2] the_long_one:
In case nobody said so yet:

I have never seen my battery last that long. Possibly the brand new device did so for the first few days, but v0.4 looks like the long-running, well-working ROM of the year! Cheers & let me buy you a beer!
[HTC One Mini 2] multiwirth:
HWC

[MENTION=7570463]nightcore500[/MENTION] have you forgot to enable hwcomposer or why is it telling me "hwcomposer present and disabled" in terminal emulator?
[HTC One Mini 2] katruzzy:
where can i find device config?
[HTC One Mini 2] AllCrash:
Hello, any chance to get an update with the KRACK vulnerability fix?? Other lineage 14.1 has it already and it is quite important!

Thanks!
[HTC One Mini 2] stkl:
Will be more or less automaticall fixed in the next release, as the patch is part of the official LOS 14.1 kernel upstream and the hostapd/wpa_supplicant packages. I already built a new version for myself and it seems to work fine.

At the risk that it's probably not what you wanted to read, I was talking about the build configuration, to be found on GitHub (device, kernel)

Nevermind, it was my fault... Should be OK with your 0.4 build.

The relevant part was hardcoded in the older Prima drivers. Although there's a module htc_wifi_nvs it doesn't seem to do the job. I patched the hdd_update_config_from_nv() of the latest Prima drivers and the address is read correctly.

--

Another possible responsiveness improvement:

I changed the default IO scheduler from BFQ to ROW (tried "deadline" for a while, but ROW had the best responsiveness and the least instabilities). Don't have any hard measures, but from my subjective experience it makes a noticeable difference.

Feel free to pick the latest commit of my Github fork (device), but it's only a 3 character change...
[HTC One Mini 2] stkl:
Could anyone with a

stock

ROM device please check which USB product IDs the device is showing to a computer?

Currently it's showing

0bb4:0c93 - LOS in MTP and Charging mode (ID belongs to HTC Evo 4G)

0bb4:0f66 - LOS in PTP mode

According to an ID list, the first should match 0bb4:0629 instead and I want to verify which one is correct.

On Linux/OSX systems just type lsusb in a terminal window and search for a line showing "HTC ..."., for Windows users it's to be found in the Device Manager, find the phone, Properties > Details > Hardware Ids.
[HTC One Mini 2] HandyBesitzer:
sry, i don't have stock -.-

I noticed a kind of bug. Last week the OS crashed another time (freeze, black screen,..) And after i could use it again, the Background was changed to the stock default one, instead of my custom pictures. Any ideas about that?? It's nothing soo important, but if you have an idea about what is causing this, it would be nice to have a fix.
[HTC One Mini 2] stkl:
Noticed the same bug some time ago. Thought it was an incompatibility with the Pixel Launcher (ported from Oreo), so I didn't investigate any further. Which launcher do you use and do you have Google Wallpapers installed?
[HTC One Mini 2] HandyBesitzer:
I have only los 14 (i think trebuchet is the name of the launcher) and the gapps pico. I don't think that google wallpaper is a part of it. So if LOS doesn't come with it, it's not installed
[HTC One Mini 2] Andruxcx:
Thats probably why we have performance issues, I will check when I get home in 4 days
[HTC One Mini 2] stkl:
You're right, so the problem belongs to LOS/Android and not the Google stuff. Good to know, so maybe it's worth having an eye on it.

Unfortunately I didn't have any crash recently, updated twice last month and switched the I/O scheduler to a slightly more robust algorithm... Will try to provoke a crash by heavy multitasking ;)
[HTC One Mini 2] nightcore500:
If you're referring to the post you quoted, I'm sorry to disappoint you. In this case, the device only pretends to be another device. Otherwise, this has nothing to do with our performance problems. The faulty name is partly caused by our device configuration and partly by our kernel.

[MENTION=1199534]stkl[/MENTION]

The ROW IO scheduler was used in the first ROMs with Cyanogenmod 13. Unfortunately, the sheduler is not suitable for multitasking. It is also a bottle neck for write accesses. The current sheduler "BFQ" is definitely not perfect. But after several benchmarks it showed the best results so far and is used in many official LOS ROM's like M8 and all other msm8974 based HTC devices.

That's one thing you can deal with for weeks. For this reason, BFQ was chosen for the time being. Unfortunately, the user's type of use is also decisive here.

[MENTION=535343]all[/MENTION]

Due to the already mentioned security flaws I will probably upload another release this weekend. But this time without any big major improvements because I haven't found much time in the last weeks.

I hope that I will be able to solve the problems in the next release with the reactivation of the display, the partially not working NFC and the not working microphone when making phone calls via loudspeaker.
[HTC One Mini 2] nightcore500:
V0.5 is here :)

Changelog

Release V0.5 (04.11.2017)

Amplifier HAL improvements

Removed useless button backlight support on liblights

GPS HAL cleanup

Enabled CLANG compilation for GPS HAL

Removed some deprecated flags

Fix tombstones creation

Root directories now created on early-init

Missing directories under /data are now created

Cleaned up main QC init script

XTRA download now uses https

Cleaned up OMX codecs packages

Added GPS configuration for China

DRM ClearKey plugin is now builded from source

Fix gpuclk and reset_count denials

Added missing OMX codecs decoders

Removed deprecated media blobs

Cleaned up bluetooth config

Decreased in call volume to about 74dB

Enabled GLONASS support

Kernel: Added Himax touchscreen driver

Look here for full kernel changelog (Last commit from previous release: 2fc6b22)
[HTC One Mini 2] Andruxcx:
Wouldnt that make apps think that they are running on a different device so it results a bigger render resolution?

I figured it was ported from another device. Thank you for clarifying
[HTC One Mini 2] stkl:
This identification has no influence on apps at all, it's just USB. And as there is no difference in the MTP capabilities of both devices, it doesn't matter what the computer "thinks" (device class IDs are fine, only the product ID is messed up - same for many ROMs on various devices).
[HTC One Mini 2] tryllz:
Can anyone confirm mic working with loudspeaker now in call..

I have done a dirty flash, mic not working with Loud Speaker in call..

Will try with complete flash and update here..
[HTC One Mini 2] HandyBesitzer:
Do i need to clean something up before i install it? Or can i simply overwrite the old version??
[HTC One Mini 2] XDAFresh:
Thanks Nightcore for your awesome work! Do you have plans to release a stable version any time soon?

And also thanks for your support of this device!
[HTC One Mini 2] nightcore500:
No, as I wrote in the last post, I haven't had enough time in the last few weeks. If I have the time I will fix the problem in the next release.

If you are already on an older release of LOS 14.1, you don't usually need a wipe. However, it can never hurt to perform a wipe of dalvik and cache before flashing.

Of course, but I can't give a date when the ROM can be considered as stable.
[HTC One Mini 2] tryllz:
Its OK, I was just concerned perhaps my mic is actually not working, Thanks, no issues..
[HTC One Mini 2] XDAFresh:
Thanks for your reply, will it then be possible to upgrade from the beta to the stable release without doing a full wipe?
[HTC One Mini 2] malstroms:
hello [MENTION=7570463]nightcore500[/MENTION] thank you for the rom, i've been using it for couple day and works great.

i've use limit background process by only 2 and it more responsive and less laggy

hope the stable version come out soon
[HTC One Mini 2] HandyBesitzer:
Hi, i noticed a kind of bug, but i'm unsure. Maybe others of you can confirm.

When i'm calling sometimes the phone hang up. I think there is a problem with the approximately sensor that does not block the input. Later when i want to hang up the phone the display didn't wake up again.

Bin mir nicht sicher, ob ihr das richtig verstanden habt und wenn ich das richtig sehe, kann hier eh jeder Deutsch :p

Also wenn ich telefoniere bricht häufig die Verbindung ab. Ich vermute, dass der Annäherungssensor nicht richtig geht und daher die Eingabe auf dem Display nicht gesperrt wird. Als ich letztens dann wirklich auflegen wollte, blieb mein Bildschirm schwarz. Was auch häufig ist, dass ich die Zahlenkombi eingeben soll, bevor ich auflegen kann.
[HTC One Mini 2] stkl:
Yep, same here, but I got this problem for quite a while (CM11 or 12I believe).

I changed the calibration data for the sensor via shell script, but had to tweak the 2 values (threshold on and off) for hours, the flip cover detection locked the phone by accident every few minutes... So probably my values won't help that much.
[HTC One Mini 2] markush1965.mh@gmail.com:
Fm radio crashed

Hallo, the rom is very great, many thanks for it. But i have a problem with fm radio. When i pluged in headphones the fm radio app crashed. Has anybdy the same problem?
[HTC One Mini 2] HandyBesitzer:
no, for me everything works fine withe radio. I used the HTC headset that came with the phone
[HTC One Mini 2] stkl:
That's what you can read about everywhere, but despite any benchmarks what I can tell from user experience alone is that ROW makes the system overall far more responsive, including switching between apps.

Talking about "multitasking" on a device like the One Mini 2 probably means a handfull of smaller background tasks. For multiple active heavyweight-apps te scheduler is definitely not our biggest problem. There are generally no real I/O-heavy operations on most mobile devices anyway and the majority is read-only, loading apps/data into memory. Hence the write botteneck doesn't have that much impact. As our device is probably not first choice for HD video recording and high frequency photography, effect opn UX is rather low.

Absolutely. I'm totally fine with your decision here, as I just change the property for my own build ;) Just wanted to provide my experience with that topic as it might be of interest and I wasn't sure if it has been a reasonable decision or just staying with some default value.
[HTC One Mini 2] mahfiaz:
Happens to me as well at times. Usually related to multitasking but I have no idea how to reproduce it.

Another strange bug:

0) not needed - make sure in Settings → Gestures → Double tap to open camera is enabled AND your camera app has "Bright screen" option enabled so it changes screen brightness (if not you may need to hard reset your device)

1) set screen brightness to automatic AND set brightness slider to 5% or less

2) put your device to sleep (turn off the screen)

3) press the power button to turn it on

Problem: screen remains black.

Workaround: double-tap power button to have camera app change screen brightness.

Workaround 2: hard-reset (press volume up and power button together for at least 9 seconds)

Workaround 3 (edit, thanks stkl): get your phone to brightly lighted room

Can anyone else confirm this?
[HTC One Mini 2] stkl:
Thanks very much for this hint!

I had the same issue for a while and thought it was random, but you're totally right, it's the brightness. Cover the sensor with a thumb (in auto-mode) and the screen stays black, hold it under light it's fine...

I already tried to debug this issue, but unfortunately no relevant kernel message and just a generic Perflock message in logcat... Now I know where to search for a solution :)
[HTC One Mini 2] mahfiaz:
Hey, turning on the lights or coming out from the basement is a good workaround as well :)
[HTC One Mini 2] Marvbox:
Moin, boot loop after installation Magisk update!
[HTC One Mini 2] cyberbix:
Great ROM, works fine. I also have the speakerphone bug reported sometimes in this thread. Microphone is dead as soon as speakerphone is enabled.

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.101.1102.19.0708

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.18.161.5

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) platform: hTCBmsm8226

(bootloader) modelid: 0P8B20000

(bootloader) cidnum: VODAP001

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP
[HTC One Mini 2] Andruxcx:
Came back from stock and the hal updates made the rom so much better!
[HTC One Mini 2] nightcore500:
V0.6 is here :)

Release V0.6 (25.11.2017)

Fix USB Accessory mode

Add ANT+ support

Swappiness has been set to 100

Kernel: Pocket check added for dt2w

Kernel: Fixed non-working microphone during a call on loudspeaker

Kernel: Improved the bus recovery procedure in qup i2c driver

Kernel: Register SPS IRQ with IRQF_NO_SUSPEND flag

Kernel: Reworked kernel config

Kernel: Merged Tag "v3.4.100"

Kernel: Merged Tag "v3.4.113"

Kernel: Max readahead size changed to 512KB

Kernel: Fix high load average from uninterruptible waits

Kernel: Do not allocate new hw_event if event is duplicate

Kernel: interactive: turn boost_pulse off on boost off

Kernel: interactive: Remove unnecessary cpu_online() check

Kernel: ablk_helper - Replace memcpy with struct assignment

Kernel: Don't plug the I/O queue in do_io_submit()

Look here for full kernel changelog (Last commit from previous release: 4e5b7fb)

At the moment I am still working on our wake-up problem. Since the problem occurs randomly, it is quite difficult to work on the problem. However, I hope that I can fix the problem with the next release. :)
[HTC One Mini 2] Marvbox:
Thanks a lot.

Is it's possible to create a small update package also?

I live so far at the Pampa, without DSL or LTE and fu..... small data packages...

Best regards.
[HTC One Mini 2] stkl:
Great, can confirm the mic and USB fixes working.

Had to re-enable linux regulatory implementation in the kernel config for compatibility with the latest wireless drivers, beside that no (new) problems so far.
[HTC One Mini 2] multiwirth:
Downloading the new build...

[MENTION=7570463]nightcore500[/MENTION] can you explain me what you did to fix the speaker crackling?

I´ve got a One M9 for 50€ (soft bricked, scratched and broken powerbutton...) and flashed offical LineageOS 14.1

It has the same crackling sound issue and maybe it can get fixed by your help :)
[HTC One Mini 2] tryllz:
[MENTION=7570463]nightcore500[/MENTION]

Thanks, Mic now working loud speaker, I believe I have to add there is minor crackling in speakers as well, I believe its just a software fix needed since there is no HTC Boom sound integrated..

Nonetheless, thanks a lot..
[HTC One Mini 2] multiwirth:
The integrated amplifier has a limiter which reduces lower frequencies and increases higher frequencies to get a higher volume withouth clipping - but you also lose the dynamic (bass).

So you can put the volume up 2 steps before max. volume until you notice the limiter.

I haven´t noticed any crackling sound with this rom, also my M8 which runs offical builds has this hardware limiter fully working.

For better sound, you can use Viper4Android which will also reduce low frequencies your phone can´t play at all and increases frequencies your phone can play very well (that´s basicly what boomsound does).

Since I´m not a developer, I have no clue how to fix this and that´s why I´m asking since the M9 could get this fixed aswell (no limiter active = horrible)
[HTC One Mini 2] nightcore500:
You need the right amplifier HAL. I just looked at the source of the official builds for your phone. The device configuration includes the "android_device_htc_hima-common" repo which apparently already has the correct amplifier HAL. (https://github.com/LineageOS/android_device_htc_hima-common/tree/cm-14.1/amplifier)

Maybe it's a hardware issue?

EDIT: Looks like the TFA DSP is disabled on official builds: https://github.com/LineageOS/androi...mmit/80a0ac9d21cfc809bcceaa477704476c6437f317
[HTC One Mini 2] shikulja:
camera very laggy..
[HTC One Mini 2] multiwirth:
Yeah looks like that...

But thank you for your help!
[HTC One Mini 2] Silver-HaOS:
Hi. Excellent ROM !!! Thanks!

But I found a bug: during the call the screen goes blank, but the touchscreen continues to work. You can lower the curtain, turn on the flashlight, accidentally end the conversation ...