yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] FutureGamerz:
Can check whether Pokémon Go is working on the latest rom? Since you said it passes safetynet check.

Haven't updated the rom for a while coz the version I have is rock stable. Thumbs up for that!!
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] abhisheksharma89:
Latest build is bug free.

nigel8, you rock man.

Keep up the good work. :good:
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] saisannihith:
Guys can someone confirm if substratum is working fine on this rom?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Andy4Shurr:
Just installed it and it let me get to point of catching the first dinosaur thing so I'm presuming all is OK with the game. I'll uninstall it now :good:

---------- Post added at 06:38 AM ---------- Previous post was at 06:36 AM ----------

Not very well for me, it can install and certain themes can be applied if you don't theme the system but i kept getting force closes on the dialer and other apps.

---------- Post added at 06:45 AM ---------- Previous post was at 06:38 AM ----------

Yeah i installed this last week, works ok but no ds4 support so touch screen only and as it's the official unmodded app it won't run on mobile data either.

You need magisk to hide root. Also you don't need to edit the build prop like that guide says.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] FutureGamerz:
I still can't get through. Says this device, OS or software not compatible. SafetyNet check also failed. How did you get it through?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Andy4Shurr:
I've installed magisk, rooted with magisksu and use the magisk hide option for any apps that have a root check. Pokémon go was hidden by default.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] FutureGamerz:
Can enlighten me the proper way to install Magisk? Have read the guide but it says restore to stock bootloader etc.

Unsure what's the proper method to install it on Custom rom.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Andy4Shurr:
Are you rooted at the moment? I had SuperSU originally installed so I fully unrooted from the SuperSU menu, installed magisk from play store, downloaded the magisk v11.6 zip using the app then rebooted to twrp and flashed it. Reboot and profit.

That worked fine for magisk and safetynet but i ended up doing a clean flash and set up of LAOS because of another app which caused problems with using magisksu and not having SuperSU. So this time round i never had to fully unroot, just install the ROM, gapps etc then boot back into to twrp and flash the magisk zip i downloaded before.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] keithleyson:
Got Magisk Installed had to clear and redo my fingerprints since the scanner was not working after boot. I fail the Safetynet check CTS mismatch. How can I fix this?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] FutureGamerz:
I didn't redo my fingerprints though.

Go to Magisk manager setting and enable magiskhide.

But... Something else not working. Though managed to get Pogo to work.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] keithleyson:
I followed this https://xdaforums.com/apps/magisk/question-safetynet-failed-cts-profile-t3558393/page8 got it finally.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
Those settings were maybe more battery friendly but at the cost of worse performance.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] sdheer2012@gmail.com:
Hi Dev., even though tried many firmware zips No call ringing, Pl help what to do, now no calls, Thank You.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ioy:
Its understood, however please understand battery seems more important to me personally. Indeed, my main activity on this phone is phoning, internet browsing, emailing etc, so as you see its kind of moderate demand for computing power ;)

And also in KernelAuditor you can create profiles for Tasker to switch between them automatically (e.g. when starting new game then Tasker actvates profile for performance, after closing a game it returns to the most battery friendly profile etc)

Please, maybe somebody keeps still this data, i.e. settings of the kernel 0319?

HELIUM, LineageOS 14.1 r.03-27-2017 by*nijel8
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] spvm500:
Awesome

Just wanted to post and say a massive thanks to those involved in the development of this ROM. I purchased a Mi Max Helium 128GB/4GB to replace my Redmi note 3 (MTK) with the sole intention of running this ROM because I don't like MIUI but love the Xiaomi design and hardware. I never got an unlock code from Xiaomi and followed every guide written ever about getting TWRP etc onto this device and all failed. Finally this worked for me: https://xdaforums.com/mi-max/how-to/guide-installing-miui-v8-2-1-twrp-root-t3573550#post71638490

It's perfect and the performance is great, GTA:SA and Bully Scholarship edition running smooth with all graphics options to the max. Battery life is also excellent.

The only problem I have is that I can't change the alarm tone from the clock app, it just reverts to rooster alarm every time. If anyone knows how to fix that I'd love to know. Such a small issue though is an indication as to how good this ROM is being to me. Iv'e tested pretty much every function and have yet to find any other issues

Now I have a reasonably priced phone with a good specification, a big screen for my bad eyes and good software to run on it. All in all 100% Happy!
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Shuyin10:
Finally i'm return from PureNexus, I prefer Nijel's rom !

But i havebone question, is it possible to have a pixel theme on Lineage ? I prefer white and blue setting from pixel :D
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
New Harfix kernel version is up. Adreno idler is implemented (idles GPU at 19Mhz) and some other fixes, kernel is updated to latest sources.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Ranomez:
[MENTION=4399618]nijel8[/MENTION] I've reported this bug before but will report it again with a workaround: the Bluetooth volume levels 3 and 4 are bugged, there is a 2 levels difference between them, for example if you increase volume from step 3 to 4 it will increase 1 level then a a few seconds later you will hear another increase (still on level 4 but sound is louder than it should), the other way around for decreasing from 4 to 3.

