yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] kevinpunk:
The day VOLTE is supported i will flash this rom.. i am done with miui.. i have used oneplus one for a while and i love stock android skin

I use my mi max as my secondary phone and i use it mostly for calls and msges thats why i need VOLTE...

So No video recording or other bug .. no issue for me

JUST waiting for VOLTE supportðŸ™ˆðŸ™ˆ
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] eseregin:
Hm... What's so miracle in VoLTE? As far as I understand, LTE itself give you internet, voice transferring, SMS, MMS - everything...

Why VoLTE is dealbreaker? Better sound?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
No, some networks don't offer normal voice connections, they only allow Voice over LTE so on such a network you can't make voice calls - it's a dealbreaker :)

Sound quality is not any better then HDVoice that is supported on HSDPA networks but is much cleaner then standard GSM voice connection.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] oatcooky:
Because some people like Jio users are stuck with LTE only service for data and voice, hence why they need VoLTE. Everyone else can use UMTS, GSM or CDMA for voice and SMS fallback.

I'm waiting for CDMA support over R-UIM on SIM2 to come to LineageOS.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] tbhuy:
Hello,

I've this problem while flashing: Error: E3004: this package is for device: hydrogen this device is helium.

How to fix it pls?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] dennis46419:
Edit with total commander the word hydrogen to helium and repack the zip it's totally easy I add screenshots
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] oatcooky:
If you can get the network settings options to appear like in the attached image, then CDMA should work. This is from RR 5.7.4.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] tombassi:
yes that is the problem, proffered network type is not working from both settings and by dialing *#*#4636#*#* it has no effect no matter what option you choose.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] tbhuy:
Thanks, it worked.

I was just afraid of flashing the wrong version
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] sp0979:
Review for Hydrogen:

1. Pretty smooth & stable.

2. Battery backup pretty good. (Rr 5.7.4 from same dev was best).

3. No mod / kernel used.

4. Using greenify & controlled apps boot via privacy guard.

5. Small issue: wifi toggle.

6. Jio working well.

7. No Volte support.

One of the best rom available for daily driver.

Thanks a lot [MENTION=4399618]nijel8[/MENTION] for all your hardwork & efforts.

Just a small request, if you could give Volte support patch separately.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] jutley:
Anyone got lineage wallpaper? And what DPI are all of us using on this ROM find 300 DPI is perfect.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] eseregin:
Use standard 360 DPI... Think looks good...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Skalexs:
After some testing, it's the best nougat ROM so far.

I don't care about soft rebooting after boot to make sim working because I don't use to shut down it

Hoping to get GPS working :laugh:
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] log30:
I have an issue, someone try it please to confirm the bug:

Record a full hd video , transfer to PC and try to play.

In my laptop appers 50â„… of the video with blur but if i use vlc is working well

Enviado desde mi Mi Max mediante Tapatalk
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] jpph:
Hi,

I have same issue on cell data not working. Rr is not working neither...

I come from miui 8...

I have a mi max 128g helium, I was able to modify the update script as shown before in this thread thanks to dennis

Edit:thank you skalex, soft reboot is working!

For the others, soft reboot is available after enabling it in developers optiond
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] aaryan45:
Please see this issue [MENTION=4399618]nijel8[/MENTION].. Any workaround will help!
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
He did state that it happens with SOME bluetooth car setups, right? So it can work with yours all right....
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] dktblade:
i feel like the volume still lower than Stock Miui.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Kevinkuensken:
How loud is the phone?i want to use it AS navigation and want to hear radio
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] sebr:
For me (Hydrogen) auto brightness does not work. It stick to the same brightness (looks like around 50%), no matter if I am in total darkness or put the device und the lamp on my desk.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] oatcooky:
Are you using SuperSU? You need to flash the latest SR3 version because older versions disable all sensors including the brightness sensor.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] sebr:
That solved it. Thank you very much :)

Another question: transmitting the display (WiDi) to my Samsung TV does not work. There are simply no devices shown. Is there also any fix for this yet?

PS: I'm on fresh install on latest Hydrogen ROM. Tried both firmware packages as well. :(
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] neoavi7:
Anyone facing network issue on this ROM? My network disconnects and connects every 5 mins or so. Don't know if it's ROM or the Network mode I'm using. I've tried almost all the options.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
You did flash firmware fix after flashing ROM? I've had problems with LTE and calling when I migrated straight from MIUI 8.1.6 to Nijel8's ROM but it all disappeared after the patch.

