yashsingh1/xdaforums huggingface dataset:
[HTC One Mini 2] tryllz:
I have to agree slightly to this, I have observed this behavior too, sometimes after call ends settings are open, swipe from top options are open etc, while I don't necessarily recall moving the phone away from the ear, could be due to moving it slightly which might trigger the sensor to deactivate.
[HTC One Mini 2] HandyBesitzer:
nice, gonna install it soon.

I have an other bug while, or better after calling. [MENTION=5810425]TryllZ[/MENTION] that bug is known and already reported. But after i called the screen stays black. It takes very long to reactivate and so to end the phone call.

What do i need to delete before flashing / what is recommend? There is

Dalvik / ART Cache

Cache

System

Daten

Interner Speicher

Micro SD-Karte

Android Secure

USB-OTG

SD-EXT

I'd guess the first both option. Is it important to do this before or after flashing? Because when i flashed the last time the LOS update, i got the option to delete dalvik and cache after it finished flashing. I wonder because i thought i need to do so before i start flashing the update
[HTC One Mini 2] stkl:
For first flash it is recommendet to wipe System, Data, Cache and Dalvik-/ART-Cache.

For updating withing LOS 14.1 it is not necessary to wipe system/data, maybe cache after flashing.

All other options are completely optional, as data stored on internal storage or SD card are usually things you want to keep indepently of the system .

For the caches it doesn't matter if you wipe before or after flashing, as there is no data written to these partitions inbetween.

I successfull dirty-flashed from CM13 without wiping in the past, but it leaves a couple of artifacts on the system which is not needed at all or might interfere with the new system. So it's defnitely cleaner to wipe beforehand and restore apps/data from a backup after system setup. When I flash twice or more a day with ohne minor changes (happens sometimes in development phase) I usually don't wipe anything wihtout any issues...
[HTC One Mini 2] HandyBesitzer:
All right, so since i've already installed this mod, i'll just wipe davlik and cache right after falshing
[HTC One Mini 2] Silver-HaOS:
It's easy to check: put the phone on the table, call, tightly closed the sensor a hand. The screen turns off, but the touchscreen continues to work. If you click on the place where the "end of call" button is located - it will work.
[HTC One Mini 2] Andruxcx:
The wifi fluctuations are unbearable
[HTC One Mini 2] HandyBesitzer:
I've tested the USB Accessory mode today and i can confirm, that it is working now :D
[HTC One Mini 2] Andruxcx:
I think i fixed it by clearing the dalvik and cache then installing the same rom over the existing one and then clearing dalvik and cache again when prompted

Edit: spoke too damn soon 2 days and its back
[HTC One Mini 2] Aussi:
am I the only one experiencing almost not workable phone?

It is extremely slow and laggy

Maybe its my phone but would love to use this ROM
[HTC One Mini 2] Opteronix:
Thanks to nightcore500, a very fine ROM.

So, after some problems with my phone-akku (thanks to Marvbox), I‘ve tested now the version 0.6.

I can confirm the „touch-screen-continues-to-work“ bug described by Silver-HaOS and TryllZ.

The clock work perfectly now.

But now, the internal cam- app will not started up, it crashes. Other cam apps as well. :crying:
[HTC One Mini 2] userx404:
I noticed an performance improvement by reducing the ram load.

Uninstalling unneeded apps and remove apps from autostart. -> reboot
[HTC One Mini 2] Aussi:
Alright will tried that ! :)

Also just notice after installing the ROM in twrp. I get 2 error message's

E:\ unknown command [log]

E:\ unknown command [log]

Don't know if any one had this problem yet? The ROM actual loads fines after those errors
[HTC One Mini 2] stkl:
The log error is a TWRP issue and does not affect the actual ROM, just ignore it for now.
[HTC One Mini 2] HandyBesitzer:
had the same messages
[HTC One Mini 2] multiwirth:
Yes.

The phone is low end now but other devices with similar hardware run much faster -still slow but useable.

I think there is still an issue with the ram and no zram or ksm can fix this.

Other phones with 1gb ram run more stable.
[HTC One Mini 2] nightcore500:
As Stkl once said in an earlier post, two differend devices cannot be compared to each other. It may be true that other devices run better with 1GB RAM. However, the hardware is not the same. Note that any components such as sensors, displays, amplifiers, radio chips etc. require a variety of drivers that are permanently loaded in the memory. In addition, there are all possible proprietary files from the respective manufacturer. And don't forget shared memory that varies from platform to platform. These little things make the big difference.