The workaround I found: stop playback, bring the volume all the way down to 0, start and stop playback again then increase the volume to step 4 then start playback again (it will start on the bugged too loud step 4 of volume) then just increase volume again (volume + button) and for some reason the volume bar will go from 4 to 3 instead of 5 and this time decrease the volume by just 1 level not 2, after that the volume levels are fixed until you either disconnect the Bluetooth device or drop the volume back to 0/increase to max.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] pehoko:
Double tap to wake screen doesn't work on my device.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] nijel8:
Stop spamming. Your problem has nothing to do not just with this rom but any.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] pehoko:
On miui works.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ioy:
I'd like to run 'my' snippet applying kernel parameters on system boot so putted it in /etc/init.d as file '99kernelinit' with 755 rights, however it doesn't do its job, no settings applied. If I run it from a text console (better termimal) manually then it works perfectly and does its job, what's wrong with init.d?

------EDIT:

After adding the line:

#!/system/bin/sh
#

at the very top of the file it works now, is it really necessary?

------EDIT2:

Allright, but in init.d there is also the file:

/etc/init.d/90userinit

which runs userscript:

/data/local/userinit.sh

When I have pasted 'my' snippet there it, again, doesn't apply kernel parameters, while from a text console does. Why?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] nijel8:
Maybe you should learn some linux bash/shell scripting basics? :)
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] nijel8:
[MENTION=2621033]Ranomez[/MENTION]

There were some questionable bt updates from CAF upstream lately which in my view broke some things. Also there is a setting in Developer options about bt volume... Try playing with that.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] SakitJiwa:
little bug

notification led keeps blinking even i've open the app

its randomly happend, sometimes from wa msg, sometimes from app msg

to fix it I restart the phone and the blink gone. no big deal just a little annoying to see blinking led when I'm in a meeting
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] faorekh:
If you cannot read the thread use miui.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ioy:
It seems its somewhat more than just about basics, if added in the beginning of the file the command:

'sleep 3;'

then it started to apply kernel settings on boot.

HELIUM, LOCKED bootloader, [ROM][UNOFFICIAL][7.1.1][HYDROGEN/HELIUM]LineageOS 14.1 r.03-27-2017 by*nijel8
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
Some startup threads on Android are running concurrently,

for my scripts on earlier phone I have been using sleep 30 to 60 and even sometimes run the same script twice with different numbers.

There is nothing wrong or broken really but just the way it works, or perhaps it should work differently but it's so hard to trace that nobody cares to do it as long as it works in the end.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] careless_angel:
Hi nijel8 and all) Noticed this behavior, if you listen to music through a third-party music player in the background from aux/jack, when you receive an audio notification in the current application, Playback of background music starts to go through the speaker of the smartphone and partially through the headphone jack, if you pause and then press the play again, the music starts playing normally through the headphone jack. I tried to do full wipe, but did not help. I listen to music quite often in the car through aux, I will be happy if someone will help with the solution of this problem.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] kyler084:
I'm so glad you have said this!! I've experienced this bug on every AOSP Based 7.1.1 rom on my Helium, thought it was my Earphones so didn't report it, Glad someone else has noticed this though! Can be irritating if your walking through a shop listening to music and it starts blazing out of the phones speaker lol
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] IndDoc:
Could be a couple of things. Try this - put your alarm tones in /media/alarms folder. Second, if you have a memory card then don't put the alarm tones on external memory, put them on internal memory. Try playing your alarm tone via any audio player and see if it plays back and is not corrupted (try x-plore file manager, it is awesome for these kinds of things).
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mongoload:
Hi nijel, thanks for this great ROM!

May we know what is your computer build for compiling this ROM? Do you have VPS? I am really curious on what ROM developers like you use on daily basis, can you tell us something on what your setup is and what is your environment? Network connection?

I know its off topic and maybe not related to this thread, but where else should i ask it other than this thread?

Thanks in advance! Looking forward on a good read with excitement!
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] grey77:
Here some observations I made while using this great ROM.

a) There r some severe issues with accurate direct battery power reading in Trepn profiler.

(The readings are provided by the PMIC and fuel-gauge software so they are accurate)

https://developer.qualcomm.com/forum/qdn-forums/software/trepn-power-profiler/33517

Trepn fails to read GPU and LCD brightness as well, yet everything works in NitrogenOS and other ROMs.

b) Whenever I touch the screen or the fingerprint sensor, the following message spams the logcat, making it very hard to dump reasonable logs. I found some info that this quirk is rather Lineage OS related and yet can I suppress it? Logcat excerpt:

E/QCOM PowerHAL(11219): Failed to acquire lock.

c) Poweramp uses Hi-Res Output (192kHz/24bit qualcomm audio driver). It works on Android 6/7 ROMs. Recently it begins to fail with LineageOS14.1@nijel8: Output failed: Poweramp Hi-Res Exp Output. Logcat:

E/PlayerService(10264): Output failed=NativePlugin[76286982] uniq_name=com.maxmpz.audioplayer/output.athd id=4 flags=80000003 name=Poweramp Hi-Res Exp Output

Thanks in advance! :)
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ioy:
[MENTION=4232632]Zola III[/MENTION] thank you very much for reviewing this draft, its interesting your hint about altering

/sys/devices/system/cpu/cpu/core_ctl/not_preferred, N=(0,4)

It is balanced indeed, however what about other values (with priority to optimize power drain)?

Please review some additional settings to add to this snippet:

################################

# IO

echo 'deadline' > /sys/block/mmcblk0/queue/scheduler

echo '1473' > /sys/class/timed_output/vibrator/vtg_level

# GPU

echo '133333333' > /sys/class/kgsl/kgsl-3d0/devfreq/min_freq

echo '20' > /sys/module/adreno_idler/parameters/adreno_idler_downdifferential

echo 'Y' > /sys/module/adreno_idler/parameters/adreno_idler_active

echo '550000000' > /sys/class/kgsl/kgsl-3d0/max_gpuclk

echo 'simple_ondemand' > /sys/class/kgsl/kgsl-3d0/devfreq/governor

echo '20' > /sys/module/adreno_idler/parameters/adreno_idler_idlewait

################################

(As probably you have noticed power saving is my priority rather than efficiency boost. In the future it might change but now the phone is fast more than enough for me, just using it for phoning, internet browsing, emailing etc so power drain seems of much more concern to me. And presently, the system of recent release drains much more power than from 0319 of its default kernel settings. Even after the settings applied. How to recreate this configuration from 0319, please help?)

HELIUM, LOCKED bootloader, [ROM][UNOFFICIAL][7.1.1][HYDROGEN/HELIUM]LineageOS 14.1 r.03-27-2017 by*nijel8
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] FutureGamerz:
Just tested mine. Tap to wake is working with the latest version. Is it not supposed to work?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Zola III:
Well I don't try to optimise it to much to either spectra just balanced and optimal with satisfactory response across the workloads.

We could argue is 550MHz for a GPU optimal for me it ain't I will throttle it down even to 450MHz on extensive load over 30 min. I don't see modding if a deadline heuristic as something useful especially what would hurt its trough output like suggested, just enable IO signaling on it...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
I haven't found any rom based on Android 7 (LAOS or AOSP) that allows Poweramp beta (702, 703 or 704) to work in HiRes mode. The last rom that worked on was Resurection Remix 5.7.4 and of course standard MIUI based on Android 6.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] grey77:
thank u, mat9v, it seems ur right - the problem is not solved by the poweramp developers. I've found ur post on the original dev. forum:

http://forum.powerampapp.com/index....-hi-res-support/&do=findComment&comment=38425
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
As much as I like to have tasks start fast and smooth this kind of setup is not very good for long idle periods like reading texts, writing something and so on. In those cases phone has much less work to do and even 1 core is enough in most cases, or 1 small and 1 big core. The active to idle periods ratio in those cases is like 1000:1, you read for 10 minutes and then switch app or something and that creates some work. So by having 4 cores active all the time you gain 1/10th of a second while starting an app but loose 2-3 times the idle power because you have too many active cores.

If you recall what I stated (in PM and later in threads) that in my first battery tests conditions were not very equal and later I have found that in fact 2 active cores per cluster to be more energy inefficient (not much, but about 1-1.5h worse then my mostly standard 16h SOT).

In your script you state "# note: this should be applied & to core 5 (cpu5) + side note in the comment " - do you mean that about values stated above the comment or below? Because you can't have different values of (min_sample_time, scaling_min_freq, max_freq_hysteresi) on per core basis - all those values are equal for the whole cluster, they are inherited from core4.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] pehoko:
Tnx nijel8, donalberto17 for me works "96 DPAD_CENTER" and fingersensor acts like power button same as in miui, finally my broken power button have option to work on this rom :good:
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Zola III:
"In your script you state "# note: this should be applied & to core 5 (cpu5) + side note in the comment " - do you mean that about values stated above the comment or below?"

No I mean core per it's pair of L2 every first active so that you utilise all L2 at significantly lower call times as it's not shared instead using in line as it is when possible & it is a playable to most case scenarios as those are any way SMP2. & it's written behind the script in the coment. You won't lose much regarding of anything & I do halt core's not to bounce on small loads only case where CPU load isn't ideal (from real workloads) as it will be more on jump frequency than it could is music playback without much processing, I let it slide fast in between especially down. You won't lose much idling either.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Zola III:
[MENTION=2473722]mat9v[/MENTION] in your case not a fifth but sixth core.

write /sys/devices/system/cpu/cpu4/core_ctl/not_preferred "1 1 0 0"

Instead:

write /sys/devices/system/cpu/cpu4/core_ctl/not_preferred "1 0 1 0"

As I did on small cluster (as it's same across the boards).

Old mpdecision whose good with only one core idle per cluster but even QC moved on to per two for cluster, alucord old default whose two per cluster & so on. Tuning a hotplug is worse than listening to Suicidal Tendencies believe me.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] nijel8:
Nothing special, 7 year old setup, Intel Core i7-2600K Sandy Bridge Quad-Core 3.4GHz running at 4.7GHz since the beginning, 16GB DDR3 [MENTION=1796504]1600[/MENTION]MHz, Gigabyte GA-P67A-UD3-B3 motherboard, old intel 80GB SSD for sources, regular HDD for out folder, Ubuntu 16.10 64 bit. Clean builds Lineage in 40 minutes.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
Nope, typical QC (if by QC you mean Qualcomm) setup is to have all 4 small cores active and none of the big cores.

Custom hotplugging is as diverse as there are developers behind it. My way is only 1 small and 1 big core active permanently and if you say that most tasks on Android are still 2-threaded then I would prefer that they share cache to more easily exchange data as it would happen when second thread is spawned, another core on the same cluster would be brought online. Remember that most programs are heavily interdependent and exchange data between threads, while the programs we use to check performance are threaded so to be non-dependent, because that way they can more easily show differences in number and speed of cores.

Typical user tasks are in fact very different from static benchmarks, just look on PC platform and it's benchmarks, where most interesting and closest to life benchmarks take hours to complete and most of them are based on real apps with real documents being created - the so-called "app trace" benchmarks.

In the example you mentioned few posts earlier, where you show 30% performance improvement over 6% more power used, you measured that using what? and how? using some benchmark like linpack or something, that loads selected core and is completely non-dependant on other tasks and threads? That is not in any way a real life load and while it does provide constant and easily interpreted data it does not help to get the "perfect balance" of power and performance because, again, it does not represent real life situations.

I'm sorry if my position is a bit stiff on this subject but I'm currently testing some Ryzen setups and fighting with stupid Microsoft scheduler settings (and those hidden in strange registry entries) that decide when and how to unpark sleeping cores, when and how to increase core frequency and so on. I just keep finding that on Ryzen it is sometimes better to force the program to run on 8 threads (4 HT threads included) on one CCX (first half of CPU) then let it use all 8 hardware cores (without HT) on both CCX and stumble on inter-core communication problems. Yeah, synthetic benchmarks are mostly blind to it while strangely some professional apps suffer and most games suffer a lot from this.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] nijel8:
Regarding hotplugging small cores... Ask yourself why there is no any official(custom or not) ROM that does it... Why there is no single kernel app with settings for small cores core-ctl... I am not an expert but there must be a reason for all that. And if those who knows better don't core_ctl little cluster so do I. Tried couple of times and performance suffers... ALWAYS! And what's the gain? Nothing that would matter in real use if any...

Just my 2¢...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Zola III:
[MENTION=2473722]mat9v[/MENTION]

Simple as it goes; the 2x L2 with duble bandwidth can duble input which leads to the greater increase of SMP integer performance as it is fpu performance already scales good in MP so it will gain less. Statically keeping cache awake counts for less than 10% power consumption compared to two core's with shared L2 cache. Just started MP2 task will be issued to the first two core's on the same cluster available. I can show you plenty example how shared L2 access diminishes performance.

Ryzen 7 is actually dual cluster quad core with hyper threading, it doesn't have shared L2 design as ARM core's instead L2 is per core & besides it relies on L3 that is probably shared per cluster. We don't really know what bus did AMD used but still 8 cores without HT should be much faster than 4 with HT, HT brings 22~46% performance increase while 8 straight should scale at least 60%. Busy signaling is actually useful especially in mixed up setups as Ryzen so try with Ubuntu at least. Synthetic benchmarks are what they are but 96% software have some MP2 support this day's letting one active idling core per cluster will save some juice only if on big cluster is nothing to be executed so only one is active present. On Android with all systems noise and background tasks you will find really rarely only one small one active. Real through is you can't adjust logic for the all tasks & that's why ARM is bringing in mixed multi cluster units next (example a FPU task will execute 20~30% faster on 4 A53 than two A72 while using less then half energy but you won't have much of MP4 capable FPU workloads if you don't use specialised math lib & I am certain you won't).