If it does not work for you, go to recovery, make backup, format /system /data and /cache and install ROM from scratch. If it works, restore /data from backup and check if your problem disappears.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ikaros80:
i have the same problem, what you mean sr3?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] aussiepr:
see here https://download.chainfire.eu/1021/SuperSU/
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ikaros80:
i flash the new twrp but still auto brightness not working

---------- Post added at 05:15 PM ---------- Previous post was at 05:04 PM ----------

the superSU ask for update, but failed

---------- Post added at 05:33 PM ---------- Previous post was at 05:15 PM ----------

and something else in the last rom , is not the same camera apk, τhe previous was better with more settings
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] pehoko:
Yes, I also confirm that "dirty supersu" always break auto brightness in all nougat.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
Except SR3 SuperSU version.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] hans william:
For me SU SR3 is working fine
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ikaros80:
Except SR3 SuperSU version.????
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] faorekh:
SR3-SuperSU-v2.79-SR3-20170114223742.zip
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ikaros80:
what about this?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
Does not break sensors on

dirty flash

like older versions of SuperSU did on CM14.1 (Lineage)
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] IndDoc:
Yep, same problem. Cannot select any network type apart from 'global'. Only major bug I've encountered on the ROM.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] oatcooky:
That's weird, I'm using the latest update with the 6.12.29 firmware files and the phone has no problem switching between LTE, WCDMA and GSM. Data and calls work fine, VoLTE is working also.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] IndDoc:
Here is a video I recorded showing the problem. Note how the network mode changes rapidly - http://sendvid.com/o2gm4fvn
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] nijel8:
Change modem... I have seen different sim cards works with different baseband. Try the two from OP... Recently user from 4PDA had success with modem from latest official MIUI Dev Global 6.1.22.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] RomanGeorg:
You are absolutely right! I know at least three users who helped.

But the modem can be everyone is different, you need to find.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Skalexs:
My problem was that I could change to GSM or HSDPA and then I lost all the signal, including calls. It means that I lost all mobile network if I lost LTE.

This issue was fixed in last build :laugh:

Now, this is the only Rom that let me work with all networks. I'm happy for it and sad because it seems that any other dev matters about it, and also it seems it can't be solved with a patch like other bugs.

I would like to use RR for the customization, but its based on official lineage os builds, instead of nijel's one :(
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Makshow:
Hi there! Flashed this ROM on my new Mi Max 3/64 helium. It works just flawlessly! So smooth, rock stable, no bugs found for the 2 days of testing, everything is awesome! And kernel has great options: hotplug for big cores (why Xiaomi didn't use it on Stock?) and min freq of 400 MHzm got 11 hours SoT on first day after setting this. Using 7.1.15 firmware from first post.

Awesome job, [MENTION=4399618]nijel8[/MENTION]! You can mark this ROM as stable for sure.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
Where did you see hotplug governor in this rom/kernel combo? As far as I know it does not have it. Maybe you flashed some other kernel?

Aside from that I agree, it's a perfect rom for this phone. Only thing it lacks is Substratum :)
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] nijel8:
He is talking about core control.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] oatcooky:
I thought the voltages for 400/691 MHz on the A53 cluster and 400/883 MHz on the A72 cluster were the same. That means it's better to set min frequency to the higher values for a faster race to sleep. You'd end up using more power on 400 MHz because it takes longer to do stuff.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
400Mhz is an idle state, the moment any significant task is to be done it jumps up. Small cores never sleep and big ones sleep almost constantly, there is practically no gains to be had (as long as you set min_big_cores to 0)
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] oatcooky:
Any problems if I set the min big cores to 0? I thought the default value was 1 for hydrogen.

I assume you'd get slightly more responsive performance with min frequency set to one step above 400 MHz because the scheduler doesn't have to wait before ramping up speed. Most of the time the base speed doesn't get used much because the little cores ramp up to 1305 MHz with heavy load.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Zola III:
Absolutely wrong! 400MHz is perfectly enough for OS wite noise & small background tasks if managed good by the CPU governor. Interactive governor (that is default) have intermediate frequency that it jumps to directly when requirements are meet & from there it scales up or down based on requirements & calculation parameters. Interactive is also very configurable and can be adjusted for better battery life (as I already talked plenty about that I won't be doing it again hire).

I also think it should be kept at 1 (min big cores in active idle state). If you want more responsiveness cut the scheduler cycle to 20000 (which is basically the time you need to blink the eye so no need to go under that at least regarding subjective experience that you can feel)...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] oatcooky:
Anyone having Bluetooth calling issues? When paired with my car BT system, I can't answer calls, the call keeps ringing but swiping the phone icon to answer doesn't work. The phone keeps thinking it's ringing, I have to reboot the phone to get calling to work again.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
No, not really, this kernel/system has "input boost" otherwise called "touchboost" and it is an instant boost to 1305Mhz once any user input is detected - it is momentary and in most cases will not be detected by software that measures median frequency on stretch of seconds - but it is there and you can see it in statistics (on my screenshot 1305Mhz clocked at over 2 minutes from just input boost) so there is no chance at stuttering. In Kernel Adiutor you can set minimal interval that cores will stay in boost mode after input detection. Really there is no situation that will result in stuttering when your interaction is required and when there is some program running and doing computations the cpu will upclock anyway including migrating to big cores under enough load.