As userx404 has already pointed out, the number of permanently active apps and their size is the deciding factor. I have absolutely no performance problem on my daily used device. Despite the fact that I have installed a lot of apps. If I don't need an app any more, I stop it completely in the "recent applications" menu and don't let it come to an intervention of the LMK. If it's already getting so tight in memory that the LMK has to intervene, it's quite logical that the performance is bad.

Due to our LMK settings, it also intervenes very late. If you want to start a very large app and the device has only more about 40MB of RAM free at its disposal due to masses of active apps, the LMK has to stop processes/apps to avoid an "out of memory". In the meantime, other processes also want to do their work. This leads to an extreme overload, which means that the device can hang up quickly. If we change the settings of the LMK that it acts more aggressively we come back to the topic "multitasking" because the LMK terminates too fast and too many active processes/apps. For this reason, we changed the current LMK setting at CM13 time and found a good compromise between performance and multitasking. As long as the points mentioned above are observed.

I hope that we can check off the topic "Memory" now.
[HTC One Mini 2] Opteronix:
All ok, camera works again :laugh:

The solution: I have deleted the cache and the Dalvik, and now, it works again. :fingers-crossed:
[HTC One Mini 2] multiwirth:
Please don´t get me wrong but working for you doesn´t mean it´s working for everyone like we saw with that wifi driver in the past and other stuff like this touchscreen thing and so on.

I don´t use this device as daily driver since it wouldn´t make sense with a broken mic and vibration and of course the broken headphone jack.

So in this case I have nearly nothing installed on it.

Some important apps like gmail or youtube are installed or an app to move files from device to device easily.

Also telegram is installed, like on every device.

Nothing else.

I always close apps from "recent apps" even on my daily driver which can handle much more apps.

This device is still unuseable.

The camera forces the system to freeze and if it respons after some time (mostly not) the system ui restarts and so on.

I´ve checked free ram:

Always about 250 mb, that´s normal.

So and now opening the camera brings the phone in a completely unusuable condition.

For some it is working, for some not.

This was already reported.

I know this device is old and slow but will the camera app and their drivers need 250mb ram?

The exact same applies to many other things.

Like our LMK wouldn´t work at all but kills apps in backround anyways (what makes no sense) but I don´t know to describe it.

So my conclusion to this is: there are more problems than 1gb of ram, at least on my device.

So that´s just my experience and I don´t want beef with you due to this.

I just want to figure out why this phone is nearly unuseable -there must be a reason.

Reflashing the rom with a full wipe doesn´t resolve it and also any updates didn´t change anything.
[HTC One Mini 2] stkl:
Interesting how different the subception can be at this point. I use this phone as a daily driver for over 2 years on CM/LOS and despite poor camera performance I don't have any issues with everyday usage (I like the form factor). This includes full Google stack, Pixel stuff, Chrome browser, messaging and sometimes Navigon navigation (which performs far better than GMaps btw.). Waiting 1-2s for an app to start is not a big deal from my point of view. Battery is really great though, usually 2-3 days without charging.

Yes, most camera apps make the phone terribly unresponsive, but I nearly never use it, so I'm fine with that (please, no discussion on camera again). Can't tell any major drawbacks for other standard apps.
[HTC One Mini 2] multiwirth:
It takes much longer to start an app.

Opening telegram... Waiting so long for the keyboard to open... I take another device to answer that guy who has sent a message to me (you can sync as much devices as you want)

So I really can't say it's peeforming very well.

Sometimes after I've got a system ui restart due to an too heavy app it performs like it should.
[HTC One Mini 2] stkl:
I did not intent to call you an lier. I know there are apps with poor performance, I just want to point out that it strongly depends on what you're doing with your phone, than with the phone or the system itself. I don't have Telegram installed, so I can't tell anything about this app in detail. Sometimes I have lags of >2s as well when "many" apps are running, but I usually close everything anyway, so it affects my workflow maybe 10 seconds per week...

If the device does not perform well for a certain usage, it might simply be the wrong device.
[HTC One Mini 2] XDAFresh:
Rom is working good, but is there a possible solution to my problem?: everytime calling, the display gets touched by my face, so is there any chance to vary the proximity sensor or sensitivity of the screen?
[HTC One Mini 2] userx404:
feel free to read de posts in this thread ;)
[HTC One Mini 2] Silver-HaOS:
Dear nightcore500, will there be a fix for the touchscreen?

Thanks.
[HTC One Mini 2] Htcminione2:
7.1.2 htc mini one 2 memul

Hi

I have the HTC mini one 2 memul unlocked. S-on and boot loader unlocked.

After installing the lineage 7.1.2 Rom my phone is so slow, the camera works but is so slow it's unusable, the sensor for when your on the phone keeps cutting in and out making my head mute, and press keys during calls. When calls come in it's so slow that I can't even answer the call as it's not on my screen before it hits my answer phone.

The phone works really well on stock 4.4.2 Rom but need it to be higher for apps and smart watch.

Anyone else had any of these issues and or could anyone help me please as I love the phone .

Regards
[HTC One Mini 2] ElektroDancer:
The latest stable custom ROM that i know is this one: [ROM]NostromoPop 2.4.0 (25/10/16)[CM12.1][5.1.1]

If Android 5.1.1 is enough for you I would use this and if LOS 14.1 running stable you can go back.
[HTC One Mini 2] multiwirth:
This is all well known -at least for some of us.

The developer's phone seems to run just very well, that's what he told us while my mini 2 is completely unuseable.

There are many improvements since he started with cm13 compared to the CM11 nightlys back in the days or the unoffical CM12.1

I haven't seen a 100% stable rom for this device and I gave up my hope when the maintainer for cm11 sold his phone -maybw the best what we can do.

Unoffical LOS14.1 is cool, but there are some major issues as you alreaey noticed.

The big thing is this tiny 1gb ram which is not enough for today.

The other thing is this memory problem.

I'm not sure what it is but zRam doesn't solve anything.

It maybe a memory leak or idk.

At least the developer has the opinion "there is nothing we can do".

Those issues with ram were already there in cm11 but not as heavy as today since cm11 (kitkat) doesn't need so much ram.

I think it will never get fixed and I already switched from memul to Galaxy S3 and then to HTC One M8.

And this M8 rocks!

LineageOS runs nearly without any problems and in all it's the same good looking phone but bigger and better.

By the way:

The Nvidia Shield Tablet has the same issue caused by ram but it has 2gb of ram so it's not a big issue for now.

The developer/maintainer knows it.

And this issue doesn't exist in nvidia stock android 7.0 and i don't think this 7.1.2 makes this big difference.

I hope it gets fixed in the future maybe with LOS15.1.

Great device anyways, has the graphics power of an galaxy s7 and this shield is from 2014!
[HTC One Mini 2] Htcminione2:
Not fixed

Thanks ElektroDancer , I downloaded this Rom today and all seemed to be working well then it just shut down and kept restarting, tried install again and then it kept having the home setup restarting.

Any other advice please or is it just it's time done now.

Called HTC and they said there is a stock Rom from them that's 5.0.1 version but won't say the Rom is, any idea ??

Regards
[HTC One Mini 2] Andruxcx:
According to this http://htc.youmobile.org/#onest it has been cancelled
[HTC One Mini 2] Aussi:
is it correct that my phone has problems with connecting to the PC? Saying it is not recognized and gives error 43.

I googled it a bit but not really found a proper solution?

I am running on Windows 10 .... that might be a issue ?
[HTC One Mini 2] Andruxcx:
Thats weird. I don't have any problems. Try reflashing
[HTC One Mini 2] Aussi:
Hmmm OK I already had the problemen also on CM13...

So might als be something else besides the ROM.

Thx for the heads up
[HTC One Mini 2] the_long_one:
Have you tried using a different cable? After some years of usage my USB jack has indeed worn out a bit. One of my many cables kept disconnecting when i picked up the connected phone.

---------- Post added at 12:54 ---------- Previous post was at 12:39 ----------

Mine works pretty fine although i really asked for trouble. I updated this ROM over nightcore's 13.1 build - i only wiped dalvik and cache. Still runs fine except for a crashing camera app :fingers-crossed:

What's wrong with the forum software? It keeps copying my own submission into the post after saving....
[HTC One Mini 2] nightcore500:
No, I don't think there's nothing we can do. I have tried to help 4 users by PM so far and find the problem. The result was that it was either a high workload due to defective hardware because the driver of the NFC chip tried to communicate with the defective NFC chip without interruption or the user had just installed so many apps with background tasks that the hardware just couldn't keep up with it.