Although power use difference between 400Mhz and 691Mhz is small, every mW matters so why not save it?

My typical battery life below:
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] oatcooky:
Are you getting 13 hours screen on time on a full charge? My highest figure was 11 hours with WiFi, LTE and Bluetooth all on.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
Probably close to 15 hours, as I have 19% battery left and 13.5 hours sot now. Bluetooth is always off - I just don't use it, LTE is always on (with data) and WiFi is mostly off, only turned on to transfer files to/from local ftp. GPS is on but rarely used. Brightness is 50% with auto so I don't really know how bright it is on average.

My highest figure was over 20 hours, it was reading books on a long connected flight from Poland to Australia. Not happy that I did not take a screenshot then :(
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] dinhvtai:
Could you please share which kernel and which setup are you applying now? Thanks :D
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Zola III:
He uses regular kernel that comes with ROM as their is no alternative yet to it & specially not the one he would want.

What he does is disabling the big cores boost function by putting them to sleep (min big cores 0), which is also much performance diminishing...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
What are you talking about?

I'm setting min_big_cores to "0" so they are sleeping at default, but they wake up when required. Also core boost function is not disabled, it is left as default, I even mentioned that I had over 2 minutes at 1305Mhz due to touch boost working. Please don't take part in conversation when you do not know the answers.

For all interested in my config here are screenshots of relevant parts in Kernel Adiutor:

Below is my "init.qcom.power.rc" file that contains any modification done to boot files.

And some things I add to build.prop:

net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.hspa=6144,87380,524288,6144,163 84,262144
net.tcp.buffersize.lte=524288,1048576,2097152,5242 88,1048576,2097152
net.tcp.buffersize.hsdpa=6144,87380,1048576,6144,8 7380,1048576
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144, 87380,1048576
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.wlan0.dns1=8.8.8.8
net.wlan0.dns2=8.8.4.4
net.eth0.dns1=8.8.8.8
net.eth0.dns2=8.8.4.4
net.gprs.dns1=8.8.8.8
net.gprs.dns2=8.8.4.4
net.ipv4.ip_no_pmtu_disc=0
net.ipv4.route.flush=1
net.ipv4.tcp_ecn=0
net.ipv4.tcp_fack=1
net.ipv4.tcp_mem=187000 187000 187000
net.ipv4.tcp_moderate_rcvbuf=1
net.ipv4.tcp_no_metrics_save=1
net.ipv4.tcp_rfc1337=1
net.ipv4.tcp_rmem=4096 39000 187000
net.ipv4.tcp_sack=1
net.ipv4.tcp_timestamps=1
net.ipv4.tcp_window_scaling=1
net.ipv4.tcp_wmem=4096 39000 18700
persist.telephony.support.ipv6=1
wifi.supplicant_scan_interval=5000
ro.config.hw_fast_dormancy=1
ro.config.hw_quickpoweron=true
persist.sys.usb.config=mtp

That is all :)
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] RomanGeorg:
Not true! I also use, but not pushing or impacting the performance of the no! Antutu the result of 90,000+!
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Zola III:
I won't argue with you, you tend to go into opposite radical settings (first it whose performance settings big cores to jump directly to the 1.8GHz mismatching the hi frequency load tunable in interactive & now opposite direction with disabling C0 (active idle state) for all cores on the big cluster also disabling their primary function to jump in when the app is launched. Input boost is something totally different & pretty much useless if you ask me (litle benefit & socks battery) especially when set as that (& over the top end matched frequently with a contained leaking for given lithography). I usually always disable it. It jumpes most of the time thanks to the Hi speed load interactive tunable and not that much because input boost one all do input boost one actually push it there even when their is no need for that. Think you have much more to learn about heuristics and infrastructure in general.

---------- Post added at 05:54 PM ---------- Previous post was at 05:46 PM ----------