I own 2 units of the Mini 2 generation. One with the current baseband version which I use daily and another one from [MENTION=5080968]MrAnswer[/MENTION] that i use for development purposes with the older baseband version. Both devices have no performance problems. So far I only know a third variation of the one mini 2 with himax touchscreen which apparently are not affected by the problem.

I can hardly imagine that there is another variation that makes such hardware/software problems. However, I do not want to rule it out either.

The only way to find the problem would be to collect further information.

First of all I need information about the hardware. Turn off the device. Press and hold power + volume down to boot into bootloader mode. Connect your device to your computer. If you don't have fastboot/adb installed on your computer you can install it with this installer: https://xdaforums.com/showthread.php?t=2588979

If the bootloader of your device should show "HBOOT", switch to the menu item "FASTBOOT" by using volume up and volme down and press the power button. You should now see "FASTBOOT USB" in red letters.

Now start cmd on your computer and execute the following command:

fastboot getvar all

Copy the output into a new text document and upload it as an attachment to your new post or copy and paste it into an CODE tag or something.

Restart the device and boot normally into android and wait 5-10 minutes. Go to the developer settings and enable the "Android debugging" setting under "Debugging". Now execute the following command in your cmd:

adb shell

You may get a line like "7[r[999;999H[6n" or something like that. Press enter and you should get "memul: / $". Now execute the following commands and copy the output again either into other text documents or copy and paste the outputs into further CODE tags or something:

cat /proc/meminfo

top -n 1

dmesg

logcat

Which Gapps do you use on your device? Which apps have you installed? Does the problem occur after the time or directly after booting?
[HTC One Mini 2] multiwirth:
I know how to do this, wasn´t necessary to explain everything in detail but doesn´t matter now.

I will collect all info i can give about my device and report it in a second post
[HTC One Mini 2] multiwirth:
[MENTION=7570463]nightcore500[/MENTION]

OpenGApps pico.

User-Apps:

AdAway (org.adaway)

App Ops (com.erickkfz.appops)

App Quarantine (com.ramdroid.appquarantine)

Chrome (com.android.chrome)

CPU-Z (com.cpuid.cpu_z)

Es File Explorer (com.estrongs.android.pop) < old non-bloated version of this app (v 3.2.5.5)

Gboard (com.google.android.inputmethod.latin)

Gmail (com.google.android.gm)

Google Play Games (com.google.android.play.games)

Google Wallpaper(com.google.android.apps.wallpaper)

NavBar Apps (pl.damianpiwowarski.navbarapps)

Pixel Launcher (com.google.android.apps.nexuslauncher) < installed to /system/apps/

SELinuxModeChanger (com.mrbimc.selinux)

SuperBeam (com.majadev.superbeam)

Telegram (org.telegram.messenger)

YouTube (com.google.android.youtube)

Note:

Many of those apps are only currently installed and might get uninstalled soon and should not affect the overall issues since this issues can´t be fixed with a wipe or having as less as possible apps installed.

Sometimes my Galaxy S3 gets slowed down which can get temporary fixed by cleaning cache.

Now the fastboot stuff:

getvar all

C:\WINDOWS\system32>cd C:\adb

C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.101.1102.16.21_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: nope
(bootloader) imei: nope
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d06a629a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.034s

top -n 1

>Attachments

dmesg

Attachments

logcat

>Attachments (too long for post)

In the logcat I´ve started the camera which worked surprisingly well this time.

Can´t say when the issues start - mostly after boot and sometimes i get a insane boost after using a big heavy app.

Btw.

http://adbdriver.com/ brings a nice and easy user interface.
[HTC One Mini 2] Finusfix:
Der Wahnsinn, wie sich manche Leute hier ausdrücken und dann noch Hilfe fordern... :good:

Sorry, aber das musste jetzt mal raus.
[HTC One Mini 2] nightcore500:
Sorry, my glass ball is broken.

Everything looks normal. The only thing I notice is that your device seems to be constantly under high memory load. Almost 50MB are still available.

Confirms that your device simply has full memory all the time and the LMK kills running background apps.

Btw. you are using an older bootloader and an older baseband version. An upgrade through the HTC ROM's is only possible with S-On and locked bootloader. However, I can't say whether the upgrade will help.
[HTC One Mini 2] tryllz:
If he did, despite you knowing, you could have just sent a smiling smiley :o instead of what you wrote and the way you wrote.

With all due respect, [MENTION=7570463]nightcore500[/MENTION] does help everyone out individually and collectively, you need to understand he is not responsible for any of our devices yet he has taken it as his responsibility, despite his own time and circumstances, and tried and solved many of the issues.
[HTC One Mini 2] stkl:
I just managed to build the first working memwl (One Remix) ROM based on our Mini 2 LOS 14.1.

At the moment I'm using the same blobs and 95% the same device configs and it runs quite a bit smoother out of the box, including camera (Snap) opening in 0.5s and ready to shoot immediately (engineering build, no GApps, no other apps yet). Don't know if it's the 1.5GB RAM, something else in the hardware or just placebo effect because the system is completely clean... I will keep monitoring and comparing when the new ROM is stable.
[HTC One Mini 2] multiwirth:
Wow wait don´t get me wrong.

I don´t want to be unfriendly and this was just a annotation so he knows he doesn´t have to tell me this next time.

It was not the first time collecting logs for this device in this thread.

So what I don´t understand: What was wrong with my annotation? Why is it unfriendly?

Sorry if it sounds unfriendly to you.

I respect nightcore500´s work and just want to help fixing some problems.

---------- Post added at 08:33 PM ---------- Previous post was at 08:27 PM ----------

Is there even an firmware update avaiable to flash?

It has the o2 cid and due to this it might be difficult to find anything.

It ran CyanogenMod 11 from day 2 so I don´t know if there was even a single OTA update.

Anyways thank you for your analysis.
[HTC One Mini 2] tryllz:
Your words choice were wrong even for an annotation as I understood it, my apologies if I misunderstood the context.
[HTC One Mini 2] moghingold:
Thank you so much for your hard work! Can't wait to try flashing it!
[HTC One Mini 2] nightcore500:
V0.7 is here :)

Release V0.7 (20.01.2018)

Update to latest LOS upstream

Shrink USB Charging Images to fit 720p screen properly

Rework init power script a bit

Unbreak perfd

Hide sRGB toggle in developer options

nfc: Advertise extended length support for IsoDep frames (Thanks to stkl)

Kernel: ANDROID: sdcardfs: notify lower file of opens

Kernel: ANDROID: sdcardfs: Add default_normal option

Kernel: Enable some perf-related configs

Kernel: drivers: touchscreen: Fix active touchscreen during calls and power button camera shortcut

Kernel: drivers: i2c: Use older QUP bus driver to fix wakeup issues on memul

Look here for full kernel changelog (Last commit from previous release: 2d22c8c)
[HTC One Mini 2] HandyBesitzer:
Is there a todo sheet somewhere??
[HTC One Mini 2] nightcore500:
[MENTION=4466518]HandyBesitzer[/MENTION] For what?
[HTC One Mini 2] tryllz:
Thanks, running smooth as ever..

Any word if Oreo is ever coming to us..
[HTC One Mini 2] HandyBesitzer:
for a fully stable rom
[HTC One Mini 2] userx404:
In my state of mind 0.7 works a bit smoother and less laggy.

Thx for fixing the touch bug :good:
[HTC One Mini 2] HandyBesitzer:
is there hope for better multi tasking?? Yesterday right after the update (spotify + chrome) crashed again and removed my background.

But the most important bug i noticed: If you are doing anything with your device and then someone calls it takes really long to show the phone mask and then to start the call.

So if you may could give the call app more priority while multitasking.
[HTC One Mini 2] multiwirth:
Is this even a good idea?

I don't know how much work this is or how difficult it is.

But i know that oreo for the galaxy s3 is a huge amount of stuff that has to get working.

And something with the kernel has to be changed.

I think porting linux 3.4 to it is required.

How is it looking for the mini 2?
[HTC One Mini 2] Finusfix:
Of course, there's a lot of work involved. As with any other android port. From the device configuration to the kernel, a lot of changes have to be made for each port.

But nightcore has us shown several times that he has the necessary know how to port new android versions to our mini 2.

I strongly believe that nightcore has android go in mind which would be good for our mini 2.

I'm already looking forward to it :good: :)