Yes but big cores than can not jump in quickly especially when they need it most when they are supposed to start a new process on (which is by the way their primary intended function as a boost big cluster) like launching an app resulting on a sluggish performance there & there for far from desired user experience. Just think about it!
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] RomanGeorg:
It n not so much that it is not worth it to worry about it! But saving battery
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Zola III:
Well for me it's worth, intended & SoC is designed for. One A72 [MENTION=4149147]1.8[/MENTION]GHz is faster than two A53's at 1.4GHz (all do it will also use at least twice as much power [A72]). I prefer to leave the thing work as intended. From a design stand point only the A73's are capable enough to be more power/performance efficient in given scenario than A53's...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] RomanGeorg:
Use as you wish! )) Everyone decides for himself that he is important!

The performance difference is not present! There is a 0.1% difference in response time, nothing more!
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] mat9v:
You may have to educate all of us on that :) Well, me certainly.

I'm not defending my settings but to summarise:

- disable boost in "/proc/sys/kernel/sched_boost"

- migrate between clusters "/proc/sys/kernel/sched_downmigrate 40" and "/proc/sys/kernel/sched_upmigrate 60" further modified in Kernel Adiutor for testing, don't really want to reflash kernel constantly

- "go_hispeed_load 65" for big cluster - go for high speed at 65%

- "hispeed_freq 1382400" - high speed target is 1.38Ghz

- "target_loads "65 1382400:80 1747200:75"" - do you see any conflict with the above? if so , explain?

Where in my config do I jump straight to 1.8Ghz ?

Why do I disable C0? Because the power strain of sometimes turning the cluster on is much less then keeping it on all the time. Most of the tasks is easily handled by small cores when they jump to high load, if not I made it easy to transfer tasks to big cores and quickly ramp up their speed to quickly finish the tasks. It does make a difference in battery life. Does it create stutter, no, why would it? Do you think that small cores can't handle scrolling or interface transitions? If that were so, phones without big cores would always stutter. Big cores are here only to take care of big sustained loads.

Look at my config - sched_downmigrate and sched_upmigrate - it is much lower then standard values and forces big cores to come online earlier and stay on longer then default. Come to think about it they should be higher because as they are they migrate tasks too early not allowing small cores to ramp up fully (and maybe they would be able to take care of the tasks on their own - will have to change that). That will probably save some battery at the cost of speedily taking care of tasks.

Input boost is disabled, look at screen 8 and 9 - it is disabled both for small and big cores - go_hispeed_load, hispeed_freq and target_loads control frequencies in this config.

There are 2 ways to deal with tasks,

1 - "slowly" increase frequency and core count (and migrate to big cores) under load - it takes more time and may induce stuttering

2 - "quickly" jump in frequency and core count (and in this case migrate to big cores) - work done quickly but at higher frequency - uses more energy at higher frequency but for shorter time - no chance of stutter

I prefer 2nd option and it works well for my needs and battery life. Please provide your settings and I will happily test them for myself, if they work for me better I will adapt them :)
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Zola III:
"hispeed_freq 1382400" - let it stay like that for big cluster & for a little one adjust it to be as close to 1GHz as possible.

"target_loads "65 1382400:80 1747200:75"" - put them higher to at least 90 for 1.38GHz (same goes for small cluster at 1GHz) to prevent unnecessary jumps beyond that frequency more often & 40-45 should be enough for a base. & put a good damn minimum of idling cores on a big cluster to 1 so that newly run task that is preliminary ment to be run on it can natively start there and then migrate to the smal cluster when initialised and running as the way you do it it's impossible as the core must be; waked, powered & tested first (which actually takes quite some time) & only then loaded & used so as you force it tasks always start on a small cluster to if their is extended need then be migrated to the big cluster & then again backed on the small one. If you get me correct this actually bricks the order as it's intended to be used. Set off line delay for big cores down to 40~60ms. Switch back to FCQ for IO governor (as I assume deadline is still not enabled if it is switch to it) & switch IO states off (will increase output a bit). Put back RAM caches for storage partitions to 512KB as this way (with keeping it on 4MB) you really really hurt asynchronous & random R/W & that what you gain on sequential is really not worth it, that is if that is what screanshot 4 represents. Put min sample time to the 20000 let's let them upscale & down scale faster by cutting internal scheduler ticks in half & enable IO is busy signaling do the same for both clusters. Also keep above high speed delay on 40~60ns, I find value you used on small cluster (59ms) as a good one but would actually sync them to scheduler ticks (so with it put to 20ms either 2 or 3 ticks which is 40 or 60ms).

In short that is all from what you showed me on so far.

Best regards.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] sebr:
As I mentioned earlier I face the same problem on my Hydrogen. Is there any workaround for this or will this bug be addressed with next update?

Aside from that I not find any flaws and this is so far the best ROM for me. Keep up the good work!:good: